MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.16 hwMstpProTcGuarded

Description

MSTP/1/PROTCGUARD:OID [OID] MSTP process's instance received TC message exceeded the threshold will be deferred to deal with at the end of TC protection time. (ProcessID=[INTEGER], InstanceID=[INTEGER])

After the TC protection of the MSTP process was enabled, the TC packets, which were received after the number of TC packets received by an instance had exceeded the threshold, were processed after the TC protection time expired.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.5.25.42.4.2.16	Critical	communicationsAlarm(2)

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
ProcessID	Indicates the ID of an MSTP process.
InstanceID	Indicates the ID of an MSTP instance.

Impact on the System

If the number of TC BPDUs exceeds the threshold, MAC address entries and ARP entries will not be deleted immediately, and the traffic forwarding path will not be changed immediately, either.

Possible Causes

The TC packets, which were received after the number of TC messages received by an MSTP process in a specified period had exceeded the threshold, were processed after the TC protection time expired.

Procedure

Check whether the network topology flaps.
- If so, go to Step 3.
- If not, go to Step 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 so, go to Step 4.
- If not, go to Step 7.
Locate the cause of the network topology flapping and rectify the fault. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 8.
- If the alarm is not cleared, go to Step 2.
Run the stp tc-protection threshold threshold command in the MSTP process view to re-set the maximum number of TC BPDUs that the MSTP process can process. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 8.
- If the alarm is not cleared, go to Step 5.
Check whether the malicious attacks exist.
- If so, go to Step 6.
- If not, go to Step 7.
Locate the attack source and remove the attack. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 8.
- If the alarm is not cleared, go to Step 7.
Collect alarm information and configuration information, and then contact technical support personnel.
End.

Related Information

None.