Owners Manual

Table 27. Event descriptions and recommended actions (continued)
Number Severity Description/Recommended actions
● No action is required.
602 Error, Warning An alert condition was detected on a Midplane Interconnect element.
The Midplane Interconnect element reports status associated with the interface between the
SBB I/O module and the midplane. This is typically some form of communication problem on the
midplane interconnect.
Recommended actions:
● Contact technical support. Provide logs to technical support personnel for analysis.
● When the problem is resolved, an event with the same code will be logged with Resolved
severity.
Resolved A previous Warning or Error condition for the Midplane Interconnect element has been resolved.
The Midplane Interconnect element reports status associated with the interface between the
SBB I/O module and the midplane.
Recommended actions:
● No action is required.
603 Error, Warning An alert condition for a SAS Connector element has been detected.
The SAS Connector element report status information for both external and internal SAS port
connectors.
Recommended actions:
● Contact technical support.
● When the problem is resolved, an event with the same code will be logged with Resolved
severity.
Info., Resolved An alert condition for a SAS Connector element has been detected.
The SAS Connector element report status information for both external and internal SAS port
connectors.
Recommended actions:
● No action is required.
604 Warning A replication snapshot was attempted and failed.
A replication-set has been configured to retain snapshots of the volume. An error is possible if
the snapshot fails.
Recommended actions:
● Monitor the health of the local system, the replication-set, the volume, and the peer-
connection. A full storage pool may be the cause of this fault.
○ Check the peer-connection system health and state.
○ Ensure that the Maximum Licensable Snapshots limit (shown by the CLI show license
command) was not exceeded.
605 Warning Inactive processing core.
The controller module has multiple processing cores. The system has enough active cores to
operate but performance is degraded.
Recommended actions:
● Attempt to restart all the processing cores as follows:
○ Shut down the controller module that logged this event.
○ Remove the controller module, wait 30 seconds, and then reinsert the controller module.
● If this event is logged again, contact technical support.
146 Events and event messages