Failure event | Level | Event display | Troubleshooting |
|---|---|---|---|
The domain ID is not configured or assigned. | Warning | Domain ID is not configured or assigned on a VSAN-number | Check the domain ID setting and set the appropriate ID. |
The principal switch was selected. | Warning | Principal switch is selected on a VSAN-number | Check whether the cable was disconnected and then reconnected. If this operation was not performed, check the SFP, cable, and the connection destination switch. |
A fabric was built or reconfigured. | Warning | Fabric is built or reconfigured on a VSAN-number | Check whether the cable was disconnected and then reconnected. If this operation was not performed, check the SFP, cable, and the connection destination switch. |
The module status has become unknown. The module is likely to be faulty. | Error | Module is unknown state | Replace the possibly faulty module. |
The module was stopped by user operation. | Warning | Module is administratively disabled | Perform a user operation to activate the module. |
The module is active, but is diagnosed to have encountered an error. | Warning | Module is operational but there is some diagnostic information available | Since this error is likely to recur, preventive replacement is recommended. |
The module has entered an error state. | Error | Module has failed due to some condition | Replace the possibly faulty module. |
The installed module was lost. | Error | Module has been provisioned but it is missing | Replace the possibly faulty module unless this status was encountered during operation. |
An incompatible module is installed. | Error | Module has not been provisioned and wrong type of module is plugged in | Verify that the components are installed at correct locations. |
The module is incompatible with the current configuration. | Error | Module is not compatible with the current configuration | Set up a configuration that is suitable for the installed module. |
A module diagnostic test encountered an error caused by hardware failure. | Error | Module diagnostic test failed due to some hardware failure | Replace the possibly faulty module. |
The module is still not ready. | Error | Module is waiting for an external or internal event to become operational | Contact the support service if the possibly faulty location cannot be identified using device error logs or other information. |
The module is inactive although it is switched on. | Error | Module is administratively set to be powered on but out of service | Check the module status or configuration. If no abnormality is found, contact the support service. |
The module is inactive due to a temperature abnormality although it is switched on. | Error | Module is powered on but out of service by environmental temperature problem | Check the fan status. If no problem is found, check the installation environment. |
The power was cut off. | Error | Module is in powered down state | If the power was not intentionally turned off, replace the possibly faulty module. |
The system power is not sufficient for the module. | Error | System does not have enough power in power budget to power on this module | Check the power environment. If no problem is found, contact the support service. |
The module is being rebooted. | Error | Module is being power cycled | If the module is not intentionally being rebooted, contact the support service. |
The module is active, but is likely to enter an error state. | Error | Module is still operational but may go into a failure state | Contact the support service if the possibly faulty location cannot be identified using device error logs or other information. |
The module is active, but is likely to encounter system failure. | Error | Module is still operational but could potentially take the system down | Contact the support service if the possibly faulty location cannot be identified using device error logs or other information. |
The power to the FRU was cut off for an unknown reason. | Error | FRU is powered off because of unknown problem | Replace the possibly faulty module. |
The power to the FRU was cut off. | Warning | FRU is administratively powered off | To maintain redundancy, perform user operation to turn on the power to the module. |
The power to the FRU was turned off because of insufficient system power. | Warning | FRU is powered off because available system power is insufficient | Check the power environment. If no problem is found, contact the support service. |
The power to the FRU was cut off because of a power problem within the FRU. | Error | FRU is powered off because of power problem in the FRU | Check the power status. If no problem is found, check the installation environment. |
The power to the FRU was cut off due to a temperature problem. | Error | FRU is powered off because of temperature problem | Check the power status. If no problem is found, check the installation environment. |
The power to the FRU was cut off due to a fan problem. | Error | FRU is powered off because of fan problems | Check the fan status. If no problem is found, check the installation environment. |
The status of the FRU has changed to error. | Error | FRU is in failed state | Replace the possibly faulty module. |
The power is normal, but the power supply fan is faulty. | Error | FRU is on but fan has failed | Replace the pertinent power supply. |
The status of the fan has changed to unknown. | Error | FAN is unknown state | Contact the support service. |
The power to the fan was cut off. | Error | FAN is powered down | Verify that the fan is correctly inserted. If the problem remains, contact the support service. |
The fan has become faulty. | Warning | FAN is partial failure | Replace the fan. |
The sensor threshold has been exceeded. | Information | The sensor value(%VALUE%) crossed the threshold(%VALUE%) | If this event recurs frequently, contact the support service. |
A software crash occurred and the core file was generated. | Information | Software crash occurs and a core file is generated. | Replace the supervisor or device. |
The trunking port has failed. | Warning | Trunking port is down(%CAUSE%) | Check whether the cable was disconnected and then reconnected. If this operation was not performed, check the SFP, cable, and the connection destination switch. The "The status of the port has changed" event occurs at the same time as this event. |
The status of the Fibre Channel port has changed to normal. | Information | The status of the port has changed to Ready/%STATUS% fc%SLOT NUMBER%/%PORT NUMBER INSIDE THE SLOT%(%PORT NUMBER%) *1 | No action is required. |
The status of the Fibre Channel port has changed to warning. | Warning | The status of the port has changed to Warning/%STATUS% fc%SLOT NUMBER%/%PORT NUMBER INSIDE THE SLOT%(%PORT NUMBER%) *1 | Check whether the cable was disconnected and then reconnected. If this operation was not performed, check the SFP, cable, and the connection destination device. |
The status of the Fibre Channel port has changed to unknown. | Warning *2 | The status of the port has changed to Unknown/%STATUS% fc%SLOT NUMBER%/%PORT NUMBER INSIDE THE SLOT%(%PORT NUMBER%) *1 | Check whether the cable was disconnected and then reconnected. If this operation was not performed, check the SFP, cable, and the connection destination device. |
The status of the Fibre Channel port has changed to error. | Error | The status of the port has changed to FAILURE/%STATUS% fc%SLOT NUMBER%/%PORT NUMBER INSIDE THE SLOT%(%PORT NUMBER%) *1 | Check whether the cable was disconnected and then reconnected. If this operation was not performed, check the SFP, cable, and the connection destination device. |
*1: Any of the following words is inserted in %STATUS%.
Unknown, Online, Offline, Bypassed, Diagnostics
*2: When "The status of the port has changed to Unknown/Offline" is displayed, it is notified as Information level.
