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

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Alarm Handling

CloudEngine 12800 and 12800E V200R005C00

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).
L2VPN_1.3.6.1.4.1.2011.5.25.119.4.1.2.3 hwPWVcDown

L2VPN_1.3.6.1.4.1.2011.5.25.119.4.1.2.3 hwPWVcDown

Description

The status of the PWE3 VC turned DOWN. (VcId=[VcId], VcType=[VcType], PeerAddress=[PeerAddress], InterfaceIndex=[InterfaceIndex], VcInboundLabel=[VcInboundLabel], VcOutboundLabel=[VcOutboundLabel], SecondaryPw=[SecondaryPw], HWL2VpnStateChangeReason=[HWL2VpnStateChangeReason], SysUpTime=[SysUpTime], InterfaceName=[InterfaceName], SwitchVcId=[SwitchVcId], TunnelPolicyName=[TunnelPolicyName])

The trap was generated when the PWE3 VC was Down.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwPWVcDown

Trap OID

1.3.6.1.4.1.2011.5.25.119.4.1.2.3

Alarm ID

0x0d4c0001

Alarm Type

communicationsAlarm

Raise or Clear

Raise

Match trap

L2VPN_1.3.6.1.4.1.2011.5.25.119.4.1.2.4 hwPWVcUp

Parameters

Parameter Description
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 transparent transmission
  • 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 AC interface index.
VcInboundLabel Indicates the incoming label of a VC.
VcOutboundLabel Indicates the outgoing label of a VC.
SecondaryPw Indicates the backup PW.
HWL2VpnStateChangeReason Indicates the cause for the VC status change.
SysUpTime Indicates the time for the system startup.
InterfaceName Indicates the AC interface name.
SwitchVcId Switches the ID of VC.
TunnelPolicyName Indicates the name of a tunnel policy.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.119.4.1.1.1.1.4

hwPWVcPeerAddr

hwPWVcID;

hwPWVcType;

1.3.6.1.4.1.2011.5.25.119.4.1.1.1.1.15

hwPWVcIfIndex

hwPWVcID;

hwPWVcType;

1.3.6.1.4.1.2011.5.25.119.4.1.1.1.1.6

hwPWVcInboundLabel

hwPWVcID;

hwPWVcType;

1.3.6.1.4.1.2011.5.25.119.4.1.1.1.1.7

hwPWVcOutboundLabel

hwPWVcID;

hwPWVcType;

1.3.6.1.4.1.2011.5.25.119.4.1.1.1.1.27

hwPWVcSecondary

hwPWVcID;

hwPWVcType;

1.3.6.1.4.1.2011.5.25.119.4.1.1.8

hwPWVcStateChangeReason

N/A

1.3.6.1.2.1.1.3

sysUpTime

N/A

1.3.6.1.4.1.2011.5.25.119.4.1.1.1.1.49

hwPWVcIfName

hwPWVcID;

hwPWVcType;

1.3.6.1.4.1.2011.5.25.119.4.1.1.1.1.9

hwPWVcSwitchID

hwPWVcID;

hwPWVcType;

1.3.6.1.4.1.2011.5.25.119.4.1.1.1.1.23

hwPWVcTnlPolicyName

hwPWVcID;

hwPWVcType;

Impact on the System

Indicates that the PWE3 service is interrupted and traffic is blocked.

Possible Causes

Cause 1: Invalid reason type

Cause 3: Local VC Deleted

Cause 4: LDP Session Down

Cause 6: Same LDP mapping was received with different label and MTU

Cause 8: LDP mapping was received with mismatching interface parameters

Cause 12: New LDP mapping message was received but remote VC or local VC is Down

Cause 13: LDP Withdrawn Received

Cause 14: LDP release message was received

Cause 19: Interface Down

Cause 20: Encapsulation changed

Cause 24: Tunnel was Down

Cause 31: LDP Notification Not-Forwarding

Cause 32: PW was recreated

Cause 41: Local PSN Fault

Cause 43: BFD for pw status changed to Down

Cause 47: Manual set was enabled

Cause 60: MTU Unmatched

Procedure

  • Case 3: Local VC Deleted.
    1. Confirm that whether the VPWS connection is need to be deleted.

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

    2. Recreate the VPWS connection. Then, check whether the alarm is cleared.

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

    3. Contact technical support personnel.
    4. End.
  • Case 4: LDP Session Down.
    1. 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. Then, check whether the alarm is cleared.

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

    2. Contact technical support personnel.
    3. End.
  • Case 13: LDP Withdrawn Received.
    1. Check whether the VPWS connection is need to be deleted by manual. If not, run the mpls l2vc command to restore the connection. Then, check whether the alarm is cleared.

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

    2. Contact technical support personnel.
    3. End.
  • Case 19: Interface Down.
    1. Run the display mpls l2vc interface interface-type interface-number command to check the AC status.

      • If the AC status is down, go to Step 2.
      • If the AC status is up, go to Step 3.

    2. Run the display interface interface-type interface-number command to view the physical and link status of the interface. If the status of the interface is down, restore the physical and link status to up. Then, check whether the alarm is cleared.

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

    3. Contact technical support personnel.
    4. End.
  • Cause 24: Tunnel was Down
    1. Run the display mpls l2vc command to check whether the tunnel ID exists.

      • If the tunnel ID exists, go to Step 3.
      • If the tunnel ID does not exist, go to Step 4.

    2. Check whether the public network interface is Down. If it is Down, bring it Up and then run the display tunnel all command to check the tunnel status. After the tunnel goes Up, check whether the alarm is cleared.

      • If the alarm is cleared, go to Step 4.
      • If the alarm persists, go to Step 3.

    3. Contact technical support personnel.
    4. End.
  • Case 31: LDP Notification Not-Forwarding.
    1. Run the display mpls l2vc interface interface-type interface-number command to check the status of the remote AC interface.

      • If the AC status is down, go to Step 2.
      • If the AC status is up, go to Step 3.

    2. Run the display interface interface-type interface-number command to view the physical and link status of the remote interface. If the status of the interface is down, restore the physical and link status to up. Then, check whether the alarm is cleared.

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

    3. Run the display mpls l2vc vc-id command to check the VC tunnel info field in the command output. If VC tunnel info is displayed as 0, it indicates that no tunnel is selected by a PW. Run the display mpls l2vc interface interface-type interface-number command to check the tunnel policy name field in the command output. If tunnel policy name is displayed as "--", it indicates that an LDP LSP is used as the tunnel for a PW or no tunnel policy is configured. An MPLS TE tunnel can be used for a PW only after a tunnel policy is configured. If tunnel policy name is not displayed as "--", it indicates that a tunnel policy is adopted. In this case, you can run the display this command in the tunnel policy view to view the tunnel policy configuration. Modify the configuration on the outbound interface on a public network and restore the tunnel connected to the peer. Then, check whether the alarm is cleared.

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

    4. Contact technical support personnel.
    5. End.
  • Case 41: Local PSN Fault.
    1. Run the display tunnel 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. Then, check whether the alarm is cleared.
    2. Contact technical support personnel.
    3. End.
  • Case 60: MTU Unmatched.
    1. Run the display mpls l2vc interface interface-type interface-number command to check whether the local VC MTU is the same as remote VC MTU.

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

    2. Check the MTU of the local VC MTU and remote VC MTU. If two MTUs are not the same, modify them to be the same. Then, check whether the alarm is cleared.

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

    3. Run the display mpls l2vc interface interface-type interface-number command to check 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. Then, check whether the alarm is cleared.

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

    4. Contact technical support personnel.
    5. End.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039527

Views: 68049

Downloads: 21

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next