Direct fabric resource manager errors Unable to retrieve the current health status of the drive enclosure Drive inserted into drive bay Drive removed from drive bay I/O adapter inserted into slot I/O adapter removed from slot 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 The drive enclosure temperature is within operational limits Alerts are now up-to-date Renamed due to SAS logical interconnect group name change An interconnect of type X is expected in Y, interconnect bay Z An interconnect of the proper type is now present An interconnect of type X is expected in enclosure Y The drive enclosure with serial number X is missing The missing drive enclosure has now been replaced All server profiles using this drive enclosure have been deleted The logical JBOD has lost connectivity to drive enclosure The logical JBOD has lost connectivity to drive enclosure No I/O adapter was found in adapter slot 1 An I/O adapter is now present in adapter slot 1 Renamed SAS logical interconnect name The SAS logical interconnect can be made consistent The SAS logical interconnect is consistent The SAS logical interconnect no longer has a missing drive The drive in drive bay X in drive enclosure Y is expected to be a Z drive, but is missing The logical JBOD no longer has a missing drive 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 I/O adapter firmware for the two I/O adapters is not at the same version The interconnect firmware for the interconnects are now at the same version The two I/O adapters are now at the same version The I/O adapter firmware is now at the same version The I/O adapter firmware is at the same version The logical interconnect has been deleted The drive enclosure has been removed The firmware on the interconnects and/or drive enclosures managed by X does not match the firmware versions specified in the firmware baseline The firmware on the interconnects and drive enclosures now match The I/O adapter in slot 1 requires a SAS interconnect in enclosure X The I/O adapter in slot 2 requires a SAS interconnect in enclosure X The I/O adapter now has a SAS interconnect An I/O adapter is not present in slot 2 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 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 Renamed due to enclosure name change Interconnects in the SAS logical interconnect X are not fully configured The SAS interconnect X is powered off The SAS interconnect is now powered on The drive enclosure X is powered off The drive enclosure is now powered on The drive enclosure X is powered off The drive enclosure drawer is open The drive enclosure drawer is closed The drive in drive bay X has failed The drive in drive bay X has failed The drive in drive bay X has failed The drive in drive bay X has an unknown failure The drive in bay X has an unknown failure The drive in bay X has an unknown failure Unable to communicate with the drive in drive bay X Unable to communicate with the drive in bay X Unable to communicate with the drive in bay X The drive in drive bay X is currently zoned The drive in drive bay X is currently in process of an erase operation The drive in drive bay X has completed the erase operation The drive in drive bay X has failed The drive in bay X has failed The drive in drive bay X has failed The drive in drive bay X is not an authentic drive The drive in drive bay X is not an authentic drive The drive in drive bay X is not an authentic drive The carrier for the drive in drive bay X has a communication fault The carrier for the drive in drive bay X has a communication fault The drive in drive bay X is not an authentic drive A drive failure is imminent for the drive in drive bay X A drive failure is imminent for the drive in bay X A drive failure is imminent for the drive in bay X The drive in drive bay X is in an unrecoverable condition. The status is normal 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 The interconnect has not been claimed The interconnect is currently configured for dual domain but is unable to establish communication 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 The interconnect is currently configured for redundancy but the WWID is different The interconnect is degraded for an unspecified reason The status of the interconnect cannot be determined The interconnect subcomponent firmware is inconsistent Port X has normal status I/O Adapter X, Port Y has normal status Link errors have been detected on port X I/O adapter X, link errors have been detected Port X does not support the device type attached I/O Adapter X, Port Y does not support the device type attached Port X is currently offline I/O Adapter X, Port Y is currently offline The drive enclosure is reporting an unrecognized error reason The drive enclosure has normal status Two I/O adapters have been detected but only one functioning communication path can be identified There is a firmware mismatch between the I/O adapters The drive drawer is open 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 problem The firmware image is inconsistent in the I/O adapters The I/O adapter is reporting an unrecognized error reason The I/O adapter in slot X has normal status The status of I/O adapter in slot X cannot be determined 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 Logical JBOD X is reporting an unrecognized error reason Zone group X has normal status 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 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 interconnect of type X is expected in enclosure Y An interconnect of type X is expected in enclosure Y Interconnects of type X are expected in enclosure Y An I/O adapter in slot X of drive enclosure Y is missing An I/O adapter in slot X of drive enclosure Y is missing 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 The interconnect X is powered off The interconnect X is powered off The SAS interconnects in the logical interconnect X are powered off The interconnect X is powered off The interconnect X is powered off The interconnect X is powered off The SAS interconnects in the logical interconnect X are powered off The SAS interconnects in the logical interconnect configuration are powered off The SAS interconnects in the logical interconnect X are powered off The SAS interconnects in the logical interconnect configuration are powered off The SAS interconnects in the logical interconnect X are powered off SAS interconnect is currently not supported for FIPS/CNSA security compliance Drive enclosure is currently not supported for FIPS/CNSA security compliance The interconnect, X, sub-component firmware is inconsistent The interconnects, X and Y, sub-component firmware is inconsistent The interconnect sub-component firmware is now consistent Erase operation started on drive Erase operation completed on drive The erase operation has failed Unable to initiate erase operation One or more logical JBODs may still have dual domain connectivity Unable to communicate with the SAS interconnect One or more logical JBODs may not have been configured for dual domain connectivity Connectivity to SAS interconnect is missing The SAS interconnect X does not support FIPS mode Unable to enable FIPS mode on SAS interconnect. Unable to create logical JBOD Unable to create logical JBOD Unable to create logical JBOD Unable to create logical JBOD Unable to create logical JBOD Unable to create logical JBOD The drive enclosure does not support FIPS mode A mismatch in logical JBOD configuration is detected The logical JBOD is not configured FIPS mode is enabled on SAS interconnect FIPS mode is disabled on SAS interconnect Unable to establish trusted communication with the SAS interconnect Unable to establish trusted communication with the SAS interconnect Unable to establish trusted communication with the SAS interconnect Unable to communicate with the interconnect Unable to establish trusted communication with the SAS interconnect The SAS interconnect now has a valid certificate The certificate on the interconnect has expired The interconnect is currently configured for redundancy The interconnect is currently configured for redundancy Unreferenced logical JBOD configuration is detected. The logical JBOD configuration is different between the redundant interconnects The link rate is less than the maximum capacity of the port The link rate is less than the maximum capacity of the port Interconnect X has the port(s) disabled to device(s) Interconnect X has the port(s) disabled to device(s) Drive enclosure information may not be up-to-date