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

S9300, S9300E, and S9300X V200R013C00

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

VRRP

VRRP_1.3.6.1.2.1.68.0.1 vrrpTrapNewMaster

Description

VRRP/2/VRRPCHANGETOMASTER:OID [oid] The status of VRRP changed to master. (VrrpIfIndex=[VrrpIfIndex], VrId=[VrId], IfIndex=[IfIndex], IPAddress=[IPAddress], NodeName=[NodeName], IfName=[IfName], ChangeReason=[ChangeReason])

The state of switch changed to master.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.2.1.68.0.1 Major environmentalAlarm(6)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VrrpIfIndex

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

VrId

ID of a VRRP backup group

IfIndex

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

IPAddress

IP address of the interface where a VRRP backup group is configured

NodeName

Device name

IfName

Name of the interface where a VRRP backup group is configured

ChangeReason

Cause for the change of the VRRP backup group status

Impact on the System

  • If master/backup switchover occurs in normal cases, services are not affected.

  • If master/backup switchover occurs in abnormal cases, services may be interrupted.

Possible Causes

Cause 1:

The former master switch was faulty.

Cause 2:

The former master link was faulty.

Cause 3:

The priority of the former master switch or backup switch changed.

Cause 4:

The logical interface where the VRRP backup group resides on the master switch is deleted or the configuration of the VRRP backup group is deleted.

Cause 5:

The former master switch recovers from a fault.

Cause 6:

The former active link recovers from a fault.

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

    • If the VRRP backup group is in the Initialize state, it indicates that the former switch is faulty. Locate the cause of the fault and restore the master switch. 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 switch and backup switch, 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.

VRRP_1.3.6.1.2.1.68.0.2 vrrpTrapAuthFailure

Description

VRRP/1/VRRPAUTHFAILED:OID [oid] VRRP failed to authentication. (IPAddress=[IPAddress], AuthErrorType=[AuthErrorType])

The authentication mode or authentication key of the received VRRP multicast packets was inconsistent with that of the local switch.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.2.1.68.0.2 Critical communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

IPAddress

IP address of the interface where a VRRP backup group is configured

AuthErrorType

Authentication failure types in the VRRP group.
  • 1: invalid authentication mode
  • 2: inconsistent authentication types on two devices in a VRRP backup group
  • 3: authentication failure

Impact on the System

The failure of the negotiation between the VRRP backup group may cause the services to be interrupted.

Possible Causes

Cause 1:

The authentication mode or authentication key of the received VRRP packets was inconsistent with that of the local switch.

Cause 2:

Authentication configured on one end is deleted.

Procedure

  1. Run the display vrrp command to view the Auth Type field and Auth Key field. Check whether the authentication type and key are configured to be the same on both devices in a VRRP backup group.

    • If not, configure the authentication type and key to be consistent. Go to Step 3.
    • If so, go to Step 2.

  2. Collect alarm information and configuration information, and then contact technical support personnel.
  3. End.

VRRP_1.3.6.1.4.1.2011.5.25.127.2.30.1 hwVrrpExtTrapMasterDown

Description

VRRP/2/VRRPMASTERDOWN:OID [oid] The state of VRRP changed from master to other state. (VrrpIfIndex=[VrrpIfIndex], VrId=[VrId], IfIndex=[IfIndex], IPAddress=[IPAddress], NodeName=[NodeName], IfName=[IfName], CurrentState=[CurrentState], ChangeReason=[ChangeReason])

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

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.127.2.30.1 Major communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VrrpIfIndex

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

VrId

ID of a VRRP backup group

IfIndex

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

IpAddress

Router id of the router where VRRP resides

NodeName

Device name

IfName

Name of the interface where a VRRP backup group is configured

CurrentState

VRRP backup group 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

Cause for the change of the VRRP backup group status

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

Cause 1:

The master switch was faulty.

Cause 2:

The active link was faulty.

Cause 3:

The priority of the VRRP backup group on the master switch or the slave switch changed.

Cause 4:

The logical interface where the VRRP backup group resides on the master switch is deleted or the configuration of the VRRP backup group is deleted.

Cause 5:

The former master switch recovers from a fault.

Cause 6:

The former active link recovers from a fault.

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.

  2. 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.
  3. Run the display vrrp command to check whether the set priorities of the VRRP backup group on the original master switch and backup switch 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.

  4. If the original master switch is faulty, locate the cause of the fault and restore the master switch.

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

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

  6. Run the display vrrp [ interface interface-type interface-number ] [virtual-router-id ] statistics 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.

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

  8. Collect alarm information and configuration information, and then contact technical support personnel.
  9. End.

VRRP_1.3.6.1.4.1.2011.5.25.127.2.30.2 hwVrrpExtTrapNonMaster

Description

VRRP/2/VRRPNONMASTER:OID [oid] The state of VRRP changed between backup and Initialize state. (VrrpIfIndex=[VrrpIfIndex], VrId=[VrId], IfIndex=[IfIndex], IPAddress=[IPAddress], NodeName=[NodeName], IfName=[IfName], CurrentState=[CurrentState], ChangeReason=[ChangeReason])

The status of a VRRP backup group changes from Backup to Initialize or from Initialize to Backup.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.127.2.30.2 Major communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VrrpIfIndex

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

VrId

ID of a VRRP backup group

IfIndex

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

IPAddress

IP address of the interface where a VRRP backup group is configured

NodeName

Device name

IfName

Name of the interface where a VRRP backup group is configured

CurrentState

VRRP backup group status after the change:
  • Initialize
  • Backup

ChangeReason

Cause for the change of the VRRP backup group status

Impact on the System

If the VRRP backup group status changes from Backup to Initialize, services may be interrupted.

If the VRRP backup group status changes from Initialize to Backup, services will not be affected.

Possible Causes

The possible causes for changing VRRP status from Backup to Initialize are as follows:
  • Cause 1: The device on which VRRP resides becomes faulty.

  • Cause 2: The interface or directly-connected link on which VRRP resides becomes faulty.

The possible causes for changing VRRP status from Initialize to Backup are as follows:
  • Cause 1: A fault on the device on which VRRP resides is rectified.

  • Cause 2: A fault on the interface or directly-connected link on which VRRP resides is rectified.

Procedure

  • Change the VRRP backup group status from Backup to Initialize.
    1. Check whether the device is functioning properly.

      • If the device is not functioning properly, go to step 3.
      • If the device is functioning properly, go to step 2.

    2. Run the display vrrp command to view the bound interface. Then run the display this interface command in the interface view to view the interface status.

      • If the interface is in the Up state, go to step 3.
      • If the interface is in the Down state, the interface or its directly connected link fails. After the interface or link fault is rectified, go to step 4.

    3. Collect alarm information and configuration information, and then contact technical support personnel.
    4. End.
  • Change the VRRP backup group status from Initialize to Backup.
    1. This trap message is informational only, and no action is required.

VRRP_1.3.6.1.2.1.207.0.1 vrrpv3NewMaster

Description

VRRP/2/VRRPV3CHANGETOMASTER:OID [oid] The status of VRRP changed to master. (VrrpIfIndex=[VrrpIfIndex], VrId=[VrId], InetAddrType=[InetAddrType], IPAddress=[IPAddress], ChangeReason=[ChangeReason])

This trap indicates that the sending agent has transitioned to 'Master' state.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.2.1.207.0.1 Major environmentalAlarm(6)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VrrpIfIndex

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

VrId

ID of a VRRP backup group

InetAddrType

IP address type supported by VRRP

IPAddress

IP address of the interface where a VRRP backup group is configured

ChangeReason

Cause for the change of the VRRP backup group status

Impact on the System

  • If a master/backup switchover occurs in normal cases, services are not affected.

  • If a master/backup switchover occurs in abnormal cases, services may be interrupted.

Possible Causes

Cause 1:

The former master switch was faulty.

Cause 2:

The former master link was faulty.

Cause 3:

The priority of the former master switch or backup switch changed.

Cause 4:

The logical interface where the VRRP backup group resides on the master switch is deleted or the configuration of the VRRP backup group is deleted.

Cause 5:

The former master switch recovers from a fault.

Cause 6:

The former active link recovers from a fault.

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

    • If the VRRP backup group is in the Initialize state, it indicates that the former switch is faulty. Locate the cause of the fault and restore the master switch. 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 VRRP is associated with a BFD session.

    • If VRRP is associated with a BFD session, go to Step 4.
    • If VRRP is not associated with a BFD session, 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 switch and backup switch, 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.

VRRP_1.3.6.1.2.1.207.0.2 vrrpv3ProtoError

Description

VRRP/2/VRRPV3PROTOERROR: OID [oid] VRRP received protocol error packet. (VrrpIfIndex=[INTEGER], VrId=[INTEGER], InetAddrType=[INTEGER], ProtoErrorType=[INTEGER])

The device in the VRRP backup group received an incorrect VRRP packet.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.2.1.207.0.2 Major environmentalAlarm(6)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VrrpIfIndex

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

VrId

ID of a VRRP backup group

InetAddrType

IP address type supported by VRRP

ProtoErrorType

Error type of the VRRP packet

Impact on the System

The device's processing performance is affected.

Possible Causes

The device received an incorrect VRRP packet.

Procedure

  1. Run the display vrrp [ interface interface-type interface-number ] [virtual-router-id ] statistics command to check the incorrect VRRP packet received by the device.
  2. Determine the type of the fault occurring on the peer device based on the type of the incorrect VRRP packet received by the device.
  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.
Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065855

Views: 4289

Downloads: 6

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