The root bridge role flapped.(ProcessID=[ProcessID], InstanceID=[InstanceID])
The root bridge role flapped for a non-root bridge device.
| Trap Attribute | Description |
|---|---|
Alarm or Event |
Alarm |
Trap Severity |
Critical |
Mnemonic Code |
hwMstpProRootShake |
Trap OID |
1.3.6.1.4.1.2011.5.25.42.4.2.30 |
MIB |
HUAWEI-MSTP-MIB |
Alarm ID |
0x0d542001 |
Alarm Name |
hwMstpProRootShake |
Alarm Type |
communicationsAlarm |
Raise or Clear |
Raise |
Match trap |
MSTP_1.3.6.1.4.1.2011.5.25.42.4.2.31 hwMstpProRootShakeResume |
| Parameter | Description |
|---|---|
ProcessID |
Process ID |
InstanceID |
Instance ID |
| VB OID | VB Name | VB Index |
|---|---|---|
1.3.6.1.4.1.2011.5.25.42.4.1.23.1.1 |
hwMstpProID |
hwMstpProID |
1.3.6.1.4.1.2011.5.25.42.4.1.19.1.1 |
hwMstpInstanceID |
hwMstpInstanceID |
When BPDU packets are transparently transmitted on an MSTP network, some ports receive multiple copies of BPDU packets. If the root bridge information in multiple copies of BPDU packets is inconsistent, the root bridge flaps and the MSTP network reconverges. When the count of root flaps up to 10 in 5 minutes, the alarm will be triggered.
1. Check MSTP logs to determine whether alarms indicating frequent intermittent Down events are reported on the ports or port priorities are frequently changed.
2. Deploy the network topology correctly and check whether the alarm is cleared.
3. Check MSTP logs to determine the source of BPDUs on the ports and identify the flapping source.
4. Collect alarm information and configuration information, and then contact technical support personnel.