No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Enterprise
Worldwide
Huawei Global - English
Search
Support Documentation
Alarm Handling
S1700, S2720, S5700, and S6700 V200R019C10

This document provides the explanations, causes, and recommended actions of alarms on the product.

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
L2V

L2V

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.7 hwVplsVcDeleted

Description

L2V/4/VPLSVC_DEL_T:OID [oid] The VPLS VC has been deleted. (VsiName=[STRING], PwId=[GAUGE], RemoteIp=[IPADDR], PwType=[INTEGER])

The VPLS VC was deleted.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.119.1.2.7

Warning

 qualityOfServiceAlarm (3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VsiName

Name of the VSI

PwId

ID of the PW

RemoteIp

IP address of the remote peer

PwType
Type of the PW. The values are as follows:
  1. normal
  2. other

Impact on the System

If the VPLS VC is Up, services on it are interrupted.

Possible Causes

Cause 1:

The peer was deleted in the VSI view, or the VSI was manually deleted.

Cause 2:

L2VPN or MPLS was disabled.

Procedure

  1. This alarm is informational only, and no action is required.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.1_hwVplsVcDown

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.1 hwVplsVcDown

Description

L2V/2/VPLSVC_DWN_ME_T:OID [oid] The status of the VPLS VC turned DOWN. (VsiName=[STRING], PwId=[GAUGE], RemoteIp=[IPADDR], PwType=[INTEGER], HWL2VpnStateChangeReason=[INTEGER], SysUpTime=[TIMETICK], TunnelPolicyName=[STRING], TunnelType=[INTEGER], SessionTunnelID=[GAUGE])

The VPLS VC changed from Up to Down.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.119.1.2.1

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VsiName

Indicates the name of a VSI.

PwId

Indicates the ID of a PW.

RemoteIp

Indicates the IP address of the remote peer.

PwType
Indicates the type of a PW:
  • 1: normal
  • 2: other

HWL2VpnStateChangeReason

Indicates the cause of the VC status change.

SysUpTime

Indicates the time for system startup.

TunnelPolicyName

Indicates the name of a tunnel policy.

TunnelType

Indicates the type of a tunnel.

SessionTunnelId

Indicates the ID of a tunnel.

Impact on the System

VPLS Services will be interrupted and the traffic will be blocked.

Possible Causes

The status of the physical link or the configurations on both ends of a link was changed.

Procedure

  1. Run the display vsi name vsi-name verbose command to check the VSIs on the local device and the peer device. In the case of the LDP VSI, check the VSIs with the same VSI ID. In the case of the BGP VSI, check the VSIs with the same VPN target.

    • If the AC interface (in the field of Interface Name in the command output) is Down, go to Step 2.
    • If the status of the VSI is Admin Down, go to Step 3.
    • If the MTUs or the encapsulation types on the local and peer devices are inconsistent, go to Step 4.
    • If the PW does not exist, go to Step 5.
    • If the PW is Down, go to Step 12.

  2. Restore the AC interface to Up, and check whether the alarm is cleared.

    • If so, go to Step 14.
    • If not, go to Step 1.

  3. Run the undo shutdown command in the VSI view to check whether the alarm is cleared.

    • If so, go to Step 14.
    • If not, go to Step 1.

  4. Run the mtu mtu command in the VSI view to set the MTUs of the VSIs on both ends to be consistent. Run the encapsulation command to set the encapsulation types on both ends to be consistent. Then, check whether the alarm is cleared.

    • If so, go to Step 14.
    • If not, go to Step 1.

  5. Run the display vsi name vsi-name verbose command to check the PW signaling.

    • If it is LDP, go to Step 6.
    • If it is BGP, go to Step 7.

  6. Run the display vsi name vsi-name verbose command to check whether the session on the VSI peer is Up.

    • If not, go to Step 8.
    • If so, go to Step 9.

  7. Run the display bgp peer command to check whether the BGP connection with the peer in the VPLS address family is established.

    • If so, go to Step 13.
    • If not, go to Step 10.

  8. Run the display mpls ldp session command to check whether the session of the peer is operational.

    • If so, go to Step 13.
    • If not, go to Step 11.

  9. Run the display vsi name vsi-name verbose command to check whether the session of the VSI peer has the tunnel ID.

    • If so, go to Step 12.
    • If not, go to Step 11.

  10. Configure the BGP connection to be established, and check whether the alarm is cleared.

    • If so, go to Step 14.
    • If not, go to Step 13.

  11. Check whether the interface on the public network is Down. Set the interface on the public network to be Up, and then check the LDP configuration. Run the display mpls ldp session command to check that the session becomes operational, and then check whether the alarm is cleared.

    • If so, go to Step 14.
    • If not, go to Step 13.

  12. Check the configurations of the routes and public network interfaces one by one. If the configuration is correct, go to Step 14. If the configuration is incorrect, restore the configuration and check whether the alarm is cleared.

    • If so, go to Step 14.
    • If not, go to Step 13.

  13. Collect alarm information and configuration information, and then contact technical support personnel.
  14. End.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.2 hwVplsVcUp

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.2 hwVplsVcUp

Description

L2V/2/VPLSVC_UP_ME_T:OID [oid] The status of the VPLS VC turned UP. (VsiName=[STRING], PwId=[GAUGE], RemoteIp=[IPADDR], PwType=[INTEGER], HWL2VpnStateChangeReason=[INTEGER], SysUpTime=[TIMETICK], TunnelPolicyName=[STRING])

The VPLS VC changed from Down to Up.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.119.1.2.2

Major

other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VsiName

Indicates the name of a VSI.

PwId

Indicates the ID of a PW.

RemoteIp

Indicates the IP address of the remote peer.

PwType
Indicates the type of a PW:
  • 1: normal
  • 2: other

HWL2VpnStateChangeReason

Indicates the cause of the VC status change. For details, refer to hwVplsStateChangeReason in the appendix of HUAWEI-VPLS-EXT-MIB.

SysUpTime

Indicates the time for system startup.

TunnelPolicyName

Indicates the name of a tunnel policy.

Impact on the System

Services will be recovered.

Possible Causes

The VPLS VC changed from Down to Up.

Procedure

  1. This trap message is informational only, and no action is required.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.1 hwVplsVcDown

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.8 hwVplsVcStatusChange

Description

L2V/4/VPLSVC_STATUS_CHANGE_T:OID [OID] The status of the VPLS VC changed. (VsiName=[STRING], PwId=[GAUGE], RemoteIp=[IPADDR], HWL2VpnStateChangeReason=[INTEGER], HWPwState=[INTEGER], HWPwWorkingState=[INTEGER], SysUpTime=[TIMETICK])

The VPLS VC status changes.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.119.1.2.8

Warning

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VsiName

Indicates the name of a VSI.

PwId

Indicates the ID of a PW.

RemoteIp

Indicates the IP address of the remote peer.

HWL2VpnStateChangeReason

Indicates the cause of the VC status change. For details, refer to hwVplsStateChangeReason in the appendix of HUAWEI-VPLS-EXT-MIB.

HWPwState
Indicates the PW status, which can be:
  • Up
  • Down

HWPwWorkingState
Indicates the PW working status, which can be:
  • Master
  • Backup

SysUpTime

Indicates the time for system startup.

Impact on the System

None

Possible Causes

Cause 1:

The status of the VPLS VC changed from Up to Down.

Cause 2:

The status of the VPLS VC changed from Down to Up.

Cause 3:

The working status of the VPLS VC changed from Master to Backup.

Cause 4:

The working status of the VPLS VC changed from Backup to Master.

Procedure

  • This trap message is informational only, and no action is required.

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.6 hwVplsVsiDeleted

Description

L2V/4/VPLS_DEL_T:OID [oid] The VPLS VSI has been deleted. (VsiName=[STRING], VsiId=[GAUGE])

The VPLS VSI was deleted.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.119.1.2.6

Warning

 qualityOfServiceAlarm (3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VsiName

Name of the VSI

VsiId

ID of the VSI

Impact on the System

VPLS services on the Up VCs in the VSI are interrupted.

Possible Causes

Cause 1:

The VSI was manually deleted.

Cause 2:

L2VPN or MPLS was disabled.

Procedure

  1. This alarm is informational only, and no action is required.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.3_hwVplsVsiDown

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.3 hwVplsVsiDown

Description

L2V/2/VPLSVSI_DWN_T:OID [oid] The status of the VPLS VSI turned DOWN. (VsiName=[STRING], InterfaceIndex=[INTEGER], VsiId=[GAUGE], HWL2VpnStateChangeReason=[INTEGER], VsiStatus=[INTEGER], InterfaceName=[STRING])

The VPLS VSI changed from Up to Down.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.119.1.2.3

Major

 qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VsiName

Indicates the name of a VSI.

InterfaceIndex

Indicates the interface index.

VsiId

Indicates the ID of a VSI.

HWL2VpnStateChangeReason

Indicates the cause of the VSI status change. For details, refer to hwVplsStateChangeReason in the appendix of HUAWEI-VPLS-EXT-MIB.

VsiStatus
Indicates the status of the VSI:
  • 1: VSI Up
  • 2: VSI Down
  • 3: VSI Admin down

InterfaceName

Indicates the interface name.

Impact on the System

VPLS Services will be interrupted and the traffic will be blocked.

Possible Causes

The status of the physical link or the VPLS configuration of any VSI device was changed.

Procedure

  1. Run the display vsi name vsi-name verbose command to check the VSIs on the local device and the peer device. In the case of the LDP VSI, check the VSIs with the same VSI ID. In the case of the BGP VSI, check the VSIs with the same VPN target.

    • If the AC interface (in the field of Interface Name in the command output) is Down, go to Step 2.
    • If the status of the VSI is Admin Down, go to Step 3.
    • If the MTUs or the encapsulation types on the local and peer devices are inconsistent, go to Step 4.
    • If the PW does not exist, go to Step 5.
    • If the PW is Down, go to Step 12.

  2. Restore the AC interface to Up, and check whether the alarm is cleared.

    • If so, go to Step 14.
    • If not, go to Step 1.

  3. Run the undo shutdown command in the VSI view to check whether the alarm is cleared.

    • If so, go to Step 14.
    • If not, go to Step 1.

  4. Run the mtu mtu command in the VSI view to set the MTUs of the VSIs on both ends to be consistent. Run the encapsulation command to set the encapsulation types on both ends to be consistent. Then, check whether the alarm is cleared.

    • If the alarm is cleared, go to Step 14.
    • If the alarm is not cleared, go to Step 1.

  5. Run the display vsi name vsi-name verbose command to check the PW signaling.

    • If it is LDP, go to Step 6.
    • If it is BGP, go to Step 7.

  6. Run the display vsi name vsi-name verbose command to check whether the session on the VSI peer is Up.

    • If not, go to Step 8.
    • If so, go to Step 9.

  7. Run the display bgp peer command to check whether the BGP peer is established.

    • If so, go to Step 13.
    • If not, go to Step 10.

  8. Run the display mpls ldp session command to check whether the session of the peer is operational.

    • If so, go to Step 13.
    • If not, go to Step 11.

  9. Run the display vsi name vsi-name verbose command to check whether the session of the VSI peer has the tunnel ID.

    • If so, go to Step 12.
    • If not, go to Step 11.

  10. Configure the BGP connection to be established, and check whether the alarm is cleared.

    • If so, go to Step 14.
    • If not, go to Step 13.

  11. Check whether the interface on the public network is Down. Set the interface on the public network to be Up, and then change the LDP configuration. Run the display mpls ldp session command to check that the session becomes operational, and then check whether the alarm is cleared.

    • If so, go to Step 14.
    • If not, go to Step 13.

  12. Repeat the preceding steps on the remote device. Then, check whether the alarm is cleared.

    • If so, go to Step 14.
    • If not, go to Step 13.

  13. Collect alarm information and configuration information, and then contact technical support personnel.
  14. End.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.4 hwVplsVsiUp

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.4 hwVplsVsiUp

Description

L2V/2/VPLSVSI_UP_T:OID [oid] The status of the VPLS VSI turned UP. (VsiName=[STRING], InterfaceIndex=[INTEGER], VsiId=[GAUGE], HWL2VpnStateChangeReason=[INTEGER], VsiStatus=[INTEGER], InterfaceName=[STRING])

The VPLS VSI changed from Down to Up.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.119.1.2.4

Major

 other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VsiName

Indicates the name of a VSI.

InterfaceIndex

Indicates the interface index.

VsiId

Indicates the ID of a VSI.

HWL2VpnStateChangeReason

Indicates the cause of the VSI status change. For details, refer to hwVplsStateChangeReason in the appendix of HUAWEI-VPLS-EXT-MIB.

VsiStatus
Indicates the status of the VSI:
  • 1: Up
  • 2: Down
  • 3: Admin Down

InterfaceName

Indicates the interface name.

Impact on the System

Services will be recovered.

Possible Causes

The VPLS VSI changed from Down to Up.

Procedure

  1. This trap message is informational only, and no action is required.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.3 hwVplsVsiDown

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.5 hwVplsVcBackup

Description

L2V/1/VPLSVC_BACKUP_T:OID [oid] The status of the VPLS VC turned BACKUP. (VsiName=[STRING], PwId=[GAUGE], RemoteIp=[IPADDR], PwType=[INTEGER], HWL2VpnStateChangeReason=[INTEGER], SysUpTime=[TIMETICK])

The VPLS VC turned to the Backup state.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.119.1.2.5

Critical

 other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VsiName

Name of a VSI.

PwId

ID of a PW.

RemoteIp

IP address of the remote peer.

PwType
Type of a PW:
  • 1: normal
  • 2: other

HWL2VpnStateChangeReason

Cause of the VC status change. For details, refer to hwVplsStateChangeReason in the appendix of HUAWEI-VPLS-EXT-MIB.

SysUpTime

Time for system startup.

Impact on the System

If the VRRP works normally, packet loss will occur within a short period of time when the traffic is switched from the master VRRP to the backup VRRP. Services will not be affected when the traffic is switched back from the backup VRRP to the master VRRP.

Possible Causes

1.

The PW-bound VRRP protection group turned to the non-master state.

2.

The PW-bound VRRP protection group turned to the backup state.

3.

The interface board configured with the PW-bound VRRP protection group was pulled out.

Procedure

  1. View user logs to check the causes of the VRRP change. You can perform operations according to the specific cause.

    • If the cause is priority calculation, go to Step 6.
    • If the cause is that the MASTER_DOWN timer expired, go to Step 2.
    • If the cause is the change of the BFD session status, go to Step 2.
    • If the cause is the change of the interface status, go to Step 2.
    • If the cause is admin-vrrp DROVE, go to Step 6.

  2. Run the display vrrp command to check the status of the VRRP backup group on the former master switch.

    • If the VRRP backup group is in the Initialize state, it indicates that the former switch is faulty. Locate the cause of the fault and restore the master switch. Go to Step 8.
    • If the VRRP backup group is in the Backup state, go to Step 6.
    • If the VRRP backup group is in the Master state, go to Step 3.

  3. Check whether the master link is faulty.

    • If BFD is configured, go to Step 4.
    • If BFD is not configured, go to Step 5.

  4. Run the display vrrp command to check the status of the BFD session.

    • If the BFD session is Down, it indicates that the former master link is faulty. Locate the cause of the fault and restore the master link. Go to Step 8.
    • If the BFD session is Up, go to Step 7.

  5. Run the display vrrp [ interface interface-type interface-number ] [virtual-router-id ] statistics command to check whether the VRRP packets are normally forwarded.

    • If not, it indicates that the link is faulty. Locate the cause of the fault and restore the link. Go to Step 8.
    • If so, go to Step 7.

  6. On the former master switch and backup switch, run the display vrrp command to check whether the configured priority of the VRRP is consistent with the running priority.

    • If not, it indicates that the link monitored through VRRP is faulty. Locate the cause of the fault and restore the monitored link. Go to Step 8.
    • If so, go to Step 7.

  7. Collect alarm information and configuration information, and then contact technical support personnel.
  8. End.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.1 hwVplsVcDown

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.2 hwVplsVcUp

L2V_1.3.6.1.4.1.2011.5.25.119.2.2.1 hwKompellaVcDown

Description

L2V/2/BGPVC_DWN_T:OID [oid] The status of the Kompella VC turned DOWN. (VcVpnName=[STRING], CeId=[GAUGE], InterfaceIndex=[INTEGER], RemoteCeId=[GAUGE], SecondaryVc=[INTEGER], HWL2VpnStateChangeReason=[INTEGER], PeerAddress=[IPADDR], TunnelPolicyName=[STRING], ActiveState=[INTEGER])

A Kompella VC became Down.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.119.2.2.1

Major

 processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VcVpnName

Indicates the VPN name.

CeId

Indicates the ID of the local CE.

InterfaceIndex

Indicates the interface index.

RemoteCeId

Indicates the ID of the remote CE.

SecondaryVc

Indicates the backup VC.

HWL2VpnStateChangeReason

Indicates the cause of the VC status change.

PeerAddress

Indicates the IP address of a peer.

TunnelPolicyName

Indicates the name of a tunnel policy.

ActiveState

Indicates the status of Active.

Impact on the System

Services will be interrupted and the traffic will be blocked.

Possible Causes

A Kompella VC became Down.

Procedure

  1. Run the display mpls l2vpn connection interface interface-type interface-number command to view the conn-type of the VC.

    • If the conn-type is unknown, go to Step 2.
    • If the conn-type is local, go to Step 14.
    • If the conn-type is remote, go to Step 5.

  2. Run the display bgp l2vpn peer command to check whether the BGP peer is established.

    • If so, go to Step 4.
    • If not, check whether the BGP configuration is correct and the trap recovers.
      • If so, go to Step 17.
      • If not, go to Step 16.

  3. Check and restore the Kompella configuration on the peer.

    • If so, go to Step 5.
    • If not, go to Step 17.

  4. Check the status of the local VC, including the physical status of the local AC interface, link status of the AC interface, status of the manual fault, and status of the selected tunnel.

    • If the local VC is Down, go to Step 6.
    • If the local VC is Up, go to Step 12.

  5. Run the display interface interface-type interface-number command to view the physical status of the interface, and change the physical status of the interface to Up.

    • If so, go to Step 7.
    • If not, go to Step 16.

  6. Check information about the tunnel of the VC.

    • If the tunnel does not exist, go to Step 8.
    • If the tunnel exists, go to Step 9.

  7. Run the display tunnel-info all command to check information about the tunnel connected to the peer. Modify the configuration on the outbound interface in a public network and restore the tunnel connected to the peer.

    • If so, go to Step 9.
    • If not, go to Step 16.

  8. Check the OAM status of the AC.

    • If it is Down, go to Step 10.
    • If it is Up, go to Step 11.

  9. Run the display interface interface-type interface-number command to check the link status of the interface. Restore the link status of the interface to Up.

    • If so, go to Step 11.
    • If not, go to Step 16.

  10. Check whether the manual fault is set or not. If it is set, cancel the setting on the AC interface.

    • If so, go to Step 12.
    • If not, go to Step 16.

  11. Run the display mpls l2vpn connection interface interface-type interface-number command to check the status of the remote VC.

    • If it is Down, go to Step 13.
    • If it is Up, go to Step 17.

  12. Check and restore the status of the Kompella VC on the peer.

    • If so, go to Step 17.
    • If not, go to Step 16.

  13. Check the physical status of the AC interface.

    • If it is Down, go to Step 14.
    • If it is Up, go to Step 15.

  14. Restore the physical status of the interface to Up.

    • If so, go to Step 15.
    • If not, go to Step 16.

  15. Check the physical status of the local interface that is connected to the peer, and restore the physical status to Up.

    • If so, go to Step 17.
    • If not, go to Step 16.

  16. Collect alarm information and configuration information, and then contact technical support personnel.
  17. End.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.2.2.2 hwKompellaVcUp

L2V_1.3.6.1.4.1.2011.5.25.119.2.2.2 hwKompellaVcUp

Description

L2V/2/BGPVC_UP_T:OID [oid] The status of the Kompella VC turned UP. (VcVpnName=[STRING], CeId=[GAUGE], InterfaceIndex=[INTEGER], RemoteCeId=[GAUGE], SecondaryVc=[INTEGER], HWL2VpnStateChangeReason=[INTEGER], PeerAddress=[IPADDR], TunnelPolicyName=[string], ActiveState=[INTEGER])

A Kompella VC became Up.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.119.2.2.2

Major

 other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VcVpnName

Indicates the VPN name.

CeId

Indicates the ID of the local CE.

InterfaceIndex

Indicates the interface index.

RemoteCeId

Indicates the ID of the remote CE.

SecondaryVc

Indicates the backup VC.

HWL2VpnStateChangeReason

Indicates the cause of the VC status change.

PeerAddress

Indicates the IP address of a peer.

TunnelPolicyName

Indicates the name of a tunnel policy.

ActiveState

Indicates the status of active.

Impact on the System

The service will be recovered.

Possible Causes

A Kompella VC became Up.

Procedure

  1. This trap message is informational only, and no action is required.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.2.2.1 hwKompellaVcDown

L2V_1.3.6.1.4.1.2011.5.25.119.2.2.3 hwKompellaSwitchWtoP

Description

L2V/2/BGPVC_W2P_T:OID [oid] The status of the Kompella VC turned protecting from working. (VcVpnName=[STRING], CeId=[GAUGE], InterfaceIndex=[INTEGER], RemoteCeId=[GAUGE],CtrlWord=[INTEGER], SecondaryVcRemoteCeId=[GAUGE], HWL2VpnStateChangeReason=[INTEGER])

A Kompella VC was changed from working state to protection state.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.119.2.2.3

Major

processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VcVpnName

Indicates the VPN name.

CeId

Indicates the ID of the local CE.

InterfaceIndex

Indicates the interface index.

RemoteCeId

Indicates the ID of the remote CE.

CtrlWord
Indicates whether the control word is enabled:
  • 1: indicates that the control word is enabled.
  • 2: indicates that the control word is disabled.

SecondaryVcRemoteCeId

Indicates the ID of the remote CE whose VC is in the Protection state.

HWL2VpnStateChangeReason

Indicates the cause of the VC status change. For details, refer to hwKompellaVcStateChangeReason in the appendix of HUAWEI-KOMPELLA-MIB.

Impact on the System

The switchover between the primary VC and the backup VC has no impact on services.

Possible Causes

A Kompella VC was changed from a working link to a protection link.

Procedure

  1. Refer to the solution to the hwKompellaVcDown trap. Then, check whether the fault is rectified.

    • If so, go to Step 3.
    • If not, go to Step 2.

  2. Collect alarm information and configuration information, and then contact technical support personnel.
  3. End.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.2.2.4 hwKompellaSwitchPtoW

L2V_1.3.6.1.4.1.2011.5.25.119.2.2.4 hwKompellaSwitchPtoW

Description

L2V/2/BGPVC_P2W_T:OID [oid] The status of the Kompella VC turned working from protecting. (VcVpnName=[STRING], CeId=[GAUGE], InterfaceIndex=[INTEGER], RemoteCeId=[GAUGE], CtrlWord=[INTEGER], PrimaryVcRemoteCeId=[GAUGEs], HWL2VpnStateChangeReason=[INTEGER])

A Kompella VC was changed from protection state to working state.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.119.2.2.4

Major

 processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VcVpnName

Indicates the VPN name.

CeId

Indicates the ID of the local CE.

InterfaceIndex

Indicates the interface index.

RemoteCeId

Indicates the ID of the remote CE.

CtrlWord
Indicates whether the control word is enabled:
  • 1: indicates that the control word is enabled.
  • 2: indicates that the control word is disabled.

PrimaryVcRemoteCeId

Indicates the ID of the remote CE whose VC is in the Working state.

HWL2VpnStateChangeReason

Indicates the cause of the VC status change. For details, refer to hwKompellaVcStateChangeReason in the appendix of HUAWEI-KOMPELLA-MIB.

Impact on the System

The switchover between the primary VC and the backup VC has no impact on services.

Possible Causes

A Kompella VC was changed from a protection link to a working link.

Procedure

  1. The trap message is informational only, and no action is required.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.2.2.3 hwKompellaSwitchWtoP

L2V_1.3.6.1.4.1.2011.5.25.119.3.2.1 hwCCCVcDown

Description

L2V/3/CCCVC_DWN_T:OID [oid] The status of the CCC VC turned DOWN. (CccName=[STRING], InterfaceIndex=[INTEGER], InterfaceIndex=[INTEGER], HWL2VpnStateChangeReason=[INTEGER], InterfaceName=[STRING])

The alarm was generated when the CCC VC was Down.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.119.3.2.1

Minor

 processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

CccName

Name of the CCC connection

InterfaceIndex

Index of the interface used as the table index

InterfaceIndex

Index of the interface reported to the network management system as a parameter

HWL2VpnStateChangeReason

Cause of the VC status change. For details, see "hwCCCVcStateChangeReason" in the appendix of HUAWEI-CCC-MIB.

InterfaceName

Name of the interface

Impact on the System

Services will be interrupted and traffic cannot be forwarded properly.

Possible Causes

1.

The inbound or outbound interface of CCC services became Down.

2.

MPLS or MPLS L2VPN was disabled.

3.

The IP address of the outbound interface of CCC services was deleted or changed into an IP address in a different segment.

Procedure

  1. Check whether the current configuration is the same as the original configuration. For example, check whether MPLS is enabled globally, or whether MPLS is enabled on the CCC outbound interface.

    • If so, go to Step 3.
    • If not, go to Step 2

  2. Restore the original configuration. Then, check whether the alarm is cleared.

    • If the alarm is cleared, go to Step 9.
    • If the alarm is not cleared, go to Step 3.

  3. Run the display vll ccc ccc-name command to check the status of the two interfaces of the CCC VC.

    • If either interface is Down or both interfaces are Down, go to Step 4.
    • If both interfaces are Up, go to Step 8.
    • If one interface goes UP, and the IP address of next hop of the other interface are displayed, go to Step 5.

  4. View the cause that the interface is Down and restore the interface to the Up status. Then, check whether the alarm is cleared.

    • If cleared, go to Step 9.
    • If persists, go to Step 8.

  5. Run the display ip routing-table command to check whether the IP address is reachable.

    • If so, go to Step 8.
    • If not, go to Step 6

  6. Run the display ip interface brief command to check whether there are addresses that are in the same segment with the IP address.

    • If so, go to Step 4.
    • If not, it indicates that the outbound interface address is deleted or changed. In this case, go to Step 7.

  7. Enter the view of the outbound interface and reconfigure an IP address in consistent with the original configuration. Then, check whether the alarm is cleared.

    • If the alarm is cleared, go to Step 9.
    • If the alarm is not cleared, go to Step 8.

  8. Collect alarm information and configuration information, and then contact technical support personnel.
  9. End.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.3.2.2 hwCCCVcUp

L2V_1.3.6.1.4.1.2011.5.25.119.3.2.2 hwCCCVcUp

Description

L2V/3/CCCVC_UP_T:OID [oid] The status of the CCC VC turned UP. (CccName=[STRING], InterfaceIndex=[INTEGER], InterfaceIndex=[INTEGER], HWL2VpnStateChangeReason=[INTEGER], InterfaceName=[STRING])

The trap was generated when the CCC VC was Up.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.119.3.2.2

Minor

 other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

CccName

Indicates the name of the CCC connection.

InterfaceIndex

Index of the interface used as the table index.

InterfaceIndex

Index of the interface reported to the network management system as a parameter.

HWL2VpnStateChangeReason

Indicates the cause of the VC status change. For details, refer to hwCCCVcStateChangeReason in the appendix of HUAWEI-CCC-MIB.

InterfaceName

Indicates the interface name.

Impact on the System

The CCC service will be recovered.

Possible Causes

1.

The trap was generated when a VC became Up.

2.

The configuration was modified. For example, the next hop address of the CCC was changed.

Procedure

  1. Check whether the service is restored.

    • If so, it indicates that the trap message is informational only, and no action is required.
    • If not, go to Step 2.

  2. Check whether the current configuration is the same as the original configuration. For example, check whether the next hop address of the CCC is the same as the address of the peer interface of the outbound interface.

    • If so, go to Step 4.
    • If not, go to Step 3.

  3. Restore the original configuration and check whether the alarm is cleared.

    • If the alarm is cleared, go to Step 5.
    • If the trap is no cleared, go to Step 4.

  4. Collect alarm information and configuration information, and then contact technical support personnel.
  5. End.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.3.2.1 hwCCCVcDown

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.1 hwPWVcSwitchWtoP

Description

L2V/4/PWE3VC_W2P_T:OID [oid] The status of the PWE3 VC turned protecting from working. ( VcId=[GAUGE], VcType=[INTEGER], CtrlWord=[INTEGER], SecondaryPwId=[GAUGE], HWL2VpnStateChangeReason=[INTEGER], InterfaceName=[STRING])

Indicates that a PW changes from the primary state to the secondary state.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.119.4.1.2.1

Warning

 other(1)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
VcId Indicates the ID of a VC.
VcType

Indicates the type of a VC:

  • 0: Initial value
  • 1: FR
  • 2: ATM AAL5
  • 3: ATM cell relay
  • 4: VLAN
  • 5: Ethernet
  • 6: HDLC
  • 7: PPP
  • 9: ATM cell VCC
  • 10: ATM cell VPC
  • 11: IP-layer 2 (used for heterogeneous IP-interworking between Huawei devices and non-Huawei devices)
  • 12: ATM, 1-to-1 VCC cell mode
  • 13: ATM, 1-to-1 VPC cell mode
  • 14: ATM, AAL5 PDU VCC Transport
  • 64: Heterogeneous IP-interworking
CtrlWord

Indicates whether the control word is enabled:

  • 1: enabled
  • 2: disabled
SecondaryPwId Indicates the remote CE ID of the VC in the Protecting state.
HWL2VpnStateChangeReason Indicates the cause for the VC status change. For details, refer to hwPwStateChangeReason in the appendix of HUAWEI-PWE3-MIB.
InterfaceName Indicates the interface name.

Impact on the System

Packet loss in millisecond may occur in the switching process. The packet loss, however, affects little to the PWE3 service.

Possible Causes

The VLL service is switched from the primary PW to the secondary PW.

Procedure

  1. Rectify the fault according to the solution to the hwPWVcDown trap. Then, check whether the fault is rectified.

    • If so, go to Step 3.
    • If not, go to Step 2.

  2. Collect alarm information and configuration information, and then contact technical support personnel.
  3. End.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.2 hwPWVcSwitchPtoW

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.2 hwPWVcSwitchPtoW

Description

L2V/4/PWE3VC_P2W_T:OID [oid] The status of the PWE3 VC turned working from protecting. (VcId=[GAUGE], VcType=[INTEGER], CtrlWord=[INTEGER], PrimaryPwId=[GAUGE], HWL2VpnStateChangeReason=[INTEGER], InterfaceName=[STRING])

Indicates that a PW changes from the secondary state to the primary state.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.119.4.1.2.2

Warning

 other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VcId

Indicates the ID of a VC.

VcType
Indicates the type of a VC:
  • 0: Initial value
  • 1: FR
  • 2: ATM AAL5
  • 3: ATM cell relay
  • 4: VLAN
  • 5: Ethernet
  • 6: HDLC
  • 7: PPP
  • 9: ATM cell VCC
  • 10: ATM cell VPC
  • 11: IP-layer 2 (used for heterogeneous IP-interworking between Huawei devices and non-Huawei devices)
  • 12: ATM, 1-to-1 VCC cell mode
  • 13: ATM, 1-to-1 VPC cell mode
  • 14: ATM, AAL5 PDU VCC TRANSPORT
  • 64: Heterogeneous IP-interworking

CtrlWord
Indicates whether the control word is enabled:
  • 1: enabled
  • 2: disabled

PrimaryPwId

Indicates the remote CE ID of the VC in the Working state.

HWL2VpnStateChangeReason

Indicates the cause for the VC status change. For details, refer to hwPwStateChangeReason in the appendix of HUAWEI-PWE3-MIB.

InterfaceName

Indicates the interface name.

Impact on the System

Packet loss in millisecond may occur in the switching process. The packet loss, however, affects little to the PWE3 service.

Possible Causes

The primary PW is rectified, and the VLL service is switched from the secondary PW to the primary PW.

Procedure

  1. This trap message is informational only, and no action is required.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.1 hwPWVcSwitchWtoP

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.5 hwPWVcDeleted

Description

L2V/4/PWE3VC_DEL_T:OID [oid] The PWE3 VC has been deleted. (VcId=[GAUGE], VcType=[INTEGER], PeerAddress=[IPADDR], InterfaceIndex=[INTEGER], VcInboundLabel=[GAUGE], VcOutboundLabel=[GAUGE], SecondaryPw=[INTEGER], InterfaceName=[STRING], SwitchVcId=[GAUGE])

The LDP VC was deleted.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.119.4.1.2.5

Warning

 qualityOfServiceAlarm (3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VcId

ID of the VC

VcType
Type of the VC. The values are as follows:
  • 0: initial value
  • 1: FR
  • 2: ATM AAL5
  • 3: ATM cell relay
  • 4: VLAN
  • 5: Ethernet
  • 6: HDLC
  • 7: PPP
  • 9: ATM cell VCC
  • 10: ATM cell VPC
  • 11: IP-layer 2 (used for heterogeneous IP-interworking between Huawei devices and non-Huawei devices)
  • 12: ATM, 1-to-1 VCC cell mode
  • 13: ATM, 1-to-1 VPC cell mode
  • 14: ATM, AAL5 PDU VCC transport
  • 64: heterogeneous interworking

PeerAddress

IP address of the peer

InterfaceIndex

Index of the interface

VcInboundLabel

Inbound label of the VC

VcOutboundLabel

Outbound label of the VC

SecondaryPw
Whether the PW is a secondary PW:
  • 1: The PW is a secondary PW.
  • 2: The PW is not a secondary PW.

InterfaceName

Name of the interface

SwitchVcId

ID of the switching VC

Impact on the System

PWE3 services are interrupted.

Possible Causes

Cause 1:

The LDP VC was manually deleted.

Cause 2:

L2VPN or MPLS was disabled.

Procedure

  1. This alarm is informational only, and no action is required.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.3_hwPWVcDown

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.3 hwPWVcDown

Description

L2V/2/PWE3VC_DWN_ME_T:OID [oid] The status of the PWE3 VC turned DOWN. (VcId=[GAUGE], VcType=[INTEGER], PeerAddress=[IPADDR], InterfaceIndex=[INTEGER], VcInboundLabel=[GAUGE], VcOutboundLabel=[GAUGE], SecondaryPw=[INTEGER], HWL2VpnStateChangeReason=[INTEGER], SysUpTime=[TIMETICK], InterfaceName=[STRING], SwitchVcId=[GAUGE], TunnelPolicyName=[STRING], ActiveState=[INTEGER], TunnelType = [INTEGER], SessionTunnelID=[GAUGE])

Indicates that a VC of the PWE3 goes Down.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.119.4.1.2.3

Major

 processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VcId

Indicates the ID of a VC.

VcType
Indicates the type of a VC:
  • 0: Initial value
  • 1: FR
  • 2: ATM AAL5
  • 3: ATM cell relay
  • 4: VLAN
  • 5: Ethernet
  • 6: HDLC
  • 7: PPP
  • 9: ATM cell VCC
  • 10: ATM cell VPC
  • 11: IP-layer 2 (used for heterogeneous IP-interworking between Huawei devices and non-Huawei devices)
  • 12: ATM, 1-to-1 VCC cell mode
  • 13: ATM, 1-to-1 VPC cell mode
  • 14: ATM, AAL5 PDU VCC TRANSPORT
  • 64: Heterogeneous IP-interworking

PeerAddress

Indicates the IP address of a peer.

InterfaceIndex

Indicates the interface index.

VcInboundLabel

Indicates the incoming label of a VC.

VcOutboundLabel

Indicates the outgoing label of a VC.

SecondaryPw
Whether the PW is a secondary PW
  • 1: The PW is a secondary PW.
  • 2: The PW is not a secondary PW.

HWL2VpnStateChangeReason

Indicates the cause for the VC status change.

SysUpTime

Indicates the time for the system startup.

InterfaceName

Indicates the name of an interface.

SwitchVcId

Indicates the ID of the switching VC.

TunnelPolicyName

Indicates the name of a tunnel policy.

ActiveState

Indicates the status of active.

TunnelType

Indicates the type of a tunnel.

SessionTunnelID

Indicates the ID of a tunnel.

Impact on the System

The PWE3 service is interrupted and traffic is blocked.

Possible Causes

1.

The local or peer AC interface went Down.

2.

The public network tunnel was faulty.

Procedure

  1. Run the display mpls l2vc interface interface-type interface-number command to check the status of the local PWE3. If the VC is in a Down state, it indicates that the PWE3 is also in the Down state. Then you need to find the cause for the Down state. The handling procedures are as follows:

    1. Check whether the LDP session is in the Down state or the Up state.
      • If the LDP session is Down, go to Step b.
      • If the LDP session is Up, go to Step c.
    2. Run the display mpls ldp session command to check the status of the LDP session to the remote end. If the LDP session of the peer does not exist, or the LDP session is not in Operational state, restore the status of the LDP session.
      • If the status is restored, go to Step c.
      • If the status is not restored, go to Step u.
    3. Check the AC state that indicates the physical status of the interface at the AC side of PWE3.
      • If the AC state is Down, go to Step d.
      • If the AC state is Up, go to Step e.
    4. Run the display interface interface-type interface-number command to view the physical status of the interface. If the physical status of the interface is Down, restore the physical status to Up.
      • If so, go to Step e.
      • If not, go to Step u.
    5. Check the local AC OAM State that indicates the link status of the interface at the AC side of PWE3. If AC OAM is enabled, you can check the related status of AC OAM. If AC OAM is not enabled, the local AC OAM status is Up.
      • If the local AC OAM state is Down, go to Step f.
      • If the local AC OAM state is Up, go to Step g.
    6. Run the display interface interface-type interface-number command to check the link status of the interface. If the link status of the interface is Down, restore the link status to Up.
      • If so, go to Step g.
      • If not, go to Step u.
    7. Check whether the local PSN state, that is, the status of BFD for LSP in PWE3, is Up. Note that the local PSN state is Down if the tunnels selected by the L2VPN are all Down after the BFD for LSP detection. Otherwise, the local PSN state is Up.
      • If the local PSN state is Down, go to Step h.
      • If the local PSN state is Up, go to Step i.
    8. Run the display bfd session all command to check the status of BFD for LSP. If the status of BFD for LSP is Down, restore the status to Up.
      • If so, go to Step i.
      • If not, go to Step t.
    9. Check the status of the local forwarding state, which indicates whether the local PWE3 can achieve forwarding. The local forwarding state indicates the AC status, status of the manual fault, and the status of the tunnel in the public network.
      • If it is not in the forwarding state, go to Step j.
      • If it is in the forwarding state, go to Step l.
    10. Check whether the interface is enabled with the function of manual fault. If so, disable the function.
      • If so, go to Step k.
      • If not, go to Step u.
    11. Check the token information of the VC tunnel, and find whether a tunnel is selected. The parameter 0 indicates that no tunnel is selected; other parameters indicate that the tunnel is selected.
      • If the parameter is 0, perform Step l.
      • If the parametric is not 0, perform Step m.
    12. Run the display tunnel-info all command to check information about the tunnel connected to the peer. Modify the configuration on the outbound interface on a public network and restore the tunnel connected to the peer.
      • If so, go to Step m.
      • If not, go to Step u.
    13. Check the status of the remote PWE3, which is indicated by the remote AC OAM state, remote PSN state, and remote forwarding state.
      • If the remote AC OAM state or the remote PSN state is Down, or the remote forwarding state is not forwarding, go to Step n.
      • If the remote AC OAM state and the remote PSN state are Up, and the remote forwarding state is forwarding, go to Step o.
    14. Check the PWE3 status on the remote router. If the PWE3 status is Down, restore the PWE3 status.
      • If the operation succeeds, go to Step o.
      • If the operation fails, go to Step u.
    15. Check whether the BFD state, that is, the status of BFD for PW, is Up.
      • If the BFD state is Down, go to Step p.
      • If the BFD state is Up or unavailable, go to Step q.
    16. Run the display bfd session all command to check the status of BFD for PW.
      • If the status of BFD for PW is the same as the VC state, go to Step q.
      • If the status of BFD for PW is not the same as the VC state, go to Step u.
    17. Check whether the local VC MTU is the same as the remote VC MTU.
      • If so, go to Step s.
      • If not, go to Step r.
    18. Check the MTU of the local AC interface and the MTU of the PWE3 interface on the peer router. If two MTUs are not the same, modify them to be the same.
      • If so, go to Step s.
      • If not, go to Step u.
    19. Check whether the local control word is the same as the remote control word. Note that they are the same only when both are either in the enable state or in the disable state.
      • If so, go to Step v.
      • If not, go to Step t.
    20. Ensure the local control word and the remote control word and ensure that they are the same.
      • If so, go to Step v.
      • If not, go to Step u.
    21. Collect alarm information and configuration information, and then contact technical support personnel.
    22. End.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.4 hwPWVcUp

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.4 hwPWVcUp

Description

L2V/2/PWE3VC_UP_ME_T:OID [oid] The status of the PWE3 VC turned UP. (VcId=[GAUGE], VcType=[INTEGER], PeerAddress=[IPADDR], InterfaceIndex=[INTEGER], VcInboundLabel=[GAUGE], VcOutboundLabel=[GAUGE], SecondaryPw=[INTEGER], HWL2VpnStateChangeReason=[INTEGER], SysUpTime=[TIMETICK], InterfaceName=[STRING], SwitchVcId=[GAUGE], TunnelPolicyName=[STRING], ActiveState=[INTEGER])

The trap was generated when the PWE3 VC was Up.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.119.4.1.2.4

Major

 other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VcId

Indicates the ID of a VC.

VcType
Indicates the type of a VC:
  • 0: Initial value
  • 1: FR
  • 2: ATM AAL5
  • 3: ATM cell relay
  • 4: VLAN
  • 5: Ethernet
  • 6: HDLC
  • 7: PPP
  • 9: ATM cell VCC
  • 10: ATM cell VPC
  • 11: IP-layer 2 (used for heterogeneous IP-interworking between Huawei devices and non-Huawei devices)
  • 12: ATM, 1-to-1 VCC cell mode
  • 13: ATM, 1-to-1 VPC cell mode
  • 14: ATM, AAL5 PDU VCC TRANSPORT
  • 64: Heterogeneous IP-interworking

PeerAddress

Indicates the IP address of a peer.

InterfaceIndex

Indicates the interface index.

VcInboundLabel

Indicates the incoming label of a VC.

VcOutboundLabel

Indicates the outgoing label of a VC.

SecondaryPw
Whether the PW is a secondary PW
  • 1: The PW is a secondary PW.
  • 2: The PW is not a secondary PW.

HWL2VpnStateChangeReason

Indicates the cause for the VC status change.

SysUpTime

Indicates the time for the system startup.

InterfaceName

Indicates the interface name.

SwitchVcId

Switches the ID of VC.

TunnelPolicyName

Indicates the name of a tunnel policy.

ActiveState

Indicates the status of active.

Impact on the System

The PWE3 service is recovered.

Possible Causes

A VC recovers from a fault.

Procedure

  1. This trap message is informational only, and no action is required.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.3 hwPWVcDown

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.6 hwPWVcBackup

Description

L2V/2/PWE3VC_BACKUP_T:OID [oid] The status of the PWE3 VC turned BACKUP. (VcId=[GAUGE], VcType=[INTEGER], PeerAddress=[IPADDR], InterfaceIndex=[INTEGER], VcInboundLabel=[GAUGE], VcOutboundLabel=[GAUGE], SecondaryPw=[INTEGER], HWL2VpnStateChangeReason=[INTEGER], SysUpTime=[TIMETICK], InterfaceName=[STRING], SwitchVcId=[GAUGE], ActiveState=[INTEGER])

Indicates that a VC turns to the backup state.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.119.4.1.2.6

Major

 other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VcId

ID of a VC.

VcType
Type of a VC:
  • 0: Initial value
  • 1: FR
  • 2: ATM AAL5
  • 3: ATM cell relay
  • 4: VLAN
  • 5: Ethernet
  • 6: HDLC
  • 7: PPP
  • 9: ATM cell VCC
  • 10: ATM cell VPC
  • 11: IP-layer 2 (used for heterogeneous IP-interworking between Huawei devices and non-Huawei devices)
  • 12: ATM, 1-to-1 VCC cell mode
  • 13: ATM, 1-to-1 VPC cell mode
  • 14: ATM, AAL5 PDU VCC TRANSPORT
  • 64: Heterogeneous IP-interworking

PeerAddress

IP address of a peer

InterfaceIndex

Interface index

VcInboundLabel

Incoming label of a VC.

VcOutboundLabel

Outgoing label of a VC

SecondaryPw
Whether the PW is a secondary PW:
  • 1: The PW is a secondary PW.
  • 2: The PW is not a secondary PW.

HWL2VpnStateChangeReason

Cause for the VC status change

SysUpTime

Time for the system startup

InterfaceName

Interface name

SwitchVcId

ID of the switching VC

ActiveState

Active state

Impact on the System

The VRRP status affects the service.

Possible Causes

A VC turned to the backup state.

Procedure

  1. View user logs to check the causes of the VRRP change. You can perform operations according to the specific cause.

    • If the cause is priority calculation, go to Step 6.
    • If the cause is that the MASTER_DOWN timer expired, go to Step 2.
    • If the cause is the change of the BFD session status, go to Step 2.
    • If the cause is the change of the interface status, go to Step 2.
    • If the cause is admin-vrrp DROVE, go to Step 6.

  2. Run the display vrrp command to check the status of the VRRP backup group on the former master switch.

    • If the VRRP backup group is in the Initialize state, it indicates that the former switch is faulty. Locate the cause of the fault and restore the master switch. Go to Step 8.
    • If the VRRP backup group is in the Backup state, go to Step 6.
    • If the VRRP backup group is in the Master state, go to Step 3.

  3. Check whether the master link is faulty.

    • If BFD is configured, go to Step 4.
    • If BFD is not configured, go to Step 5.

  4. Run the display vrrp command to check the status of the BFD session.

    • If the BFD session is Down, it indicates that the former master link is faulty. Locate the cause of the fault and restore the master link. Go to Step 8.
    • If the BFD session is Up, go to Step 7.

  5. Run the display vrrp [ interface interface-type interface-number ] [virtual-router-id ] statistics command to check whether the VRRP packets are normally forwarded.

    • If not, it indicates that the link is faulty. Locate the cause of the fault and restore the link. Go to Step 8.
    • If so, go to Step 7.

  6. On the former master switch and backup switch, run the display vrrp command to check whether the configured priority of the VRRP is consistent with the running priority.

    • If not, it indicates that the link monitored through VRRP is faulty. Locate the cause of the fault and restore the monitored link. Go to Step 8.
    • If so, go to Step 7.

  7. Collect alarm information and configuration information, and then contact technical support personnel.
  8. End.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.3 hwPWVcDown

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.4 hwPWVcUp

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.10 hwVpwsPwRedundancyDegraded

Description

L2V/2/PWE3_VPWS_DEGRADED_T: OID [OID] VPWS PW redundancy reported a protect degraded alarm. (PrimaryPwId=[GAUGE], PrimaryPwType=[INTEGER], InterfaceIndex=[INTEGER], InterfaceName=[STRING])

VLL FRR protection degraded.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.119.4.1.2.10

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

PrimaryPwId

Primary PW ID

PrimaryPwType

Primary PW type

InterfaceIndex

Index of the interface where the PW resides

InterfaceName

Interface where the PW resides

Impact on the System

If the primary or secondary PW for VLL FRR fails, VLL FRR protection will degrade.

Possible Causes

The primary or secondary PW for VLL FRR failed.

Procedure

  1. Perform the troubleshooting operations described in hwPWVcDown to rectify the fault and then check whether the trap is cleared.

    • If trap is cleared, go to step 2.
    • If trap is not cleared, go to step 3.

  2. Collect alarm information and configuration information, and then contact technical support personnel.
  3. End.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.11_hwVpwsPwRedundancyDegradedClear

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.11 hwVpwsPwRedundancyDegradedClear

Description

L2V/2/PWE3_VPWS_DEGRADED_CLEAR_T: OID [OID] VPWS PW redundancy reported the clearing of the protect degraded alarm. (PrimaryPwId=[GAUGE], PrimaryPwType=[INTEGER], InterfaceIndex=[INTEGER], InterfaceName=[STRING])

The VLL FRR protection degrade alarm was cleared.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.119.4.1.2.11

Major

other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

PrimaryPwId

Primary PW ID

PrimaryPwType

Primary PW type

InterfaceIndex

Index of the interface where the PW resides

InterfaceName

Interface where the PW resides

Impact on the System

Services will not be affected.

Possible Causes

The faulty primary or secondary PW for VLL FRR recovered.

Procedure

  • This message is informational only, and no action is required.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.10_hwVpwsPwRedundancyDegraded

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.4.3 hwSvcDown

Description

L2V/2/SVC_DWN_T:OID [oid] The status of the SVC VC turned DOWN. (InterfaceIndex=[INTEGER], InterfaceIndex=[INTEGER], SvcId=[GAUGE], SVcType=[INTEGER], PeerAddress=[IPADDR], SvcInboundLabel=[GAUGE], SvcOutboundLabel=[GAUGE], HWL2VpnStateChangeReason=[INTEGER], InterfaceName=[STRING], TunnelPolicyName=[STRING], ActiveState=[INTEGER], TunnelType = [INTEGER], SessionTunnelId=[GAUGE])

Indicates an SVC goes Down.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.119.4.1.4.3

Major

 processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

InterfaceIndex

Index of the interface used as the table index.

InterfaceIndex

Index of the interface reported to the network management system as a parameter.

SvcId

Indicates the ID of an SVC.

SVcType
Indicates the type of an SVC:
  • 0: Initial value
  • 1: FR
  • 2: ATM AAL5
  • 3: ATM cell relay
  • 4: VLAN
  • 5: Ethernet
  • 6: HDLC
  • 7: PPP
  • 9: ATM cell VCC
  • 10: ATM cell VPC
  • 11: IP-layer 2 (used for heterogeneous IP-interworking between Huawei devices and non-Huawei devices)
  • 12: ATM, 1-to-1 VCC cell mode
  • 13: ATM, 1-to-1 VPC cell mode
  • 14: ATM, AAL5 PDU VCC Transport
  • 64: Heterogeneous IP-interworking

PeerAddress

Indicates the IP address of a peer.

SvcInboundLabel

Indicates the incoming label of an SVC.

SvcOutboundLabel

Indicates the outgoing label of an SVC.

HWL2VpnStateChangeReason

Indicates the cause for the SVC status change.

InterfaceName

Indicates the interface name.

TunnelPolicyName

Indicates the name of a tunnel policy.

ActiveState

Indicates the status of active.

TunnelType

Indicates the type of a tunnel.

SessionTunnelId

Indicates the ID of a tunnel.

Impact on the System

The SVC service is interrupted and the traffic is blocked.

Possible Causes

1.

The local or peer AC interface went Down.

2.

The public network tunnel was faulty.

Procedure

  1. Run the display mpls static-l2vc interface interface-type interface-number command to check whether the AC goes Up.

    • If so, go to Step 3.
    • If not, go to Step 2.
    The SVC status can be Up if two conditions are met. That is, the AC status is Up and the tunnel is selected.

  2. Check whether the AC interface goes Down.

    • If so, rectify the fault and ensure that the AC interface goes Up. Then, check whether the fault is rectified. If so, go to Step 7; if not, go to Step 3.
    • If not, go to Step 3.

  3. View the command output in Step 1 to check whether the number of tunnels in the VC tunnel/token info field is 0.

    • If so, go to Step 4.
    • If not, go to Step 7.

  4. Run the display tunnel-info all command to check whether there is information about the LSP tunnel with the destination address being the address of the peer PE.

    • If so, go to Step 7.
    • If no, go to Step 5.

  5. Check and rectify the configuration of the public network interface. Check whether the fault is rectified.

    • If so, go to Step 7.
    • If not, go to Step 6.

  6. Collect alarm information and configuration information, and then contact technical support personnel.
  7. End.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.4.4 hwSvcUp

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.4.4 hwSvcUp

Description

L2V/2/SVC_UP_T:OID [oid] The status of the SVC VC turned UP. (InterfaceIndex=[INTEGER], InterfaceIndex=[INTEGER], SvcId=[GAUGE], SVcType=[INTEGER], PeerAddress=[IPADDR], SvcInboundLabel=[GAUGE], SvcOutboundLabel=[GAUGE], HWL2VpnStateChangeReason=[INTEGER], InterfaceName=[STRING], TunnelPolicyName=[STRING], ActiveState=[INTEGER])

The trap was generated when the SVC VC was Up.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.119.4.1.4.4

Major

other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

InterfaceIndex

Index of the interface used as the table index.

InterfaceIndex

Index of the interface reported to the network management system as a parameter.

SvcId

Indicates the ID of an SVC.

SVcType
Indicates the type of an SVC:
  • 0: Initial value
  • 1: FR
  • 2: ATM AAL5
  • 3: ATM cell relay
  • 4: VLAN
  • 5: Ethernet
  • 6: HDLC
  • 7: PPP
  • 9: ATM cell VCC
  • 10: ATM cell VPC
  • 11: IP-layer 2 (used for heterogeneous IP-interworking between Huawei devices and non-Huawei devices)
  • 12: ATM, 1-to-1 VCC cell mode
  • 13: ATM, 1-to-1 VPC cell mode
  • 14: ATM, AAL5 PDU VCC TRANSPORT
  • 64: Heterogeneous IP-interworking

PeerAddress

Indicates the IP address of a peer.

SvcInboundLabel

Indicates the incoming label of an SVC.

SvcOutboundLabel

Indicates the outgoing label of an SVC.

HWL2VpnStateChangeReason

Indicates the cause for the SVC status change.

InterfaceName

Indicates the interface name.

TunnelPolicyName

Indicates the name of a tunnel policy.

ActiveState

Indicates the status of active.

Impact on the System

The SVC service is recovered.

Possible Causes

An SVC goes Up.

Procedure

  1. This trap message is informational only, and no action is required.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.4.3 hwSvcDown

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.4.5 hwSvcDeleted

Description

L2V/4/SVC_DEL_T:OID [oid] The SVC has been deleted. (InterfaceIndex=[INTEGER], InterfaceIndex=[INTEGER], SvcId=[GAUGE], SVcType=[INTEGER], PeerAddress=[IPADDR], SvcInboundLabel=[GAUGE], SvcOutboundLabel=[GAUGE], InterfaceName=[STRING])

The SVC was deleted.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.119.4.1.4.5

Warning

 qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

InterfaceIndex

Index of the interface used as the table index

InterfaceIndex

Index of the interface reported to the network management system as a parameter

SvcId

ID of the SVC

SVcType
Type of the SVC. The values are as follows:
  • 0: initial value
  • 1: FR
  • 2: ATM AAL5
  • 3: ATM cell relay
  • 4: VLAN
  • 5: Ethernet
  • 6: HDLC
  • 7: PPP
  • 9: ATM cell VCC
  • 10: ATM cell VPC
  • 12: ATM, 1-to-1 VCC cell mode
  • 13: ATM, 1-to-1 VPC cell mode
  • 14: ATM, AAL5 PDU VCC transport
  • 64: heterogeneous interworking

PeerAddress

IP address of the peer

SvcInboundLabel

Inbound label of the SVC

SvcOutboundLabel

Outbound label of the SVC

InterfaceName

Name of the interface

Impact on the System

SVC services are interrupted.

Possible Causes

Cause 1:

The SVC was manually deleted.

Cause 2:

L2VPN or MPLS was disabled.

Procedure

  1. This alarm is informational only, and no action is required.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.4.3_hwSvcDown

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.9 hwPWVcStatusChange

Description

L2V/4/PWE3VC_STATUS_CHANGE_T:OID [oid] The active state of the PWE3 VC changed. (VcId=[GAUGE], VcType=[INTEGER], PeerAddress=[IPADDR], VcStatus=[INTEGER], ActiveState=[INTEGER])

The active status of a PWE3 VC changed.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.119.4.1.2.9

Warning

qualityOfServiceAlarm

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VcId

Indicates the ID of the PW.

VcType

Indicates the type of the PW.

PeerAddress

Indicates the IP address of a peer.

VcStatus

Indicates the status of a VC.

ActiveState

Indicates the status of Active.

Impact on the System

The service forwarding path changed.

Possible Causes

Cause 1:

The PW went Down from the Up state or went Up from the Down state.

Cause 2:

PW switching occurred when primary and secondary PWs are deployed.

Cause 3:

A fault occurred or was rectified on the public network or an interface when bypass PWs are deployed.

Procedure

  1. Run the display mpls l2vc interface interface-type interface-number command to check the status of the local PWE3. If the VC is in a Down state, it indicates that the PWE3 is also in the Down state. Then you need to find the cause for the Down state. The handling procedures are as follows:

    1. Check whether the LDP session is in the Down state or the Up state.
      • If the LDP session is Down, go to Step b.
      • If the LDP session is Up, go to Step c.
    2. Run the display mpls ldp session command to check the status of the LDP session to the remote end. If the LDP session of the peer does not exist, or the LDP session is not in Operational state, restore the status of the LDP session.
      • If the status is restored, go to Step c.
      • If the status is not restored, go to Step u.
    3. Check the AC state that indicates the physical status of the interface at the AC side of PWE3.
      • If the AC state is Down, go to Step d.
      • If the AC state is Up, go to Step e.
    4. Run the display interface interface-type interface-number command to view the physical status of the interface. If the physical status of the interface is Down, restore the physical status to Up.
      • If so, go to Step e.
      • If not, go to Step u.
    5. Check the local AC OAM State that indicates the link status of the interface at the AC side of PWE3. If AC OAM is enabled, you can check the related status of AC OAM. If AC OAM is not enabled, the local AC OAM status is Up.
      • If the local AC OAM state is Down, go to Step f.
      • If the local AC OAM state is Up, go to Step g.
    6. Run the display interface interface-type interface-number command to check the link status of the interface. If the link status of the interface is Down, restore the link status to Up.
      • If so, go to Step g.
      • If not, go to Step u.
    7. Check whether the local PSN state, that is, the status of BFD for LSP in PWE3, is Up. Note that the local PSN state is Down if the tunnels selected by the L2VPN are all Down after the BFD for LSP detection. Otherwise, the local PSN state is Up.
      • If the local PSN state is Down, go to Step h.
      • If the local PSN state is Up, go to Step i.
    8. Run the display bfd session all command to check the status of BFD for LSP. If the status of BFD for LSP is Down, restore the status to Up.
      • If so, go to Step i.
      • If not, go to Step t.
    9. Check the status of the local forwarding state, which indicates whether the local PWE3 can achieve forwarding. The local forwarding state indicates the AC status, status of the manual fault, and the status of the tunnel in the public network.
      • If it is not in the forwarding state, go to Step j.
      • If it is in the forwarding state, go to Step l.
    10. Check whether the interface is enabled with the function of manual fault. If so, disable the function.
      • If so, go to Step k.
      • If not, go to Step u.
    11. Check the token information of the VC tunnel, and find whether a tunnel is selected. The parameter 0 indicates that no tunnel is selected; other parameters indicate that the tunnel is selected.
      • If the parameter is 0, perform Step l.
      • If the parametric is not 0, perform Step m.
    12. Run the display tunnel-info all command to check information about the tunnel connected to the peer. Modify the configuration on the outbound interface on a public network and restore the tunnel connected to the peer.
      • If so, go to Step m.
      • If not, go to Step u.
    13. Check the status of the remote PWE3, which is indicated by the remote AC OAM state, remote PSN state, and remote forwarding state.
      • If the remote AC OAM state or the remote PSN state is Down, or the remote forwarding state is not forwarding, go to Step n.
      • If the remote AC OAM state and the remote PSN state are Up, and the remote forwarding state is forwarding, go to Step o.
    14. Check the PWE3 status on the remote router. If the PWE3 status is Down, restore the PWE3 status.
      • If the operation succeeds, go to Step o.
      • If the operation fails, go to Step u.
    15. Check whether the BFD state, that is, the status of BFD for PW, is Up.
      • If the BFD state is Down, go to Step p.
      • If the BFD state is Up or unavailable, go to Step q.
    16. Run the display bfd session all command to check the status of BFD for PW.
      • If the status of BFD for PW is the same as the VC state, go to Step q.
      • If the status of BFD for PW is not the same as the VC state, go to Step u.
    17. Check whether the local VC MTU is the same as the remote VC MTU.
      • If so, go to Step s.
      • If not, go to Step r.
    18. Check the MTU of the local AC interface and the MTU of the PWE3 interface on the peer router. If two MTUs are not the same, modify them to be the same.
      • If so, go to Step s.
      • If not, go to Step u.
    19. Check whether the local control word is the same as the remote control word. Note that they are the same only when both are either in the enable state or in the disable state.
      • If so, go to Step v.
      • If not, go to Step t.
    20. Ensure the local control word and the remote control word and ensure that they are the same.
      • If so, go to Step v.
      • If not, go to Step u.
    21. Collect alarm information and configuration information, and then contact technical support personnel.
    22. End.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.3 hwPWVcDown

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.9 hwVplsVcNumberThresholdExceed

Description

L2V/3/VPLSVC_THRESHOLD_EXCEED_T:OID [OID] The number of VPLS VCs reaches the upper threshold. (LimitClass=[INTEGER], CurrentVcNumber=[GAUGE], UpperThreshold=[GAUGE], MaxiVcNumber=[GAUGE])

The proportion of VPLS VCs created to the maximum VPLS VCs allowed reached the upper alarm threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.119.1.2.9

Minor

qualityOfServiceAlarm

Parameters

Name Meaning

OID

Indicates the MIB object ID of the alarm.

LimitClass

Limit type

CurrentVcNumber

Number of VPLS VCs created

UpperThreshold

Upper alarm threshold

MaxiVcNumber

Maximum number of VPLS VCs allowed

Impact on the System

Services will not be affected.

Possible Causes

The proportion of VPLS VCs created to the maximum VPLS VCs allowed reached the upper alarm threshold.

Procedure

  1. Run the display vpls connection command to check the number of configured VPLS VCs. Reduce the number of VPLS VCs created to prevent device performance deterioration.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.10 hwVplsVcNumberThresholdClear

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.10 hwVplsVcNumberThresholdClear

Description

L2V/3/VPLSVC_THRESHOLD_CLEAR_T: OID [OID] The number of VPLS VCs falls below the lower threshold.

The proportion of VPLS VC created to the maximum VPLS VCs allowed fell below the lower alarm threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.119.1.2.10

Minor

qualityOfServiceAlarm

Parameters

Name Meaning

OID

Indicates the MIB object ID of the alarm.

Impact on the System

Services will not be affected.

Possible Causes

The proportion of VPLS VCs created to the maximum VPLS VCs allowed fell below the lower alarm threshold.

Procedure

  1. This message is informational only, and no action is required.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.9 hwVplsVcNumberThresholdExceed

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.11 hwVplsVcNumberMaxExceed

Description

L2V/3/VPLSVC_MAX_EXCEED_T: OID [OID] The number of VPLS VCs reaches the maximum limit. (LimitClass=[INTEGER], MaxiVcNumber=[GAUGE])

The number of VPLS VCs created reached the maximum number of VPLS VCs allowed.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.119.1.2.11

Minor

qualityOfServiceAlarm

Parameters

Name Meaning

OID

Indicates the MIB object ID of the alarm.

LimitClass

Warning limit type

MaxiVcNumber

Maximum number of VPLS VCs allowed

Impact on the System

No more VPLS VCs can be created.

Possible Causes

The number of VPLS VCs created reached the maximum number of VPLS VCs allowed.

Procedure

  1. Run the display vpls connection command to check the number of configured VPLS VCs. Reduce the number of VPLS VCs created to prevent device performance deterioration.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.12 hwVplsVcNumberMaxClear

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.12 hwVplsVcNumberMaxClear

Description

L2V/3/VPLSVC_MAX_CLEAR_T: OID [OID] The number of VPLS VCs is less than 95% of the maximum limit.

The number of VPLS VC created fell below 95% of the maximum number of VPLS VCs allowed.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.119.1.2.12

Minor

qualityOfServiceAlarm

Parameters

Name Meaning

OID

Indicates the MIB object ID of the alarm.

Impact on the System

Services will not be affected.

Possible Causes

The number of VPLS VC created fell below 95% of the maximum number of VPLS VCs allowed.

Procedure

  1. This message is informational only, and no action is required.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.11 hwVplsVcNumberMaxExceed

Translation
日本語 简体中文
Download
Updated: 2022-05-25

Document ID: EDOC1100127008

Views: 75683

Downloads: 321

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Digital Signature File

Digital Signature Authentication Mode
Share
Previous Next

Copyright © 2023 Huawei Technologies Co., Ltd. All rights reserved.

You are going to visit :