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 V200R010C00

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).
TRUNK_1.3.6.1.4.1.2011.5.25.41.3.41 hwExtTrunkWorkingStatusChange

TRUNK_1.3.6.1.4.1.2011.5.25.41.3.41 hwExtTrunkWorkingStatusChange

Description

TRUNK/4/TRUNK_WORKING_STATUS_CHANGE: OID [OID] The working status of the backup trunk changed. (TrunkIfIndex=[INTEGER], WorkingPortIndex=[INTEGER], TrunkName=[OCTET], WorkingPortName=[OCTET])

The working status of an Eth-Trunk interface in master/backup mode changed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.41.3.41 Warning communicationsAlarm(2)

Parameters

Name Meaning

OID

Indicates the MIB object ID of the alarm.

TrunkIndex

Index of an Eth-Trunk interface

WorkingPortIndex

Index of a working member interface

TrunkName

Name of an Eth-Trunk interface

WorkingPortName

Name of a working member interface

Impact on the System

Services will not be affected if an Eth-Trunk interface in master/backup mode performs a master/backup switchover. However, if the Eth-Trunk interface switches to the initializing state, services will be affected.

Possible Causes

Cause 1:

An Eth-Trunk interface in master/backup mode performed a master/backup switchover.

Cause 2:

An Eth-Trunk interface in master/backup mode became Down.

Procedure

  • Cause 1: An Eth-Trunk interface in master/backup mode performed a master/backup switchover.

    This trap message is informational only, and no action is required.

  • Cause 2: An Eth-Trunk interface in master/backup mode became Down.

    1. Run the display this command in the Eth-Trunk interface view to check whether the Eth-Trunk interface is shut down.
      • If the Eth-Trunk interface is shut down, go to Step 2.

      • If the Eth-Trunk interface is not shut down, go to Step 3.

    2. Run the undo shutdown command in the Eth-Trunk interface view and check whether the trap is cleared. If the trap persists, go to Step 3.
    3. Run the display trunkmembership eth-trunk trunk-id command to check whether the Eth-Trunk interface has member interfaces.
      • If the Eth-Trunk interface does not have member interfaces, go to Step 4.
      • If the Eth-Trunk interface has member interfaces, go to Step 5.
    4. Add interfaces to the Eth-Trunk interface in master/backup mode based on the networking topology and check whether the trap is cleared. If the trap persists, go to Step 5.
    5. Check whether all the Eth-Trunk member interfaces are Up.

      • If one or more member interfaces are Down, go to Step 6.
      • If all the member interfaces are Up, go to Step 10.
    6. Run the display this command in the Eth-Trunk member interface view to check whether the member interface is shut down.

      • If the member interface is not shut down, go to Step 8.
      • If the member interface is shut down, go to Step 7.
    7. Run the undo shutdown command in the Eth-Trunk member interface view and check whether the trap is cleared. If the trap persists, go to Step 8.

    8. Check whether the physical link status of the interface is normal and whether hardware such as the network cable or optical module looses or is disconnected.

      • If the physical link status of the interface is normal, go to Step 10.

      • If the physical link status of the interface is abnormal, go to Step 9.

    9. Correctly connect the physical link and check whether the trap is cleared. If the trap persists, go to Step 10.

    10. Collect alarm information and configuration information, and then contact technical support personnel.

Related Information

None

Translation
Download
Updated: 2019-08-21

Document ID: EDOC1000142054

Views: 191185

Downloads: 44

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