EIGRP goodbyesPosted by stretch in Networking on Thursday, 14 Aug 2008 at 9:31 a.m. GMTEIGRP includes a special type of hello packet, known as a "goodbye." Goodbyes are transmitted by an EIGRP router to its peer whenever a neighbor adjacency fails but the interface to reach that neighbor is still up. This could be the result of administrative reconfiguration, but sometimes the physical link between two EIGRP neighbors will fail without the routers realizing it (the interface status remains up/up). In this case, the router will continue to transmit hellos (among other data) to the neighbor without receiving any hellos in return until the hold timer expires and the adjacency is torn down. When this happens, a router will transmit a goodbye message as an explicit notification that it is tearing down the adjacency. You're likely to wonder what the point of this is if the link to the neighbor has failed. However, goodbyes provide an excellent troubleshooting tool when dealing with links that have only partially failed and have become unidirectional. This is a common scenario with fiber connections, and as I have come to find, with satellite links. Often one satellite station will be receiving from another, but for some reason (such as poor weather) will not be transmitting at a high enough power for its signal to be received by the distant station. When EIGRP is run across such a link, the distant station will tear down the adjacency and transmit a goodbye packet, giving the operator a clear indication of the direction in which the link is still functional.
The goodbye packet itself is actually a hello packet with all its K values set to 255. An example can be seen in packet #9 of this EIGRP traffic capture. |
Navigation
Armory
Online Toolbox
|
A Cisco router that runs a software release that does not support the goodbye message will misinterpret the message as a K-value mismatch and display the following message:
The goodbye message is supported in Cisco IOS Release 12.3(2), 12.3(3)B, and 12.3(2)T and later releases.
I found this during my BSCI studies :)
So, when running a fiber ring w/ Spanning Tree blocking on one of the uplinks (making one of the nodes unidirectional to one of it's neighbors), how do you stabilize the EIGRP process? One node sends goodbyes to it's neighbors, and then the the adjacency immediate syncs back up.