- Table of Contents
-
- 10-MPLS
- 01-HH3C-MPLSRSVP-MIB
- 02-HH3C-L2VPN-MIB
- 03-HH3C-L3VPN-MIB
- 04-HH3C-MPLS-LDP-MIB
- 05-HH3C-MPLSCRLSP-MIB
- 06-HH3C-MPLSEXT-MIB
- 07-HH3C-MPLSLSPV-MIB
- 08-HH3C-VSI-MIB
- 09-HH3C-MPLSTE-MIB
- 10-HH3C-MPLSSLSP-MIB
- 11-HH3C-MPLSPCE-MIB
- 12-MPLS-FRR-FACILITY-STD-MIB
- 13-MPLS-L3VPN-STD-MIB
- 14-MPLS-LDP-STD-MIB
- 15-MPLS-LSR-STD-MIB
- 16-PW-STD-MIB
- 17-TE-MIB
- Related Documents
-
Title | Size | Download |
---|---|---|
16-PW-STD-MIB | 63.15 KB |
PW-STD-MIB
About this MIB
Use this MIB to configure PW related settings.
MIB file name
rfc5601-pw-std.mib
Notifications
pwDown
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.2.1.10.246.0.1 |
PW down |
Error |
Major |
1.3.6.1.2.1.10.246.0.2 (pwUp) |
OFF |
Notification triggers
This notification is generated when the pwOperStatus object for one or more contiguous entries in the pwTable are about to enter the down(2) or lowerLayerDown(6) state from any other state, except for transition from the notPresent(5) state.
Possible reasons for this notification include the following:
The physical link of the PW went down.
The configuration at the two ends of the PW changed.
System impact
Traffic forwarding fails in the PW.
Status control
ON
CLI: Use the snmp-agent trap enable l2vpn pw-up-down command.
OFF
CLI: undo snmp-agent trap enable l2vpn pw-up-down command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.2.1.10.246.1.2.1.38 (pwOperStatus) |
PW operational status. |
pwIndex |
PwOperStatusTC |
up(1), down(2), testing(3), dormant(4), notPresent(5), lowerLayerDown(6) |
Recommended action
To resolve this issue:
Use the display l2vpn pw verbose command to view the Down Reasons field. Common reasons and solutions are as follows:
BFD session for PW down—The BFD session for PW detection is down. In this case, use the display bfd session command to view the reasons for the BFD session down, and then correct the BFD configuration or troubleshoot the physical link and link quality issues accordingly.
BGP RD was deleted—The BGP RD has been deleted. In this case, execute the route-distinguisher route-distinguisher command in auto-discovery cross-connect group view.
BGP RD was empty—No BGP RD is configured. In this case, execute the route-distinguisher route-distinguisher command in auto-discovery cross-connect group view.
Control word not match—The control word configuration on the two ends of the PW is inconsistent. In this case, configure the same control word setting on the two ends of the PW by using the control-word enable command in the PW class specified for the PW.
Encapsulation not match—The encapsulation types on the two ends of the PW are inconsistent. In this case, configure the same PW data encapsulation type on the two ends of the PW by using the pw-type command in the PW class specified for the PW.
LDP interface parameter not match—The LDP negotiation parameters on the two ends of the PW are inconsistent. In this case, configure the same VCCV CC type on the two ends of the PW by using the vccv cc command in the PW class specified for the PW. Or, configure the same CEM class settings for the CEM interfaces used by the two ends of the PW.
Non-existent remote LDP PW—The remote device has deleted the LDP PW. In this case, reconfigure the PW on the remote device.
Local AC Down—The local AC is down. In this case, verify that the configuration of the AC interface is correct and the state of the AC interface is up on the local device.
Local AC was non-existent—No local AC is configured. In this case, configure a local AC and associate it with the VSI.
MTU not match—The MTU configuration on the two ends of the PW is inconsistent. In this case, configure the same MTU on the two ends of the PW or use the mtu-negotiate disable command to disable PW MTU negotiation.
Remote AC Down—The remote AC is down. In this case, verify that the configuration of the AC interface is correct and the state of the AC interface is up on the remote device.
pwUp
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.2.1.10.246.0.2 |
PW up |
Recovery |
Warning |
N/A (N/A) |
OFF |
Notification triggers
This notification is generated when the pwOperStatus object for one or more contiguous entries in the pwTable are about to enter the up(1) state from some other state except the notPresent(5) state and given that the pwDown notification been issued for these entries.
System impact
The service carried on the PW will become available again.
Status control
ON
CLI: Use the snmp-agent trap enable l2vpn pw-up-down command.
OFF
CLI: undo snmp-agent trap enable l2vpn pw-up-down command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.2.1.10.246.1.2.1.38 (pwOperStatus) |
PW operational status. |
pwIndex |
PwOperStatusTC |
up(1), down(2), testing(3), dormant(4), notPresent(5), lowerLayerDown(6) |
Recommended action
No action is required.
pwDeleted
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.2.1.10.246.0.3 |
PW deleted |
Error |
Major |
N/A (N/A) |
OFF |
Notification triggers
This notification is generated when a PW is deleted.
Possible reasons for this notification include the following:
The peer was deleted in VSI view or the VSI was deleted manually.
The peer was deleted in cross-connect view or the cross-connect was deleted manually.
L2VPN or MPLS was disabled.
System impact
Traffic forwarding fails in the PW.
Status control
ON
CLI: Use the snmp-agent trap enable l2vpn pw-delete command.
OFF
CLI: Use the undo snmp-agent trap enable l2vpn pw-delete command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.2.1.10.246.1.2.1.2 (pwType) |
PW data encapsulation type. |
pwIndex |
IANAPwTypeTC |
other(0), frameRelayDlciMartiniMode(1), atmAal5SduVcc(2), atmTransparent(3), ethernetTagged(4), ethernet(5), hdlc(6), ppp(7), cem(8) -- Historic type, atmCellNto1Vcc(9), atmCellNto1Vpc(10), ipLayer2Transport(11), atmCell1to1Vcc(12), atmCell1to1Vpc(13), atmAal5PduVcc(14), frameRelayPortMode(15), cep(16),, e1Satop(17), t1Satop(18), e3Satop(19), t3Satop(20), basicCesPsn(21), basicTdmIp(22), tdmCasCesPsn(23), tdmCasTdmIp(24), frDlci(25), wildcard (32767) |
1.3.6.1.2.1.10.246.1.2.1.12 (pwID) |
PW ID. |
pwIndex |
PwIDType |
Unsigned32(1..4294967295) |
1.3.6.1.2.1.10.246.1.2.1.8 (pwPeerAddrType) |
Type of the peer IP address of the PW. |
pwIndex |
InetAddressType |
unknown(0), ipv4(1), ipv6(2), ipv4z(3), ipv6z(4), dns(16) |
1.3.6.1.2.1.10.246.1.2.1.9 (pwPeerAddr) |
Peer IP address of the PW. |
pwIndex |
InetAddress |
OCTET STRING (SIZE (0..255)) |
Recommended action
This is a normal operating message. If the related configuration was deleted mistakenly, restore the configuration as needed.