Routing Alarms

bgp-nbr-state-change

Description	BGP neighbor connection state changed. This impacts the service, because the BGP session to the neighbor goes down.
Cause	Interface on which the BGP peering session was established went down. BGP peer configuration changed. BGP peer reset.
Action	Ping the BGP neighbor address to check the when the BGP session went down. It is likely because the Controller node went down or there is a data path connectivity issue. If the Controller node is Up and ping is not working, determined the state of the IPsec session to the Controller node and debug data path connectivity.

Related Commands

Syslog:

Aug 30 19:07:59 branch /opt/versa/bin/versa-rtd[8094]: [rtd] [bgpNbrStateChange] [2017-08-30T19:07:59-0700] BGP instance 1: Peer 10.0.192.2 transitioned to Idle state
Aug 30 19:08:09 branch /opt/versa/bin/versa-rtd[8094]: [rtd] [bgpNbrStateChange] [2017-08-30T19:08:09-0700] BGP instance 1: Peer 10.0.192.2 transitioned to Established state

CLI:

admin@branch-cli> show alarms last-n 50 | grep BGP
 rtd        bgpNbrStateChange       2017-08-30T19:03:43-0 BGP instance 2: Peer 10.1.64.1 transitioned to Established state
 rtd        bgpNbrStateChange       2017-08-30T19:03:44-0 BGP instance 2: Peer 10.1.64.2 transitioned to Established state
 rtd        bgpNbrStateChange       2017-08-30T19:03:56-0 BGP instance 1: Peer 10.0.192.1 traexinsitioned to Established state
 rtd        bgpNbrStateChange       2017-08-30T19:07:59-0 BGP instance 1: Peer 10.0.192.2 transitioned to Idle state
 rtd        bgpNbrStateChange       2017-08-30T19:08:09-0 BGP instance 1: Peer 10.0.192.2 transitioned to Established state

monitor-down

Description	A named monitor transitions to the Down state. This impacts the service, because the next hop is not reachable.
Cause	Issues with data path used to reach the monitored next hop. Network link issues. Dropped packets.
Action	Check the data path connectivity.

nexthop-down

Description	An unnamed monitor transitions to Down state. This impacts the service, because the next hop is not reachable.
Cause	Reachability to next hop may be down. Interface may be in down state.
Action	Check the data path connectivity.

Related Commands

Syslog:

Aug 30 12:06:17 branch versa-rfd[1877]: [rfd] [nexthopDown] [2017-08-30T12:06:17-0700] Nexthop 192.168.5.1/Internet-Transport-VR is down.
Aug 30 19:04:15 branch versa-vmod: [rfd] [nexthopDown] [2017-08-30T19:04:15-0700] Provider: Nexthop 192.168.5.1/Internet-Transport-VR is down.

CLI:

admin@branch-cli> show alarms last-n 50 | grep nexthop
rfd        nexthopUp               2017-08-30T19:03:35-0 Provider: Nexthop 192.168.4.1/MPLS-Transport-VR is up.
rfd        nexthopDown             2017-08-30T19:04:15-0 Provider: Nexthop 192.168.5.1/Internet-Transport-VR is down.
monitor-down

Supported Software Information

Releases 20.2 and later support all content described in this article.

Additional Information

Configure VOS Device Alarms