BGP/2/PEER_BACKWARDTRANS_NOTIFICATION
Message
BGP/2/PEER_BACKWARDTRANS_NOTIFICATION:The BGP FSM moved from a higher numbered state to a lower numbered state. (BgpPeerRemoteAddr=[PeerIpv4Addr], BgpPeerLastError=[PeerLastError], BgpPeerState=[PeerState], VpnInstance=[VpnInstance])
Parameters
Parameter Name | Parameter Meaning |
---|---|
BgpPeerRemoteAddr |
The address of the BGP peer. NOTE:
This log
is reported to the NMS based on the bgpBackwardTransNotification object
in the public MIB (Bgp4-mib.mib). This MIB object applies to IPv4
peers, not to IPv6 peers. As a result, this log is not reported if
IPv6 peer status changes. In this case, you need to query the bgpBackwardTransition alarm on the device. |
BgpPeerLastError |
The value of the Error Code field in the Notification packet generated when the peer relationship was interrupted last time. |
BgpPeerState |
The status of the BGP peer. |
VpnInstance |
Name of a VPN instance |
Possible Causes
Cause 1: The BGP peer was disconnected due to BGP configurations.
Cause 2: The local device received a Notification message.
Cause 3: The local device received error packets.
Cause 4: The BGP hold timer expired.
Cause 5: The BGP peer was unreachable.
Cause 6: The directly connected BGP interface was disconnected.
Cause 7: The number of BGP routes exceeded the upper threshold.
Procedure
- Cause 1: The BGP peer was disconnected due to BGP configurations.
- Cause 2: The local device received a Notification message.
- Cause 3: The local device received error packets.
- Cause 4: The BGP hold timer expired.
- Cause 5: The BGP peer was unreachable.
- Cause 6: The directly connected BGP interface was disconnected.
- Check whether the shutdown command is run on the directly connected interface.
- Collect the alarm information, log information, and configuration information, and then contact technical support personnel technical support personnel.
- Cause 7: The number of BGP routes exceeded the upper threshold.