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

ETRUNK

ETRUNK_1.3.6.1.4.1.2011.5.25.178.2.1 hwETrunkStatusChange

Description

ETRUNK/4/TRAP_STATUS:OID [oid] The status of an E-Trunk changed.(Index=[integer], State=[integer], Reason=[integer])

The status change of an E-Trunk was advertised to the NMS.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.178.2.1 Warning equipmentAlarm(5)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

Index

Index of the E-Trunk

State

Status of the E-Trunk
  • initialize(1)

  • backup(2)

  • master(3)

Reason

Cause for the E-Trunk in such a status

Impact on the System

The system is not affected.

Possible Causes

1.

The priority of the E-Trunk was changed.

2.

The packet-receiving timer at the local device expired.

3.

BFD detected the fault on the control link between PEs.

Procedure

  1. Run the display e-trunk etrunk-id command to check the cause for the master/backup status switchover of the E-Trunk.

    • If the entry PRI(1) is displayed, indicating that the master/backup status is determined by the E-Trunk priority, go to Step 2.

    • If the entry TIMEOUT(2) is displayed, indicating that the local device becomes the master because it receives no protocol packets from the peer device within the timeout period, go to Step 3.

    • If the entry BFD_DOWN(3) is displayed, indicating that the local BFD detects the link-down event between the local device and the peer device, go to Step 4.

    • If the entry PEER_TIMEOUT(4) is displayed, indicating that the peer device becomes the master because it receives no protocol packets from the local device within the timeout period, go to Step 3.

    • If the entry PEER_BFD_DOWN(5) is displayed, indicating that the peer BFD detects the link-down event between the local device and the peer device, go to Step 4.

    • If the entry ALL_MEMBER_DOWN(6) is displayed, indicating that the two devices of an E-Trunk are Down, go to Step 4.

    • If the entry INIT(7) is displayed, indicating that the E-Trunk is being initialized, go to Step 5.

  2. Check whether the master/backup status of the E-Trunk is switched over according to user's requirement.

    • If so, go to Step 14.

    • If not, go to Step 6.

  3. Check whether the IP addresses of the E-Trunk local device and peer device are correctly configured.

    • If so, go to Step 7.

    • If not, go to Step 12.

  4. Check whether the E-Trunk interface is shut down.

    • If so, go to Step 8.

    • If not, go to Step 10.

  5. Check whether the E-Trunk is correctly initialized.

    • If so, go to Step 14.

    • If not, go to Step 13.

  6. Check whether the E-Trunk priority is changed according to the entries displayed in Step 1.

    • If so, go to Step 9.

    • If not, go to Step 13.

  7. Check whether the route between E-Trunk devices is reachable.

    • If so, go to Step 13.

    • If not, go to Step 10.

  8. Run the undo shutdown command in the interface view to check whether the trap is cleared.

    • If so, go to Step 14.

    • If not, go to Step 10.

  9. Check whether the E-Trunk priority is changed according to a legal requirement.

    • If so, go to Step 14.

    • If not, go to Step 11.

  10. Check whether the physical links are repaired, and the trap is cleared.

    • If so, go to Step 14.

    • If not, go to Step 13.

  11. Run the priority priority command in the E-Trunk view to correctly configure the E-Trunk priority according to the networking requirement, and then check whether the trap is cleared.

    • If so, go to Step 14.

    • If not, go to Step 13.

  12. Run the peer-address peer-ip-address source-address source-ip-address command in the E-Trunk view to correctly configure the IP addresses of the E-Trunk local device and peer device, and then check whether the trap 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.

Related Information

None

ETRUNK_1.3.6.1.4.1.2011.5.25.178.2.2 hwETrunkMemberStatusChange

Description

ETRUNK/4/TRAP_MEMBER_STATUS:OID [oid] The status of an E-Trunk member changed. (E-Trunk ID=[integer], Member type=[integer], Member ID=[integer], Member status=[integer], Status reason=[integer])

The status change of an E-Trunk member was advertised to the NMS.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.178.2.2 Warning equipmentAlarm(5)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

E-Trunk ID

ID of the E-Trunk to which the E-Trunk member belongs

Member type

Type of E-Trunk member. There is only one member type: Eth-Trunk.

Member ID

ID of the E-Trunk member

Member status

Status of the E-Trunk member

Status reason

Cause for the E-Trunk member in such a status

Impact on the System

If the local E-Trunk member is the master, the E-Trunk member can forward data.

If the local E-Trunk member is the backup, the E-Trunk member cannot forward data.

Possible Causes

1.

The status of the E-Trunk to which the local E-Trunk member belongs was changed.

2.

The peer of the E-Trunk member was faulty or recovered from a fault.

3.

The operating mode of the local E-Trunk member is changed.

Procedure

  1. Run the display e-trunk etrunk-id command to check whether the master/backup status is changed on the local end of the E-Trunk.

  2. Check whether the operating mode of the local E-Trunk member is changed.

    • If so, go to Step 5.

    • If not, go to Step 3.

  3. Check whether the E-Trunk interface is shut down.

    • If so, go to Step 7.

    • If not, go to Step 4.

  4. Check whether the physical links are repaired, and the trap is cleared.

    • If so, go to Step 9.

    • If not, go to Step 8.

  5. Check whether the operating mode of the local E-Trunk member is changed according to a legal requirement.

    • If so, go to Step 9.

    • If not, go to Step 8.

  6. Run the e-trunk mode { auto |force-master | force-backup } command in the Eth-Trunk interface view to correctly configure the operating mode of the Eth-Trunk in the E-Trunk according to the networking requirement. Then, check whether the trap is cleared.

    • If so, go to Step 9.

    • If not, go to Step 8.

  7. Run the undo shutdown command in the interface view to check whether the trap is cleared.

    • If so, go to Step 9.

    • If not, go to Step 4.

  8. Collect alarm information and configuration information, and then contact technical support personnel.
  9. End.
Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065855

Views: 3509

Downloads: 2

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