HP StorageWorks 2000 G2 Modular Smart Array Reference Guide Part number: 500911-002 First edition: May 2009
Legal and notice information © Copyright 2009 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Microsoft and Windows are U.S.
Contents About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document conventions and symbols . . . . . . . .
Configuring user accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing a host's name . . Changing host mappings. . Configuring CHAP . . . . . . Deleting schedules . . . . . . .. .. .. .. . . . . .. .. .. .. .. .. .. .. . . . . .. .. .. .. . . . . .. .. .. .. .. .. .. .. . . . . .. .. .. .. .. .. .. .. . . . . .. .. .. .. . . . . .. .. .. .. .. .. .. .. . . . . .. .. .. .. .. .. .. .. . . . . .. .. .. .. . . . . . . . . . . . . .. .. .. .. . . . . .. .. .. .. .. .. .. .. . . . . .... .... .... .... . . . . . . . . . . . . . . . . . .
External details for connUnitRevsTable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External details for connUnitSensorTable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External details for connUnitPortTable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring SNMP event notification in SMU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 1 2 3 Relationship between a master volume and its snapshots and snap pool . . . . . . . . . . . . . . . . . . . . . . 20 Rolling back a master volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Creating a volume copy from a master volume or a snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 SMU communication status icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Settings for default users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Example applications and RAID levels . . . . . . .
About this guide This guide provides information about managing an 2000 G2 Modular Smart Array storage system by using its web interface, Storage Management Utility (SMU). Intended audience This guide is intended for storage system administrators.
CAUTION: NOTE: TIP: Indicates that failure to follow directions could result in damage to equipment or data. Provides additional information. Provides helpful hints and shortcuts. HP technical support Telephone numbers for worldwide technical support are listed on the HP support web site: http://www.hp.com/support/.
1 Getting started Storage Management Utility (SMU) is a web-based application for configuring, monitoring, and managing the storage system. Each controller module in the storage system contains a web server, which you access when you sign in to SMU. In a dual-controller system, you can access all functions from either controller. If one controller becomes unavailable, you can continue to manage the storage system from the partner controller. SMU is also referred to as the web-browser interface (WBI).
3. Click Sign In. If the system is available, the System Overview page is displayed; otherwise, a message indicates that the system is unavailable. Tips for signing in and signing out • Do not include a leading zero in an IP address. For example, enter 10.1.4.6 not 10.1.4.06. • Each user has a Monitor or Manage access level, as described in About user accounts on page 15. Multiple monitor and manage users can be signed in to each controller simultaneously.
Tips for using the help window • In the main panel, click the help icon to display help for the last-selected item, whether it is a component in the Configuration View panel or a subpanel in the main panel. • In the help window, click the table of contents icon to show or hide the Contents pane. • A help topic remains displayed until you browse to another topic in the help window, display help for a different item in the main window, or close the help window.
• Locale. The user’s preferred display language, which overrides the system’s default display language. Installed language sets include Chinese-simplified, Chinese-traditional, Dutch, English, French, German, Italian, Japanese, Korean, and Spanish. Settings for default users Table 3 Name Password Level Type WBI CLI FTP Base Prec. Units Temp.
When a disk fails, the system looks for a dedicated spare first. If it does not find a properly sized dedicated spare, it looks for a global spare. If it does not find a properly sized global spare and the dynamic spares option is enabled, it takes any properly sized available disk. If no properly sized spares are available, reconstruction cannot start. About volumes A volume is a logical subdivision of a vdisk, and can be mapped to controller host ports for access by hosts.
• Define CHAP secret in the host iSCSI initiator. • Request host login to the storage system. The host should be displayable by the system, as well as the ports through which connections were made. If it becomes necessary to add more hosts after CHAP is enabled, additional CHAP node names and secrets can be added. If a host attempts to login to the storage system, it will become visible to the system, even if the full login is not successful due to incompatible CHAP definitions.
About volume cache options You can set options that optimize reads and writes performed for each volume. Using write-back or write-through caching NOTE: Only disable write-back caching if you fully understand how the host operating system, application, and adapter move data. If used incorrectly, you might hinder system performance. You can change a volume's write-back cache setting.
• The Maximum option lets the controller dynamically calculate the maximum read-ahead cache size for the volume. For example, if a single volume exists, this setting enables the controller to use nearly half the memory for read-ahead cache. Only use Maximum when disk latencies must be absorbed by cache. • The Disabled option turns off read-ahead cache. This is useful if the host is triggering read ahead for what are random accesses.
The snapshot service has two features for reverting data back to original data: • Deleting only modified data on a snapshot. For snapshots that have been made accessible as read-write, you can delete just the modified (write) data that was written directly to a snapshot. When the modified data is deleted, the snapshot data reverts to the original data that was snapped. This feature is useful for testing an application, for example. You might want to test some code, which writes data to the snapshot.
Benefits include: • Additional data protection. An independent copy of a volume (versus logical copy through snapshot) provides additional data protection against a complete master volume failure. If the source master volume fails, the volume copy can be used to restore the volume to the point in time the volume copy was taken. • Non-disruptive use of production data. With an independent copy of the volume, resource contention and the potential performance impact on production volumes is mitigated.
About the VDS and VSS hardware providers Virtual Disk Service (VDS) enables host-based applications to manage vdisks and volumes. Volume Shadow Copy Service (VSS) enables host-based applications to manage snapshots. For more information, see the VDS and VSS hardware provider documentation for your product. About RAID levels The RAID controllers enable you to set up and manage vdisks, whose storage may be spread across multiple disks. This is accomplished through firmware resident in the RAID controller.
Table 5 RAID level Min.
About size representations In SMU panels, parameters such as names of users and volumes have a maximum length in bytes. ASCII characters are 1 byte; most Latin (Western European) characters with diacritics are 2 bytes; most Asian characters are 3 bytes. Operating systems usually show volume size in base 2. Disk drives usually show size in base 10. Memory size is always shown in base 2. In SMU, the base for entry and display of storage-space sizes can be set per user or per session.
About storage-space color codes SMU panels use the following color codes to identify how storage space is used.
About data protection in a single-controller storage system A 2000 G2 Modular Smart Array storage system can be purchased or operated with a single controller. Because single-controller mode is not a redundant configuration, this section presents some considerations concerning data protection. A volume’s default caching mode is write back, as opposed to write through. In write-back mode, data is held in controller cache until it is written to disk. In write-through mode, data is written directly to disk.
Getting started
2 Configuring the system Using the Configuration Wizard The Configuration Wizard helps you initially configure the system or change system configuration settings. The wizard has several steps, which are highlighted at the bottom of the panel as you complete them. The last step prompts you to confirm changes before applying them. If you cancel the wizard, no changes are made. Step 1: Starting the wizard 1.
• File Transfer Protocol (FTP). A secondary interface for installing firmware updates, downloading logs, and installing a license. • Simple Network Management Protocol (SNMP). Used for remote monitoring of the system through your network. • Service Interface. Used for technical support only. • Service Debug. Used for technical support only. In-band management interfaces operate through the data path and can slightly reduce I/O performance. The in-band options are: • In-band CAPI Capability.
3. Click Next to continue. Step 7: Configuring host ports In order for hosts to properly access the system, you must configure the system's host-interface options. For FC ports you can set these options: • Speed can be set to auto, which auto-negotiates the proper link speed with the host, or to 2Gb (Gbit per second) or 4Gb. A speed mismatch with a host prevents that host from accessing the storage system. • Connection mode can be set to loop or point-to-point.
To change iSCSI host-interface settings 1. For each iSCSI port, set the IP address, netmask, and gateway. 2. For all iSCSI ports, set the authentication, jumbo frames, link speed, and iSNS options. 3. Click Next to continue. Step 8: Confirming configuration changes Confirm that the values listed in the wizard panel are correct. • If they are not correct, click Previous to return to previous steps and make necessary changes.
To install a permanent license 1. Ensure that: • The license file is saved to a network location that SMU can access. • You are signed into the controller enclosure that the file was generated for. 2. In the Configuration View panel, right-click the system and select Tools > Install License. 3. Click Browse to locate and select the license file. 4. Click Install License File. If installation succeeds, the System Licenses table is updated. The licensing changes take effect immediately.
Configuring email notification To configure email notification of events 1. In the Configuration View panel, right-click the system and select Configuration > Services > Email Notification. 2. In the main panel, set the options: • Notification Level. Select the minimum severity for which the system should send notifications: Critical (only); Warning (and Critical); Informational (all). The default is none, which disables email notification. • SMTP Server address.
• User Type. Select Standard to allow access to standard functions, or Advanced to allow access to all functions except diagnostic functions, or Diagnostic to allow access to all functions. NOTE: This release has no functions that require Advanced or Diagnostic access; a Standard user can access all functions. • WBI Access. Allows access to the web-based management interface. • CLI Access. Allows access to the command-line management interface. • FTP Access.
• Temperature Preference. Specifies to use either the Celsius scale or the Fahrenheit scale for temperature values. • Auto Sign Out. Select the amount of time that the user's session can be idle before the user is automatically signed out: 5, 15, or 30 minutes, or Never (9999 minutes). The default is 30 minutes. • Locale. The user's preferred display language, which overrides the system's default display language.
Changing host interface settings In order for hosts to properly access the system, you must configure the system's host-interface options. There are options for FC and iSCSI ports but not for SAS ports. To change FC host interface settings 1. In the Configuration View panel, right-click the system and select Configuration > System Settings > Host Interfaces. 2. Set the speed to the proper value to communicate with the host.
• Link Speed. Sets the link speed to auto, which allows the system to negotiate the proper speed, or forces it to 1 Gbit/sec (1g). The default is auto. • iSNS. Enables or disables registration with a specified Internet Storage Name Service server, which provides name-to-IP-address mapping. Disabled by default. • iSNS Address. Specifies the IP address of an iSNS server. The default address is all zeroes. • Alternate iSNS Address.
Configuring advanced settings Changing disk settings Configuring SMART Self-Monitoring Analysis and Reporting Technology (SMART) provides data that enables you to monitor disks and analyze why a disk failed. When SMART is enabled, the system checks for SMART events one minute after a restart and every five minutes thereafter. SMART events are recorded in the event log. To change the SMART setting 1. In the Configuration View panel, right-click the system and select Configuration > Advanced Settings > Disk.
Changing cache settings Changing the synchronize-cache mode You can control how the storage system handles the SCSI SYNCHRONIZE CACHE command. Typically you can use the default setting. However, if the system has performance problems or problems writing to databases or other applications, contact technical support to determine if you should change this option. To change the synchronize-cache mode 1.
Changing auto-write-through cache triggers and behaviors You can set conditions that cause (“trigger”) a controller to change the cache mode from write-back to write-through, as described in About volume cache options on page 19. You can also specify actions for the system to take when write-through caching is triggered. To change auto-write-through cache triggers and behaviors 1. In the Configuration View panel, right-click the system and select Configuration > Advanced Settings > Cache. 2.
TIP: If you choose to disable background scrub, you can still scrub selected vdisks by using Media Scrub Vdisk. To change the background scrub setting 1. In the Configuration View panel, right-click the system and select Configuration > Advanced Settings > System Utilities. 2. Either select (enable) or clear (disable) the Background Scrub option. 3. Click Apply.
Changing a vdisk's name To change a vdisk's name 1. In the Configuration View panel, right-click a vdisk and select Configuration > Modify Vdisk Name. The main panel shows the vdisk's name. 2. Enter a new name. A vdisk name is case sensitive and cannot already exist in the system. A name cannot include a comma, double quote, or backslash. 3. Click Modify Name. The new name appears in the Configuration View panel.
Changing a volume's cache settings CAUTION: • Only disable write-back caching if you fully understand how the host operating system, application, and adapter move data. If used incorrectly, you might hinder system performance. • Only change read-ahead cache settings if you fully understand how the host operating system, application, and adapter move data so that you can adjust the settings accordingly. To change a volume's cache settings 1.
3 Provisioning the system Using the Provisioning Wizard The Provisioning Wizard helps you create a vdisk with volumes and to map the volumes to hosts. The wizard has several steps, which are highlighted at the bottom of the panel as you complete them. The last step prompts you to confirm changes before applying them. If you cancel the wizard, no changes are made. Step 1: Starting the wizard 1.
Step 3: Selecting disks Select disks to include in the vdisk. The Disk Selection Sets table has one row for each sub-vdisk in a RAID-10 or RAID-50 vdisk, or a single row for a vdisk having another RAID level. The table also has a SPARE row where you can assign dedicated pares to the vdisk. In each row, the Disks field shows how many disks you can, and have, assigned. As you select disks, the table shows the amount of storage space in the vdisk.
4. Select the access level that hosts will have to the volumes: read-write, read-only, or no-access (masked). 5. Click Next to continue. Step 6: Confirming vdisk settings Confirm that the values listed in the wizard panel are correct. • If they are not correct, click Previous to return to previous steps and make necessary changes. • If they are correct, click Finish to apply the setting changes and finish the wizard. Creating a vdisk To create a vdisk 1.
Expanding a vdisk You can expand the capacity of a vdisk by adding disks to it. Host I/O to the vdisk can continue while the expansion proceeds. You can then create or expand a volume to use the new free space, which becomes available when the expansion is complete. You can expand only one vdisk at a time. The RAID level determines whether the vdisk can be expanded and the maximum number of disks the vdisk can have.
Creating a volume set In a vdisk that has sufficient free space, you can create multiple volumes with the same base name, size, and default mapping settings. To create a volume set 1. In the Configuration View panel, right-click a vdisk and select Provisioning > Create Volume Set. 2. In the main panel, set the options: • Volume Set Base-name. Optionally change the base name for the volumes. The volume names will consist of the base name and a number that increments from 000.
Deleting volumes CAUTION: Deleting a volume removes its mappings and deletes its data. To delete volumes 1. Verify that hosts are not accessing the volumes that you want to delete. 2. In the Configuration View panel, either: • Right-click the system or Vdisks or a vdisk and then select Provisioning > Delete Volumes. • Right-click a volume and select Provisioning > Delete Volume. 3. In the main panel, select the volumes to delete. To select or clear all volumes, toggle the checkbox in the heading row. 4.
Changing a volume's explicit mappings CAUTION: Volume mapping changes take effect immediately. Make changes that limit access to volumes when the volumes are not in use. Be sure to unmount a mapped volume from a host system before changing the mapping's LUN. To view volume mappings In the Configuration View panel, right-click a volume and select Provisioning > Explicit Mappings. The main panel shows the following information about the volume's mappings: • Type. Explicit or Default.
Creating multiple snapshots You can select multiple volumes and immediately create a snapshot of each volume. To create multiple snapshots 1. In the Configuration View panel, right-click the system or Vdisks or a vdisk and then select Provisioning > Create Snapshots. 2. In the main panel, select each volume to take a snapshot of. To select or clear all volumes, toggle the checkbox in the heading row. 3. Click Create Snapshots. If the task succeeds, the snapshots appear in the Configuration View panel.
Deleting a snapshot When you delete a snapshot, all data uniquely associated with that snapshot is deleted and associated space in the snap pool is freed for use. Snapshots can be deleted in any order, irrespective of the order in which they were created. CAUTION: Deleting a snapshot removes its mappings and deletes its data. To delete a snapshot 1. Verify that hosts are not accessing the snapshot that you want to delete. 2.
Creating a volume copy With the appropriate license, you can copy a volume or a snapshot to a new standard volume. The destination volume must be in a vdisk owned by the same controller as the source volume. If the source volume is a snapshot, you can choose whether to include its modified data (data written to the snapshot since it was created). The resulting volume is completely independent of the source volume.
• With Modified Data. If the source volume is a snapshot, select this option to include the snapshot’s modified data in the copy. Otherwise, the copy will contain only the data that existed when the snapshot was created. • Start Schedule. Specify a date and a time in the future for the schedule to start running. • Date must use the format yyyy-mm-dd. • Time must use the format hh:mm followed by either AM, PM, or 24H (24-hour clock). For example, 13:00 24H is the same as 1:00 PM. • Recurrence.
To roll back a volume 1. Unmount the volume from hosts. 2. If the roll back will include snapshot modified data, unmount the snapshot from hosts. 3. In the Configuration View panel, right-click a volume and select Provisioning > Roll Back Volume. 4. In the main panel, set the options: • For Volume. • From Snapshot Volume. Enter the name of the snapshot to roll back to. • With Modified Data. Select this option to include the snapshot’s modified data in the roll back.
Changing a host's name To change a host's name 1. In the Configuration View panel, right-click a host and select Provisioning > Rename Host. 2. Enter a new name that helps you easily identify the host; for example, MailServer_P1. A host name is case sensitive and cannot already exist in the system. A name cannot include a comma, double quote, or backslash. 3. Click Modify Name. Changing host mappings For each volume that is mapped to the selected host, you can create, modify, and delete explicit mappings.
Configuring CHAP For iSCSI, you can use Challenge-Handshake Authentication Protocol (CHAP) to perform authentication between the initiator and target of a login request. To perform this identification, a database of CHAP entries must exist on each device. Each CHAP entry can specify one name-secret pair to authenticate the initiator only (one-way CHAP) or two pairs to authenticate both the initiator and the target (mutual CHAP).
4 Using system tools Updating firmware You can view the current versions of firmware in controller modules, expansion modules (in drive enclosures), and disks, and install new versions. TIP: To ensure success of an online update, select a period of low I/O activity. This helps the update complete as quickly as possible and avoids disruptions to host and applications due to timeouts.
To update expansion module firmware 1. Obtain the appropriate firmware file and download it to your computer or network. 2. Stop I/O to vdisks before starting the firmware update. 3. In the Configuration View panel, right-click the system and select Tools > Update Firmware. The table titled Current Versions of All Expansion Modules (EMPs) shows the currently installed versions. 4. Select the expansion modules to update. 5. Click Browse and select the firmware file to install. 6.
7. If the updated disks must be power cycled: a. Shut down both controllers; see Restarting or shutting down controllers on page 62. b. Power cycle all enclosures as described in your product’s user guide. NOTE: If you loaded firmware to a Seagate 750-Gbyte Barracuda ES SATA drive, after spin-up it will be busy for about 50 seconds completing its update. Then it will be ready for host I/O. 8. Verify that each disk has the correct firmware revision.
Rescanning disk channels A rescan forces a rediscovery of disks and enclosures in the storage system. If two Storage Controllers are online, rescan also reassigns the enclosure IDs of attached enclosures based on controller A's enclosure cabling order. A manual rescan may be needed after system power-up to display enclosures in the proper order. A manual rescan temporarily pauses all I/O processes, then resumes normal operation. It can take up to two minutes for the enclosure IDs to be corrected.
To perform a restart 1. In the Configuration View panel, right-click the local system and select Configuration > Shut Down or Restart Controller. 2. In the main panel, set the options: • Select the Restart operation. • Select the type of controller processor to restart. • Select whether to restart the processor in controller A, B, or both. 3. Click Restart now. A confirmation dialog appears. 4. Click Yes to continue; otherwise, click No. If you clicked Yes, a second confirmation dialog appears. 5.
Verifying a vdisk If you suspect that a redundant (mirror or parity) vdisk has a problem, you can run the Verify utility to check the vdisk's integrity. For example, if the storage system was operating outside the normal temperature range, you might want to verify its vdisks. The Verify utility checks whether the redundancy data in the vdisk is consistent with the user data in the vdisk. For RAID 3, 5, 6, and 50, the utility checks all parity blocks to find data-parity mismatches.
Removing a vdisk from quarantine A previously fault-tolerant vdisk becomes quarantined when not all of its disks are detected after a restart or rescan. A quarantined vdisk is shown with health Critical and status QTCR or QTOF.
Using system tools
5 Viewing system status Viewing information about the system In the Configuration View panel, right-click the system and select View > Overview. The System Overview table shows: • The system’s health: OK. The system is operating normally. Degraded. Fault. Unknown. At least one component is degraded or has a fault.
Snapshot properties When you select the Snapshots component a table shows each snapshot's name, serial number, source volume, snap-pool name, amounts of snap data, unique data, and shared data, and vdisk name. • Snap data is the total amount of data associated with the specific snapshot (data copied from a source volume to a snapshot and data written directly to a snapshot). • Unique data is the amount of data that has been written to the snapshot since the last snapshot was taken.
NOTE: If you are having a problem with the system or a vdisk, check the event log before calling technical support. Event messages might enable you to resolve the problem. When reviewing events, do the following: 1. For any critical or warning events, look for recommended actions in the Event code reference appendix. Identify the primary events and any that might be the cause of the primary event. For example, an over-temperature event could cause a disk failure. 2.
• Current Owner. Either the preferred owner during normal operation or the partner controller when the preferred owner is offline. • Disks. • Spares. Viewing information about a vdisk In the Configuration View panel, right-click a vdisk and select View > Overview.
• OFFL: The vdisk is offline because it is using offline initialization, or because disks are down and data may be lost. • QTCR: The vdisk is in a critical state and has been quarantined because some disks are missing. • QTOF: The vdisk is offline and has been quarantined because some disks are missing. • UP: The vdisk is online and does not have fault-tolerant attributes. • Current Job. If a utility is running on the vdisk, this field shows the utility's name and progress.
Volume properties When you select the Volumes component, the Volumes table shows: • The volume’s name, serial number, and size • The name of the vdisk containing the volume Snap-pool properties When you select the Snap Pools component, the Snap Pools table shows: • The snap pool's name, serial number, size, and free space • The quantity of master volumes and snapshots associated with the snap pool • The name of the vdisk containing the snap pool Viewing information about a volume In the Configuration View
Schedule properties If any schedules exist for this volume, when you select the Schedules component, the Schedules table shows information about each schedule. For the selected schedule, the Schedule Details table shows: • Schedule Name. • Schedule Specification. • Schedule Status. • Next Time. • Task Type. • Task Status. • Task State. • Source Volume. • Source Volume Serial. • Prefix. • Count. • Last Created.
Mapping properties When you select the Maps component, the Maps for Volume table shows: • Type. Explicit or Default. Settings for an explicit mapping override the default mapping. • Host ID. WWPN or IQN. • Name. Host name. • Ports. Controller host ports through which the volume is mapped to the host. • LUN. Volume identifier presented to the host. • Access. Volume access type: read-write, read-only, no-access (masked), or not-mapped.
Host properties When you select the Host component, the Properties for Host table shows: • Host ID. WWPN or IQN. • Name. • Discovered. If the host was discovered and its entry was automatically created, Yes. If the host entry was manually created, No. • Mapped. If volumes are mapped to the host, Yes; otherwise, No. • Profile. If the host type is Standard, LUN 0 can be assigned to a mapping. If the host type is OpenVMS, LUN 0 cannot be assigned to a mapping.
Viewing system status
A SNMP reference This appendix describes the Simple Network Management Protocol (SNMP) capabilities that 2000 G2 Modular Smart Array storage systems support. This includes standard MIB-II, the FibreAlliance SNMP Management Information Base (MIB) version 2.2 objects, and enterprise traps. 2000 G2 Modular Smart Array storage systems can report their status through SNMP. SNMP provides basic discovery using MIB-II, more detailed status with the FA MIB 2.2, and asynchronous notification using enterprise traps.
FA MIB 2.2 SNMP behavior The FA MIB 2.2 objects are in compliance with the FibreAlliance MIB v2.2 Specification (FA MIB2.2 Spec). For a full description of this MIB, go to: http://www.emc.com/microsites/fibrealliance. FA MIB 2.2 is a subset of FA MIB 4.0, which is included with HP System Insight Manager (SIM) and other products. The differences are described in FA MIB 2.2 and 4.0 Differences on page 87. FA MIB 2.
Table 10 FA MIB 2.2 objects, descriptions, and values (continued) Object Description Value connUnitTable Includes the following objects as specified by the FA MIB2.
Table 10 80 FA MIB 2.2 objects, descriptions, and values (continued) Object Description Value connUnitContact Settable: Contact information for this connectivity unit Default: Uninitialized Contact connUnitLocation Settable: Location information for this connectivity unit Default: Uninitialized Location connUnitEventFilter Defines the event severity that will be logged by this connectivity unit. Settable only through SMU.
Table 10 FA MIB 2.2 objects, descriptions, and values (continued) Object Description Value connUnitPortTable Includes the following objects as specified by the FA MIB2.
Table 10 FA MIB 2.2 objects, descriptions, and values (continued) Object Description Value connUnitEventTable Includes the following objects as specified by the FA MIB2.
Table 10 FA MIB 2.2 objects, descriptions, and values (continued) Object Description Value trapRegRowState Specifies the state of the row • READ: rowActive[3] if traps are enabled through Telnet; otherwise rowInactive[2] • WRITE: Not supported External details for certain FA MIB 2.2 objects Tables in this section specify values for certain objects described in Table 10.
External details for connUnitSensorTable Table 12 connUnitSensorTable index, name, type, and characteristic values connUnitSensorIndex connUnitSensorName connUnitSensorType connUnitSensor Characteristic 1 CPU Temperature (Controller A) board [8] temperature[3] 2 CPU Temperature (Controller B) board [8] temperature[3] 3 FPGA Temperature (Controller A) board [8] temperature[3] 4 FPGA Temperature (Controller B) board [8] temperature[3] 5 Onboard Temperature 1 (Controller A) board [8] tem
External details for connUnitPortTable Table 13 connUnitPortTable index and name values connUnitPortIndex connUnitPortName 1 Host Port 1 (Controller A) 2 Host Port 2 (Controller B) 3 Host Port 1 (Controller A) 4 Host Port 2 (Controller B) Configuring SNMP event notification in SMU 1. Verify that the storage system’s SNMP service is enabled; see Changing management interface settings on page 33. 2. Configure and enable SNMP traps; see Configuring SNMP notification on page 34.
FROM RFC-1215 connUnitEventId, connUnitEventType, connUnitEventDescr FROM FA-MIB40; --Textual conventions for this MIB ----------------------------------------------------------------------- vendor hp nm hpMSA OBJECT IDENTIFIER ::= { enterprises 11 } OBJECT IDENTIFIER ::= { hp 2 } OBJECT IDENTIFIER ::= { nm 51 } -- Related traps msaEventInfoTrap TRAP-TYPE ENTERPRISE hpMSA VARIABLES { connUnitEventId, connUnitEventType, connUnitEventDescr } DESCRIPTION "An event has been generated by the storage array.
-- Trap annotations are as follows: --#TYPE "Error storage event" --#SUMMARY "Error storage event # %d, type %d, description: %s" --#ARGUMENTS {0,1,2} --#SEVERITY MAJOR --#TIMEINDEX 6 ::= 3003 msaEventCriticalTrap TRAP-TYPE ENTERPRISE hpMSA VARIABLES { connUnitEventId, connUnitEventType, connUnitEventDescr } DESCRIPTION "An event has been generated by the storage array.
SNMP reference
B Event code reference Information in this appendix is for reference by storage administrators and technical support personnel to aid troubleshooting. An event code identifies a type of event that has occurred in the storage system, and corresponds to an event message that is recorded in the system’s event log, which you can view using SMU or the CLI. You may also receive notifications, depending on your SMU event notification settings.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code Description 19 Informational A rescan has completed. 20 Informational A firmware update has completed. 21 Informational or warning Vdisk verification has completed. This event is logged as informational if the command fails immediately, succeeds, or is aborted by the user; or a warning if the operation fails during verification. 23 Informational Vdisk creation has started.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code Description Recommended action 40 The sensors monitored a temperature or voltage in the failure range. • Check that the storage system’s fans are Critical running. • Check that the ambient temperature is not too warm. The enclosure operating range is 41–104° F (5–40° C). • Check for any obstructions to the airflow. • If none of the above explanations apply, replace the controller FRU that reported the error.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code Description Recommended action 59 The controller detected an error while communicating with the specified SCSI device. The error was detected by the controller, not the disk. This event is logged as a warning for parity errors, and as informational for other errors.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code Description Recommended action 75 Informational The specified volume’s LUN has been unassigned because it conflicts with LUNs assigned to other volumes. This can happen when disks containing data for a mapped volume have been inserted from another enclosure. If you want hosts to access the volume data on the inserted disks, map the volume with a different LUN.
Table 14 Event code descriptions and recommended actions (continued) 94 Event Event type code Description 90 Informational 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 cleared. 95 Critical Both controllers in an active-active configuration have the same serial number.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code Description Recommended action 116 Critical After a recovery, the partner controller was killed while mirroring write-back data to the current controller. The current controller 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.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code Description 161 Informational One or more enclosures do not have a valid path to an EMP. All enclosure EMPs are disabled. 162 Warning The host WWNs (node and port) previously presented by this controller module in this system are unknown. This event has two possible causes: Recommended action Verify the WWN information for this controller module on all hosts that access it.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code Description Recommended action 169 Informational The specified SES alert condition has been cleared in the enclosure indicated. This event is generated when the problem that caused event 168 is cleared. 170 Informational The last rescan indicates that the specified enclosure was added to the system. 171 Informational The last rescan indicates that the specified enclosure was removed from the system.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code Description 190– 201 Informational Includes component-specific environmental indicator events generated by the auto-write-through feature when an environmental change occurs. If an auto-write-through-trigger condition has been met, write-back cache is disabled and event 188 is also logged. Once the fault is resolved, event 187 is logged to indicate that write-back mode has been restored.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code Description Recommended action 214 Informational The creation of snapshots is complete. The number of snapshots is specified. 215 Informational A previously created batch of snapshots is now committed and ready for use. The number of snapshots is specified. 217 Critical A super-capacitor failure has occurred on the controller.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code Description Recommended action 230 The snap pool has reached the snap pool error threshold. You can expand the snap pool or delete snapshots. Warning The system will take the action set up in the policy. Default is to delete the oldest snapshot. 231 Critical The snap pool has reached the snap pool critical threshold. The system will take the action set up in the policy.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code Description Recommended action 245 Informational An existing disk channel target device is not responding to SCSI discovery commands. Check the indicated target device for bad hardware or bad cable, then initiate a rescan. 246 Warning The coin battery is either not present, or it is not properly seated, or it has reached end of life. (The battery is a battery backup for the real-time (date/time) clock.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code Description Recommended action 265 Informational Port bypass circuits currently use the service port, which may limit the link speed or interconnect mode support. Perform a system-level shutdown and restart. Note that this will cause all data to be unavailable for about 1 minute. 266 Informational A copy operation for the specified master volume has been aborted.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code Description Recommended action 306 Informational An old serial number in SC flash memory has been updated to a new serial number. 307 Critical A temperature sensor on a controller FRU detected an over-temperature condition that caused the controller to shut down. Check that the storage system’s fans are running. Check that the ambient temperature is not too warm.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code Description Recommended action 322 The controller has an older SC version than the version used to create the CHAP authentication database in the controller’s flash memory. Upgrade to an SC version that is current for the indicated database version. Warning The CHAP database cannot be read or updated.
As referred to in Table 14, the following table lists disk- error conditions and recommended actions. Table 15 Disk error conditions and recommended actions Status Recommended action The status of the vdisk that originally had the failed disk status is Good. A global or vdisk (dedicated) spare has been successfully integrated into the vdisk and the replacement disk can be assigned as either a global spare or a vdisk spare. Use SMU to assign the new disk as either a global spare or a vdisk spare.
Event code reference
C Using FTP to download logs and update firmware Although SMU is the preferred interface for downloading logs, updating firmware, and installing a license, you can also use FTP to do these tasks. Downloading system logs To help service personnel diagnose a system problem, you might be asked to download and submit system log data. You can do this by accessing the system’s FTP interface and running the get logs command.
Updating controller module firmware A controller enclosure can contain one or two controller modules. In a dual-controller system, both controllers should run the same firmware version. You can update the firmware in each controller module by loading a firmware file obtained from the HP web download site, http://www.hp.com/go/msa. To install an HP ROM Flash Component or firmware Smart Component, follow the instructions on the HP web site; otherwise, to install a firmware binary file, follow the steps below.
Updating expansion module firmware A drive enclosure can contain one or two expansion modules. Each expansion module contains an enclosure management processor (EMP). All modules of the same model should run the same firmware version. You can update the firmware in each expansion module by loading a firmware file obtained from the HP web download site, http://www.hp.com/go/msa.
Updating disk firmware You can update disk firmware by loading a firmware file obtained from the HP web download site, http://www.hp.com/go/msa, or from the disk manufacturer. To install an HP ROM Flash Component or firmware Smart Component, follow the instructions on the HP web site; otherwise, to install a firmware binary file, follow the steps below. A dual-ported disk can be updated from either controller.
6. Quit the FTP session. 7. If the updated disks must be power cycled: a. Shut down both controllers by using SMU. b. Power cycle all enclosures as described in your product’s user guide. NOTE: If you loaded firmware to a Seagate 750-Gbyte Barracuda ES SATA drive, after spin-up it will be busy for about 50 seconds completing its upgrade. Then it will be ready for host I/O. 8. In SMU, verify that each disk has the correct firmware revision. 9. Resume host I/O. Installing a license file 1.
Using FTP to download logs and update firmware
Glossary CHAP Challenge-Handshake Authentication Protocol. chunk size The amount of contiguous data that is written to a vdisk member before moving to the next member of the vdisk. dedicated spare A disk that is reserved for use by a specific vdisk to replace a failed disk. default mapping Host-access settings that are configured when a volume is created. dual-port disk A dual-port disk is connected to both controllers so its data path is fault tolerant.
snap pool A volume that stores data that is specific to snapshots of an associated master volume, including copy-on-write data and data written explicitly to the snapshots. A snap pool cannot be mapped. snapshot A “virtual” volume that preserves the state of a master volume’s data as it existed when the snapshot was created. Data associated with a snapshot is recorded in both the master volume and in its associated snap pool. A snapshot can be mapped and written to. SSD Solid-state drive.
Index Symbols * (asterisk) in option name 14 A asterisk (*) in option name 14 audience 11 B browser buttons to avoid 14 setup 13 bytes versus characters 25 C cache configuring auto-write-through triggers and behaviors 41 configuring host access to 40 configuring system settings 40 configuring volume settings 44 CHAP add or modify records 58 configure for iSCSI hosts 58 configuring 31, 37 delete records 58 overview 17 characters versus bytes 25 color codes for storage space 26 configuration browser 13 fir
using WBI to update expansion module 59 versions 68 firmware update, partner configuring 41 FTP downloading system logs 107 updating controller module firmware 108 updating disk drive firmware 110 updating expansion module firmware 109 G global spare 16 global spares adding and removing 48 H hardware versions 68 help displaying online 15 obtaining 12 using the help window 15 host adding 56 changing mappings 57 changing name 57 create 115 properties 75 viewing information about 74 host access to cache conf
Provisioning Wizard using to create a vdisk with volumes and mappings 45 Q quarantined vdisk 65 R RAID levels about 23 read-ahead caching optimizing 19 related documentation 11 rescan disk channels 62 restarting controllers 62 revert volume data See roll back volume data roll back volume data about 21 S schedule properties 68 schedule properties 74 schedules deleting 58 scheduling snapshot 52 snapshot reset 53 volume copy 54 scrub configuring background 41 SCSI MODE SELECT command configuring handling of
U unique data (snapshot) 73 Universal Time (UT) 25 users about user accounts 15 adding 34 change default passwords with Configuration Wizard 29 maximum that can sign in 14 modifying 35 removing 36 utility priority configuring 42 V vdisk abort verification 64 aborting scrub 64 changing name 43 changing owner 43 configuring 42 creating 47 creating with the Provisioning Wizard 45 expanding 48 health values 69, 70 properties 67, 70 reconstruction 26 removing from quarantine 65 scrubbing 64 status values 69, 70
