Contents

MSDP-MIB· 1

About this MIB· 1

MIB file name· 1

Notifications· 1

msdpEstablished· 1

msdpBackwardTransition· 2

 

 

MSDP-MIB

About this MIB

Use the MIB to query state query and record transmitted messages for communication by using MSDP among multicast domains on network devices.

Only notifications are supported.

MIB file name

rcf4624-msdp.mib

Notifications

msdpEstablished

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.3.92.1.1.0.1	An MSDP peer relationship was established.	Informational	Critical	N/A (N/A)	ON

 

Notification triggers

This notification is generated when an MSDP peer relationship is established.

System impact

Source active (SA) messages can be exchanged between MSDP peers.

Status control

ON

CLI: Use the snmp-agent trap enable msdp established command.

OFF

CLI: Use the undo snmp-agent trap enable msdp established command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.3.92.1.1.5.1.15 (msdpPeerFsmEstablishedTransitions)	Number of times the MSDP FSM entered the ESTABLISHED  state.	msdpPeerRemoteAddress	Counter32	As per the MIB.

 

Recommended action

No action is required.

msdpBackwardTransition

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.3.92.1.1.0.2	The MSDP FSM transitioned from the established state to another state.	Fault	Critical	1.3.6.1.3.92.1.1.0.1 (msdpEstablished)	ON

 

Notification triggers

This notification is generated when any of the following events occurs:

The forwarding path between MSDP peers fails.

The MSDP peer on the local or remote device is deleted.

The TCP connection between MSDP peers fails is disconnected.

System impact

Source active (SA) messages cannot be exchanged between MSDP peers.

Status control

ON

CLI: Use the snmp-agent trap enable msdp backward-transition command.

OFF

CLI: Use the undo snmp-agent trap enable msdp backward-transition command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.3.92.1.1.5.1.15 (msdpPeerFsmEstablishedTransitions)	MSDP TCP connection state.	msdpPeerRemoteAddress	INTEGER	inactive(1),, listen(2),, connecting(3),, established(4),, disabled(5)

 

Recommended action

1.Use the display this command in MSDP view on both the local and remote devices to check whether MSDP peers are configured.

  - If yes, proceed to step 2.

  - If no, use the peer command to configure an MSDP peer.

2.Use the display this command in MSDP view to check whether MSDP authentication settings are the same on the local and remote devices.

  - If yes, proceed to step 3.

  - If no, use the peer password command to configure the same MSDP authentication settings or cancel the MSDP authentication settings.

3.Use the display this command in MSDP view on the local and remote devices to check whether the connection interfaces in the Connect interface field are correct.

  - If yes, proceed to step 4.

  - If no, use the peer command to configure a connection interface.

4.Use the ping command to test the connectivity between MSDP peers.

  - If the ping operation succeeds, proceed to step 6.

  - If the ping operation fails, proceed to step 5.

5.Use the display ip routing-table command to check whether the unicast route to the remote peer is normal.

  - If the unicast route to the peer is normal, proceed to step 6.

  - If the unicast route to the peer is abnormal, make the unicast route normal.

6.Use the display msdp peer-status command to check the state of the MSDP peer.

  - If the state of the MSDP peer is Up, proceed to step 7.

  - If the state of the MSDP peer is Shutdown, execute the undo shutdown command in MSDP view.

7.Check whether the reset msdp peer command is executed on the remote device.

  - If yes, wait for the peer relationship to be re-established.

  - If no, proceed to step 8.

8.Collect alarm information and configuration information, and contact H3C Support.