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

HWCM

HWCM_1.3.6.1.4.1.2011.6.10.2.1 hwCfgManEventlog

Description

HWCM/4/CFGCHANGE:OID [oid] Configure changed. (EventIndex=[integer], CommandSource=[integer], ConfigSource=[integer], ConfigDestination=[integer])

The trap was generated when the configuration changed.

Attribute

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

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

EventIndex

Indicates the index of EventTable.

CommandSource

Indicates a command source, that is, a command delivery mode that triggers changes.

  • 1. Command proxy
  • 2. Simple Network Management Protocol (SNMP)
  • 4. Others

ConfigSource

Configuration source, that is, the change source.

  • 1. Configuration file clearance
  • 2. Configuration file modification
  • 3. Tool-side configuration operation
  • 4. Saving of the next-startup configuration file
  • 5. Non-configuration file renaming or moving
  • 6. FTP-related get or put operation
  • 7. Hot swap of an interface board

ConfigDestination

Configuration destination, that is, the object to be changed.

  • 2. Running configurations
  • 4. Startup configuration file

Impact on the System

System will not be affected.

Possible Causes

Operations, such as copy, delete, rename, move, and download, were performed, causing the startup configuration file to be modified.

Procedure

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

Related Information

None

HWCM_1.3.6.1.4.1.2011.6.10.2.2 hwCfgOperateCompletion

Description

HWCM/4/CFGCOPY:OID [oid] Configure copy. (OperationIndex=[integer], OperationResultIndex=[integer], OperationType=[integer], OperationTime=[timetick], OperationState=[integer], OperationEndTime=[timetick])

The trap was generated when the configuration was complete. The configuration includes:
  1. Uploaded the configuration file from the PC and then delivered the configuration file.

  2. Downloaded the current configuration from the system to the PC.

  3. Saved the current configuration to the device.

  4. Ran the configuration file.

  5. Uploaded the configuration file from the PC but did not deliver it.

  6. Downloaded the configuration file from the system to the PC.

Attribute

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

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

OperationIndex

Indicates the operation index.

OperationResultIndex

Indicates the index of the operation result.

OperationType

Indicates the operation type.

OperationTime

Indicates operation time.

OperationState

Indicates the operating status.

OperationEndTime

Indicates end time of an operation.

Impact on the System

If the configurations are delivered to and performed successfully on the device, the current configuration on the device will be changed. The impacts on the current configuration depend on the specific configuration that is delivered.

Possible Causes

The trap was triggered when the NMS of the device performed the following operations. The trap was used to record the configuration results. Operations included:

  1. Uploaded the configuration file from the PC and then delivered the configuration file.

  2. Downloaded the current configuration from the system to the PC.

  3. Saved the current configuration to the device.

  4. Ran the configuration file.

  5. Uploaded the configuration file from the PC but did not deliver it.

  6. Downloaded the configuration file from the system to the PC.

Procedure

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

Related Information

None

HWCM_1.3.6.1.4.1.2011.6.10.2.5 hwCfgB2STransferFail

Description

HWCM/4/HWCM_B2S_TRANSFAIL: OID [oid] Failed to transfer the configuration file to (index=[integer]) server [server-ip] through [transport-type] when automatically backing up the configuration.

Failed to set up a connection with the server when backing up the configuration file to the server probably because the configuration parameter was incorrect or the server was unreachable.

Attribute

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

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
index Indicates the index of the backup server table.
[server-ip] Indicates the IP address of the server.
[transport-type] Indicates the protocol used to transmit backup configurations. Possible causes can be:
  • FTP
  • TFTP
  • SFTP

Impact on the System

This alarm indicates that the configuration file fails to be backed up to the server this time. If this alarm is generated multiple times, the configuration is probably incorrect or the link is probably faulty. You need to check the configuration and network condition.

Possible Causes

  • The server was unreachable.
  • The password was incorrect.
  • The user name was inexistent or the path to the server was inexistent.

Procedure

  1. Run the ping command on the device to ping the server to check whether the server is reachable.

    • Y=>2.

    • N=>4.

  2. Check the set save-configuration backup-to-server server configuration to determine whether the correct user name and password are used.

    • If the correct user name and password are used, go to Step 3.

    • If the correct user name and password are not used, reset the user name and password and go to Step 5.

  3. Check the set save-configuration backup-to-server path configuration to determine whether the correct path is used.

    • If the correct path is used, go to Step 4.

    • If the correct path is not used, reconfigure a path and go to Step 4.

  4. Collect alarm information and configuration information, and then contact technical support personnel.
  5. End.

Related Information

None.

HWCM_1.3.6.1.4.1.2011.6.10.2.6 hwCfgB2SOperate

Description

HWCM/4/HWCM_B2S_BACKUP:OID [oid] Began to back up the current configuration to the server.

The configuration file was backed up to the server.

Attribute

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

Parameters

Name Meaning

OID

Indicates the MIB object ID of the alarm.

Impact on the System

This alarm indicates that time when the configuration file is backed up to the server is reached.

Possible Causes

The timer expired, and the configuration file was backed up to the server.

Procedure

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

Related Information

None.

HWCM_1.3.6.1.4.1.2011.6.10.2.7 hwCfgRestoreFail

Description

HWCM/2/RESTORE_CONFIGURATION_FAIL:OID [OID] Failed to restore system configurations.(ErrCode=[ErrorCode])

Failed to restore the system configurations.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.6.10.2.7 Major processingErrorAlarm(2)

Parameters

Name Meaning

OID

Indicates the MIB object ID of the alarm.

ErrorCode

Indicates the error code.

Impact on the System

Configurations for current services are lost.

Possible Causes

The configuration database file was lost or damaged.

Procedure

  1. Run the display startup command to check the startup configuration file. Determine whether the file exists and has correct configuration data.

    • If the file exists and has correct configuration data, go to Step 2.

    • If the file does not exist or have correct configuration data, go to Step 4.

  2. Run the display configuration recover-result command to check configuration restoration failure details.
  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information

None

Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065855

Views: 4970

Downloads: 6

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