MPLS
- MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.23 hwBoardMplsPhpResLack
- MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.24 hwBoardMplsNonSupport
- MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.25 hwBoardMplsFwdResLack
- MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.26 hwBoardMplsFwdResLackResume
- MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.54 hwBoardMplsFwdResFull
MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.23 hwBoardMplsPhpResLack
Description
MPLS/4/PHP_RESLACK:OID [OID] PHP labels added failed because of insufficient resource. (Slot=[OCTET])
PHP labels failed to be added due to insufficient resources.
Attribute
Alarm ID | Alarm Severity | Alarm Type |
---|---|---|
1.3.6.1.4.1.2011.5.25.227.2.1.23 | Warning |
processingErrorAlarm(4) |
Possible Causes
Cause 1:
The ACL resources are insufficient.
Cause 2:
The MPLS PHP label specified exceeds the upper threshold.
Procedure
- Run the label advertise { explicit-null | non-null } command in the MPLS view of the switch directly connected to the local device to enable the egress switch to distribute a label without an explicit null label to the PHP node.
- Run the reset mpls ldp command in the user view of the local device to enable LDP globally.
MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.24 hwBoardMplsNonSupport
Description
MPLS/4/MPLSNONSUPPORT:OID [OID] The board does not support the MPLS function due to hardware limit, it will be reset. (Slot=[OCTET])
Due to hardware limitations, the device does not support MPLS, and will be restarted.
Attribute
Alarm ID | Alarm Severity | Alarm Type |
---|---|---|
1.3.6.1.4.1.2011.5.25.227.2.1.24 | Warning |
equipmentAlarm(5) |
Impact on the System
The stack system provides services normally; however, the device newly added to the stack will be restarted repeatedly.
Possible Causes
MPLS has been enabled on a stack, but the device newly added to the stack does not support MPLS.
Procedure
- Check whether MPLS needs to be enabled in the stack.
- If so, go to step 2.
- If not, go to step 3.
- Remove the newly added device from the stack, or replace it with an MPLS-capable device. Before device replacement, run the display device capability command to check whether the device supports MPLS.
- Run the undo mpls command in the system view to disable MPLS globally.
MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.25 hwBoardMplsFwdResLack
Description
MPLS/4/MPLS_LACK:OID [OID] The MPLS resource usage has reached or exceeded [GAUGE]%. (EntPhysicalIndex=[GAUGE], Slot=[OCTET], ResourceType=[INTEGER])
The usage of MPLS forwarding entries has reached or exceeded the upper threshold.
Attribute
Alarm ID | Alarm Severity | Alarm Type |
---|---|---|
1.3.6.1.4.1.2011.5.25.227.2.1.25 |
Warning |
equipmentAlarm(5) |
Parameters
Name | Meaning |
---|---|
OID |
Indicates the MIB object ID of the alarm. |
GAUGE |
Indicates the upper threshold of an alarm. |
EntPhysicalIndex |
Indicates the physical entity index. |
Slot |
Indicates the slot ID. |
ResourceType |
Indicates a resource type.
|
Impact on the System
When the usage of MPLS forwarding entries reaches 85%, the MPLS service cannot be normally transmitted. When the value of ResourceType is 777, the number of VXLAN VP entries exceeds the upper limit, causing abnormal VXLAN service transmission.
Procedure
- Run the display current-configuration command to check detailed device configuration. Delete unnecessary service configuration based on the value of ResourceType in the alarm information.
- If the value of ResourceType is 330, 777, or 331, check whether the configuration of VPLS, VXLAN, VLL, or PWE3 is redundant.
- If the value of ResourceType is 332, check whether the configuration of VPLS, VLL, PWE3, L3VPN, MPLS LDP, or MPLS TE is redundant.
- If the value of ResourceType is 333, check whether the configuration of MPLS LDP or MPLS TE is redundant.
- If the value of ResourceType is 578, check whether the configuration of VPLS or VXLAN is redundant.
- Check whether the alarm is cleared. If not, go to step 3.
- Collect alarm information and configuration information, and then contact technical support personnel.
MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.26 hwBoardMplsFwdResLackResume
Description
MPLS/4/MPLS_RESUME:OID [OID] The MPLS resource usage is restored to be lower than [GAUGE]%. (EntPhysicalIndex=[GAUGE], Slot=[OCTET], ResourceType=[INTEGER])
The usage of MPLS forwarding entries has fallen below the lower threshold.
Attribute
Alarm ID | Alarm Severity | Alarm Type |
---|---|---|
1.3.6.1.4.1.2011.5.25.227.2.1.26 | Warning |
equipmentAlarm(5) |
Parameters
Name | Meaning |
---|---|
OID | Indicates the MIB object ID of the alarm. |
GAUGE | Indicates the lower threshold of an alarm. |
EntPhysicalIndex | Indicates the physical entity index. |
Slot | Indicates the slot ID. |
ResourceType | Indicates a resource type.
|
MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.54 hwBoardMplsFwdResFull
Description
MPLS/4/MPLSRESOURCEFULL: OID [OID] The MPLS entry resource has been exhausted. (Slot=[OCTET], ResourceType=[INTEGER])
The MPLS forwarding entry resources have been exhausted.
Attribute
Alarm ID | Alarm Severity | Alarm Type |
---|---|---|
1.3.6.1.4.1.2011.5.25.227.2.1.54 | Warning |
environmentalAlarm(6) |
Parameters
Name | Meaning |
---|---|
OID | Indicates the MIB object ID of the alarm. |
Slot | Slot ID. |
ResourceType | Resource type.
|
Impact on the System
If the MPLS forwarding entry resources are exhausted, the MPLS and VPN service traffic fails to be forwarded.
Possible Causes
The usage of the MPLS forwarding entry resources reaches or exceeds the upper limit.
Procedure
- Run the display current-configuration command to check detailed device configuration. Delete unnecessary service configuration based on the value of ResourceType in the alarm information.
- If the value of ResourceType is 331, check whether the configuration of VPLS, VLL, PWE3, or VXLAN is redundant.
- If the value of ResourceType is 332, check whether the configuration of VPLS, VLL, PWE3, L3VPN, MPLS LDP, or MPLS TE is redundant.
- If the value of ResourceType is 333, check whether the configuration of MPLS LDP or MPLS TE is redundant.
- Check whether the clear alarm MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.26 hwBoardMplsFwdResLackResume is reported. If not, go to step 3.
- Collect alarm information and configuration information, and then contact technical support personnel.
- MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.23 hwBoardMplsPhpResLack
- MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.24 hwBoardMplsNonSupport
- MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.25 hwBoardMplsFwdResLack
- MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.26 hwBoardMplsFwdResLackResume
- MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.54 hwBoardMplsFwdResFull