No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

E9000 Server V100R001 HMM Alarm Handling 19

This document describes E9000 server alarms in terms of the meaning, impact on the system, possible causes, and solutions.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
MSTP

MSTP

MSTP_1.3.6.1.2.1.17.0.1 newRoot

Description

This bridge changed to be the root bridge.

After the network converged, the local bridge was elected as the new root bridge in the topology.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Critical

Mnemonic Code

newRoot

Trap OID

1.3.6.1.2.1.17.0.1

Alarm ID

This is an event trap and does not involve alarm ID.

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

This is an event trap and does not involve the match trap.

Trap Buffer

NA

VB

VB OID

VB Name

VB Index

None

None

None

Impact on the System

The topology changes, and traffic may be lost.

Possible Causes

Cause 1: The local bridge was added into a new network topology.

Cause 2: The priority of the local bridge was increased.

Cause 3: The root bridge in the original topology was faulty.

Cause 4: The priority of the root bridge in the original topology was reduced.

Procedure
  • Cause 1: The local bridge was added into a new network topology.
    1. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number ] [ brief ] command to check whether the priority of the local bridge is the lowest on the network.
      • If the priority of the local bridge is the lowest on the network, go to Step 2.
      • If the priority of the local bridge is not the lowest on the network, go to Step 3.
    2. Check whether the local bridge is specified as the root bridge in the Layer 2 network topology.
      • If the local bridge is specified as the root bridge, no action is required.
      • If the local bridge is not specified as the root bridge, go to Step 3.
    3. Run the stp [ instance instance-id ] priority priority command to reset the priority of the local bridge as required. Alternatively, run the undo stp [ instance instance-id ] priority command to restore the default priority of the local bridge.
  • Cause 2: The priority of the local bridge was increased.
    1. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number ] [ brief ] command to check whether the priority of the local bridge is the lowest on the network.
      • If the priority of the local bridge is the lowest on the network, go to Step 2.
      • If the priority of the local bridge is not the lowest on the network, go to Step 3.
    2. Check whether the local bridge is specified as the root bridge in the Layer 2 network topology.
      • If the local bridge is specified as the root bridge, no action is required.
      • If the local bridge is not specified as the root bridge, go to Step 3.
    3. Run the stp [ instance instance-id ] priority priority command in the system view to reset the priority of the local bridge as required. Alternatively, run the undo stp [ instance instance-id ] priority command to restore the default priority of the local bridge.
  • Cause 3: The root bridge in the original topology was faulty.
    1. Rectify the fault in the original network topology. Then, check whether the alarm is cleared.
      • If the alarm is cleared, no action is required.
      • If the alarm persists, go to Step 2.
    2. Collect trap, log, and configuration information, and contact technical support personnel.
  • Cause 4: The priority of the root bridge in the original topology was reduced.
    1. Run the stp [ instance instance-id ] priority priority command or the stp [ instance instance-id ] root primary command on the original root bridge to re-specify the original root bridge as the root bridge. Then, check whether the alarm is cleared. If the alarm persists, go to Step 2.
    2. Collect trap, log, and configuration information, and contact technical support personnel.

MSTP_1.3.6.1.2.1.17.0.2 topologyChange

Description

Bridge topology changed.

The topology calculated by the STP changes.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Alert

Mnemonic Code

topologyChange

Trap OID

1.3.6.1.2.1.17.0.2

Alarm ID

This is an event trap and does not involve alarm ID.

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

This is an event trap and does not involve the match trap.

Parameters

None

VB

VB OID

VB Name

VB Index

None

None

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 [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number ] [ brief ] 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 trap, log, and configuration information, and 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 trap, log, and configuration information, and 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 trap, log, and configuration information, and contact technical support personnel.

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.1 hwMstpiPortStateForwarding

Description

The port has been set to forwarding state. (InstanceID=[INTEGER], PortIndex=[INTEGER], IfIndex=[INTEGER], PortName=[STRING], PwName=[PwName])

The port entered the forwarding state.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwMstpiPortStateForwarding

Trap OID

1.3.6.1.4.1.2011.5.25.42.4.2.1

Alarm ID

This is an event trap and does not involve alarm ID.

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

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

InstanceID

Indicates the instance ID.

PortID

Indicates the port ID.

IfIndex

Indicates the interface index.

PortName

Indicates the port name.

PwName

Indicates the pw name.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.19.1.1

hwMstpInstanceID

hwMstpInstanceID

1.3.6.1.4.1.2011.5.25.42.4.1.20.1.1

hwMstpInstanceID

hwMstpiPortIndex

1.3.6.1.2.1.31.1.1.1.1

hwMstpiPortIndex

ifName

Impact on the System

The network topology will change.

Possible Causes

The network topology changed.

Procedure
  • The network topology changed.
    1. View physical devices on the network to check whether a new physical link that has STP enabled is added.
      • If a new physical link that has STP enabled is added, go to Step 2.
      • If no new physical link that has STP enabled is added, go to Step 3.
    2. Check whether the added physical link is necessary.
      • If the added physical link is necessary, go to Step 3.
      • If the added physical link is unnecessary, go to Step 4.
    3. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] 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 5.
    4. Correctly deploy the network topology, and then check whether the alarm is cleared. If the alarm persists, go to Step 5.
    5. Collect trap, log, and configuration information, and contact technical support personnel.

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.2 hwMstpiPortStateDiscarding

Description

The port has been set to discarding state. (InstanceID=[INTEGER], PortIndex=[INTEGER], IfIndex=[INTEGER], PortName=[STRING], PwName=[STRING])

The port entered the blocking state.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwMstpiPortStateDiscarding

Trap OID

1.3.6.1.4.1.2011.5.25.42.4.2.2

Alarm ID

This is an event trap and does not involve alarm ID.

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

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

InstanceID

Indicates the instance ID.

PortIndex

Indicates the port ID.

IfIndex

Indicates the interface index.

PortName

Indicates the port name.

PwName

Indicates the pw name.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.19.1.1

hwMstpInstanceID

hwMstpInstanceID

1.3.6.1.4.1.2011.5.25.42.4.1.20.1.1

hwMstpInstanceID

hwMstpiPortIndex

1.3.6.1.2.1.31.1.1.1.1

hwMstpiPortIndex

ifName

Impact on the System

The network topology will be changed.

Possible Causes

The network topology changed.

Procedure
  • The network topology changed.
    1. View physical devices on the network to check whether a new physical link that has STP enabled is added.
      • If a new physical link that has STP enabled is added, go to Step 2.
      • If no new physical link that has STP enabled is added, go to Step 3.
    2. Check whether the added physical link is necessary.
      • If the added physical link is necessary, go to Step 3.
      • If the added physical link is unnecessary, go to Step 4.
    3. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] 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 5.
    4. Correctly deploy the network topology, and then check whether the alarm is cleared. If the alarm persists, go to Step 5.
    5. Collect trap, log, and configuration information, and contact technical support personnel.

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.3 hwMstpiBridgeLostRootPrimary

Description

This bridge is no longer the root bridge of the MSTP. (InstanceID=[InstanceID])

This bridge is no longer the root bridge of the instance.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Notice

Mnemonic Code

hwMstpiBridgeLostRootPrimary

Trap OID

1.3.6.1.4.1.2011.5.25.42.4.2.3

Alarm ID

This is an event trap and does not involve alarm ID.

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

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

InstanceID

Indicates the instance ID.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.19.1.1

hwMstpInstanceID

hwMstpInstanceID

Impact on the System

The actual network topology may not be the same as the expected one.

Possible Causes

Cause 1: This bridge received BPDUs with higher priorities.

Cause 2: The priority of another bridge is modified to be higher than the root bridge priority.

Procedure
  • Cause 1: This bridge received BPDUs with higher priorities.
    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 [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number ] [ brief ] command to check whether the interfaces are consistent with the STP calculation results.
      • If the interfaces are consistent with the STP calculation results, no action is required.
      • If the interfaces are inconsistent with the STP calculation results, go to Step 4.
    3. Correctly deploy the network topology, and then check whether the alarm is cleared. If the alarm persists, go to Step 4.
    4. Collect trap, log, and configuration information, and contact technical support personnel.
  • Cause 2: The priority of another bridge is modified to be higher than the root bridge priority.
    1. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] command to check whether the operation of changing the priority is correct in the network topology.
      • If the operation is correct, no action is required.
      • If the operation is incorrect, go to Step 2.
    2. Run the stp [ instance instance-id ] priority priority command to reset the priority of the local bridge as required. Alternatively, run the undo stp [ instance instance-id ] priority command or the undo stp [ instance instance-id ] root command to restore the default value of the priority of the local bridge. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
    3. Collect trap, log, and configuration information, and contact technical support personnel.

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.4 hwMstpiPortRootGuarded

Description

The root protection port received a superior message. (InstanceID=[InstanceID], PortIndex=[PortIndex], IfIndex=[IfIndex], PortName=[PortName], PwName=[PwName])

The port that has root protection enabled received BPDUs with higher priorities.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwMstpiPortRootGuarded

Trap OID

1.3.6.1.4.1.2011.5.25.42.4.2.4

Alarm ID

This is an event trap and does not involve alarm ID.

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

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

InstanceID

Indicates the instance ID.

PortIndex

Indicates the port ID.

IfIndex

Indicates the interface index.

PortName

Indicates the port name.

PwName

Indicates the pw name.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.19.1.1

hwMstpInstanceID

hwMstpInstanceID

1.3.6.1.4.1.2011.5.25.42.4.1.20.1.1

hwMstpInstanceID

hwMstpiPortIndex

1.3.6.1.2.1.31.1.1.1.1

hwMstpiPortIndex

ifName

Impact on the System

The actual network topology may not be the same as the expected one.

Possible Causes

Cause 1: The port that has root protection enabled received BPDUs of higher priorities than that of the bridge.

Cause 2: The priorities of some switches changed on the network.

Procedure
  • Cause 1: The port that has root protection enabled received BPDUs of higher priorities than that of the bridge.
    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 [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number ] [ brief ] command to check whether the interfaces are consistent with the STP calculation results.
      • If the interfaces are consistent with the STP calculation results, no action is required.
      • If the interfaces are inconsistent with the STP calculation results, go to Step 4.
    3. Correctly deploy the network topology, and then check whether the alarm is cleared. If the alarm persists, go to Step 4.
    4. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] command to check whether an interface is under the protection of the root bridge.
      • If an interface is under the protection of the root bridge, go to Step 5.
      • If no interface is under the protection of the root bridge, go to Step 6.
    5. Run the undo stp root-protection command in the interface view to delete the configuration of the protection under the root bridge. Then, check whether the alarm is cleared. If the alarm persists, go to Step 6.
    6. Collect trap, log, and configuration information, and contact technical support personnel.
  • Cause 2: The priorities of some switches changed on the network.
    1. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number ] [ brief ] command to check whether the operation of changing the priority is correct.
      • If the operation is correct, go to Step 3.
      • If the operation is incorrect, go to Step 2.
    2. Run the stp [ instance instance-id ] priority priority command to reset the priority of the local bridge as required. Alternatively, run the undo stp [ instance instance-id ] priority command or the undo stp [ instance instance-id ] root command to restore the default value of the priority of the local bridge. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.
    3. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number ] [ brief ] command to check whether an interface is under the protection of the root bridge.
      • If an interface is under the protection of the root bridge, go to Step 4.
      • If no interface is under the protection of the root bridge, go to Step 5.
    4. Run the undo stp root-protection command in the interface view to delete the configuration of the protection under the root bridge. Then, check whether the alarm is cleared. If the alarm persists, go to Step 5.
    5. Collect trap, log, and configuration information, and contact technical support personnel.

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.5 hwMstpiPortBpduGuarded

Description

The edge port with BPDU protection enabled will be shut down, because it received a BPDU packet that may be used to initiate an attack. (InstanceID=[InstanceID], PortIndex=[PortIndex], IfIndex=[IfIndex], PortName=[PortName])

The edge port that has BPDU protection enabled received BPDUs and was shut down.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwMstpiPortBpduGuarded

Trap OID

1.3.6.1.4.1.2011.5.25.42.4.2.5

Alarm ID

This is an event trap and does not involve alarm ID.

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

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

InstanceID

Indicates the instance ID.

PortIndex

Indicates the port ID.

IfIndex

Indicates the interface index.

PortName

Indicates the port name.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.20.1.1

hwMstpInstanceID

hwMstpiPortIndex

1.3.6.1.2.1.31.1.1.1.1

hwMstpiPortIndex

ifName

Impact on the System

The user network connected to this port will be broken down.

Possible Causes

The edge port received BPDUs, and BPDU protection was enabled globally.

Procedure
  • The edge port received BPDUs, and BPDU protection was enabled globally.
    1. Check whether the interface is directly connected to a user terminal and can be specified as an edge port.
      • If the interface is directly connected to a user terminal and therefore can be specified as an edge port, go to Step 2.
      • If the interface is indirectly connected to a user terminal and therefore cannot be specified as an edge port, go to Step 3.
    2. Locate the source of the BPDUs on the interface and check whether the malicious attack exists.
      • If the malicious attack exists, go to Step 4.
      • If the malicious attack does not exist, go to Step 3.
    3. Run the undo stp edged-port command and the undo shutdown command in the interface view to delete the configuration of the edge port and restart the interface. Then, check whether the alarm is cleared. If the alarm persists, go to Step 4.
    4. Collect trap, log, and configuration information, and contact technical support personnel.

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.6 hwMstpiPortLoopGuarded

Description

The loop protection port did not receive BPDU packets within prescriptive time. (InstanceID=[InstanceID], PortIndex=[PortIndex], IfIndex=[IfIndex], PortName=[PortName], PwName=[PwName])

The port that has loop protection enabled did not receive BPDUs within the specified time.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwMstpiPortLoopGuarded

Trap OID

1.3.6.1.4.1.2011.5.25.42.4.2.6

Alarm ID

This is an event trap and does not involve alarm ID.

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

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

InstanceID

Indicates the instance ID.

PortIndex

Indicates the instance ID of the port.

IfIndex

Indicates the interface index.

PortName

Indicates the port name.

PwName

Indicates the pw name.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.19.1.1

hwMstpInstanceID

hwMstpInstanceID

1.3.6.1.4.1.2011.5.25.42.4.1.20.1.1

hwMstpInstanceID

hwMstpiPortIndex

1.3.6.1.2.1.31.1.1.1.1

hwMstpiPortIndex

ifName

Impact on the System

The interface will not forward data.

Possible Causes

Cause 1: The spanning tree function was disabled on the peer device.

Cause 2: The links connected to the peer were congested.

Procedure
  • Cause 1: The spanning tree function was disabled on the peer device.
    1. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] command to check whether STP is disabled on the interfaces that are directly connected.
      • If STP is disabled on the interfaces that are directly connected, go to Step 2.
      • If STP is enabled on the interfaces that are directly connected, go to Step 3.
    2. Run the stp enable command in the interface view to enable STP. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.
    3. Collect trap, log, and configuration information, and contact technical support personnel.
  • Cause 2: The links connected to the peer were congested.
    1. Check whether the link between the local device and the neighbor device is congested.
      • If the link is congested, go to Step 2.
      • If the link is not congested, go to Step 3.
    2. Repair the physical link and then check whether the alarm is cleared. If the alarm persists, go to Step 3.
    3. Collect trap, log, and configuration information, and contact technical support personnel.

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.7 hwMstpiEdgePortChanged

Description

After the edge port receives a BPDU packet, the port is no longer an edge port. (InstanceID=[InstanceID], PortIndex=[PortIndex], EdgePortEnableState=[EdgePortEnableState], IfIndex=[IfIndex], PortName=[PortName], PwName=[PwName])

The edge port lost the attributes of an edge port after receiving BPDUs.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Emergency

Mnemonic Code

hwMstpiEdgePortChanged

Trap OID

1.3.6.1.4.1.2011.5.25.42.4.2.7

Alarm ID

This is an event trap and does not involve alarm ID.

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

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

InstanceID

Indicates the instance ID.

PortIndex

Indicates the port ID.

IfIndex

Indicates the interface index.

EdgePortEnableState

Indicates whether BPDU-guard is enabled on the edge port.

PortName

Indicates the port name.

PwName

Indicates the pw name.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.20.1.9

hwMstpInstanceID

hwMstpiStpPortEdgeport

1.3.6.1.2.1.31.1.1.1.1

hwMstpiPortIndex

ifName

Impact on the System

The network topology may be changed.

Possible Causes

The edge port received BPDUs.

Procedure
  • The edge port received BPDUs.
    1. Check whether the interface is directly connected to a user terminal and can be specified as an edge port.
      • If the interface is directly connected to a user terminal and therefore can be specified as an edge port, go to Step 2.
      • If the interface is indirectly connected to a user terminal and therefore cannot be specified as an edge port, go to Step 3.
    2. Locate the source of the BPDUs on the interface and check whether the malicious attack exists.
      • If the malicious attack exists, go to Step 4.
      • If the malicious attack does not exist, go to Step 3.
    3. Run the undo stp edged-port command and the undo shutdown command in the interface view to delete the configuration of the edge port and restart the interface. Then, check whether the alarm is cleared. If the alarm persists, go to Step 4.
    4. Collect trap, log, and configuration information, and contact technical support personnel.

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.15 hwMstpiTcGuarded

Description

With the TC protection enabled, if TC BPDUs were received after the number of TC BPDUs received by an instance exceeded the threshold, these TC BPDUs were processed after the TC protection time expires. (InstanceID=[InstanceID], bridgePriority=[bridgePriority])

If the number of TC BPDUs received by the instance exceeds the threshold, any new TC BPDU will be processed after the TC protection time expires.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwMstpiTcGuarded

Trap OID

1.3.6.1.4.1.2011.5.25.42.4.2.15

Alarm ID

This is an event trap and does not involve alarm ID.

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

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

InstanceID

Indicates the instance ID.

bridgePriority

Indicates the bridge priority.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.19.1.3

hwMstpInstanceID;

hwMstpiBridgePriority

Impact on the System

If the number of TC BPDUs exceeds the threshold, MAC entries and ARP entries will not be deleted immediately, and network topology will not be changed immediately, either.

Possible Causes

The number of TC messages received by an MSTP process in a specified period exceeded the threshold.

Procedure
  • The number of TC messages received by an MSTP process in a specified period exceeded the threshold.
    1. Check whether the network topology flapping occurs.
      • If the network topology flapping occurs, go to Step 3.
      • If the network topology flapping does not occur, go to Step 2.
    2. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] command to check whether the number of TC BPDUs exceeds the set threshold on the interface.
      • If the number of TC BPDUs exceeds the set threshold on the interface, go to Step 4.
      • If the number of TC BPDUs does not exceed the set threshold on the interface, go to Step 7.
    3. Locate the cause of the network topology flapping and rectify the fault. Then, check whether the alarm is cleared. If the alarm persists, go to Step 2.
    4. Run the stp tc-protection threshold threshold command in the interface view to reset the maximum number of TC BPDUs that the device can process. Then, check whether the alarm is cleared. If the alarm persists, go to Step 5.
    5. Check whether the malicious attack exists.
      • If the malicious attack exists, go to Step 6.
      • If the malicious attack does not exist, go to Step 7.
    6. Locate the attack source and remove the attack. Then, check whether the alarm is cleared. If the alarm persists, go to Step 7.
    7. Collect trap, log, and configuration information, and contact technical support personnel.

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.16 hwMstpProTcGuarded

Description

With the TC protection enabled, if TC BPDUs were received after the number of TC BPDUs received by an instance exceeded the threshold, these TC BPDUs were processed after the TC protection time expires. (ProcessID=[ProcessID], proTcGuard=[proTcGuard], InstanceID=[InstanceID], proInstBridgePriority=[proInstBridgePriority])

If the number of TC BPDUs received by the MSTP process instance exceeds the threshold, any new TC BPDU will be processed after the TC protection time expires.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwMstpProTcGuarded

Trap OID

1.3.6.1.4.1.2011.5.25.42.4.2.16

Alarm ID

This is an event trap and does not involve alarm ID.

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

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

ProcessID

Indicates the ID of an MSTP process.

proTcGuard

Indicates that the TC protection is enabled or disabled.

InstanceID

Indicates the instance ID.

proInstBridgePriority

Indicates the root priority.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.23.1.21

hwMstpProID

hwMstpProTcGuard

1.3.6.1.4.1.2011.5.25.42.4.1.28.1.2

hwMstpInstanceID

hwMstpProInstanceBridgePriority

Impact on the System

If the number of TC BPDUs exceeds the threshold, MAC entries and ARP entries will not be deleted immediately, and network topology will not be changed immediately, either.

Possible Causes

The number of TC messages received by an MSTP process in a specified period exceeded the threshold.

Procedure
  • The number of TC messages received by an MSTP process in a specified period exceeded the threshold.
    1. Check whether the network topology flapping occurs.
      • If the network topology flapping occurs, go to Step 3.
      • If the network topology flapping does not occur, go to Step 2.
    2. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] command to check whether the number of TC BPDUs exceeds the set threshold on the interface.
      • If the number of TC BPDUs exceeds the set threshold on the interface, go to Step 4.
      • If the number of TC BPDUs does not exceed the set threshold on the interface, go to Step 7.
    3. Locate the cause of the network topology flapping and rectify the fault. Then, check whether the alarm is cleared. If the alarm persists, go to Step 2.
    4. Run the stp tc-protection threshold threshold command in the MSTP process view to reset the maximum number of TC BPDUs that the MSTP process can process. Then, check whether the alarm is cleared. If the alarm persists, go to Step 5.
    5. Check whether the malicious attack exists.
      • If the malicious attack exists, go to Step 6.
      • If the malicious attack does not exist, go to Step 7.
    6. Locate the attack source and remove the attack. Then, check whether the alarm is cleared. If the alarm persists, go to Step 7.
    7. Collect trap, log, and configuration information, and contact technical support personnel.

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.17 hwMstpProRootChanged

Description

The root bridge of MSTP process changed. (ProcessID=[ProcessID], InstanceID=[InstanceID], PortID=[PortID])

The root bridge in the MSTP process changed.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwMstpProRootChanged

Trap OID

1.3.6.1.4.1.2011.5.25.42.4.2.17

Alarm ID

This is an event trap and does not involve alarm ID.

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

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

ProcessID

Indicates the ID of an MSTP process.

InstanceID

Indicates the instance ID.

PortID

Indicates the port ID.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.28.1.5

hwMstpProID;hwMstpInstanceID

hwMstpProInstanceRootPort

Impact on the System

If the root bridge is not a core node, it will affect the performance of the entire network.

Possible Causes

Cause 1: A new device, which had the optimal bridge ID, was added.

Cause 2: The priorities of the devices or the domain configuration on the current network were modified.

Procedure
  • Cause 1: A new device, which had the optimal bridge ID, was added.
    1. Check whether the added physical link is required.
      • 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 [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] command to check whether the bridge ID is optimal on the entire network.
      • If the bridge ID is optimal on the entire network, go to Step 3.
      • If the bridge ID is not optimal on the entire network, go to Step 5.
    3. Check whether the bridge ID of the added device should be the optimal one on the entire network.
      • If the bridge ID of the added device should be the optimal one on the entire network, the alarm will be cleared.
      • If the bridge ID of the added device should not be the optimal one on the entire network, go to Step 4.
    4. Correctly configure the device according to the topology, and then check whether the alarm is cleared. If the alarm persists, go to Step 5.
    5. Collect trap, log, and configuration information, and contact technical support personnel.
  • Cause 2: The priorities of the devices or the domain configuration on the current network were modified.
    1. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number ] [ brief ] command to check whether the operation of changing the vectors of the instance or the domain configuration is correct. If the operation is incorrect, go to Step 2.
    2. Correctly configure the device according to the topology, and then check whether the alarm is cleared. If the alarm persists, go to Step 3.
    3. Collect trap, log, and configuration information, and contact technical support personnel.

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.18 hwMstpProNewPortStateForwarding

Description

The MSTP process's port has been set to forwarding state. (ProcessID=[ProcessID], InstanceID=[InstanceID], PortID1=[PortID1], PortID2=[PortID2], PortID3=[PortID3], PortID4=[PortID4], PortIDFlag=[PortIDFlag], PortState=[PortState], IfIndex=[IfIndex], PortName=[PortName], PwName=[PwName])

The port in the MSTP process entered the forwarding state.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwMstpProNewPortStateForwarding

Trap OID

1.3.6.1.4.1.2011.5.25.42.4.2.18

Alarm ID

This is an event trap and does not involve alarm ID.

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

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

ProcessID

Indicates the MSTP process ID.

InstanceID

Indicates the instance ID.

PortID1

Indicates ID 1 of the port in the MSTP process.

PortID2

Indicates ID 2 of the port in the MSTP process.

PortID3

Indicates ID 3 of the port in the MSTP process.

PortID4

Indicates ID 4 of the port in the MSTP process.

PortIDFlag

Indicates the port flag.

IfIndex

Indicates the interface index.

PortState

Indicates the port state.

PortName

Indicates the port name.

PwName

Indicate the pw name.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.29.1.1

hwMstpProNewPortState

hwMstpProNewPortState

1.3.6.1.4.1.2011.5.25.42.4.1.33

hwMstpPwName

hwMstpPwName

1.3.6.1.2.1.31.1.1.1.1

ifName

ifName

Impact on the System

The network topology will change.

Possible Causes

The network topology changed.

Procedure
  • The network topology changed.
    1. View physical devices on the network to check whether a new physical link that has STP enabled is added.
      • If a new physical link that has STP enabled is added, go to Step 2.
      • If no new physical link that has STP enabled is added, go to Step 3.
    2. Check whether the added physical link is necessary.
      • If the added physical link is necessary, go to Step 3.
      • If the added physical link is unnecessary, go to Step 4.
    3. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] 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 5.
    4. Correctly deploy the network topology, and then check whether the alarm is cleared. If the alarm persists, go to Step 5.
    5. Collect trap, log, and configuration information, and contact technical support personnel.

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.19 hwMstpProNewPortStateDiscarding

Description

The MSTP process's port has been set to discarding state. (ProcessID=[ProcessID], InstanceID=[InstanceID], PortID1=[PortID1], PortID2=[PortID2], PortID3=[PortID3], PortID4=[PortID4], PortIDFlag=[PortIDFlag], PortState=[PortState], IfIndex=[IfIndex], PortName=[PortName], PwName=[PwName])

The port in the MSTP process entered the blocking state.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwMstpProNewPortStateDiscarding

Trap OID

1.3.6.1.4.1.2011.5.25.42.4.2.19

Alarm ID

This is an event trap and does not involve alarm ID.

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

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

ProcessID

Indicates the MSTP process ID.

InstanceID

Indicates the instance ID.

PortID1

Indicates ID 1 of the port in the MSTP process.

PortID2

Indicates ID 2 of the port in the MSTP process.

PortID3

Indicates ID 3 of the port in the MSTP process.

PortID4

Indicates ID 4 of the port in the MSTP process.

PortIDFlag

Indicates the port flag.

IfIndex

Indicates the interface index.

PortState

Indicates the port state.

PortName

Indicates the port name.

PwName

Indicates the pw name.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.29.1.1

hwMstpProNewPortState

hwMstpProNewPortState

1.3.6.1.4.1.2011.5.25.42.4.1.33

hwMstpPwName

hwMstpPwName

1.3.6.1.2.1.31.1.1.1.1

ifName

ifName

Impact on the System

The network topology will be changed.

Possible Causes

The network topology changed.

Procedure
  • The network topology changed.
    1. View physical devices on the network to check whether a new physical link that has STP enabled is added.
      • If a new physical link that has STP enabled is added, go to Step 2.
      • If no new physical link that has STP enabled is added, go to Step 3.
    2. Check whether the added physical link is necessary.
      • If the added physical link is necessary, go to Step 3.
      • If the added physical link is unnecessary, go to Step 4.
    3. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] 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 5.
    4. Correctly deploy the network topology, and then check whether the alarm is cleared. If the alarm persists, go to Step 5.
    5. Collect trap, log, and configuration information, and contact technical support personnel.

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.20 hwMstpProNewBridgeLostRootPrimary

Description

MSTP process is no longer the root bridge of the instance. (ProcessID=[ProcessID],InstanceID=[InstanceID],proInstRootType=[proInstRootType])

This bridge is no longer the root bridge of the instance.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwMstpProNewBridgeLostRootPrimary

Trap OID

1.3.6.1.4.1.2011.5.25.42.4.2.20

Alarm ID

This is an event trap and does not involve alarm ID.

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

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

ProcessID

Indicates the MSTP process ID.

InstanceID

Indicates the instance ID.

proInstRootType

Indicates the root type.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.28.1.6

hwMstpProID;hwMstpInstanceID;

hwMstpProInstanceRootType

Impact on the System

The actual network topology may not be the same as the expected one.

Possible Causes

Cause 1: A new link was added to the network topology, and the network topology changed.

Cause 2: The priorities of some switches changed on the network.

Procedure
  • Cause 1: A new link was added to the network topology, and the network topology changed.
    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 [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number ] [ brief ] command to check whether the interfaces are consistent with the STP calculation results.
      • If the interfaces are consistent with the STP calculation results, no action is required.
      • If the interfaces are inconsistent with the STP calculation results, go to Step 4.
    3. Correctly deploy the network topology, and then check whether the alarm is cleared. If the alarm persists, go to Step 4.
    4. Collect trap, log, and configuration information, and contact technical support personnel.
  • Cause 2: The priorities of some switches changed on the network.
    1. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] command to check whether the operation of changing the priority is correct in the network topology.
      • If the operation is correct, no action is required.
      • If the operation is incorrect, go to Step 2.
    2. Run the stp [ instance instance-id ] priority priority command to reset the priority of the local bridge as required. Alternatively, run the undo stp [ instance instance-id ] priority command or the undo stp [ instance instance-id ] root command to restore the default value of the priority of the local bridge. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.
    3. Collect trap, log, and configuration information, and contact technical support personnel.

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.21 hwMstpProNewPortRootGuarded

Description

The root protection port of the instance of the MSTP process received a superior message. (ProcessID=[ProcessID], InstanceID=[InstanceID], PortID1=[PortID1], PortID2=[PortID2], PortID3=[PortID3], PortID4=[PortID4], PortIDFlag=[PortIDFlag], PortState=[PortState], IfIndex=[IfIndex], PortName=[PortName], PwName=[PwName])

The port in the MSTP process instance that has root protection enabled received BPDUs with higher priorities.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwMstpProNewPortRootGuarded

Trap OID

1.3.6.1.4.1.2011.5.25.42.4.2.21

Alarm ID

This is an event trap and does not involve alarm ID.

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

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

ProcessID

Indicates the MSTP process ID.

InstanceID

Indicates the instance ID.

PortID1

Indicates ID 1 of the port in the MSTP process.

PortID2

Indicates ID 2 of the port in the MSTP process.

PortID3

Indicates ID 3 of the port in the MSTP process.

PortID4

Indicates ID 4 of the port in the MSTP process.

PortIDFlag

Indicates the port flag.

IfIndex

Indicates the interface index.

PortState

Indicates the port state.

PortName

Indicates the port name.

PwName

Indicates the pw name.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.29.1.1

hwMstpProNewPortState

hwMstpProNewPortState

1.3.6.1.4.1.2011.5.25.42.4.1.33

hwMstpPwName

hwMstpPwName

1.3.6.1.2.1.31.1.1.1.1

ifName

ifName

Impact on the System

The actual network topology may not be the same as the expected one.

Possible Causes

Cause 1: The port that has root protection enabled received BPDUs of higher priorities than that of the bridge.

Cause 2: The priorities of some switches changed on the network.

Procedure
  • Cause 1: The port that has root protection enabled received BPDUs of higher priorities than that of the bridge.
    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 [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] command to check whether the interfaces are consistent with the STP calculation results.
      • If the interfaces are consistent with the STP calculation results, no action is required.
      • If the interfaces are inconsistent with the STP calculation results, go to Step 4.
    3. Correctly deploy the network topology, and then check whether the alarm is cleared. If the alarm persists, go to Step 4.
    4. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number ] [ brief ] command to check whether an interface is under the protection of the root bridge.
      • If an interface is under the protection of the root bridge, go to Step 5.
      • If no interface is under the protection of the root bridge, go to Step 6.
    5. Run the undo stp root-protection command in the interface view to disable the protection under the root bridge. Then, check whether the alarm is cleared. If the alarm persists, go to Step 6.
    6. Collect trap, log, and configuration information, and contact technical support personnel.
  • Cause 2: The priorities of some switches changed on the network.
    1. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number ] [ brief ] command to check whether the operation of changing the priority is correct in the network topology.
      • If the operation is correct, go to Step 3.
      • If the operation is incorrect, go to Step 2.
    2. Run the stp [ instance instance-id ] priority priority command to reset the priority of the local bridge as required. Alternatively, run the undo stp [ instance instance-id ] priority command or the undo stp [ instance instance-id ] root command to restore the default value of the priority of the local bridge. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.
    3. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number ] [ brief ] command to check whether an interface is under the protection of the root bridge.
      • If an interface is under the protection of the root bridge, go to Step 4.
      • If no interface is under the protection of the root bridge, go to Step 5.
    4. Run the undo stp root-protection command in the interface view to disable the protection under the root bridge. Then, check whether the alarm is cleared. If the alarm persists, go to Step 5.
    5. Collect trap, log, and configuration information, and contact technical support personnel.

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.22 hwMstpProNewPortBpduGuarded

Description

The MSTP process's edge port with BPDU protection enabled will be shut down, because it received a BPDU packet. (ProcessID=[ProcessID], InstanceID=[InstanceID], PortID1=[PortID1], PortID2=[PortID2], PortID3=[PortID3], PortID4=[PortID4], PortIDFlag=[PortIDFlag], PortState=[PortState], IfIndex=[IfIndex], PortName=[PortName])

The edge port in the MSTP process that has BPDU protection enabled received BPDUs and was shut down.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwMstpProNewPortBpduGuarded

Trap OID

1.3.6.1.4.1.2011.5.25.42.4.2.22

Alarm ID

This is an event trap and does not involve alarm ID.

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

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

ProcessID

Indicates the MSTP process ID.

InstanceID

Indicates the instance ID.

PortID1

Indicates ID 1 of the port in the MSTP process.

PortID2

Indicates ID 2 of the port in the MSTP process.

PortID3

Indicates ID 3 of the port in the MSTP process.

PortID4

Indicates ID 4 of the port in the MSTP process.

PortIDFlag

Indicates the port flag.

IfIndex

Indicates the interface index.

PortState

Indicates the port state.

PortName

Indicates the port name.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.29.1.1

hwMstpProNewPortState

hwMstpProNewPortState

1.3.6.1.2.1.31.1.1.1.1

ifName

ifName

Impact on the System

The user network connected to this port will be broken down.

Possible Causes

The edge port received BPDUs, and BPDU protection was enabled globally.

Procedure
  • The edge port received BPDUs, and BPDU protection was enabled globally.
    1. Check whether the interface is directly connected to a user terminal and can be specified as an edge port.
      • If the interface is directly connected to a user terminal and therefore can be specified as an edge port, go to Step 2.
      • If the interface is indirectly connected to a user terminal and therefore cannot be specified as an edge port, go to Step 3.
    2. Locate the source of the BPDUs on the interface and check whether the malicious attack exists.
      • If the malicious attack exists, go to Step 4.
      • If the malicious attack does not exist, go to Step 3.
    3. Run the undo stp root-protection and undo shutdown commands in the interface view to delete the configuration of the edge port and restart the interface. Then, check whether the alarm is cleared. If the alarm persists, go to Step 4.
    4. Collect trap, log, and configuration information, and contact technical support personnel.

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.23 hwMstpProNewPortLoopGuarded

Description

The loop protection port in the instance of the MSTP process did not receive BPDU packets within prescriptive time. (ProcessID=[ProcessID], InstanceID=[InstanceID], PortID1=[PortID1], PortID2=[PortID2], PortID3=[PortID3], PortID4=[PortID4], PortIDFlag=[PortIDFlag], PortState=[PortState], IfIndex=[IfIndex], PortName=[PortName], PwName=[PwName])

The port in the MSTP process instance that has loop protection enabled did not receive BPDUs within the specified time.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwMstpProNewPortLoopGuarded

Trap OID

1.3.6.1.4.1.2011.5.25.42.4.2.23

Alarm ID

This is an event trap and does not involve alarm ID.

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

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

ProcessID

Indicates the MSTP process ID.

InstanceID

Indicates the instance ID.

PortID1

Indicates ID 1 of the port in the MSTP process.

PortID2

Indicates ID 2 of the port in the MSTP process.

PortID3

Indicates ID 3 of the port in the MSTP process.

PortID4

Indicates ID 4 of the port in the MSTP process.

PortIDFlag

Indicates the port flag.

IfIndex

Indicates the interface index.

PortState

Indicates the port state.

PortName

Indicates the port name.

PwName

Indicates the pw name.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.29.1.1

hwMstpProNewPortState

hwMstpProNewPortState

1.3.6.1.4.1.2011.5.25.42.4.1.33

hwMstpPwName

hwMstpPwName

1.3.6.1.2.1.31.1.1.1.1

ifName

ifName

Impact on the System

The interface will not forward data.

Possible Causes

Cause 1: The spanning tree function was disabled on the peer device.

Cause 2: The links connected to the peer were congested.

Procedure
  • Cause 1: The spanning tree function was disabled on the peer device.
    1. Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] command to check whether STP is disabled on the interfaces that are directly connected.
      • If STP is disabled on the interfaces that are directly connected, go to Step 2.
      • If STP is enabled on the interfaces that are directly connected, go to Step 3.
    2. Run the stp enable command in the interface view to enable STP. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.
    3. Collect trap, log, and configuration information, and contact technical support personnel.
  • Cause 2: The links connected to the peer were congested.
    1. Check whether the link is congested between the local device and the neighbor device.
      • If the link is congested, go to Step 2.
      • If the link is not congested, go to Step 3.
    2. Repair the physical link and then check whether the alarm is cleared. If the alarm persists, go to Step 3.
    3. Collect trap, log, and configuration information, and contact technical support personnel.

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.24 hwMstpProNewEdgePortChanged

Description

After the edge port receives a BPDU packet, the port is no longer an edge port. (ProcessID=[ProcessID], InstanceID=[InstanceID], PortID1=[PortID1], PortID2=[PortID2], PortID3=[PortID3], PortID4=[PortID4], PortIDFlag=[PortIDFlag], PortState=[PortState], IfIndex=[IfIndex], PortName=[PortName], PwName=[PwName])

The edge port of the MSTP process lost the attributes of an edge port after receiving BPDUs.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwMstpProNewEdgePortChanged

Trap OID

1.3.6.1.4.1.2011.5.25.42.4.2.24

Alarm ID

This is an event trap and does not involve alarm ID.

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

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

ProcessID

Indicates the MSTP process ID.

InstanceID

Indicates the instance ID.

PortID1

Indicates ID 1 of the port in the MSTP process.

PortID2

Indicates ID 2 of the port in the MSTP process.

PortID3

Indicates ID 3 of the port in the MSTP process.

PortID4

Indicates ID 4 of the port in the MSTP process.

PortIDFlag

Indicates the port flag.

IfIndex

Indicates the interface index.

PortState

Indicates the port state.

PortName

Indicates the port name.

PwName

Indicates the pw name.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.29.1.1

hwMstpProNewPortState

hwMstpProNewPortState

1.3.6.1.4.1.2011.5.25.42.4.1.33

hwMstpPwName

hwMstpPwName

1.3.6.1.2.1.31.1.1.1.1

ifName

ifName

Impact on the System

Services will not be affected.

Possible Causes

In the MSTP process, the edge port received BPDUs.

Procedure
  • In the MSTP process, the edge port received BPDUs.
    1. Check whether the interface is directly connected to a user terminal and can be specified as an edge port.
      • If the interface is directly connected to a user terminal and therefore can be specified as an edge port, go to Step 2.
      • If the interface is indirectly connected to a user terminal and therefore cannot be specified as an edge port, go to Step 3.
    2. Locate the source of the BPDUs on the interface and check whether the malicious attack exists.
      • If the malicious attack exists, go to Step 4.
      • If the malicious attack does not exist, go to Step 3.
    3. Run the undo stp edged-port command and the undo shutdown command in the interface view to delete the configuration of the edge port and restart the interface. Then, check whether the alarm is cleared. If the alarm persists, go to Step 4.
    4. Collect trap, log, and configuration information, and contact technical support personnel.

MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.25 hwMstpProLoopbackDetected

Description

The MSTP process's port has been set to discarding state because of detecting loopback. (ProcessID=[ProcessID], InstanceID=[InstanceID], PortID1=[PortID1], PortID2=[PortID2], PortID3=[PortID3], PortID4=[PortID4], PortIDFlag=[PortIDFlag], PortState=[PortState], IfIndex=[IfIndex], PortName=[PortName], PwName=[PwName])

When the port detected loopback, block the port and arise trap.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwMstpProLoopbackDetected

Trap OID

1.3.6.1.4.1.2011.5.25.42.4.2.25

Alarm ID

This is an event trap and does not involve alarm ID.

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

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

ProcessID

Indicates the MSTP process ID.

InstanceID

Indicates the instance ID.

PortID1

Indicates ID 1 of the port in the MSTP process.

PortID2

Indicates ID 2 of the port in the MSTP process.

PortID3

Indicates ID 3 of the port in the MSTP process.

PortID4

Indicates ID 4 of the port in the MSTP process.

PortIDFlag

Indicates the port flag.

IfIndex

Indicates the interface index.

PortState

Indicates the port state.

PortName

Indicates the port name.

PwName

Indicates the pw name.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.42.4.1.29.1.1

hwMstpProNewPortState

hwMstpProNewPortState

1.3.6.1.4.1.2011.5.25.42.4.1.33

hwMstpPwName

hwMstpPwName

1.3.6.1.2.1.31.1.1.1.1

ifName

ifName

Impact on the System

After detecting a port blocked by local loopback, the system considers that a network storm occurs and blocks the local port to prevent the network storm from affecting services of the entire network. Services on the blocked port will be interrupted.

Possible Causes

The STP port of the equipment detected a loopback.

Procedure
  • The STP port of the equipment detected a loopback.
    1. Check whether a local loopback is configured on the interface where the alarm is generated.
      • If a local loopback is configured on the interface where the alarm is generated, go to Step 3.
      • If no local loopback is configured on the interface where the alarm is generated, go to Step 2.
    2. Check whether a loop is formed by a hub and devices, one of which is connected to the interface.
      • If a loop is formed by a hub and devices, one of which is connected to the interface, go to Step 4.
      • If no loop is formed by a hub and devices, one of which is connected to the interface, go to Step 5.
    3. Delete the local loopback configuration, and check whether the alarm is cleared. If the alarm persists, go to Step 5.
    4. Remove the self-loop network cable from the hub and check whether the alarm is cleared. If the alarm persists, go to Step 5.
    5. Collect trap, log, and configuration information, and contact technical support personnel.
Translation
Download
Updated: 2018-08-16

Document ID: EDOC1000015902

Views: 196852

Downloads: 1572

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next