HP StorageWorks 2300 Modular Smart Array reference guide Part number: 500911-001 First edition: January 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document conventions and symbols . . . . . . . .
Viewing information about a snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Snapshot properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mapping properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing information about all hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the EMP polling rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To change the EMP polling rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing cache settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the synchronize-cache mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing a volume's default mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To change a volume's default mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing a volume's explicit mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To view volume mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A SNMP reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Standard MIB-II behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enterprise traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FA MIB 2.2 SNMP behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 1 2 3 4 5 Relationship between a master volume and its snapshots and snap pool . . Rolling back a master volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Volume copy from a master volume and a snapshot . . . . . . . . . . . . . . . . Copying a master volume and a snapshot . . . . . . . . . . . . . . . . . . . . . . Rolling back a master volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. .. .. .. .. .. .. .. .. . . . . . .. .. .. .. .. .. .
Tables 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 SMU communication status icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Settings for default users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Example applications and RAID levels . . . . . . .
About this guide This guide provides information about managing an 2300 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: Indicates that failure to follow directions could result in damage to equipment or data. IMPORTANT: NOTE: TIP: Provides clarifying information or specific instructions. 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/.
Documentation feedback HP welcomes your feedback. To make comments and suggestions about product documentation, please send a message to storagedocs.feedback@hp.com. All submissions become the property of HP.
1 Using Storage Management Utility (SMU) 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).
• Many tables can be sorted by a specific column. To do so, click the column heading to sort low to high; click again to sort high to low. • Do not use the browser's Back, Forward, Reload, or Refresh buttons. The application is essentially a single page that is automatically updated to show current data. You do not need to refresh it and if you click Back, you may exit the application. • An asterisk (*) identifies a required setting.
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. Allows access to the file transfer protocol interface, which provides a way to download logs and install firmware updates. • Base Preference. The base for entry and display of storage-space sizes.
In a dual-controller system, when a controller fails, the partner controller assumes temporary ownership of the failed controller's vdisks and resources. If the system uses a fault-tolerant cabling configuration, both controllers' LUNs become accessible through the partner. When you create a vdisk you can also create volumes within it. A volume is a logical subdivision of a vdisk, and can be mapped to controller host ports for access by hosts. The storage system presents only volumes, not vdisks, to hosts.
You must assign a name to an automatically added host to have the system retain it after a restart. Naming hosts also makes them easy to recognize for volume mapping. A maximum of 63 names can be assigned. The Configuration Viewpanel lists hosts by name, or if they are unnamed, by ID. About volume mapping Each volume has default host-access settings that are set when the volume is created; these settings are called the default mapping.
does not mirror the write data because the data is written to the disk before posting command completion and mirroring is not required. You can set conditions that cause the controller to change from write-back caching to write-through caching. In both caching strategies, active-active failover of the controllers is enabled. You can enable and disable the write-back cache for each volume. By default, volume write-back cache is enabled.
About the Snapshot feature Snapshot is a licensed feature that provides data protection by enabling you to create and save snapshots of a volume. Each snapshot preserves the source volume's data state at the point in time when the snapshot was created. Snapshots can be created manually or by using the task scheduler. When the first snapshot is taken of a standard volume, the system automatically converts the volume into a master volume and reserves additional space for snapshot data.
The following figure shows the difference between rolling back the master volume to the data that existed when a specified snapshot was created (preserved), and rolling back preserved and modified data. MasterVolume-1 Snapshot-1 Preserved Data (Wed Jan 18 22:37:17 2008) Modified Data (Thur Jan 22 21:20:30 2008) When you use the rollback feature, you can choose to exclude the modified data, which will revert the data on the master volume to the preserved data when the snapshot was taken.
The following figure illustrates how volume copies are created. Copying a standard or master volume Source volume Transient snapshot Data transfer New volume 1. Volume copy request is made with a standard volume or a master volume as the source. 2. If the source a standard volume, it is converted to a master volume and a snap pool is created. 3. A new volume is created for the volume copy, and a hidden, transient snapshot is created. 4. Data is transferred from the transient snapshot to the new volume.
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. RAID refers to vdisks in which part of the storage capacity may be used to store redundant data. The redundant data enables the system to reconstruct data if a disk in the vdisk fails. Hosts see each partition of a vdisk, known as a volume, as a single disk.
Table 5 RAID level comparison (continued) RAID level Min.
About size representations 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. When entering storage-spaces sizes only, either base-2 or base-10 units can be specified.
About storage-space color codes SMU panels use the following color codes to identify how storage space is used.
Using Storage Management Utility (SMU)
2 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 overall health: OK. The system is operating normally. Degraded. Fault. Unknown. At least one component is degraded or has a fault.
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. Review the event log for the controller that reported the critical/warning event by viewing the event log by controller. Locate the critical/warning events in the sequence.
Viewing information about a vdisk In the Configuration View panel, right-click a vdisk and select View > Overview. The Vdisks Overview table shows: • The overall health, capacity, and space usage of the vdisk • The overall health, quantity, capacity, and space usage of disks in the vdisk • The quantity, capacity, and space usage of volumes in the vdisk • The quantity, capacity, and space usage of snap pools in the vdisk For descriptions of storage-space color codes, see About storage-space color codes.
Disk properties When you select the Disks component, two tables appear. The Disk Sets table shows: • Total Space. Total storage space in the vdisk. • Type. For RAID 10 or RAID 50, the sub-vdisk that the disk is in; for other RAID levels, the disk's RAID level; or spare. • Disk Type. SAS (dual port), SAS-S (single port), SATA (dual port), or SATA-S (single port). • Disks. • Size. The Enclosure Front View table has two tabs. The Tabular tab shows: • Health. Shows whether the disk is healthy or has a problem.
Viewing information about a volume In the Configuration View panel, right-click a volume and select View > Overview. The Volume Overview table shows: • The capacity and space usage of the volume • The quantity of mappings for the volume • The quantity of task schedules for the volume For descriptions of storage-space color codes, see About storage-space color codes. Select a component to see more information about it.
• Source Volume Serial. • Prefix. • Count. • Last Created. Viewing information about a snapshot In the Configuration View panel, right-click a snapshot and select View > Overview. The Snapshot Overview table shows: • The capacity and space usage of the snapshot • The quantity of mappings for the snapshot • The quantity of task schedules for the snapshot For descriptions of storage-space color codes, see About storage-space color codes. Select a component to see more information about it.
Schedule properties If any schedules exist for the snapshot, 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 Host table shows: • Type. Explicit or Default. Settings for an explicit mapping override the default mapping. • Name. Volume name. • Serial Number. Volume serial number. • 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.
3 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. To use the wizard 1.
Enabling management interfaces You can enable or disable management-interface services to limit the ways in which users and host-based management applications can access the storage system. Network management interfaces operate out-of-band and do not affect host I/O to the system. The network options are: • Web Browser Interface (WBI). The primary interface for managing the system. You can enable use of HTTP, of HTTPS for increased security, or both. • Command Line Interface (CLI).
2. In the SNMP Configuration section, 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 SNMP notification. • Read Community. The SNMP read password for your network. The value is case sensitive. The default is public. • Write Community. The SNMP write password for your network. The value is case sensitive. The default is private.
To install a 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 > License Management. 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. The default is 30 minutes. • Locale. The user's preferred display language, which overrides the system's default display language.
Changing host port settings In order for hosts attached to the storage system's host ports to properly access the system, you must configure the system's host-interface options. To change FC host port 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.
Setting system information To set system information 1. In the Configuration View panel, right-click the system and select Configuration > System Settings > System Information. 2. In the main panel, set the name, contact person or group, location, and other information about the system. The system name is shown in the browser title bar or tab. All four values are recorded in system debug logs for reference by service personnel. 3. Click Apply.
To change the EMP polling rate 1. In the Configuration View panel, right-click the system and select Configuration > Advanced Settings > Disk. 2. Set the EMP Polling Rate interval. The default is 5 seconds. 3. Click Apply. 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.
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. 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.
NOTE: 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.
4 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. To use the wizard 1.
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.
To specify the default mapping 1. Set the options: • Select the Map checkbox. • LUN. Optionally change the LUN that attached hosts can use to access the volume. • Access. Select the access level that hosts will have to the volumes. • In the enclosure view or list, select controller host ports through which attached hosts can access the volume. 2. Click Next to continue. Confirming vdisk settings Confirm that the values listed in the wizard panel are correct.
5. Click Delete to continue; otherwise, click Cancel. If you clicked Delete, a processing dialog appears. As vdisks are deleted they are removed from the table and from the Configuration View panel. When processing is complete a success dialog appears. 6. Click OK. 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.
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.
• LUN. Volume identifier presented to the host. • Access. Volume access type: read-write, read-only, no-access (masked), or not-mapped. To create an explicit mapping 1. In the Maps for Volume table, select the Default mapping to change. The mapping options appear. 2. Select Map. 3. Set the LUN and select the access type and ports. 4. Click Apply. A message specifies whether the change succeeded or failed. 5. Click OK. The mapping becomes Explicit with the new settings. To modify an explicit mapping 1.
Creating a snapshot You can create a snapshot now or schedule the snapshot task. NOTE: The first time a snapshot is created of a standard volume, the volume is converted to a master volume and a snap pool is created. The snap pool's size is 20% of the volume size or 10 GB, whichever is larger. Before creating or scheduling snapshots, verify that the vdisk has enough free space. To create a snapshot now 1. In the Configuration View panel, right-click a volume and select Provisioning > Create Snapshot. 2.
3. In the main panel, select the snapshot to delete. 4. Click Delete Snapshot. 5. Click OK to continue; otherwise, click Cancel. If you clicked OK, a processing dialog appears. When the snapshot is deleted it is removed from the table and from the Configuration View panel. When processing is complete a success dialog appears. 6. Click OK. Resetting a snapshot Instead of taking a new snapshot of a volume, you can replace the data in a snapshot with the current data in the source volume.
Copy a volume 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. Volume Copy from a Master Volume Master Volume Transient Snapshot Data Transfer New Volume 1.
To copy a volume now 1. In the Configuration View panel, right-click a volume and select Provisioning > Create Volume Copy. 2. In the main panel, select Now. 3. Set the options: • New Volume Name. Optionally change the default name for the destination volume. A volume name is case sensitive and cannot already exist in a vdisk. A name cannot include a comma, double quote, or backslash. • Residing On Vdisk. Optionally change the destination vdisk. • With Modified Data.
Rolling back a volume You can roll back (revert) the data in a volume to the data that existed when a specified snapshot was created. You also have the option of including its modified data (data written to the snapshot since it was created). For example, you might want to take a snapshot, mount it for read/write, and then install new software on the snapshot for testing. If the software installation is successful, you can roll back the volume to the contents of the modified snapshot.
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. Otherwise, the master volume will contain only the data that existed when the snapshot was created. 5. Click Roll Back Volume. The roll back starts. You can now remount the volume. The panel shows the roll back's progress. 6.
Changing host mappings For each volume that is mapped to the selected host, you can create, modify, and delete explicit mappings. To change a volume's default mapping, see Changing a volume's default mapping. 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.
5 Using system utilities Resetting a host port Making a configuration or cabling change on a host might cause the storage system to stop accepting I/O requests from that host. For example, this problem can occur after moving host cables from one HBA to another on the host. To fix such a problem you might need to reset controller host ports (channels). For a Fibre Channel host port configured to use FC-AL (loop) topology, a reset issues a loop initialization primitive (LIP). To reset a host port 1.
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 QRCR or QROF.
Using system utilities
A SNMP reference This appendix describes the Simple Network Management Protocol (SNMP) capabilities that 2300 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. 2300 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. 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 74 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 trapRegFilter Settable: Defines the trap severity filter for this trap host. The connUnit will send traps to this host that have a severity level less than or equal to this value. Default: warning[6] 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.
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. 2. Configure and enable SNMP traps; see Configuring SNMP notification.
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 Vdisk verification has completed. This event or warning 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 60 Informational A disk channel was reset from another initiator or target. 61 Critical A serious error, which might indicate hardware failure, occurred while communicating on the specified disk channel. The controller will attempt to recover. 62 Informational A spare disk has failed.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code Description Recommended action 77 Informational The cache was initialized as a result of power up or failover. 78 Warning 79 Informational The trust vdisk operation has completed successfully. 80 Informational The controller has modified mode parameters on one or more disks. 81 Informational The current controller has unkilled the partner controller. The other controller will restart.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code 88 Description 96 Informational Pending configuration changes that take effect at startup were ignored because customer data might be present in cache. 100 Informational During active-active operation, an event (potential error) occurred while communicating with the EMP, which reports SES data. 101 Informational An update of EMP data has been triggered. This event is for internal use only.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code Description Recommended action 136 Errors detected on the specified disk channel have caused the storage system to mark the channel as degraded. Determine the source of the errors on the specified disk channel and replace the faulty hardware. Warning When the problem is fixed, event 189 is logged. 139 Informational The MC has powered up or restarted. 140 Informational The MC is about to restart.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code Description Recommended action 163 The host WWNs (node and port) previously presented by an offline controller module in this system are unknown. Verify the WWN information for the other controller module on all hosts that access it. Warning This event has two possible causes: • The online controller module reporting the event was replaced or moved while the system was powered off.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code Description Recommended action 173 Informational The specified vdisk has been removed from quarantine. 174 Informational A device firmware update has completed. 175 Informational An Ethernet link has changed status (up/down). 176 Informational The error statistics for the specified disk have been reset. 177 Informational The cache data for a missing volume was purged.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code Description 202 Informational An auto-write-through-trigger condition has been cleared, causing write-back cache to be re-enabled. The environmental change is also logged. (See events 190–200 and 241 and 242.) 203 Warning An environmental change occurred that allows write-back cache to be enabled, but the auto-write-back preference is not set. Recommended action Manually enable write-back cache.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code Description Recommended action 216 Informational The deletion of a batch of snapshots is complete. 217 Critical A super-capacitor failure has occurred on the controller. A service technician must replace the super-capacitor pack on the controller reporting this event. 218 Warning The super-capacitor pack is near end of life.
Table 14 Event code descriptions and recommended actions (continued) Event Event type code Description Recommended action 231 The snap pool has reached the snap pool critical threshold. If the policy is to halt writes, then you must free up space on the snap pool master, or convert the master volume to a standard volume in order to resume operations. Critical The system will take the action set up in the policy. Default is to delete all snapshots on the snap pool.
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 96 Description 265 Informational Port bypass circuits currently use the service port, which may limit the link speed or interconnect mode support. 266 Informational A copy operation for the specified master volume has been aborted. 268 Informational A background copy operation for the specified master volume completed. 269 Informational A partner firmware update operation has started.
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 354 Informational SAS topology has changed on a host port. For example, the SAS cable connecting a controller host port to a host has been disconnected. 355 Warning The faceplate's debug button was found to be stuck in the On position during boot up. 412 Warning One disk in the specified RAID-6 vdisk failed.
As referred to in Table 14, the following table lists power supply module faults and recommended actions. Table 16 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 SMU. • Make sure that no slots are left open for more than 2 minutes.
Event code reference
C Using FTP to download logs and update firmware 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 (not a controller 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 drive 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. SAS disks are dual ported and can be updated from either controller. SATA disks are single ported.
7. If the updated disks must be power cycled: a. Shut down both controllers by accessing the CLI and using the shutdown command. For details, see your product’s CLI reference guide. 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.
Using FTP to download logs and update firmware
Glossary 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.
volume copy Licensed capability to create a copy, or clone, a volume. ULP Unified LUN Presentation. A RAID controller feature that enables a host to access mapped volumes through any controller host port. WWN World Wide Name. A globally unique 64-bit number that identifies a node process or node port. WWNN World Wide Node Name. A globally unique 64-bit number that identifies a node process. WWPN World Wide Port Name. A globally unique 64-bit number that identifies a node port.
Index Symbols browser buttons to avoid 18 setup 17 disks configure SMART 47 configuring background scrub 49 identifying solid-state 38 document conventions 13 prerequisite knowledge 13 related documentation 13 documentation, HP web site 13 dynamic spare 20 dynamic spares configuring 47 C E * (asterisk) in option name 18 A asterisk (*) in option name 18 audience 13 B cache configuring auto-write-through triggers and behaviors 49 configuring host access to 48 cache settings configuring 48 color codes
host adding 65 changing mappings 66 changing name 65 create 109 properties 37 viewing information about 37 host access to cache configuring 48 host mapping properties 38 host ports configuring 46 configuring with Configuration Wizard 41 resetting 67 hosts about 20 removing 65 viewing information about all 37 HP storage web site 14 Subscriber’s choice web site 14 technical support 14 I icon SMU communication status 18 WBI link status 18 L leftover disk 67 licensed features managing 41 snapshot 23 volume co
signing in to SMU 17 signing in to the WBI 17 size representations about 28 SMART configuring 47 SMU about 17 communication status icon 18 signing in 17 snap data 36 snap pool about 23 properties 34 snapshot creating 60 deleting 60 properties 36 resetting to current data in master volume 61 viewing information about 36 snapshot mapping properties 36 snapshots about 23 creating for multiple volumes 59 SNMP configuring traps 79 differences between FA MIB 2.2 and 4.
copying 62 creating 57 expanding 59 properties 34, 35 rolling back data 64 schedule properties 35 setting OpenVMS UID 57 view OpenVMS UID 35 viewing information about 35 volume cache options about 21 volume copy about 24 volume mapping about 21 properties 35 volume masking 21 volume set creating 57 volumes about 20 deleting 58 W WBI about 17 link status icon 18 signing in 17 web sites HP documentation 13 HP storage 14 HP Subscriber’s choice 14 web-browser interface See WBI write-back caching 21 write-throu
