VBST
These alarms can be only queried through a command but not the MIB.
- VBST_1.3.6.1.4.1.2011.5.25.323.2.3 hwVbstPVNumExceeded
- VBST_1.3.6.1.4.1.2011.5.25.323.2.4 hwVbstPVNumResumed
- VBST_1.3.6.1.4.1.2011.5.25.323.2.7 hwVbstTrapInvalidPV
- VBST_1.3.6.1.4.1.2011.5.25.323.2.8 hwVbstTrunkPVNumExceeded
- VBST_1.3.6.1.4.1.2011.5.25.323.2.9 hwVbstTrunkPVNumResumed
- VBST_1.3.6.1.4.1.2011.5.25.323.2.10 hwVbstRspanCfgConflict
VBST_1.3.6.1.4.1.2011.5.25.323.2.3 hwVbstPVNumExceeded
Description
VBST/4/PORTVLANEXCEED: OID [OID] The limit of port-VLAN exceeded. (entPhysicalIndex=[ULONG], entPhysicalName=[STRING], MaxNum=[ULONG])
The number of interfaces and VLANs participating in VBST calculation exceeded the maximum number of interfaces and VLANs allowed by VBST.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.323.2.3 | Warning | qualityOfServiceAlarm(3) |
Parameters
| Name | Meaning |
|---|---|
| OID | Indicates the MIB object ID of the alarm. |
| entPhysicalIndex | Index of a slot number participating in the VBST calculation |
| entPhysicalName | Name of a slot number participating in the VBST calculation |
| MaxNum | Number of interfaces and VLANs participating in the VBST calculation. |
Impact on the System
- The VBST calculation efficiency will be affected, delaying network loop breaking.
- The CPU usage may become high, the calculation of other protocols is affected, and even the device may fail to be managed by the NMS.
Possible Causes
VBST performs a spanning tree calculation based on VLANs. As a result, all the interfaces added to a VLAN participated in the VBST calculation by default.
Procedure
- Check whether all the interfaces participating in the VBST
calculation must be added to the VLAN.
- If it is unnecessary, remove some interfaces from the VLAN and check whether the alarm is cleared. If the alarm persists, go to Step 2.
- If it is necessary, go to Step 2.
- Run the stp disable command in the views of the interfaces that do not need to participate in the VBST calculation to disable the Eth-Trunk interfaces from performing the spanning tree calculation. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.
- Collect alarm, log, and configuration information, and contact technical support personnel.
VBST_1.3.6.1.4.1.2011.5.25.323.2.4 hwVbstPVNumResumed
Description
VBST/4/PORTVLANRESUME: OID [OID] The limit of port-VLAN resumed. (entPhysicalIndex=[ULONG], entPhysicalName=[STRING], MaxNum=[ULONG])
This alarm is triggered when the number of interfaces and VLANs participating in VBST calculation falls below the maximum number of interfaces and VLANs allowed by VBST.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.323.2.4 | Warning | qualityOfServiceAlarm(3) |
Parameters
| Name | Meaning |
|---|---|
| OID | Indicates the MIB object ID of the alarm. |
| entPhysicalIndex | Index of a slot number participating in the VBST calculation. |
| entPhysicalName | Name of a slot number participating in the VBST calculation. |
| MaxNum | Number of interfaces and VLANs participating in the VBST calculation. |
VBST_1.3.6.1.4.1.2011.5.25.323.2.7 hwVbstTrapInvalidPV
Description
VBST/4/PORTVLANINVALID:OID [OID] The number of VLANs that do not participate in calculation in the VBST BPDUs received by interface is [ULONG]. (InterfaceName=[STRING], VlanId=[STRING])
The number of VLANs that do not participate in calculation in the VBST BPDUs received by the interface exceeds the threshold.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.323.2.7 | Warning | qualityOfServiceAlarm(3) |
Parameters
| Name | Meaning |
|---|---|
| OID | Indicates the ID of a MIB object. |
| hwVbstTrapVlanNum | Indicates the number of VLANs that do not participate in calculation in the VBST BPDUs received by the interface. |
| hwVbstTrapVlan | Indicates the list of VLANs that do not participate in calculation in the VBST BPDUs received by the interface. |
| hwVbstTrapPort | Indicates the list of interfaces where the received VBST BPDUs contain the VLANs that do not participate in calculation. |
Impact on the System
When the local end receives VBST BPDUs from VBST-incapable VLANs, VBST calculation in VBST-enabled VLANs on the local end may be affected and even protocol flapping may occur.
Possible Causes
When the local end receives VBST BPDUs from VBST-incapable VLANs, VBST calculation in VBST-enabled VLANs on the local end may be affected. In this case, the system counts the number of VLANs that do not participate in calculation. When the value exceeds the threshold of 15, an alarm is generated.
Procedure
- Check whether VBST needs to be enabled in VLANs in the alarm.
- Run the stp vlan { vlan-id1 [ to vlan-id2 ] } &<1-10> enable command to enable VBST in corresponding VLANs in the alarm. Check whether the alarm still exists. If the alarm still exists, go to step 4.
- Check the configuration of corresponding remote interfaces and disable spanning tree calculation in VLANs on corresponding interfaces. Check whether the alarm still exists. If the alarm still exists, go to step 4.
- Collect trap, log, and configuration information, and contact technical support personnel.
VBST_1.3.6.1.4.1.2011.5.25.323.2.8 hwVbstTrunkPVNumExceeded
Description
VBST/4/ETHTRUNKPVEXCEED:OID [OID] The number of port VLANs of Eth-Trunk exceeds the limit of VBST. (max=[ULONG])
The number of PVs of an Eth-Trunk (PV is the production of the VBST-enabled interface quantity multiplied by the VLAN quantity) exceeds the maximum value.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.323.2.8 | Warning | qualityOfServiceAlarm(3) |
Parameters
| Name | Meaning |
|---|---|
| OID | Indicates the MIB object ID of the alarm. |
| max | Indicates the maximum number of PVs on an Eth-Trunk. |
Impact on the System
VBST calculation efficiency may be affected, and the network loop elimination time is increased.
The CPU usage becomes high, affecting calculation of other protocols. Even the device may be not managed by the NMS.
Procedure
- Check whether the Eth-Trunk that does not need to join
the VLAN where VBST calculation is performed is added to the VLAN.
- If so, remove the Eth-Trunk from the VLAN and check whether the alarm still exists. If the alarm still exists, go to step 2.
- If not, go to step 2.
- Run the stp disable command to disable STP on the interface that does not need to participate in VBST calculation. Check whether the alarm still exists. If the alarm exists, go to step 3.
- Collect alarms, logs, and configurations, and contact technical support personnel.
VBST_1.3.6.1.4.1.2011.5.25.323.2.9 hwVbstTrunkPVNumResumed
Description
VBST/4/ETHTRUNKPVRESUME:OID [OID] The number of port VLANs of Eth-Trunk falls below the limit of VBST. (max=[ULONG])
The number of PVs of an Eth-Trunk (PV is the production of the VBST-enabled interface quantity multiplied by the VLAN quantity) returns to the allowed range.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.323.2.9 | Warning | qualityOfServiceAlarm(3) |
VBST_1.3.6.1.4.1.2011.5.25.323.2.10 hwVbstRspanCfgConflict
Description
VBST/4/RSPANCFGCONFLICT: OID [OID] In VBST mode, the Eth-Trunk configuration conflicts with the remote observing port configuration. (Description=[OCTET])
In VBST mode, the Eth-Trunk configuration conflicts with the remote observing port configuration.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.323.2.10 | Warning | environmentalAlarm(6) |
Parameters
| Name | Meaning |
|---|---|
| OID | Indicates the MIB object ID of the alarm. |
| Description | Cause of a configuration conflict. |
Possible Causes
- The switch is configured to operate in VBST mode.
- An Eth-Trunk is configured on the switch, and STP is enabled on the Eth-Trunk.
- The Eth-Trunk or an Eth-Trunk member interface is configured as a remote observing port.
Procedure
- Run the display stp command to check whether the switch operates in VBST mode.
- If the switch operates in VBST mode, go to step 2.
- If the switch operates in another mode, the alarm has expired, and no action is required. Go to step 9.
- Run the display eth-trunk command to check whether an Eth-Trunk is configured on the switch.
- If so, go to step 3.
- If not, the alarm has expired, and no action is required. Go to step 9.
- Run the display stp interface eth-trunk interface-number command to check whether STP is enabled on the Eth-Trunk.
- If so, go to step 4.
- If not, the alarm has expired, and no action is required. Go to step 9.
- Run the display observe-port command to check whether the Eth-Trunk or an Eth-Trunk member interface is configured as a remote observing port.
- If so, go to step 5.
- If not, the alarm has expired, and no action is required. Go to step 9.
- Run the display device command to check the switch model.
- If the switch is an EI series fixed switch, the Eth-Trunk configuration conflicts with the remote observing port configuration. Go to step 6.
- If the switch is a non-EI series fixed switch, no action is required. Go to step 9.
- Delete conflicting configurations based on service requirements.
- Run the undo observe-port observe-port-index command to delete the remote observing port with conflicting configurations.
- Run the stp disable command to disable STP on the Eth-Trunk with conflicting configurations.
- Run the undo stp mode command to restore the operation mode of the spanning tree protocol to the default value, that is, MSTP mode.
- If the switch still reports an alarm after the conflicting configurations are deleted, go to step 8. Otherwise, go to step 9.
- Collect alarm and configuration information, and contact technical support personnel.
- End.
- VBST_1.3.6.1.4.1.2011.5.25.323.2.3 hwVbstPVNumExceeded
- VBST_1.3.6.1.4.1.2011.5.25.323.2.4 hwVbstPVNumResumed
- VBST_1.3.6.1.4.1.2011.5.25.323.2.7 hwVbstTrapInvalidPV
- VBST_1.3.6.1.4.1.2011.5.25.323.2.8 hwVbstTrunkPVNumExceeded
- VBST_1.3.6.1.4.1.2011.5.25.323.2.9 hwVbstTrunkPVNumResumed
- VBST_1.3.6.1.4.1.2011.5.25.323.2.10 hwVbstRspanCfgConflict