No relevant resource is found in the selected language.
Enterprise
Worldwide
Search
Support Documentation
S1700, S2720, S5700, and S6700 V200R019C10 Alarm Handling

This document provides the explanations, causes, and recommended actions of alarms on the product.

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

MBR

MBR_1.3.6.1.4.1.2011.5.25.327.31.3.2.1 hwUniMbrConnectError

Description

MBR/2/CONNECTERROR: OID [oid] Connection error on the fabric-port in unified management. (Reason=[STRING])

Cable connection on the fabric port was incorrect.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.327.31.3.2.1

Major

environmentalAlarm(6)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

Reason

Indicates the reason of incorrect cable connection. Reasons include the physical port number and peer AS MAC address involved in the cable connection. If the peer AS MAC address cannot be obtained, the MAC address displays --.

Impact on the System

ASs fail to go online due to the incorrect cable connection.

Possible Causes

The Reason parameter in an alarm describes the causes for the alarm:

  • Cause 1: There is a configuration file in the client.

    The AS has a startup configuration file.

  • Cause 2: Input has been detected in the client.

    Input exists on the console interface of an AS.

  • Cause 3: Port check failed.

    The AS attempts to connect to the parent through an unsupported port.

  • Cause 4: The fabric-port has already linked to a client.

    Member ports of the same downlink fabric port connect to two ASs.

  • Cause 5: The client has already linked to a father device.

    The AS connects to two parent switches.

  • Cause 6: The client has already linked to a fabric-port from current device.

    The uplink port of the AS connects to multiple fabric ports of the parent.

  • Cause 7: The fabric-port has been linked to another level-1 AS.

    The downlink fabric port of a level-1 AS connects to another level-1 AS.

  • Cause 8: The parent device has been linked to a level-2 AS.

    The parent directly connects to a level-2 AS.

  • Cause 9: The downstream fabric-port has been linked to another downstream fabric-port.

    A downlink fabric port of an AS connects to the parent.

  • Cause 10: The port has not received any response packets.

    The parent does not receive any response packet.

  • Cause 11: Create Trunk failed in the client.

    Failed to create an Eth-Trunk on an AS.

  • Cause 12: Port Bind Eth-Trunk failed in the client.

    Failed to add ports of an AS to an Eth-Trunk.

  • Cause 13: The switch has been in uni-mng system force mode.

    An AS has been configured to work in client mode.

  • Cause 14: The fabric-port has been linked to another parent device.

    The fabric port of the parent connects to another parent.

  • Cause 15: The current status of AS is busy.

    The system is busy on the AS.

  • Cause 16: The Layer 3 hardware forwarding mode has been enabled on the AS.

    Layer 3 hardware forwarding for IPv4 packets has been enabled using the assign forward-mode ipv4-hardware command on the AS.

  • Cause 17: The port cannot be added to the Eth-Trunk because the port has configurations on the AS.

    Configurations exist on the port of an AS.

  • Cause 18: A downstream port on the AS has been configured as a stack port.

    On the AS, its downlink service port is configured as a stack port.

  • Cause 19: The switch cannot be used as an AS because the assign trunk command has been run.

    SVF cannot be enabled because Eth-Trunk specifications have been increased on the AS.

  • Cause 20: The AS [STRING]s's port [STRING]s has been configured as a downstream fabric port.

    The AS port has been configured as a downstream fabric member port.

  • Cause 21: The level-1 AS's downlink fabric port mode conflicts with the level-1 AS mode.

    The level-1 AS uses the centralized mode, while the level-1 AS's downlink fabric port connecting to a level-2 AS has the independent mode configured, which conflicts with the centralized mode of the level-1 AS.

  • Cause 22: The mode configured for the parent is inconsistent with the mode of level-1 or level-2 ASs.

    The AS service configuration mode configured on the parent is inconsistent with the actual AS service configuration mode.

  • Cause 23: A VLAN has been created on the AS.

    The VLAN for VCMP or PNP exists on the AS.

Procedure

  • Cause 1: There is a configuration file in the client.

    Run the undo startup saved-configuration command in the system view to clear the startup configuration file and restart the AS.

  • Cause 2: Input has been detected in the client.

    After the AS is restarted, do not perform any operation on the serial port until the message "The switch has entered the uni-mng AS mode, and console port input is allowed." is displayed on the serial port.

  • Cause 3: Port check failed.

    Connect the AS to the parent through an uplink port or subcard port. Run the display port connection-type access all command to check all downlink ports on the AS.

  • Cause 4: The fabric-port has already linked to a client.

    Member ports of a downlink fabric port can connect to only one AS, and different ASs must connect to different fabric ports.

  • Cause 5: The client has already linked to a father device.

    Disconnect the AS from one parent switch.

  • Cause 6: The client has already linked to a fabric-port from current device.

    Retain the connection with only one fabric port and disconnect the AS from other fabric ports.

  • Cause 7: The fabric-port has been linked to another level-1 AS.

    Disconnect the two level-1 ASs from each other.

  • Cause 8: The parent device has been linked to a level-2 AS.

    Disconnect the parent from the level-2 AS.

  • Cause 9: The downstream fabric-port has been linked to another downstream fabric-port.

    Disconnect the fabric port of the AS from the parent.

  • Cause 10: The port has not received any response packets.

    Ensure that the parent is a Huawei switch that supports the SVF function. When the parent is an S5720-EI, delete its configuration file to ensure that it starts without configuration.

  • Cause 11: Create Trunk failed in the client.

    Disconnect the AS from the parent and then reconnect them.

  • Cause 12: Port Bind Eth-Trunk failed in the client.

    Disconnect the AS from the parent and then reconnect them.

  • Cause 13: The switch has been in uni-mng system force mode.

    On the parent, run the port connect-type indirect command to configure the indirect connection mode for the fabric port that connects to the AS. Alternative, run the undo uni-mng enable command on the AS and restart the AS to enable it exit from the client mode.

  • Cause 14: The fabric-port has been linked to another parent device.

    Disconnect the fabric port from the remote parent.

  • Cause 15: The current status of AS is busy.

    Wait until the AS is idle.

  • Cause 16: The Layer 3 hardware forwarding mode has been enabled on the AS.

    Run the undo assign forward-mode command to disable Layer 3 hardware forwarding for IPv4 packets.

  • Cause 17: The port cannot be added to the Eth-Trunk because the port has configurations on the AS.

    Delete the configurations of the port.

  • Cause 18: A downstream port on the AS has been configured as a stack port.

    Clear the stack configuration of the downlink service port.

  • Cause 19: The switch cannot be used as an AS because the assign trunk command has been run.

    Run the undo assign trunk command to restore the default Eth-Trunk specifications and then enable SVF.

  • Cause 20: The AS [STRING]s's port [STRING]s has been configured as a downstream fabric port.

    Delete the member port configuration or use another port to replace the AS port for configuration.

  • Cause 21: The level-1 AS's downlink fabric port mode conflicts with the level-1 AS mode.

    Run the undo port connect command to change the service configuration mode of the downlink fabric port to centralized mode.

  • Cause 22: The mode configured for the parent is inconsistent with the mode of level-1 or level-2 ASs.

    Ensure that the AS service configuration mode configured on the parent is consistent with the actual AS service configuration mode.

  • Cause 23: A VLAN has been created on the AS.

    Run the reset vcmp or undo pnp startup-vlan command in user view on the AS to restart the AS.

MBR_1.3.6.1.4.1.2011.5.25.327.31.3.2.2 hwUniMbrASDiscoverAttack

Description

MBR/1/ASDISCOVERYATTACK: OID [oid] An AS discover packet attack is detected. (DeviceName=[OCTET], ASIndex=[INTEGER], Interface=[STRING], Rate(pps)=[INTEGER])

A fabric port was attacked by AS Discovery packets.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.327.31.3.2.2 Critical environmentalAlarm(6)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
DeviceName Indicates the device name.
ASIndex Indicates the AS index.
Interface Indicates the name of the local port.
Rate(pps) Indicates the rate at which AS Discovery packets are received.

Impact on the System

The fabric port may not change to Up state and ASs may not go online.

Possible Causes

Unauthorized users sent a large number of AS Discovery packets to the fabric port.

Procedure

  1. Obtain the device name and local connection port of the unauthorized user.

    1. DeviceName in the alarm indicates the unauthorized device name.
    2. Interface in the alarm indicates the local connection port name.

  2. Disconnect the unauthorized user from the fabric port.

    1. Run the display lldp neighbor brief command and find the topology in which the unauthorized user connects to the parent based on the local port name, local device name, and unauthorized device name.
    2. Remove this unauthorized device based on the topology.

Related Information

None.

MBR_1.3.6.1.4.1.2011.5.25.327.31.3.2.3 hwUniMbrFabricPortMemberDelete

Description

MBR/4/FABRICPORTMEMDEL: OID [oid] The member port cancel from fabric-port. (LocalDeviceName=[STRING], LocalASIndex=[INTEGER], LocalInterfaceName=[STRING])

A member port was removed from the fabric port.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
LocalDeviceName Indicates the name of the local device.
LocalASIndex Indicates the index of the local AS.
NOTE:

When the value of LocalASIndex is 4294967295 (0xFFFFFFFF), it indicates the parent switch.

LocalInterfaceName Indicates the name of the local port.

Impact on the System

If all member ports in a fabric port are deleted, ASs go offline.

Possible Causes

The administrator deleted a member port in the fabric port.

Procedure

  1. No action is required.

Related Information

None.

MBR_1.3.6.1.4.1.2011.5.25.327.31.3.2.4 hwUniMbrIllegalFabricConfig

Description

MBR/2/ILLEGALFABRICCONFIG: OID [oid] The AS has downstream fabric-port(s) configured improperly. (ASDeviceName=[STRING], ASIndex=[INTEGER], Reason=[STRING])

An invalid downlink fabric port is pre-configured on the parent for the AS.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.327.31.3.2.4

Major

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

ASDeviceName

Indicates the AS name.

ASIndex

Indicates the AS index.

Reason

Indicates invalid configuration.

Impact on the System

The configured invalid downlink fabric port does not take effect but the number of valid fabric ports is reduced.

Possible Causes

  1. Reason=Downstream fabric-ports [STRING] have been configured on the level-2 AS.

    The member port of this downlink fabric port resides on a level-2 AS.

  2. Reason=Downstream fabric-ports [STRING] have been configured on the indirect AS.

    The member port of the downlink fabric port resides on an indirectly connected AS.

  3. Reason=The downlink port [STRING] has been configured as a stack port.

    The member port of the downlink fabric port has been configured as a stack port.

  4. Reason=The downlink port [STRING] has been negotiated as an uplink fabric-port.

    The member port of the downlink fabric port has been negotiated as a member port of an uplink fabric port.

  5. Reason=The port [STRING] can not be added to the Eth-Trunk[INTEGER] because the port has other configurations on the independent AS.

    The member port of the downlink fabric port has other configurations. As a result, this member port cannot be added to the fabric port.

  6. Reason=The port [STRING] can not be added to the Eth-Trunk[INTEGER] because the port is the member port of another Eth-Trunk on the independent AS.

    The member port of the downlink fabric port has been added to another Eth-Trunk or fabric port.

  7. Reason=The port [STRING] can not be added to the Eth-Trunk[INTEGER] because the port type is different from the member port of the Eth-Trunk on the independent AS.

    The type of the member port of the downlink fabric port is different from the type of other member ports of this fabric port.

  8. Reason=The port [STRING] can not be added to the Eth-Trunk[INTEGER] because the number of member ports in the Eth-Trunk has reached the maximum value on the independent AS.

    The number of member ports of the downlink fabric has reached the maximum value. As a result, this member port cannot be added to the fabric port.

Procedure

  1. Run the undo interface fabric-port port-id command to delete the invalid fabric port.

Related Information

None

MBR_1.3.6.1.4.1.2011.5.25.327.31.3.2.5 hwUniMbrAsServiceAbnormal

Description

MBR/4/ASSERVICEABNORMAL: OID [oid] The service abnormal on AS. (ASDeviceName=[STRING], ASIndex=[INTEGER], Description=[STRING])

Services on an AS become abnormal.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.327.31.3.2.5

Warning

qualityOfServiceAlarm (3)

Parameters

Name Meaning

oid

Indicates the ID of the alarm MIB object.

ASDeviceName

Indicates the name of as AS.

ASIndex

Indicates the index of an AS.

Description

Indicates the alarm description of an AS.

Impact on the System

Some commands delivered from the parent to this AS do not take effect. The AS needs to return the service error information to the parent and corresponding alarms need to be generated on the parent.

Possible Causes

  • The Description field in the alarm information describes MAC services:

    • Description=MAC address information. (Information=Type-Ifindex-Vlaninvalid-Vlanid-Mac-address).

      The MAC address changed.

    • Description=MAC move detected. (VlanId=[INTEGER], MacAddress=[STRING], Original-Port=[STRING], Flapping port=[STRING] and [STRING]).

      The MAC address in the VLAN flapped.

    • Description=MAC move detected. (VSI-Name=[STRING], MacAddress=[STRING], Original-Port=[STRING], Flapping port=[STRING]).

      The MAC address in the VSI flapped.

    • Description=MAC move detected. (Bridge-domain ID=[INTEGER], Original-port=[STRING], Flapping-port 1=[STRING], Flapping-port 2=[STRING], MacAddress=[STRING]).

      The MAC address in the BD domain flapped.

    • Description=The port was removed from the VLAN due to MAC flapping. (InterfaceName=[STRING], VLAN=[INTEGER]).

      MAC address flapping caused the port to be removed from the VLAN.

    • Description=The port is added to the VLAN again after it was removed from the VLAN due to MAC flapping. (InterfaceName=[STRING], VLAN=[INTEGER]).

      The port that was removed from the VLAN due to MAC flapping is added to the VLAN again.

  • The Description field in the alarm information describes port security services:

    • Description=The number of sticky or secure MAC address reaches the max.

      The number of sticky or secure MAC addresses learned by the device reached the maximum value.

    • Description=The port received an insecure MAC address. (MacAddress=[STRING], VLAN=[INTEGER], InterfaceName=[STRING], PortStatus=[INTEGER] (1:restrict;2:protect;3:error-down)).

      The port received packets with a new MAC address after the number of secure MAC addresses on the port exceeded the limit.

    • Description=The port received a packet with a flapping static MAC. (MacAddress=[STRING], VLAN=[INTEGER], InterfaceName=[STRING]).

      The source MAC address in the packet received by the interface already exists in the static MAC address table of another interface.

  • The Description field in the alarm information describes store control services:

    • Description=Storm-control alarm. (IfIndex=[STRING], IfName=[STRING], Action=[STRING], Interval=[STRING], Status=[STRING]).

      After store control was configured, the rate of broadcast, unknown multicast, and unknown unicast packets received on the interface within a detection interval exceeded the configured maximum limit.

  • The Description field in the alarm information describes voice VLAN services.

    • Description=Configure the organizationally unique identifier (OUI) address of the voice VLAN: MAC address=[STRING], mask=[STRING] failed because of no enough resources or hash collision.

      The voice-vlan mac-address mac-address mask oui-mask command used to configure an OUI for a voice VLAN does not take effect.

    • Description=Configure the 802.1p priority or DSCP value for a voice VLAN: 802.1p=[STRING], DSCP=[STRING] failed because of no enough resources or hash collision.

      The voice-vlan remark { 8021p 8021p-value| dscp dscp-value } command used to configure the 802.1p priority or DSCP priority for a voice VLAN does not take effect.

    • Description=Configure VLAN [STRING] as a voice VLAN and enable the voice VLAN function on [STRING] failed because of no enough resources or hash collision.

      The voice-vlan vlan-id enable [ include-untagged | include-tag0 ] command used to enable a voice VLAN does not take effect.

    • Description=Enable CDP-compatible LLDP on [STRING] failed because of no enough resources or hash collision.

      The voice-vlan legacy enable command used to configure a voice VLAN to be compatible with CDP does not take effect.

    • Description=Configure the voice VLAN to work in auto mode on [STRING] failed because of no enough resources or hash collision.

      The voice-vlan mode auto command used to configure a voice VLAN to work in automatic mode on an interface does not take effect.

    • Description=Configure the voice VLAN to work in manual mode on [STRING] failed because of no enough resources or hash collision.

      The voice-vlan mode manual command used to configure a voice VLAN to work in manual mode on an interface does not take effect.

    • Description=Enable the secure mode of the voice VLAN on [STRING] failed because of no enough resources or hash collision.

      The voice-vlan security enable command used to configure a voice VLAN to work in security mode does not take effect.

    • Description=Disable the secure mode of the voice VLAN on [STRING] failed because of no enough resources or hash collision.

      The undo voice-vlan security enable command used to configure a voice VLAN to work in normal mode does not take effect.

    • Description=Configure [STRING] to increase the priority of voice packets based on MAC addresses failed because of no enough resources or hash collision.

      The voice-vlan remark-mode mac-address command used to configure the switch to increase the priority of voice packets based on MAC addresses does not take effect.

    • Description=Configure [STRING] to increase the priority of voice packets based on VLAN IDs failed because of no enough resources or hash collision.

      The voice-vlan remark-mode vlan command used to configure the switch to increase the priority of voice packets based on VLAN IDs does not take effect.

    • Description=Add [STRING] to Eth-Trunk [STRING] failed because of no enough resources or hash collision.

      Failed to add an interface to an Eth-Trunk.

  • The Description field in the alarm information describes SACL services.

    • Description=Fail to apply SACL 'traffic-filter inbound acl [STRING]', insufficient rule resource on slot [STRING] globally.

      ACL resources are insufficient.

    • Description=Fail to apply SACL 'traffic-filter inbound acl [STRING]', insufficient slice resource on slot [STRING] globally.

      Slice resources are insufficient.

    • Description=Fail to apply SACL 'traffic-limit inbound acl [STRING]', insufficient counter resource on slot [STRING] globally.

      Counter resources are insufficient.

    • Description=Fail to apply SACL 'traffic-limit inbound acl [STRING]', insufficient meter resource on slot [STRING] globally.

      Meter resources are insufficient.

    • Description=Fail to apply SACL 'traffic-filter inbound acl [STRING]', insufficient UDF resource on slot [STRING] globally.

      UDF resources are insufficient.

    • Description=Fail to apply SACL 'port add-tag acl [STRING]', there is conflict between action "remark vlan-id" and "add-tag" on interface [STRING] of slot [STRING].

      A configuration conflict occurs.

  • The Description field in the alarm information describes MQC services.

    • Description=Add rule failed. Insufficient rule resource in policy [STRING] classifier [STRING] behavior [STRING] acl [STRING], rule [STRING] on slot [STRING] globally.

      ACL resources are insufficient.

    • Description=Add rule failed. Insufficient slice resource in policy [STRING] classifier [STRING] behavior [STRING] acl [STRING], rule [STRING] on slot [STRING] globally.

      Slice resources are insufficient.

    • Description=Add rule failed. Insufficient counter resource in policy [STRING] classifier [STRING] behavior [STRING] acl [STRING], rule [STRING]on slot [STRING] globally.

      Counter resources are insufficient.

    • Description=Add rule failed. Insufficient meter resource in policy [STRING] classifier [STRING] behavior [STRING] acl [STRING], rule [STRING] on slot [STRING] globally.

      Meter resources are insufficient.

    • Description=Add rule failed. Insufficient UDF resource in policy [STRING] classifier [STRING] behavior [STRING] acl [STRING], rule [STRING] on slot [STRING] globally.

      UDF resources are insufficient.

    • Description=Add rule failed, remark vlan can not be configured together with add-tag in current view or direction about policy [STRING], class [STRING], behavior [STRING] on slot [STRING] globally.

      A configuration conflict occurs.

Procedure

  1. Determine the service module to which the alarm is related based on the Description field in this alarm.

    • The alarm is related to MAC services.
      • If the MAC address changed, rectify the fault according to hwMacTrapAlarm.
      • If the MAC address in a VLAN flapped, rectify the fault according to hwMflpVlanAlarm.
      • If the MAC address in a VSI flapped, rectify the fault according to hwMflpVsiAlarm.
      • If the MAC address in a BD domain flapped, rectify the fault according to hwMflpBdAlarm.
      • If the port was removed from the VLAN due to MAC address flapping, rectify the fault according to hwMflpQuitVlanAlarm.
      • The port that was removed from the VLAN due to MAC flapping is added to the VLAN again. This alarm is informational, and no action is required.
    • The alarm is related to port security services.
      • If the number of sticky or secure MAC addresses learned by the device reached the maximum value, rectify the fault according to hwPortStickyReachMaxAlarm.
      • If the port received packets with a new MAC address after the number of secure MAC addresses on the port exceeded the limit, rectify the fault according to hwPortSecRcvInsecurePktAlarm.
      • If the source MAC address in the packet received by the interface already exists in the static MAC address table of another interface, rectify the fault according to hwPortsecStaticFlpAlarm.
    • If the alarm is related to storm control services, run the display storm-control [ interface interface-type interface-number ] command to check the storm control configuration on the specified interface. Determine whether to cancel or change the storm control configuration based on service requirements. To change the configuration or threshold, run the storm-control command.
    • If the alarm is related to voice VLAN services, modify the configuration command based on the alarm cause. For example, in case of "Description=Enable CDP-compatible LLDP on [STRING] failed because of no enough resources or hash collision", you can run the undo voice-vlan legacy enable command.
    • If the alarm indicates insufficient resources of the SACL or MQC service, run the display acl resource command to check resources and then delete unnecessary services to release ACL resources. For example, in case of "Description=Fail to apply SACL 'traffic-limit inbound acl [STRING]', insufficient counter resource on slot [STRING] globally", you can run the display acl resource command to check the Counter field, delete unnecessary services to release ACL resources, and then reconfigure the command that needs to be delivered.
    • If the alarm is related to the SACL or MQC configuration, modify the configuration based on the specific alarm information. For example, in case of "Description=Add rule failed, remark vlan can not be configured together with add-tag in current view or direction about policy [STRING], class [STRING], behavior [STRING] on slot [STRING] globally", modify the configuration based on the alarm information that remark vlan-id vlan-id and add-tag vlan-id vlan-id cannot be configured together.

      There are a large number of SACL or MQC-related configuration conflict alarms. For details about the troubleshooting procedure, see the specific alarm description.

  2. Collect alarm, log, and configuration information, and contact technical support personnel.

Related Information

None

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.2.1 hwASBrdTempAlarm

Description

MBR/1/ASBRDTEMPALARM: OID [oid] Temperature rise over or fall below the warning alarm threshold. (ASName=[OCTET], ASIndex=[INTEGER], Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityThresholdType=[INTEGER], EntityThresholdValue=[INTEGER], EntityThresholdCurrent=[INTEGER], EntityTrapFaultID=[INTEGER])

The temperature of the AS exceeded the upper threshold or fell below the lower threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.327.31.6.2.2.1 Critical equipmentAlarm(5)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.
Index Indicates the entity index.
EntityPhysicalIndex Indicates the entity index.
PhysicalName Indicates the entity name.
EntityThresholdType Indicates the alarm threshold type.
EntityThresholdValue Indicates the temperature threshold.
EntityThresholdCurrent Indicates the current temperature.
EntityTrapFaultID Indicates the error code.

Impact on the System

When the temperature exceeds the upper threshold or falls below the lower threshold, the device may not work properly and packet loss may occur. Or more seriously, the device may be suspended or reset abnormally.

Possible Causes

Cause 1: Fans were not present in the chassis or failed.

Cause 2: The ambient temperature was too low or high.

Procedure

  1. Run the display temperature { all | slot slot-id } command to check whether the ambient temperature is too low or high.

    • If the temperature is too low, take proper measures to increase the temperature, for example, increase the air conditioner temperature.
    • If the temperature is too high, take proper measures to lower the temperature, for example, lower the air conditioner temperature and ventilate the equipment room. If the fault persists, go to step 2.

  2. Check whether the device temperature is within the acceptable range.
    • If so, run the temperature threshold slot { slot-id | all } lower-limit min-temperature upper-limit max-temperature command to change the temperature alarm threshold.
    • If not, go to step 3.
  3. Check whether the device has a fan module.

    • If so, go to step 4.
    • If not, install a fan module.

  4. Run the display device command to check whether the fan module works properly.

    • If so, go to step 5.
    • If not, remove and reinstall the fan module. If the fault persists, replace the fan module.

  5. Check whether the alarm is cleared.

    • If so, the alarm handling ends.
    • If not, collect alarm information and configuration information, and then contact technical support personnel.

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.2.2 hwASBrdTempResume

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.2.2 hwASBrdTempResume

Description

MBR/4/ASBRDTEMPRESUME: OID [oid] Temperature is restored to the normal range. (ASName=[OCTET], ASIndex=[INTEGER], Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityThresholdType=[INTEGER], EntityThresholdValue=[INTEGER], EntityThresholdCurrent=[INTEGER], EntityTrapFaultID=[INTEGER])

The temperature of the AS restored to the normal range.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.
Index Indicates the entity index.
EntityPhysicalIndex Indicates the entity index.
PhysicalName Indicates the entity name.
EntityThresholdType Indicates the alarm threshold type.
EntityThresholdValue Indicates the temperature threshold.
EntityThresholdCurrent Indicates the current temperature.
EntityTrapFaultID Indicates the error code.

Impact on the System

None.

Possible Causes

The temperature of the AS restored to the normal range.

Procedure

  1. No action is required.

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.2.1 hwASBrdTempAlarm

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.3.1 hwASBoardFail

Description

MBR/2/ASBRDFAIL: OID [oid] Board become failure for some reason. (ASName=[OCTET], ASIndex=[INTEGER], Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityTrapEntType=[INTEGER], EntityTrapFaultID=[INTEGER])

An AS card experienced a partial failure.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.327.31.6.2.3.1 Major equipmentAlarm(5)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.
Index Indicates the entity index.
EntityPhysicalIndex Indicates the entity index.
PhysicalName Indicates the entity name.
EntityTrapEntType Indicates the entity type.
EntityTrapFaultID Indicates the error code.

Impact on the System

The card may fail to work or some of its functions are unavailable. Services on the card may be interrupted.

Possible Causes

View the description in the ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.3 hwBoardFail alarm based on the error code.

Procedure

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.3.2 hwASBoardFailResume

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.3.2 hwASBoardFailResume

Description

MBR/4/ASBRDFAILRESUME: OID [oid] Board resume from failure. (ASName=[OCTET], ASIndex=[INTEGER], Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityTrapEntType=[INTEGER], EntityTrapFaultID=[INTEGER])

An AS card recovered from a partial failure.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.
Index Indicates the entity index.
EntityPhysicalIndex Indicates the entity index.
PhysicalName Indicates the entity name.
EntityTrapEntType Indicates the entity type.
EntityTrapFaultID Indicates the error code.

Impact on the System

None.

Possible Causes

The AS card recovered from a partial failure.

Procedure

  1. No action is required.

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.3.1 hwASBoardFail

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.4.1 hwASOpticalInvalid

Description

MBR/3/ASOPTINVALID: OID [oid] Optical Module is invalid. (ASName=[OCTET], ASIndex=[INTEGER], Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityTrapFaultID=[INTEGER])

An optical module on the AS failed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.327.31.6.2.4.1 Minor equipmentAlarm(5)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.
Index Indicates the entity index.
EntityPhysicalIndex Indicates the entity index.
PhysicalName Indicates the entity name.
EntityTrapFaultID Indicates the error code.

Impact on the System

The optical module may fail to work. Services may be interrupted on the port that has the optical module installed.

Possible Causes

Cause 1: The optical module is a non-Huawei-customized optical module. The error code is 136192.

Cause 2: The transmit optical power of the optical module was too high. The error code is 136193.

Cause 3: The transmit optical power of the optical module was too low. The error code is 136194.

Cause 4: The receive optical power of the optical module was too high. The error code is 136195.

Cause 5: The receive optical power of the optical module was too low. The error code is 136196.

Procedure

  • Cause 1: The optical module is a non-Huawei-customized optical module. The error code is 136192.
    1. If this optical module was early delivered from Huawei, run the transceiver phony-alarm-disable command to disable the alarm function for non-Huawei-customized optical modules.
    2. If this optical module is not delivered from Huawei or is not customized for Huawei, replace it with a Huawei-customized optical module.
  • Cause 2: The transmit optical power of the optical module was too high. The error code is 136193.
    1. Run the display transceiver slot slot-id verbose command in the system view to check whether the transmit power Tx Power of the optical module is within the allowed range.

      • If so, services are not affected. Collect alarms, logs, and configurations and contact technical support personnel.
      • If not, go to step 2.

    2. Check whether the transmit power upper threshold of the optical module is within the acceptable range.

      • If so, run the transceiver diagnosis threshold tx-power command to change the transmit power upper threshold of the optical module. The alarm handling ends.
      • If not, go to step 3.

    3. Use an optical attenuator to reduce the transmit power of the optical module to the acceptable range. Check whether the alarm is cleared.

      • If so, the alarm handling ends.
      • If not, go to step 4.

    4. Replace the optical module, and check whether the alarm is cleared.

      • If so, the alarm handling ends.
      • If not, collect alarms, logs, and configurations, and contact technical support personnel.

  • Cause 3: The transmit optical power of the optical module was too low. The error code is 136194.
    1. Run the display transceiver slot slot-id verbose command in the system view to check whether the transmit power Tx Power of the optical module is within the allowed range.

      • If so, services are not affected. Collect alarms, logs, and configurations and contact technical support personnel.
      • If not, go to step 2.

    2. Check whether the transmit power lower threshold of the optical module is within the acceptable range.

      • If so, run the transceiver diagnosis threshold tx-power command to change the transmit power lower threshold of the optical module. The alarm handling ends.
      • If not, go to step 3.

    3. Replace the optical module, and check whether the alarm is cleared.

      • If so, the alarm handling ends.
      • If not, collect alarms, logs, and configurations, and contact technical support personnel.

  • Cause 4: The receive optical power of the optical module was too high. The error code is 136195.
    1. Run the display transceiver slot slot-id verbose command in the system view to check whether the receive power Rx Power of the optical module is within the allowed range.

      • If so, collect alarms, logs, and configurations, and contact technical support personnel.
      • If not, go to step 2.

    2. Check whether the receive power of the optical module is within a usable range.

      • If so, run the transceiver diagnosis threshold rx-power command to change the receive power upper threshold of the optical module. The alarm handling ends.
      • If not, go to step 3.

    3. Check whether an alarm is generated for high transmit power on the peer optical module. If so, rectify the peer optical module fault first.
    4. Check whether the peer optical module and the local optical module are of the same type. If not, replace the local optical module with a new one to ensure they are of the same type.
    5. Add -5 dBm (recommended) attenuators to the optical module.
    6. If the problem persists after the preceding steps, collect alarms, logs, and configurations, and contact technical support personnel.
  • Cause 5: The receive optical power of the optical module was too low. The error code is 136196.
    1. Run the display transceiverslot slot-id verbose command in the system view to check whether the receive power Rx Power of the local interface is within the acceptable range.

      • If so, collect alarms, logs, and configurations, and contact technical support personnel.
      • If not, go to step 2.

    2. Check whether the receive power of the optical module is within a usable range.

      • If so, run the transceiver diagnosis threshold rx-power command to change the receive power lower threshold of the optical module. The alarm handling ends.
      • If not, go to step 3.

    3. Check whether the peer port is physically Up and whether there is no alarm indicating that the transmit power is too low.

      • If so, perform an external loopback test on the interface. If the interface is in Up state, perform loopback tests on the nodes along the transmission path to locate the failure point or link. Then check whether the alarm is cleared. If not, go to 4.
      • If not, go to step 4.

    4. Check whether the peer port is physically Down and a corresponding alarm is generated, rectify the fault on the peer port.

      • If so, repair the pee port. Check whether the alarm is cleared. If not, go to step 5.
      • If not, go to step 5.

    5. Test whether the fiber is working normally.

      • If so, replace the fiber and check whether the alarm is cleared. If not, go to step 6.
      • If not, go to step 6.

    6. Replace the optical module of the local port and check whether the alarm is cleared.

      • If so, the alarm handling ends.
      • If not, go to step 7.

    7. Collect alarms, logs, and configurations, and contact technical support personnel.

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.4.2 hwASOpticalInvalidResume

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.4.2 hwASOpticalInvalidResume

Description

MBR/4/ASOPTINVALIDRESUME: OID [oid] Optical Module resume from invalid situation. (ASName=[OCTET], ASIndex=[INTEGER], Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityTrapFaultID=[INTEGER])

A faulty optical module on the AS recovered.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.
Index Indicates the entity index.
EntityPhysicalIndex Indicates the entity index.
PhysicalName Indicates the entity name.
EntityTrapFaultID Indicates the error code.

Impact on the System

None.

Possible Causes

The faulty optical module recovered.

Procedure

  1. No action is required.

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.4.1 hwASOpticalInvalid

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.5.1 hwASPowerRemove

Description

MBR/4/ASPOWERREMOVE: OID [oid] Power is absent. (ASName=[OCTET], ASIndex=[INTEGER], Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityTrapFaultID=[INTEGER])

A power module was removed from the AS.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.
Index Indicates the entity index.
EntityPhysicalIndex Indicates the entity index.
PhysicalName Indicates the entity name.
EntityTrapFaultID Indicates the error code.

Impact on the System

The device may not work properly due to lack of power.

Possible Causes

The power module was removed.

Procedure

  1. Check whether the power module is installed in the slot.

    • If so, go to step 2.
    • If not, install the power module in the slot.

  2. Run the display device command to check whether the power module is working properly.

    • If so, but the alarm persists, replace the power module.
    • If not, install the power module securely.

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.5.2 hwASPowerInsert

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.5.2 hwASPowerInsert

Description

MBR/4/ASPOWERINSERT: OID [oid] Power is present. (ASName=[OCTET], ASIndex=[INTEGER], Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityTrapFaultID=[INTEGER])

A power module was installed on the AS.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.
Index Indicates the entity index.
EntityPhysicalIndex Indicates the entity index.
PhysicalName Indicates the entity name.
EntityTrapFaultID Indicates the error code.

Impact on the System

None.

Possible Causes

The power module was installed on the AS.

Procedure

  1. No action is required.

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.5.1 hwASPowerRemove

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.5.3 hwASPowerInvalid

Description

MBR/1/ASPOWERINV: OID [oid] Power is invalid for some reason. (ASName=[OCTET], ASIndex=[INTEGER], Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityTrapFaultID=[INTEGER])

A power module on the AS completely failed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.327.31.6.2.5.3 Critical equipmentAlarm(5)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.
Index Indicates the entity index.
EntityPhysicalIndex Indicates the entity index.
PhysicalName Indicates the entity name.
EntityTrapFaultID Indicates the error code.

Impact on the System

The device may not be powered on due to lack of power, and cannot work. The fault should be rectified quickly.

Possible Causes

Cause 1: The power module failed. The error code is 136961.

Cause 2: The power module was installed but not powered on. The error code is 136966.

Cause 3: The type of the PoE power module was incorrect. The error code is 136972.

Cause 4: The power module configuration is incorrect. The error code is 136973.

Procedure

  • Cause 1: The power module failed. The error code is 136961.
    1. Replace the power module.
  • Cause 2: The power module was installed but not powered on. The error code is 136966.
    1. Power on the power module.
  • Cause 3: The type of the PoE power module was incorrect. The error code is 136972.
    1. Check whether a DC power module is installed in the PoE power module slot. If so, replace it with an AC power module.
    2. If an AC power module is installed in the PoE power module slot, the power module may fail. Contact technical support personnel.
  • Cause 4: The power module configuration is incorrect. The error code is 136973.
    1. Check whether the power module works properly.
    2. Check whether the required power module is installed.
    3. If the power module configuration is correct but the alarm persists, contact technical support personnel.

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.5.4 hwASPowerInvalidResume

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.5.4 hwASPowerInvalidResume

Description

MBR/4/ASPOWERINVRESUME: OID [oid] Power resume from invalid situation. (ASName=[OCTET], ASIndex=[INTEGER], Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityTrapFaultID=[INTEGER])

A power module on the AS recovered from a complete failure.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.
Index Indicates the entity index.
EntityPhysicalIndex Indicates the entity index.
PhysicalName Indicates the entity name.
EntityTrapFaultID Indicates the error code.

Impact on the System

None.

Possible Causes

The power module on the AS recovered from a complete failure.

Procedure

  1. No action is required.

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.5.3 hwASPowerInvalid

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.6.1 hwASFanRemove

Description

MBR/4/ASFANREMOVE: OID [oid] Fan has been removed. (ASName=[OCTET], ASIndex=[INTEGER], Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityTrapFaultID=[INTEGER])

A fan module on the AS was removed or not installed properly.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.
Index Indicates the entity index.
EntityPhysicalIndex Indicates the entity index.
PhysicalName Indicates the entity name.
EntityTrapFaultID Indicates the error code.

Impact on the System

The fan module fault affects heat dissipation performance of the device and increases the device temperature. Services are not affected in a short time, but the fault should be rectified quickly.

Possible Causes

The fan module was removed or not installed properly.

Procedure

  1. Check whether the fan module needs to be removed.

    • If so, the alarm handling ends.
    • If not, install the fan module.

  2. Check whether the fan module is installed properly.

    • If so, replace it.
    • If not, install it securely.

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.6.2 hwASFanInsert

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.6.2 hwASFanInsert

Description

MBR/4/ASFANINSERT: OID [oid] Fan has been inserted. (ASName=[OCTET], ASIndex=[INTEGER], Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityTrapFaultID=[INTEGER])

A fan module was installed on the AS.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.
Index Indicates the entity index.
EntityPhysicalIndex Indicates the entity index.
PhysicalName Indicates the entity name.
EntityTrapFaultID Indicates the error code.

Impact on the System

None.

Possible Causes

A fan module was installed.

Procedure

  1. No action is required.

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.6.1 hwASFanRemove

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.6.3 hwASFanInvalid

Description

MBR/1/ASFANINVALID: OID [oid] Fan is invalid. (ASName=[OCTET], ASIndex=[INTEGER], Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityTrapFaultID=[INTEGER])

A fan module on the AS completely failed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.327.31.6.2.6.3 Critical equipmentAlarm(5)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.
Index Indicates the entity index.
EntityPhysicalIndex Indicates the entity index.
PhysicalName Indicates the entity name.
EntityTrapFaultID Indicates the error code.

Impact on the System

Because the fan module fails, the device temperature increases. The device may not work properly and packet loss may occur. Or more seriously, the device may be suspended or reset abnormally.

Possible Causes

The fan module was not installed properly or a hardware fault occurred.

Procedure

  1. Check whether the fan module needs to be removed.

    • If so, the alarm handling ends.
    • If not, install the fan module.

  2. Check whether the fan module is installed properly.

    • If so, replace it.
    • If not, install it securely.

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.6.4 hwASFanInvalidResume

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.6.4 hwASFanInvalidResume

Description

MBR/4/ASFANINVALIDRESUME: OID [oid] Fan resume from invalid situation. (ASName=[OCTET], ASIndex=[INTEGER], Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityTrapFaultID=[INTEGER])

A fan module on the AS recovered from a complete failure.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.
Index Indicates the entity index.
EntityPhysicalIndex Indicates the entity index.
PhysicalName Indicates the entity name.
EntityTrapFaultID Indicates the error code.

Impact on the System

None.

Possible Causes

The hardware fault of the fan module was rectified.

Procedure

  1. No action is required.

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.6.3 hwASFanInvalid

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.7.1 hwASCommunicateError

Description

MBR/4/ASCOMMUNICATEERROR: OID [oid] Communication error has been detected. (ASName=[OCTET], ASIndex=[INTEGER], Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityTrapEntType=[INTEGER], EntityTrapFaultID=[INTEGER], EntityCommunicateType=[INTEGER])

A channel failed.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.
Index Indicates the entity index.
EntityPhysicalIndex Indicates the entity index.
PhysicalName Indicates the entity name.
EntityTrapEntType Indicates the entity type.
EntityTrapFaultID Indicates the error code.
EntityCommunicateType Indicates the type of the communication fault.

Impact on the System

The device cannot obtain the working status of the lithium battery.

Possible Causes

The RS232 serial port that the lithium battery used to communicate with the device failed.

Procedure

  1. Remove and reinstall the lithium battery several times. If the lithium battery still fails to communicate with the device, replace the lithium battery.

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.7.2 hwASCommunicateResume

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.7.2 hwASCommunicateResume

Description

MBR/4/ASCOMMUNICATERESUME: OID [oid] Resume from communication error situation. (ASName=[OCTET], ASIndex=[INTEGER], Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityTrapEntType=[INTEGER], EntityTrapFaultID=[INTEGER], EntityCommunicateType=[INTEGER])

A faulty channel recovered.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.
Index Indicates the entity index.
EntityPhysicalIndex Indicates the entity index.
PhysicalName Indicates the entity name.
EntityTrapEntType Indicates the entity type.
EntityTrapFaultID Indicates the error code.
EntityCommunicateType Indicates the type of the communication fault.

Impact on the System

None.

Possible Causes

The communication between the lithium battery and the device was restored.

Procedure

  1. No action is required.

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.7.1 hwASCommunicateError

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.8.1 hwASCPUUtilizationRising

Description

MBR/4/ASENTITYCPUALARM: OID [oid] CPU utilization exceeded the pre-alarm threshold. (ASName=[OCTET], ASIndex=[INTEGER], Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityThresholdType=[INTEGER], EntityThresholdValue=[INTEGER], EntityThresholdCurrent=[INTEGER], EntityTrapFaultID=[INTEGER])

The CPU usage of the AS exceeded the threshold.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.
Index Indicates the entity index.
EntityPhysicalIndex Indicates the entity index.
PhysicalName Indicates the entity name.
EntityThresholdType Indicates the alarm threshold type.
EntityThresholdValue Indicates the alarm threshold.
EntityThresholdCurrent Indicates the current value.
EntityTrapFaultID Indicates the error code.

Impact on the System

The high CPU usage will delay processing of some services.

Possible Causes

The CPU usage of the device exceeded the threshold.

Procedure

  • Rectify the fault according to CPU Usage Is High in the Troubleshooting Insights-Campus Switch-Device Management And Maintenance.

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.8.2 hwASCPUUtilizationResume

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.8.2 hwASCPUUtilizationResume

Description

MBR/4/ASENTITYCPURESUME: OID [oid] CPU utilization recovered to the normal range. (ASName=[OCTET], ASIndex=[INTEGER], Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityThresholdType=[INTEGER], EntityThresholdValue=[INTEGER], EntityThresholdCurrent=[INTEGER], EntityTrapFaultID=[INTEGER])

The CPU usage of the AS restored to the normal range.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.
Index Indicates the entity index.
EntityPhysicalIndex Indicates the entity index.
PhysicalName Indicates the entity name.
EntityThresholdType Indicates the alarm threshold type.
EntityThresholdValue Indicates the alarm threshold.
EntityThresholdCurrent Indicates the current value.
EntityTrapFaultID Indicates the error code.

Impact on the System

None.

Possible Causes

The CPU usage fell below the alarm threshold.

Procedure

  1. No action is required.

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.8.1 hwASCPUUtilizationRising

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.9.1 hwASMemUtilizationRising

Description

MBR/4/ASMEMORYALARM: OID [oid] Memory usage exceeded the threshold. (ASName=[OCTET], ASIndex=[INTEGER], Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityThresholdType=[INTEGER], EntityThresholdValue=[INTEGER], EntityThresholdCurrent=[INTEGER], EntityTrapFaultID=[INTEGER])

The memory usage of the AS exceeded the threshold.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.
Index Indicates the entity index.
EntityPhysicalIndex Indicates the entity index.
PhysicalName Indicates the entity name.
EntityThresholdType Indicates the alarm threshold type.
EntityThresholdValue Indicates the alarm threshold.
EntityThresholdCurrent Indicates the current value.
EntityTrapFaultID Indicates the error code.

Impact on the System

The high memory usage will delay processing of some services.

Possible Causes

The memory usage of the device exceeded the threshold.

Procedure

  • Rectify the fault according to High Memory Usage in the Troubleshooting Insights-Campus Switch-Device Management And Maintenance.

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.9.2 hwASMemUtilizationResume

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.9.2 hwASMemUtilizationResume

Description

MBR/4/ASMEMORYRESUME: OID [oid] Memory usage recovered to the normal range. (ASName=[OCTET], ASIndex=[INTEGER], Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityThresholdType=[INTEGER], EntityThresholdValue=[INTEGER], EntityThresholdCurrent=[INTEGER], EntityTrapFaultID=[INTEGER])

The memory usage of the AS restored to the normal range.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.
Index Indicates the entity index.
EntityPhysicalIndex Indicates the entity index.
PhysicalName Indicates the entity name.
EntityThresholdType Indicates the alarm threshold type.
EntityThresholdValue Indicates the alarm threshold.
EntityThresholdCurrent Indicates the current value.
EntityTrapFaultID Indicates the error code.

Impact on the System

None.

Possible Causes

The memory usage fell below the alarm threshold.

Procedure

  1. No action is required.

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.9.1 hwASMemUtilizationRising

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.10.1 hwASMadConflictDetect

Description

MBR/4/ASMULATVDETECT: OID [oid] Multi-active scenario is detected. (ASName=[OCTET], ASIndex=[INTEGER])

A multi-active fault occurred.

Attribute

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

Parameters

Name Meaning

oid

 Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.

Impact on the System

Multiple switches with the same IP address, MAC address, and global configuration exist on the network. As a result, an address conflict occurs.

Possible Causes

The stack link failed.

Procedure

  1. Obtain the name of the AS where the fault occurred. In the alarm, ASName indicates the AS name.
  2. Check whether the stack cable of the AS is loose. If so, reconnect the stack cable securely. If the corresponding clear alarm is not generated, replace the stack cable.
  3. Check whether the corresponding clear alarm is generated. If so, no action is required. If not, go to step 4.
  4. Collect alarm information and configuration information, and then contact technical support personnel.

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.10.2 hwASMadConflictResume

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.10.2 hwASMadConflictResume

Description

MBR/4/ASMULATVMERGE: OID [oid] Multi-active scenario is merged. (ASName=[OCTET], ASIndex=[INTEGER])

A multi-active fault was rectified.

Attribute

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

Parameters

Name Meaning

oid

 Indicates the MIB object ID of the alarm.
ASName Indicates the AS name.
ASIndex Indicates the AS index.

Impact on the System

None.

Possible Causes

The faulty stack link recovered.

Procedure

  1. No action is required.

Related Information

MBR_1.3.6.1.4.1.2011.5.25.327.31.6.2.10.1 hwASMadConflictDetect

Translation
日本語 简体中文
Download
Updated: 2022-05-25

Document ID: EDOC1100127008

Views: 104506

Downloads: 365

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Digital Signature File

Digital Signature Authentication Mode
Share
Previous Next

Copyright © 2023 Huawei Technologies Co., Ltd. All rights reserved.

You are going to visit :