Re: 5000 RTO EIGRP

Report Inappropriate Content · ‎07-06-2012

Hi everybody,

I have a issue in my network, i have 2 data connections with 2 different ISP (Principal & Backup connection).

But with ISP "X" the RTO are stable (RTO 240), but with the ISP "Y" the RTO is in 5000 and the connection always are flapping

What can i say to my "Y" ISP?

Thanks!!

Francesco Pettene · ‎07-06-2012

Hi

what about the other neighbors' values? Try posting the output of

show ip eigrp neighbors

Those timeouts might be due to a number of reasons...

Report Inappropriate Content · ‎07-06-2012

Hi Francesco,

This is it:

XXXX#sh ip eigrp neighbors

IP-EIGRP neighbors for process 18

H Address Interface Hold Uptime SRTT RTO Q Seq

(sec) (ms) Cnt Num

0 30.30.30.2 Fa0/0 14 03:47:51 137 5000 0 122758

Thanks!

Francesco Pettene · ‎07-06-2012

You might have occasionally (actually not in you output) high SRTT values, which

lead to timeouts and consequently highs RTO values.

You should gather some stats about rtt, jitter and packet loss values: for instance

you could try running an extended ping to 30.30.30.2 with your router-id as the source

of icmp packets

Alessio Andreoli · ‎07-06-2012

pleasepost more info:

show ip eigrp interface

show ip eigrp nei

show interface point_to_Y

and post the RTT as well, the full output. 5000 is not a casual value.

http://www.cisco.com/en/US/docs/ios/12_0/np1/command/reference/1reigrp.html

HTH

Alessio

Alessio Andreoli · ‎07-06-2012

H guys,

read here that can help :)

http://ieoc.com/forums/p/5028/16536.aspx

HTH

Alessio

Francesco Pettene · ‎07-06-2012

Sure... there's a lot of reason why that would do so, high rtts, jitter over wan, maybe even

a unidirectional wan link...

Alessio Andreoli · ‎07-06-2012

You did not get what i meant.

No matters

Alessio

Report Inappropriate Content · ‎07-06-2012

Hi!!

this is the information that you ask:

XXXXX>sh ip eigrp neighbors

IP-EIGRP neighbors for process 1

H Address Interface Hold Uptime SRTT RTO Q Seq

(sec) (ms) Cnt Num

0 192.168.1.1 Fa0 13 05:59:16 1191 5000 0 4

XXXXXX>sh ip eigrp interfaces fa0

IP-EIGRP interfaces for process 1

Xmit Queue Mean Pacing Time Multicast Pending

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

Fa0 1 0/0 1191 0/10 5956 0

XXXXX>sh int fa0

FastEthernet0 is up, line protocol is up

Hardware is PQUICC_FEC, address is 0019.e8c9.d469 (bia 0019.e8c9.d469)

Internet address is 192.168.1.2/24

MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 100Mb/s, 100BaseTX/FX

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:00, output 00:00:00, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 1000 bits/sec, 1 packets/sec

5 minute output rate 1000 bits/sec, 1 packets/sec

150811 packets input, 201215750 bytes

Received 5207 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog

0 input packets with dribble condition detected

153684 packets output, 201503066 bytes, 0 underruns

0 output errors, 0 collisions, 2 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

This is the another point:

XXXXX#show ip eigrp interface fa0

IP-EIGRP interfaces for process 1

Xmit Queue Mean Pacing Time Multicast Pending

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

Fa0 1 0/0 4 0/10 50 0

XXXXXX#show ip eigrp nei

IP-EIGRP neighbors for process 1

H Address Interface Hold Uptime SRTT RTO Q Seq

(sec) (ms) Cnt Num

0 192.168.1.2 Fa0 13 06:03:55 4 200 0 12

XXXXXXX#show interface fa0

FastEthernet0 is up, line protocol is up

Hardware is PQUICC_FEC, address is 0013.c42c.732f (bia 0013.c42c.732f)

Internet address is 192.168.1.1/24

MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 100Mb/s, 100BaseTX/FX

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:00, output 00:00:00, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 0 bits/sec, 1 packets/sec

5 minute output rate 1000 bits/sec, 1 packets/sec

5408 packets input, 494337 bytes

Received 5092 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog

0 input packets with dribble condition detected

7624 packets output, 640891 bytes, 0 underruns

0 output errors, 0 collisions, 2 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

Thanks!!

rizwanr74 · ‎07-06-2012

Hi Kenneth,

neighbors flapping is due to, missed hello-packet from remote-eigrp peer.

what is the bandwidth set on the interface, on one which neighbors is flapping?

Look forward to hear from you.

thanks

Report Inappropriate Content · ‎07-06-2012

Hi

rizwanr74

The interface bandwidth set 100mbps and it is 192.168.1.2 that is constantly flapping....

thanks

Ivan Krimmel · ‎07-06-2012

Hello,

what is actually flapping - interface or EIGRP? can we have a 'sh logg' please?

EIGRP uses multicast for hello transmission, right? hence verifying unicast might not be the way forward. Do you have any issues with multicast? can you ping 224.0.0.10 off that interface?

Alessio Andreoli · ‎07-06-2012

the interface speed should be 100 Mbps ... no 10..

check again

Alessio

Report Inappropriate Content · ‎07-06-2012

Smooth Round Trip Time (SRTT) - the average time in milliseconds between the transmission of a packet to a neighbour and the receipt of an acknowledgement.

Retransmission Timeout (RTO) - if a multicast has failed, then a unicast is sent to that particular router, the RTO is the time in milliseconds that the router waits for an acknowledgement of that unicast.

I talk to with "Y" ISP and they said that problem is that between these two points in the ring of them, is a very long distance, they will change the route of the fiber.

Thank you very much for your help.