Thursday, January 24, 2013

BGP Error Code Cease & subCode @ other configuration changed

One of the most important player of a Service Provider Backbone Network is BGP which should be stable at any cost, but it will make life tough when you see some logs like shown below or something down and BGP is associated with that down state. Same is the case happened with us yesterday, we received a TT for a circuit was down, when we check all the possible aspects, so We came across with this BGP error named CEASE with subCode error other configuration changed shown below in logs.  

Jan 22 2013 09:45:07.700.3+03:00 PE-AggX16-Baha-712-1 %%01BGP/3/STATE_CHG_UPDOWN(l)[743]:The status of the peer 172.31.184.110 changed from ESTABLISHED to IDLE. (InstanceName=V1907:MOI-PRISON, StateChangeReason=Notification Message Received)

Jan 22 2013 09:44:51.50.1+03:00 PE-AggX16-Baha-712-1 %%01BGP/3/STATE_CHG_UPDOWN(l)[744]:The status of the peer 172.31.184.110 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=V1907:MOI-PRISON, StateChangeReason=Up)

Jan 22 2013 09:44:19.690.3+03:00 PE-AggX16-Baha-712-1 %%01BGP/3/STATE_CHG_UPDOWN(l)[745]:The status of the peer 172.31.184.110 changed from ESTABLISHED to IDLE. (InstanceName=V1907:MOI-PRISON, StateChangeReason=Notification Message Received)

Jan 22 2013 09:44:05.40.1+03:00 PE-AggX16-Baha-712-1 %%01BGP/3/STATE_CHG_UPDOWN(l)[747]:The status of the peer 172.31.184.110 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=V1907:MOI-PRISON, StateChangeReason=Up)

Jan 22 2013 09:43:33.620.3+03:00 PE-AggX16-Baha-712-1 %%01BGP/3/STATE_CHG_UPDOWN(l)[748]:The status of the peer 172.31.184.110 changed from ESTABLISHED to IDLE. (InstanceName=V1907:MOI-PRISON, StateChangeReason=Notification Message Received)

Peer: 172.x.x.x
Date/Time     : 2013-01-22 13:22:19+03:00
State         : Down
Error Code    : 6(CEASE)
Error Subcode : 6(Other Configuration Change)
Notification: Receive Notification

There can be multiple Subcode error, I will talk here error CEASE with Subcode other configuration changed, According to RFC 4486 - If a BGP speaker decides to administratively reset the peering with a neighbour due to a configuration change other than the ones described above, then the speaker SHOULD send a NOTIFICATION message with the Error Code Cease and the Error Subcode “Other Configuration Change“.

I hope this will be informative for you :)