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

E9000 Server V100R001 HMM Alarm Handling 19

This document describes E9000 server alarms in terms of the meaning, impact on the system, possible causes, and solutions.
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).
SYSTEM

SYSTEM

SYSTEM_1.3.6.1.4.1.2011.5.25.19.2.1 hwSysClockChangedNotification

Description

The local time is changed with LocalTime [localtime].

The system clock changed.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Critical

Mnemonic Code

hwSysClockChangedNotification

Trap OID

1.3.6.1.4.1.2011.5.25.19.2.1

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the match trap.

Parameters

None

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.19.1.1.1

hwSysLocalClock

N/A

Impact on the System

Services are not affected.

Possible Causes

The system clock changed.

Procedure
  • The log is informational only, and no action is required.

SYSTEM_1.3.6.1.4.1.2011.5.25.19.2.2 hwSysReloadNotification

Description

The board was reboot. (ReloadIndex=[ReloadIndex], ReloadImage=[ReloadImage], ReloadCfg=[ReloadCfg], ReloadReason=[ReloadReason], ReloadTime=[ReloadTime], ReloadAction=[ReloadAction], ReloadPaf=[ReloadPaf], ReloadLicense=[ReloadLicense], ReloadPatch=[ReloadPatch]).

This trap is generated when the system restarts.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwSysReloadNotification

Trap OID

1.3.6.1.4.1.2011.5.25.19.2.2

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

ReloadIndex

Index of the reload plan

ReloadImage

Index of the reload image file

ReloadCfg

Index of the reload configuration file

ReloadReason

Reload reason

ReloadTime

Reload time

ReloadAction

Reload action

ReloadPaf

Index of the reload PAF file

ReloadLicense

Index of the reload license file

ReloadPatch

Index of the reload patch file

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.19.1.3.3.1.4

hwSysReloadImage

hwSysReloadScheduleIndex

1.3.6.1.4.1.2011.5.25.19.1.3.3.1.3

hwSysReloadCfgFile

hwSysReloadScheduleIndex

1.3.6.1.4.1.2011.5.25.19.1.3.3.1.5

hwSysReloadReason

hwSysReloadScheduleIndex

1.3.6.1.4.1.2011.5.25.19.1.3.3.1.6

hwSysReloadScheduleTime

hwSysReloadScheduleIndex

1.3.6.1.4.1.2011.5.25.19.1.3.2

hwSysReloadAction

N/A

1.3.6.1.4.1.2011.5.25.19.1.3.3.1.8

hwSysReloadPafFile

hwSysReloadScheduleIndex

1.3.6.1.4.1.2011.5.25.19.1.3.3.1.9

hwSysReloadLicenseFile

hwSysReloadScheduleIndex

1.3.6.1.4.1.2011.5.25.19.1.3.3.1.10

hwSysReloadPatchFile

hwSysReloadScheduleIndex

1.3.6.1.4.1.2011.5.25.19.1.3.3.1.15

hwSysReloadAndroidFile

hwSysReloadScheduleIndex

Impact on the System

Services are not affected.

Possible Causes

The system succeeded in restarting the image file.

Procedure
  • The log is informational only, and no action is required.

SYSTEM_1.3.6.1.4.1.2011.5.25.19.2.8 hwSysSlaveSwitchSuccessNotification

Description

Succeeded to run slave switch with SlvSwitchIndex [SlvSwitchIndex], ChassisNum[ChassisNum], SlaveSwitchSrc[SlaveSwitchSrc], SlaveSwitchDst[SlaveSwitchDst].

The master/slave main control board switchover succeeded.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Critical

Mnemonic Code

hwSysSlaveSwitchSuccessNotification

Trap OID

1.3.6.1.4.1.2011.5.25.19.2.8

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

[SlvSwitchIndex]

Index of a master/slave main control board switchover

[ChassisNum]

Number of a chassis on which a master/slave main control board switchover is performed

[SlaveSwitchSrc]

Source end of a master/slave main control board switchover

[SlaveSwitchDst]

Target end of a master/slave main control board switchover

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.19.1.3.7.1.2

hwSysSlaveSwitchChassisNum

hwSysSlaveSwitchIndex

1.3.6.1.4.1.2011.5.25.19.1.3.7.1.5

hwSysSlaveSwitchSrc

hwSysSlaveSwitchIndex

1.3.6.1.4.1.2011.5.25.19.1.3.7.1.6

hwSysSlaveSwitchDst

hwSysSlaveSwitchIndex

Impact on the System

None

Possible Causes

The device successfully performed a master/slave main control board switchover.

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

SYSTEM_1.3.6.1.4.1.2011.5.25.19.2.9 hwSysSlaveSwitchFailNotification

Description

Failed to run slave switch with SlvSwitchIndex [SlvSwitchIndex], ChassisNum[ChassisNum].

A master/slave main control board switchover failed.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Critical

Mnemonic Code

hwSysSlaveSwitchFailNotification

Trap OID

1.3.6.1.4.1.2011.5.25.19.2.9

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

[SlvSwitchIndex]

Index of a master/slave main control board switchover

[ChassisNum]

Number of a chassis on which a master/slave main control board switchover is performed

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.19.1.3.7.1.2

hwSysSlaveSwitchChassisNum

hwSysSlaveSwitchIndex

Impact on the System

User services may be interrupted.

Possible Causes

The slave switch is Up.

Procedure
  • Check wether the slave switch is Up.
    • If the slave switch is Up, go to step 3.
    • If the slave switch is not Up, go to step 2.
  • Install the slave switch and perform a master/slave switchover. Check whether the alarm is cleared.
    • If the alarm is cleared, go to Step 4.
    • If the alarm persists, go to Step 3.
  • Collect trap, log, and configuration information, and contact technical support personnel.
  • End.

SYSTEM_1.3.6.1.4.1.2011.5.25.19.2.5.1 hwPatchErrorTrap

Description

Failed to operate patch. (PatchErrorIndex=[PatchErrorIndex], SlotIndex=[SlotIndex], PkgIndex=[PkgIndex], ErrorCode=[ErrorCode], PkgName=[PkgName])

The patch operation failed.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Critical

Mnemonic Code

hwPatchErrorTrap

Trap OID

1.3.6.1.4.1.2011.5.25.19.2.5.1

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

PatchErrorIndex

Index of a patch error.

SlotIndex

Index of a device resides.

PkgIndex

Index of a patch package.

ErrorCode

Error code for an operation.

PkgName

Name of a patch package.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.19.1.8.5.4.1.2

hwPatchErrorSlot

hwPatchErrorIndex

1.3.6.1.4.1.2011.5.25.19.1.8.5.4.1.4

hwPatchErrorPatchIndex

hwPatchErrorIndex

1.3.6.1.4.1.2011.5.25.19.1.8.5.4.1.5

hwPatchErrorCode

hwPatchErrorIndex

1.3.6.1.4.1.2011.5.25.19.1.8.5.4.1.3

hwPatchErrorPatchFileName

hwPatchErrorIndex

Impact on the System

Services will not be affected.

Possible Causes
  1. The patch operation failed.
Procedure
  • Rectify the fault based on the information about the specific error code.

SYSTEM_1.3.6.1.4.1.2011.5.25.19.2.5.4 hwPatchUpdateTrap

Description

The patch with slot [PatchSlotIndex], patch index [PatchIndex], version [PatchVersion] and type [PatchType] has updated to the state [PatchState].

The state of the patch has been changed.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Notice

Mnemonic Code

hwPatchUpdateTrap

Trap OID

1.3.6.1.4.1.2011.5.25.19.2.5.4

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

[PatchSlotIndex]

Index of a device resides.

[PatchIndex]

Index of a patch package.

[PatchVersion]

Version of a patch.

[PatchType]

Type of a patch.

[PatchState]

State of a patch.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.19.1.8.5.1.1.4

hwPatchVersion

hwPatchSlotIndex;hwPatchIndex

1.3.6.1.4.1.2011.5.25.19.1.8.5.1.1.10

hwPatchType

hwPatchSlotIndex;hwPatchIndex

1.3.6.1.4.1.2011.5.25.19.1.8.5.1.1.14

hwPatchOperateState

hwPatchSlotIndex;hwPatchIndex

Impact on the System

Services will not be affected.

Possible Causes
  1. The patch state is changed.
Procedure
  • This log is generated when configurations are changed. No action is required.

SYSTEM_1.3.6.1.4.1.2011.5.25.19.2.11 hwPatchInstallFail

Description

Patch package installation failed. (SlotIndex=[SlotIndex], PatchIndex=[PatchIndex], PackageName=[PackageName], PackageVersion=[PackageVersion], FailReason=[FailReason])

The patch failed to be installed.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwPatchInstallFail

Trap OID

1.3.6.1.4.1.2011.5.25.19.2.11

Alarm ID

0x0d160004

Alarm Type

processingErrorAlarm

Raise or Clear

Raise

Match trap

Clear-alarm trap: SYSTEM_1.3.6.1.4.1.2011.5.25.19.2.12 hwPatchInstallFailClear

Parameters

Parameter

Description

SlotIndex

Indicates the index of the board on which the patch installation failed.

PatchIndex

Indicates the patch index.

PackageName

Indicates the patch name.

PackageVersion

Indicates the patch version.

FailReason

Indicates the reason for patch installation failure.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.19.1.8.5.1.1.3

hwPatchUsedFileName

hwPatchSlotIndex;

hwPatchIndex

1.3.6.1.4.1.2011.5.25.19.1.8.5.1.1.4

hwPatchVersion

hwPatchSlotIndex;

hwPatchIndex

1.3.6.1.4.1.2011.5.25.19.1.8.1.8

hwPatchFailReason

N/A

Impact on the System

Services are not affected.

Possible Causes

Cause 1: Failed to read the configuration information of the patch package.

Cause 2: Failed to get the patch package.

Cause 3: There was insufficient memory space for the patch package.

Cause 4: The patch conflicted with the previous one.

Cause 5: The patch package version was incorrect.

Procedure
  • Cause 1: Failed to read the configuration information of the patch package.
    1. Re-install the patch package. After the installation is complete, run the display patch-information command to check the patch package status.
      • If the status is run, the patch package has been successfully installed and no action is required.
      • If the status is not run, go to Step 2.
    2. Collect the alarm information, log information, and configurations, and then contact technical support personnel.
  • Cause 2: Failed to get the patch package.
    1. Collect the alarm information, log information, and configurations, and then contact technical support personnel.
  • Cause 3: There was insufficient memory space for the patch package.
    1. Collect the alarm information, log information, and configurations, and then contact technical support personnel.
  • Cause 4: The patch conflicted with the previous one.
    1. Collect the alarm information, log information, and configurations, and then contact technical support personnel.
  • Cause 5: The patch package version was incorrect.
    1. Collect the alarm information, log information, and configurations, and then contact technical support personnel.

SYSTEM_1.3.6.1.4.1.2011.5.25.19.2.12 hwPatchInstallFailClear

Description

The patch-installation failure alarm is cleared. (SlotIndex=[SlotIndex], PatchIndex=[PatchIndex], PackageName=[PackageName], PackageVersion=[PackageVersion], FailReason=[FailReason])

The patch-installation failure alarm was cleared.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwPatchInstallFailClear

Trap OID

1.3.6.1.4.1.2011.5.25.19.2.12

Alarm ID

0x0d160004

Alarm Type

processingErrorAlarm

Raise or Clear

Clear

Match trap

Clear-alarm trap: SYSTEM_1.3.6.1.4.1.2011.5.25.19.2.11 hwPatchInstallFail

Parameters

Parameter

Description

SlotIndex

Indicates the index of the board on which the patch installation failed.

PatchIndex

Indicates the patch index.

PackageName

Indicates the patch name.

PackageVersion

Indicates the patch version.

FailReason

Indicates the reason for patch installation failure.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.19.1.8.5.1.1.3

hwPatchUsedFileName

hwPatchSlotIndex;

hwPatchIndex

1.3.6.1.4.1.2011.5.25.19.1.8.5.1.1.4

hwPatchVersion

hwPatchSlotIndex;

hwPatchIndex

1.3.6.1.4.1.2011.5.25.19.1.8.1.8

hwPatchFailReason

N/A

Impact on the System

Services are not affected.

Possible Causes

The patch-installation failure alarm was cleared.

Procedure
  • The log is informational only, and no action is required.

SYSTEM_1.3.6.1.4.1.2011.5.25.129.2.4.1 hwCPUUtilizationRisingAlarm

Description

The CPU usage exceeded the pre-set overload threshold.(TrapSeverity=[TrapSeverity], ProbableCause=[ProbableCause], EventType=[EventType], PhysicalIndex=[PhysicalIndex], PhysicalName=[PhysicalName], RelativeResource=[RelativeResource], UsageType=[UsageType], SubIndex=[SubIndex], CpuUsage=[CpuUsage], Unit=[Unit], CpuUsageThreshold=[CpuUsageThreshold])

CPU usage was sampled for a period of time. In one sampling period (overload times x sampling interval), if each CPU usage sample exceeded the pre-set overload threshold, this alarm was generated.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwCPUUtilizationRisingAlarm

Trap OID

1.3.6.1.4.1.2011.5.25.129.2.4.1

Alarm ID

0x00010084

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Raise

Match trap

SYSTEM_1.3.6.1.4.1.2011.5.25.129.2.4.2 hwCPUUtilizationResume

Parameters

Parameter

Description

TrapSeverity

Alarm severity

ProbableCause

Possible cause

EventType

Alarm type

PhysicalIndex

Physical index

PhysicalName

Entity name

RelativeResource

Relevant resource name

UsageType

Overload type

SubIndex

Entity sub-index

CpuUsage

CPU usage

Unit

Unit

CpuUsageThreshold

Overload threshold

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.129.1.1

hwBaseTrapSeverity

N/A

1.3.6.1.4.1.2011.5.25.129.1.2

hwBaseTrapProbableCause

N/A

1.3.6.1.4.1.2011.5.25.129.1.3

hwBaseTrapEventType

N/A

1.3.6.1.2.1.47.1.1.1.1.7

entPhysicalName

entPhysicalIndex;

1.3.6.1.4.1.2011.5.25.129.1.4

hwBaseTrapRelativeResource

N/A

1.3.6.1.4.1.2011.5.25.129.1.7.1.3

hwBaseUsageValue

entPhysicalIndex;

hwBaseUsageType;

hwBaseUsageIndex;

1.3.6.1.4.1.2011.5.25.129.1.7.1.4

hwBaseUsageUnit

entPhysicalIndex;

hwBaseUsageType;

hwBaseUsageIndex;

1.3.6.1.4.1.2011.5.25.129.1.7.1.5

hwBaseUsageThreshold

entPhysicalIndex;

hwBaseUsageType;

hwBaseUsageIndex;

Impact on the System

If the CPU usage is high for a long period of time, services cannot be processed in time, and the system performance is affected. The system performance, for example, time taken to process user operations, neighbor status, and route convergence performance, will be affected.

Possible Causes

The CPU usage exceeded the pre-set overload threshold.

Procedure
  • Cause: The CPU usage exceeded the pre-set overload threshold.
    1. Run the display cpu threshold command to check the CPU usage and its overload threshold.
      • If CPU usage exceeds the overload threshold, go to Step 2.
      • If CPU usage is below the overload threshold, go to Step 4.
    2. Delete unnecessary services and configurations to reduce CPU usage, and then check whether the alarm is cleared.
      • If the recovery alarm is generated, the fault is rectified.
      • If this alarm persists, go to Step 3.
    3. Run the set cpu threshold threshold-value [ restore restore-threshold-value ] [ slot slot-id ] command to adjust the overload threshold, and then check whether the alarm is cleared.
      • If the recovery alarm is generated, the fault is rectified.
      • If this alarm persists, go to Step 4.
    4. Collect log messages and contact technical support personnel.

SYSTEM_1.3.6.1.4.1.2011.5.25.129.2.4.2 hwCPUUtilizationResume

Description

The CPU usage falls below the pre-set clear threshold.(TrapSeverity=[TrapSeverity], ProbableCause=[ProbableCause], EventType=[EventType], PhysicalIndex=[PhysicalIndex], PhysicalName=[PhysicalName], RelativeResource=[RelativeResource], UsageType=[UsageType], SubIndex=[SubIndex], CpuUsage=[CpuUsage], Unit=[Unit], CpuUsageThreshold=[CpuUsageThreshold])

CPU usage was sampled for a period of time. In one sampling period (overload times x sampling interval), if every sampled CPU usage is below the pre-set clear threshold, this alarm was generated.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwCPUUtilizationResume

Trap OID

1.3.6.1.4.1.2011.5.25.129.2.4.2

Alarm ID

0x00010084

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Clear

Match trap

SYSTEM_1.3.6.1.4.1.2011.5.25.129.2.4.1 hwCPUUtilizationRisingAlarm

Parameters

Parameter

Description

TrapSeverity

Alarm severity

ProbableCause

Possible cause

EventType

Alarm type

PhysicalIndex

Physical index

PhysicalName

Entity name

RelativeResource

Relevant resource name

UsageType

Overload type

SubIndex

Entity sub-index

CpuUsage

CPU usage

Unit

Unit

CpuUsageThreshold

Overload threshold

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.129.1.1

hwBaseTrapSeverity

N/A

1.3.6.1.4.1.2011.5.25.129.1.2

hwBaseTrapProbableCause

N/A

1.3.6.1.4.1.2011.5.25.129.1.3

hwBaseTrapEventType

N/A

1.3.6.1.2.1.47.1.1.1.1.7

entPhysicalName

entPhysicalIndex;

1.3.6.1.4.1.2011.5.25.129.1.4

hwBaseTrapRelativeResource

N/A

1.3.6.1.4.1.2011.5.25.129.1.7.1.3

hwBaseUsageValue

entPhysicalIndex;

hwBaseUsageType;

hwBaseUsageIndex

1.3.6.1.4.1.2011.5.25.129.1.7.1.4

hwBaseUsageUnit

entPhysicalIndex;

hwBaseUsageType;

hwBaseUsageIndex

1.3.6.1.4.1.2011.5.25.129.1.7.1.5

hwBaseUsageThreshold

entPhysicalIndex

hwBaseUsageType;

hwBaseUsageIndex

Impact on the System

Services are not affected.

Possible Causes

The CPU usage fell below the pre-set overload threshold.

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

SYSTEM_1.3.6.1.4.1.2011.5.25.129.2.6.1 hwStorageUtilizationRisingAlarm

Description

The storage usage exceeded the pre-set overload threshold.(TrapSeverity=[TrapSeverity], ProbableCause=[ProbableCause], EventType=[EventType], PhysicalIndex=[PhysicalIndex], PhysicalName=[PhysicalName], RelativeResource=[RelativeResource], UsageType=[UsageType], SubIndex=[SubIndex], UsageValue=[UsageValue], Unit=[Unit], UsageThreshold=[UsageThreshold])

Memory or storage usage was sampled for a period of time. In one sampling period (overload times x sampling interval), if each memory or storage usage sample exceeded the pre-set overload threshold, this alarm was generated.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwStorageUtilizationRisingAlarm

Trap OID

1.3.6.1.4.1.2011.5.25.129.2.6.1

Alarm ID

0x00010085

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Raise

Match trap

SYSTEM_1.3.6.1.4.1.2011.5.25.129.2.6.2 hwStorageUtilizationResume

Parameters

Parameter

Description

TrapSeverity

Alarm severity

ProbableCause

Possible cause, values are as follows:

  • 75264:Memory usage exceeded the overload threshold.
  • 75265:Storage usage exceeded the overload threshold.
  • 75268:Storage usage exceeded the limit threshold.

EventType

Alarm type

PhysicalIndex

Physical index

PhysicalName

Entity name

RelativeResource

Relevant resource name

UsageType

Overload type

SubIndex

Entity sub-index

UsageValue

Storage usage

Unit

Unit

UsageThreshold

Overload threshold

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.129.1.1

hwBaseTrapSeverity

N/A

1.3.6.1.4.1.2011.5.25.129.1.2

hwBaseTrapProbableCause

N/A

1.3.6.1.4.1.2011.5.25.129.1.3

hwBaseTrapEventType

N/A

1.3.6.1.2.1.47.1.1.1.1.7

entPhysicalName

entPhysicalIndex;

1.3.6.1.4.1.2011.5.25.129.1.4

hwBaseTrapRelativeResource

N/A

1.3.6.1.4.1.2011.5.25.129.1.7.1.3

hwBaseUsageValue

entPhysicalIndex;hwBaseUsageType;hwBaseUsageIndex;

1.3.6.1.4.1.2011.5.25.129.1.7.1.4

hwBaseUsageUnit

entPhysicalIndex;hwBaseUsageType;hwBaseUsageIndex;

1.3.6.1.4.1.2011.5.25.129.1.7.1.5

hwBaseUsageThreshold

entPhysicalIndex;hwBaseUsageType;hwBaseUsageIndex;

Impact on the System
  1. If services cannot successfully obtain memory resources, the system automatically restarts.
  2. If the remaining space in the storage is insufficient, the log function and software upgrade are affected.
Possible Causes

Cause 1: The memory usage exceeded the pre-set overload threshold.

Cause 2: The storage usage of the storage medium exceeded the pre-set overload threshold.

Cause 3: The storage usage of the storage medium exceeded the pre-set limit threshold.

Procedure
  • Cause 1: The memory usage exceeded the pre-set overload threshold.
    1. Run the display memory threshold command to check the memory usage and its upper threshold.
      • If memory usage exceeds the overload threshold, go to Step 2.
      • If memory usage is below the overload threshold, go to Step 4.
    2. Delete unnecessary services and configurations to reduce memory usage, and then check whether the alarm is cleared.
      • If the clear alarm is generated, the fault is rectified.
      • If this alarm persists, go to Step 3.
    3. Run the set memory threshold threshold-value [ restore restore-threshold-value ] [ slot slot-id ] command to adjust the memory overload threshold, and then check whether the alarm is cleared.
      • If the clear alarm is generated, the fault is rectified.
      • If this alarm persists, go to Step 4.
    4. Collect log messages and contact technical support personnel.
  • Cause 2: The storage usage exceeded the pre-set overload threshold.
    1. Run the cd flash: command to access the directory, and then run the dir command to view the storage usage.
      • If storage usage is higher than the overload threshold, go to Step 2.
      • If storage usage is lower than the overload threshold, go to Step 3.
    2. Run the delete /unreserved *.cc command and the delete /unreserved *.PAT command to delete the unnecessary .cc and .PAT files. Run the reset recycle-bin command to clear the cache and reduce storage usage. Then check whether the alarm is cleared.
      • For a stack system, you need to perform this step on both the master and slave devices. Before performing this step, run the cd Stack_ID#flash: command to access the directory of the corresponding storage medium.
      • If the clear alarm is generated, the fault is rectified.
      • If this alarm persists, go to Step 3.
    3. Collect log messages and contact technical support personnel.
  • Cause 3: The storage usage of the storage medium exceeded the pre-set limit threshold.
    1. Run the cd flash: command to access the directory of a storage medium, and then run the dir command to view the storage usage of the storage medium.
      • If storage usage of the storage medium is higher than the limit threshold, go to Step 2.
      • If storage usage of the storage medium is lower than the limit threshold, go to Step 3.
    2. Run the delete /unreserved *.cc command and the delete /unreserved *.PAT command to delete the unnecessary .cc and .PAT files. Run the reset recycle-bin command to clear the cache and reduce storage usage. Then check whether the alarm is cleared.
      • For a stack system, you need to perform this step on both the master and slave devices. Before performing this step, run the cd Stack_ID#flash: command to access the directory of the corresponding storage medium.
      • If the clear alarm is generated, the fault is rectified.
      • If this alarm persists, go to Step 3.
    3. Collect log messages and contact technical support personnel.

SYSTEM_1.3.6.1.4.1.2011.5.25.129.2.6.2 hwStorageUtilizationResume

Description

The storage usage falls below the pre-set clear threshold.(TrapSeverity=[TrapSeverity], ProbableCause=[ProbableCause], EventType=[EventType], PhysicalIndex=[PhysicalIndex], PhysicalName=[PhysicalName], RelativeResource=[RelativeResource], UsageType=[UsageType], SubIndex=[SubIndex], UsageValue=[UsageValue], Unit=[Unit], UsageThreshold=[UsageThreshold])

Memory or storage space usage was sampled for a period of time. In one sampling period (overload times x sampling interval), if every sampled memory or storage space usage was below the pre-set clear threshold, this alarm was generated.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwStorageUtilizationResume

Trap OID

1.3.6.1.4.1.2011.5.25.129.2.6.2

Alarm ID

0x00010085

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Clear

Match trap

SYSTEM_1.3.6.1.4.1.2011.5.25.129.2.6.1 hwStorageUtilizationRisingAlarm

Parameters

Parameter

Description

TrapSeverity

Alarm severity

ProbableCause

Possible cause

EventType

Alarm type

PhysicalIndex

Physical index

PhysicalName

Entity name

RelativeResource

Relevant resource name

UsageType

Overload type

SubIndex

Entity sub-index

UsageValue

Storage usage

Unit

Unit

UsageThreshold

Overload threshold

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.129.1.1

hwBaseTrapSeverity

N/A

1.3.6.1.4.1.2011.5.25.129.1.2

hwBaseTrapProbableCause

N/A

1.3.6.1.4.1.2011.5.25.129.1.3

hwBaseTrapEventType

N/A

1.3.6.1.2.1.47.1.1.1.1.7

entPhysicalName

entPhysicalIndex;

1.3.6.1.4.1.2011.5.25.129.1.4

hwBaseTrapRelativeResource

N/A

1.3.6.1.4.1.2011.5.25.129.1.7.1.3

hwBaseUsageValue

entPhysicalIndex;hwBaseUsageType;hwBaseUsageIndex;

1.3.6.1.4.1.2011.5.25.129.1.7.1.4

hwBaseUsageUnit

entPhysicalIndex;hwBaseUsageType;hwBaseUsageIndex;

1.3.6.1.4.1.2011.5.25.129.1.7.1.5

hwBaseUsageThreshold

entPhysicalIndex;hwBaseUsageType;hwBaseUsageIndex;

Impact on the System

Services are not affected.

Possible Causes

Cause 1: The memory usage fell below the pre-set overload threshold.

Cause 2: The storage usage fell below the default overload threshold.

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

SYSTEM_1.3.6.1.4.1.2011.5.25.219.2.11.1 hwSystemConfigError

Description

A system configuration error occurs. ( EntityTrapFaultID = [EntityTrapFaultID])

The system configuration was incorrect.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwSystemConfigError

Trap OID

1.3.6.1.4.1.2011.5.25.219.2.11.1

Alarm ID

0x0d300004

Alarm Type

equipmentAlarm

Raise or Clear

Raise

Match trap

SYSTEM_1.3.6.1.4.1.2011.5.25.219.2.11.2 hwSystemConfigResume

Parameters

Parameter

Description

EntityTrapFaultID

Trap error codes.

  • EntityTrapFaultID=144130 indicates that the package versions of the master and slave boards were inconsistent.
  • EntityTrapFaultID=144133 indicates that the memory of the master and slave boards were inconsistent.
VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.219.1.3

hwEntityTrapFaultID

N/A

Impact on the System
  • The slave board cannot be activated when the package versions of the master and slave boards are inconsistent.
  • The master/slave main control board switchover may fail if the memory on the master main control board is inconsistent with that on the slave main control board.
Possible Causes
  • Cause 1: The package versions of the master and slave boards were inconsistent.
  • Cause 2: The memory of the master and slave boards were inconsistent.
Procedure
  • Cause 1: The package versions of the master and slave boards were inconsistent.
    1. Run the startup system-software system-file [ all | slave-board | slot slot-id ] command to configure the slave board version to be consistent with the master board version. Run the reset command to reset the slave board. Wait for a period of time, and then check whether the alarm is cleared.
      • If yes, go to Step 3.
      • If No, go to Step 2.
    2. Collect the alarm information, log information, and configuration information, and then contact technical support personnel.
    3. End.
  • Cause 2: Collect the alarm information, log information, and configuration information, and then contact technical support personnel for memory replacement to ensure the consistency.

SYSTEM_1.3.6.1.4.1.2011.5.25.219.2.11.2 hwSystemConfigResume

Description

The system configuration error has been rectified. ( EntityTrapFaultID = [EntityTrapFaultID])

The system configuration was corrected.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwSystemConfigError

Trap OID

1.3.6.1.4.1.2011.5.25.219.2.11.2

Alarm ID

0x0d300004

Alarm Type

equipmentAlarm

Raise or Clear

Clear

Match trap

SYSTEM_1.3.6.1.4.1.2011.5.25.219.2.11.1 hwSystemConfigError

Parameters

Parameter

Description

EntityTrapFaultID

Trap error codes.

  • EntityTrapFaultID=144130 indicates that the package versions of the master and slave boards were inconsistent.
VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.219.1.3

hwEntityTrapFaultID

N/A

Impact on the System

Services are not affected.

Possible Causes

Cause 1: The package versions of the master and slave boards changed from being inconsistent to being consistent.

Cause 2: The versions of the PAF and startup package changed from being inconsistent to being consistent.

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

SYSTEM_1.3.6.1.4.1.2011.5.25.219.2.2.17 hwBoardHeartbeatTimeout

Description

The heartbeat connection between the board and main control board timed out. (EntityPhysicalIndex=[EntityPhysicalIndex], PhysicalIndex=[PhysicalIndex], PhysicalName=[PhysicalName])

The heartbeat packets between a board and the main control board were lost.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwBoardHeartbeatTimeout

Trap OID

1.3.6.1.4.1.2011.5.25.219.2.2.17

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

EntityPhysicalIndex

Heartbeat index

PhysicalIndex

Physical index

PhysicalName

Name of a physical entity

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.219.1.1

hwEntityPhysicalIndex

N/A

1.3.6.1.2.1.47.1.1.1.1.7

entPhysicalName

entPhysicalIndex

Impact on the System

Services on the board will be affected.

Possible Causes

Cause 1: A communication failure occurred.

Cause 2: The system was busy.

Procedure
  • Cause 1: A communication failure occurred.
    1. Check whether the board is properly installed or whether a link is faulty.
  • Cause 2: The system was busy.
    1. Check whether the CPU usage on the board is too high.

SYSTEM_1.3.6.1.4.1.2011.5.25.219.2.2.18 hwBoardHeartbeatResume

Description

The heartbeat connection between the board and main control board was restored. (EntityPhysicalIndex=[EntityPhysicalIndex], PhysicalIndex=[PhysicalIndex], PhysicalName=[PhysicalName])

The heartbeat packets between a board and the main control board were restored.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwBoardHeartbeatResume

Trap OID

1.3.6.1.4.1.2011.5.25.219.2.2.18

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

EntityPhysicalIndex

Heartbeat index

PhysicalIndex

Physical index

PhysicalName

Name of a physical entity

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.219.1.1

hwEntityPhysicalIndex

N/A

1.3.6.1.2.1.47.1.1.1.1.7

entPhysicalName

entPhysicalIndex

Impact on the System

Services will not be affected.

Possible Causes

Services were restored.

Procedure
  • This message is informational only, and no action is required.

SYSTEM_1.3.6.1.4.1.2011.5.25.19.2.13 hwSumUpgradeSuccess

Description

For system [sysIndex], upgrade [CurrentPackageVersion] successfully.

The system version was upgraded.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Notice

Mnemonic Code

hwSumUpgradeSuccess

Trap OID

1.3.6.1.4.1.2011.5.25.19.2.13

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

[sysIndex]

Index of a system

[CurrentPackageVersion]

Version of the current system

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.19.1.4.2.1.5

hwSysImageVersion

hwSysImageIndex

Impact on the System

Services will not be affected.

Possible Causes

The system version was upgraded.

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

SYSTEM_1.3.6.1.4.1.2011.5.25.19.2.15 hwSysImageErrorNotification

Description

The next startup image package is error. (imageIndex=[imageIndex], curImageName=[curImageName], nextImageName=[nextImageName], errReason=[errReason])

An error occurred in the next startup image package.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwSysImageErrorNotification

Trap OID

1.3.6.1.4.1.2011.5.25.19.2.15

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

imageIndex

Index of the image file

curImageName

Name of the current image file

nextImageName

Name of the next startup image file

errReason

Cause for an error

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.19.1.4.2.1.2

hwSysImageName

hwSysImageIndex

1.3.6.1.4.1.2011.5.25.19.1.4.2.1.2

hwSysImageName

hwSysImageIndex

1.3.6.1.4.1.2011.5.25.19.1.4.2.1.6

hwSysImageReason

hwSysImageIndex

Impact on the System

Services will not be affected.

Possible Causes

An error occurred in the next startup image file.

Procedure
  • Replace the startup image file in which the error occurred.
Translation
Download
Updated: 2018-08-16

Document ID: EDOC1000015902

Views: 208246

Downloads: 1590

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