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

E9000 Server V100R001 HMM Alarm Handling 19

This document describes E9000 server alarms in terms of the meaning, impact on the system, possible causes, and solutions.
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

VRRP

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

VRRP_1.3.6.1.2.1.68.0.2 vrrpTrapAuthFailure

Description

VRRP authentication failed. (vrrpTrapPacketSrc=[vrrpTrapPacketSrc], vrrpTrapAuthErrorType=[vrrpTrapAuthErrorType])

VRRP authentication failed.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Error

Mnemonic Code

vrrpTrapAuthFailure

Trap OID

1.3.6.1.2.1.68.0.2

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 match trap.

Parameters

Parameter

Description

vrrpTrapPacketSrc

Primary IP address of an interface on which a VRRP backup group is configured.

vrrpTrapAuthErrorType

Authentication failure types in the VRRP group.

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 the master and backup devices in a VRRP backup group are not configured with the same authentication modes, the two devices fail to negotiate.

Possible Causes

Cause 1: invalidAuthType.

Cause 2: authTypeMismatch.

Cause 3: authFailure.

Procedure
  • Cause 1: invalidAuthType.
    1. Collect configurations, trap messages, and log messages, and then contact technical support personnel.
  • Cause 2: authTypeMismatch.
    1. Run the display vrrp command to check VRRP authentication modes configured on the master and backup devices.
      • If simple authentication is configured on one end and MD5 authentication is configured on the other end, go to Step 2.
      • If both ends are configured with simple or MD5 authentication, go to Step 3.
    2. Configure the same VRRP authentication mode and authentication key on the master and backup devices in a VRRP backup group.
    3. Collect configurations, trap messages, and log messages, and contact technical support personnel.
  • Cause 3: authFailure.
    1. Run the display vrrp command to check the VRRP authentication modes and authentication keys configured on the master and backup devices.
      • If the authentication modes are the same, but the authentication keys are different, go to Step 2.
      • If the authentication modes are different or both the authentication modes and authentication keys are the same, go to Step 3.
    2. Configure the same VRRP authentication mode and authentication key on the master and backup devices in a VRRP backup group.
    3. Collect configurations, trap messages, and log messages, and contact technical support personnel.

VRRP_1.3.6.1.4.1.2011.5.25.127.2.30.1 hwVrrpExtTrapMasterDown

Description

The VRRP status changed from master to another state. (ifIndex=[ifIndex], VrId=[VrId], MasterIpAddr=[MasterIpAddr], sysName=[sysName], ifName=[ifName], CurrentState=[CurrentState], ChangeReason=[ChangeReason])

The VRRP backup group was changed from the Master state to another state.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwVrrpExtTrapMasterDown

Trap OID

1.3.6.1.4.1.2011.5.25.127.2.30.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 match trap.

Parameters

Parameter

Description

VrrpIfIndex

Indicates the index of the interface where VRRP resides.

VrId

Indicates the ID of VRRP.

IfIndex

Indicates the index of the interface where VRRP resides.

IpAddress

Indicates the Router id of the interface where VRRP resides.

NodeName

Indicates the device name.

IfName

Indicates the name of the VRRP interface.

CurrentState

VRRP status after the change:

  • Notactive: Indicates that the VRRP backup group in the master state is deleted. Configurations of this VRRP backup group cannot be viewed by using the display vrrp command.
  • Initialize
  • Backup

ChangeReason

Indicates the cause for the VRRP status change.

VB

VB OID

VB Name

VB Index

1.3.6.1.2.1.68.1.3.1.7

vrrpOperMasterIpAddr

ifIndex

vrrpOperVrId

1.3.6.1.2.1.1.5

sysName

None

1.3.6.1.2.1.31.1.1.1.1

ifName

ifIndex;

1.3.6.1.2.1.68.1.3.1.3

vrrpOperState

ifIndex

vrrpOperVrId

1.3.6.1.4.1.2011.5.25.127.1.7

hwVrrpExtStateChangeReasonString

None

Impact on the System
  • If master/backup switchover occurs normally, services are not affected.
  • If master/backup switchover occurs abnormally, services may be interrupted.
Possible Causes

The status of VRRP configured on the device changed from MASTER to other status.

Procedure
  1. View the value of CurentState in the trap, check the status after the VRRP backup group changes, and perform operations according to the specific cause.
  • If the value of CurentState is Notactive, go to Step 2.
  • If the value of CurentState is Backup, go to Step 3.
  • If the value of CurentState is Initialize, go to Step 4.
  1. If the VRRP backup group in the Master state is deleted, you cannot view the configurations of the VRRP backup group by using the display vrrp command. You can check the operation records of command lines by viewing log information.
  2. Run the display vrrp command to check whether the set priorities of the VRRP backup group on the original master device and backup device are the same as the running priorities.

    • If so, go to Step 7.
    • If not, it indicates that the link monitored by the VRRP backup group is faulty and the priorities are increased or reduced. Locate the cause of the fault and restore the monitored link. Then, go to Step 4.

  3. If the original master device is faulty, locate the cause of the fault and restore the master device.

    • Check whether the interface where the VRRP backup group resides is normal, and then go to Step 6.
    • Check whether the link that the VRRP backup group monitors is normal, and then go to Step 7.
    • If the VRRP backup group and BFD are associated, check the link that BFD monitors and go to Step 5.

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

    • If the BFD session is Up, go to Step 8.
    • If the BFD session is Down, it indicates that the original active link is faulty. Locate the cause of the fault and restore the active link. Then, go to Step 9.

  5. Run the display vrrp command to check whether VRRP Advertisement packets can be normally received and sent.

    • If so, go to Step 8.
    • If not, it indicates that the link is faulty. Locate the cause of the fault and restore the link. Then, go to Step 9.

  6. Run the display vrrp command to view the interface that is monitored by the BFD session associated with the VRRP backup groups and then enter the interface view to run the display this interface command to detect the interface status.

    • If the interface status is Up, go to Step 8.
    • If the interface status is Down, it indicates that the link is faulty. Locate the cause of the fault and restore the active link. Then, go to Step 9.

  7. Collect information about configurations, trap messages, and log messages, and then contact technical support personnel.
  8. End.

VRRP_1.3.6.1.4.1.2011.5.25.127.2.30.2 hwVrrpExtTrapNonMaster

Description

The VRRP status changed between backup and initialize. (ifIndex=[ifIndex], VrId=[VrId], MasterIpAddr=[MasterIpAddr], sysName=[sysName], ifName=[ifName], CurrentState=[CurrentState], ChangeReason=[ChangeReason])

The VRRP status changed between Backup and Initialize.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwVrrpExtTrapNonMaster

Trap OID

1.3.6.1.4.1.2011.5.25.127.2.30.2

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 match trap.

Parameters

Parameter

Description

ifIndex

Index of the interface on which the VRRP backup group is configured

VrId

ID of the VRRP backup group

MasterIpAdd

IP address of the interface on which the VRRP backup group is configured

sysName

System name

ifName

Name of the interface on which the VRRP backup group is configured

CurrentState

VRRP status after the change. Possible values are as follows:

  • Initialize
  • Backup

ChangeReason

Reason of the VRRP status change.

VB

VB OID

VB Name

VB Index

1.3.6.1.2.1.68.1.3.1.8

vrrpOperPrimaryIpAddr

ifIndex

vrrpOperVrId

1.3.6.1.2.1.1.5

sysName

None

1.3.6.1.2.1.31.1.1.1.1

ifName

ifIndex

1.3.6.1.2.1.68.1.3.1.3

vrrpOperState

ifIndex

vrrpOperVrId

1.3.6.1.4.1.2011.5.25.127.1.7

hwVrrpExtStateChangeReasonString

None

Impact on the System
  • When the VRRP status changes from Backup to Initialize, services may be interrupted.
  • When the VRRP status changes from Initialize to Backup, services are not affected.
Possible Causes

Possible causes for the VRRP status change from Backup to Initialize are as follows:

  • Cause 1: The device on which the VRRP backup group is configured failed.
  • Cause 2: The interface on which the VRRP backup group is configured or its connected link failed.

Possible causes for the VRRP status change from Initialize to Backup are as follows:

  • Cause 1: The device on which the VRRP backup group is configured recovered.
  • Cause 2: The interface on which the VRRP backup group is configured or its connected link recovered.
Procedure
  1. Check whether the value of CurentState is Initialize or Backup.
  • If the value of CurentState is Initialize, go to Step 2.
  • If the value of CurentState is Backup, go to Step 6.
  1. Check whether the interface on which the VRRP backup group is configured or the link monitored by BFD that is associated with VRRP is Up.

    • If the interface on which the VRRP backup group is configured is Up, go to Step 3.
    • If the link monitored by BFD that is associated with VRRP is Up, go to Step 4.

  2. Run the display this interface command in the view of the interface on which the VRRP backup group is configured to check the physical and protocol statuses of the interface.

    • If the physical status of the interface is Down, the link connected to the interface fails. Rectify the fault and check whether the VRRP backup group has recovered.
      • If the VRRP backup group has recovered, go to Step 6.
      • If the VRRP backup group has not recovered, go to Step 5.
    • If the physical status of the interface is Up but its protocol status is Down, the IP address of the interface has been deleted. Reassign an IP address to the interface and check whether the VRRP backup group has recovered.
      • If the VRRP backup group has recovered, go to Step 6.
      • If the VRRP backup group has not recovered, go to Step 5.
    • If the physical and protocol statuses of the interface are both Up, the IP address of the interface is not on the same network segment as the virtual IP address of the VRRP backup group. Reassign an IP address to the interface and ensure that the IP address is on the same network segment as the virtual IP address of the VRRP backup group. Then check whether the VRRP backup group has recovered.
      • If the VRRP backup group has recovered, go to Step 6.
      • If the VRRP backup group has not recovered, go to Step 5.

  3. Run the display vrrp command and check whether the value of BFD-Session State in the command output is UP.

    • If the value of BFD-Session State in the command output is DOWN, the original standby link fails. Rectify the fault and check whether the VRRP backup group has recovered.
      • If the VRRP backup group has recovered, go to Step 6.
      • If the VRRP backup group has not recovered, go to Step 5.
    • If the value of BFD-Session State in the command output is UP, go to Step 5.

  4. Collect trap, log, and configuration information, and contact technical support personnel.
  5. End.
Translation
Download
Updated: 2018-08-16

Document ID: EDOC1000015902

Views: 215825

Downloads: 1596

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