Skip to main content

BGP Neighbor down states

BGP Neighbor down states

Troubleshooting for BGP neighbor down. We can check with  #debug ip bgp events command. 

When the neighbor interface shut down we can see the log like that.

*Mar  1 00:57:57.451: BGP: 10.1.12.2 remote close, state CLOSED
*Mar  1 00:57:57.451: BGP: 10.1.12.2 -reset the session
*Mar  1 00:57:57.451: BGPNSF state: 10.1.12.2 went from nsf_not_active to nsf_not_active
*Mar  1 00:57:57.455: BGP: 10.1.12.2 went from Established to Idle
*Mar  1 00:57:57.455: %BGP-5-ADJCHANGE: neighbor 10.1.12.2 Down Peer closed the session

When neighbor advertise again with wrong AS after established.

*Mar  1 01:03:01.827: BGP: 10.1.12.2 remote close, state CLOSEWAIT
*Mar  1 01:03:01.827: BGP: 10.1.12.2 -reset the session
*Mar  1 01:03:01.827: BGPNSF state: 10.1.12.2 went from nsf_not_active to nsf_not_active
*Mar  1 01:03:01.827: BGP: 10.1.12.2 went from Established to Idle
*Mar  1 01:03:01.827: %BGP-5-ADJCHANGE: neighbor 10.1.12.2 Down Peer closed the session

Labels:

Comments

Post a Comment

Popular posts from this blog

Nested Route Reflection Cluster

Figure 1.1 R1 router bgp 65000  bgp cluster-id 10  neighbor 2.2.2.2 remote-as 65000  neighbor 2.2.2.2 update-source Loopback0  neighbor 2.2.2.2 route-reflector-client  neighbor 3.3.3.3 remote-as 65000  neighbor 3.3.3.3 update-source Loopback0  neighbor 3.3.3.3 route-reflector-client R2 router bgp 65000  bgp cluster-id 20  net 22.22.22.0 mask 255.255.255.0  neighbor 1.1.1.1 remote-as 65000  neighbor 1.1.1.1 update-source Loopback0  neighbor 4.4.4.4 remote-as 65000  neighbor 4.4.4.4 update-source Loopback0  neighbor 4.4.4.4 route-reflector-client R3 router bgp 65000  bgp cluster-id 30  net 33.33.33.0 mask 255.255.255.0  neighbor 1.1.1.1 remote-as 65000  neighbor 1.1.1.1 update-source Loopback0  neighbor 5.5.5.5 remote-as 65000  neighbor 5.5.5.5 update-source Loopback0  neighbor 5.5.5.5 route-reflector-client R4 router bgp 65000 ...
Post a Comment
Read more

OSPF Traffic Types

Three types of traffic may be defined in relation to areas: Intra-area traffic consists of packets that are passed between routers within a single area. Inter-area traffic consists of packets that are passed between routers in different areas. External traffic consists of packets that are passed between a router within the OSPF domain and a router within another routing domain. Area ID 0 (or 0.0.0.0) is reserved for the backbone. The backbone is responsible for summarizing the topologies of each area to every other area. For this reason, all inter-area traffic must pass through the backbone; non-backbone areas cannot exchange packets directly. Ref: Routing TCP/IP volume 1
Post a Comment
Read more