From: Marc (tan@dia.janis.or.jp)
Date: Tue May 13 2003 - 22:56:25 GMT-3
EIGRP discovery process uses multicast. If that multicast address was
blocked/filtered, maybe the neighbor command is your best option. I recall
from Doyle v1 the neighbor adjacency/hello/acknowledge process jumps back
and forth from multicast to unicast depending on various things and unicast
is a last resort before declaring neighbor down. But if you use neighbor,
then all eigrp messaging in unicast.
And I believe multicast is blocked out the interface that has the neighbor
as well. In rip, if you do neighbor command, broadcasts still sent in
addition to unicasts. If you add passive-interface, then broadcast
suppressed. But for eigrp (definitely not 100% on this), using neighbor also
does a sort of passive interface on the interface assigned the subnet of the
neighbor command. I don't think this would come up in an exam. But keep in
mind the first part about discovery process relies on multicast unless use
neighbor command.
Marc
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> ccie2be
> Sent: Wednesday, May 14, 2003 2:12 AM
> To: Group Study
> Subject: Eigrp's neighbor command
>
>
> Hi all,
>
> When is it necessary to use the neighbor command under the
> Eigrp process?
>
> Jim
This archive was generated by hypermail 2.1.4 : Mon Jun 02 2003 - 15:13:41 GMT-3