eigrp neighbor command ?

Answered Question
Feb 26th, 2008

Hi,

Does the 'neighbor' command under eigrp send a unicast request to the neighbor as opposed to the multicast address 224.0.0.10 ?

Regards,

Phil.

I have this problem too.
0 votes
Correct Answer by Edison Ortiz about 8 years 9 months ago

Hi Phil,

That's correct.

See my debug below

Rack1R2#

*Mar 1 00:05:09.923: IP: s=192.168.12.2 (local), d=224.0.0.10 (Serial1/0), len 60, sending broad/multicast

Rack1R2#

Rack1R2(config)#router eigrp 1

Rack1R2(config-router)#neighbor 192.168.12.1 Serial1/0

Rack1R2(config-router)#end

Rack1R2#

*Mar 1 00:06:27.283: IP: tableid=0, s=192.168.12.1 (Serial1/0), d=192.168.12.2 (Serial1/0), routed via RIB

*Mar 1 00:06:27.287: IP: s=192.168.12.1 (Serial1/0), d=192.168.12.2 (Serial1/0), len 60, rcvd 3

*Mar 1 00:06:28.215: IP: s=192.168.12.2 (local), d=192.168.12.1 (Serial1/0), len 60, sending

*Mar 1 00:06:28.291: IP: tableid=0, s=192.168.12.1 (Serial1/0), d=192.168.12.2 (Serial1/0), routed via RIB

*Mar 1 00:06:28.295: IP: s=192.168.12.1 (Serial1/0), d=192.168.12.2 (Serial1/0), len 60, rcvd 3

*Mar 1 00:06:28.303: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 192.168.12.1 (Serial1/0) is up: new adjacency

*Mar 1 00:06:28.307: IP: tableid=0, s=192.168.12.1 (Serial1/0), d=192.168.12.2 (Serial1/0), routed via RIB

*Mar 1 00:06:28.311: IP: s=192.168.12.1 (Serial1/0), d=192.168.12.2 (Serial1/0), len 40, rcvd 3

*Mar 1 00:06:28.319: IP: s=192.168.12.2 (local), d=192.168.12.1 (Serial1/0), len 60, sending

*Mar 1 00:06:28.327: IP: s=192.168.12.2 (local), d=192.168.12.1 (Serial1/

Rack1R2#0), len 40, sending

*Mar 1 00:06:28.419: IP: tableid=0, s=192.168.12.1 (Serial1/0), d=192.168.12.2 (Serial1/0), routed via RIB

*Mar 1 00:06:28.423: IP: s=192.168.12.1 (Serial1/0), d=192.168.12.2 (Serial1/0), len 40, rcvd 3

*Mar 1 00:06:28.435: IP: s=192.168.12.2 (local), d=192.168.12.1 (Serial1/0), len 40, sending

*Mar 1 00:06:28.507: IP: tableid=0, s=192.168.12.1 (Serial1/0), d=192.168.12.2 (Serial1/0), routed via RIB

*Mar 1 00:06:28.511: IP: s=192.168.12.1 (Serial1/0), d=192.168.12.2 (Serial1/0), len 40, rcvd 3

HTH,

__

Edison.

Correct Answer by adam.sellhorn about 8 years 9 months ago

yep. Here is more information regarding the neighbor command if interested.

http://www.cisco.com/warp/public/103/eigrpfaq.shtml#ten

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Correct Answer
Edison Ortiz Tue, 02/26/2008 - 10:31

Hi Phil,

That's correct.

See my debug below

Rack1R2#

*Mar 1 00:05:09.923: IP: s=192.168.12.2 (local), d=224.0.0.10 (Serial1/0), len 60, sending broad/multicast

Rack1R2#

Rack1R2(config)#router eigrp 1

Rack1R2(config-router)#neighbor 192.168.12.1 Serial1/0

Rack1R2(config-router)#end

Rack1R2#

*Mar 1 00:06:27.283: IP: tableid=0, s=192.168.12.1 (Serial1/0), d=192.168.12.2 (Serial1/0), routed via RIB

*Mar 1 00:06:27.287: IP: s=192.168.12.1 (Serial1/0), d=192.168.12.2 (Serial1/0), len 60, rcvd 3

*Mar 1 00:06:28.215: IP: s=192.168.12.2 (local), d=192.168.12.1 (Serial1/0), len 60, sending

*Mar 1 00:06:28.291: IP: tableid=0, s=192.168.12.1 (Serial1/0), d=192.168.12.2 (Serial1/0), routed via RIB

*Mar 1 00:06:28.295: IP: s=192.168.12.1 (Serial1/0), d=192.168.12.2 (Serial1/0), len 60, rcvd 3

*Mar 1 00:06:28.303: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 192.168.12.1 (Serial1/0) is up: new adjacency

*Mar 1 00:06:28.307: IP: tableid=0, s=192.168.12.1 (Serial1/0), d=192.168.12.2 (Serial1/0), routed via RIB

*Mar 1 00:06:28.311: IP: s=192.168.12.1 (Serial1/0), d=192.168.12.2 (Serial1/0), len 40, rcvd 3

*Mar 1 00:06:28.319: IP: s=192.168.12.2 (local), d=192.168.12.1 (Serial1/0), len 60, sending

*Mar 1 00:06:28.327: IP: s=192.168.12.2 (local), d=192.168.12.1 (Serial1/

Rack1R2#0), len 40, sending

*Mar 1 00:06:28.419: IP: tableid=0, s=192.168.12.1 (Serial1/0), d=192.168.12.2 (Serial1/0), routed via RIB

*Mar 1 00:06:28.423: IP: s=192.168.12.1 (Serial1/0), d=192.168.12.2 (Serial1/0), len 40, rcvd 3

*Mar 1 00:06:28.435: IP: s=192.168.12.2 (local), d=192.168.12.1 (Serial1/0), len 40, sending

*Mar 1 00:06:28.507: IP: tableid=0, s=192.168.12.1 (Serial1/0), d=192.168.12.2 (Serial1/0), routed via RIB

*Mar 1 00:06:28.511: IP: s=192.168.12.1 (Serial1/0), d=192.168.12.2 (Serial1/0), len 40, rcvd 3

HTH,

__

Edison.

Kevin Dorrell Wed, 02/27/2008 - 00:22

Yes it does. Unlike RIP, setting a static neighbor in EIGRP will inhibit the multicast. RIP with a static neighbor will continue to send a multicast as well.

OTOH, the behavior of passive-interface is different in RIP than in EIGRP.

I investigated this recently and wrote a short piece about it in my blog, if you are interested:

http://dorreke.wordpress.com/2008/02/11/static-neighbors/

Kevin Dorrell

Luxembourg

Actions

This Discussion