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 8800, 7800, 6800, and 5800 V200R002C50

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).
VRRP_1.3.6.1.2.1.68.0.1 vrrpTrapNewMaster

VRRP_1.3.6.1.2.1.68.0.1 vrrpTrapNewMaster

Description

The VRRP status changed to master. (ifIndex=[ifIndex], VrId=[VrId], MasterIPAddress=[MasterIPAddress], sysName=[sysName], ifName=[ifName], ChangeReason=[ChangeReason])

The VRRP status changed to Master.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

vrrpTrapNewMaster

Trap OID

1.3.6.1.2.1.68.0.1

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the matching trap.

Parameters

Parameter Description

ifIndex

Index of an interface where VRRP resides.

VrId

VRRP ID.

MasterIPAddress

IP address of the master device.

sysName

System name.

ifName

Name of the VRRP interface.

ChangeReason

Cause for the VRRP status change.

VB

VB OID

VB Name

VB Index

1.3.6.1.2.1.68.1.5

vrrpTrapPacketSrc

None

1.3.6.1.2.1.68.1.6

vrrpTrapAuthErrorType

None

Impact on the System

If a master/backup VRRP switchover is implemented and the user traffic path changes, the switchover may lead to a traffic interruption.

Possible Causes

Cause 1: priority calculation.

Cause 2: protocol timer expired.

Cause 3: ip owner.

Cause 4: admin-vrrp drove.

Procedure

  • Cause 1: priority calculation.
    1. On the former master device and backup device, run the display vrrp command to check whether the configured priority of the VRRP is consistent with the running priority.

      • If the priorities do not match, go to Step 2.
      • If the priorities match, go to Step 3.

    2. If the priorities do not match, the link monitored through VRRP is faulty. Locate the cause of the fault and restore the monitored link.
    3. Collect configurations, trap messages, and log messages, and contact technical support personnel.
  • Cause 2: protocol timer expired.
    1. Run the display vrrp command to check the status of the VRRP backup group on the former master device.

      • If the VRRP backup group is in the Initialize state, the former device is faulty. Locate the cause of the fault and restore the master device.
      • If the VRRP backup group is in the Backup state, go to Step 2.
      • If the VRRP backup group is in the Master state, go to Step 4.

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

      • If the priorities do not match, go to Step 3.
      • If the priorities match, go to Step 7.

    3. If the priorities do not match, the link monitored through VRRP is faulty. Locate the cause of the fault and restore the monitored link.
    4. Check whether the links between the switch device and the master device and between the switch device and the backup deviceare normal.

      • If the VRRP backup group is associated with BFD, go to Step 5.
      • If the VRRP backup group is not associated with BFD, go to Step 6.

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

      • If the BFD session is Down, the link between the switch device and the master deivce or between the switch device and the backup device is faulty. Locate the cause of the fault and restore the link.
      • If the BFD session is Up, go to Step 7.

    6. Run the debugging vrrp packet command to check whether the VRRP packets are normally forwarded.

      • If the packets are not normally forwarded, the link is faulty. Locate the cause of the fault and restore the link.
      • If the packets are normally forwarded, go to Step 7.

    7. Collect configurations, trap messages, and log messages, and contact technical support personnel.
  • Cause 3: ip owner.
    1. Run the display vrrp command to check whether the VRRP device is configured as the IP address owner.

      • If the VRRP device is the IP address owner, this device is in the Master state.
      • If the VRRP device is not the IP address owner, go to Step 2.

    2. Collect configurations, trap messages, and log messages, and contact technical support personnel.
  • Cause 4: admin-vrrp drove.
    1. Run the display vrrp command to check whether a VRRP backup group is bound to an mVRRP backup group.

      • If a VRRP backup group is bound to an mVRRP backup group, go to Step 2.
      • If a VRRP backup group is not bound to an mVRRP backup group, go to Step 3.

    2. Run the display vrrp command to check whether the mVRRP status is Master.

      • If the mVRRP status is Master, the status has changed. Locate the cause of the status change.
      • If the mVRRP status is not Master, go to Step 3.

    3. Collect configurations, trap messages, and log messages, and contact technical support personnel.
Translation
Download
Updated: 2019-03-20

Document ID: EDOC1000166558

Views: 193761

Downloads: 113

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