HP MSA Event Descriptions Reference Guide Abstract This guide is for reference by storage administrators to help troubleshoot storage-system issues. It describes event messages that may be reported during system operation and specifies any actions recommended in response to an event.
© Copyright 2014 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents Event descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting steps for leftover disk drives . . . . . . . . . . . . . . . . . . . .
Contents
1 Event descriptions Introduction This guide is for reference by storage administrators to help troubleshoot storage-system issues. It describes event messages that may be reported during system operation and specifies any actions recommended in response to an event. This guide applies to MSA 1040 and 2040 storage systems, and to MSA P2000 G3 and MSA 2000 storage systems that have been updated to the most recent firmware available. It describes all event codes that exist as of publication.
Event descriptions 1 Warning If the indicated vdisk is RAID 6, it is operating with degraded health due to the failure of two disks. If the indicated vdisk is not RAID 6, it is operating with degraded health due to the failure of one disk. The vdisk is online but cannot tolerate another disk failure. If a dedicated spare or global spare of the proper type and size is present, that spare is used to automatically reconstruct the vdisk; events 9 and 37 are logged to indicate this.
6 Warning A failure occurred during initialization of the indicated vdisk. This was probably caused by the failure of a disk drive. The initialization may have completed but the vdisk probably has a status of FTDN (fault tolerant with a down disk), CRIT (critical), or OFFL (offline), depending on the RAID level and the number of disks that failed. Recommended actions • Look for another event logged at approximately the same time that indicates a disk failure, such as event 55, 58, or 412.
• If the associated vdisk is offline and you do not want to use the trust command, perform these steps: • Delete the vdisk (delete vdisks CLI command). • Clear the indicated disk’s metadata so the disk can be re-used (clear disk-metadata CLI command). • Replace the failed disk or disks. (Look for other instances of event 8 in the event log to determine which disks failed.) • Re-create the vdisk (create vdisk CLI command).
21 Error Vdisk verification completed. Errors were found but not corrected. Recommended actions • Perform a vdisk scrub to find and correct the errors. Warning Vdisk verification did not complete because of an internally detected condition such as a failed disk. If a disk fails, data may be at risk. Recommended actions • Resolve any non-disk hardware problems, such as a cooling problem or a faulty controller module, expansion module, or power supply.
32 Info. Vdisk verification has started. Recommended actions • No action is required. 33 Info. Controller time/date has been changed. This event is logged before the change happens, so the timestamp of the event shows the old time. This event may occur often if NTP is enabled Recommended actions • No action is required. 34 Info. The controller configuration has been restored to factory defaults. Recommended actions • For an FC controller, restart it to make the default loop ID take effect. 37 Info.
40 Error The sensors monitored a temperature or voltage in the failure range. When the problem is resolved, event 47 is logged for the component that logged event 40. Recommended actions • Check that the storage system’s fans are running. • Check that the ambient temperature is not too warm. The enclosure operating range is 5–40 C (41 F–104 F). • Check for any obstructions to the airflow. • Check that there is a module or blank plate in every module slot in the enclosure.
50 Error A correctable ECC error occurred in cache memory more than 10 times during a 24-hour period, indicating a probable hardware fault. Recommended actions • Replace the controller module that logged this event. Warning A correctable ECC error occurred in cache memory. This event is logged with Warning severity to provide information that may be useful to technical support, but no action is required now. It will be logged with Error severity if it is necessary to replace the controller module.
55 Warning The indicated disk reported a SMART event. A SMART event indicates impending disk failure. Recommended actions • Resolve any non-disk hardware problems, especially a cooling problem or a faulty power supply. • If the disk is in a vdisk that uses a non-fault-tolerant RAID level (RAID 0 or non-RAID), copy the data to a different vdisk and replace the faulty disk. • If the disk is in a vdisk that uses a fault-tolerant RAID level, replace the faulty disk.
61 Error The controller reset a disk channel to recover from a communication error. This event is logged to identify an error trend over time. Recommended actions • If the controller recovers, no action is required. • View other logged events to determine other action to take. 62 Warning The indicated global or dedicated spare disk has failed. Recommended actions • Replace the disk with one of the same type (SAS SSD, enterprise SAS, or midline SAS) and the same or greater capacity.
74 Info. The FC loop ID for the indicated vdisk was changed to be consistent with the IDs of other vdisks. This can occur when disks that constitute a vdisk are inserted from an enclosure having a different FC loop ID. This event is also logged by the new owning controller after vdisk ownership is changed. Recommended actions • No action is required. 75 Info. The indicated volume’s LUN (logical unit number) has been unassigned because it conflicts with LUNs assigned to other volumes.
80 Info. The controller enabled or disabled the indicated parameters for one or more disks. Recommended actions • No action is required. 81 Info. The current controller has unkilled the partner controller. The other controller will restart. Recommended actions • No action is required. 83 Info. The partner controller is changing state (shutting down or restarting). Recommended actions • No action is required.
90 Info. The partner controller does not have a mirrored configuration image for the current controller, so the current controller's local flash configuration is being used. This event is expected if the other controller is new or its configuration has been changed. Recommended actions • No action is required. 91 Error In a testing environment, the diagnostic that checks hardware reset signals between controllers in Active-Active mode failed. Recommended actions • Perform failure analysis.
107 Error A serious error has been detected by the controller. In a single-controller configuration, the controller will restart automatically. In an Active-Active configuration, the partner controller will kill the controller that experienced the error. Recommended actions • See “Resources for diagnosing and resolving problems” (page 5). 108 Info. The indicated volume has been deleted from the indicated vdisk. Recommended actions • No action is required. 109 Info.
116 Error After a recovery, the partner controller was killed while mirroring write-back cache data to the controller that logged this event. The controller that logged this event restarted to avoid losing the data in the partner controller’s cache, but if the other controller does not restart successfully, the data will be lost.
141 Info. This event is logged when the IP address used for management of the system has been changed by a user or by a DHCP server (if DHCP is enabled). This event is also logged during power up or failover recovery, even when the address has not changed. Recommended actions • No action is required. 152 Warning The Management Controller (MC) has not communicated with the Storage Controller (SC) for 15 minutes and may have failed. This event is initially logged as Informational severity.
155 Info. New loader firmware has been loaded in the Management Controller (MC). Recommended actions • No action is required. 156 Warning The Management Controller (MC) has been restarted from the Storage Controller (SC) for the purpose of error recovery. Recommended actions • See the recommended actions for event 152, which is logged at approximately the same time. Info.
162 Warning The host WWNs (node and port) previously presented by this controller module are unknown. In a dual-controller system this event has two possible causes: • One or both controller modules have been replaced or moved while the system was powered off. • One or both controller modules have had their flash configuration cleared (this is where the previously used WWNs are stored). The controller module recovers from this situation by generating a WWN based on its own serial number.
168 Error The indicated SES alert condition was detected in the indicated enclosure. This event is logged as Error severity when one of the power supplies in an enclosure has no power supplied to it or when a hardware failure is detected. Recommended actions • Check that all modules in the enclosure are fully seated in their slots and that their latches are locked.
170 Info. The last rescan detected that the indicated enclosure was added to the system. Recommended actions • No action is required. 171 Info. The last rescan detected that the indicated enclosure was removed from the system. Recommended actions • No action is required. 172 Error The indicated vdisk has been quarantined because not all of its disks are accessible. While the vdisk is quarantined, any attempt to access the volumes in the vdisk from a host will fail.
173 Info. The indicated vdisk has been removed from quarantine. Recommended actions • No action is required. 174 Info. Enclosure or disk firmware update has succeeded, been aborted by a user, or failed. If the firmware update fails, the user will be notified about the problem immediately and should take care of the problem at that time, so even when there is a failure, this event is logged as Informational severity. Recommended actions • No action is required. 175 Info.
182 Info. All disk channels have been paused. I/O will not be performed on the disks until all channels are unpaused. Recommended actions • If this event occurs in relation to disk firmware update, no action is required. When the condition is cleared, event 183 is logged. • If this event occurs and you are not performing disk firmware update, see “Resources for diagnosing and resolving problems” (page 5). 183 Info. All disk channels have been unpaused, meaning that I/O can resume.
190 Info. The controller module's supercapacitor pack has started charging. This change met a condition to trigger the auto-write-through feature, which has disabled write-back cache and put the system in write-through mode. When the fault is resolved, event 191 is logged to indicate that write-back mode has been restored. Recommended actions • If event 191 is not logged within 5 minutes after this event, the supercapacitor has probably failed and the controller module should be replaced. 191 Info.
198 Info. A power supply has failed. This indicates that a trigger condition has occurred that has caused the auto-write-through feature to disable write-back cache and put the system in write-through mode. When the fault is resolved, event 199 is logged to indicate that write-back mode has been restored. Recommended actions • If event 199 has not been logged since this event was logged, the power supply probably does not have a health of OK and the cause should be investigated.
204 Error An error occurred with either the CompactFlash card (NV device) or the transport mechanism. The system may attempt to recover itself. The CompactFlash card is used for backing up unwritten cache data when a controller goes down unexpectedly, such as when a power failure occurs. This event is generated when the Storage Controller (SC) detects a problem with the CompactFlash as it is booting up. Recommended actions • Restart the Storage Controller that logged this event.
207 Error Vdisk scrub completed and found an excessive number of errors in the indicated vdisk. This event is logged as Error severity when more than 100 parity or mirror mismatches are found and corrected during a scrub or when 1 to 99 parity or mirror mismatches are found and corrected during each of 10 separate scrubs of the same vdisk. For non-fault-tolerant RAID levels (RAID 0 and non-RAID), media errors may indicate loss of data.
209 Error A scrub-disk job logged with event 208 has completed and found one or more media errors, SMART events, or hard (non-media) errors. If this disk is used in a non-fault-tolerant vdisk, data may have been lost. Recommended actions • Replace the disk with one of the same type (SAS SSD, enterprise SAS, or midline SAS) and the same or greater capacity. For continued optimum I/O performance, the replacement disk should have performance that is the same as or better than the one it is replacing.
213 Info. The indicated standard volume has been converted to a master volume, or the indicated master volume has been converted to a standard volume. Recommended actions • No action is required. 214 Info. The creation of snapshots is complete. The number of snapshots is indicated. Additional events give more information for each snapshot. Recommended actions • No action is required. 215 Info. A previously created batch of snapshots is now committed and ready for use.
222 Info. The policy for the snap pool has been changed by a user. A policy specifies the action for the system to automatically take when the snap pool reaches the associated threshold level. Recommended actions • No action is required. 223 Info. The threshold level for the snap pool has been changed by a user. Each snap pool has three threshold levels that notify you when the snap pool is reaching decreasing capacity.
229 Warning The indicated snap pool has reached its warning threshold. Recommended actions • You can expand the snap pool or delete snapshots. 230 Warning The indicated snap pool has reached its error threshold. When the error threshold is reached, the system automatically takes the action set in the policy for this threshold level. The default policy for the error threshold is to auto-expand the snap pool. Recommended actions • You can expand the snap pool or delete snapshots.
236 Error A special shutdown operation has started. These special shutdown types indicate an incompatible feature. Recommended actions • Replace the indicated controller module with one that supports the indicated feature. Info. A special shutdown operation has started. These special shutdown types are used as part of the firmware-update process. Recommended actions • No action is required. 237 Info. A firmware update has started and is in progress.
243 Info. A new controller enclosure has been detected. This happens when a controller module is moved from one enclosure to another and the controller detects that the midplane WWN is different from the WWN it has in its local flash. Recommended actions • No action is required. 245 Info. An existing disk channel target device is not responding to SCSI discovery commands. Recommended actions • Check the indicated target device for bad hardware or bad cable, then initiate a rescan.
251 Info. A volume-copy operation has started for the indicated source volume. If the source volume is a master volume, you can remount it. If the source volume is a snapshot, do not remount it until the copy is complete (as indicated by event 268). Recommended actions • No action is required. 252 Info. Data written to the indicated snapshot after it was created has been deleted. The snapshot now represents the state of the master volume when the snapshot was created.
259 Info. In-band CAPI commands have been disabled. Recommended actions • No action is required. 260 Info. In-band CAPI commands have been enabled. Recommended actions • No action is required. 261 Info. In-band SES commands have been disabled. Recommended actions • No action is required. 262 Info. In-band SES commands have been enabled. Recommended actions • No action is required. 263 Warning The indicated spare disk is missing. Either it was removed or it is not responding.
269 Info. A partner firmware update operation has started. This operation is used to copy firmware from one controller to the other to bring both controllers up to the same version of firmware. Recommended actions • No action is required. 270 Warning Either there was a problem reading or writing the persistent IP data from the FRU ID SEEPROM, or invalid data were read from the FRU ID SEEPROM.
274 Warning The indicated PHY has been disabled, either automatically or by a user. Drive PHYs are automatically disabled for empty disk slots or if a problem is detected. The following reasons indicate a likely hardware fault: • Disabled because of error count interrupts • Disabled because of excessive PHY change counts • PHY is ready but did not pass COMINIT Recommended actions • If none of the reasons listed above, no action is required.
298 Warning The controller's real-time clock (RTC) setting is invalid. This event will most commonly occur after a power loss if the real-time clock battery has failed. The time may have been set to a time that is up to 5 minutes before the power loss occurred, or it may have been reset to 1980-01-01 00:00:00. Recommended actions • Check the system date and time. If either is incorrect, set them to the correct date and time. • Also look for event 246 and follow the recommended action for that event.
305 Info. A serial number in Storage Controller (SC) flash memory was found to be invalid when compared to the serial number in the controller-module or midplane FRU ID SEEPROM. The valid serial number has been recovered automatically. Recommended actions • No action is required. 306 Info. The controller-module serial number in Storage Controller (SC) flash memory was found to be invalid when compared to the serial number in the controller-module FRU ID SEEPROM.
312 Info. This event is used by email messages and SNMP traps when testing notification settings. This event is not recorded in the event log. Recommended actions • No action is required. 313 Error The indicated controller module has failed. This event can be ignored for a single-controller configuration. Recommended actions • It this is a dual-controller system, replace the failed controller module. The module’s Fault/Service Required LED will be illuminated (not blinking).
319 Warning The indicated available disk has failed. Recommended actions • Replace the disk with one of the same type (SAS SSD, enterprise SAS, or midline SAS) and the same or greater capacity. For continued optimum I/O performance, the replacement disk should have performance that is the same as or better than the one it is replacing. 322 Warning The controller has an older Storage Controller (SC) version than the version used to create the CHAP authentication database in the controller’s flash memory.
356 Warning This event can only result from tests that are run in the manufacturing environment. Recommended actions • Follow the manufacturing process. 357 Warning This event can only result from tests that are run in the manufacturing environment. Recommended actions • Follow the manufacturing process. 358 Critical All PHYs are down for the indicated disk channel. The system is degraded and is not fault tolerant because all disks are in a single-ported state.
362 Critical, The scheduler experienced a problem with the indicated task. Error, or Recommended actions Warning • Take appropriate action based on the indicated problem. Info. The scheduler experienced a problem with the indicated task. Recommended actions • No action is required. 363 Error When the Management Controller (MC) is restarted, firmware versions that are currently installed are compared against those in the bundle that was most recently installed.
401 Warning The indicated log has filled to a level at which diagnostic data will be lost if not transferred to a log-collection system. Recommended actions • Transfer the log file to the log-collection system. 402 Error The indicated log has wrapped and has started to overwrite its oldest diagnostic data. Recommended actions • Investigate why the log-collection system is not transferring the logs before they are overwritten.
416 Error Failed to delete the indicated replication set. This can occur if an invalid identifier was specified for the replication set, or if the specified primary volume is not in the local system. Recommended actions • Repeat the deletion using a valid replication-set identifier, or on the local system for the primary volume. 417 Info.
421 Info. Completed adding the indicated secondary volume to the indicated replication set. Recommended actions • No action is required. 422 Info. Completed removing the indicated secondary volume from the indicated replication set. Recommended actions • No action is required. 423 Error Failed to remove the indicated volume from the indicated replication set. This can occur for several reasons, such as: • The volume record is not found. • The volume record is not yet available.
429 Info. A user resumed a replication to the indicated secondary volume. Recommended actions • No action is required. 430 Info. A user aborted a replication to the indicated secondary volume. Recommended actions • No action is required. 431 Error Replication to the indicated volume has been suspended due to an error detected during the replication process. User intervention is required to resume replication. This can occur for several reasons, such as: • The cache request was aborted.
435 Warning Failed to initialize the indicated replication set. This can occur because: • Firmware in the remote system is incompatible with firmware in the local system. • The primary volume and secondary volume involved in replication cannot communicate. Recommended actions • Update the firmware on one or both systems so they are running the same version. • Check your network or fabric for abnormally high congestion or connectivity issues.
440 Warning Retrying a replication due to an error in the indicated secondary volume. This can occur for several reasons, such as: • The cache request was aborted. • The cache detected that the source or target volume is offline. • The cache detected a media error. • The snap pool is full. • The communication link is busy or experienced an error. • The snapshot being used for the replication is invalid. • There was a problem establishing proxy communication.
449 Info. Roll back was aborted for the indicated master volume. This can occur if a roll back is in progress and a user selects to roll back a different volume, which will abort the first roll back and start a new roll back. A user can't explicitly abort a roll back because that would corrupt the master volume. Recommended actions • No action is required. 450 Warning A remote volume’s status changed from online to offline.
456 Warning The system's IQN was generated from the default OUI because the controllers could not read the OUI from the midplane FRU ID data during startup. If the IQN is wrong for the system's branding, iSCSI hosts might be unable to access the system. Recommended actions • If event 270 with status code 0 is logged at approximately the same time, restart the Storage Controllers. 464 Warning A user inserted an unsupported cable or SFP into the indicated controller host port.
472 Error A replication failed to start on the indicated secondary volume. This can occur when the secondary system is not licensed for replication (for example, a temporary license expired). Recommended actions • To perform replication, ensure that the secondary system has a valid replication license. 475 Info. A replication was queued because the indicated secondary volume is offline. Recommended actions • No action is required.
479 Error The controller reporting this event was unable to flush data to or restore data from non-volatile memory. This mostly likely indicates a CompactFlash failure, but it could be caused by some other problem with the controller module. The Storage Controller that logged this event will be killed by its partner controller, which will use its own copy of the data to perform the flush or restore operation.
484 Warning No compatible spares are available to reconstruct this vdisk if it experiences a disk failure. Only vdisks that have dedicated spares will start reconstruction automatically. This situation puts data at increased risk because it will require user action to configure a disk as a dedicated or global spare before reconstruction can begin on the indicated vdisk if a disk in that vdisk fails in the future.
486 Warning A recovery process was initiated to prevent writing invalid data that may exist in the controller that logged this event. The controller that logged this event has detected (via information saved in the vdisk metadata) that it may contain outdated data that should not be written to the vdisks. The controller will log this event, restart the partner controller, wait 10 seconds, then kill itself. The partner controller will then unkill this controller and mirror the correct cache data to it.
• If that does not resolve the problem, the fault is probably in the enclosure midplane. Replace the chassis-and-midplane FRU of the most-upstream enclosure with reported failures. If that does not resolve the problem and there is more than one enclosure with reported failures, replace the chassis-and-midplane FRU of the other enclosures with reported failures until the problem is resolved. 496 Warning An unsupported disk type was found. Recommended actions • Replace the disk with a supported type.
499 Info. A disk copyback operation started. The indicated disk is the destination disk. When a disk fails, reconstruction is performed using a spare disk. When the failed disk is replaced, the data that was reconstructed in the spare disk (and any new data that was written to it) is copied to the disk in the slot where the data was originally located. This is known as slot affinity.
507 Info. The link speed of the indicated disk does not match the link speed that the enclosure is capable of. This event is logged when the auto-negotiated link speed is less than the maximum speed that the enclosure supports. The disk is functional, but I/O performance is reduced. This event may be logged for one disk channel or for both disk channels. Recommended actions • If the disk is a member of a non-fault-tolerant vdisk (RAID 0 or non-RAID), move the data to a different vdisk.
515 Info An FDE disk was repurposed by a user. The disk was reset to its original factory state. Recommended actions • No action is required. 516 Error An FDE disk has been placed in the unavailable state. The related event message 518, which indicates that a disk operation failed, may provide additional information. Recommended actions • See the recommended action specified in the event message. 517 Info A disk that was formerly in the FDE unavailable state is no longer unavailable.
524 Error A temperature or voltage sensor reached a critical threshold. A sensor monitored a temperature or voltage in the critical range. When the problem is resolved, event 47 is logged for the component that logged event 524. If the event refers to a disk sensor, disk behavior may be unpredictable in this temperature range. Check the event log to determine if more than one disk has reported this event. • If multiple disks report this condition there could be a problem in the environment.
530 Error The local Expander Controller (EC) firmware detected a level of incompatibility with the partner Expander Controller (EC) . This incompatibility could be due to unsupported hardware or firmware. As a preventative measure, the local Expander Controller (EC) is holding the partner Expander Controller (EC) in a reset loop. Recommended actions • Remove the partner controller module from the enclosure.
548 Warning Vdisk reconstruction failed. When a disk fails, reconstruction is performed using a spare disk. However, this operation failed. This event can be logged for two reasons: • Some of the data in the other disk(s) in the vdisk is unreadable (uncorrectable media error), so part of the data cannot be reconstructed. • The disk that was used as a replacement for the failed disk is also faulty. This failure may also be caused by a fault in the midplane of the enclosure that the disks are inserted into.
Troubleshooting steps for leftover disk drives HP MSA 1040 and 2040 arrays use metadata on hard drives to identify vdisk members and identify other disk members of the vdisk. Hard drives enter a Leftover state for several reasons: • Drive spin up was not completed before a controller polled the drive. When the controller queries the drive and finds the drive is not in a ready state, the controller may place the drive into a Leftover state. • Improper power-on sequences.
Power supply faults and recommended actions Table 1 Power supply faults and recommended actions Fault Recommended action Power supply fan warning or failure, or power supply warning or failure. Event code 168. • Check that all of the fans are working using the SMU. • Make sure that no slots are left open for more than two minutes. If you need to replace a module, leave the old module in place until you have the replacement, or use a blank cover to close the slot.
Event descriptions
2 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
Table 3 Document conventions (continued) Convention Element Monospace text • • • • File and directory names System output Code Commands, their arguments, and argument values Monospace, italic text • • Code variables Command variables Monospace, bold text Emphasized monospace text Indicates that failure to follow directions could result in bodily harm or death. WARNING! CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.
3 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
Documentation feedback
Glossary 2U12 A enclosure that is two rack units in height and can contain 12 disks. 2U24 A enclosure that is two rack units in height and can contain 24 disks. Additional Sense See ASC/ASCQ. Code/Additional Sense Code Qualifier Advanced Encryption Standard See AES. AES Advanced Encryption Standard. A specification for the encryption of data using a symmetric-key algorithm. Air Management Sled See AMS. ALUA Asymmetric Logical Unit Access. AMS For a 2U12 or 2U24 enclosure, Air Management Sled.
complex programmable logic device See CPLD. Configuration See CAPI. Application Programming Interface controller A (or B) A short way of referring to controller module A (or B). controller enclosure An enclosure that contains one or two controller modules.
DSD Drive spin down. A power-saving feature that monitors disk activity in the storage system and spins down inactive disks based on user-selectable policies. dual-port disk A disk that is connected to both controllers so it has two data paths, achieving fault tolerance. Dynamic Host See DHCP. Configuration Protocol dynamic spare An available compatible disk that is automatically assigned, if the dynamic spares option is enabled, to replace a failed disk in a vdisk with a fault-tolerant RAID level.
host An external port that the storage system is attached to. The external port may be a port in an I/O adapter in a server, or a port in a network switch. Product interfaces use the terms host and initiator interchangeably. host port A port on a controller module that interfaces to a host computer, either directly or through a network switch. host bus adapter See HBA. image ID A globally unique serial number that identifies the point-in-time image source for a volume.
masking A volume-mapping setting that specifies no access to that volume by hosts. See also default mapping and explicit mapping. master volume A volume that is enabled for snapshots and has an associated snap pool. MC Management Controller. A processor (located in a controller module) that is responsible for human-computer interface and computer-computer interfaces, including the WBI, CLI, and FTP interfaces, and interacts with the Storage Controller. See also EC and SC.
remote replication Asynchronous (batch) replication of block-level data from a volume in a primary system to a volume in one or more secondary systems by creating a replication snapshot of the primary volume and copying the snapshot data to the secondary systems via Fibre Channel or iSCSI links. The capability to perform remote replication is a licensed feature (Remote Snap). remote syslog support See syslog.
serial electrically erasable programmable ROM See SEEPROM. Service Location Protocol See SLP. SES SCSI Enclosure Services. The protocol that allows the initiator to communicate with the enclosure using SCSI commands. SFCB Small Footprint CIM Broker. SFF Small form factor. A type of disk drive. SHA Secure Hash Algorithm. A cryptographic hash function. SLP Service Location Protocol. Enables computers and other devices to find services in a local area network without prior configuration.
Storage Networking Industry Association See SNIA. storage system A controller enclosure with at least one connected drive enclosure. Product documentation and interfaces use the terms storage system and system interchangeably. syslog Remote syslog support. A configuration that, when enabled, sends selected event messages to the syslog on a remote system. UCS Transformation Format - 8-bit See UTF-8. ULP Unified LUN Presentation.
