Installation and Reference Guide HP StorageWorks Secure Path 3.0F Service Pack 4 for HP-UX 11i v1.0 and 11i v2.
Legal and notice information © Copyright 2009 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents About this guide ................................................................................... 9 Overview ................................................................................................................................... 9 Intended audience ...................................................................................................................... 9 Related documentation ................................................................................................
Secure Path for Active-Passive devices .................................................................................... 35 spmgr commands ........................................................................................................ 36 Common spmgr terms .................................................................................................. 38 Displaying configuration information .....................................................................................
System requirements ........................................................................................................... Installing Secure Path .......................................................................................................... Installing Secure Path on a SAN boot device .......................................................................... Upgrading from the Web ..........................................................................................................
Figures 1 Basic Secure Path Fibre Channel configuration ............................................................ 14 2 Driver model structure ..............................................................................................
Tables 1 Document conventions ............................................................................................. 10 2 Path management behavior summary of Secure Path .................................................... 19 3 Target or LUNS per array comparison chart with dual fabric ......................................... 24 4 Example of a normal array with a single LUN ............................................................. 28 5 spmgr commands .............................................
About this guide This guide describes HP StorageWorks Secure Path for Active-Passive disk arrays and Secure Path for Active-Active disk arrays. It provides information to help you: • • • • Understand Secure Path technology Determine hardware and software prerequisites Install Secure Path software Manage Secure Path NOTE: The HSG family of arrays was last supported in Secure Path HP-UX 3.0F. Any references to support these arrays applies to 3.0F and earlier releases of Secure Path.
Related documentation In addition to this guide, see the HP StorageWorks Secure Path 3.0F Service Pack 4 for HP-UX 11i v1.0 and 11i v2.0 release notes. Document conventions and symbols Table 1 Document conventions Convention Element Blue text: Table 1 Cross-reference links and e-mail addresses Blue, underlined text: http://www.hp.
• • • • • Technical support registration number (if applicable) Product serial numbers Error messages Operating system type and revision level Detailed questions Subscription service HP recommends that you register your product at the Subscriber's Choice for Business website: http://www.hp.com/go/e-updates After registering, you will receive e-mail notification of product enhancements, new driver versions, firmware updates, and other product resources.
About this guide
1 Secure Path for Active-Passive disk arrays HP StorageWorks Secure Path is a server-based software product that enhances HP StorageWorks RAID array storage systems by providing automatic path recovery from server-to-storage-system connection failures. Secure Path supports multiple input/output (I/O) paths between host and storage, which improves overall data availability. If any component in a path between host and storage fails, Secure Path redirects I/O requests to an alternate path.
Figure 1 Basic Secure Path Fibre Channel configuration Secure Path disk arrays enables dual StorageWorks RAID controllers to operate in an Active-Passive mode, referred to as dual-redundant multiple-bus mode. Multiple-bus mode allows each controller to process I/O independently of the other controller under normal operation. A path consists of a unique connection from adapter to device.
• Determines the status of available storage units and physical paths through path verification diagnostics • Monitors and identifies failed paths and failed over storage units • Facilitates static load balancing, which allows movement of devices between controllers • Automatically restores failed-over storage units to repaired paths with auto failback enabled • Implements anti-thrash filters to prevent failover or failback caused by marginal or intermittent conditions • Improves data throughput and increas
Figure 2 Driver model structure Agent The Secure Path agent (spagent) is a daemon process that provides an interface for Secure Path applications and utilities to communicate to the Secure Path drivers. The spagent daemon also provides notification of path-change events through e-mail. You do not need to run the spagent daemon for Secure Path drivers to provide full failover functionality. However, if you want an e-mail notification, then you must run the spagent daemon.
• Active-Active — In the Active-Active model, I/O processing may be routed through both controllers simultaneously, providing better performance in addition to high availability. NOTE: Secure Path automatically retries I/O requests that terminate in error due to ownership transfers. Active-Passive disk arrays also queues new I/O requests until the ownership transfer has completed to ensure data integrity.
When a failure occurs, Secure Path marks the affected path as failed. This removes it from the list of usable paths for the LUN. If no active paths remain on the same controller, Secure Path attempts to move the device to a standby controller. Failback options Secure Path lets you set the path failback option to manual mode or automatic mode. • In manual mode, you must enter a management utility command to restore devices to their preferred path.
Path management behavior Table 2 provides the summary of path management behavior for Secure Path. Table 2 Path management behavior summary of Secure Path Feature Behavior or action Chooses the preferred path to the controller to which the LUN is online. Startup Marks the preferred path active. If no path is marked preferred, selects one and makes it the active path. Marks the active path as failed. Active path failure Redirects I/O through available path.
• Configure SAN switches, as described in Configuring switches. • Configure the StorageWorks RAID array, as described in Configuring the HSG80-based StorageWorks array. • Perform system configuration, as described in System configuration. NOTE: If the array has not been configured with your HP server, complete the procedure described in Installing a new Secure Path configuration.
NOTE: HP recommends this configuration to optimize storage component availability. Configuring switches To configure switches, complete the following steps: 1. 2. Turn on the power to the SAN switches. Log on to the switch. NOTE: For more information, see the Fibre Channel SAN switch management guide that was shipped with your switch. 3.
4. Configure the EMA12000, EMA16000, MA8000, or RA8000 array for fabric connectivity.
8. If the array is in SCSI-2 mode and you want to use the SCSI-3 mode, verify that unit D0 is unassigned. If it is assigned, delete D0 and reassign. To do this, enter the following command: HSG80> delete D0 Go to step 12. 9. If the array is not in SCSI-2 mode, set the array to SCSI-2 mode by entering the following command: HSG80> set this_controller scsi_version=scsi-2 10.
Setting up additional SCSI-2 LUNs The HP-UX sdisk driver allows only 8 LUNs per target. The EMA12000, EMA16000, MA8000, or RA8000 arrays normally present the LUNs under a single target. You can set the array to present a second target of another 8 LUNs for a maximum of 16 LUNs for the array. See Table 3, when deciding which configuration to use.
5. Select two paths that you want to assign to the second target on the configuration map. NOTE: This assignment must allow each adapter to reach opposite controllers (this and other) through opposite switches. For example, in the previous table, select either !NEWCON13 and !NEWCON15, or !NEWCON14 and !NEWCON16.. 6. Enter the following commands for the selected pair: HSG80> set !newcon13 unit_offset=10 HSG80> set !newcon15 unit_offset=10 7. 8.
For example, enter the following command to prefer unit D5 to this controller, and then later set a preferred path to that unit using the Secure Path spmgr utility prefer command: HSG80> set D5 preferred_path=this_controller Using SCSI-3 This section describes the following requirements for SCSI-3: • Secure Path 3.0F SP4 requires the HSG80 controllers to be at ACS firmware 8.7 or later for SCSI3 operation with extended LUN support.
NOTE: On HP servers running Secure Path, the floating nature of the CCL could result in unreliable unit assignments when adding or deleting units. HP recommends that D0 be left unassigned if the CCL is required or that the CCL is disabled if it is not going to be used. Configuring the HSV100/110–based StorageWorks array Before beginning the configuration, collect and record the following host information: • Host LAN name. • Host IP address. • Fibre Channel adapter WWNs configured for Secure Path.
During the boot process, device special files are created for each logical unit configured on the Active-Passive controller and are assigned to each LUN or virtual disk configured on the ActivePassive controller. Because Secure Path is not yet installed, you should see an instance of a LUN for every path to the array. For example, if you have 2 adapters, 2 switches, and 2 connections from each switch to the array, you have 4 distinct device instances (paths) to each LUN that is configured on the array. 2.
Class I H/W path Driver S/W state H/W type Description /dev/td1 fcp 1 0/4/0/0.1 fcp CLAIMED INTERFACE FCP Domain ext_bus 13 0/4/0/0.1.18.255.0 fcpdev CLAIMED INTERFACE FCP Device Interface target 9 0/4/0/0.1.18.255.0.0 tgt CLAIMED DEVICE disk 346 0/4/0/0.1.18.255.0. 0.0 sdisk CLAIMED DEVICE DEC HSG80 /dev/dsk/c13t0d0 /dev/rdsk/c13t0d0 ext_bus 15 0/4/0/0.1.19.255.0 fcpdev CLAIMED INTERFACE target 10 0/4/0/0.1.19.255.0.0 tgt CLAIMED DEVICE disk 348 0/4/0/0.1.19.
HSG80> set !NEWCON2 operating_system=HP (or HP_VSA) HSG80> set !NEWCON3 operating_system=HP (or HP_VSA) HSG80> set !NEWCON4 operating_system=HP (or HP_VSA) NOTE: The array must be running firmware revision ACS 8.7 or later to use the SCSI-3 protocol and the HP_VSA mode. 3. Verify that all connections are now in HP mode by entering the following command: HSG80> show connections 4.
# fcmsutil /dev/td1 get remote all (to form 0x011200 for attached arrays) # fcmsutil /dev/td1 replace_dsk Target # fcmsutil /dev/td1 replace_dsk Target … … # fcmsutil /dev/td1 replace_dsk Target # fcmsutil /dev/tdn get remote all (to form 0x011200 for attached arrays) … … … # ioscan -fn obtain all Target N_Port_ids in the N_Port_id#1 N_Port_id#2 N_Port_id#n obtain all Target N_Port_ids in the For example, if your server has HBAs td0 and td1, then you need to issue the following command for both HBAs: # f
# fcmsutil /dev/td0 replace_disk 0x011000 # fcmsutil /dev/td0 replace_disk 0x011100 NOTE: You must issue these commands for each HBA and for each Target N_Port_id on the server. Installing Secure Path for Active-Passive disk arrays The installation process installs Secure Path drivers, management utilities, and manual pages.
8. Select Secure Path 3.0F SP4 for HP-UX for Active-Passive disk arrays when prompted, and follow the on-screen instructions. The system reboots after successful installation of Secure Path 3.0F SP4 for HP-UX for Active-Passive disk arrays. NOTE: In HP-UX 11i v2.0, the following message is displayed at the end of the installation process: WARNING: The currently running configuration has changes that are being held for next boot. ==> Do you wish to continue? y Enter Y.
• The manual pages for spmgr, spagent, spinit, hsx, and swsp. If you are using StorageWorks Command Console (SWCC) to manage an HSG80 environment, all devices that existed prior to the install are now hidden behind the hsx and swsp drivers, and new names are presented to the sdisk SCSI class driver. To update the new device names, complete the following procedure: 1. Execute the ioscan command to determine the new device names. 2.
4. Determine the hardware path of the standby path for the EVA boot LUN by using the spmgr display and ioscan commands. Set the alternate boot path with this hardware path by using the command setboot –a hardware_path. NOTE: To install Secure Path, follow the instructions in Installing Secure Path or Removing and upgrading Secure Path for Active-Passive disk arrays. Do not use the swinstall command to install the Secure Path depot package.
• Common spmgr terms spmgr commands Table 5 lists the spmgr command options. Their format and syntax are presented and described in the sections following the table.
Command Options or arguments Description Refreshes the array controller serial numbers NOTE: spmgr refreshdisplay no argument Only the controller serial number is updated and not the controller status. This is because the controller status is determined by the status of the paths going through that controller.
• spmgr alias • spmgr unalias • spmgr notify Common spmgr terms Table 6 describes the common spmgr terms. For more Secure Path for Active-Passive terms, see the glossary provided at the end of this guide. Table 6 Common spmgr terms Term Definition Device The standard representation for a device or device link on a server.
Controller state Unknown Description The server cannot communicate with this controller. Path states Table 8 describes the path states reported by Secure Path for 3.0F SP4 for Active-Passive disk arrays. Table 8 Path states for Secure Path 3.0F SP4 Active-Passive disk arrays Path state Description Active The path is currently used for the I/O stream. Available The path is available on the active controller for the I/O stream. Failed The path is currently unusable for the I/O stream.
It is possible in most cases, however, to map the device instance number back to the array unit number by using the path instance number. In most cases, the path instance target or LUN doublet is the octal equivalent of the array unit number as seen by Secure Path for Active-Passive arrays. For example, here is partial output of an spmgr display command: TGT/LUN Device WWLUN_ID H/W_Path #_Paths 0/ 3 c12t0d3 6000-1FE1-0016-6C30-0009-2030-2549-000A 4 255/0.0.
Displaying differences between HSG and HSV controllers All general examples in this document use the HSG80 serialization format and actual HSG80 examples. The HSG80 and HSV110 Array Controllers present objects to Secure Path for Active-Passive arrays in identical ways. Therefore, there are no differences in the way you manage settings, paths, and devices using the spmgr utility.
This section describes the following: • • • • • • • • • # # # # # # # # # spmgr spmgr spmgr spmgr spmgr spmgr spmgr spmgr spmgr display display -a[v] HBA display -c[v] controller_serial_number display -d[v] device_instance display –p path_instance display –r[v] WWNN display -s display -u refreshdisplay # spmgr display When you enter the spmgr display command, all information for the entire configuration is displayed.
# spmgr display -a[v] HBA The -a switch lists HBA (adapter) related information. If a parameter is supplied, it must be the adapter instance number. Syntax: # spmgr display -a –av –a HBA –av HBA When the -a switch is used without a parameter, the display contains a complete list of all HBAs in the Secure Path for Active-Passive configuration from the server where the command is entered. Example: # spmgr display -a Server: hp.mydomain.
# spmgr display -c[v] controller_serial_number The -c switch displays controller-related information. If a parameter is supplied, it must be a controller serial number. The command has four possible forms: Syntax: # spmgr display -c -cv -c controller_serial_number -cv controller_serial_number Example: # spmgr display –c Server: hp.mydomain.
2 c16t0d1 ZG10505167 td0 0/0/255.0.0.1 c4t0d1 WWNN: 5000-1FE1-0010-5B00 Path State: Standby 3 c16t0d1 ZG10505167 td1 0/0/255.0.0.1 c10t0d1 WWNN: 5000-1FE1-0010-5B00 Path State: Standby 4 c16t0d2 ZG10505167 td0 0/0/255.0.0.2 c4t0d2 WWNN: 5000-1FE1-0010-5B00 Path State: Standby 5 c16t0d2 ZG10505167 td1 0/0/255.0.0.2 c10t0d2 WWNN: 5000-1FE1-0010-5B00 Path State: Standby # spmgr display –d[v] device_instance The -d switch displays device-related information.
# spmgr display –d c16t0d2 Server:hp.mydomain.com Report Created: Thu, Sep 13 16:51:43 2004 Command: spmgr display -d c16t0d2 Device: c16t0d2 Status: Operational [4 paths (2/0/2)] Storage: 5000-1FE1-0010-5B00 LUN ID: 6000-1FE1-0010-5B00-0009-1050-6981-0015 Preferred Controller: None HBAs: td0 td1 Example: # spmgr display –dv c16t0d2 Server:hp.mydomain.
spmgr display –r Server: hp.mydomain.com Report Created: Wed, Aug 15 15:19:38 2004 Command: spmgr display –r Storage Systems List = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Storage: 5000-1FE1-0010-5B00 Storage: 5000-1FE1-0010-59F0 Example: # spmgr display –rv Server: hp.mydomain.
ZG10505136, Operational Devices: c21t0d0 c21t0d1 c21t0d2 c21t0d3 c21t0d4 c21t0d5 Path Information: [P] = Preferred Item Device Controller HBAHardware Path Instance = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 0 c21t0d0 ZG10504878 td0 0/0/255.1.0.0 c11t0d0 WWNN: 5000-1FE1-0010-59F0 Path State: Standby 1 c21t0d0 ZG10505136 td0 0/0/255.1.0.0 c12t0d0 WWNN: 5000-1FE1-0010-59F0 Path State: Active 2 c21t0d0 ZG10504878 td1 0/0/255.1.0.
Storage: (fire) 5000-1FE1-0000-1290 LUN ID: 6000-1FE1-0000-1290-5000-1FE1-0000-4321 6000-1FE1-0000-1290-5000-1FE1-0000-4334 Storage: (jazzy) 5000-1FE1-0003-4420 LUN ID: 6000-1FE1-0000-9320-5000-1FE1-9321-5733 # spmgr refreshdisplay This command updates the serial number of all available array controllers. Syntax: # spmgr refreshdisplay alias and unalias commands Secure Path for Active-Passive supports the use of aliases. Aliases replace longer strings with shorter strings.
# spmgr unalias old_name alias_name In the following example, the alias Birdtop, is removed from the alias table. # spmgr unalias Birdtop # spmgr alias Use the spmgr alias command to display the alias table. Syntax: # spmgr alias Example: # spmgr alias Server: hp.mydomain.
• Path verification—The driver checks the state of all possible paths to all units at a selectable period or frequency. By default, the path verification is enabled with a period of 30 seconds. • Auto-restore—The auto-restore command enables the driver to automatically restore paths to their preferred path after a failure and subsequent reinstatement of that path. By default, auto-restore is disabled. Syntax: # spmgr set [option] Options: • -b [WWNN] — Enables or disables load balancing.
NOTE: On a server reboot, it does not matter if auto-restore is on or off, or if paths have been preferred or not. The active path comes up on the last path probed and not necessarily on the preferred path. You must run the spmgr restore all command to restore all active paths to their preferred paths. # spmgr set -b on | off | rr | lb | li | ls WWNN This command enables or disables the load balancing option of the driver.
• If 1 is selected, then 1 is logged. • If 0 is selected, then logging is disabled for that item. The log command includes the following: • • • • # # # # spmgr spmgr spmgr spmgr log -l 0, 1..3 log -c 0,1..3 log -n 0, 3 log # spmgr log -l 0, 1..3 This command sets the level of logging to the syslog of the server. When you select level 1…3, messages of that severity and higher are written to the syslog file. The default setting is 2. # spmgr log -c 0,1..
• # spmgr notify Severity levels Messages from the Secure Path for Active-Passive devices are one of the following three severity levels: • Critical messages are severity level 1. • Warning messages are severity level 2. • Informational messages are severity level 3. The notify command sends event notices from the highest to the lowest level of the severity, marking as follows: • A user with severity level 3 receives level 3, 2, and 1 severity messages.
Command: spmgr notify Current Log Options Severity Mode e-mail_address = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 1 M elizabeth.bradshaw@dork.com 3 M evil.knevil@jump.net 2 M harry.houdini@magic.org = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Path management Secure Path for Active-Passive 3.0F SP4 supports up to 32 paths to an HSG or HSV unit on a storage system.
on that controller as selected. This command indicates which controller to begin selecting and which unit to end marking. Thus if there are three HBAs with paths through that controller, the Secure Path for Active-Passive device will mark one path for the device from one HBA. The overall result is to have identified selected paths for a single unit with this command.
Because Secure Path can have more than one path to each controller, you can further specify a preferred path. To differentiate between the controller unit attribute of preferred_path and the Secure Path preferred path, this document refers to the controller-based preferred-path attribute as the preferred controller.
driver. Therefore, the path may be maintained permanently until removed or another preferred path is selected. prefer and unprefer commands To support adding and removing preferred paths, spmgr provides two commands, spmgr prefer and spmgr unprefer. These two commands each require the path instance parameter. NOTE: The results of these commands are stored in configuration files, and the files persist across reboots.
If load balancing is enabled and you set the path as preferred, the driver marks the path as preferred, but the path is not used as preferred until the load balancing is turned off. If load balancing is enabled and you select a path, the system performs the following actions: • If the path is on the standby controller, I/O moves to the standby controller and the selected path is one of the active paths.
Syntax: # spmgr restore -d device Example: # spmgr restore –d c21t0d2 # spmgr restore -r WWNN This command restores a preferred path to the specified storage system. Syntax: # spmgr restore -r WWNN Example: # spmgr restore –r 5000-1FE1-0010-5B00 # spmgr restore all This command restores all LUNs to their preferred paths and preferred controller. If there is no preferred controller, the current controller becomes the default controller.
# spmgr display -a HBA Use this feature to move I/O to another adapter as the first step to replacing an HBA. Example: # spmgr quiesce -a td0 # spmgr quiesce -c controller_serial_number When this command is invoked, spmgr moves all active I/O using this controller to paths on the other controller of the storage system. The paths of the specified controller are marked as quiesced and no further I/O is sent along that path until the controller returns to service with the restart command.
• • • • # # # # spmgr spmgr spmgr spmgr restart restart restart restart -a HBA -c controller -p path_instance all # spmgr restart -a HBA When this command is invoked, spmgr verifies the existence of the HBA and then uses the HBA to change the state of the paths to available or standby. If the auto-restore feature is enabled and a path using that HBA is the preferred path, the path is made as the active path.
Table 10 describes terms that have special meaning for the spmgr command.
# spmgr add WWLUNID This command verifies the specified unit and adds the unit to the storage system. Syntax: # spmgr add WWLUNID NOTE: WWLUNID is the World Wide LUN ID of the unit to add to the storage system. Example: # spmgr add 6000-1FE1-0005-B480-0009-9341-4111-00FB When this command is invoked, the Secure Path for Active-Passive device searches for the unit and, if it is available, adds it to the data. This command requires that you use administrative commands before and afterwards.
When this command is invoked, the Secure Path for Active-Passive device searches for all unclaimed units associated with the specified array and, if available, adds them to the data. At the same time, the configuration files gets updated. This command requires that you use administrative commands before and afterwards. Before running the spmgr add command, new array units must be found by the system and after running the spmgr add command, units must be claimed by the system.
After the delete, use the following command sequence at least once to delete one or more units from the system.
Syntax: # spmgr clean [option] Options: -d -Cleans LUN configuration data from the stale device list. -r -Cleans all the array configuration data from the stale device list. all -- Full system-wide clean. NOTE: WWNN is the World Wide Node Name of the array, and WWLUNID is the World Wide LUN ID of the device. # spmgr clean -d WWLUNID This command verifies and cleans the indicated unit from Secure Path for Active-Passive configuration.
# spmgr passwd This command provides security on the server side to restrict client access. Syntax: spmgr passwd/password NOTE: You cannot execute the spmgr passwd command remotely. Secure Path for Active-Passive remote management Remote management executes spmgr commands on any server in which Secure Path for Active-Passive disk arrays is installed.
The previous commands must be executed from the server on which Secure Path for Active-Passive array is installed and is to be managed. Remote spmgr execution To execute remote management, enter the following command: spmgr remote_host:command_name Example: # spmgr xyz.hp.com:display The spmgr remote_host:command_name command executes the specified command on the system on which Secure Path for Active-Passive disk arrays is installed, and displays information on the remotely managed host.
Removing Secure Path software You can remove Secure Path by using HP’s SD utility or the System Administration Manager (SAM). When you remove Secure Path, all files, including configuration files, are removed. You can use SAM or enter the following command to remove Secure Path: # swremove –x autoreboot=true CPQswsp,r=* NOTE: After removing Secure Path, you must reconfigure the array for transparent failover mode and restore the server to a single-path RAID storage environment.
2. 3. 4. Perform a complete system backup and document your server file systems, mount points, and device files. Select one of the following SCSI options: • If you want to continue to use SCSI-2 and ACS 8.6 or later, proceed to Upgrading from the Web. • If you are using SCSI-2 and want to use SCSI-3, you must first change the array in SCSI-3 mode. Complete the procedure in Using SCSI-3. Keep the following in mind: • Secure Path 3.0F SP4 requires ACS 8.7 or later for use with SCSI-3 mode.
!NEWCON15 HP_VSA THIS 1offline 0 HOST_ID=5006-0B00-0009-CE61 ADAPTER_ID=5006-0B00-0009-CE60 !NEWCON16 HP_VSA THIS 2offline 0 HOST_ID=5006-0B00-0009-D8C7 ADAPTER_ID=5006-0B00-0009-D8C6 Upgrading from the Web To upgrade your Secure Path for Active-Passive disk arrays software, access the upgrade package available at: http://www.hp.com/country/us/eng/prodserv/storage.html This package is intended as an upgrade only. The patch depot upgrades only Secure Path 3.0A, 3.0 SP3, 3.0B SP3, 3.0C, 3.0D, 3.0E, 3.0F, 3.
Troubleshooting Secure Path for Active-Passive disk arrays You or an HP service representative can perform troubleshooting, depending on your HP service contract. If you are unable to resolve an error condition, ask your HP service representative for assistance. Table 11 lists Secure Path events, sample user notification messages, and sample syslog messages.
Event description User notification messages Syslog messages Occurs when there is a failure to retrieve the persistent data of an array (like load balancing, path verification, path verification period, auto-restore) or a failure while retrieving the persistent data of the swsp interface nodes of the array. CPQswsp: Persistence error. Cause: Insufficient system memory. Failed to retrieve/update the persistent data.
Event description User notification messages Syslog messages Occurs when all the paths to the LUN have failed. All paths for Target/LUN 0/2 (WWID=600508B4000 149200001600000C00000) on Controller P4889B49IM failed. WARNING: CPQswsp: All paths for Target/LUN 0/2 (WWID=600508B400 01490C0001A00001E20000) on Controller P4889B49IM failed Occurs when a new LUN is added or a quiesced LUN is restored to Secure Path. Availability for LUN 600508B40001490C0001A00001E20000 changed to Alive.
Event description User notification messages Syslog messages Occurs usually when the unit which was deleted in the previous boot using the spmgr delete command is not discovered during boot scan of this session. CPQswsp: The unit 600508B400 01492000016000005B0000 is not discovered and not associated with any of the discovered Arrays.
Event description User notification messages Syslog messages Multiple luns [ lun: & lun: ] present at target/lun [target]/[lun] on array .
Event Response action Level Active path changed LOG+CONSOLE+NOTIFY INFORMATIONAL New LUN added LOG+CONSOLE+NOTIFY INFORMATIONAL New path added LOG+CONSOLE+NOTIFY INFORMATIONAL Path verification On/Off changed LOG INFORMATIONAL 78 Secure Path for Active-Passive disk arrays
2 Secure Path for Active-Active disk arrays HP StorageWorks Secure Path 3.0F SP4 for Active-Active disk arrays provides automatic I/O path failover, failback, recovery, and load balancing for host systems configured with multiple host adapters and connections to disk arrays.
• Support for Virtual Device Special File (referred as “vdsf” throughout this guide) for each LUN under Secure Path’s control that are not configured under HP LVM to provide highavailability access to raw devices • Includes a new autopath virtualdsf command to create virtual device files for the LUNs under Secure Path's control • Includes a new autopath monitor command to start the monitor deamon to control the failback and pro-active path monitor features for faster path failover and recovery.
NOTE: All persistent data are moved to KRS from the /opt/HPswsp/perset data file. The vdsf is a link to the physical path of the device configured under HP LVM and dynamically points to the next active path of the device (when the configured primary path fails and the system reboots). All the Secure Path commands except autopath add command, supports vdsf as a command argument and provides all the operations of Secure Path commands.
Automatic failover In the event of a failure of any part of a path between the disk arrays and a server, Secure Path automatically switches to an alternate path, dropping the failed path out of the I/O rotation without any loss of data. The failover is not visible to applications, so normal operation continues without downtime.
NOTE: You must have root account privileges to install Secure Path software. System requirements To install Secure Path, your system must conform to the following requirements: • HP-UX OS 11i v1.0 or11i v2.0 64-bit operating system • Administrator root access to the host system • SCSI ULM Services B.11.11.01 for HP-UX 11i v1.0 For specific installation requirements for your system, contact your HP account representative. NOTE: See the HP StorageWorks Secure Path 3.0F Service Pack 4 for HP-UX 11i v1.
changes.log file is copied into the /Autopath directory, and the master, system, and mod.o files are copied into the /HPswsp directory. Installing Secure Path on a SAN boot device Complete the following steps to install Secure Path for the first time on a SAN boot device: 1. 2. 3. 4. Install HP-UX 11i v1.0 or 11i v2.0 on the Active-Active disk arrays LUN and boot the system. Install Secure Path on the boot LUN. Configure LVM with alternate physical volume paths to the primary boot volume path.
HPswsp A.3.0F.04F.00F HP StorageWorks Secure Path Device Driver and utilities for Active-Active disk arrays. 6. Run the autopath discover and autopath retrieve command to complete the upgrade and to get all the persistence settings. NOTE: Configuration setting are migrated across upgrades only for 3.0F and later releases. The configuration settings are lost while migrating from versions prior to Secure Path 3.0F. NOTE: For XP arrays: Starting with Secure Path 3.
• autopath set_lbpolicy command • autopath set_prefpath command autopath delete command The autopath delete command deletes a device, LUN, array, or an array type from Secure Path's control. This command succeeds only if the LUN is not busy (for example, when there is no I/O happening and when the LUN is not mounted or open). You can also use the autopath delete command to remove those LUN, array, or an array type that are added to the configuration, but not discovered by Secure Path.
autopath delete -l • Example:: autopath delete -l 6005-08B4-0001-499C-0002-0000-0005-0000 • Deleting an array using the array type: • Syntax: autopath delete —r • Example:: autopath delete -r EVA-AA NOTE: The autopath delete command fails if: • Device is configured under crashconf (dump). • A failed device is opened or mounted.
autopath add -a autopath add -a 5005-08B3-0091-16A0 The autopath add command succeeds even if the LUN is in use. This command removes the LUN WWID entry from the unattached list. autopath set command The autopath set command sets the configuration parameters, including the load balancing policy, retry timeouts, path verification interval, and read optimization for a Secure Path device.
# autopath set -a 5000-1FE1-0027-0CF0 -o ON # autopath set -a 5000-1FE1-0027-0CF0 -p 00:50 NOTE: The pro-active path monitoring feature gets triggered whenever an automatic path failover happens for all the arrays, even though the feature is disabled for one or all the arrays. NOTE: • Supports timeout feature for VxFS file system only • If the file system changes from VxFS to HFS, the autopath set -t command will not work. The HFS file system defaults remain in effect.
================================================================== HPswsp Version : A.3.0F.04F.00F ================================================================== Array IDs ================================================================== 060B-0000-14E2-E050 060B-0000-1534-1C50 ================================================================== Details of all LUNs connected from an array The autopath display -r command displays details of all LUNs connected from an array.
Auto Discover : ON ================================================================== Array Type : EVA-AA Array WWN : 5000-1FE1-0027-0CF0 Read Optimize : ON Path Verification Period : 00:10 ================================================================== List of array controllers connected to the host The autopath display -c command displays a list of controllers connected to the host.
================================================================== Deleted Arrays ================================================================== Array ID Array Type -----------------------------------------------------------------5000-1FE1-5000-B5D0 EVA-AA -----------------------------------------------------------------================================================================== Array Type : EVA-AA Array ID : 5000-1FE1-0027-0CF0 --------------------------------------------------------------
Display LUN info using a LUN WWID The autopath display -l command displays LUN info of the LUN using the LUN WWID. Syntax: autopath display -l Example: aphn5# autopath display -l 6005-08B3-0091-16A0-BFA5-F0A6-7FCE-0064 ================================================================== HPswsp Version : A.3.0F.04F.
/dev/dsk/c52t0d0 /dev/dsk/c51t0d0 Active Active ================================================================== ================================================================== Lun WWN : 6005-08B3-0091-16A0-6328-4F90-E473-005F Virtual Device File : /hpap/dsk/hpap7 Load Balancing Policy : Shortest Queue Length Lun Timeout : Infinite Retry (-1) ================================================================== Device Path Status ================================================================== /dev/ds
autopath virtualdsf command The autopath virtualdsf command creates and updates the virtual device special files for the LUNs. Syntax: #autopath virtualdsf [clean] The virtual device files are created for all the LUNs under Secure Path's control. The virtual device files for all the undiscovered, deleted, and collided LUNs gets deleted.
# autopath monitor description : starts the monitor deamon to control the fail-back and pro-active path monitor features NOTE: For more information, see I/O load balancing . autopath help command The autopath help command lists all of the autopath commands. It also displays syntax of an autopath command and its usage. Syntax: # autopath help [command] Example: # autopath help usage: autopath command: add : add a LUN/Array-Type to SecurePath's control.
usage: autopath add {option} {device path | WWLUNID | Array Type} option: -l -r -- for entering the WWLUNID -- for entering the Array Type device path : WWLUNID : Array Type : -- device special file e.g./dev/dsk/c#t#d# -- World Wide Node Name of the LUN -- Array Type( XP/VA/EVA-AA) Example: # autopath help delete description: delete LUNs from the SecurePath's active device list usage: autopath delete device path : -- device special file e.g.
autopath retrieve command The autopath retrieve command restores the Secure Path load balancing policy, preferred path settings, and deleted LUNs across Secure Path upgrades. Retrieval of settings may not be effective if you have made SAN configuration changes for the host. Use the autopath retrieve command for retrieving persistence data after upgrade. Syntax: autopath retrieve Example: # autopath retrieve NOTE: Starting with 3.0F SP2, the command 'autopath retrieve' is obsolete.
Example: # autopath set_prefpath /dev/dsk/c4t0d0 Troubleshooting Secure Path for Active-Active disk arrays You or an HP service representative can perform troubleshooting, depending upon your HP service contract. If you are unable to resolve an error condition, ask your HP service representative for assistance. This section describes the following: • Recovering after a failure • Secure Path messages Recovering after a failure When a path fails, it is no longer used by Secure Path.
Event Syslog message NO AUTOPATH DEVICE AUTOPATH : no Secure Path device found SET POLICY SUCCESS AUTOPATH : load balance policy set successfully for 0x1f040000 SET NEXT PATH AS PREF PATH AUTOPATH : path is not up, so the next active path is set as Preferred Path SET PREFERRED PATH SUCCESS AUTOPATH : Preferred Path set successfully for 0x1f040000 NO ALTERNATE LINKS PRESENT AUTOPATH : no alternate links present MONITOR IOCTL FAILED AUTOPATH : monitor command failed INVALID DEVICE ENTRY AUTOPAT
Event Syslog message UNINSTALL IN PROGRESS AUTOPATH: un-install in progress. Aborting the command execution UNINSTALL ABORT AUTOPATH: cannot un - install hpap module, one of the paths on which I/O / Open was issued originally is failed UNINSTALL ABORT AUTOPATH: Cannot un - install hpap module, The following Device(s) have I/O's Queued DEVICE ACCESS FAILED MESSAGE AUTOPATH : Warning: Unable to access device MAXIMUM LUN COUNT REACHED MESSAGE AUTOPATH: Warning: LUN count reached maximum value of %d.
Secure Path for Active-Active disk arrays
Glossary This glossary defines terms used in this guide or related to this product and is not a comprehensive glossary of computer terms. controller A controller is a hardware device that facilitates communication between a host and one or more LUNs organized as an array. The HSG80 and HSV110 controllers are supported for use with Secure Path. controller states • critical−Reported for a controller pair bound in multi-bus failover mode when only one of the controllers is available.
port a The relative number of an HBA. A specific port number is determined according to its order of discovery by the Windows operating system and includes SCSI, Fibre Channel, and IDE adapter types. SAN Storage Area Network. A configuration of networked devices for storage. state State is an attribute that describes the current operational condition of an object. See also Path, Path States, Controller States, and Device States.
Index Symbols # spmgr add WWLUNID, 64, 64 client add, 68 client delete, 68 display (default), 42 display -s, 48 display -u, 48 log -c, 53 log -l, 53 log -n, 53, 53 notify, 54 notify add, 54 notify delete, 54 password, 69 quiesce - a controller, 61 quiesce - a HBA, 60 quiesce - c controller, 61 quiesce - c path_instance, 61 quiesce - p path_instance, 61 refreshdisplay, 49 restart -p path_instance, 62 restart -a HBA, 62 restart -c controller, 62 restart -p path_instance, 62 restore all, 60 restore all paths t
display command, 41 # spmgr, 42 log settings, 53 displaying alias, an, 50 configuration information, 38 path states, 45 documentation providing feedback, 11 documentation, array configuration, 22 drivers HPswsp, 85 hsx, 15 sdisk, 24 swsp, 15 dual RAID controllers, 15 I E L enable notification, logging, 53 enterprise virtual array array, configuring, 27 HSV element manager, 27 upgrading Secure Path, 70 EVA3000, overview, 13 EVA5000, overview, 13 F failback options, 18 failed state, 39 failover, 17, 82 f
P path definition management behavior, 19 verification, 18 management, 55 management behavior summary, 19 selecting, controller_serial_number, 55 states, 39 verification defined, 18 interval, setting, 52 parameters, 51 setting, 52 path_instance quiesce, 61 restart -p x11 x11 # spmgr, 62 select, 56 paths load balancing and active paths, 58 restoring to device, 60 restoring to storage system, 60 selecting, 55 PREFERRED_PATH unit attribute, 14 preferring, unit to a controller, 25 Q quiesce -a x11 # spmgr, 60
spmgr alias, 49 commands, 36 common terms, 38 controller states, 39 display -s, 48 display -u, 48 displaying an alias, 50 log -c, 53 log -l, 53 log -n, 53, 53 notify delete, 54 notify add, 54 notify display, 54 overview, 35 quiesce - a controller, 61 quiesce - a HBA, 60 quiesce - c controller, 61 quiesce - p path_instance, 61 refreshdisplay, 49 remote management, 68 restart -a HBA, 62 restart -c controller, 62 restart -p path_instance, 62 restore all, 60 restore all paths to device, 60 restore all paths to
