HP StorageWorks 2000 Family Modular Smart Array reference guide Part number: 481599-003 Third edition: August 2008
Legal and notice information © Copyright 2008 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Contents About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2. Configuring Your System for the First Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Configuring Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Configuring User Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 User Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Access Privileges . . . . . . . . . . . . .
Configuring Network Management Services Configuring Event Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Enabling or Disabling Event Notification Configuring Visual Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Configuring Email Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Configuring SNMP Traps .
Managing Global Spares Managing Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Understanding Volumes Adding a Volume Expanding a Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 . . . . . . . . . . . . . . . . . . .
Using Volume-Copy Services Copying a Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Viewing the Status of a Volume Copy Canceling a Volume Copy Using the Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5. Monitoring System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Displaying Status Information Status Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Virtual Disk Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Host Port Status . . . . . . . . . . . . . . .
6. Displaying Notification Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Additional Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Additional Configuration Functions and Utilities Updating Software . . . . . . . . . . . . . . . . . . . . . . . 181 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reviewing Disk Drive Error Statistics Reviewing the Event Logs Reconstructing a Virtual Disk Isolating Data Path Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Isolating Internal Data Path Faults . . . . . . . . . . . . . . . . . . .
Configuring the Debug Log Correcting Enclosure IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Problems After Power-On or Restart A. SNMP Configuration Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 . . . . . . . . . . . . . . . . . .
Comparing RAID Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Mixing Disk Drive Models C. Host Access to Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Node and Port Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 FC D. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 . . . . . . . . . . . . . . . .
About This Guide Intended Audience This guide is intended for use by system administrators who are experienced with the following: ■ Direct attach storage (DAS) or storage area network (SAN) management ■ Network administration ■ Storage system configuration Prerequisites Prerequisites for installing and configuring this product include familiarity with: ■ Servers and computer networks ■ Fibre Channel, iSCSI, Serial Attached SCSI (SAS), and Ethernet protocols Document Conventions Typeface Meaning Exampl
HP Technical Support Telephone numbers for worldwide technical support are listed on the HP support website: http://www.hp.com/support/. Collect the following information before calling: Technical support registration number (if applicable) ■ Product serial numbers ■ Product model names and numbers ■ Applicable error messages ■ Operating system type and revision level ■ Detailed, specific questions ■ For continuous quality improvement, calls may be recorded or monitored.
Subscription Service HP strongly recommends that customers sign up online using the Subscriber's choice website: http://www.hp.com/go/e-updates. Subscribing to this service provides you with e-mail updates on the latest product enhancements, newest versions of drivers, and firmware documentation updates as well as instant access to numerous other product resources. HP Websites For other product information, see the following HP websites: ■ ■ ■ ■ ■ http://www.hp.com http://www.hp.com/go/storage http://www.
HP StorageWorks 2000 Family Modular Smart Array reference guide • August 2008
CH A P T E R 1 Introducing and Using SMU This chapter introduces HP StorageWorks MSA2000 Family Storage Management Utility (SMU), the web-browser interface for MSA2000 Family storage systems. It also describes how to configure this interface by setting system preferences, configuring users, and managing licenses.
SMU also includes monitoring and diagnostic features that enhance the reliability, availability, and serviceability (RAS) of your storage system. You can configure the transmission of event notifications (alerts), which can be sent to the screen or to email addresses, and Simple Network Management Protocol (SNMP) traps, which can be sent to an SNMP application. Events are also recorded in an event log on the storage system from which they can be viewed.
Logging In and Out of SMU SMU distinguishes users by the IP addresses from which they log in. If you log in to SMU using multiple browser instances on the same management host, SMU considers all instances as a single user. Actions you take in one SMU instance are reflected in the other SMU instances on the same host. A controller permits only one browser instance for each management host IP address. Do not log in more than once from the same host.
3. Click Log In. The Status Summary page displays the overall status and health of the system. Note – If you cannot navigate past the Log In page, check the browser settings described on page 18. To log out of SMU: 1. Click Log Off at the bottom of the menu. The Log Off page is displayed. 2. Click Log Off.
Understanding the Interface The topics in this section describe elements of SMU pages and provide help for navigating pages: ■ “Interface Elements” on page 21 ■ “Navigating SMU” on page 23 ■ “Help Bar Icons” on page 24 ■ “Virtual Disk Icons” on page 24 ■ “System Panel” on page 26 ■ “Help Menu” on page 27 ■ “Size Representations in SMU” on page 27 Interface Elements The following figure shows SMU as it would appear for a dual-controller system with one healthy virtual disk and one virtual disk being initial
The following table describes the key elements of SMU pages. Table 1-1 Key Elements of SMU Pages 22 Element Description Menu area This area on each page includes monitoring functions in the Monitor menu, management functions in the Manage menu, and a Log Off function. An arrow icon marks the menu item for the currently displayed page. The type of user that is logged in is displayed beneath the Log Off button. (User types are described in “Access Privileges” on page 32.
Navigating SMU The following table describes how to navigate SMU pages. Table 1-2 SMU Navigation Task Navigation Action Select a menu item Click the menu item in the menu on the left side of each page. When you click some menu items, the menu changes to display different submenus. This book uses the following convention to indicate the steps in navigating to a function: Select Menu > Submenu > Function View more information Click a virtual disk or volume icon or click blue or red text.
Help Bar Icons The Help Bar at the top of each page can include event notification, page refresh, and page help icons. ■ – An event occurred that is configured to display a visual alert. Click this icon to view the most recent events monitored by Event Notification. To control how you receive information about events, see “Configuring Event Notification” on page 53. ■ – The page refreshes automatically when its content changes status.
Table 1-3 Virtual Disk Status Icons (Continued) Icon Description RAID-6 virtual disk is online in a degraded state. The virtual disk can perform I/O functions for data hosts and is fault tolerant, but has degraded performance due to one missing drive. This might indicate that a disk drive has failed in the virtual disk or that the virtual disk is reconstructing. You can use a virtual disk in this state but resolve the problem as soon as possible.
System Panel The System Panel at the bottom of each page includes system information, the overall status of system components, controller information, and the Event Log icon. Figure 1-2 System Panel (FC Example) The following information is shown: ■ System information – The system’s name and location. ■ Overall status – The Virtual Disk category shows the status of virtual disks in the system. The Hardware category shows the status of I/O modules and enclosure components.
Help Menu The Help submenu in the Monitor menu provides the following options for getting online help: ■ Getting Started – Shows information about configuring your browser to use SMU and shows tips for using SMU. ■ Subject Index – Provides an alphabetically ordered list of actions you can perform in SMU. If you have the proper role to perform an action, a link to the associated page is displayed; otherwise, the name of the associated page and the role required to access it are displayed.
HP StorageWorks 2000 Family Modular Smart Array reference guide • August 2008
CH A P T E R 2 Configuring Your System for the First Time This chapter describes how to use SMU to configure your system for the first time.
2. Set the following options: Preference Description Page Refresh Rate Select how often you want pages to refresh based on the speed of your computer and Ethernet connection. • Fast – Use for fast computers with a fast Ethernet connection. For example, Pentium III 500 MHz or higher with a T1 connection. • Medium – Use for slower computers with a slower Ethernet connection. For example, Pentium III 400 MHz and slower with a cable modem or DSL connection.
Configuring User Access By default, the system provides three users that can access the system. In addition to these users, which you can modify, you can add 10 other users (13 maximum). The user configuration function enables you to define user roles by setting specific access privileges. For each user you can set a password and enable or disable access to the following system interfaces: WBI (SMU), CLI (command-line interface), and FTP.
Access Privileges User access privileges are based on the following user types: ■ Standard – Enables access to most functions. ■ Advanced – In addition to enabling Standard functions, enables access to infrequently used administrative functions. ■ Diagnostic – In addition to enabling Standard and Advanced functions, enables access to troubleshooting functions.
Note – For security reasons, create different usernames unique to your site. If you keep the default ones, change their default passwords. 4. Change the user’s password. The password is case sensitive and can include 19 characters. Allowed characters include letters, numbers, hyphens, underscores, and spaces. 5. Change the user’s access level: ■ Monitor enables access to all functions on the Monitor menu. ■ Manage enables access to all functions on the Monitor and Manage menus.
Adding Users SMU allows a maximum of 13 users, including the three default users shown in Table 2-1. To add a user: 1. Select Manage > General Config > User Configuration > Add Users. The Add System User panel displays the current list of configured users. 2. Type a new username. The name is case sensitive and can include 19 characters. Allowed characters include letters, numbers, hyphens, underscores, and spaces. 3. Type a password. The password is case sensitive and can include # characters.
Deleting Users You can delete any user from the system, including the default users. Note – The deletion of a system user cannot be undone. To delete a user: 1. Select Manage > General Config > User Configuration > Delete Users. The System User List panel displays the current list of configured users. 2. Select a user from the Username drop-down list and click Delete User. A confirmation prompt is displayed. 3. Click OK to confirm the operation or Cancel to stop it.
Viewing Installed Licenses To view installed licenses: ● Select Manage > General Config > License Management > Installed Licenses. The Licensed Features Installed panel shows whether a license certificate file is installed and the status of licensed features. For a licensed feature that has a quantity limit, the panel shows the maximum quantity available with the license and the baseline maximum quantity available without a license. ■ Snapshot – Shows whether snapshot services are enabled or disabled.
Setting System Information You can specify information about the system to enable you to identify it. The system name and location are displayed in the System Panel. To set system information: 1. Select Manage > General Config > System Information. The System Information panel is displayed. 2. Type information in each field. Each value can include 74 characters. Allowed characters include letters, numbers, hyphens, underscores, and spaces.
If no NTP server is present, the date and time are maintained as if NTP had not been enabled. To manually set the system date and time: 1. Select Manage > General Config > Set Date/Time. 2. In the Set System Date panel, select the current month, day, and year. 3. In the Set System Time panel, type time values using a 24-hour clock (where hour 8 represents 8 a.m. and hour 20 represents 8 p.m.) and select the proper time zone. For information about time-zone offsets, see http://wikipedia.org. 4.
Configuring Host Ports This section describes how to configure host ports on Fibre Channel (FC) or iSCSI controller modules. No host-port configuration is needed for SAS controller modules. Configuring FC Host Ports On the Host Port Configuration page you can view the location, link speed, and topology of each FC host port in each controller module.
Setting FC Host Port Link Speed A host port’s link speed must match the speed of the host (HBA or switch) to which the port is connected. In a dual-controller system, setting the speed of host port 0 on one controller also sets the speed of host port 1 on the other controller. A speed mismatch with the host prevents the host from accessing the storage system. To set host port link speed: 1. Select Manage > General Config > Host Port Configuration. 2.
■ 0–125 – Select a specific number if you want the loop ID to stay the same after you power down and power up. SMU cannot determine which loop IDs are available. If the controller cannot get the specified loop ID during the loop initialization process, it tries to get a soft address. 4. Click Save And Continue. A message informs you that the new values will be requested the next time the controller is restarted. 5. Click OK. When processing is complete, the main Host Port Configuration page is displayed.
To change the host port interconnect setting: 1. Select Manage > General Config > Host Port Configuration. 2. In the Advanced Options panel, click Change FC Port Interconnect Settings. The Host Port Configuration panel displays the current interconnect setting. 3. Set Internal Host Port Interconnect to Interconnected (enabled) or Straight-through (disabled). The default is Straight-through. This setting affects all host ports on both controllers. 4. Click Save And Continue.
If host port interconnects are enabled, the paired ports are connected in a loop and must be set to use loop topology. Changing the topology setting for one host port automatically changes the setting for the paired port on the partner controller. If host port interconnects are disabled, you can change the topology setting for each host port individually.
Configuring iSCSI Host Ports You can configure the following settings for the iSCSI ports on each MSA2012i controller module. Figure 2-2 Host Port Configuration Settings (Common and Controller A) Settings that are common to all iSCSI ports are: ■ Authentication – Enables or disables use of Challenge-Handshake Authentication Protocol (CHAP). Disabled by default. To set CHAP names and shared secrets, see “Configuring iSCSI Login Authentication” on page 45.
■ ■ iSNS Address – Specifies the IP address of an iSNS server. The default address is all zeroes. Alternate iSNS Address – Optional. Specifies the IP address of an alternate iSNS server, which can be on a different subnet. The default address is all zeroes. Settings that can differ for each port are: ■ IP Address – IP address for a specific port. The system uses port 0 of each controller as one failover pair, and port 1 of each controller as a second failover pair.
On the Manage CHAP page you can create, view, modify, and delete entries. Panels on this page have these icons: ■ Expand panel icon – Click to show the panel’s content. ■ Collapse panel icon – Click to hide the panel’s content. ■ Cancel icon – Click to cancel creating an entry. Creating a CHAP Entry To create a CHAP entry: 1. Select Manage > General Config > Manage CHAP. 2. In the CHAP Entries panel click Add New Entry. The Create CHAP Entry panel is displayed. 3.
Viewing a CHAP Entry To view a CHAP entry: 1. Select Manage > General Config > Manage CHAP. The CHAP Entries panel lists entries by node name. 2. Click the entry to view. The entry’s names and secrets are displayed in the CHAP Entry Details panel. Modifying a CHAP Entry To modify a CHAP entry’s secret or mutual-CHAP values: 1. Select Manage > General Config > Manage CHAP. The CHAP Entries panel lists entries by node name. 2. Click the entry to modify.
Configuring Ethernet Management Ports You can configure addressing parameters for each controller’s Ethernet management port and the timeout value for Telnet sessions. You can also view and configure the SNMP event filter and the web page caching mode. If you accessed SMU for the first time using the default IP address, you should set the IP address for each controller. You can also the change the IP settings as needed.
Using Static IP Settings To set IP values for Ethernet management ports: 1. Select Manage > General Config > LAN Configuration. 2. In the IP Address Assignment panel, set Source For IP Address to Manual. 3. In the IP Configuration panel for each controller, set appropriate values for your network. Use dotted decimal notation. ■ The default IP address is 10.0.0.2 for controller A and 10.0.0.3 for controller B. ■ The default IP subnet mask is 255.255.255.0. ■ The default gateway IP address is 10.0.0.1.
Setting the SNMP Event Table Filter Your storage system supports a Simple Network Management Protocol (SNMP) management information base (MIB) that includes a table of events that have occurred on the system. You can filter the criticality of events that are included in this table. The filter is applied as events are put into the table. Changing the filter does not affect events already recorded in the table; therefore, old events are reported even though they might not meet the current filter criteria.
Setting the Web Page Caching Mode The web page caching mode controls how SMU handles web page names. The names interact with your browser’s caching operations to determine which pages and image files are retrieved. To set the web page caching mode: 1. Select Manage > General Config > LAN Configuration. 2. In the Advanced LAN Options panel, click Advanced Options. 3.
Configuring Network Management Services You can configure network management services and in-band management services to limit the ways in which users and host-based management applications can access the system. If a service is disabled, it continues to run but cannot be accessed. For information about permitting users to use enabled WBI, CLI, or FTP services, see “Configuring User Access” on page 31.
Configuring Event Notification You can configure how and under what conditions the system alerts you when specific events occur. The system generates events having three severity levels: ■ Critical – Something related to the system or to a virtual disk has failed and requires immediate attention. ■ Warning – Something related to the system or to a virtual disk has a problem. Correct the problem as soon as possible.
Enabling or Disabling Event Notification You can enable or disable the following notification methods for selected event categories or individual events: ■ Visual Alerts – SMU shows a visual alert indicator that a notification event has occurred. To see this, SMU must be operating on a management host. ■ Email Alerts – The system sends an email containing the events that have occurred to the designated users. ■ SNMP Traps – The system sends an SNMP trap to the designated trap host.
To select event categories for notification: 1. On the Event Notification Summary page, for each category you want to be notified of, select a notification method. For example, to receive email for all critical events, in the All Critical Events row select only the Email Alerts check box. To receive no notification of informational events, clear all check boxes in the All Informational Events row. 2. Click Change Notification Settings.
3. Select a value for Maximum Events to Display at One Time. SMU can display a maximum of 100 events at a time; the default is 10. For example, if 10 events can display at a time and 15 are pending then the pop-up window shows the first 10 events and clicking the Acknowledge button will show the remaining events and new events that might have occurred. If more than 100 are pending, the oldest ones are dropped. 4. Enable or disable visual notification. The default is Enable. 5.
2. Type values in the following fields: ■ Email Address 1–4 – Email addresses that the system should send notifications to. Email addresses must use the format user-name@domain-name. ■ Email Comment – Text to send with email messages. For example, you might want to identify the location, name, or use of the system. ■ Mail Server – The IP address of the SMTP mail server to use for the email messages.
Configuring SNMP Traps You can configure the following options for SNMP notification of events: ■ Read and write community strings ■ IP addresses of hosts that are configured to receive SNMP traps To configure SNMP traps: 1. Select Manage > Event Notification > SNMP Configuration. 2. Type values in the following fields: ■ SNMP Read Community – The SNMP read password for your network. The value is case sensitive and can include 15 characters. The default is public.
The disadvantage of ICPM is that if a controller fails, the other controller cannot fail over (that is, take over I/O processing for the failed controller). If a controller fails, the host loses access to the volumes owned by that controller. If a controller experienced a complete hardware failure, and needed to be replaced, then user data in its write-back cache is lost.
Saving the Configuration to a File As an Advanced Manage user, you can save the storage system’s configuration settings to a file. This enables you to make a backup of your settings in case a subsequent configuration change causes a problem, or if you want to apply one system’s settings to another system. For information on restoring configuration data, see “Restoring a Saved Configuration File” on page 187.
Restarting and Shutting Down a Controller You can restart or shut down controllers when a controller is not working properly or when the system will be serviced or moved.
Shutting Down a Controller Shut down a controller module before you remove it from an enclosure, or before you power off its enclosure for maintenance, repair, or a move. Shutting down a controller module halts I/O to that module, ensures that any data in the write cache is written to disk, and initiates failover to the partner controller, if it is active. Caution – If you shut down both controller modules, you lose access to SMU, CLI, and FTP and users lose access to data.
CH A P T E R 3 Managing Storage This chapter describes how to use SMU to configure and manage virtual disks, spare disks, volumes, volume-to-host mappings, and to use volume snapshot features.
The following table specifies the minimum and maximum numbers of disk drives supported for each RAID level. For more information about RAID levels, see Appendix B. Table 3-1 Number of Disk Drives Supported for Each RAID Level RAID Level Min. Drives Max. Drives Non-RAID 1 1 0 2 16 1 2 2 3 3 16 5 3 16 6 4 16 10 4 16 RAID 10 must have the same, even number of drives in each sub-vdisk. Each sub-vdisk can have 2–8 drives.
You can create a virtual disk automatically or manually: ■ Automatic Virtual Disk Creation (Policy-based) creates a virtual disk based on minimal information. See “Creating a Virtual Disk Automatically” on page 65. ■ Manual Virtual Disk Creation (Detail-based) creates a virtual disk based on parameters you select, which provides greater control over the configuration than Automatic Virtual Disk Creation. See “Creating a Virtual Disk Manually” on page 67.
5. Set Minimum Size Of Virtual disk to the amount of available space to use for all volumes on the new virtual disk. This value is rounded to the nearest Gbyte and is shown to the right of this field as Targeted Virtual Disk Size. Because SMU allocates entire drives to virtual disks, the resulting virtual disk is typically larger than the requested size; capacity beyond that allocated to volumes is designated as free space.
Creating a Virtual Disk Manually To create a virtual disk manually: 1. Select Manage > Virtual Disk Config > Create A Vdisk. 2. Select Manual Virtual Disk Creation. 3. Type a name for the virtual disk. The name is case sensitive and can include 17 characters, but not comma, quotation mark ("), or backslash. 4.
7. Select the drives to use in the virtual disk. Only available drives are selectable. Available drives are neither in a virtual disk nor assigned as a spare. The minimum and maximum number of drives that you can select when creating a virtual disk are shown in Table 3-1. In a multi-enclosure system, for certain RAID levels you can select drives in a way that provides some protection against enclosure failure: ■ RAID 1, 3, 5, or 6 – Select each drive from a different enclosure.
d. Click Continue. The Configure Volumes For Virtual Disk page is displayed and summarizes your selections. 10. (Optional) Set How Many Volumes to the number of standard volumes you want in your virtual disk. You can create a virtual disk that has no volumes (the default), one volume, or multiple volumes (online initialization only). If you choose to create no volumes, you can later add standard volumes or volumes of other types. 11.
13. Click Create Virtual Disk. The system creates the virtual disk and shows the next page in the process. ■ If you accepted the default volume options, the final page shows the progress of virtual disk initialization. Proceed to “Virtual Disk Initialization” on page 70. ■ If you changed any of the volume options, an Add Volumes To Virtual Disk page is displayed showing information based on your selections from the previous page. Continue with Step 14. 14.
Managing Virtual Disks SMU enables you to manage virtual disks in a variety of ways. You can: ■ View the status of virtual disks and disk drives ■ Expand virtual disk capacity ■ Removing a virtual disk from quarantine ■ Verify a virtual disk ■ Change a virtual disk’s owner ■ Change a virtual disk’s name ■ Delete a virtual disk For information about reconstructing a failed virtual disk, see “Troubleshooting Using SMU” on page 195.
Critical – Either the virtual disk is being initialized or reconstructed; or, one drive is down or missing in a RAID 1, 3, 5, 10, or 50 virtual disk; or, two drives are down in a RAID 6 virtual disk. ■ Offline – The virtual disk has an unrecoverable error, and data is lost. ■ Quarantined – One or more drives in the virtual disk were not detected after a restart or rescan.
Disk Drive Status To view information about the drives in a virtual disk: 1. Select Manage > Virtual Disk Config > Vdisk Configuration > Disk Drive Status. For each virtual disk, the virtual disk panel shows a status icon; the name, RAID level, size, number of disk drives, and number of volumes; and utility status, if any. 2. Select a virtual disk.
Expanding Virtual Disk Capacity You can expand the capacity of a virtual disk by adding drives to it. Because virtual disk expansion does not require I/O to be quiesced, the virtual disk can continue to be used while the Expand utility runs. Expanding a virtual disk adds free space after the space used by existing volumes. You can then create or expand a volume to use the free space. You can expand only one virtual disk at a time.
4. Click Expand Virtual Disk. Expansion begins and the percentage completed is shown. You can perform other functions during the expansion. You can view the status of the expansion on the Vdisk Utility Progress page or on any page that shows virtual disk icons. Checking the Progress of a Utility To check the status of any running virtual disk utilities: ● Select Manage > Virtual Disk Config > Vdisk Utility Progress.
The quarantined virtual disk’s drives are “write locked,” and the virtual disk is not available to hosts until the virtual disk is removed from quarantine. The system waits indefinitely for the missing drives. If the drives are found, the system automatically removes the virtual disk from quarantine. If the drives are never found because they have been removed or have failed, you must manually remove the virtual disk from quarantine.
The verification process checks whether the redundancy data in the virtual disk is consistent with the user data in the virtual disk. The number of inconsistencies found is noted in the “Vdisk verification complete” event (event code 21) in the event log. Such inconsistencies can indicate that a drive in the virtual disk is going bad. For information about identifying a failing drive, see “Enabling or Disabling SMART Changes” on page 137.
Changing Virtual Disk Ownership Each virtual disk is owned by one of the controllers. SMU balances the number of virtual disks each controller owns. In a dual-controller system, when a controller fails, the partner controller assumes temporary ownership of the failed controller’s virtual disks and resources. If the system uses a fault-tolerant cabling configuration, both controllers’ LUNs will be accessible through the partner. Typically, you should not need to change virtual disk ownership.
Changing a Virtual Disk Name To change the name of a virtual disk: 1. Select Manage > Virtual Disk Config > Vdisk Configuration > Change Vdisk Name. For each virtual disk, the virtual disk panel shows a status icon; the name, RAID level, size, number of disk drives, and number of volumes; and utility status, if any. 2. In the Change Virtual Disk Name field, type a new name. The name is case sensitive and can include 17 characters, but not comma, quotation mark ("), or backslash. 3.
Managing Spares Controllers in your system automatically reconstruct redundant (fault-tolerant) virtual disks (RAID 1, 3, 5, 6, 10, and 50) if a virtual disk becomes critical and a properly sized spare disk is available. A virtual disk becomes critical when one or more of its disks fails. There are three types of spares: ■ A vdisk spare is an available drive that is assigned to a specific virtual disk.
To configure dynamic spares: 1. Select Manage > General Config > System Configuration. 2. Set Dynamic Spare Configuration to Enabled. 3. Click Change System Configuration. When Dynamic Spare Configuration is enabled, the Dynamic Spare Rescan Rate option is displayed. Use the default rescan rate. 4. Click Change System Configuration. Managing Vdisk Spares This section describes how to designate available drives as spares for use by one virtual disk only.
To add spares to a virtual disk: 1. Select Manage > Virtual Disk Config > Vdisk Configuration > Add Vdisk Spares. For each virtual disk, the virtual disk panel shows a status icon; the name, RAID level, size, number of disk drives, and number of volumes; and utility status, if any. 2. Select a virtual disk. 3. In the Select Drives To Be Vdisk Spares panel, select drives to be spares for the selected virtual disk. Only appropriate drives are selectable. 4. Click Add Vdisk Spares.
Managing Global Spares This section describes how to designate available drives as spares for use by any virtual disk. It also describes how to return spares to the pool of available drives. Adding Global Spares You can designate a maximum of eight global spares for the system. If a disk in any redundant virtual disk (RAID 1, 3, 5, 6, 10, and 50) fails, a global spare is automatically used to reconstruct the virtual disk. At least one virtual disk must exist before you can add a global spare.
Displaying Global Spares To display global spares: ● Select Manage > Virtual Disk Config > Global Spare Menu > Show Global Spares. Drives whose icons are gray with a “G” are global spares. Managing Volumes SMU lets you manage volumes in a variety of ways.
You can give each volume a name. Assign names that indicate how the volumes are to be used. For example, if the first volume will be used to store your customer database, give it a name such as: cust_database. When you create a virtual disk, you can specify the number of volumes you want and their sizes. If the total size of the volume or volumes equals the size of the virtual disk, you will not have any free space, as shown in Figure 3-1.
Adding a Volume You must have free space in a virtual disk before you can add a volume. You can create free space by deleting a volume (see “Deleting a Volume” on page 93) or by expanding the virtual disk (see “Expanding Virtual Disk Capacity” on page 74). You can add volumes to a virtual disk until you use all of the free space. To add a volume: 1. Select Manage > Volume Management > Volume Menu > Add Volume.
Expanding a Volume You can expand a standard volume or a snap pool if the virtual disk has free space and sufficient resources. Because volume expansion does not require I/O to be quiesced, the volume can continue to be used while it is expanded. To expand a volume: 1. Select Manage > Volume Management > Volume Menu > Expand Volume. For each virtual disk, the virtual disk panel shows a status icon; the name, RAID level, size, number of disk drives, and number of volumes; and utility status, if any. 2.
On Volume Management pages, the Volume Menu panel shows a color-coded “map” of the space used by each volume in the selected virtual disk. The color codes are: ■ Gray – Free space ■ Green – Standard volume ■ Blue – Snap pool ■ Orange – Master volume ■ Yellow – Snapshot The panel also shows a table with information about each volume and the amount of free space. The information that is shown varies, depending on the page.
3. Select the volume to rename. 4. In the Change Volume Name field, type a new name. The name is case sensitive and can include 20 characters, but not comma, quotation mark ("), or backslash. 5. Click Change Volume Name. When processing is complete, the new name is displayed in the Volume Menu panel. Changing a Volume’s Read-Ahead Cache Settings As an Advanced Manage user, you can optimize a volume for sequential reads or streaming data by changing its read-ahead cache settings.
3. Select the standard, snap-pool, or master volume whose cache settings you want to change. 4. Set Read Ahead Size to one of the following options: ■ Default – Sets one chunk for the first access in a sequential read and one stripe for all subsequent accesses. The size of the chunk is based on the chunk size used when you created the virtual disk (the default is 64 KB). Non-RAID and RAID 1 virtual disks are considered to have a stripe size of 64 KB. ■ Disabled – Turns off read-ahead cache.
Changing a Volume’s Write-Back Cache Setting As an Advanced Manage user, you can change a volume’s write-back cache setting. Write-back is a cache-writing strategy in which the controller receives the data to be written to disk, stores it in the memory buffer, and immediately sends the host operating system a signal that the write operation is complete, without waiting until the data is actually written to the disk drive.
To change a volume’s write-back cache setting: 1. Select Manage > Volume Management > Volume Menu > Write Back Cache. For each virtual disk, the virtual disk panel shows a status icon; the name, RAID level, size, number of disk drives, and number of volumes; and utility status, if any. 2. Select a virtual disk. The selected virtual disk’s volume names, sizes, and write-back cache settings are displayed, and the amount of free space. 3.
■ ■ ■ Power Supply Failure Trigger – Changes to write-through if a power supply unit fails. The default is Disabled. Fan Failure Trigger – Changes to write-through if a cooling fan fails. The default is Disabled. Overtemp Failure Trigger – Forces a controller shutdown if a temperature is detected that exceeds system threshold limits. The default is Disabled. 4.
5. Click OK to confirm the operation or Cancel to stop it. If you clicked OK, a message indicates whether the operation succeeded. If it succeeded, the volume is removed from the Volume Menu panel. Managing Host Access to Volumes Each volume has default host-access settings that were set when the volume was created; these settings are called the default mapping. The default mapping applies to any host that has not been explicitly mapped with different settings.
Managing the Global Host List The following topics describe managing the host list on an FC, SAS, or iSCSI storage system. Managing the Global Host List on an FC System The global host list is a list of ports on a host HBA or FC switch that can be used for volume mapping. The list is automatically populated with port WWNs of hosts that have sent an inquiry command or a report luns command to the system. Hosts typically do this when they boot up or rescan for devices.
2. Click Add New Port. If the WWN and nickname are not in the list, the port is added. If the WWN is in the list, the nickname is changed. If the nickname is in the list, you must specify a unique nickname. To delete either a manually added port or the nickname of an automatically added port: ● In the host port’s row, click Delete. If the host scanned for devices since the storage system was restarted, restart the system to complete the deletion.
To add a port or change a port’s nickname: 1. In the Add Port To Global Host Port List panel, type the port WWN and a nickname. The name is case sensitive and can include 15 characters, but not comma, quotation mark ("), or backslash. 2. Click Add New Port. If the WWN and nickname are not in the list, the port is added. If the WWN is in the list, the nickname is changed. If the nickname is in the list, you must specify a unique nickname.
To display the global host list: ● Select Manage > General Config > Manage Host List. The Global Host List panel shows the node name, any controller ID and port numbers through which the host has logged in, and the nickname (if any) for each host node. To change a host node’s nickname: 1. Type a new nickname in the node’s Nickname field. The name is case sensitive and can include 15 characters, but not comma, quotation mark ("), or backslash. 2. Click Update. To add a host node: 1.
Managing Volume Mappings In the Map Hosts To Volume page you can add, change, or delete explicit mappings between volumes and hosts. Managing Volume Mappings on an FC System 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 manage host-to-volume mappings: 1. Select Manage > Volume Management > Volume Mapping > Map Hosts To Volume.
b. To set read-write or read-only access on one or more ports, specify a LUN and select port access privileges. More than one host can use the same LUN to access the same volume. A mapping cannot include both read-write and read-only access. c. Click Map It. When processing is complete, the page shows the mapping changes. 5. To add or change an explicit mapping for the selected volume: a. In the Assign Host Access Privileges panel, select a host. b.
3. Select a volume. The Current Host-Volume Relationships panel shows which host nodes have access to the selected volume. For the selected volume you might see the following mappings: ■ All Hosts – Shows the settings used by all host nodes to access the volume. This entry is displayed only if no host nodes are explicitly mapped. If a host node is explicitly mapped, All Hosts changes to All Other Hosts. ■ IQN-value – Shows an explicit mapping between a host node and the volume.
6. To remove an explicit mapping: a. In the Assign Host Access Privileges panel, select a host node. b. Click Unmap It. When processing is complete, the mapping is removed from the page. Managing Volume Mappings on a SAS System 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 manage host-to-volume mappings: 1.
b. To set read-write or read-only access on one or more ports, specify a LUN and select the access privilege and ports. More than one host can use the same LUN to access the same volume. If a port is not selected, its access is automatically set to none. c. Click Map It. When processing is complete, the page shows the mapping changes. 5. To add or change an explicit mapping for the selected volume: a. In the Add Or Modify A Mapping panel, select a host. b. Click Map It.
Using Snapshot Services Snapshot services provide data protection by enabling you to create and save snapshots of a volume, where each snapshot preserves the volume’s data state at the point in time when the snapshot was created. Snapshots can be taken of master volumes only. A master volume is a volume that has been enabled for snapshots. You can either create a master volume directly or convert a standard volume to a master volume.
The snapshot service uses the single copy-on-write function to capture only data that has changed. That is, if a block is to be overwritten on the master volume, and a snapshot depends on the existing data in the block being overwritten, the data is copied from the master volume to the snap pool before the data is changed. All snapshots that depend on the older data are able to access it from the same location on the snap pool; this reduces the impact of snapshots on master volume writes.
How much modified (write) data will the snapshots have? Of the snapshots that will be mounted as read-write and actually written to, factor in the average amount of data that will be modified. Add 750 Mbyte of reserve space for internal use. Add a recommended 25% safety margin to the snap pool in case actual capacity use exceeds the estimate. ■ ■ ■ You can estimate snap-pool size as shown in following example.
Reverting to Original Data The snapshot service has two features for reverting data back to original data: ■ Deleting only modified data on a snapshot ■ Rolling back the data in a master volume 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 application test, for example.
MasterVolume-1 Snapshot-1 Preserved Data (Wed Jan 18 22:37:17 2006) Modified Data (Thur Jan 22 21:20:30 2006) 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.
Creating a Snap Pool Before you can convert a standard volume to a master volume or create a master volume for snapshots, a snap pool must exist. A snap pool and its associated master volumes can be in different virtual disks, but must be owned by the same controller. You can create a maximum of 16 snap pools. To create a snap-pool volume: 1. Select Manage > Volume Management > Snapshot Services > Create Snap-Pool.
Setting Snap Pool Policies and Thresholds Each snap pool has three policy levels that notify you when the snap pool is reaching decreasing capacity. Each policy level has an associated policy that specifies system behavior when an associated threshold value is reached. The following table summarizes the default thresholds and policies. You can set the Warning and Error thresholds and the Error and Critical policies. Policy Level Threshold Policy Warning 75% Notify Only.
To set a snap pool’s policies and thresholds: 1. Select Manage > Volume Management > Snapshot Services > Set Snap-Pool Policy. For each virtual disk, the virtual disk panel shows a status icon; the name, RAID level, size, number of disk drives, and number of volumes; and utility status, if any. 2. Select a virtual disk. The selected virtual disk’s volume names, sizes, and types are displayed, and the amount of free space. 3. Select the snap pool to configure. 4. Set the Warning Policy threshold.
■ ■ Halt Writes – Halts all writes to the master volume (each write returns an error). Snapshot data is preserved. Delete Oldest Snapshots – Deletes the oldest snapshots until the amount of data in the snap pool is below the threshold. 7. Click Set Policy & Threshold. The changes take effect immediately. Creating a Master Volume You can take snapshots of a snapshot-enabled volume (a master volume). A maximum of 16 master volumes can exist and they all can be associated with a single snap pool.
5. (Optional) Change the name for the new volume. The default name is vdisk-name_Vnumber. For example, MyVdisk_V1. The name is case sensitive and can include 20 characters, but not comma, quotation mark ("), or backslash. Note – If the default name exceeds 20 characters it will be truncated. 6. (Optional) Change the LUN setting. ■ NONE – The volume is not accessible by connected hosts. This setting is the default. You can map the volume to hosts later; see “Managing Volume Mappings” on page 99.
5. Click Convert To Master Volume. When processing is complete, the volume type is updated in the Volume Menu panel. Taking a Snapshot You can take a snapshot of the data state of a selected master volume. The snapshot data is stored in the snap pool associated with the master volume. To take a snapshot: 1. Select Manage > Volume Management > Snapshot Services > Take Snapshot.
Resetting a Snapshot You can reset a snapshot to replace its content with the current data state of the associated master volume. The selected snapshot is replaced with a current snapshot having the same characteristics, such as name and LUN. The snapshot data is stored in the snap pool associated with the master volume. Before being reset, a snapshot must be unmounted from hosts. Caution – Before resetting a snapshot you must unmount it from data hosts to avoid data corruption. To reset a snapshot: 1.
Caution – Before deleting modified data you must unmount the snapshot from data hosts to avoid data corruption. To delete the modified (write) data from a snapshot: 1. Unmount the snapshot from hosts. 2. Select Manage > Volume Management > Snapshot Services > Delete Modified Data. For each virtual disk, the virtual disk panel shows a status icon; the name, RAID level, size, number of disk drives, and number of volumes; and utility status, if any. 3. Select a virtual disk.
Only one rollback is allowed on the same master volume at one time. Multiple rollbacks on subsequent volumes on the same snap pool are performed sequentially; that is, additional rollbacks are queued until the current rollback is complete. However, after the rollback is requested, the master volume is available for use as if the rollback has already completed. To rollback a master volume: 1. Unmount the master volume from hosts. 2.
Deleting a Snapshot You can delete snapshots at any time, including when: ■ The associated snap pool is reaching capacity and you want to free some space ■ The maximum number of snapshots is reached and you want to delete older snapshots ■ You no longer need the data associated with the snapshot To delete a snapshot: 1. Unmount the snapshot from hosts. 2. Select Manage > Volume Management > Snapshot Services > Delete Snapshot.
3. Select a volume. The Volume Information panel shows the following information, depending on the type of volume selected. Volume Type Field Description (All) Volume Type (not shown for standard volumes) One of the following volume types: Master – A standard volume that is enabled for snapshots and is associated with a snap pool. Snap Pool – A virtual volume in which snapshots of the associated master volume are stored.
Volume Type Field Description Master Volume Status Indicates whether the snapshot is Available or Unavailable. Status Reason Shows the reason for Unavailable status: • MV Not Ready (master volume is not ready) • SP Not Ready (snap pool is not ready) • SP Not Found (snap pool is not found) • Unknown Associated Snap Pool The name of the associated snap pool. Number of Snapshots of Volume The number of existing snapshots. Snapshot Data Size Total size of stored snapshots.
Volume Type Field Description Snap Data – The total amount of data associated with the specific snapshot (data copied from a master volume to a snapshot and data written directly to a snapshot). Unique Data – The amount of data that has been written to the snapshot since the last snapshot was taken. If the snapshot has not been written or is deleted, this field will show a value of 0.
Volume Copy from a Master Volume Master Volume Transient Snapshot Data Transfer New Volume 1. Volume copy request is made with a master volume as the source. 2. A new volume is created for the volume copy, and a hidden, transient snapshot is created. 3. Data is transferred from the transient snapshot to the new volume. 4.
Some guidelines to keep in mind when performing a volume copy include: ■ The virtual disk selected for the volume copy must be on the same controller. ■ The virtual disk selected for the volume copy must have free space that is at least as large as the mount of space allocated to the original volume. A new volume will be created using this free space for the volume copy.
Copying a Volume You can copy a master volume or a snapshot to a new standard volume. The volume-copy operation takes a snapshot of all data in the source volume and creates a destination volume that you specify. The destination volume must be in a virtual disk owned by the same controller as the source volume. Caution – To avoid data corruption in the destination volume, prepare for the copy operation as described in Step 1. To copy a volume: 1.
6. If the source volume is a snapshot, select whether the copy should include or exclude data modified in the snapshot since it was taken. The default is Exclude, which means that the copy will contain only the data that existed when the snapshot was taken. 7. Click Volume Copy. The copy operation starts. While the operation is in progress, the destination volume is offline and its type is shown as Standard*. ■ If you unmounted a master volume to copy, you can remount it now.
■ ■ ■ ■ ■ ■ Volume is presented to all hosts not explicitly mapped – Specifies whether the volume is visible to all connected hosts. If the value is Yes, the LUN is also shown. Volume Serial Number – Serial number of the volume being created. Source Volume Name – Name of the volume being copied. Percent Complete – Percent complete of the volume copy. Volume Copy Status – Indicates whether the destination volume is Unavailable or Suspended.
Using the Scheduler You can use the Scheduler feature to create tasks and define schedules at which the system will automatically perform those tasks. Actions you can perform on the Scheduler page are: ■ Create tasks to take a snapshot, reset a snapshot, or copy a volume ■ View task information ■ Delete tasks ■ Schedule tasks ■ View schedule information ■ Delete schedules Panels on this page have these icons: ■ – Click to show the panel’s content. ■ – Click to hide the panel’s content.
3. Select Take Snapshot. 4. Select a master volume to take snapshots of. 5. Specify a prefix to identify snapshots created by this task. The prefix is case sensitive and can include 14 characters, but not comma, quotation mark ("), or backslash. Automatically created snapshots are named prefix_Sxxxx, where xxxx increments from 0001 to 9999 before rolling over. 6. Specify the number of snapshots with this prefix to retain. The default and minimum value is 1. Your license determines the maximum value. 7.
5. Specify a name for the task. The name is case sensitive and can include 32 characters. Allowed characters include letters, numbers, hyphens, underscores, and spaces. 6. Click Create Task. The Tasks panel is updated and task information is displayed in the Task Details panel. Creating a Volume Copy Task If an installed license enables this feature, you can copy a snapshot or a master volume to a new standard volume.
9. Click Create Task. The Tasks panel is updated and task information is displayed in the Task Details panel. Viewing Task Information To view information about existing tasks: 1. Select Manage > Scheduler > Manage Scheduler. The Tasks panel shows the name, type, and status of existing tasks. If a task fails, an error icon is displayed and the task type and status are shown in red. The task remains in the current state until an associated schedule initializes the task to run again.
■ ■ ■ Include modified data Last copy created, if the task has run Error message, if any Deleting a Task You can delete an unscheduled task. If the task is scheduled, you must delete the schedule first. To delete a task: 1. Select Manage > Scheduler > Manage Scheduler. 2. In the Tasks panel click a task name. 3. In the Task Details panel, click Delete Task. 4. Click OK to confirm the operation or Cancel to stop it. Creating a Schedule To schedule a task: 1. Select Manage > Scheduler > Manage Scheduler.
■ ■ ■ Only On – Specifies days when the task should run. You can select a combination of: any day or a day by number; a day by type or name; and all months or a month by name. For the day number, the Specific option uses a number you type in an adjacent field. Repeat – Specifies the number of times the task should run, including the first time. Expires On – Specifies the date and time when the task should stop running. 6. Select a task to schedule. 7. Specify a name for the schedule.
Deleting a Schedule To delete a schedule: 1. Select Manage > Scheduler > Manage Scheduler. 2. In the Schedules panel click a schedule name. 3. In the Schedule Details panel, click Delete Schedule. 4. Click OK to confirm the operation or Cancel to stop it.
HP StorageWorks 2000 Family Modular Smart Array reference guide • August 2008
CH A P T E R 4 Managing Disk Drives and Enclosures This chapter describes how to use SMU to manage a system’s disk drives and enclosures. Topics covered in this chapter are: ■ “Managing Disk Drives” on page 135 ■ “Managing Enclosures” on page 142 Managing Disk Drives SMU provides a variety of functions related to disk drives.
Viewing Disk Drive Status To view the status of the drives in a selected virtual disk: ● Select Manage > Virtual Disk Config > Vdisk Configuration > Disk Drive Status. For a description of the information contained on this page, see “Disk Drive Status” on page 73. Note – If a disk drive has failed or malfunctioned, it might not be listed. Clearing Metadata From Leftover Disk Drives The storage system uses metadata to identify virtual disk members after restarting or replacing enclosures.
Enabling or Disabling SMART Changes As an Advanced Manage user, you can configure the ability to change the SelfMonitoring Analysis and Reporting Technology (SMART) settings for all disk drives in the storage system. When SMART is enabled, SMART events are recorded in the event log and are counted on the Disk Error Stats page. This information enables you to monitor your disk drives or analyze why a disk drive failed. For more information about the event log, see “Viewing the Event Log” on page 171.
Viewing Disk Drive Read-Cache Status To view a disk drive’s read-cache status: 1. Select Manage > Utilities > Disk Drive Utilities > Display Disk Cache. The page shows the enclosure view with a drive selected, and shows the drive’s read-cache status. The first drive in the enclosure is selected by default. 2. Select a drive. 3. Click Show Disk Drive Cache Status. Illuminating a Drive Module LED You can illuminate a drive module LED to help you visually locate the drive in its enclosure.
Viewing Disk Drive Types and Firmware Versions To view the firmware version (revision) and type of each disk drive in each enclosure connected to the system, do either of the following: ● Select Manage > Update Software > Disk Drive Firmware > Show Disk Drives. The page shows similar information to the Disk Drive List page; see “Disk Drive List” on page 155. However, instead of the Encl.
3. Ensure that no other user is performing administrative functions on the storage system. 4. Verify that background scrub is disabled. “Enabling and Disabling Background Scrub for Disks” on page 189. 5. Back up the data for the virtual disk that the drive is part of. 6. Stop host I/O by either disconnecting data cables from the storage system controllers or powering down all hosts connected to the system. To update disk drive firmware: 1.
6. Click Browse to select the firmware update file. 7. Click Load Device Firmware File. 8. To start the firmware update, click Start Firmware Update. To cancel the firmware update, click Cancel. The file is transferred to the controller where it is temporarily stored prior to download to the disk drives. Once the firmware update process has started, the Drive Firmware Loading Progress page provides the update progress of each disk drive, including when the firmware update completes successfully.
Managing Enclosures Each controller module and expansion module contains an Expander Controller (EC). The storage system can query EC for information about enclosure environmental conditions such as temperature, power supply and fan status, and the presence or absence of disk drives. The system can also communicate information to the EC about RAID activities such as disk drive rebuilds and failed disk drives. The EC is also referred to as the enclosure management processor (EMP).
Viewing Enclosure Details To view enclosure details: 1. Select Manage > General Config > Enclosure Management. 2. Pause your cursor over an enclosure icon. A pop-up shows the enclosure status and other details. Entering Enclosure Information To enter the name, location, rack number, and rack position for an enclosure: 1. Select Manage > General Config > Enclosure Management. 2. If there is more than one enclosure, select the enclosure for which you want to enter information. 3.
Illuminating Enclosure LEDs To illuminate an enclosure LED to help you visually locate the enclosure: 1. Select Manage > General Config > Enclosure Management. 2. If there is more than one enclosure, select the enclosure to locate. 3. Click Illuminate Locator LED. To stop illuminating an enclosure LED: 1. Select the enclosure. 2. Click Turn Off Locator LED. Changing the Enclosure Polling Rate You can change the interval at which the storage system polls the EC (EMP) for status changes.
Correcting Enclosure IDs Rescan forces rediscovery of attached disk drives and enclosures. If both Storage Controllers are online, it also forces re-evaluation of the enclosure IDs of attached drive enclosures, so that IDs are assigned 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 is not required to detect when drives are inserted or removed; the controllers do this automatically.
■ Total Number of this Type – The number of expansion modules that have the same vendor, model, and firmware revision. For example, two identical expansion modules with different firmware revisions are considered to be different types. If firmware update is not supported for an expansion module type, the Select column shows “Not Supported” for that type and you cannot continue the firmware update process.
8. Click Load Device Firmware File. 9. To start the firmware update, click Start Firmware Update. To cancel the firmware update, click Cancel. The file is transferred to the RAID controller where it is temporarily stored prior to download to the enclosure. Once the firmware update process has started, a page shows the update progress of each enclosure, including when the firmware update has completed successfully. This operation can take several minutes to complete.
HP StorageWorks 2000 Family Modular Smart Array reference guide • August 2008
CH A P T E R 5 Monitoring System Status This chapter describes how to use SMU to monitor your system to ensure that its components are working properly.
To display the Status Summary page from another SMU page: ● Select Monitor > Status > Status Summary. Virtual Disk Status You can view detailed information about a virtual disk’s status, including its disk drives and volumes. You can display virtual disk status information in two ways. To view virtual disk (vdisk) status from the menu: ● Select Monitor > Status > Vdisk Status. To view virtual disk status from another page’s Virtual Disk Overview panel: ● Click the virtual disk’s icon.
■ ■ ■ ■ ■ ■ ■ ■ ■ Number Of Spares – Number of spares assigned to the virtual disk. Number Of Volumes – Number of volumes in the virtual disk. Virtual Disk Name – Name assigned to the virtual disk. Virtual Disk Serial Number – Unique number assigned by the owning controller. Preferred Owner – Controller that owns the virtual disk during normal operation. Current Owner – Either the preferred owner during normal operation or the partner controller when the preferred owner is offline.
Host Port Status This section describes status information shown for host ports on Fibre Channel (FC), iSCSI, or SAS controller modules. FC Host Port Status The Host Port Status page shows a graphical representation of the host ports on each controller, including a color-coded status for each port. Figure 5-1 FC Host Port Status Example To display host port status information: 1. Select Monitor > Status > Advanced Settings > Host Port Status.
■ Topology – One of the following values: ■ Point-to-Point ■ Loop, if the loop is inactive ■ Private Loop, if the port is directly attached to a host ■ Public Loop, if the port is attached to a switch To change this setting, see “Setting FC Host Port Topology” on page 42. ■ ■ ■ ■ ■ Speed – 2 Gbit/sec or 4 Gbit/sec. To change this setting, see “Setting FC Host Port Link Speed” on page 40. FC Address – 24-bit FC address, or Unavailable if the FC link is not active.
Details in the lower part of the panel vary depending on the selected port's status.
Details in the lower part of the panel vary depending on the selected port’s status. ■ Topology – Port connection type. ■ Speed – Actual link speed in Gbit per second per PHY lane. ■ Number of Active Lanes - The number of active PHY lanes and the number of lanes in the port. ■ Port WWN – Port World Wide Name. ■ Health – Port status: ■ Healthy – All PHY lanes are active in the port. ■ Degraded – At least one PHY lane is inactive in the port.
■ ■ Belongs To Virtual Disk – Different information depending on the drive’s status: ■ If used in a virtual disk, the virtual disk name. ■ If used as a spare, the type of spare. ■ If unused, Available. ■ If contains leftover metadata, Leftover. A Manage user can return leftover drives to available status; see “Clearing Metadata From Leftover Disk Drives” on page 136. Enclosure Name – Name of the enclosure containing the drive.
■ ■ ■ Model – Enclosure model number Version – Expander Controller software version WWN – Enclosure node World Wide Name For a drive the following information is displayed. ■ Drive Status – Up if operational or Down if failed. ■ Encl – Number of the enclosure containing the drive. ■ Slot – Number of the drive slot in the enclosure. ■ Mfr – Drive manufacturer. ■ Model – Drive model number. ■ Size – Drive size in Gbyte. ■ Type – Drive architecture (SATA or SAS). ■ Serial # – Drive serial number.
LAN Information You can view Ethernet and IP information for each controller, and information about the system. To change the LAN settings, see “Configuring Ethernet Management Ports” on page 48. To change the system information, see “Setting System Information” on page 37. To view LAN information: ● Select Monitor > Status > Advanced Settings > LAN Information.
Module Status You can view summary status information for each controller module and all enclosures in the storage system. More detail is available on other Monitor pages. To view module status: ● Select Monitor > Status > Module Status. The Rear Panel Chassis View shows the back of the controller enclosure and the current status of power-and-cooling modules and controller modules. Failed modules are displayed in red.
The status is OK when there are no critical or warning conditions for the element type. If no enclosure polling data is available, a message is displayed stating this. For information about a critical or warning condition, view the event log; see “Viewing the Event Log” on page 171. Controller Versions You can view the software, hardware, and other version information for each controller module. During normal operation, all software versions should be the same on both controller modules.
FRU Information You can view information about field-replaceable units (FRUs) other than drive modules in an enclosure. For information about installed drive modules, see “Disk Drive List” on page 155. To view FRU information: 1. Select Monitor > Status > Advanced Settings > FRU Information. The drive enclosure panel shows all enclosures in the system and the status of each enclosure. 2. Select an enclosure.
■ ■ ■ ■ ■ ■ ■ ■ Location – Enclosure location, if set. Status – Specifies whether the enclosure is OK or has an error. Misc – Enclosure ID, which is 0 for a controller enclosure and increments from 1 for attached drive enclosures. World Wide Name – Enclosure node World Wide Name. Model – Enclosure model number. Rack:Position – Assigned rack number and position of the enclosure within the rack, or 0:0 if not set. Position 1 is the top and 16 is the bottom.
Temperature Status As an Advanced user, you can view the current temperature status of each temperature sensor in each controller module. Each controller has six temperature sensors. To change the temperature display mode, see “Configuring Preferences” on page 29. To view temperature status: ● Select Monitor > Status > Advanced Settings > Temperature Status. The following panels are displayed: ■ Temperature Status – Shows each sensor's current temperature and status.
Volume Information To view information about all volumes in the system: ● Select Monitor > Status > Advanced Settings > Volume Information. The Volume Information panel shows the following information.
Misc Configuration As an Advanced user, you can view the following categories of configuration settings: general, RAID controller, EMP, security access to services, user preferences, and Network Time Protocol (NTP). To view miscellaneous configuration settings: ● Select Monitor > Status > Advanced Settings > Misc Configuration. The information is displayed in five panels.
■ SMART – Shows whether Self-Monitoring Analysis and Reporting Technology (SMART) settings for all drives in the system can be changed. The setting can be Enabled, Disabled, or Don't Modify. The default is Enabled. For more information, see“Enabling or Disabling SMART Changes” on page 137.
■ ■ Auto-Logout Timeout – The number of idle minutes before SMU session times out and requires you to log back in, or “No timeout.” The default is 30 minutes. Temperature Display Mode – Fahrenheit or Celsius for all temperature status displays. The default is Celsius. The Network Time Protocol panel shows the following information. To change these settings see “Setting Date and Time” on page 37. ■ NTP Enabled – Shows whether NTP is enabled (activated) or disabled (deactivated).
To view expander status information: 1. Select Monitor > Status > Advanced Settings > Expander Status. 2. Select an enclosure. The information is displayed in three panels. The Enclosure Details panel shows the following information about the selected enclosure: ■ Name – Name assigned to the enclosure. ■ Vendor – Enclosure manufacturer. ■ Location – Enclosure location, if set. ■ Status – Specifies whether the enclosure is OK or has an error.
■ ■ ■ ■ Type – Specifies one of the following: ■ Disk – Communicates between the expander and a disk drive. ■ Inter-Exp – (Controller module only) Communicates between the expander and the partner’s expander. ■ SC – (Controller module only) Communicates between the expander and the SC. ■ Egress – Communicates between the expander and an expansion port or SAS Out port. ■ Ingress – (Expansion module only) Communicates between an expansion port and the expander.
■ ■ ■ ■ Invalid Doubleword Count – Specifies the number of invalid doublewords that have been received by the PHY, not including those received during Link Reset sequences. Reset Error Count – Specifies the number of times the expander performed a reset. Phy Disabled – Specifies whether the PHY is enabled (True) or disabled (False). Fault Reason – A coded value that explains why the EC isolated the PHY. If the PHY is active, this value is 0x0.
Viewing the Event Log The system’s event log contains important information about the status of the system, virtual disks, and disk drives. Check it regularly to monitor the status of your system. For information about viewing the event log and about specific events and errors, see “Using Event Logs” on page 218.
Rate Statistics for Virtual Disks You can view the following I/O statistics for all virtual disks: ■ The total IOPS and bandwidth for all virtual disks ■ The IOPS and bandwidth for each virtual disk To view overall rate statistics for virtual disks: ● Select Monitor > Statistics > Overall Rate Stats. Statistics shown are based on host-side activity in the interval since the page was last refreshed. The page automatically refreshes at a 60-second interval.
Rate Statistics for Volumes You can view the following I/O statistics for a selected virtual disk: ■ The total IOPS and bandwidth for all volumes in the virtual disk ■ The IOPS and bandwidth for each volume in the virtual disk To view volume rate statistics. 1. Select Monitor > Statistics > Volume Rate Stats. 2. Select the virtual disk whose statistics you want to view. Statistics shown are based on host-side activity in the interval since the page was last refreshed.
3. Select the volume whose statistics you want to view. Statistics shown are based on host-side activity in the interval since the page was last refreshed. The page automatically refreshes at a 60-second interval. Real-Time Statistics for Volumes As an Advanced user, you can view the overall performance of volumes and related ports. This information is updated at a two-second interval.
Field Description I/O Timeout Count The number of times the drive accepted an I/O request but did not complete it in the required amount of time. Excessive timeouts can indicate potential device failure (media retries or soft, recoverable errors) No Response Count The number of times the drive failed to respond to an I/O request. A high value can indicate that the drive is too busy to respond to further requests.
Disk Space Usage Statistics As an Advanced user, you can view information about overall disk space usage for all disk drives in the storage system. The following information is displayed about virtual disk space, excluding spares. 176 Field Description Volume Space Space for user data storage. Free Space Space allocated for a virtual disk but not used by volumes. Free space in a virtual disk can be used to add an additional volume to that virtual disk or to expand a volume in that virtual disk.
The following information is displayed about spares and unused space. Field Description Virtual Disk Spare Space Space on spare disk drives that are designated for use by a specific virtual disk. Global Spare Space Space on spare disk drives that are designated for use by any virtual disk. Available Drive Space Space on unassigned disk drives that are available for creating new virtual disks, for expanding virtual disks, or for use as spares.
To reset statistics: 1. Select Monitor > Statistics > Reset All Statistics. 2. Click the button for the statistics you want to reset. A message is displayed indicating whether the reset succeeded. Displaying Notification Events The Show Notification Events panel shows events that have occurred that were selected for Visual Notification. This panel specifies how many notification events are pending and shows up to a configured maximum number of events.
Additional Status Information The following additional status information will help you monitor the system: ■ Using the debug log as explained in “Troubleshooting Using SMU” on page 195. ■ LED status descriptions in the user guide.
HP StorageWorks 2000 Family Modular Smart Array reference guide • August 2008
CH A P T E R 6 Additional Configuration Functions and Utilities This chapter describes how to use SMU to run system utilities and perform advanced configuration tasks.
Note – By default the storage system’s Partner Firmware Upgrade option is enabled, so when you upgrade one controller the system automatically upgrades the partner controller. If Partner Firmware Upgrade is disabled or if the Independent Cache Performance Mode option is enabled, after updating software on one controller you must manually upgrade the partner controller. Caution – Do not turn off or restart the system during this process.
Disabling Partner Firmware Upgrade If a service technician tells you to disable partner firmware upgrade: 1. Select Manage > General Config > System Configuration. 2. Set Partner Firmware Upgrade to Disabled. Changing Utility Priority You can change the priority at which the Verify, Reconstruct, Expand, and Initialize utilities run when there are active I/O operations competing for the system’s controllers.
Scanning for Device Changes Rescan forces rediscovery of attached disk drives and enclosures. If both storage controllers are online, it also forces re-evaluation of the enclosure IDs of attached drive enclosures, so that IDs are assigned 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 is not required to detect when drives are inserted or removed; the controllers do this automatically.
Resetting a Host Channel on an FC or SAS System 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).
Clearing Unwritable Cache Data The controller cache contains data that cannot be written out to a virtual disk because that virtual disk is no longer accessible. The virtual disk might be offline or missing. Unwritable cache data can exist if I/O to the virtual disk does not complete because drives or enclosures fail or are removed before the data can be written. Recovery is possible if the missing devices can be restored so that the cached data can be written to the virtual disk.
Restoring a Saved Configuration File As an Advanced Manage user, if you have created a backup configuration file as explained in “Saving the Configuration to a File” on page 60, you can load (restore) the configuration data to either: ■ The same system to revert its current configuration to the saved configuration ■ A second system to “clone” the first system's configuration Note – The file does not include configuration data for virtual disks and volumes.
3. Click Continue. A new page is displayed whose content depends on the IP address option you selected. 4. If you selected the second option in Step 2: a. Enter network information in the fields. b. Click Continue Restore Process. 5. Click Browse to navigate to a previously saved configuration file. 6. Click Restore Configuration File. Viewing and Restoring Default Settings You can view current and default settings as well as restore the system’s default settings.
Caution – Restoring default settings replaces your current configuration changes with the original manufacturer configuration settings. Some of these settings take effect immediately while others take effect after you restart the RAID controllers. Restoring default settings cannot be undone. To restore all defaults: 1. Select Manage > General Config > Restore Defaults. 2. (Optional) To see a list of the current settings and default settings, click See Restore Defaults Changes.
Controlling Host Access to the System’s Write-Back Cache Setting You can prevent hosts from using SCSI MODE SELECT commands to change the system’s write-back cache setting. Some operating systems disable write cache. If host control of write-back cache is disabled, the host cannot modify the cache setting. The default is Disabled. This option is useful in some environments where the host disables the system’s write-back cache, resulting in degraded performance.
Changing the Missing LUN Response Option Some operating systems do not look beyond LUN 0 if they do not find a LUN 0 or cannot handle noncontiguous LUNs. Missing LUN Response handles these situations by enabling the host drivers to continue probing for LUNs until they reach the LUN to which they have access.
Configuring In-band Management Services You can manage the storage system in-band with custom applications written using the Configuration API (CAPI). If you are not using CAPI-based applications, you can disable in-band management. You can also monitor system status in-band based on SCSI Enclosure Services (SES) data. To configure in-band management services: 1. Select Manage > General Config > Services Security. 2.
To save log information to a file: 1. Select Manage > Utilities > Debug Utilities > Save Logs To File. 2. In the Enter Your Contact Information panel, type contact information and comments to include in the log information file. Contact information provides the support representatives who are reviewing the file a means to identify who saved the log. Comments can explain why the logs are being saved and include pertinent information about system faults. 3.
HP StorageWorks 2000 Family Modular Smart Array reference guide • August 2008
CH A P T E R 7 Troubleshooting Using SMU This chapter describes how to use SMU to troubleshoot your storage system and its FRUs. It also describes solutions to problems you might experience when using SMU.
Problems Using SMU to Access a Storage System The following table lists problems you might encounter when using SMU to access a storage system. Table 7-1 Problems Using SMU to Access a Storage System Problem Solution You cannot access SMU. • Verify that you entered the correct IP address. • Enter the IP address using the format http://ip-address/index.html • If the system has two controllers, enter the IP address of the partner controller. SMU pages do not display properly.
Determining Storage System Status and Verifying Faults The System Summary page shows you the overall status of the storage system. To view storage system status: 1. Select Monitor > Status > Status Summary. 2. Check the status icon at the upper left corner of each panel. ■ A green icon indicates that components associated with that panel are operating normally.
6. Review the information displayed in the status page. If the fault relates to a controller module or power module, an image of the enclosure is displayed. ■ The module is shaded red if it has a fault or is powered off. ■ The module is overlaid with the words “NOT INSTALLED” if it is absent or not fully inserted. Stopping I/O When troubleshooting drive and connectivity faults, ensure you have a current full backup. As an additional data protection precaution, stop all I/O to the affected virtual disks.
4. In the Host-Generated I/O & Bandwidth Totals for All Virtual Disks panel, verify that both indicators display 0 (no activity). Clearing Metadata From Leftover Disk Drives A drive becomes a “leftover” when its metadata identifies the drive as being part of a nonexistent virtual disk, or when a controller forces the drive offline because it reported too many errors.
When you have confirmed a drive fault, record the drive’s enclosure number and slot number. To identify the physical location of a faulty drive: 1. Select Manage > Utilities > Disk Drive Utilities > Locate Disk Drive. 2. Select the faulty drive. If the drive is absent or not fully inserted, it is represented with a white rectangle and is not selectable, as shown in the following example. 3. Click Update LED Illumination. The upper LED on the selected drive illuminates solid blue.
4. Note any error counts displayed for these statistics. Field Description SMART Event Count The number of SMART (Self-Monitoring Analysis and Reporting Technology) events that the drive recorded. These events are often used by the vendor to determine the root cause of a drive failure. Some SMART events may indicate imminent electromechanical failure. I/O Timeout Count The number of times the drive accepted an I/O request but did not complete it in the required amount of time.
Capturing Error Trend Data To capture error trend data for one or more drives: 1. Perform the procedure in “Reviewing Disk Drive Error Statistics” on page 200. 2. Create a baseline by clearing the current error statistics. To clear the statistics for one drive, select the drive and click Clear Selected Disk Drive Error Statistics. To clear the statistics for all drives, click Clear All Disk Drive Error Statistics. You cannot clear the Bad Block List Size statistic.
Reconstructing a Virtual Disk If one or more drives fail in a redundant virtual disk (RAID 1, 3, 5, 6, 10, or 50) and properly sized spares are available, the storage system automatically uses the spares to reconstruct the virtual disk. Virtual disk reconstruction does not require I/O to be quiesced, so the virtual disk can continue to be used while the Reconstruct utility runs. A properly sized spare is one whose capacity is equal to or greater than the smallest drive in the virtual disk.
Note – Reconstruction can take hours or days to complete, depending on the virtual disk RAID level and size, drive speed, utility priority, and other processes running on the storage system. You can stop reconstruction only by deleting the virtual disk. Isolating Data Path Faults When isolating data path faults, you must first isolate the fault to an internal data path or an external data path. This will help to target your troubleshooting efforts.
PHYs are tested and verified before shipment as part of the manufacturing and qualification process.
SMU provides an Expander Status page, which contains an Expander Controller Phy Detail panel. This panel shows information about each PHY in the internal data paths between the Storage Controller, Expander Controller, drives, and expansion ports. By reviewing this page you can quickly locate the internal data path that has a fault. Checking PHY Status SMU's Expander Status page includes an Expander Controller PHY Detail panel.
Reviewing the Event Log for Disabled PHYs If the fault isolation firmware disables a PHY, the event log shows a message like the following:. Phy disabled. Enclosure:A00. Phy11. PhysId11 Type:Drive. Reason:Externally Disabled. When a PHY has been disabled manually, the event log shows a similar message with a different reason: Phy disabled. Enclosure:A00. Phy11. PhysId11. Type:Drive. Reason:Ctrl Page Disabled. Resolving PHY Faults 1. Ensure that the cables are securely connected.
Isolating External Data Path Faults on an FC Storage System To troubleshoot external data path faults, perform the following steps: 1. Select Monitor > Status > Advanced Settings > Host Port Status. This page provides a graphical representation of controller host port status and port details. 2. Review the graphical representation of host port status.
Isolating External Data Path Faults on an iSCSI Storage System To troubleshoot external data path faults, perform the following steps: 1. Select Monitor > Status > Advanced Settings > Host Port Status. This page provides a graphical representation of controller host port status and port details. 2. Review the graphical representation of host port status.
Isolating External Data Path Faults on a SAS Storage System To troubleshoot external data path faults, perform the following steps: 1. Select Monitor > Status > Advanced Settings > Host Port Status. This page provides a graphical representation of controller host port status and port details. 2. Review the graphical representation of host port status.
Resetting a Host Channel on an FC or SAS Storage System 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).
Disabling or Enabling a PHY To disable or enable a PHY: ● In the Expander Controller Phy Detail panel, click the PHY's Disable or Enable button. When you disable a PHY, its button changes to Enable and its Status value changes to DISABLED. When you enable a PHY, its button changes to Disable and its status value changes to OK or another status.
Using Recovery Utilities This section describes recovering data from a virtual disk that is quarantined or offline (failed). Removing a Virtual Disk From Quarantine The quarantine icon indicates that a previously fault-tolerant virtual disk is quarantined because not all of its drives were detected after a restart or rescan. For information about when and how you can recover data from a quarantined virtual disk, see“Removing a Virtual Disk From Quarantine” on page 75.
To enable and use Trust Vdisk: 1. Select Manage > Utilities > Recovery Utilities > Enable Trust Vdisk. 2. Select Enabled. 3. Click Enable/Disable Trust Vdisk. The option remains enabled until you trust a virtual disk or restart the storage system. 4. Select Manage > Utilities > Recovery Utilities > Trust Vdisk. 5. Select the virtual disk and click Trust This Vdisk. 6. Back up the data from all the volumes residing on this virtual disk and audit it to make sure that it is intact. 7.
Problems Scheduling Tasks If your task does not run at the times you specified, check the schedule specifications. It is possible to create conflicting specifications. ■ Start time is the first time the task will run. ■ If you use the Between option, the starting date/time must be in the Between range. ■ The year must be four digits, between 2006 and 2999. ■ Either the Repeat option or the Expires On option will end a schedule.
Affect of Changing the Date and Time Resetting the storage system date or time might affect scheduled tasks. Because the schedule begins with the start time, no schedules will run until the date and time are set. If the system is configured to use Network Time Protocol (NTP), and if an NTP server is available, the system time and date is obtained from the NTP server. To manually change the date or time, see “Setting Date and Time” on page 37.
Individual event selections do not override the Notification Enabled or Event Categories settings. If the notification is disabled, the individual event selection is ignored. Similarly, Event Categories settings have higher precedence for enabling events than individual event selection. If the critical event category is selected, all critical events cause a notification regardless of the individual critical event selection.
Selecting or Clearing All Events for Notification You can select or clear all individual events for any or all of the notification types. Selecting all individual events is useful if you want to select many events but not all; set all the events on this page, then go to pages for individual events and clear events you don't want. Clearing all individual events is useful if you want to clear all the individual event settings so you can set up a new custom configuration. To select all events: 1.
Event Severities The storage system generates events having three severity levels: ■ Informational – A problem occurred that the system corrected, or a system change has been made. These events are purely informational; no action required. ■ Warning – Something related to the system or to a virtual disk has a problem. Correct the problem as soon as possible. ■ Critical – Something related to the system or to a virtual disk has failed and requires immediate attention.
To view the event log: 1. Do one of the following: ■ In the System Panel, click the icon. ■ In the menu, select Monitor > Status > View Event Log. The event log page is displayed. 2. Click one of the following buttons in the Select Event Table To View panel to see the corresponding events. For a dual-controller system: Button Description Controller A & B Events Shows all events for both controllers. This is the default.
For example: Severity Level Info Critical Date/Time 2008-08-06 09:35:07 2008-04 12:12:05 Event Code 33 Event Serial Number A29856 65 A29809 Message Time/date has been changed Uncorrectable ECC error in buffer memory address 0x0 on bootup Viewing an Event Log Saved From SMU You can save event log data to a file on your network as described in “Saving Log Information to a File” on page 192.
For example: Event SN A29856 A29809 Date/Time 08-06 09:35:07 08-04 12:12:05 Code 33 65 Severity I C Controller A A Description Time/date has been changed Uncorrectable ECC error in buffer memory address 0x0 on bootup Reviewing Event Logs When reviewing events, do the following: 1. Review the critical/warning events. Identify the primary events and any that might be the cause of the primary event. For example, an over temperature event could cause a drive failure. 2.
Saving Log Information to a File You can save the following types of log information to a file: ■ Device status summary, which includes basic status and configuration information for the system. ■ Event logs from both controllers when in active-active mode. ■ Debug logs from both controllers when in active-active mode. ■ Boot logs, which show the startup sequence for each controller. ■ Up to four critical error dumps from each controller. These will exist only if critical errors have occurred.
8. If prompted to specify the file location and name, do so using a .logs extension. The default file name is store.logs. If you intend to capture multiple event logs, be sure to name the files appropriately so that they can be identified later. Note – If you are using Firefox and have a download directory set, the file is automatically saved there. Configuring the Debug Log When instructed to do so by service personnel, as an Advanced Manage user you can configure the debug log.
■ ■ No Debug Tracing – Collects no debug data. Custom Debug Tracing – Shows that specific events are selected for inclusion in the log. This is the default. If no events are selected, this option is not displayed. 3. Click Change Debug Logging Setup. 4. If instructed by service personnel, click Advanced Debug Logging Setup Options and select one or more additional types of events.
HP StorageWorks 2000 Family Modular Smart Array reference guide • August 2008
APPENDIX A SNMP Configuration This appendix describes the Simple Network Management Protocol (SNMP) capabilities that MSA2000 Family storage systems support. This includes standard MIB-II, the Fibre Alliance SNMP Management Information Base (MIB) version 2.2 objects, and enterprise traps. Topics covered in this appendix are: ■ “Introduction” on page 227 ■ “Standard MIB-II Behavior” on page 228 ■ “Enterprise Traps” on page 228 ■ “FA MIB 2.
An SNMP object identifier (OID) is a number assigned to devices in a network for identification purposes. OID numbering is hierarchical. Using the IETF notation of digits and dots resembling very long IP addresses, various registries such as ANSI assign high-level numbers to vendors and organizations. They, in turn, append digits to the number to identify individual devices or software processes.
FA MIB 2.2 SNMP Behavior The FA2.2 MIB objects are in compliance with the Fibre Alliance MIB v2.2 Specification (FA MIB2.2 Spec). For a full description of this MIB, go to: http://www.fibrealliance.org/fb/mib/mib2_2.htm 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 245. FA MIB 2.
The following table lists the MIB objects, their descriptions and the value set in an MSA2000 Family storage system. Unless specified otherwise, objects are not settable. Table A-1 FA MIB 2.2 Objects, Descriptions, and Values Object Description Value RevisionNumber Revision number for this MIB 0220 UNumber Number of connectivity units present 1 SystemURL Top-level URL of the device; for example, http://10.1.2.3.
Table A-1 FA MIB 2.2 Objects, Descriptions, and Values (Continued) Object Description Value connUnitTable Includes the following objects as specified by the FA MIB2.
Table A-1 FA MIB 2.
Table A-1 FA MIB 2.2 Objects, Descriptions, and Values (Continued) Object Description Value connUnitRevsTable Includes the following objects as specified by the FA MIB2.
Table A-1 FA MIB 2.2 Objects, Descriptions, and Values (Continued) Object Description Value connUnitSensorMessage Description the sensor status as a message connUnitSensorName followed by the appropriate sensor reading. Temperatures display in both Celsius and Fahrenheit; for example, CPU Temperature (Controller Module A): 48C 118F). Reports “Not installed” or “Offline” if data is not available.
Table A-1 FA MIB 2.
Table A-1 FA MIB 2.2 Objects, Descriptions, and Values (Continued) Object Description Value connUnitPortName String describing the addressed port See “External Details for connUnitPortTable” on page 240 connUnitPortPhysical Number Port number represented on the hardware Port number represented on the hardware connUnitPortStatObject Not supported 0 (No statistics available) connUnitEventTable Includes the following objects as specified by the FA MIB2.
Table A-1 FA MIB 2.
External Details for Certain FA MIB 2.2 Objects Tables in this section specify values for certain objects described in Table A-1. External Details for connUnitRevsTable The following table provides external details for the connUnitRevsTable objects connUnitRevsIndex and connUnitRevsDescription.
External Details for connUnitSensorTable The following table provides external details for the connUnitSensorTable objects connUnitSensorIndex, connUnitSensorName, connUnitSensorType, and connUnitSensorCharacteristic.
Table A-3 connUnitSensorTable Index, Name, Type, and Characteristic Values (Continued) Sensor Index Sensor Name Sensor Type Sensor Characteristic 24 Capacitor Cell 4 Voltage (Controller Module B) board [8] power[9] 25 Capacitor Charge Current (Controller Module A) board [8] currentValue[6] 26 Capacitor Charge Current (Controller Module B) board [8] currentValue[6] 27 Power Supply 1 Voltage, 12V power-supply[5] power[9] 28 Power Supply 1 Voltage, 5V power-supply[5] power[9] 29 Power
Configuring SNMP Event Notification in SMU As a Manage user you can configure and enable SNMP event notification. To do so: 1. Select the level of events to include in the FA2.2 event table; see “Setting the SNMP Event Table Filter” on page 50. 2. Verify that the storage system’s SNMP service is enabled; see “Configuring Network Management Services” on page 52. 3. Select event levels for notification; see “Selecting Event Categories to Monitor” on page 54. 4.
Enterprise Trap MIB The following pages show the source for the HP enterprise traps MIB, msa2000traps.mib. This MIB defines the content of the SNMP traps that MSA2000 Family storage systems generate. -- ---------------------------------------------------------------------------- MSA2000 Array MIB for SNMP Traps --- $Revision: 11692 $ --- Copyright (c) 2008 Hewlett-Packard Development Company, L.P. -- Copyright (c) 2005-2008 Dot Hill Systems Corp. -- Confidential computer software.
-- 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.
msaEventErrorTrap TRAP-TYPE ENTERPRISE hpMSA VARIABLES { connUnitEventId, connUnitEventType, connUnitEventDescr } DESCRIPTION "An event has been generated by the storage array.
FA MIB 2.2 and 4.0 Differences FA MIB 2.2 is a subset of FA MIB 4.0. Therefore, SNMP elements implemented in MSA2000 Family storage systems can be accessed by a management application that uses FA MIB 4.0. The following tables are not implemented in 2.2: ■ ■ ■ ■ ■ ■ connUnitServiceScalars connUnitServiceTables connUnitZoneTable connUnitZoningAliasTable connUnitSnsTable connUnitPlatformTable The following variables are not implemented in 2.
HP StorageWorks 2000 Family Modular Smart Array reference guide • August 2008
APPENDIX B RAID Levels This appendix describes the different RAID levels that virtual disks in your system can use. Topics covered in this appendix are: ■ “Introduction” on page 247 ■ “RAID Level Descriptions” on page 249 ■ “Comparing RAID Levels” on page 252 ■ “Mixing Disk Drive Models” on page 253 Introduction The RAID controllers enable you to set up and manage virtual disks, whose storage may be spread across multiple disk drives. This is accomplished through software resident in the RAID controller.
Table B-1 Example Applications and RAID Levels 248 Application RAID Level Testing multiple operating systems or software development (where redundancy is not an issue) non-RAID Fast temporary storage or scratch disks for graphics, page layout, and image rendering 0 Workgroup servers 1 or 1+0 (10) Video editing and production 3 Network operating system, databases, high availability applications, workgroup servers 5 Very large databases, Web server, video on demand 5+0 (50) Mission-critical en
RAID Level Descriptions RAID levels are numbered from 0 through 6; a higher RAID level does not necessarily indicate a higher level of performance or fault tolerance. The RAID controllers support RAID levels that have proven to be the most useful for RAID applications: RAID 0, 1, 10, 3, 5, 50, and 6. You can use Non-RAID for a virtual disk that will have a single drive and not need the data redundancy or performance benefits of RAID.
A mirrored virtual disk is also highly reliable, because both disk drives in a pair must fail for the virtual disk to fail. In an virtual disk with five pairs of mirrored disk drives, for example, the virtual disk can maintain its integrity even if five disks fail—as long as each pair is left with one good disk. The main disadvantage of a mirrored virtual disk is its cost.
RAID 50 RAID 50 virtual disks are made up of two or more RAID 5 virtual disks, across which data is striped. RAID 50 virtual disks contain redundant information in the form of parity data, which is calculated block-by-block for all user data. As in a RAID 5 virtual disk, the parity information is distributed across the disk drives in the virtual disk and occupies the equivalent capacity of one disk drive per RAID 5. Data is interspersed with the parity information.
Comparing RAID Levels Table A-2 illustrates the differences between the different RAID levels. Table B-2 RAID Level Comparison RAID Level Min.
Table B-2 RAID Level Comparison (Continued) RAID Level Min.
HP StorageWorks 2000 Family Modular Smart Array reference guide • August 2008
APPENDIX C Host Access to Storage A volume in a virtual disk can be mapped through all controller host ports (target ports) to all data hosts, or through specific controller host ports to specific data hosts. Each mapping between a volume and a data host includes a logical unit number (LUN) that identifies the mapping. This appendix describes how the controllers present volumes to data hosts in direct attach and switch attach configurations, during normal operation and after failover.
Node and Port Identifiers This section describes the node and port identifiers presented by FC, iSCSI, and SAS storage systems. FC Each controller has a unique, permanent node WWN. Each controller host port has a unique port WWN that is based on the node WWN. The WWN format is: 27 ■ port – 0 for a node; the port number for a port. ■ A/B – 0 for controller A; 8 for controller B. ■ multiID – 0 for a node; 0 for the first ID on each port per controller.
iSCSI Each controller has a unique, permanent hardware address. Each controller host port has a unique, user-defined IP address. The following table shows example hardware addresses and port IP addresses. Controller Hardware Address iSCSI Port IP Address A 00C0FF0A8A51 0: 10.11.10.4 1: 10.10.10.5 B 00C0FF0A8A52 0: 10.11.10.2 1: 10.10.10.3 SAS Both controllers have the same unique, permanent node WWN. Each controller host port has a unique port WWN that is based on the node WWN.
FC Direct Attach Configuration When a data host is directly connected to controller host ports, loop topology must be used. The host should have one HBA port connected to each controller. When the host-port interconnects are enabled, the host has access to both controllers’ mapped volumes. If one controller fails in this configuration, the interconnects remain active so hosts can continue to access all mapped volumes without the intervention of host-based multipathing software.
The following figure shows how port WWNs and mapped volumes are presented if controller B fails.
FC Switch Attach Configuration The topology only affects how mapped volumes and port WWNs are presented if one controller fails. Whichever topology is used, each data host has dual-ported access to volumes through both controllers. ■ Failover in a switch attach, loop configuration. If one controller fails in a switch attach configuration using loop topology, the host ports on the surviving controller present the port WWNs for both controllers. Each controller’s mapped volumes remain accessible.
For a system using loop topology, the following figure shows how port WWNs and mapped volumes are presented if controller B fails.
For a system using point-to-point topology, the following figure shows how port WWNs and mapped volumes are presented if controller B fails.
iSCSI Switch Attach Configuration The high-availability configuration requires two gigabit Ethernet (GbE) switches. During active-active operation, both controllers’ mapped volumes are visible to both data hosts. A dual-controller MSA2012i storage system uses port 0 of each controller as one failover pair and port 1 of each controller as a second failover pair. If one controller fails, all mapped volumes remain visible to all hosts.
The following figure shows how port IP addresses and mapped volumes are presented if controller B fails.
SAS Direct Attach Configurations The SAS storage system uses Unified LUN Presentation (ULP). ULP is a controller software feature that enables hosts to access mapped volumes through both controllers’ host ports (target ports) without the need for internal or external switches. In a dual-controller SAS system, both controllers share a unique node WWN so they appear as a single device to hosts. The controllers also share one set of LUNs to use for mapping volumes to hosts.
If a controller fails, the hosts maintain access to all of the volumes through the host ports on the surviving controller, as shown below. No data A0 WWN, A & B volumes A1 WWN, A & B volumes A0 A1 B0 B1 No data (Failed) Figure 7-3 SAS Storage Presentation During Failover (High-Availability, DualController, Direct Attach with Two Hosts) In the following configuration, each host has a non-redundant connection to all mapped volumes.
APPENDIX D SMU Menu Reference This appendix shows the SMU menu hierarchy. As described in “Introducing and Using SMU” on page 17, user configuration affects the SMU menu. ■ “Standard and Advanced User Functions” on page 267 lists the SMU functions available to Standard and Advanced users. ■ “Diagnostic User Functions” on page 274 lists the SMU functions available to Diagnostic users only. If users do not have access to a function, the specified user type might be preventing access.
Table D-1 Monitor Menu – Standard and Advanced User Functions (Continued) Submenu Page See Advanced Settings Statistics Help 268 • Controller Versions “Controller Versions” on page 160 • FRU Information “FRU Information” on page 161 • Disk Drive List “Disk Drive List” on page 155 • Host Port Status “Host Port Status” on page 152 • Volume Information “Volume Information” on page 164 • Misc Configuration “Misc Configuration” on page 165 • Expander Status “Expander Status” on page 167 • LA
Table D-2 Manage Menu – Standard and Advanced User Functions Submenu Page Virtual Disk Config Vdisk Configuration See • Vdisk Status “Virtual Disk Status” on page 71 • Disk Drive Status “Viewing Virtual Disk and Disk Drive Status Information” on page 71 • Verify Virtual Disk “Starting Virtual Disk Verification” on page 77 • Expand Virtual Disk “Expanding Virtual Disk Capacity” on page 74 • Add Vdisk Spares “Adding Vdisk Spares” on page 81 • Delete Vdisk Spares “Deleting Vdisk Spares” on page
Table D-2 Manage Menu – Standard and Advanced User Functions (Continued) Submenu Page Volume Management Volume Menu 270 See • Volume Status “Viewing Volume Status Information” on page 87 • Add Volume “Adding a Volume” on page 86 • Delete Volume “Deleting a Volume” on page 93 • Expand Volume “Expanding a Volume” on page 87 • Change Volume Name “Changing a Volume Name” on page 88 • Read Ahead Cache “Changing a Volume’s Read-Ahead Cache Settings” on page 89 • Write Back Cache “Changing a Vol
Table D-2 Manage Menu – Standard and Advanced User Functions (Continued) Submenu Page See Volume Mapping • Map Hosts To Volume “Managing Volume Mappings” on page 99 • Manage Host List (FC only) “Managing the Global Host List” on page 95 Scheduler Manage Scheduler “Using the Scheduler” on page 127 General Config LAN Configuration “Configuring Ethernet Management Ports” on page 48 Host Port Configuration “Configuring Host Ports” on page 39 Manage Host List (iSCSI and SAS only) “Managing the Gl
Table D-2 Manage Menu – Standard and Advanced User Functions (Continued) Submenu Event Notification Utilities Page See System Configuration • “Changing the Cache Redundancy Mode” on page 58 • “Managing Dynamic Spares” on page 80 • “Changing Auto-Write-Through Triggers and Behaviors” on page 92 • “Changing Utility Priority” on page 183 • “Enabling and Disabling Background Scrub for Disks” on page 189 • “Disabling Partner Firmware Upgrade” on page 183 • “Controlling Host Access to the System’s Write-Bac
Table D-2 Manage Menu – Standard and Advanced User Functions (Continued) Submenu Page See Configuration Utilities • Show Changed Settings “Viewing Changed Settings” on page 188 • Save Config File “Saving the Configuration to a File” on page 60 • Restore Config File “Restoring a Saved Configuration File” on page 187 Debug Utilities • Save Logs to File “Saving Log Information to a File” on page 192 • Debug Log Setup “Setting Up the Debug Log” on page 193 Restart System Shut Down/Restart “Restar
Diagnostic User Functions The SMU menu options listed in the following table are available to Diagnostic Manage users for troubleshooting purposes. This guide does not include functions for use by service personnel.
APPENDIX E Event Codes Information in this appendix is for reference by storage administrators and technical support personnel to aid troubleshooting. Event messages appear in the event log, which you can view using SMU or the CLI, and in debug logs. You may also receive notifications, depending on your SMU event notification settings. The following table describes the events that can occur during operation. Events are listed in order by numeric event code.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description 6 Informational or warning Vdisk creation status. This event is logged as informational if creation immediately failed, was canceled by the user, or succeeded. This event is logged as a warning if creation failed during initialization. 8 Warning A drive in a vdisk failed and the vdisk changed to a critical or offline state.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description 24 Informational The assigned LUN for this volume has changed. 25 Informational The statistics for the specified vdisk have been reset. 27 Informational Cache parameters have been changed for the specified vdisk. 28 Informational Controller parameters have been changed.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description Recommended Action 39 Warning The sensors monitored a temperature or voltage in the warning range. • Check that the storage system’s fans are running. • Check that the ambient temperature is not too warm. The enclosure operating range is 41° F to 104° F (5° C to 40° C). • Check for any obstructions to the airflow.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description 45 Informational A communication failure has occurred between the controller and an EMP. 47 Informational An error detected by the sensors has been cleared. 48 Informational The vdisk name has been changed. 49 Informational A lengthy SCSI maintenance command has completed. 52 Informational Vdisk expansion has started.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type 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. • If the controller recovers, no action is required. • View other logged events to determine other action to take. 62 Informational A spare drive has failed.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description 73 Informational (Active-active environment) The two controllers are communicating with each other and cache redundancy is enabled. 74 Informational The FC loop ID for the specified vdisk was changed to be consistent with the IDs of other vdisks. This can occur when drives containing a vdisk are inserted from an enclosure having a different FC loop ID.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description 80 Informational The controller has modified mode parameters on one or more drives. 81 Informational The current controller has unkilled the partner controller. The other controller will restart. 83 Informational The partner controller is changing state (shutting down or restarting).
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type 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 E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description Recommended Action 107 Critical The controller experienced the specified critical error. In a nonredundant configuration the controller will be restarted automatically. In an active-active configuration the surviving controller will kill the controller that experienced the critical error. A service technician can use the debug log to determine the problem. 108 Informational A volume has been deleted.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description Recommended Action 127 Warning The controller has detected an invalid disk drive dual-port connection. This connection does not have the benefit of fault tolerance. Failure of the disk drive port would cause loss of access to the drive. The single disk drive port should be connected to one controller only.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description 154 Informational New software has been loaded on the Management Controller. 155 Informational New loader software has been loaded on the Management Controller. 156 Informational The Management Controller has been restarted from the Storage Controller. 157 Critical A failure occurred when trying to write to the Storage Controller flash chip. Replace the controller module.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description Recommended Action 163 Warning The host FC World Wide Names (node and port) previously presented by an offline controller module in this system are unknown. This event has two possible causes: • The online controller module reporting the event was replaced or moved while the system was powered off. • The online controller module had its flash configuration (where previously used WWNs are stored) cleared.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description Recommended Action 168 Warning or informational The specified SES alert condition was detected in the enclosure indicated. Most voltage and temperature errors and warnings relate to the power-and-cooling module. See “Power-and-Cooling Module Faults and Recommended Actions” on page 302. 169 Informational The specified SES alert condition has been cleared in the enclosure indicated.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description 176 Informational The error statistics for the specified drive have been reset. 177 Informational The cache data for a missing volume was purged. 178 Informational A host has been added to the list of hosts that can access, or be denied access to, a LUN. An Add Host command was successful.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description 189 Informational A disk channel that was previously degraded or failed is now healthy. 190–201 Informational Includes component-specific environmental indicator events generated by the auto-write-through feature when an environmental change occurs. If an auto-writethrough-trigger condition has been met, write-back cache is disabled and event 188 is also logged.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description 207 Informational Vdisk scrub has completed. The event message reports the number of: • Data parity mismatches for RAID 3, 5, 6, and 50 • Mirror verify errors for RAID 1 and 10 • Medium errors for other types 208 Informational Drive scrub has started. 209 Informational Drive scrub has completed. 210 Informational All snapshot volumes have been deleted.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description 215 Informational A previously created batch of snapshots is now committed and ready for use. The number of snapshots is specified. 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.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description Recommended Action 225 Critical Background master write copy-onwrite operation has failed. There was an internal I/O error. Could not complete the write operation to the disk. A probable hardware failure has prevented the software from operating successfully. Isolate and replace and failed hardware components.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description Recommended Action 233 Warning The specified drive type is invalid and not allowed in the current configuration. One or more drives are not allowed for this platform. They have been removed from the configuration. (Some platforms are SAS- or SATA-only). Replace the disallowed drives with ones that are supported.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description 241–242 Informational Compact flash status events generated by the auto-write-through feature whenever an environmental change occurs. If an auto-write-throughtrigger condition has been met, writeback cache is disabled. 243 Informational A new RAID enclosure has been detected.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description 249 Informational A valid license has been installed for the specified feature. This event is logged for each feature license installed. 250 Warning A license could not be installed (license is invalid). 252 Informational Snapshot write data on the specified master volume has been deleted. 256 Informational The specified snapshot has been created but not committed.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type 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 E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description Recommended Action 298 Warning The controller’s real-time clock (RTC) settings might be invalid after an unexpected power loss. Check the system date and time. If either is incorrect, set them to the correct date and time. 299 Informational The controller’s real-time clock (RTC) settings were recovered after an unexpected power loss. 300 Informational CPU frequency has been adjusted to high.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description Recommended Action 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. The enclosure operating range is 41° F to 104° F (5° C to 40° C). • Check for any obstructions to the airflow.
TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code Event Type Description Recommended Action 314 Critical A FRU has failed or is not operating correctly. This event follows some other FRU specific event indicating a problem. Examine the FRU specified in the message to determine whether it needs to be replaced. Disk Drive Errors and Recommended Actions As referred to in TABLE E-1, the following table lists disk-drive error conditions and recommended actions.
TABLE E-2 Disk Drive Error Conditions and Recommended Actions (Continued) Status Recommended Action If the status of the virtual disk that originally had the failed drive status is FATAL FAIL, two or more drive modules have failed. All data in the virtual disk is lost. Use the SMU Trust Virtual Disk function to attempt to bring the virtual disk back online. Select Manage > Utilities > Recovery Utilities > Trust Virtual Disk.
Power-and-Cooling Module Faults and Recommended Actions As referred to in TABLE E-1, the following table lists power-and-cooling module faults and recommended actions. TABLE E-3 Power-and-Cooling Module 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.
Glossary The glossary defines terms and acronyms used in MSA2000 Family storage system documentation. Definitions obtained from the Storage Networking Industry Association (SNIA) Dictionary are indicated with “(SNIA)” at the end. For the complete SNIA Dictionary, go to www.snia.org/education/dictionary. active-active Synonym for dual active components or controllers.
cache The location in which data is stored temporarily. There are a variety of cache types. Read cache holds data in anticipation that it will be requested. Write cache holds data written by a client until it can be stored on other (typically slower) storage media such as disk or tape. (SNIA) See also write-back cache, write-through cache.
controller enclosure controller module copy-on-write (COW) An enclosure that contains disk drives and one or two controller modules. See controller module. A FRU that contains: a Storage Controller processor; a Management Controller processor; a SAS expander and Expander Controller processor; management interfaces; a LAN subsystem; cache protected by a capacitor pack and Compact Flash memory; host, expansion, management, and service ports; and midplane connectivity.
data mirroring Data written to one disk drive is simultaneously written to another disk drive. If one disk fails, the other disk can be used to run the virtual disk and reconstruct the failed disk. The primary advantage of disk mirroring is 100 percent data redundancy: since the disk is mirrored, it does not matter if one of the disks fails; both disks contain the same data at all times and either can act as the operational disk.
enclosure management processor (EMP) Ethernet adapter Expander Controller (EC) expansion module fabric fabric switch An Expander Controller subsystem that provides data about an enclosure’s environmental conditions such as temperature, power supply and fan status, and the presence or absence of disk drives. An adapter that connects an intelligent device to an Ethernet network. Usually called an Ethernet network interface card, or Ethernet NIC.
fault-tolerant virtual disk FC FC-AL Fibre Channel (FC) Fibre ChannelArbitrated Loop (FC-AL) field-replaceable unit (FRU) FRU 308 A virtual disk that provides protection of data in the event of a single disk drive failure by employing RAID 1, 3, 5, 6, 10, or 50. RAID 6 also provides protection against the failure of two drives. See Fibre Channel (FC). See Fibre Channel-Arbitrated Loop (FC-AL).
host bus adapter (HBA) host port host port interconnect hot swap in-band management An adapter that connects a host I/O bus to a computer’s memory system. Host bus adapter is the preferred term in SCSI contexts. Adapter and NIC are the preferred terms in Fibre Channel contexts. The term NIC is used in networking contexts such as Ethernet and token ring. (SNIA) A host-interface port on a controller module or an expansion module.
I/O module (IOM) IP IQN iSCSI iSNS JBOD jumbo frame Kbyte (KB) LAN leftover drive local area network (LAN) logical unit number (LUN) See controller module and expansion module. Internet Protocol. ISCSI Qualified Name. Internet Small Computer System Interface. Internet Storage Name Service. Just a Bunch of Disks. A drive enclosure that is directly attached to a host. In an iSCSI network, a frame that can contain 9000 bytes for large data transfers. A normal frame can contain 1500 bytes. Kilobyte.
management host management information base (MIB) master volume Mbyte MC metadata MIB network interface card (NIC) Network Time Protocol (NTP) NIC node WWN Non-RAID NTP originator A workstation with direct or network connections to a storage system’s management ports and that is used to manage the system. A database of managed objects accessed by network management protocols.
out-of-band management ownership PHY PID point-to-point port bypass circuit (PBC) port WWN power-and-cooling module In an active-active configuration, one controller has ownership of the following resources: virtual disks and vdisk spares. When a controller fails, the other controller assumes temporary ownership of its resources. Hardware component that converts between digital and analog in the signal path between the Storage Controller, Expander Controller, disk drives, and SAS ports.
RAS Reliability, availability, and serviceability. These headings refer to a variety of features and initiatives all designed to maximize equipment uptime and mean time between failures, minimize downtime and the length of time necessary to repair failures, and eliminate or decrease single points of failure in favor of redundancy.
SCSI Enclosure Services (SES) An ANSI X3T10 standard for management of environmental factors such as temperature, power, voltage, etc. (SNIA) In MSA2000 Family storage systems, SES data is managed by the Expander Controller and EMP. secret SFP Small form-factor pluggable connector, used in FC controller module host ports. An SFP is a FRU. SID Secondary controller identifier number. SMART Self-Monitoring Analysis and Reporting Technology.
standard volume standby state Storage Area Network (SAN) Storage Controller (SC) storage system A volume that is not enabled for snapshots. See spare. The current operational status of a disk drive, a virtual disk, or controller. A controller module stores the states of drives, virtual disks, and the controller in its nonvolatile memory. This information is retained across power interruptions.
ULP UT Universal Time. A modern time system related to the conventional Greenwich Mean Time (GMT) used for time zones. UPS Uninterruptible Power Supply. vdisk Abbreviation for virtual disk. vdisk spare A disk drive that is marked as a spare to support automatic data rebuilding after a disk drive associated with a virtual disk fails.
world wide name (WWN) A unique 64-bit number assigned by a recognized naming authority (often via block assignment to a manufacturer) that identifies a node process or node port. (SNIA) MSA2000 Family storage systems derive WWNs from the serial numbers of controller modules and expansion modules. world wide node name (WWNN) world wide port name (WWPN) write policy write-back cache A globally unique 64-bit identifier assigned to each Fibre Channel node process.
HP StorageWorks 2000 Family Modular Smart Array reference guide • August 2008
Index A access level changing, 33 default user configuration, 31 definition, 31 setting, 34 access privileges See also user type changing, 33 definition, 32 setting, 34 adding dedicated spares, 82 global spares, 83 licenses, 36 users, 34 volumes, 86 advanced user type changing, 33 definition, 32 list of available functions, 267 setting, 34 alerts configuring email, 56 visual, 55 enabling email, 54 SNMP traps, 54 visual, 54 asterisks marking current setting, 33 shown in FC port status, 152 auto expand, snap
capacity expanding snap pools, 111 expanding volumes, 87 CAPI enabling or disabling for in-band management, 192 Celsius configuring temperature status display, 30 CHAP configuring, 45 CLI displaying current configuration, 166 enabling and disabling user access, 33 enabling service security, 51 command-line interface. See CLI clone.
deleting dedicated spares, 82 global spares, 83 mapping, 100, 102, 103 modified data on snapshots, 116 snapshots, 118 users, 35 virtual disks, 79 volumes, 93 DHCP, using to obtain controller IP addresses, 48 diagnostic manage-level only functions selecting individual events for notification, 216 diagnostic user type changing, 33 definition, 32 setting, 34 disabled PHY, 205 disaster recovery.
errors displaying media errors, 175, 201 displaying non-media errors, 175, 201 PHY, 205 reviewing disk drive statistics, 200 Ethernet link, displaying information for controllers, 158 event codes, 275 event log disabled PHY, 207 displaying, 220 event type, 219 reviewing, 202 viewing using SMU, 219 event notification displaying, 178 enabling and disabling, 54 selecting categories to monitor, 54 selecting individual events to monitor, 55, 216 severity levels, 53 event, table selecting filters, informational,
configuring, 39, 44 interconnects, 42 topology, 42 displaying status, 152, 153, 154 link speed, configuring, 40 host ports, resetting, 185, 211 hosts, mapping to volumes, 99, 100, 102 HTTP displaying current configuration, 166 enabling, 52 I I/O checking status, 198 displaying timeout count, 175, 201 icons health status, 26 system panel, 26 virtual disk, 24 icons, system status, 197 in-band management, enabling and disabling, 192 informational events, 219 enabling, 53, 219 selecting to monitor, 217 interfa
memory controller updating, 181 menu hierarchy, 267 options shown based on user configuration, 32 metadata clearing, 136, 199 MIB differences between FA 2.2 and 4.
Q quarantined virtual disk, 213 R rack specifying location, 143 specifying number, 143 RAID levels comparison, 252 descriptions, 249 read-ahead cache changing, 89 displaying current configuration, 164 enabling and disabling, 89 rebuilding.
critical, 112 default settings, 110 error, 111 setting values, 111 trigger behavior, 110 warning, 111 reserve space, 110 thresholds default settings, 110 setting values, 111 snapshots automating creation of, 127 automating reset of, 128 cancel copy, 126 copying, 124 creating a snap pool, 109 definition, 104 deleting, 118 deleting modified data, 116 displaying current configuration, 118 maximum base number, 105 resetting, 115 snap pool critical policy options, 112 error policy options, 111 warning policy opt
See also WBI available menu options based on user configuration, 32 browser support, 18 browser’s local-intranet security option, 18 caching web pages, 51 configuring preferences, 29 definition, 17 displaying current configuration, 166 enabling and disabling access, 33 enabling service security, 52 guidelines for using, 18 help bar icons, 24 interface elements, 21 logging out, 19 login access levels, 31 navigating, 23 optimizing performance, 18 prerequisites, 18 system requirements, 18 Storage Management Ut
modifying, 32 setting access level, 34 setting access to system interfaces, 34 setting passwords, 34 setting user type, 34 user name and role, viewing current, 22, 32 user type advanced, 32 changing, 33 default, 31 definition, 32 diagnostic, 32 setting, 34 standard, 32 username maximum character length, 32, 34 utility priority changing, 183 displaying current configuration, 165 V vdisk.
viewing copy status, 125 visual representation of, 88 volumes, displaying current configuration, 164 write-back cache, 92 write-back cache, enabling and disabling, 91 W warning conditions, displaying for virtual disks, 159 warning events, 219 selecting to monitor, 217 warning policy, snap pool default, 110 options, 111 setting, 111 WBI See Storage Management Utility web page caching mode, configuring, 51 web pages caching, 51 web sites HP storage, 15 websites HP storage, 15 HP Subscriber’s choice, 15 world
HP StorageWorks 2000 Family Modular Smart Array reference guide • August 2008
