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

BASETRAP

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.1.1 hwEntityRemove

Description

BASETRAP/4/ENTITYREMOVE: OID [oid] Physical entity is removed. (Index=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], ContainedIn=[INTEGER], PhysicalName="[OCTET]")

This alarm is generated when the physical entity, such as the board, subcard, power module, or fan or optical module is removed.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the entity, such as the board, power module, fan, or subcard.
Severity Indicates the severity level of the alarm.
ProbableCause Indicates the possible causes of the alarm. The codes of the possible causes are as follows:

1024: IANAITUPROBABLECAUSE_OTHER indicates that the causes are unknown.

EventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2)
  • qualityOfServiceAlarm (3)
  • processingErrorAlarm (4)
  • equipmentAlarm (5)
  • environmentalAlarm (6)

This alarm is an alarm of the equipmentAlarm type, that is, the alarm on device errors.

ContainedIn Indicates the parent index of the entity where the alarm is generated.

1. If the entity is a board, fan, or power module, the parent index is the index of the slot where the board, fan, or power module is located.

2. If the entity is a subcard, the parent index is the index of the slot where the subcard is located on the board.

PhysicalName Indicates the physical name of the entity where the alarm is generated. For example, the physical name of an LPU is LE01G48SC.

Impact on the System

If an LPU is removed, all services running on the LPU are interrupted.

If the main control board is removed, the system reliability is affected. The removal of the master main control board causes the active/standby switchover, which interrupts all services in the system.

If an optical module is removed, the services on the corresponding interface are interrupted.

Possible Causes

An entity is removed.

Procedure

  1. Check whether the board in the slot is removed for certain reasons, for example, routine maintenance.

    • If so, go to step 7.
    • If not, go to step 2.

  2. Check whether the MPU is removed based on the slot ID reported in the alarm.

    • If so, go to step 4.
    • If not, go to step 3.

  3. Check whether the board needs to be inserted again as required.

    • If so, go to step 4.
    • If not, go to step 7.

  4. Insert the corresponding board. After the board is started, run the display device command to check whether the board in the corresponding slot is registered successfully.

    • If so, go to step 7.
    • If not, collect alarm information and configuration information, and then contact technical support personnel.

  5. Check whether the optical module inserted in the interface corresponding to EntPhysicalName is removed.

    • If so, go to step 7.
    • If not, go to step 6.

  6. Remove the optical module and insert it into the interface tightly.

    • If an alarm is generated for the inserted optical module, go to step 7.
    • If no alarm is generated for the inserted optical module, collect alarm information and configuration information, and then contact technical support personnel.

  7. End.

    The following situations indicate that the fault is rectified:

    1. This alarm is not displayed on the NMS.
    2. This alarm is not displayed when you run the display trapbuffer command to view the trap buffer.
    3. This alarm is not displayed when you run the terminal monitor and terminal trapping commands.
    NOTE:

    If subcards are hot swappable, this alarm is informational, and no action is required. If subcards are not hot swappable, when this alarm is displayed, you need to restart the device to restore services. For details about whether subcards are hot swappable, see the subcard description in the Hardware Description.

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.1.2 hwEntityInert

Description

BASETRAP/4/ENTITYINSERT: OID [oid] Physical entity is inserted. (Index=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], ContainedIn=[INTEGER], PhysicalName="[OCTET]")

This alarm is generated when a physical entity, such as a board, power module, or fan, is installed.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the entity, such as the board, power module, fan, or subcard.
Severity Indicates the severity level of the alarm.
ProbableCause Indicates the possible causes of the alarm. The codes of the possible causes are as follows:

1024: IANAITUPROBABLECAUSE_OTHER indicates that the causes are unknown.

EventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2)
  • qualityOfServiceAlarm (3)
  • processingErrorAlarm (4)
  • equipmentAlarm (5)
  • environmentalAlarm (6)

This alarm is an alarm of the equipmentAlarm type, that is, the alarm on device errors.

ContainedIn Indicates the parent index of the entity where the alarm is generated.

1. If the entity is a board, fan, or power module, the parent index is the index of the slot where the board, fan, or power module is located.

2. If the entity is a subcard, the parent index is the index of the slot where the subcard is located on the board.

PhysicalName Indicates the physical name of the entity where the alarm is generated. For example, the physical name of an LPU is LE01G48SC.

Impact on the System

None.

Possible Causes

An entity is installed.

Procedure

  1. This is a normal notification and no action is required.

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.1.5 hwEntityReset

Description

BASETRAP/4/ENTITYRESET: OID [oid] Physical entity is reset. (Index=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], ContainedIn=[INTEGER], PhysicalName="[OCTET]", RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

An LPU is reset.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.129.2.1.5 Warning processingErrorAlarm(4)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the entity, which can be an LPU, a power module, a fan, or a subcard.
Severity Indicates the severity of the alarm.
ProbableCause Indicates the possible cause of the alarm. The codes of the possible causes are as follows:

(1) 1024: IANAITUPROBABLECAUSE_OTHER indicates that the cause is unknown.

(2) 153: IANAITUPROBABLECAUSE_CORRUPTDATA indicates that data is damaged.

EventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2): alarm for communication problems
  • qualityOfServiceAlarm (3): alarm for service quality
  • processingErrorAlarm (4): alarm for processing errors
  • equipmentAlarm (5): alarm for the equipment
  • environmentalAlarm (6): alarm for the environment

This alarm is of the processingErrorAlarm type, that is, the alarm for processing errors.

ContainedIn Indicates the parent index of the entity. In the alarm, this parameter indicates the index of the slot where the board is located.
PhysicalName Indicates the physical name of the entity. For example, the physical name of an LPU is LE01G48SC.
RelativeResource Indicates the name of the component associated with the alarm.
ReasonDescription

Indicates the description of alarm causes.

Impact on the System

The services on the LPU are interrupted.

Possible Causes

The LPU is abnormal.

Procedure

  1. Run the display reset-reason [ slot slot-id ] command in the system view to check the LPU reset reason.
  2. Check whether the LPU is removed for routine maintenance based on the reset reason.

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

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.1.6 hwEntityResetDone

Description

BASETRAP/4/ENTITYRESETDONE: OID [oid] Physical entity resetting ended. (Index=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], ContainedIn=[INTEGER], PhysicalName="[OCTET]", RelativeResource="[OCTET]", ReasonDescr="[OCTET]")

A board is reset.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.129.2.1.6 Warning processingErrorAlarm(4)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the entity, such as a board, a power module, a fan, or a subcard.
Severity Indicates the severity level of the alarm.
ProbableCause Indicates the possible causes of the alarm. The codes of the possible causes are as follows:

1) 1024: IANAITUPROBABLECAUSE_OTHER indicates that the causes are unknown.

2) 153: IANAITUPROBABLECAUSE_CORRUPTDATA indicates that data is damaged.

EventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2): alarm for communication problems
  • qualityOfServiceAlarm (3): alarm for service quality
  • processingErrorAlarm (4): alarm for processing errors
  • equipmentAlarm (5): alarm for the equipment
  • environmentalAlarm (6): alarm for the environment

This alarm is an alarm of the processingErrorAlarm type, that is, the alarm for processing errors.

ContainedIn Indicates the parent index of the entity. In the alarm message, this parameter indicates the index of the slot where the board is located.
PhysicalName Indicates the physical name of the entity. For example, the physical name of an LPU is LE01G48SC.
RelativeResource Indicates the name of the component that is associated with the alarm.
ReasonDescr Indicates the description of alarm causes.

Impact on the System

Services are not affected.

Possible Causes

A reset of the board has completed.

Procedure

  1. The board starts successfully and no action is required.

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.1.7 hwEntityCommunicateError

Description

BASETRAP/1/ENTCOMMUNICATEERROR: OID [oid] Communication channel failed. (Index=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], ContainedIn=[INTEGER], PhysicalName="[OCTET]", RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

Signals are lost on the CANbus.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the entity. The entity in the alarm message is a board.
Severity Indicates the severity level of the alarm.
ProbableCause Indicates the error code: 140312.
EventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2)
  • qualityOfServiceAlarm (3)
  • processingErrorAlarm (4)
  • equipmentAlarm (5)
  • environmentalAlarm (6)

This alarm is an alarm of the communicationsAlarm type, that is, the alarm on communications errors.

ContainedIn Indicates the parent index of the entity. In the alarm message, this parameter indicates the index of the slot where the board is located.
PhysicalName Indicates the physical name of the entity.
RelativeResource Indicates the name of a component that is associated with the alarm.
ReasonDescription Indicates the description of causes of the alarm.

Impact on the System

Some or all services are interrupted due to the CANbus failure.

Possible Causes

  • The card is not installed properly.
  • The CANbus does not work normally, causing communication interruption.

Procedure

  1. Remove and reinstall the card to check whether a clear alarm is generated.
    • If so, the alarm handling ends.
    • If not, collect alarm information and configuration information, and then contact technical support personnel.

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.1.8 hwEntityCommunicateResume

Description

BASETRAP/4/ENTCOMMUNICATERESUME: OID [oid] Communication channel recovered from a failure. (Index=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], ContainedIn=[INTEGER], PhysicalName="[OCTET]", RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

An alarm is generated when signals are recovered on the CANbus.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the entity. The entity in the alarm message is a board.
Severity Indicates the severity level of the alarm.
ProbableCause Indicates the error code: 140312.
EventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2)
  • qualityOfServiceAlarm (3)
  • processingErrorAlarm (4)
  • equipmentAlarm (5)
  • environmentalAlarm (6)

This alarm is an alarm of the communicationsAlarm type, that is, the alarm on communications errors.

ContainedIn Indicates the parent index of the entity. In the alarm message, this parameter indicates the index of the slot where the board is located.
PhysicalName Indicates the physical name of the entity. For example, the physical name of an LPU is LE01G48SC.
RelativeResource Indicates the name of a component that is associated with the alarm.
ReasonDescription Indicates the description of causes of the alarm.

Impact on the System

None.

Possible Causes

The board has been securely inserted, the CANbus fault has been rectified, or available power modules have been installed.

Procedure

  • This alarm is informational only, and no action is required.

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid

Description

BASETRAP/1/ENTITYINVALID: OID [oid] Physical entity failed. (EntityPhysicalIndex=[INTEGER], BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], EntPhysicalContainedIn=[INTEGER], EntPhysicalName="[OCTET]", RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

The physical entity is faulty.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
EntityPhysicalIndex Indicates the physical index.
BaseTrapSeverity Indicates the alarm severity.
BaseTrapProbableCause Indicates the possible causes of the alarm.
BaseTrapEventType Indicates the alarm type.
EntPhysicalContainedIn Indicates the parent index of the entity.
EntPhysicalName Indicates the name of the entity.
RelativeResource Indicates the part related to the alarm.
ReasonDescription Indicates the description of the alarm cause.

Impact on the System

The problematic board does not work, and services on the board are interrupted. If a PHY failure has occurred, the RUN indicator on the board is off, and the Alarm indicator is steady red.

Possible Causes

Cause 1:

Optical modules used on the board are non-Huawei-certified switch optical modules optical modules. This alarm may also be reported for early delivered Huawei optical modules because vendor information of these optical modules is not recorded.

Cause 2:

The link between the CPU and PCI bridge has failed. (PCI stands for Peripheral Component Interconnect.)

Cause 3:

The link between the CPU and forwarding module has failed.

Cause 4:

The field programmable gate array (FPGA) does not work normally.

Cause 5:

The network processor (NP) does not work normally.

Cause 6:

The phase-locked loop (PLL) is abnormal.

Cause 7:

The complex programmable logical device (CPLD) does not work normally.

Cause 8:

The link between the CPU and PCI-PCIe bridge has failed. (PCIe stands for Peripheral Component Interconnect Express.)

Cause 9:

Physical ports on the chip do not work normally.

Cause 10:

Fans do not work normally.

Cause 11:

The Centralized Monitoring Unit (CMU) of the switch does not work normally.

Cause 12:

An error occurs when operations are performed on the flash memory.

Cause 13:

The PHY layer does not work normally.

Cause 14:

The TCAM does not work normally.

Cause 15:

The RTC does not work normally.

Procedure

  1. If non-Huawei-certified switch optical modules optical modules are used (cause 1), use either of the following methods to clear the alarm:

    1. If the optical modules were early delivered from Huawei, the alarm does not need to be handled. Run the transceiver phony-alarm-disable command to disable the alarm for non-Huawei Switch-nertified optical modules. If you cannot confirm whether the optical modules were early delivered from Huawei, contact technical support personnel.
    2. If the optical modules are non-Huawei-certified switch optical modules, replace them with Huawei-certified switch optical modules. Use either of the following methods to determine whether an optical module is a Huawei-certified switch optical module:
      1. Run the display transceiver command to check information about the optical module. If the Vendor Name field does not display HUAWEI, it is not a Huawei-certified switch optical module.
      2. Run the undo transceiver phony-alarm-disable command to enable alarm for non-Huawei-certified switch optical modules. If an alarm is generated for the optical module, the optical module is not a Non-Huawei-certified switch optical module.
        NOTE:

        Huawei-certified switch optical module identification is supported since V200R001.

        Boards with manufacture date later than June 30, 2013 (January 1, 2016 for QSFP+ 40GE optical modules, CFP 40GE optical modules and CFP 100GE optical modules) in their electronic labels are considered new boards. The boards can report alarms periodically after non-Huawei-certified switch optical modules are installed. Old boards do not report alarms for non-Huawei-certified switch optical modules.

  2. If cause 1 is excluded, reset the board and check whether the alarm is cleared.

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

  3. Replace the board and 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.

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume

Description

BASETRAP/4/ENTITYRESUME: OID [oid] Physical entity recovered from a failure. (Index=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER] , EventType=[INTEGER], ContainedIn=[INTEGER], PhysicalName="[OCTET]", RelativeResource="[OCTET]", ReasonDescr="[OCTET]")

The physical entity fault is rectified.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
EntityPhysicalIndex Indicates the physical index.
BaseTrapSeverity Indicates the alarm severity.
BaseTrapProbableCause Indicates the possible causes of the alarm.
BaseTrapEventType Indicates the alarm type.
EntPhysicalContainedIn Indicates the parent index of the entity.
EntPhysicalName Indicates the name of the entity. The value varies with the board type, for example, MPU Board 4, LPU Board 1, and Power Board 24.
RelativeResource Indicates the part related to the alarm.
ReasonDescription Indicates the description of the alarm cause.

Impact on the System

None.

Possible Causes

Cause 1:

The fault of the GE physical interface on the BCM54980 was rectified.

Cause 2:

The fault of the link between the CPU and PCI was rectified.

Cause 3:

The fault of the link between the CPU and forwarding module was rectified.

Cause 4:

The fault of the interface on the BCM88230 was rectified.

Cause 5:

The fault of the FPGA was rectified.

Cause 6:

The fault of the NP was rectified.

Cause 7:

The fault of the PLL was rectified.

Cause 8:

The fault of the CPLD was rectified.

Cause 9:

The fault of the link between the CPU and PCI/PCIe was rectified.

Cause 10:

The fault of the FE physical interface on the forwarding module was rectified.

Cause 11:

The fault of the XGE physical interface on the BCM8754 was rectified.

Cause 12:

The fault of the fan was rectified.

Procedure

  1. This alarm message is informational only, and no action is required.

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.1.12 hwEntityBecomeMaster

Description

BASETRAP/4/ENTITYBECOMEMASTER: OID [oid] Physical entity changed to the master state. (Index=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], ContainedIn=[INTEGER], PhysicalName="[OCTET]", RelativeResource="[OCTET]", ReasonDescr="[OCTET]")

This alarm is generated when the entity is switched from standby state to active state.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.129.2.1.12 Warning processingErrorAlarm(4)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the entity.
Severity Indicates the severity level of the alarm.
ProbableCause Indicates the possible causes of the alarm. The codes of the possible causes are as follows:

612: IANAITUPROBABLECAUSE_OUTOFSERVICE indicates that the main control board is abnormal and cannot provide services.

EventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2)
  • qualityOfServiceAlarm (3)
  • processingErrorAlarm (4)
  • equipmentAlarm (5)
  • environmentalAlarm (6)

This alarm is an alarm of the processingErrorAlarm type, that is, the alarm for processing errors.

ContainedIn Indicates the parent index of the entity.
PhysicalName Indicates the physical name of the entity.
RelativeResource Indicates the name of a component that is associated with the alarm.
ReasonDescription Indicates the description of causes of the alarm.

Impact on the System

None.

Possible Causes

Cause 1

The operator performs active/standby switchover manually.

Cause 2

Exceptions occur on the original active MPU.

Procedure

  1. When the alarm is generated, the active MPU is reset. After about three minutes, run the display device command in the user view to locate the causes of the active/standby switchover according to the slot ID of the MPU in the alarm.

    • If the standby MPU can be registered successfully after the switchover, the switchover is performed through command lines and no action is required.
    • If the standby MPU fails to be registered, switchover may be caused by the active MPU error or abnormal resetting. Go to Step 2.

  2. Replace the active MPU.
  3. Check whether the errors are rectified.

    If the following conditions are met, it indicates that the fault is rectified:

    • The alarm is not displayed on the NMS.
    • After you run the display trapbuffer command, this alarm is not displayed.
    • After you run the terminal monitor and terminal trapping commands, this alarm is not displayed.
    • Three or four minutes later after the switchover, run the display device command to check whether the standby MPU is registered successfully.
      • If so, the alarm handling ends.
      • If not, collect alarm information and configuration information, and then contact technical support personnel.

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.1.18 hwEntityRegSuccess

Description

BASETRAP/4/ENTITYREGSUCCESS: OID [oid] Physical entity registered successfully. (Index=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], ContainedIn=[INTEGER], PhysicalName="[OCTET]", RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

This recovery notification is generated when the board is registered successfully.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.129.2.1.18 Warning operationalViolation(8)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the entity. The entity in the alarm message is a board.
Severity Indicates the severity level of the alarm.
ProbableCause Indicates the possible causes of the alarm. The codes of the possible causes are as follows:

1024: IANAITUPROBABLECAUSE_OTHER indicates that the causes are unknown.

EventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2): alarm for communication problems
  • qualityOfServiceAlarm (3): alarm for service quality
  • processingErrorAlarm (4): alarm for processing errors
  • equipmentAlarm (5): alarm for the equipment
  • environmentalAlarm (6): alarm for the environment
  • operationalViolation (8): alarm for the operation

The type of this alarm is operationalViolation (8).

ContainedIn Indicates the parent index of the entity. In the alarm message, this parameter indicates the index of the slot where the board is installed.
PhysicalName Indicates the physical name of the entity. For example, the physical name of an LPU is LE01G48SC.
RelativeResource Indicates the name of a component that is associated with the alarm.
ReasonDescription Indicates the description of causes of the alarm.

Impact on the System

None.

Possible Causes

The board is registered successfully.

Procedure

  1. This is a normal notification and no action is required.

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.2.1 hwTempRisingAlarm

Description

BASETRAP/3/TEMRISING: OID [oid] Temperature exceeded the upper pre-alarm limit. (Index=[INTEGER], BaseThresholdPhyIndex=[INTEGER], ThresholdType=[ INTEGER], ThresholdIndex=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], PhysicalName="[OCTET]", ThresholdValue=[INTEGER], ThresholdUnit=[INTEGER], ThresholdHighWarning=[INTEGER], ThresholdHighCritical=[INTEGER])

This alarm is generated when the temperature displayed on the sensor of an entity (board or its subcard) exceeds the upper threshold.

The upper threshold is determined by the hardware characteristics of the sensor.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.129.2.2.1 Minor environmentalAlarm(6)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the entity. The entity in the alarm message is a board.
BaseThresholdPhyIndex Indicates the index of the entity. The entity in an alarm on temperature can be a board, fan, or power module.
ThresholdType Indicates the type of the threshold that triggers the alarm. The threshold types are classified into the following:

(1) temperatureSensor: temperature sensor

(2) humiditySensor: humidity sensor

(3) voltageSensor: voltage sensor

(4) currentSensor: current sensor

(5) powerSensor: power sensor

(6) portTraffic: traffic of the port

(7) portCrcError: CRC check of the port

(8) portBroadcast: broadcast traffic on the port

This alarm is triggered by the threshold of the temperature sensor.

Severity Indicates the severity level of the alarm.
ProbableCause Indicates the possible causes of the alarm. The code of the possible cause is as follows:

102: IANAITUPROBABLECAUSE_airConditioningFailure indicates that the fan is faulty.

EventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2)
  • qualityOfServiceAlarm (3)
  • processingErrorAlarm (4)
  • equipmentAlarm (5)
  • environmentalAlarm (6)

This alarm is an alarm of the environmentalAlarm type.

PhysicalName Indicates the physical name of the entity.
ThresholdIndex Indicates the subindex of the entity where the alarm is generated. A subindex identifies a temperature sensor when a board contains multiple temperature sensors.
ThresholdValue Indicates the current temperature. You can run the display temperature all command to view the temperature of the current board.
ThresholdUnit Indicates the unit of the temperature. The unit is as follows:

2: THRESHOLDUNIT_CENTIGRADE1 indicates that the temperature is expressed in centigrade.

ThresholdHighWarning Indicates the temperature threshold that triggers a minor alarm. The temperature threshold is determined by the hardware characteristics of the sensor. You can run the display temperature all command to view the threshold of the sensor on a board.
ThresholdHighCritical Indicates the temperature threshold that triggers a critical alarm. Currently, the value of this parameter is the same as the value of ThresholdHighWarning.

Impact on the System

Services on the switch may be affected if the temperature becomes too high.

Possible Causes

  • The chassis is not ventilated well, which causes heat unable to be dissipated.

  • The air filter is blocked by dust.

  • Vacant slots are not covered with filler panels.

  • The ambient temperature is high.

  • There are not enough fans in the switch.

  • One or more fans in the switch have failed.

Procedure

  1. Clean the air filter and remove the objects that block the air exhaust vents (if any). Cover all vacant slots with filler panels to ensure efficient heat dissipation. Then check whether the alarm is cleared.

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

  2. Check whether the ambient temperature of the device is too high.

    • If so, go to step 3.
    • If not, go to step 4.

  3. Lower the temperature in the equipment room, and then go to step 4.
  4. Check whether fans are properly installed in all fan slots.

    • If so, go to step 6.
    • If not, go to step 5.

  5. Increase the number of fans, and then go to step 6.
  6. Run the display fan command to check the status of fans and determine whether any fan is faulty.

    • If so, go to step 7.
    • If not, go to step 8.

  7. Replace the faulty fan, and then go to step 8.
  8. After the switch has been running for a period of time, run the display temperature all command to check whether temperature of the device is still high.

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

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

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.2.2 hwTempRisingResume

Description

BASETRAP/4/TEMRISINGRESUME: OID [oid] Temperature recovered to the normal range and the high temperature alarm was cleared. (Index=[INTEGER], BaseThresholdPhyIndex=[INTEGER], ThresholdType=[INTEGER], ThresholdIndex=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], PhysicalName="[OCTET]", ThresholdValue=[INTEGER], ThresholdUnit=[INTEGER], ThresholdHighWarning=[INTEGER], ThresholdHighCritical= [INTEGER])

This recovery notification is generated when the temperature of the entity is reduced to the normal range.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the entity. The entity in the alarm message is a board.
BaseThresholdPhyIndex Indicates the index of the entity. The entity in an alarm on temperature can be a board, fan, or power module.
ThresholdType Indicates the type of the threshold that triggers the alarm. The threshold types are classified into the following:

(1) temperatureSensor: temperature sensor

(2) humiditySensor: humidity sensor

(3) voltageSensor: voltage sensor

(4) currentSensor: current sensor

(5) powerSensor: power sensor

(6) portTraffic: traffic of the port

(7) portCrcError: CRC check of the port

(8) portBroadcast: port broadcast

This alarm is triggered by the threshold of the temperature sensor.

Severity Indicates the severity level of the alarm.
ProbableCause Indicates the possible causes of the alarm. The codes of the possible causes are as follows:

130: IANAITUPROBABLECAUSE_lowTemperatue indicates that temperature is reduced.

EventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2)
  • qualityOfServiceAlarm (3)
  • processingErrorAlarm (4)
  • equipmentAlarm (5)
  • environmentalAlarm (6)

This alarm is an alarm of the environmentalAlarm type.

PhysicalName Indicates the physical name of the entity.
ThresholdIndex Indicates the subindex of the entity where the alarm is generated. A subindex identifies a temperature sensor when a board contains multiple temperature sensors.
ThresholdValue Indicates the current temperature. You can run the display temperature all command to view the temperature of the current board.
ThresholdUnit Indicates the unit of the temperature. The unit is as follows:

2: THRESHOLDUNIT_CENTIGRADE1 indicates that the temperature is expressed in centigrade.

ThresholdHighWarning Indicates the temperature threshold that triggers a minor alarm. The temperature threshold is determined by the hardware characteristics of the sensor. You can run the display temperature all command to view the threshold of the sensor on a board.
ThresholdHighCritical Indicates the temperature threshold that triggers a critical alarm. Currently, the value of this parameter is the same as the value of ThresholdHighWarning.

Impact on the System

None.

Possible Causes

An alarm is generated when the temperature of the entity exceeds the upper threshold of the sensor. In this case, you can take cooling measures to make the temperature lower than the upper threshold allowed by the sensor.

Procedure

  1. This is a normal notification and no action is required.

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.2.9 hwVoltRisingAlarm

Description

BASETRAP/1/VOLTRISING: OID [oid] Voltage exceeded the upper pre-alarm limit. (Index=[INTEGER], BaseThresholdPhyIndex=[INTEGER], ThresholdType=[INTEGER], ThresholdIndex=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], PhysicalName="[OCTET]", ThresholdValue=[INTEGER], ThresholdUnit=[INTEGER], ThresholdHighWarning=[INTEGER], ThresholdHighCritical= [INTEGER])

The voltage exceeds the upper threshold.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the entity. The entity in the alarm is a board.
BaseThresholdPhyIndex Indicates the index of the entity. The entity in the voltage alarm can be a board, a fan, or a power module.
ThresholdType Indicates the object that triggers the alarm. The threshold types are classified into the following:

(1) temperatureSensor: temperature sensor

(2) humiditySensor: humidity sensor

(3) voltageSensor: voltage sensor

(4) currentSensor: current sensor

(5) powerSensor: power sensor

(6) portTraffic: traffic of the port

(7) portCrcError: CRC check of the port

(8) portBroadcast: broadcast of the port

This alarm is triggered by the threshold of the voltage sensor.

Severity Indicates the severity level of the alarm.
ProbableCause Indicates the possible cause of the alarm. The code of the possible cause is as follows:

533: IANAITUPROBABLECAUSE_POWERPROBLEMS indicates that the power module is faulty.

EventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2): alarm for communication problems
  • qualityOfServiceAlarm (3): alarm for service quality
  • processingErrorAlarm (4): alarm for processing errors
  • equipmentAlarm (5): alarm for the equipment
  • environmentalAlarm (6): alarm for the environment

This alarm is an alarm of the environmentalAlarm type.

PhysicalName Indicates the physical name of the entity.
ThresholdIndex Indicates the sub-index of the entity where the alarm is generated. A sub-index identifies a voltage sensor when a board contains multiple voltage sensors.
ThresholdValue Indicates the voltage of the board. You can run the display voltage all command to view the voltage values and voltage thresholds of the voltage sensors on each board.
ThresholdUnit Indicates the unit of the voltage. The unit is as follows:

4: THRESHOLDUNIT_VOLTAGE1 indicates that the unit is V.

ThresholdHighWarning Indicates the voltage threshold that triggers a minor alarm. The voltage threshold is determined by the hardware feature of the sensor. You can run the display voltage all command to view the threshold of the sensor on a board.
ThresholdHighCritical Indicates the voltage threshold that triggers a critical alarm. Currently, the value of this parameter is the same as the value of ThresholdHighWarning.

Impact on the System

Services are affected if any power or board has a hardware failure.

Possible Causes

Cause 1: A power module has failed.

Cause 2: The board has failed.

Procedure

  1. Check whether any power module has a hardware failure.

    • If so, go to step 2.
    • If not, go to step 3.

    Use a power module that can work normally to replace the power modules in the switch one by one. Each time a power module is replaced, run the display voltage slot slot-id command to check the voltage on each board. If all boards have normal voltage, the replaced power module has a hardware failure.

  2. Replace the faulty power module. Run the display voltage slot slot-id command to check whether the voltage of the board that has generated the alarm is normal.

    • If so, no action is required.
    • If not, go to step 3.

  3. Reset the board and check whether the alarm is cleared.

    • If so, no action is required.
    • If not, go to step 4.

  4. Replace the board and check whether the alarm is cleared.

    • If so, no action is required.
    • If not, collect alarm information and configuration information, and then contact technical support personnel.

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.2.10 hwVoltRisingResume

Description

BASETRAP/4/VOLTRISINGRESUME: OID [oid] Voltage recovered to the normal range and the high voltage alarm was cleared. (Index=[INTEGER], BaseThresholdPhyIndex=[INTEGER], ThresholdType=[INTEGER], ThresholdIndex=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], PhysicalName="[OCTET]", ThresholdValue=[INTEGER], ThresholdUnit=[INTEGER], ThresholdHighWarning=[INTEGER], ThresholdHighCritical=[INTEGER])

This recovery notification is generated when the voltage of the entity is reduced to the normal range.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the entity. The entity in the alarm message is a board.
BaseThresholdPhyIndex Indicates the index of the entity. The entity in an alarm on voltage can be a board, fan, or power module.
ThresholdType Indicates the type of the threshold that triggers the alarm. The threshold types are classified into the following:

(1) temperatureSensor: temperature sensor

(2) humiditySensor: humidity sensor

(3) voltageSensor: voltage sensor

(4) currentSensor: current sensor

(5) powerSensor: power sensor

(6) portTraffic: traffic of the port

(7) portCrcError: CRC check of the port

(8) portBroadcast: port broadcast

This alarm is triggered by the threshold of the voltage sensor.

Severity Indicates the severity level of the alarm.
ProbableCause Indicates the possible causes of the alarm. The codes of the possible causes are as follows:

115: IANAITUPROBABLECAUSE_rectifierHighVoltage indicates that the voltage is adjusted to the normal range.

EventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2)
  • qualityOfServiceAlarm (3)
  • processingErrorAlarm (4)
  • equipmentAlarm (5)
  • environmentalAlarm (6)

This alarm is an alarm of the environmentalAlarm type.

PhysicalName Indicates the physical name of the entity.
ThresholdIndex Indicates the subindex of the entity where the alarm is generated. A subindex identifies a voltage sensor when a board contains multiple voltage sensors.
ThresholdValue Indicates the current voltage. You can run the display voltageall command to view the current voltage of the board and the voltage threshold.
ThresholdUnit Indicates the unit of the voltage. The unit is as follows:

4: THRESHOLDUNIT_VOLTAGE1 indicates that the voltage is expressed in V.

ThresholdHighWarning Indicates the voltage threshold that triggers a minor alarm. The voltage threshold is determined by the hardware characteristics of the sensor. You can run the display voltageall command to view the threshold of the sensor on a board.
ThresholdHighCritical Indicates the voltage threshold that triggers a critical alarm. Currently, the value of this parameter is the same as the value of ThresholdHighWarning.

Impact on the System

Services will be unaffected.

Possible Causes

Cause 1

The fault on the power module is rectified.

Cause 2

The fault on the board is rectified.

Procedure

  1. This is a normal notification and no action is required.

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.2.11 hwVoltFallingAlarm

Description

BASETRAP/1/VOLTFALLING: OID [oid] Voltage has fallen below the lower pre-alarm limit. (Index=[INTEGER], BaseThresholdPhyIndex=[INTEGER], ThresholdType=[INTEGER], ThresholdIndex=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], PhysicalName="[OCTET]", ThresholdValue=[INTEGER], ThresholdUnit=[INTEGER], ThresholdLowWarning=[INTEGER], ThresholdLowCritical=[INTEGER])

The voltage is less than the lower threshold.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the entity. The entity in the alarm is a board.
BaseThresholdPhyIndex Indicates the index of the entity. The entity in an alarm on voltage can be a board, fan, or power module.
ThresholdType Indicates the type of the threshold that triggers the alarm. The possible threshold types are as follows:

(1) temperatureSensor: temperature sensor

(2) humiditySensor: humidity sensor

(3) voltageSensor: voltage sensor

(4) currentSensor: current sensor

(5) powerSensor: power sensor

(6) portTraffic: traffic of the port

(7) portCrcError: CRC check of the port

(8) portBroadcast: broadcast traffic on the port

This alarm is triggered by the threshold of the voltage sensor.

Severity Indicates the severity level of the alarm.
ProbableCause Indicates the possible causes of the alarm. The code of the possible cause is as follows:

533: IANAITUPROBABLECAUSE_POWERPROBLEMS indicates that the power module is faulty.

EventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2)
  • qualityOfServiceAlarm (3)
  • processingErrorAlarm (4)
  • equipmentAlarm (5)
  • environmentalAlarm (6)

This alarm is an alarm of the environmentalAlarm type.

PhysicalName Indicates the physical name of the entity.
ThresholdIndex Indicates the subindex of the entity where the alarm is generated. A subindex identifies a voltage sensor when there are multiple voltage sensors on a board.
ThresholdValue Indicates the current voltage. You can run the display voltage all command to view the current voltage of the board and the voltage threshold.
ThresholdUnit Indicates the unit of the voltage. The unit is as follows:

4: THRESHOLDUNIT_VOLTAGE1 indicates that the voltage is expressed in V.

ThresholdLowWarning Indicates the voltage threshold that triggers a minor alarm. The voltage threshold is determined by the hardware characteristics of the sensor. You can run the display voltage all command to view the threshold of the sensor on a board.
ThresholdLowCritical Indicates the voltage threshold that triggers a critical alarm. Currently, the value of this parameter is the same as the value of ThresholdLowWarning.

Impact on the System

The board may be powered off, causing interruption of services on the board.

Possible Causes

Cause 1: The board has failed.

Cause 2: A power module in the switch has failed.

Cause 3: The power provided to the switch is insufficient because there are not enough power modules in the switch.

Procedure

  1. Run the display device command to check device information. Based on the information, check whether the models of power modules installed in the device are supported by the chassis and whether the power modules are sufficient to provide power to all the boards installed in this chassis. For the models of power modules supported by each chassis model, see Hardware Description > Chassis > Power Supply Slot Configuration.

    • If so, go to step 3.
    • If not, go to step 2.

  2. Replace the unsupported power modules with those supported by the chassis, and add power modules based on the required power to ensure power sufficiency. Check whether the alarm is cleared.

    • If so, no action is required.
    • If not, go to step 3.

  3. Check whether any power module has a hardware failure.

    • If so, go to step 4.
    • If not, go to step 5.

    Use a power module that can work normally to replace the power modules in the switch one by one. Each time a power module is replaced, run the display voltage slot slot-id command to check the voltage on each board. If all boards have normal voltage, the replaced power module has a hardware failure.

  4. Replace the faulty power module. Run the display voltage slot slot-id command to check whether the voltage of the board that has generated the alarm is normal.

    • If so, no action is required.
    • If not, go to step 5.

  5. Reset the board and check whether the alarm is cleared.

    • If so, no action is required.
    • If not, go to step 6.

  6. Replace the board and check whether the alarm is cleared.

    • If so, no action is required.
    • If not, contact technical support personnel.

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.2.12 hwVoltFallingResume

Description

BASETRAP/4/VOLTFALLINGRESUME: OID [oid] Voltage recovered to the normal range and the low voltage alarm was cleared. (Index=[INTEGER], BaseThresholdPhyIndex=[INTEGER], ThresholdType=[INTEGER], ThresholdIndex=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], PhysicalName="[OCTET]", ThresholdValue=[INTEGER], ThresholdUnit=[INTEGER], ThresholdLowWarning=[INTEGER], ThresholdLowCritical=[INTEGER])

The voltage increased to the normal range and the low voltage alarm was cleared.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the entity. The entity in the voltage alarm can be a board, a fan, or a power module.
BaseThresholdPhyIndex Indicates the index of the entity. The entity in an alarm on voltage can be a board, a fan, or a power module.
ThresholdType Indicates the object that triggers the alarm. The objects are as follows:

(1) temperatureSensor: temperature sensor

(2) humiditySensor: humidity sensor

(3) voltageSensor: voltage sensor

(4) currentSensor: current sensor

(5) powerSensor: power sensor

(6) portTraffic: traffic of the port

(7) portCrcError: CRC check of the port

(8) portBroadcast: broadcast of the port

This alarm is triggered by the threshold of the voltage sensor.

Severity Indicates the severity level of the alarm.
ProbableCause Indicates the possible cause of the alarm. The code of the possible cause is as follows:

116: IANAITUPROBABLECAUSE_rectifierLowFVoltage indicates that the low voltage is adjusted.

EventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2): alarm for communication problems
  • qualityOfServiceAlarm (3): alarm for service quality
  • processingErrorAlarm (4): alarm for processing errors
  • equipmentAlarm (5): alarm for the equipment
  • environmentalAlarm (6): alarm for the environment

This alarm is of the environmentalAlarm type, that is, the alarm on environment errors.

PhysicalName Indicates the physical name of the entity.
ThresholdIndex Indicates the sub-index of the entity where the alarm is generated. A sub-index identifies a voltage sensor when a board contains multiple voltage sensors.
ThresholdValue Indicates the current voltage. You can run the display voltageall command to view the current voltage of the board and the voltage threshold.
ThresholdUnit Indicates the unit of the voltage. The unit is as follows:

4: THRESHOLDUNIT_VOLTAGE1 indicates that the unit is V.

ThresholdLowWarning Indicates the voltage threshold that triggers a minor alarm. The voltage threshold is determined by the hardware feature of the sensor. You can run the display voltageall command to view the threshold of the sensor on a board.
ThresholdLowCritical Indicates the voltage threshold that triggers a critical alarm. Currently, the value of this parameter is the same as the value of ThresholdHighWarning.

Impact on the System

None.

Possible Causes

The power module is restored and the voltage of the board has increased to the normal range.

Procedure

  1. This alarm is informational and no action is required.

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.2.21 hwPowerInsufficiencyAlarm

Description

BASETRAP/2/POWERLACK: OID [oid] The available power of device is not enough for the board. (Index=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], PhysicalContainedIn=[INTEGER], PhysicalName="[OCTET]", EntityRatedPower=[INTEGER], DevAvailablePower=[INTEGER], DeviceTotalPower=[INTEGER])

When a board is installed, the system allocates the rating power of the board to the board. This alarm is generated when the available power of the system is smaller than the rating power of the board.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the entity. The entity in an alarm on power is a board.
Severity Indicates the severity level of the alarm.
ProbableCause Indicates the possible causes of the alarm. The codes of the possible causes are as follows:

533: IANAITUPROBABLECAUSE_POWERPROBLEMS indicates that the power module is faulty.

EventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2)
  • qualityOfServiceAlarm (3)
  • processingErrorAlarm (4)
  • equipmentAlarm (5)
  • environmentalAlarm (6)

This alarm is an alarm of the equipmentAlarm type.

PhysicalName Indicates the physical name of the entity.
PhysicalContainedIn Indicates the index of the parent entity of the alarm entity. In the alarm message, this parameter indicates the index of the slot where the power module is located.
EntityRatedPower Indicates the rating power of the board.
DevAvailablePower Indicates the available power of the system.
DeviceTotalPower Indicates the total power of the system.

Impact on the System

The board to be installed cannot be switched on.

Possible Causes

The available power of the system is less than the rating power of the board.

Procedure

  1. Run the display power system command to check the total power and available power of the system and the rated power of each board that is switched on.
  2. Check whether this board needs to be installed.

    • If so, go to step 3.
    • If not, remove this board. The alarm handling ends.

  3. Check whether other unnecessary boards can be removed.

    • If so, go to step 4.
    • If not, this board cannot be installed. The alarm handling ends.

  4. Remove unnecessary boards, and then run the display power system command to check whether the remaining power is sufficient for the newly installed board.

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

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.2.22 hwPowerInsufficiencyResume

Description

BASETRAP/4/POWERLACKRESUME: OID [oid] The available power of the device is enough for the board. (Index=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], PhysicalContainedIn=[INTEGER], PhysicalName="[OCTET]", EntityRatedPower=[INTEGER], DevAvailablePower=[INTEGER], DeviceTotalPower=[INTEGER])

This recovery notification is generated when the available power of the system is more than the rating power of the board.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the entity. The entity in an alarm on power is a board.
Severity Indicates the severity level of the alarm.
ProbableCause Indicates the possible causes of the alarm. The codes of the possible causes are as follows:

533: IANAITUPROBABLECAUSE_POWERPROBLEMS indicates that the power module is faulty.

EventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2)
  • qualityOfServiceAlarm (3)
  • processingErrorAlarm (4)
  • equipmentAlarm (5)
  • environmentalAlarm (6)

This alarm is an alarm of the equipmentAlarm type.

PhysicalName Indicates the physical name of the entity.
PhysicalContainedIn Indicates the index of the parent entity of the alarm entity. In the alarm message, this parameter indicates the index of the slot where the power module is located.
EntityRatedPower Indicates the rating power of the board.
DevAvailablePower Indicates the available power of the system.
DeviceTotalPower Indicates the total power of the system.

Impact on the System

Services will be unaffected.

Possible Causes

If the available power of the system is more than the rating power of the board, it indicates that the requirements on the power of the board are met.

Procedure

  1. This is a normal notification and no action is required.

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.3.1 hwPowerOff

Description

BASETRAP/1/POWEROFF: OID [oid] The power supply is off. (Index=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], ContainedIn=[INTEGER], PhysicalName="[OCTET]")

The power module is powered off.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.

Index

Indicates the index of the entity. The entity in the alarm is a power module.

Severity

Indicates the severity level of the alarm.

ProbableCause

Indicates the possible cause of the alarm. The code of the possible cause is as follows:

78: IANAITUPROBABLECAUSE_POWERSUPPLYFAILURE indicates that the power module fails.

EventType

Indicates the alarm type. Alarms are classified into the following types:

  • communicationsAlarm (2): alarm for communication problems
  • qualityOfServiceAlarm (3): alarm for service quality
  • processingErrorAlarm (4): alarm for processing errors
  • equipmentAlarm (5): alarm for the equipment
  • environmentalAlarm (6): alarm for the environment

This alarm is of the equipmentAlarm type, that is, the alarm for the equipment.

ContainedIn

Indicates the index of the parent entity of the alarm entity. In the alarm, this parameter indicates the index of the slot where the power module is located.

PhysicalName

Indicates the name of the entity. In the alarm message, this parameter indicates a power supply board.

Impact on the System

Services are affected if there is a backup power module.

Possible Causes

Cause 1:

The power module is powered off manually.

Cause 2:

The power module is powered off because of natural factors. For example, the power module is loose.

Cause 3:

The power module is faulty.

Procedure

  1. Check whether the power module is powered off manually for routine maintenance.

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

  2. Check whether the power switch on the power module is turned on.

    • If so, go to step 4.
    • If not, go to step 3.

  3. Turn on the power switch, and then check whether a power-on alarm is generated.

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

  4. If the DC power module is used, check whether the power cable is loose.

    • If so, go to step 5.
    • If not, go to step 6.

  5. Connect the DC power module properly, and then check whether a power-on alarm is generated.

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

  6. Check whether the hardware of the power module is faulty.

    Method: Replace this power module with a normal power module to check whether a power-on alarm is generated.

    • If so, go to step 7.
    • If not, collect alarm information and configuration information, and then contact technical support personnel.

  7. Replace this power module, and then check whether a power-on alarm is generated.

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

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.3.2 hwPowerOn

Description

BASETRAP/4/POWERON: OID [oid] The power supply is on. (Index=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], ContainedIn=[INTEGER], PhysicalName="[OCTET]")

This recovery notification is generated when the power module is switched on.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the entity. The entity in an alarm on power supply is a power supply board.
Severity Indicates the severity level of the alarm.
ProbableCause Indicates the possible causes of the alarm. The codes of the possible causes are as follows:

1024: IANAITUPROBABLECAUSE_OTHER indicates that the causes are unknown.

EventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2)
  • qualityOfServiceAlarm (3)
  • processingErrorAlarm (4)
  • equipmentAlarm (5)
  • environmentalAlarm (6)

This alarm is an alarm of the equipmentAlarm type.

ContainedIn Indicates the index of the parent entity of the alarm entity. In the alarm message, this parameter indicates the index of the slot where the power supply is located.
PhysicalName Indicates the name of the entity. In the alarm message, this parameter indicates a power supply board.

Impact on the System

None.

Possible Causes

Cause 1

The power module is switched on.

Cause 2

The fault on the power module is rectified.

Procedure

  1. This is a normal notification and no action is required.

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.4.1 hwCPUUtilizationRisingAlarm

Description

BASETRAP/2/CPUUSAGERISING: OID [oid] CPU utilization exceeded the pre-alarm threshold. (Index=[INTEGER], BaseUsagePhyIndex=[INTEGER], UsageType=[INTEGER], UsageIndex=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], PhysicalName="[OCTET]", RelativeResource="[OCTET]", UsageValue=[INTEGER], UsageUnit=[INTEGER], UsageThreshold=[INTEGER])

The CPU usage exceeds the threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.129.2.4.1 Major processingErrorAlarm(4)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the entity. The entity in an alarm on the CPU is a board.
BaseUsagePhyIndex Indicates the index of the physical entity. The entity in an alarm on the CPU is a board.
UsageType Indicates the type of the alarm on usage.
UsageIndex Indicates the index of the sub-entity of the alarm entity. In the alarm on CPU usage, the fixed value of this parameter is 0.
Severity Indicates the severity level of the alarm.
ProbableCause Indicates the possible cause of the alarm. The code of the possible cause is as follows:

154: IANAITUPROBABLECAUSE_OUTOFCPUCYCLES indicates that the CPU usage exceeds the threshold.

EventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2): alarm for communication problems
  • qualityOfServiceAlarm (3): alarm for service quality
  • processingErrorAlarm (4): alarm for processing errors
  • equipmentAlarm (5): alarm for the equipment
  • environmentalAlarm (6): alarm for the environment

This alarm is of the processingErrorAlarm type, that is, the alarm for processing errors.

PhysicalName Indicates the name of the entity. In the alarm message, this parameter indicates a board.
RelativeResource Indicates the resources that are associated with the alarm. The current value on the device is empty.
UsageValue Indicates the current CPU usage of the board.
UsageUnit Indicates the unit of the CPU usage. The unit is percent.
UsageThreshold Indicates the alarm threshold of the CPU usage.

Impact on the System

High CPU usage in a very short period does not affect services; however, long-term high CPU usage may delay service processing.

Possible Causes

Cause 1:

The alarm threshold of the CPU usage is low.

Cause 2:

The switch provides too many services.

Cause 3:

The switch is attacked, causing high CPU usage.

Procedure

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

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.4.2 hwCPUUtilizationResume

Description

BASETRAP/4/CPUUSAGERESUME: OID [oid] CPU utilization recovered to the normal range. (Index=[INTEGER], BaseUsagePhyIndex=[INTEGER], UsageType=[INTEGER], UsageIndex=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], PhysicalName="[OCTET]", RelativeResource="[OCTET]", UsageValue=[INTEGER], UsageUnit=[INTEGER], UsageThreshold=[INTEGER])

This recovery notification is generated when the CPU usage is reduced to the normal range.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.129.2.4.2 Warning processingErrorAlarm(4)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the entity. The entity in an alarm on the CPU is a board.
BaseUsagePhyIndex Indicates the index of the physical entity. The entity in an alarm on the CPU is a board.
UsageType Indicates the type of the alarm on usage.
UsageIndex Indicates the index of the sub-entity of the alarm entity. In the alarm on CPU usage, the fixed value of this parameter is 0.
ProbableCause Indicates the possible causes of the alarm. The codes of the possible causes are as follows:

1024: IANAITUPROBABLECAUSE_OTHER indicates that the causes are unknown.

EventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2)
  • qualityOfServiceAlarm (3)
  • processingErrorAlarm (4)
  • equipmentAlarm (5)
  • environmentalAlarm (6)

This alarm is an alarm of the environmentalAlarm type.

PhysicalName Indicates the name of the entity. In the alarm message, this parameter indicates a board.
RelativeResource Indicates the resources that are associated with the alarm. The current value on the device is null.
UsageValue Indicates the CPU usage of the current board.
UsageUnit Indicates the unit of the CPU usage. The unit is percent.
UsageThreshold Indicates the alarm threshold of CPU usage.

Impact on the System

None.

Possible Causes

The CPU usage is reduced to the normal range.

Procedure

  1. This is a normal notification and no action is required.

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.5.11 hwPortPhysicalEthHalfDuplexAlarm

Description

BASETRAP/4/HALFDUPLEXALARM: OID [oid] The port works in half duplex mode. (EntityPhysicalIndex=[INTEGER], BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], EntPhysicalName="[OCTET]", RelativeResource="[OCTET]")

The operation mode of the interface is negotiated to half duplex after certain events occur, for example, the interface status becomes Up or Down, or the user manually sets the operation mode to half duplex.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.129.2.5.11 Warning operationalViolation(8)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
EntityPhysicalIndex Indicates the entity index.
BaseTrapSeverity Indicates the severity level of the alarm.
BaseTrapProbableCause Indicates the possible cause of the alarm.
BaseTrapEventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2): alarm for communication problems
  • qualityOfServiceAlarm (3): alarm for service quality
  • processingErrorAlarm (4): alarm for processing errors
  • equipmentAlarm (5): alarm for the equipment
  • environmentalAlarm (6): alarm for the environment
  • operationalViolation (8): alarm for the operation

The type of this alarm is operationalViolation (8).

EntPhysicalName Indicates the entity name.
RelativeResource Indicates the resource related to this alarm.

Impact on the System

Services are not affected.

Possible Causes

The operation mode of the interface is negotiated to half duplex after certain events occur, for example, the interface status becomes Up or Down, or the user manually sets the operation mode to half duplex.

Procedure

  1. Check whether the duplex half or auto duplex half command has been executed to set the operation mode to half duplex.

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

  2. Run the shutdown and undo shutdown commands on this interface and then check whether the interface works in full duplex mode.

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

Related Information

None

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.5.12 hwPortPhysicalEthFullDuplexClear

Description

BASETRAP/4/HALFDUPLEXCLEAR: OID [oid] The port works in full duplex mode. (EntityPhysicalIndex=[INTEGER], BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], EntPhysicalName="[STRING]", RelativeResource="[STRING]")

The interface working mode changed to half duplex.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.129.2.5.12 Warning operationalViolation(8)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
EntityPhysicalIndex Indicates the interface index.
BaseTrapSeverity Indicates the alarm severity.
BaseTrapProbableCause Indicates the alarm cause.
BaseTrapEventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2): alarm for communication problems
  • qualityOfServiceAlarm (3): alarm for service quality
  • processingErrorAlarm (4): alarm for processing errors
  • equipmentAlarm (5): alarm for the equipment
  • environmentalAlarm (6): alarm for the environment
  • operationalViolation (8): alarm for the operation

The type of this alarm is operationalViolation (8).

EntPhysicalName Indicates the interface name.
RelativeResource Indicates the relative resource.

Impact on the System

The interface alternates between Up and Down states.

Possible Causes

The interface begins to work in half duplex mode. When the interface works in full duplex mode, a full duplex alarm is generated.

Procedure

  1. Check whether the current duplex mode of the interface is correct according to networking requirements.

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

  2. Run the duplex half or auto duplex half command to configure the interface to work in half duplex mode.

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.5.13 hwPortPhysicalPortTypeChange

Description

BASETRAP/4/PORTTYPECHG: OID [oid] Physical entity port type changed. (EntityPhysicalIndex=[INTEGER], BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], EntPhysicalName="[OCTET]", EntityPhysicalLastPortType=[INTEGER], EntityPhysicalCurPortType=[INTEGER])

The alarm is generated when the interface type is changed through commands.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.129.2.5.13 Warning operationalViolation(8)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
EntityPhysicalIndex Indicates the entity index.
BaseTrapSeverity Indicates the severity level of the alarm.
BaseTrapProbableCause Indicates the possible cause of the alarm.
BaseTrapEventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2): alarm for communication problems
  • qualityOfServiceAlarm (3): alarm for service quality
  • processingErrorAlarm (4): alarm for processing errors
  • equipmentAlarm (5): alarm for the equipment
  • environmentalAlarm (6): alarm for the environment
  • operationalViolation (8): alarm for the operation

The type of this alarm is operationalViolation (8).

EntPhysicalName Indicates the entity name.
EntityPhysicalLastPortType Indicates the interface type before the change.
EntityPhysicalCurPortType Indicates the current interface type.

Impact on the System

Services are not affected.

Possible Causes

The interface type is changed through the commands.

Procedure

  1. This log is normal operation information and does not need to be processed.

Related Information

None

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.6.1 hwStorageUtilizationRisingAlarm

Description

BASETRAP/2/STORAGEUSAGERISING: OID [oid] Storage utilization exceeded the pre-alarm threshold. (Index=[INTEGER], BaseUsagePhyIndex=[INTEGER], UsageType=[INTEGER], UsageIndex=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], PhysicalName="[OCTET]", RelativeResource="[OCTET]", UsageValue=[INTEGER], UsageUnit=[INTEGER], UsageThreshold=[INTEGER])

This alarm is generated when the usage of a storage device exceeds the upper threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.129.2.6.1 Major processingErrorAlarm(4)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the entity. The entity in an alarm on storage device usage is a board.
BaseUsagePhyIndex Indicates the index of the physical entity. The entity in an alarm on storage device usage is a board.
UsageType Indicates the type of the alarm on usage.
UsageIndex Indicates the index of the sub-entity of the alarm entity. In the alarm on storage device usage, the fixed value of this parameter is 0.
Severity Indicates the severity level of the alarm.
ProbableCause Indicates the possible causes of the alarm. The codes of the possible causes are as follows:

151: IANAITUPROBABLECAUSE_STORAGECAPACITYPROBLEM indicates the errors of storage device usage.

EventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2)
  • qualityOfServiceAlarm (3)
  • processingErrorAlarm (4)
  • equipmentAlarm (5)
  • environmentalAlarm (6)
PhysicalName Indicates the name of the entity.
RelativeResource Indicates the name of the resource that is associated with the alarm.
UsageValue Indicates the usage of the storage.
UsageUnit Indicates the unit of the storage device usage. The unit is percent.
UsageThreshold Indicates the alarm threshold of storage device usage.

Impact on the System

Impact 1: If this alarm is not cleared immediately, the storage space will be insufficient to record logs and diagnostic information. In this case, the system running information and fault locating information will be missing.

Impact 2: The system operations on files may fail because of insufficient storage space.

Possible Causes

Cause 1

The storage device stores too many logs and too much diagnostic information.

Cause 2

The storage device stores too many unnecessary or expired files.

Procedure

  1. Check the value of hwBaseUsageType in the reported alarm. Run the cd cfcard:\ command to access the CF card directory, and then run the dir command to check the used space and remaining space of the storage device.
  2. Run the dir command to check the list of files stored in the storage device and detailed information about files and directories, such as the file size and created logs. Check whether there are unnecessary or expired files that need to be deleted.

    • If so, go to step 3.
    • If not, go to step 6.

  3. Delete the unnecessary files or run the move command to move the files to other storage devices.

    Check whether the size of log files or diagnostic log files in the storage device is too large.

    • If so, go to step 4.
    • If not, go to step 5.

  4. Delete the log files or diagnostic log files or move the files to other storage devices.
  5. Check whether the alarm recovery message is received.

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

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.6.2 hwStorageUtilizationResume

Description

BASETRAP/4/STORAGEUSAGERESUME: OID [oid] Storage utilization resumed to normal range. (Index=[INTEGER], BaseUsagePhyIndex=[INTEGER], UsageType=[INTEGER], UsageIndex=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], PhysicalName="[OCTET]", RelativeResource="[OCTET]", UsageValue=[INTEGER], UsageUnit=[INTEGER], UsageThreshold=[INTEGER])

This recovery notification is generated when the storage device usage is reduced to the normal range.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.129.2.6.2 Warning processingErrorAlarm(4)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the entity. The entity in an alarm on storage device usage is a board.
BaseUsagePhyIndex Indicates the index of the physical entity. The entity in an alarm on storage device usage is a board.
UsageType Indicates the type of the alarm on usage.
UsageIndex Indicates the index of the sub-entity of the alarm entity. In the alarm on storage device usage, the fixed value of this parameter is 0.
Severity Indicates the severity level of the alarm.
ProbableCause Indicates the possible causes of the alarm. The codes of the possible causes are as follows:

1024: IANAITUPROBABLECAUSE_OTHER indicates that the causes are unknown.

EventType Indicates the alarm type. Alarms are classified into the following types:
  • communicationsAlarm (2)
  • qualityOfServiceAlarm (3)
  • processingErrorAlarm (4)
  • equipmentAlarm (5)
  • environmentalAlarm (6)

This alarm is an alarm of the processingErrorAlarm type.

PhysicalName Indicates the name of the entity.
RelativeResource Indicates the name of the resource that is associated with the alarm.
UsageValue Indicates the usage of the storage.
UsageUnit Indicates the unit of the storage device usage. The unit is percent.
UsageThreshold Indicates the alarm threshold of storage device usage.

Impact on the System

None.

Possible Causes

Cause 1

The system deletes part of the expired files automatically.

Cause 2

Part of the files are deleted manually.

Procedure

  1. This is a normal notification and no action is required.

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.17.1 hwOpticalPowerAbnormal

Description

BASETRAP/3/OPTPWRABNORMAL: OID [oid] Optical module power is abnormal. (EntityPhysicalIndex=[INTEGER], BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], EntPhysicalContainedIn=[INTEGER], EntPhysicalName="[OCTET]", RelativeResource="[OCTET]", ReasonDescription="[OCTET]")

An alarm is generated when the transmit or receive power of an optical module is out of the allowed range.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
EntityPhysicalIndex Indicates the physical index.
BaseTrapSeverity Indicates the alarm severity.
BaseTrapProbableCause Indicates the possible causes of the alarm.
BaseTrapEventType Indicates the alarm type.
EntPhysicalContainedIn Indicates the parent index of the entity.
EntPhysicalName Indicates the name of the entity.
RelativeResource Indicates the part related to the alarm.
ReasonDescription Indicates the description of the alarm cause.

Impact on the System

This alarm does not affect system operating if the interface on which the optical module is installed works properly.

Possible Causes

The ReasonDescription parameter in the alarm describes the cause for the abnormal optical power.
  • Cause 1: The transmit power of the optical module exceeds the maximum value. The ReasonDescription parameter description includes the following: Overhigh sending power of fabric module.
  • Cause 2: The transmit power of the optical module falls below the minimum value. The ReasonDescription parameter description includes the following: Overlow sending power of fabric module.
  • Cause 3: The receive power of the optical module exceeds the maximum value. The ReasonDescription parameter description includes the following: Overhigh receiving power of fabric module.
  • Cause 4: The receive power of the optical module falls below the minimum value. The ReasonDescription parameter description includes the following: Overlow receiving power of fabric module.
NOTE:

If the interface is in shutdown, errordown, or loopback state, this alarm is not generated when the transmit power falls below the minimum value. When a link fault occurs, the interface enabled with the ALS function sends LOS signals. This alarm is not generated when the transmit power or the receive power falls below the minimum value.

Procedure

  1. Run the display transceiver verbose command to check the power of the optical module.
  2. Check whether the interface status and data forwarding are normal.

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

BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.17.2 hwOpticalPowerResume

Description

BASETRAP/4/OPTPWRRESUME: OID [oid] Optical module recovered from power abnormal. (Index=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER] , EventType=[INTEGER], ContainedIn=[INTEGER], PhysicalName="[OCTET]", RelativeResource="[OCTET]", ReasonDescr="[OCTET]")

An alarm is generated when the transmit or receive power of the optical module recovers to the allowed range.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
EntityPhysicalIndex Indicates the physical index.
BaseTrapSeverity Indicates the alarm severity.
BaseTrapProbableCause Indicates the possible causes of the alarm.
BaseTrapEventType Indicates the alarm type.
EntPhysicalContainedIn Indicates the parent index of the entity.
EntPhysicalName Indicates the name of the entity.
RelativeResource Indicates the part related to the alarm.
ReasonDescription Indicates the description of the alarm cause.

Impact on the System

None.

Possible Causes

The optical module power recovers to the allowed range.

Procedure

  1. This alarm message is informational only, and no action is required.

BASETRAP_1.3.6.1.4.1.2011.5.25.31.7.2.1 hwEntityHeartbeatTrap

Description

BASETRAP/4/NETWORKHEARTBEATTRAP: OID [oid] Network heart beat.

The device periodically sends heartbeat packets to the NMS. The NMS considers the device present if it receives heartbeat packets from the device.

Attribute

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

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.

Impact on the System

None

Possible Causes

The device reports this alarm after it is enabled to send heartbeat packets to the NMS.

Procedure

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

Related Information

None

Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065855

Views: 4187

Downloads: 6

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