No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

The NE80 Gives Alarms on BGP Exception When the Competitor's Device Acts as RR

Publication Date:  2012-07-27 Views:  51 Downloads:  0
Issue Description
The competitor’s (C) device acts as RR and the NE80 as the client of RR. When BGP routes change on the NE80, the NE80 gives the following alarms:
Dec 29 2007 08:12:44 WJ_NE80_A %%01BGP/3/WRONG_NEXTHOPID(l): The next hop carried in the received Update message was one of the interface addresses!
Dec 29 2007 08:12:44 WJ_NE80_A %%01BGP/3/IBGP_ORGINID_ANTI(l): When peer was IBGP, the Originator ID carried in the received Update message was equal to the local routerID!
Dec 29 2007 08:12:44 WJ_NE80_A %%01BGP/3/WRONG_NEXTHOPID(l): The next hop carried in the received Update message was one of the interface addresses!
Dec 29 2007 08:12:44 WJ_NE80_A %%01BGP/3/IBGP_ORGINID_ANTI(l): When peer was IBGP, the Originator ID carried in the received Update message was equal to the local routerID!
Dec 29 2007 08:12:34 WJ_NE80_A %%01BGP/3/WRONG_NEXTHOPID(l): The next hop carried in the received Update message was one of the interface addresses!
Dec 29 2007 08:12:34 WJ_NE80_A %%01BGP/3/IBGP_ORGINID_ANTI(l): When peer was IBGP, the Originator ID carried in the received Update message was equal to the local routerID!
Dec 29 2007 08:12:34 WJ_NE80_A %%01BGP/3/WRONG_NEXTHOPID(l): The next hop carried in the received Update message was one of the interface addresses!
Dec 29 2007 08:12:34 WJ_NE80_A %%01BGP/3/IBGP_ORGINID_ANTI(l): When peer was IBGP, the Originator ID carried in the received Update message was equal to the local routerID! 
 
Alarm Information
Dec 29 2007 08:12:44 WJ_NE80_A %%01BGP/3/WRONG_NEXTHOPID(l): The next hop carried in the received Update message was one of the interface addresses!
Dec 29 2007 08:12:44 WJ_NE80_A %%01BGP/3/IBGP_ORGINID_ANTI(l): When peer was IBGP, the Originator ID carried in the received Update message was equal to the local routerID!
Dec 29 2007 08:12:44 WJ_NE80_A %%01BGP/3/WRONG_NEXTHOPID(l): The next hop carried in the received Update message was one of the interface addresses!
Dec 29 2007 08:12:44 WJ_NE80_A %%01BGP/3/IBGP_ORGINID_ANTI(l): When peer was IBGP, the Originator ID carried in the received Update message was equal to the local routerID!
Dec 29 2007 08:12:34 WJ_NE80_A %%01BGP/3/WRONG_NEXTHOPID(l): The next hop carried in the received Update message was one of the interface addresses!
Dec 29 2007 08:12:34 WJ_NE80_A %%01BGP/3/IBGP_ORGINID_ANTI(l): When peer was IBGP, the Originator ID carried in the received Update message was equal to the local routerID!
Dec 29 2007 08:12:34 WJ_NE80_A %%01BGP/3/WRONG_NEXTHOPID(l): The next hop carried in the received Update message was one of the interface addresses!
Dec 29 2007 08:12:34 WJ_NE80_A %%01BGP/3/IBGP_ORGINID_ANTI(l): When peer was IBGP, the Originator ID carried in the received Update message was equal to the local routerID! 
 
Handling Process
It is normal that the NE80 gives the alarms when the competitor’s (C) router acts as RR. Therefore, it is unnecessary to adopt special measures to clear the alarms. 
Root Cause
1. The engineer first checked whether router-id was configured repeatedly.
2. In the course of debugging, the engineer found that the NE80 received the same update message immediately after sending it when its BGP routes changed.
3. Through further check, the engineer found that the problem was caused by the competitor’s (C) router acting as RR. That is, when the competitor’s router acted as RR, it reflected the update message to all its clients. Thus, the NE80 gave the preceding alarms when receiving the update message that it just sent. 
 
Suggestions
Null

END