eigrp convergency.

stephtchoko · ‎07-23-2005

Good day,

I 'm configuring two hosts RTA (UBR7246) and second RTB (UBR7111),

le link between RTA and RTB is done by interface cable of UBR7246 which is connected via docsis wireless to interface fastethernet 0/1 of UBR7111.

The adjency cannot be established between the 2 hosts,

There is show message:

RTA#show ip eigrp interfaces cable 3/0

IP-EIGRP interfaces for process 100

Xmit Queue Mean Pacing Time Multicast Pending

Interface Peers Un/Reliable SRTT Un/Reliable Flow Timer Routes

Ca3/0 1 0/0 0 0/10 50 0

RTB#show ip eigrp neighbors

IP-EIGRP neighbors for process 100

RTB#show ip eigrp traffic

IP-EIGRP Traffic Statistics for process 100

Hellos sent/received: 943/0

Updates sent/received: 0/896

Queries sent/received: 0/0

Replies sent/received: 0/0

Acks sent/received: 0/0

Input queue high water mark 1, 0 drops

SIA-Queries sent/received: 0/0

SIA-Replies sent/received: 0/0

There are log messages from RTA

RTA#debug ip eigrp

6d10h: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 131.107.2.171 (Cable3/0) is

down: retry limit exceeded

6d10h: destroy peer: 131.107.2.171

6d10h: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 131.107.2.171 (Cable3/0) is

up: new adjacency

Any help will be appreciate.

Best regards

Richard Burts · ‎07-23-2005

This seems to have symptoms of one way traffic.

It would be helpful if you would post the config of both routers (at least interface and routing protocol) and also any log messages from the other router.

HTH

Rick

HTH

Rick

stephtchoko · ‎07-24-2005

RTA#show ip eigrp neighbors

IP-EIGRP neighbors for process 100

H Address Interface Hold Uptime SRTT RTO Q Seq Typ

e

(sec) (ms) Cnt Num

0 131.107.2.171 Ca3/0 13 00:00:51 1 5000 2 0

1 196.202.232.1 Fa0/0 10 04:41:22 1 200 0 151

This log message appera everytime:

6d23h: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 131.107.2.171 (Cable3/0) is

down: retry limit exceeded

6d23h: destroy peer: 131.107.2.171

6d23h: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 131.107.2.171 (Cable3/0) is

up: new adjacency

!

there is log message:

RTB#

Jul 24 15:07:10.125: EIGRP: Sending HELLO on FastEthernet0/1

Jul 24 15:07:10.125: AS 100, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

Jul 24 15:07:10.437: EIGRP: Received UPDATE on FastEthernet0/1 nbr 131.107.2.172

Jul 24 15:07:10.437: AS 100, Flags 0x1, Seq 446/0 idbQ 0/0

Jul 24 15:07:10.437: EIGRP: Neighbor(131.107.2.172) not yet found

Thanks

Richard Burts · ‎07-24-2005

I think the issue is mostly the configuration of RTA. I notice that RTA has a single network statement which is:

network 196.202.232.0

This network statement matches the primary address of FastEthernet0/0 and matches one of the secondary addresses on Cable3/0. It does not match the primary address on Cable3/0. One of the things about EIGRP is that it forms adjacencies on the primary address. So the primary address should be matched in a network statement in EIGRP.

I suggest that you include a network statement in RTA for 131.107.2.0 similar to the one you have configured in RTB. When both routers have network statements for the primary address I think they will work much better.

Try it and let us know if it works better.

HTH

Rick

HTH

Rick

stephtchoko · ‎07-25-2005

Ok,

I include network 131.107.2.0 0.0.0.255 on RTA eigrp 100 configuration.

From RTA

RTA#show ip eigrp neighbors

IP-EIGRP neighbors for process 100

H Address Interface Hold Uptime SRTT RTO Q Seq Ty

e

(sec) (ms) Cnt Num

0 131.107.2.171 Ca3/0 12 00:01:12 1 5000 2 0

1 196.202.232.1 Fa0/0 11 16:19:25 3 200 0 163

From RTB

RTB#show ip eigrp neighbors

IP-EIGRP neighbors for process 100

RTB#show ip eigrp traffic

IP-EIGRP Traffic Statistics for process 100

Hellos sent/received: 24878/0

Updates sent/received: 0/19227

Queries sent/received: 0/0

Replies sent/received: 0/0

Acks sent/received: 0/0

Input queue high water mark 1, 0 drops

SIA-Queries sent/received: 0/0

SIA-Replies sent/received: 0/0

RTB doesn't see RTA as its neighbor.

Best regards.

Richard Burts · ‎07-25-2005

I am sorry that adding the network statement on RTA did not fix the problem. I still think that having that network statement is a good thing.

I would like to see the output of show ip eigrp interface from both routers.

Looking at the eigrp traffic on RTB is interesting. Would you post the output of that command on RTA also?

Looking at the statistics in show ip eigrp traffic I get the feeling that traffic may be one way. Are the routers communicating both directions? Does CDP run on these interfaces? If so it would be helpful to see the output of show CDP neighbor on both of the routers. Can both of the routers ping to the other router?

HTH

Rick

HTH

Rick

stephtchoko · ‎07-25-2005

The cdp protocol is not supported by cable interface of UBR7246.

There are show ip eigrp interface from the two routers:

RTA#show ip eigrp interfaces

IP-EIGRP interfaces for process 100

Xmit Queue Mean Pacing Time Multicast Pending

Interface Peers Un/Reliable SRTT Un/Reliable Flow Timer Routes

Ca3/0 1 0/0 0 0/10 50 0

Fa0/0 1 0/0 9 0/10 50 0

RTB#show ip eigrp interfaces

IP-EIGRP interfaces for process 100

Xmit Queue Mean Pacing Time Multicast Pending

Interface Peers Un/Reliable SRTT Un/Reliable Flow Timer Routes

Fa0/1 0 0/0 0 0/10 0 0

The router RTB can ping RTA

RBT#ping 131.107.2.172

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 131.107.2.172, timeout is 2 seconds:

!!!!!

Is the interface cable of UBR7246(RTA) can send a multicast traffic ?

Best regards.

Richard Burts · ‎07-25-2005

One way to check this is to do a ping 224.0.0.10 (you probably need to be in privilege mode to do this). I would suggest doing it on both RTA and RTB.

Try it and let us know what happens.

HTH

Rick

HTH

Rick

stephtchoko · ‎07-25-2005

from RTA:

RTA#ping 224.0.0.10

Type escape sequence to abort.

Sending 1, 100-byte ICMP Echos to 224.0.0.10, timeout is 2 seconds:

Reply to request 0 from 196.202.232.1, 4 ms

From RTB

RTB#ping 224.0.0.10

Type escape sequence to abort.

Sending 1, 100-byte ICMP Echos to 224.0.0.10, timeout is 2 seconds:

Reply to request 0 from 131.107.2.172, 48 ms

Best regards.

Richard Burts · ‎07-25-2005

I think this demonstrates that there is a one way flow of traffic. When RTA sends the ping it should have gone out both interfaces FastEthernet0/0 and Cable3/0. It only received a response from the neighbor on FastEthernet0/0 and not from the neighbor on Cable3/0. I take this as an indication that the multicast packet did not get to RTB. If you really want to prove this I think you should turn on debug ip icmp on RTB and do the ping from RTA again. I believe that the debug will show that the ping does not get to RTB.

I do not have enough experience with the UBR7246 to know what the issue is with sending multicast. Perhaps someone with more experience in this area can contribute something.

HTH

Rick

HTH

Rick

stephtchoko · ‎07-28-2005

Please,

help me, how can i set interface cable to send hello ?

Best regards.