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, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R010

This document provides the trap description, attributes, parameters, impact on the system, possible causes, procedures, and references. This document provides a complete set of traps, through which intended readers are kept of the running status of the device so as to locate faults.
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.5 hwVplsVcBackup

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 router.

    • If the VRRP backup group is in the Initialize state, it indicates that the former router is faulty. Locate the cause of the fault and restore the master router. 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 router and backup router, 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.
Translation
Download
Updated: 2019-08-12

Document ID: EDOC1100034065

Views: 144027

Downloads: 42

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