Time (TIME)

Time when the operation was performed.

Severity (LEVEL)

Severity level of the log.

User (USER)

Account name of the user who performed the operation.

Object (slot number) (MODULE(BAYID))

Object or module of the operation, and the slot number (if any) of the module.

Event (EVENT)

Operation details.

Result (RESULT)

Operation result.

Reason (REASON)

If the operation failed, this field displays the cause.

Time (TIME)

Time when the event occurred.

Severity (LEVEL)

Severity level of the event.

Object (slot number) (MODULE

/ BAYID)

Module of the event, and the slot number (if any) of the module.

Event (EVENT)

Event details.

1

Emergency

Emergency condition. For example, SYN attack, Tear Drop attack, and Ping of Death attack.

2

Alert

Action must be taken immediately. For example, firewall attack and key expiration.

3

Critical

Critical condition. For example, HA state change.

4

Error

Error condition. For example, anti-virus scanning failure and SSH server connection failure.

5

Warning

Warning condition. For example, email server connection failure and authentication failure, timeout, or success.

6

Notification

Normal but significant condition. For example, manual configuration change.

7

Informational

Informational message.

Message text

Set basic enclosure information

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / B16000 / Set basic enclosure information / SUCCESS

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object: B16000 enclosure

Event: Set basic enclosure information

Result: Succeeded.

Cause: None.

Explanation

Set the basic enclosure information successfully.

Recommended action

No action is required.

Message text

Primary OM module restarted

Variable fields

N/A

Severity level

Informational

Example

2019/03/15 11:27:04 / Informational / User1 / OM(bay2) / Primary OM module restarted/SUCCESS

Timestamp: 2019/09/20 11:27:04

Severity level: Informational

Username: User1

Object (slot number): OM module (slot 2)

Event: Restart the primary OM module.

Result: Succeeded.

Cause: None.

Explanation

Restarted the primary OM module successfully.

Recommended action

No action is required.

Message text

Obtain OM diagnostic-information logs

Variable fields

-

Severity level

Informational

Example

2019/03/15 11:27:04 / Informational / User1 / OM(bay2) / Obtain OM diagnostic-information logs/ FAILED / Network connection timed out

Timestamp: 2019/09/20 11:27:04

Severity level: Informational

Username: User1

Object (slot number): OM module (slot 2)

Event: Download the diagnostic-information file of the OM module in slot 2.

Result: Failed.

Cause: Communication timed out.

Explanation

Failed to download the diagnostic-information file of the OM module in slot 2, because the communication timed out.

Recommended action

Try again after a while. If the problem persists, export the log through the serial port and contact H3C Support.

Message text

Obtain OM diagfile logs

Variable fields

-

Severity level

Informational

Example

2019/03/15 11:27:04 / Informational / User1 / OM(bay2) / Obtain OM diagfile logs/ FAILED / Backup OM module is in abnormal state

Timestamp: 2019/09/20 11:27:04

Severity level: Informational

Username: User1

Object (slot number): OM module (slot 2)

Event: Download the diagfile file of the OM module in slot 2.

Result: Failed.

Cause: The OM module in slot 2 is abnormal.

Explanation

Failed to download the diagfile file of the OM module in slot 2, because the OM module is abnormal.

Recommended action

1.     Verify whether the OM module in slot 2 is abnormal.

¡     If the OM module is abnormal, resolve the issue.

¡     If the OM module is normal, go to the next step.

2.     Export the log through the serial port and contact H3C Support.

Message text

Obtain OM logfile logs

Variable fields

-

Severity level

Informational

Example

2019/03/15 11:27:04 / Informational / User1 / OM(bay2) / Obtain OM logfile logs/ FAILED / Backup OM module is in abnormal state

Timestamp: 2019/09/20 11:27:04

Severity level: Informational

Username: User1

Object (slot number): OM module (slot 2)

Event: Download the logfile file of the OM module in slot 2.

Result: Failed.

Cause: The OM module in slot 2 is abnormal.

Explanation

Failed to download the logfile file of the OM module in slot 2, because the OM module is abnormal.

Recommended action

1.     Verify whether the OM module in slot 2 is abnormal.

¡     If the OM module is abnormal, resolve the issue.

¡     If the OM module is normal, go to the next step.

3.     Export the log through the serial port and contact H3C Support.

Message text

Restore OM default configuration

Variable fields

-

Severity level

Informational

Example

2021/04/20 11:27:00 / Informational / User1 / OM(bay2) / Restore OM default configuration / SUCCESS

Timestamp: 2021/04/20 11:27:00

Severity level: Informational

Username: User1

Object (slot number): OM module (slot 2)

Event: Restore default OM configuration

Result: Succeeded.

Cause: None.

Explanation

Restarted the OM module and restored the default OM configuration successfully.

Recommended action

No action is required.

Message text

Restore OM default configuration

Variable fields

-

Severity level

Warning

Example

2021/04/20 11:27:00 / Warning / User1 / OM(bay2) / Restore OM default configuration / FAILED / Failed to delete configuration file

Timestamp: 2021/04/20 11:27:00

Severity level: Warning

Username: User1

Object (slot number): OM module (slot 2)

Event: Restore default OM configuration

Result: Failed.

Cause: Failed to delete the db configuration file.

Explanation

Failed to restore the default OM configuration, because the db configuration file failed to be deleted.

Recommended action

1.     Verify that the db configuration file on the OM module has been deleted.

2.     If the problem persists, export the log through the serial port, and then contact H3C Support.

Message text

Port ($1) status $2 to $3

Variable fields

$1: Type of the device connected to the interface.

$2: Original interface state.

$3: New interface state.

Severity level

Warning

Example

2019/01/28 14:21:29 / Warning / OM (bay2) / Port (connect Blade 1) status DOWN to UP

Timestamp: 2019/01/28 14:21:29

Severity level: Warning

Object (slot number): OM module (slot 2)

Event: The internal port that connects the OM module to the blade server or AE module comes up.

Explanation

The internal port that connects the OM module to the blade server or AE module comes up.

Recommended action

1.     Verify whether a blade server was inserted into the slot when the log was generated.

¡     If a blade server was inserted, no action is required.

¡     If no blade server was inserted, go to the next step.

3.     Verify whether the blade server in the slot was started or restarted when the log was generated.

¡     If the blade server was started or restarted, no action is required.

¡     If the blade server was not started or restarted, go to the next step.

4.     Verify whether the network adapter of the blade server was brought up in the operating system when the log was generated.

¡     If it was brought up, no action is required.

¡     If it was not brought up, go to the next step.

5.     Export the log and contact H3C Support.

Message text

Port ($1) status $2 to $3

Variable fields

$1: Type of the device connected to the interface.

$2: Original interface state.

$3: New interface state.

Severity level

Warning

Example

2019/01/28 14:21:29 / Warning / OM (bay2) / Port (connect Blade 1) status Up to Down

Timestamp: 2019/01/28 14:21:29

Severity level: Warning

Object (slot number): OM module (slot 2)

Event: The internal port that connects the OM module to the blade server goes down.

Explanation

The internal port that connects the OM module in slot 2 to the blade server in slot 1 goes down.

Recommended action

1.     Verify whether a blade server was removed from the slot when the log was generated.

¡     If it was removed, no action is required.

¡     If it was not removed, go to the next step.

2.     Verify whether the blade server in the slot was shut down or restarted when the log was generated.

¡     If it was shut down or restarted, no action is required.

¡     If it was not shut down or restarted, go to the next step.

3.     Verify whether the network adapter of the blade server was shut down in the operating system when the log was generated.

¡     If it was shut down, enable the port in the operating system of the blade server.

¡     If it was not shut down, go to the next step.

4.     Reset the HDM of the blade server on the OM webpage. Then, verify whether the port becomes normal on the OM webpage.

¡     If it becomes normal, no action is required.

¡     If it does not become normal, go to the next step.

5.     Export the log and contact H3C Support.

Message text

Management module inserted

Variable fields

-

Severity level

Warning

Example

2019/01/28 16:36:21 / Warning / OM (bay1) / Management module inserted

Timestamp: 2019/01/28 16:36:21

Severity level: Warning

Object (slot number): OM module (slot 1)

Event: An OM module was inserted to the enclosure.

Explanation

The OM module in slot 1 was inserted to the enclosure.

Recommended action

No action is required.

Message text

Management module removed

Variable fields

-

Severity level

Warning

Example

2019/03/13 17:53:28 / Warning / OM (bay1) / Management module removed

Timestamp: 2019/03/13 17:53:28

Severity level: Warning

Object (slot number): OM module (slot 1)

Event: An OM module was removed from the enclosure

Explanation

The OM module in slot 1 was removed from the enclosure.

Recommended action

No action is required.

Message text

Device state changed

Variable fields

-

Severity level

Warning

Example

2019/03/13 13:32:22 / Warning / OM (bay1) / Device state changed

Timestamp: 2019/03/13 13:32:22

Severity level: Warning

Object (slot number): OM module (slot 1)

Event: OM module state changed.

Explanation

The state of the OM module in slot 1 changed.

Recommended action

1.     Verify whether the OM module in the slot is abnormal on the OM webpage.

¡     If it is normal, no action is required.

¡     If it is abnormal, go to the next step.

2.     Verify whether the OM module was being restarted when the log was generated.

¡     If it was being restarted, no action is required.

¡     If it was not being restarted, go to the next step.

3.     Verify whether the temperature of the OM module reaches the threshold.

¡     If the temperature reaches the threshold, perform the following tasks to reduce the temperature: replace the faulty fans, install blanks over empty slots, clear the blockage in the air inlet and outlet, and reduce the temperature of the equipment room.

¡     If the temperature does not reach the threshold, go to the next step.

4.     Export the log and contact H3C Support.

Message text

UID LED state changed

Variable fields

-

Severity level

Informational

Example

2019/03/13 01:28:34 / Informational / OM (bay2) / UID LED Changed

Timestamp: 2019/03/13 01:28:34

Severity level: Informational

Object (slot number): OM module (slot 2)

Event: The UID LED state of the OM module in slot 2 changed.

Explanation

The UID LED state of the OM module in slot 2 changed.

Recommended action

1.     Verify whether the UID LED of the OM module was turned on or off when the log was generated.

¡     If it was turned on or off, no action is required.

¡     If it was not turned on or off, go to the next step.

2.     Verify whether the OM module is being upgraded when the log was generated.

¡     The UID LED of an OM module is in flashing blue when the OM module is being upgraded.

¡     If it was not being upgraded, go to the next step.

3.     Export the log and contact H3C Support.

Message text

ACT LED state changed

Variable fields

-

Severity level

Informational

Example

2019/03/13 02:34:41 / Informational / OM (bay2) / ACT LED Changed

Timestamp: 2019/03/13 02:34:41

Severity level: Informational

Object (slot number): OM module (slot 2)

Event: ACT LED state changed.

Explanation

The ACT LED state of the OM module in slot 2 changed.

Recommended action

Verify whether the OM module was being restarted, inserted, or removed when the log was generated.

·     If it was being restarted, inserted, or removed, no action is required. The OM module is the primary when the LED is in steady green. The OM module is the backup when the LED is off.

·     If it was not being restarted, inserted, or removed, export the log and contact H3C Support.

Message text

HLY LED state changed

Variable fields

-

Severity level

Informational

Example

2019/03/13 00:04:51 / Informational / OM (bay2) / HLY LED Changed

Timestamp: 2019/03/13 00:04:51

Severity level: Informational

Object (slot number): OM module (slot 2)

Event: Health LED state changed.

Explanation

The health LED state of the OM module in slot 2 changed.

Recommended action

Take actions based on the health LED state, which can be one of the following:

·     Off:

¡     If the OM module is not correctly installed, install it.

¡     If the OM module is a backup, no action is required.

·     Steady green—No action is required.

·     Flashing amber—A module in the enclosure has non-critical alarms. Resolve the issues on the OM webpage. If the problem persists, export the log and contact H3C Support.

·     Flashing red—A module in the enclosure has critical alarms. Resolve the issues on the OM webpage. If the problem persists, export the log and contact H3C Support.

Message text

Temperature reached the alarm threshold

Variable fields

-

Severity level

Warning

Example

2019/03/13 09:18:53 / Warning / OM (bay2) / Temperature reached the alarm threshold

Timestamp: 2019/03/13 09:18:53

Severity level: Warning

Object (slot number): OM module (slot 2)

Cause: Temperature reached the alarm threshold

Explanation

The temperature of the OM module in slot 2 reaches the alarm threshold.

Recommended action

Reduce the device temperature by using the following methods:

·     Replace the faulty fan.

·     Install blanks over empty slots.

·     Clear the blockage in the air inlet and outlet.

·     Reduce the temperature of the equipment room.

Monitor the temperature in real time.

Message text

Temperature reached the power-off threshold

Variable fields

N/A

Severity level

Emergency

Example

2019/03/13 03:58:21 / Emergency / OM (bay1) / Temperature reached the power-off threshold

Timestamp: 2019/03/13 03:58:21

Severity level: Emergency

Object (slot number): OM module (slot 1)

Event: Temperature reached the power-off threshold

Explanation

The temperature of the OM module in slot 1 reaches the power-off threshold.

Recommended action

Reduce the device temperature by using the following methods:

·     Replace the faulty fan.

·     Install blanks over empty slots.

·     Clear the blockage in the air inlet and outlet.

·     Reduce the temperature of the equipment room.

Monitor the temperature in real time.

Message text

The backup device took over the primary role

Variable fields

N/A

Severity level

Critical

Example

2019/03/13 10:32:11 / Critical / OM (bay1) / The backup device took over the primary role

Timestamp: 2019/03/13 10:32:11

Severity level: Critical

Object (slot number): OM module (slot 1)

Event: The backup device becomes the primary device.

Explanation

The backup OM module in slot 1 became the primary OM module.

Recommended action

No action is required.

Message text

OM failed to receive fan speed change request from device

Variable fields

N/A

Severity level

Error

Example

2020/01/13 15:33:42 / Error / OM (bay1) / OM failed to receive fan speed change request from device

Timestamp: 2020/01/13 15:33:42

Severity level: Error

Object (slot number): OM module (slot 1)

Event: OM failed to receive fan speed change request

Explanation

The OM failed to receive the fan speed change request.

Recommended action

1.     Verify whether the internal port connecting to the OM module was shut down when the log was generated.

¡     If the port was shut down, bring it up.

¡     If the port was not shut down, go to the next step.

2.     Use the serial port to verify whether the OM module is being restarted.

¡     If it is being restarted, no action is required.

¡     If it is not being restarted, go to the next step.

3.     Export the log and contact H3C Support.

Message text

OM received the full fan speed request from device

Variable fields

N/A

Severity level

Critical

Example

2020/01/13 16:33:42 / Error / OM (bay1) / OM received the full fan speed request from device

Timestamp: 2020/01/13 16:33:42

Severity level: Critical

Object (slot number): OM module (slot 1)

Event: OM received the full fan speed request from device

Explanation

OM received the full fan speed request from the OM module in slot 1.

Recommended action

1.              Verify whether an overtemperature alarm was generated for the OM module when the log was generated.

¡     If an overtemperature alarm was generated, go to the next step.

¡     If no overtemperature alarm was generated, no action is required.

2.     Reduce the device temperature immediately, and monitor the OM module temperature in real time.

Message text

Device recovered and sent fan speed change request to OM

Variable fields

N/A

Severity level

Informational

Example

2020/01/13 16:36:42 / Informational / OM (bay1) / OM received the full fan speed request from device

Timestamp: 2020/01/13 16:36:42

Severity level: Informational

Object (slot number): OM module (slot 1)

Event: Device recovered and sent fan speed change request to OM

Explanation

The OM module in slot 1 recovered and sent fan speed change request to OM.

Recommended action

No action is required.

Message text

Set power option

Variable fields

-

Severity level

Informational

Example

2019/03/15 11:27:04 / Informational / User1 / ICM(bay3) / Set power option / FAILED / No permissions available to perform this operation

Timestamp: 2019/03/15 11:27:04

Severity level: Informational

Username: User1

Object (slot number): interconnect module (slot 3)

Event: Set power option

Result: Failed.

Cause: The user was not authorized to perform this operation.

Explanation

Failed to set power options for the interconnect module in slot 3, because the user was not permitted to perform this operation.

Recommended action

Try again by using an account that is permitted to operate the interconnect module in the slot.

Message text

Set power option

Variable fields

-

Severity level

Informational

Example

2019/03/15 08:03:46 / Informational / admin / ICM(bay3) / Set power option / FAILED / Enclosure Allocation Power Insufficient

Timestamp: 2019/03/15 08:03:46

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Set power option

Result: Failed.

Cause: The enclosure power is insufficient.

Explanation

Failed to set power options for the interconnect module in slot 3, because the enclosure power is insufficient.

Recommended action

1.     Verify whether the total power capacity allocated by the enclosure has reached the limit on the OM webpage.

¡     If the capacity has reached the limit, go to the next step.

¡     If the capacity has not reached the limit, export the log and contact H3C Support.

2.     Verify whether the power modules are running correctly.

¡     If the power modules are running correctly, check the power supply system, and add more power modules. If the problem persists, export the log and contact H3C Support.

¡     If the power modules are not running correctly, locate and restore the faulty power modules on the OM webpage. If the problem persists, export the log and contact H3C Support.

Message text

Reboot device

Variable fields

N/A

Severity level

Informational

Example

2019/03/15 11:27:04 / Informational / User1 / ICM(bay3) / Reboot device / FAILED / No permissions available to perform this operation

Timestamp: 2019/03/15 11:27:04

Severity level: Informational

Username: User1

Object (slot number): interconnect module (slot 3)

Event: Restart device

Result: Failed.

Cause: The user was not authorized to perform this operation.

Explanation

Failed to restart the interconnect module in slot 3, because the user was not permitted to perform this operation.

Recommended action

Try again by using an account that is permitted to operate the interconnect module in the slot.

Message text

Set user-defined name

Variable fields

-

Severity level

Informational

Example

2019/03/15 19:33:59 / Informational / admin / ICM(bay3) / Set user-defined name / SUCCESS

Timestamp: 2019/03/15 19:33:59

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Configure a user-defined name for the interconnect module in slot 3

Result: Succeeded.

Cause: None.

Explanation

Configured a user-defined name for the interconnect module in slot 3 successfully.

Recommended action

No action is required.

Message text

Refresh device information

Variable fields

-

Severity level

Informational

Example

2019/03/15 19:33:59 / Informational / admin / ICM(bay3) / Refresh device information / FAILED / Refresh In Progress

Timestamp: 2019/03/15 19:33:59

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Refresh device information.

Result: Failed.

Cause: A refresh operation is in progress.

Explanation

Failed to refresh the device information about the interconnect module in slot 3, because system refresh is in progress.

Recommended action

Refresh the page after five seconds.

Message text

Refresh UID LED state

Variable fields

-

Severity level

Informational

Example

2019/03/15 19:33:59 / Informational / admin / ICM(bay3) / Refresh UID LED state / FAILED / Refresh In Progress

Timestamp: 2019/03/15 19:33:59

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Refresh UID LED state information.

Result: Failed.

Cause: A refresh operation is in progress.

Explanation

Failed to refresh the UID LED state information about the interconnect module in slot 3, because system refresh is in progress.

Recommended action

Refresh the page after five seconds.

Message text

Refresh temperature sensor information

Variable fields

-

Severity level

Informational

Example

2019/03/15 19:33:59 / Informational / admin / ICM(bay3) / Refresh temperature sensor information / FAILED / Refresh In Progress

Timestamp: 2019/03/15 19:33:59

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Refresh temperature sensor information

Result: Failed.

Cause: A refresh operation is in progress.

Explanation

Failed to refresh the temperature sensor information about the interconnect module in slot 3, because system refresh is in progress.

Recommended action

Refresh the page after five seconds.

Message text

Refresh port mapping information

Variable fields

-

Severity level

Informational

Example

2019/03/15 19:33:59 / Informational / admin / ICM(bay3) / Refresh port mapping information / FAILED / Refresh In Progress

Timestamp: 2019/03/15 19:33:59

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Refresh port mapping information.

Result: Failed.

Cause: A refresh operation is in progress.

Explanation

Failed to refresh the port mapping information about the interconnect module in slot 3, because system refresh is in progress.

Recommended action

Refresh the page after five seconds.

Message text

Refresh internal port mapping information

Variable fields

-

Severity level

Informational

Example

2019/03/15 19:33:59 / Informational / admin / ICM(bay3) / Refresh internal port mapping information / FAILED / Refresh In Progress

Timestamp: 2019/03/15 19:33:59

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Refresh internal port mapping information

Result: Failed.

Cause: A refresh operation is in progress.

Explanation

Failed to refresh the internal port mapping information about the interconnect module in slot 3, because system refresh is in progress.

Recommended action

Refresh the page after five seconds.

Message text

Refresh external port mapping information

Variable fields

-

Severity level

Informational

Example

2019/03/15 19:33:59 / Informational / admin / ICM(bay3) / Refresh external port mapping information / FAILED / Refresh In Progress

Timestamp: 2019/03/15 19:33:59

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Refresh external port mapping information

Result: Failed.

Cause: A refresh operation is in progress.

Explanation

Failed to refresh the external port mapping information about the interconnect module in slot 3, because system refresh is in progress.

Recommended action

Refresh the page after five seconds.

Message text

Refresh IPv4 address of the device

Variable fields

-

Severity level

Informational

Example

2019/03/15 19:33:59 / Informational / admin / ICM(bay3) / Refresh IPv4 address of the device / FAILED / Refresh In Progress

Timestamp: 2019/03/15 19:33:59

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Refresh device IPv4 address information.

Result: Failed.

Cause: A refresh operation is in progress.

Explanation

Failed to refresh the IPv4 address information about the interconnect module in slot 3, because system refresh is in progress.

Recommended action

Refresh the page after five seconds.

Message text

Refresh device state

Variable fields

-

Severity level

Informational

Example

2019/03/15 19:33:59 / Informational / admin / ICM(bay3) / Refresh device state / FAILED / Refresh In Progress

Timestamp: 2019/03/15 19:33:59

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Refresh device state information.

Result: Failed.

Cause: A refresh operation is in progress.

Explanation

Failed to refresh the device state information about the interconnect module in slot 3, because system refresh is in progress.

Recommended action

Refresh the page after five seconds.

Message text

Refresh device diagnostic state

Variable fields

-

Severity level

Informational

Example

2019/03/15 19:33:59 / Informational / admin / ICM(bay3) / Refresh device diagnostic state / FAILED / Refresh In Progress

Timestamp: 2019/03/15 19:33:59

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Refresh device diagnostic state.

Result: Failed.

Cause: A refresh operation is in progress.

Explanation

Failed to refresh the device diagnostic state information about the interconnect module in slot 3, because system refresh is in progress.

Recommended action

Refresh the page after five seconds.

Message text

Upgrade device firmware

Variable fields

-

Severity level

Informational

Example

2019/03/15 19:33:59 / Informational / admin / ICM(bay3) / Upgrade device firmware / SUCCESS

Timestamp: 2019/03/15 19:33:59

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Upgrade interconnect module firmware

Result: Succeeded.

Cause: None.

Explanation

Upgraded the firmware of the interconnect module in slot 3 successfully.

Recommended action

No action is required.

Message text

Refresh state and power information

Variable fields

-

Severity level

Informational

Example

2019/03/15 19:33:59 / Informational / admin / ICM(bay3) / Refresh state and power information / FAILED / Refresh In Progress

Timestamp: 2019/03/15 19:33:59

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Refresh state and power information.

Result: Failed.

Cause: A refresh operation is in progress.

Explanation

Failed to refresh the state and power information about the interconnect module in slot 3, because system refresh is in progress.

Recommended action

Refresh the page after five seconds.

Message text

Set port rate

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Set port rate / FAILED / The target object does not exist

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Set port rate for interconnect module

Result: Failed.

Cause: The interconnect module is absent.

Explanation

Failed to set a port rate for the interconnect module, because the interconnect module is absent.

Recommended action

Verify whether an interconnect module was present in the slot when the log was generated.

·     If an interconnect module was present, reinstall the interconnect module based on the installation guide. If the problem persists, export the log and contact H3C Support.

·     If no interconnect module was present, install an interconnect module and try again.

Message text

Set port rate

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Set port rate / FAILED / Connection Error

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Set port rate for interconnect module

Result: Failed.

Cause: Failed to connect to the interconnect module.

Explanation

Failed to set a port rate for the interconnect module, because the system failed to connect to the interconnect module.

Recommended action

1.     Verify whether the interconnect module is correctly connected.

¡     If it is not correctly connected, go to the next step.

¡     If it is correctly connected, export the log and contact H3C Support.

6.     Verify whether the interface that connects the interconnect module to the OM module is down.

¡     If the interface is down, bring up the interface.

¡     If the interface is up, go to the next step.

7.     Reset the AMC of the interconnect module in the slot on the OM webpage to restore the connection to the interconnect module. If the problem persists, export the log and contact H3C Support.

Message text

Set UID LED

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Set uid led / FAILED / The device was being upgraded

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Set the UID LED state for the interconnect module.

Result: Failed.

Cause: The interconnect module is in upgrade.

Explanation

Failed to set the UID LED state for the interconnect module in slot 3, because the interconnect module is in upgrade.

Recommended action

Try again after the upgrade of the interconnect module completes.

Message text

Set UID LED

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Set uid led / FAILED / The target object does not exist

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Set the UID LED state for the interconnect module.

Result: Failed.

Cause: The interconnect module is absent.

Explanation

Failed to set the UID LED state for the interconnect module in slot 3, because the interconnect module is absent.

Recommended action

Verify whether an interconnect module was present in the slot when the log was generated.

·     If an interconnect module was present, reinstall the interconnect module based on the installation guide. If the problem persists, export the log and contact H3C Support.

·     If no interconnect module was present, install an interconnect module and try again.

Message text

Set UID LED

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Set uid led / FAILED / Cannot perform this operation

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Set the UID LED state for the interconnect module.

Result: Failed.

Cause: The UID LED of the interconnect module is flashing.

Explanation

Failed to set the UID LED state for the interconnect module in slot 3, because the UID LED of the interconnect module is flashing.

Recommended action

1.     Verify whether an SOL connection has been established to the interconnect module.

¡     If an SOL connection has been established, you cannot configure the UID LED when the LED is flashing.

¡     If no SOL connection is established, go to the next step.

8.     Verify whether the interconnect module is in upgrade.

¡     If it is in upgrade, try again after the upgrade completes.

¡     If it is not in upgrade, go to the next step.

9.     Export the log and contact H3C Support.

Message text

Set UID LED

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Set uid led / FAILED / Operation not supported. The device has been powered off

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Set the UID LED state for the interconnect module.

Result: Failed.

Cause: The interconnect module is powered off.

Explanation

Failed to set the UID LED state for the interconnect module in slot 3, because the interconnect module has been powered off.

Recommended action

Verify whether the interconnect module is powered off.

·     If the interconnect module is powered off, power on the interconnect module, and try again.

·     If the interconnect module is not powered off, export the log and contact H3C Support.

Message text

Set UID LED

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Set uid led / FAILED / Connection Error

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Set the UID LED state for the interconnect module.

Result: Failed.

Cause: Failed to connect to the interconnect module.

Explanation

Failed to set the UID LED state for the interconnect module in slot 3, because the system failed to connect to the interconnect module.

Recommended action

1.     Verify whether the interconnect module is correctly connected.

¡     If it is not correctly connected, go to the next step.

¡     If it is correctly connected, export the log and contact H3C Support.

10.     Verify whether the interface that connects the interconnect module to the OM module is down.

¡     If the interface is down, bring up the interface.

¡     If the interface is up, go to the next step.

11.     Reset the AMC of the interconnect module in the slot on the OM webpage to restore the connection to the interconnect module. If the problem persists, export the log and contact H3C Support.

Message text

Reset AMC

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Set uid led / FAILED / The target object does not exist

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Reset interconnect module AMC

Result: Failed.

Cause: The interconnect module is absent.

Explanation

Failed to reset the AMC of the interconnect module, because the interconnect module is absent.

Recommended action

Verify whether an interconnect module was present in the slot when the log was generated.

·     If an interconnect module was present, reinstall the interconnect module based on the installation guide. If the problem persists, export the log and contact H3C Support.

·     If no interconnect module was present, install an interconnect module and try again.

Message text

Reset AMC

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Set uid led / FAILED / AMC is being initialized

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Reset interconnect module AMC

Result: Failed.

Cause: AMC is initializing

Explanation

Failed to reset the AMC of the interconnect module in slot 3, because the AMC of the interconnect module is initializing.

Recommended action

Try again after the AMC initialization is finished.

Message text

Reset AMC

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Set uid led / FAILED / Another user was performing the operation

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Reset interconnect module AMC

Result: Failed.

Cause: Another user is performing operations on the interconnect module.

Explanation

Failed to reset the AMC of the interconnect module, because another user is performing operations on the interconnect module.

Recommended action

Try again after the other users finish configuration. If the problem persists, export the log and contact H3C Support.

Message text

Reset AMC

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Set uid led / FAILED / Connection Error

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Reset interconnect module AMC

Result: Failed.

Cause: Failed to connect to the interconnect module.

Explanation

Failed to reset the AMC of the interconnect module, because the system failed to connect to the interconnect module.

Recommended action

1.     Verify whether the interconnect module is correctly connected.

¡     If it is not correctly connected, go to the next step.

¡     If it is correctly connected, export the log and contact H3C Support.

12.     Verify whether the interface that connects the interconnect module to the OM module is down.

¡     If the interface is down, bring up the interface.

¡     If the interface is up, export the log and contact H3C Support.

Message text

Obtain ICM diagnostic-information logs

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Obtain ICM diagnostic-information logs / FAILED / Operation not supported. The device has been powered off

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Download the diagnostic-information file of the interconnect module.

Result: Failed.

Cause: The interconnect module is powered off. This operation is not supported.

Explanation

Failed to download the diagnostic-information log file of the interconnect module, because the interconnect module is powered off. This operation is not supported.

Recommended action

Power on the interconnect module, and download the diagnostic-information log file again.

Message text

Obtain ICM diagnostic-information logs

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Obtain ICM diagnostic-information logs / FAILED / The target object does not exist

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Download the diagnostic-information file of the interconnect module.

Result: Failed.

Cause: The interconnect module is absent.

Explanation

Failed to download the diagnostic-information log file of the interconnect module, because the interconnect module is absent.

Recommended action

Verify whether an interconnect module was present in the slot when the log was generated.

·     If an interconnect module was present, reinstall the interconnect module based on the installation guide. If the problem persists, export the log and contact H3C Support.

·     If no interconnect module was present, install an interconnect module and try again.

Message text

Obtain ICM diagfile logs

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Obtain ICM diagfile logs / FAILED / Operation not supported. The device has been powered off

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Download the diagfile log file of the interconnect module.

Result: Failed.

Cause: The interconnect module is powered off. This operation is not supported.

Explanation

Failed to download the diagfile log file of the interconnect module, because the interconnect module is powered off. This operation is not supported.

Recommended action

Power on the interconnect module, and download the diagfile log file again.

Message text

Obtain ICM diagfile logs

Variable fields

N/A

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Obtain ICM diagfile logs / FAILED / The target object is in abnormal state

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Download the diagfile log file of the interconnect module.

Result: Failed.

Cause: The interconnect module is abnormal.

Explanation

Failed to download the diagfile log file of the interconnect module, because the interconnect module is abnormal.

Recommended action

1.     Verify whether the interconnect module is correctly connected.

¡     If it is not correctly connected, go to the next step.

¡     If it is correctly connected, export the log and contact H3C Support.

13.     Verify whether the interface that connects the interconnect module to the OM module is down.

¡     If the interface is down, bring up the interface.

¡     If the interface is up, go to the next step.

14.     Reset the AMC of the interconnect module on the OM webpage to restore the connection to the interconnect module. If the problem persists, export the log and contact H3C Support.

Message text

Obtain ICM diagfile logs

Variable fields

N/A

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Obtain ICM diagfile logs / FAILED / The target object does not exist

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Download the diagfile log file of the interconnect module.

Result: Failed.

Cause: The interconnect module is absent.

Explanation

Failed to download the diagfile log file of the interconnect module, because the interconnect module is absent.

Recommended action

Verify whether an interconnect module was present in the slot when the log was generated.

·     If an interconnect module was present, reinstall the interconnect module based on the installation guide. If the problem persists, export the log and contact H3C Support.

·     If no interconnect module was present, install an interconnect module and try again.

Message text

Obtain ICM logfile logs

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Obtain ICM logfile logs / FAILED / Operation not supported. The device has been powered off

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Download the logfile log file of the interconnect module.

Result: Failed.

Cause: The interconnect module is powered off. This operation is not supported.

Explanation

Failed to download the logfile log file of the interconnect module, because the interconnect module is powered off.

Recommended action

Power on the interconnect module, and download the logfile log file again. If the problem persists, export the log and contact H3C Support.

Message text

Obtain ICM logfile logs

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Obtain ICM logfile logs / FAILED / The target object is in abnormal state

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Download the logfile log file of the interconnect module.

Result: Failed.

Cause: The interconnect module is abnormal.

Explanation

Failed to download the logfile log file of the interconnect module, because the interconnect module is abnormal.

Recommended action

1.     Verify whether the interconnect module is correctly connected.

¡     If it is not correctly connected, go to the next step.

¡     If it is correctly connected, export the log and contact H3C Support.

15.     Verify whether the interface that connects the interconnect module to the OM module is down.

¡     If the interface is down, bring up the interface.

¡     If the interface is up, go to the next step.

16.     Reset the AMC of the interconnect module in the slot on the OM webpage to restore the connection to the interconnect module. If the problem persists, export the log and contact H3C Support.

Message text

Obtain ICM logfile logs

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Obtain ICM logfile logs / FAILED / The target object does not exist

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Download the logfile log file of the interconnect module.

Result: Failed.

Cause: The interconnect module is absent.

Explanation

Failed to download the logfile log file of the interconnect module, because The interconnect module is absent.

Recommended action

Verify whether an interconnect module was present in the slot when the log was generated.

·     If an interconnect module was present, reinstall the interconnect module based on the installation guide. If the problem persists, export the log and contact H3C Support.

·     If no interconnect module was present, install an interconnect module and try again.

Message text

Resetting device

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Resetting device / FAILED / The target object is in abnormal state

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Reset SAS switch module

Result: Failed.

Cause: The SAS switch module is abnormal

Explanation

Failed to reset the SAS switch module, because the SAS switch module is abnormal.

Recommended action

1.     Verify whether the SAS switch module is correctly connected.

¡     If it is correctly connected, go to the next step.

¡     If it is not correctly connected, export the log and contact H3C Support.

17.     Verify whether the interface that connects the SAS switch module to the OM module is down.

¡     If the interface is down, bring up the interface.

¡     If the interface is up, go to the next step.

18.     Reset the AMC of the interconnect module on the OM webpage to restore the connection to the interconnect module. If the problem persists, export the log and contact H3C Support.

Message text

SAS switch create supportdump

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) /SAS switch create supportdump / FAILED / The target object is in abnormal state

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: SAS switch module generates supportdump

Result: Failed.

Cause: The interconnect module is abnormal.

Explanation

The SAS switch module failed to generate supportdump, because the interconnect module is abnormal.

Recommended action

1.     Verify whether the SAS switch module is correctly connected.

¡     If it is correctly connected, go to the next step.

¡     If it is not correctly connected, export the log and contact H3C Support.

19.     Verify whether the interface that connects the SAS switch module to the OM module is down.

¡     If the interface is down, bring up the interface.

¡     If the interface is up, go to the next step.

20.     Reset the AMC of the SAS switch module on the OM webpage to restore the connection to the SAS switch module. If the problem persists, export the log and contact H3C Support.

Message text

SAS switch create supportdump

Variable fields

-

Severity level

Warning

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) /SAS switch create supportdump / FAILED / Command execution timed out

Timestamp: 2019/01/28 14:21:29

Severity level: Warning

Username: admin

Object (slot number): interconnect module (slot 3)

Event: SAS switch module generates supportdump

Result: Failed.

Cause: Command execution timed out.

Explanation

The SAS switch module failed to generate supportdump, because command execution timed out.

Recommended action

1.     Verify whether the SAS switch module is correctly connected.

¡     If it is correctly connected, go to the next step.

¡     If it is not correctly connected, export the log and contact H3C Support.

21.     Verify whether the interface that connects the SAS switch module to the OM module is down.

¡     If the interface is down, bring up the interface.

¡     If the interface is up, go to the next step.

22.     Reset the AMC of the SAS switch module on the OM webpage to restore the connection to the SAS switch module. If the problem persists, export the log and contact H3C Support.

Message text

SAS switch create supportdump

Variable fields

-

Severity level

Warning

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) /SAS switch create supportdump / FAILED / Unknown error

Timestamp: 2019/01/28 14:21:29

Severity level: Warning

Username: admin

Object (slot number): interconnect module (slot 3)

Event: SAS switch module generates supportdump

Result: Failed.

Cause: Unknown error.

Explanation

The SAS switch module failed to generate supportdump because of unknown errors.

Recommended action

Export the log and contact H3C Support.

Message text

Configure the SAS switching fabric module as the primary module

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Configure the SAS switching fabric module as the primary module / FAILED / The target object is in abnormal state

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Configure the SAS switch module as the primary module

Result: Failed.

Cause: The interconnect module is abnormal.

Explanation

Failed to configure the SAS switch module as the primary module, because the interconnect module is abnormal.

Recommended action

1.     Verify whether the SAS switch module is correctly connected.

¡     If it is correctly connected, go to the next step.

¡     If it is not correctly connected, export the log and contact H3C Support.

23.     Verify whether the interface that connects the SAS switch module to the OM module is down.

¡     If the interface is down, bring up the interface.

¡     If the interface is up, go to the next step.

24.     Reset the AMC of the SAS switch module on the OM webpage to restore the connection to the SAS switch module. If the problem persists, export the log and contact H3C Support.

Message text

Restore factory defaults of the SAS switching fabric module

Variable fields

-

Severity level

Informational

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Restore factory defaults of the SAS switching fabric module / FAILED / The target object is in abnormal state

Timestamp: 2019/01/28 14:21:29

Severity level: Informational

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Restore the factory defaults of the SAS switching fabric module.

Result: Failed.

Cause: The interconnect module is abnormal.

Explanation

Failed to restore the factory defaults of the SAS switch module, because the interconnect module is abnormal.

Recommended action

1.     Verify whether the SAS switch module is correctly connected.

¡     If it is correctly connected, go to the next step.

¡     If it is not correctly connected, export the log and contact H3C Support.

25.     Verify whether the interface that connects the SAS switch module to the OM module is down.

¡     If the interface is down, bring up the interface.

¡     If the interface is up, go to the next step.

26.     Reset the AMC of the SAS switch module on the OM webpage to restore the connection to the SAS switch module. If the problem persists, export the log and contact H3C Support.

Message text

Refresh state of the SAS switching fabric module

Variable fields

-

Severity level

Warning

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Refresh state of the SAS switching fabric module / FAILED / Unknown error

Timestamp: 2019/01/28 14:21:29

Severity level: Warning

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Refresh SAS switch module state

Result: Failed.

Cause: Unknown error.

Explanation

Failed to refresh the SAS switch module state because of unknown errors.

Recommended action

Export the log and contact H3C Support.

Message text

Refresh state of the SAS switching fabric module

Variable fields

-

Severity level

Warning

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Refresh state of the SAS switching fabric module / FAILED / The target object does not exist

Timestamp: 2019/01/28 14:21:29

Severity level: Warning

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Refresh SAS switch module state

Result: Failed.

Cause: The SAS switch module in slot 3 is absent

Explanation

Failed to refresh the state of the SAS switch module in slot 3, because no SAS switch module is present in the slot.

Recommended action

Verify whether an SAS switch module was present in the slot when the log was generated.

·     If an SAS switch module was present, reinstall the SAS switch module based on the installation guide. If the problem persists, export the log and contact H3C Support.

·     If no SAS switch module was present, insert an SAS switch module and try again.

Message text

Refresh state of the SAS switching fabric module

Variable fields

-

Severity level

Warning

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Refresh state of the SAS switching fabric module / FAILED /The target object is in abnormal state

Timestamp: 2019/01/28 14:21:29

Severity level: Warning

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Refresh SAS switch module state

Result: Failed.

Cause: The SAS switch module in slot 3 is abnormal

Explanation

Failed to refresh the state of the SAS switch module in slot 3, because the SAS switch module is abnormal.

Recommended action

1.     Verify whether the SAS switch module is correctly connected.

¡     If it is correctly connected, go to the next step.

¡     If it is not correctly connected, export the log and contact H3C Support.

27.     Verify whether the interface that connects the SAS switch module to the OM module is down.

¡     If the interface is down, bring up the interface.

¡     If the interface is up, go to the next step.

28.     Reset the AMC of the SAS switch module on the OM webpage to restore the connection to the SAS switch module. If the problem persists, export the log and contact H3C Support.

Message text

Refresh state of the SAS switching fabric module

Variable fields

-

Severity level

Warning

Example

2019/01/28 14:21:29 / Informational / admin / ICM(bay3) / Refresh state of the SAS switching fabric module / FAILED / A refresh task was running

Timestamp: 2019/01/28 14:21:29

Severity level: Warning

Username: admin

Object (slot number): interconnect module (slot 3)

Event: Refresh SAS switch module state

Result: Failed.

Cause: The SAS switch module state is being refreshed.

Explanation

Failed to refresh the state of the SAS switch module in slot 3, because the SAS switch module state is being refreshed.

Recommended action

Try again after five seconds.

Message text

Enable NETCONF service

Variable fields

-

Severity level

Informational