BGP
bgpBackwardTransNotification
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2039 |
Event name |
bgpBackwardTransNotification |
SNMP notification prefix and OID |
BGP4-MIB.bgpNotification.2 |
Default severity | warning |
Source stream | main |
Message format string |
(ASN $tBgpASN4Byte$) $bgp_peer_name$: moved from higher state $old_state_str$ to lower state $new_state_str$ due to event $event_str$ |
Cause |
The bgpBackwardTransNotification event is generated when the BGP FSM moves from a higher numbered state to a lower numbered state. This Notification replaces the bgpBackwardsTransition Notification. |
Effect | N/A |
Recovery | N/A |
bgpCfgViol
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2017 |
Event name |
bgpCfgViol |
SNMP notification prefix and OID | N/A |
Default severity | warning |
Source stream |
main |
Message format string | $subject$: BGP - $field$ configuration ignored - $reason$ |
Cause |
BGP configuration was invalid. |
Effect | The configuration that led to the violation will be totally ignored. |
Recovery | N/A |
bgpConnMgrTerminated
Property name | Value |
---|---|
Application name | BGP |
Event ID |
2013 |
Event name | bgpConnMgrTerminated |
SNMP notification prefix and OID | N/A |
Default severity |
warning |
Source stream | main |
Message format string | $subject$: BGP connection manager for address family $addr_family_str$ has terminated |
Cause | BGP is being shut down or deleted. |
Effect | No inbound BGP connections will be accepted. |
Recovery | BGP must be re-enabled. |
bgpConnNoKA
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2008 |
Event name |
bgpConnNoKA |
SNMP notification prefix and OID | N/A |
Default severity | warning |
Source stream |
main |
Message format string | (ASN $tBgpASN4Byte$) $bgp_peer_name$: closing inbound connection because the BGP peer did not receive "keepalive" |
Cause | A BGP KEEPALIVE message was not received within the hold-time limit. |
Effect | Inbound connection failed to establish. |
Recovery | Reset and try again. |
bgpConnNoOpenRcvd
Property name | Value |
---|---|
Application name | BGP |
Event ID |
2009 |
Event name | bgpConnNoOpenRcvd |
SNMP notification prefix and OID | N/A |
Default severity |
warning |
Source stream | main |
Message format string | (ASN $tBgpASN4Byte$) $bgp_peer_name$: closing inbound connection because the BGP peer did not receive "open" |
Cause | A BGP OPEN message was not received within the hold-time limit. |
Effect | Inbound connection failed to establish. |
Recovery | Reset and try again. |
bgpEstablishedNotification
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2038 |
Event name |
bgpEstablishedNotification |
SNMP notification prefix and OID |
BGP4-MIB.bgpNotification.1 |
Default severity | minor |
Source stream | main |
Message format string |
(ASN $tBgpASN4Byte$) $bgp_peer_name$: moved into established state |
Cause | The bgpEstablishedNotification event is generated when the BGP FSM enters the established state. This Notification replaces the bgpEstablished Notification. |
Effect | The BGP instance is now running. |
Recovery |
N/A |
bgpInterfaceDown
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2007 |
Event name |
bgpInterfaceDown |
SNMP notification prefix and OID | N/A |
Default severity | warning |
Source stream |
main |
Message format string | (ASN $tBgpASN4Byte$) $bgp_peer_name$: being disabled because the interface is operationally disabled |
Cause | The IP interface is down. |
Effect |
All EBGP peers directly attached to the interface for the peering go down. |
Recovery |
Bring the interface up. |
bgpNoMemoryPeer
Property name | Value |
---|---|
Application name | BGP |
Event ID |
2015 |
Event name | bgpNoMemoryPeer |
SNMP notification prefix and OID | N/A |
Default severity |
critical |
Source stream | main |
Message format string | (ASN $tBgpASN4Byte$) $bgp_peer_name$: out of memory - disabled the peer |
Cause | The router has run out of memory. |
Effect |
The peering that first hit the out of memory condition on a memory allocation request is going to go down and it will be marked DISABLED. |
Recovery | Upgrade the box's memory or shut down the memory hogging peering sessions. |
bgpPeerNotFound
Property name | Value |
---|---|
Application name | BGP |
Event ID |
2012 |
Event name | bgpPeerNotFound |
SNMP notification prefix and OID | N/A |
Default severity |
warning |
Source stream | main |
Message format string | (ASN $tBgpASN4Byte$) $subject$: Closing connection: $peer_ip_str$ not enabled or not in configuration |
Cause |
BGP peering session won't come up. |
Effect | Inbound connection failed to establish as the peer that the remote end is trying to connect to does not exist in the current configuration. |
Recovery | Change the BGP configuration to create a peering session with the remote peer. |
bgpRejectConnBadLocAddr
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2010 |
Event name |
bgpRejectConnBadLocAddr |
SNMP notification prefix and OID |
N/A |
Default severity | warning |
Source stream | main |
Message format string |
(ASN $tBgpASN4Byte$) $bgp_peer_name$: inbound connection rejected because the BGP peer received connection attempt on $rcv_addr_str$ but it only accepts connection on $lcl_addr_str$ |
Cause |
Inbound BGP connection not being attempted through the correct IP address. |
Effect | Inbound connection will be rejected - failed to establish the peering session. |
Recovery | The remote peer should be trying to open the peering connection to the appropriate IP address; for example, the one mentioned in the local-address of the local peer. |
bgpRemoteEndClosedConn
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2011 |
Event name |
bgpRemoteEndClosedConn |
SNMP notification prefix and OID |
N/A |
Default severity | warning |
Source stream | main |
Message format string |
(ASN $tBgpASN4Byte$) $bgp_peer_name$: remote end closed connection |
Cause | The remote end of the BGP connection closed the TCP connection. |
Effect | The BGP peering session is closed. All routes learned from that peer were rejected. |
Recovery | Reset and try to re-establish the peering. |
bgpTerminated
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2014 |
Event name |
bgpTerminated |
SNMP notification prefix and OID | N/A |
Default severity | warning |
Source stream |
main |
Message format string | $subject$: BGP has terminated |
Cause | BGP is being shut down or deleted. |
Effect |
The BGP protocol will terminate. |
Recovery | BGP must be re-enabled. |
bgpVariableRangeViolation
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2016 |
Event name |
bgpVariableRangeViolation |
SNMP notification prefix and OID |
N/A |
Default severity | warning |
Source stream | main |
Message format string |
$subject$: trying to set $varname$ to $tryval$ - valid range is [$minval$- $maxval$] - setting to $finalval$ |
Cause | The event is caused by setting some variable through a MIB that is outside the valid range accepted by the application. The system gets into this scenario when the agent is not able to catch the variable range violation because from the perspective of the MIB variable that is being set it is an acceptable value. e.g. min-route-advertisement has a range in the Nokia MIB that is more strict than the standard BGP4 MIB. Although the agent will allow larger range values for this MIB variable the BGP implementation will reject it as it is restricted by the Nokia BGP MIB. |
Effect | The set value is not accepted but the closest valid value to the set value is accepted. |
Recovery | N/A |
receiveNotification
Property name | Value |
---|---|
Application name | BGP |
Event ID |
2006 |
Event name | receiveNotification |
SNMP notification prefix and OID | N/A |
Default severity |
warning |
Source stream | main |
Message format string | (ASN $tBgpASN4Byte$) $bgp_peer_name$: received notification: code $code_str$ subcode $subcode_str$ |
Cause | Any error that occurred between BGP peers that was first recognized by the remote BGP instance. e.g. 1) An error occurred in the state transitions of a peering session. 2) An error occurred during the exchange of routing information between BGP peers. 3) The two BGP peers mismatch on the capability that they can support. |
Effect | The system closes the existing socket connection and tries to establish the peering session again. |
Recovery | N/A |
sendNotification
Property name | Value |
---|---|
Application name | BGP |
Event ID |
2005 |
Event name | sendNotification |
SNMP notification prefix and OID | N/A |
Default severity |
warning |
Source stream | main |
Message format string | (ASN $tBgpASN4Byte$) $bgp_peer_name$: sending notification: code $code_str$ subcode $subcode_str$ |
Cause | Any error that occurred between BGP peers that was first recognized by the local BGP instance. e.g. 1) An error occurred in the state transitions of a peering session. 2) An error occurred during the exchange of routing information between BGP peers. 3) The two BGP peers mismatch on the capability that they can support. |
Effect | The system brings down the peering and attempts to establish a new peering session. |
Recovery | N/A |
tBgp4PathAttrDiscarded
Property name | Value |
---|---|
Application name | BGP |
Event ID |
2040 |
Event name | tBgp4PathAttrDiscarded |
SNMP notification prefix and OID | TIMETRA-BGP-MIB.tBgpNotifications.24 |
Default severity | warning |
Source stream |
main |
Message format string | (ASN $tBgpASN4Byte$) $vRtrID$: Discarded path attribute received from BGP Peer $tBgpPeerNgAddr$ with attribute type [$tBgp4PathAttrType$] and length [ $tBgp4PathAttrLength$]. Hex dump: $tBgp4PathAttribute$ |
Cause |
The tBgp4PathAttrDiscarded notification is generated when a path attribute tBgp4PathAttribute is discarded from an UPDATE message. A path attribute may be discarded because it is malformed. |
Effect | A log entry is generated for each path attribute discarded from an UPDATE message. The UPDATE message continues to be processed. |
Recovery | There is no recovery required for this notification. |
tBgp4PathAttrInvalid
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2028 |
Event name |
tBgp4PathAttrInvalid |
SNMP notification prefix and OID |
TIMETRA-BGP-MIB.tBgpNotifications.16 |
Default severity | warning |
Source stream | main |
Message format string |
(ASN $tBgpASN4Byte$) $vRtrID$: BGP Peer $tBgpPeerNgAddr$: Invalid path attribute received with attribute type [ $tBgp4PathAttrType$] and length [$tBgp4PathAttrLength$]. Hex dump: $tBgp4PathAttribute$ |
Cause | The tBgp4PathAttrInvalid notification is generated when an error with a path attribute tBgp4PathAttribute is detected. |
Effect | A log entry is generated for each withdrawn route. Further effect depends on fault-tolerance and graceful-restart settings. |
Recovery | There is no recovery required for this notification. |
tBgp4RouteInvalid
Property name | Value |
---|---|
Application name | BGP |
Event ID |
2027 |
Event name | tBgp4RouteInvalid |
SNMP notification prefix and OID | TIMETRA-BGP-MIB.tBgpNotifications.15 |
Default severity | warning |
Source stream |
main |
Message format string | (ASN $tBgpASN4Byte$) $vRtrID$: BGP Peer: $tBgpPeerNgAddr$, Route invalid Reason - $tBgpRouteInvalidReason$ NLRI - $tBgpRouteNLRI$ |
Cause | The tBgp4RouteInvalid notification is generated when the received route is invalid for a specific reason and the route cannot be used or advertised further. |
Effect | The BGP peer ignores the route and flags the path attribute and the route so that the peer/tribe that was attempting to advertise the associated route can skip this route. The BGP peering is not torn down in this case. |
Recovery | There is no recovery required for this notification. |
tBgp4UpdateInvalid
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2030 |
Event name |
tBgp4UpdateInvalid |
SNMP notification prefix and OID |
TIMETRA-BGP-MIB.tBgpNotifications.18 |
Default severity | warning |
Source stream | main |
Message format string |
(ASN $tBgpASN4Byte$) $vRtrID$: BGP Peer: $tBgpPeerNgAddr$. Hex dump: $tBgp4UpdateMessage$ |
Cause | The tBgp4UpdateInvalid notification is generated when an UPDATE message has a critical length error or an error not specific to any path attribute. |
Effect | A log entry is generated for each withdrawn route. Further effect depends on fault-tolerance and graceful-restart settings. |
Recovery | There is no recovery required for this notification. |
tBgp4WithdrawnRtFromUpdateError
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2029 |
Event name |
tBgp4WithdrawnRtFromUpdateError |
SNMP notification prefix and OID |
TIMETRA-BGP-MIB.tBgpNotifications.17 |
Default severity |
warning |
Source stream | main |
Message format string | (ASN $tBgpASN4Byte$) $vRtrID$: BGP Peer: $tBgpPeerNgAddr$, Route: $tBgp4WithdrawnRoutePrefix$ withdrawn because of error in BGP update message. |
Cause | The tBgp4WithdrawnRtFromUpdateError notification is generated when NLRI is withdrawn because of error in BGP update message. |
Effect | This notification has no direct effect. The withdrawn routes are logged to aid debugging and tracking back the root cause of the problem. |
Recovery | There is no recovery required for this notification. |
tBgpFibResourceFailPeer
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2032 |
Event name |
tBgpFibResourceFailPeer |
SNMP notification prefix and OID |
N/A |
Default severity | critical |
Source stream | main |
Message format string |
$bgp_peer_name$: FIB resource fail - disabled the peer |
Cause |
The router has run out of memory. It is triggered when BGP fails to add a route into RTM. |
Effect | The system disables the peer. |
Recovery |
There is no automatic recovery. The user has to manually enable the peer again. |
tBgpFlowspecUnsupportdComAction
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2022 |
Event name |
tBgpFlowspecUnsupportdComAction |
SNMP notification prefix and OID |
TIMETRA-BGP-MIB.tBgpNotifications.10 |
Default severity |
warning |
Source stream | main |
Message format string | (ASN $tBgpASN4Byte$) $bgp_peer_name$: Flowspec NLRI - unsupported community action : [ $tBgpFlowspecExtCommunityAction$], action value : [$tBgpFlowspecExtCommActionValue$] received. |
Cause | The tBgpFlowspecUnsupportdComAction notification is generated when the best route for a flow specification NLRI (Network Layer Reachability Information) is received from a remote BGP peer with an extended community action that is unsupported. |
Effect | The BGP peer does not create an IP filter entry for the received flow route even if the NLRI (Network Layer Reachability Information) has valid extended community actions. |
Recovery | There is no recovery required for this notification. |
tBgpGeneral
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2031 |
Event name |
tBgpGeneral |
SNMP notification prefix and OID | N/A |
Default severity | warning |
Source stream |
main |
Message format string | $subject$: $title$ $message$ |
Cause | The general event is generated when certain error conditions are reported by the BGP application. |
Effect | Each condition has its own effect. |
Recovery |
The recovery depends on the condition reported. |
tBgpInstanceDynamicPeerLmtReachd
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2036 |
Event name |
tBgpInstanceDynamicPeerLmtReachd |
SNMP notification prefix and OID |
TIMETRA-BGP-MIB.tBgpNotifications.22 |
Default severity |
minor |
Source stream | main |
Message format string |
$bgp_peer_name$: Closing connection: reached dynamic peer limit ($tBgpInstanceDynamicPeerLimit$) for BGP instance $tBgpInstanceIndex$ |
Cause | A tBgpInstanceDynamicPeerLmtReachd notification is generated when the dynamic peer limit for this BGP instance is reached. |
Effect | Whenever an incoming connection for a new dynamic session would cause dynamic peer limit for this BGP instance to be exceeded, the connection attempt is rejected. |
Recovery | Increase the dynamic peer limit for this BGP instance. |
tBgpInstConvStateTransition
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2042 |
Event name |
tBgpInstConvStateTransition |
SNMP notification prefix and OID |
TIMETRA-BGP-MIB.tBgpNotifications.25 |
Default severity |
minor |
Source stream | main |
Message format string |
Convergence state for family $tBgpConvergenceFamily$ transitioned from $tBgpOldConvergenceState$ to $tBgpConvergenceState$ |
Cause | The tBgpInstConvStateTransition notification is generated when the convergence state transitions. |
Effect | A log entry is generated. |
Recovery |
There is no recovery required for this notification. |
tBgpMaxNgPfxLmt
Property name | Value |
---|---|
Application name | BGP |
Event ID |
2034 |
Event name | tBgpMaxNgPfxLmt |
SNMP notification prefix and OID | TIMETRA-BGP-MIB.tBgpNotifications.20 |
Default severity | minor |
Source stream |
main |
Message format string | (ASN $tBgpASN4Byte$) $bgp_peer_name$: number of routes learned has exceeded configured maximum ($tBgpPeerNgPfxLmtMaxPrefix$) for $tBgpPeerNgPfxLmtFamily$ family |
Cause | A tBgpMaxNgPfxLmt notification is generated when the number of routes learned from the peer has exceeded the configured maximum. |
Effect | No direct effect but if the peer continues to advertise more routes then the number of routes may exceed the configured maximum (tBgpPeerNgPfxLmtMaxPrefix). In that case the peer would just be disabled. |
Recovery | Increase the max-prefix for this peer. |
tBgpMaxNgPfxLmtThresholdReached
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2035 |
Event name |
tBgpMaxNgPfxLmtThresholdReached |
SNMP notification prefix and OID |
TIMETRA-BGP-MIB.tBgpNotifications.21 |
Default severity |
minor |
Source stream | main |
Message format string |
(ASN $tBgpASN4Byte$) $bgp_peer_name$: number of routes learned has exceeded $tBgpPeerNgPfxLmtThreshold$ percentage of the configured maximum ( $tBgpPeerNgPfxLmtMaxPrefix$) for $tBgpPeerNgPfxLmtFamily$ family |
Cause |
A tBgpMaxNgPfxLmtThresholdReached notification is generated when the number of routes learned from the peer has exceeded tBgpPeerNgPfxLmtThreshold percent of the configured maximum (tBgpPeerNgPfxLmtMaxPrefix). |
Effect | No direct effect but if the peer continues to advertise more routes then the number of routes may exceed the configured maximum (tBgpPeerNgPfxLmtMaxPrefix). In that case the peer would just be disabled. |
Recovery | Increase the max-prefix for this peer. |
tBgpNgBackwardTransition
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2020 |
Event name |
tBgpNgBackwardTransition |
SNMP notification prefix and OID |
TIMETRA-BGP-MIB.tBgpNotifications.8 |
Default severity |
warning |
Source stream | main |
Message format string | (ASN $tBgpASN4Byte$) $bgp_peer_name$: moved from higher state $old_state_str$ to lower state $new_state_str$ due to event $event_str$ |
Cause | The tBgpNgBackwardTransition notification is generated when the BGP FSM moves from a higher numbered state to a lower numbered state. |
Effect | N/A |
Recovery | N/A |
tBgpNgEstablished
Property name | Value |
---|---|
Application name | BGP |
Event ID |
2019 |
Event name | tBgpNgEstablished |
SNMP notification prefix and OID | TIMETRA-BGP-MIB.tBgpNotifications.7 |
Default severity | minor |
Source stream |
main |
Message format string | (ASN $tBgpASN4Byte$) $bgp_peer_name$: moved into established state |
Cause | The tBgpNgEstablished notification is generated when the BGP FSM enters the ESTABLISHED state. |
Effect | The BGP instance is now running. |
Recovery |
N/A |
tBgpPeerGRStatusChange
Property name | Value |
---|---|
Application name | BGP |
Event ID |
2018 |
Event name | tBgpPeerGRStatusChange |
SNMP notification prefix and OID | TIMETRA-BGP-MIB.tBgpNotifications.6 |
Default severity | warning |
Source stream |
main |
Message format string | (ASN $tBgpASN4Byte$) $bgp_peer_name$: graceful restart status changed to $tBgpPeerNgOperGRStatus$ |
Cause | The BGP peer is either restarting or just changed the graceful restart status to 'helping'/'not helping'/'restart complete'. |
Effect | N/A |
Recovery | N/A |
tBgpPeerNgGRStatusChange
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2043 |
Event name |
tBgpPeerNgGRStatusChange |
SNMP notification prefix and OID |
TIMETRA-BGP-MIB.tBgpNotifications.6 |
Default severity |
minor |
Source stream | main |
Message format string |
(ASN $tBgpASN4Byte$) $bgp_peer_name$: graceful restart status changed to $tBgpPeerNgOperGRStatus$ |
Cause | The BGP peer is either restarting or just changed the graceful restart status to 'helping'/'not helping'/'restart complete'. |
Effect | N/A |
Recovery | N/A |
tBgpPeerNgHoldTimeInconsistent
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2021 |
Event name |
tBgpPeerNgHoldTimeInconsistent |
SNMP notification prefix and OID |
TIMETRA-BGP-MIB.tBgpNotifications.9 |
Default severity |
warning |
Source stream | main |
Message format string | (ASN $tBgpASN4Byte$) $bgp_peer_name$: attempted to negotiate a hold timer lower than the configured minimum value of $tBgpPeerNgMinHoldTime$ |
Cause | The BGP peer tried to establish a peering with a hold time less than the configured minimum hold time value. |
Effect | The BGP peering is rejected. |
Recovery |
Establish peering with a hold time equal to or greater than the minimum hold time configured. |
tBgpPGDynamicPeerLmtReached
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2037 |
Event name |
tBgpPGDynamicPeerLmtReached |
SNMP notification prefix and OID |
TIMETRA-BGP-MIB.tBgpNotifications.23 |
Default severity |
minor |
Source stream | main |
Message format string |
$bgp_peer_name$: Closing connection: reached dynamic peer limit ($tBgpPGDynamicPeerLimit$) for BGP group $tBgpPeerGroupName$ |
Cause | A tBgpPGDynamicPeerLmtReached notification is generated when the dynamic peer limit for this group is reached. |
Effect | Whenever an incoming connection for a new dynamic session would cause dynamic peer limit for this group to be exceeded, the connection attempt is rejected. |
Recovery | Increase the dynamic peer limit for this group. |
tBgpPGDynNbrIfMaxSessLmtReachd
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2044 |
Event name |
tBgpPGDynNbrIfMaxSessLmtReachd |
SNMP notification prefix and OID |
TIMETRA-BGP-MIB.tBgpNotifications.26 |
Default severity |
minor |
Source stream | main |
Message format string |
$bgp_peer_name$: Closing connection: reached max sessions limit ($tBgpPGDynNbrIfMaxSessions$) for interface $tBgpPGDynNbrInterfaceIndex$ |
Cause | The tBgpPGDynNbrIfMaxSessLmtReachd notification is generated when the dynamic session limit for this interface is reached. |
Effect | Whenever an incoming connection for a new dynamic session would cause dynamic session limit for this interface to be exceeded, the connection attempt is rejected. |
Recovery | Increase the dynamic peer limit for this interface. |
tBgpReceivedInvalidNlri
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2033 |
Event name |
tBgpReceivedInvalidNlri |
SNMP notification prefix and OID |
TIMETRA-BGP-MIB.tBgpNotifications.19 |
Default severity | warning |
Source stream | main |
Message format string |
For the bad_network error type $tBgp4BadErrorMessageType$ the message received is $tBgp4BadErrorMessage$. |
Cause | The tBgpReceivedInvalidNlri notification is generated when there is a parsing error in BGP routes that is not related to attribute errors. |
Effect | BGP will send a notification message to the peer and bring down the peering. |
Recovery | Peering will be re-established with the offending peer. |
tmnxBmpSessionStatusChange
Property name | Value |
---|---|
Application name |
BGP |
Event ID | 2041 |
Event name |
tmnxBmpSessionStatusChange |
SNMP notification prefix and OID |
TIMETRA-BMP-MIB.tmnxBmpNotifications.1 |
Default severity |
minor |
Source stream | main |
Message format string |
VR $tmnxBmpSessionChangeVRtrID$: Station $tmnxBmpSessionChangeStationName$ moved from state $tmnxBmpSessionChangeOldState$ to state $tmnxBmpSessionChangeNewState$ due to reason: $tmnxBmpSessionChangeReason$ |
Cause | The tmnxBmpSessionStatusChange notification is generated when a BMP session has changed its status. |
Effect | This notification has no direct effect. The old and new connection states and the change reason are logged to aid debugging and tracking back the root cause of the problem. |
Recovery | There is no recovery required for this notification. |