MSTP_1.3.6.1.2.1.17.0.2 topologyChange

Trap Buffer Description

Bridge topology changed.

Specify that the topology of STP has been changed

Trap Attributes

Trap Attribute	Description
Alarm or Event	Event
Trap Severity	Alert
Mnemonic Code	TOPOLOGY_CHANGE
Trap OID	1.3.6.1.2.1.17.0.2
MIB	BRIDGE-MIB
Alarm ID	This is an event trap and does not involve alarm ID.
Alarm Name	This is an event trap and does not involve alarm name.
Alarm Type	This is an event trap and does not involve alarm type.
Raise or Clear	This is an event trap and does not involve alarm generation or clearance.
Match trap	-

Trap Buffer Parameters

None

VB Parameters

None

Impact on the System

The topology changes, and traffic may be lost.

Possible Causes

Cause 1: The network topology changed because a new link was added into the network topology. Cause 2: The network topology changed because interfaces went Up or Down. Cause 3: A fault occurred on the network.

Procedure

Cause 1: The network topology changed because a new link was added into the network topology.

1. Check whether the added physical link is necessary.

If the added physical link is necessary, go to Step 2.
If the added physical link is unnecessary, go to Step 3.

2. Run the display stp command to check whether the interfaces are consistent with the STP calculation results.

If the interfaces are consistent with the STP calculation results, the alarm will be cleared.
If the interfaces are inconsistent with the STP calculation results, go to Step 3.

3. Collect alarm information and configuration information, and then contact technical support personnel.

Cause 2: The network topology changed because interfaces went Up or Down.

1. Run the undo shutdown command in the interface view to check whether the alarm is cleared. If the alarm persists, go to Step 2.

2. Collect alarm information and configuration information, and then contact technical support personnel.

Cause 3: A fault occurred on the network.

1. Rectify the fault in the original network topology. If the fault persists, go to Step 2.

2. Collect alarm information and configuration information, and then contact technical support personnel.