The primary node has detected that the state of another node has changed to being failed. The reason for the failure may be one of the following: "OverHeat" Fan failure, component failure, or an external heat condition has caused the temperature of the module to exceed its operating limit. "Process Failure" The node can not continue to function due the abnormal termination of an an essential software module due to corruption or inconsistency. "Hw Failure" An essential hardware component on the module has failed. "Slot unsecured" The module present in the slot is not safely locked in the chassis. "Dual Master" More than one node is claiming to be the master (primary). This may be caused by a communication failure betweeen the nodes. "Backup lost" The master (primary) node has lost communication with the backup node and so it has forced the backup node into failed state. "No Master" A standby node has lost communication with the master (primary) node and no backup node is available or taken over the role of master node. "License Mismatch" The license installed on the node is not as capable as the license that is installed on the master (primary) node. "Not In Sync" The master (primary) node has failed or otherwise the backup node has lost communication with it before the backup had synchronized with the primary, and consequently the backup can not become primary. "Incompatible XOS" The version of EXOS running on the failed node is not compatible with the version running on the master (primary) node. "Card Mismatch" The module type present in the slot does not match the configured type for that slot. "Device Timeout" The module present in the slot is not responding to informational queries within the expected time period. "Node Not Yet UP" The node has not yet assumed the role of a standby node when the master (primary) is ready to proceed with module initialization.
Possible resolutions to the problem depend on the exact reason for the failure; and the approach should be to alleviate the cause as described.
Critical
%SlotName% has failed for the reason of \"%ReasonStr%\".
| Name | Type |
|---|---|
| SlotName | String |
| ReasonStr | String |
Print
this page
Email this topic
Feedback
View PDF
Download EPUB