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).
UNI-TOPOMNG

UNI-TOPOMNG

UNI-TOPOMNG_1.3.6.1.4.1.2011.5.25.327.31.1.2.1 hwTopomngLinkNormal

Description

UNI-TOPOMNG/4/LINKNORMAL: OID [oid] A new link is normal. (SrcMAC=[OPAQUE], SrcPort=[STRING], SrcTrunk=[INTEGER], DstMAC=[OPAQUE], DstPort=[STRING], DstTrunk=[INTEGER], Reason=[STRING])

The status of the link between two SVF-enabled devices became normal.

Attribute

Alarm ID Alarm Severity Alarm Type
11.3.6.1.4.1.2011.5.25.327.31.1.2.1 Warning environmentalAlarm(6)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
SrcMAC Indicates the MAC address of the local device.
SrcPort Indicates the name of the local physical port.
SrcTrunk Indicates the name of the local Eth-Trunk.
DstMAC Indicates the MAC address of the peer device.
DstPort Indicates the name of the peer physical port.
DstTrunk Indicates the name of the peer Eth-Trunk.
Reason Indicates the alarm cause.

Impact on the System

None.

Possible Causes

The link between two SVF-enabled devices became normal or another link was added.

Procedure

  1. No action is required.

UNI-TOPOMNG_1.3.6.1.4.1.2011.5.25.327.31.1.2.2 hwTopomngLinkAbnormal

Description

UNI-TOPOMNG/4/LINKABNORMAL: OID [oid] A link is abnormal. (SrcMAC=[OPAQUE], SrcPort=[STRING], SrcTrunk=[INTEGER], DstMAC=[OPAQUE], DstPort=[STRING], DstTrunk=[INTEGER], Reason=[STRING])

The link between two SVF-enabled devices failed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.327.31.1.2.2 Warning environmentalAlarm(6)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
SrcMAC Indicates the MAC address of the local device.
SrcPort Indicates the name of the local physical port.
SrcTrunk Indicates the name of the local Eth-Trunk.
DstMAC Indicates the MAC address of the peer device.
DstPort Indicates the name of the peer physical port.
DstTrunk Indicates the name of the peer Eth-Trunk.
Reason Indicates the alarm cause:
  • Physical port down: A physical interface becomes Down.
  • Physical port up: A physical interface becomes Up.
  • Mbrmng protocol down: The neighbor discovery protocol is Down.
  • Mbrmng protocol up: The neighbor discovery protocol is Up.
  • Topology explore delay timeout: Topology collection times out.
  • System mac change: The device MAC address changes.
  • Uni-mng enable: SVF is enabled.
  • As Fault: An AS fault occurs.
  • As delete: An AS is deleted.
  • As normal: An AS recovers.
  • As link restart: An AS is restarted.

Impact on the System

ASs may go offline abnormally due to the link fault.

Possible Causes

The cable connecting the two SVF-enabled devices was removed or failed.

Procedure

  1. If ASs go offline normally, no action is required.
  2. The cable connecting the two SVF-enabled devices was faulty, rectify the fault based on the following causes:

    1. If the cause is "Physical port down", based on SrcPort in the alarm, check whether the cable connected to this port is loose or damaged or this port is shut down.
    2. If the cause is "Mbrmng protocol down", based on SrcTrunk in the alarm, run the display uni-mng interface fabric-port state command, find the corresponding Fabric state information, and rectify the fault according to Detail in the command output.
    3. If the cause is "Topology explore delay timeout", perform steps a and b. If the fault persists, go to step 3.
    4. If the cause is "System mac change", check whether the system MAC address of the local device changes. If it changes normally, this AS goes online again after a while. If the AS does not go online, perform step 3.
    5. If the cause is "As Fault", perform steps a and b. If the fault persists, go to step 3.
    6. If the cause is "As delete", run the display as all command to check whether the DstMAC field value in the alarm exists in the AS list. If not, check whether this AS is still required. If it is still required, add this AS again based on the configuration manual. If it is not required, ignore this alarm.
    7. If the cause is "As link restart", find the corresponding ASs based on SrcPort and DstPort in the alarm, wait for a while and then check whether the ASs can go online normally. If not, go to step 3.

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

Document ID: EDOC1100065855

Views: 3466

Downloads: 2

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