NBRCHANGE - Possible error

[DAvelarNIC]

Hello experts!

I have a question. One of our clients has this in all their core switches and it happens constantly. This probably started about 3 months ago. Is this stating that the interface is going up and down?

Jun  7 2012 07:18:11 PST-ST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.254.254.33 (Vlan254) is down: holding time expired

Jun  7 2012 07:18:13 PST-ST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.254.254.33 (Vlan254) is up: new adjacency

Jun  7 2012 07:18:15 PST-ST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.254.254.33 (Vlan254) is down: Peer Termination received

Jun  7 2012 07:18:15 PST-ST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.254.254.33 (Vlan254) is up: new adjacency Jun  7 2012 07:18:11 PST-ST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.254.254.33 (Vlan254) is down: holding time expired
Jun  7 2012 07:18:13 PST-ST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.254.254.33 (Vlan254) is up: new adjacency
Jun  7 2012 07:18:15 PST-ST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.254.254.33 (Vlan254) is down: Peer Termination received
Jun  7 2012 07:18:15 PST-ST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.254.254.33 (Vlan254) is up: new adjacency

Is there a way to determine what is causing this issue?

Thanks

[vmiller · Accepted solution]

vlan254 link at the ip address has some connectivity issues of some kind. the neighbor relationship keeps getting hammered.

I'd start by getting on the device that hosts that address and poke around from there..

[DAvelarNIC]

Can you explain what the "holding time expired" means?

Thanks for the quick reply!

[lgijssel]

Depending on the age of the network this may be a very old cosmetic bug.

This could be a K-factor mismatch.

The bug is that the message is misleading, it puts you on the wrong track.

EIGRP has 5 elements to calculate the metric: bandwidth, delay, mtu load and reliability.

Normally only two are used but what counts is that they must be configured the same on all routers.

You may get errors like this on older ios versions when the true cause is in fact the K-factor mismatch.

http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/1cfeigrp.html

regards,

Leo

[dslice · Accepted solution]

Holding time expired means the router didn't receive a Hello within the hold time. Hellos are normally sent every 5 seconds on most networks and the Hold time is normally 15 seconds. Unless someone has modified the Hello/Hold time via CLI, the error message you see is due to missing three Hellos. Look for link errors or congestion or some other reason packets aren't being delivered.

Sent from Cisco Technical Support iPad App