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

AR100-S, AR110-S, AR120-S, AR150-S, AR160-S, AR200-S, AR1200-S, AR2200-S, and AR3200-S V200R009

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_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.
Translation
Download
Updated: 2019-05-06

Document ID: EDOC1000174085

Views: 128298

Downloads: 20

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