MSDP_1.3.6.1.3.92.1.1.0.2 msdpBackwardTransition

Description

MSDP/2/BACKWARD:OID [oid] MSDP peer exit the established state. (RemoteAddr=[ipaddr], PeerState=[integer], InstanceName=[string], ExitReason=[integer])

The MSDP peer connection was closed.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.3.92.1.1.0.2	Major	communicationsAlarm(2)

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
RemoteAddr	Indicates the peer address.
PeerState	Indicates the current peer status. 1: inactive: The peer is inactive. 2: listen: The peer is in the listening state. 3: connecting: The peer is establishing a relationship with the local device. 4: established: The peer has established a relationship with the local device. 5: disabled: The peer is disabled. NOTE: The device supports only the "disabled" state.
InstanceName	Indicates the instance name.
ExitReason	Indicates the cause for MSDP peers to exit from the Established state. 1: The holdtime of the peer status expires. 3: Errors occur in the socket. 4: MSDP messages with incorrect TLVs are received. 5: MSDP Notification messages are received. 6: A user manually changes the MSDP peer relationship status.

Impact on the System

The MSDP connection is closed, which has impact on multicast services.

Possible Causes

This trap is generated when the status of the MSDP peer relationship changed from Established to another state.

1. The link was faulty.

2. The peer switch was faulty.

Procedure

In the MSDP view, run the display this command. If no MSDP configuration is displayed, you need to first run the multicast routing-enable command in the system view. Then, enter the MSDP view and run the peer peer-address connect-interface interface-type interface-number command to establish an MSDP peer relationship and run the pim sm command or the pim dm command on the interfaces connected with the MSDP peers. If MSDP configurations are displayed, run the switch command to check whether an MSDP peer relationship is established between two ends.
- If so, go to Step 3.
- If not, go to Step 2.
Run the peer peer-address connect-interface interface-type interface-number command to configure the MSDP peer on the local switch and peer switch. Run the display msdp brief command on both ends of the MSDP peer to check whether the neighbor status is Up.
- If so, go to Step 6.
- If not, go to Step 3.
Run the display ip routing-table ip-address command to check whether the route to the peer switch exists.
- If so, go to Step 5.
- If not, go to Step 4.
Run the display ip routing-table ip-address command to view unicast routing information on the peer. On the remote end, enter the interface view of the peer and run the display this command to view interface configurations. After the route is normal, run the display msdp brief command to check whether the neighbor status is Up.
- If so, go to Step 6.
- If not, go to Step 5.
Collect alarm information and configuration information, and then contact technical support personnel.
End.

Related Information

MSDP_1.3.6.1.3.92.1.1.0.1 msdpEstablished