Direct fabric resource manager errors Unable to retrieve the current health status of the drive enclosure Unable to retrieve the current health status of the interconnect An unexpected was encountered updating the current alerts The drive enclosure has been powered off to protect it One or more components in the drive enclosure is reporting a temperature which exceeds the warning threshold An interconnect of type X is expected in Y, interconnect bay Z An interconnect of the proper type is now present. The drive enclosure with serial number X is missing No I/O adapter was found in adapter slot 1 The drive in drive bay X in drive enclosure Y is expected to be a Z drive, but is missing The drive in drive bay X in drive enclosure Y is expected to be of minimum Z The interconnect firmware for the interconnects in logical interconnect X is not at the same version The two I/O adapters in the drive enclosure X have different firmware versions The firmware on the interconnects and/or drive enclosures managed by X does not match the firmware versions specified in the firmware baseline The I/O adapter in slot 1 requires a SAS interconnect in enclosure X, interconnect bay Y The I/O adapter in slot 2 requires a SAS interconnect in enclosure X, interconnect bay Y A mismatch between the logical interconnect configuration and the interconnect configuration has been detected Interconnect configuration has been detected but there is no logical interconnect associated with the interconnect A mismatch between the logical interconnect configuration and the interconnect configuration has been detected A mismatch between the logical interconnect configuration and the interconnect configuration has been detected Interconnect configuration has been detected but there is no logical interconnect associated with the interconnect A mismatch between the logical interconnect configuration and the interconnect configuration has been detected A mismatch between the logical interconnect configuration and the interconnect configuration has been detected Unable to fully discover and configure the interconnect Interconnects in the SAS logical interconnect X are not fully configured The SAS interconnect X is powered off The drive enclosure X is powered off The drive in drive bay X is reporting an unrecognized error reason The drive in drive bay X has an unknown failure Unable to communicate with the drive in drive bay X The drive in drive bay X has failed The drive in drive bay X is not an authentic drive and must be replaced The carrier for the drive in drive bay X has a communication fault A drive failure is imminent for the drive in drive bay X The drive in drive bay X is in an unrecoverable condition The interconnect in bay X is reporting an unrecognized error reason One or more internal switch components are having communication issues The SAS interconnect is experiencing errors when discovering attached devices The claim status of the interconnect indicates that it has been moved to a different enclosure A redundant interconnect is expected but not detected The interconnect is currently configured for dual domain but communication with partner switch has failed The interconnect is currently configured for redundancy but the firmware version is different between the redundant interconnects The interconnect is currently configured for redundancy but the zoning configuration is different between the redundant interconnects The interconnect is currently configured for redundancy but the WWID is different between the redundant interconnects The interconnect is degraded for an unspecified reason The interconnect in bay X has failed The status of the interconnect cannot be determined Port X is reporting an unrecognized error reason Y Link errors have been detected on port X and it is operating in a degraded performance state Port X does not support the device type attached Port X is currently offline The drive enclosure is reporting an unrecognized error reason X Two I/O adapters have been detected but only one functioning communication path can be identified The drive enclosure drawer has been open for an extended duration The drive enclosure is offline There is a communication failure between the drive enclosure and the associated SAS interconnects The drive enclosure is reporting an internal hardware error The I/O adapter in slot X is reporting an unrecognized error reason The status of I/O adapter in slot X cannot be determined because the SAS interconnect topology has errors Communication with I/O adapter in slot X has been lost The I/O adapter in slot X has an unknown failure The I/O adapter in slot X is reporting an internal hardware error An issue with the I/O adapter links in slot X has been detected that prevents assigning drives from the drive enclosure to server profiles Logical JBOD X is reporting an unrecognized error reason The status for logical JBOD X cannot be determined The configuration for logical JBOD X is not consistent with the hardware state The configuration of logical JBOD X cannot be applied to the port since a zoning capable device is attached Logical JBOD X has one or more drive enclosures that are either missing or offline The zoning configuration for X does not reference any ports or bays The SAS interconnect is not present in bay X of enclosure Y The interconnects are missing An I/O adapter in slot X of drive enclosure Y is missing. The dual domain connectivity is lost The drive enclosure X is not part of dual domain configuration of SAS logical interconnect The drive enclosure X is not part of dual domain configuration of SAS logical interconnect The interconnect X is powered off. Dual domain connectivity is lost The interconnect X is powered off. Dual domain connectivity is lost The SAS interconnect(s) in the logical interconnect configuration are powered off. Connectivity to SAS logical JBODs, if exists, will be lost The SAS interconnect(s) in the logical interconnect configuration are powered off. Connectivity to SAS logical JBODs, if exists, will be lost