< Home

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

Parent Topic: L2V
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >