Installation and Reference Guide hp StorageWorks Secure Path v3.0C for Linux and Linux Workgroup Edition Product Version: 3.0C Third Edition (February 2004) Part Number: AA–RU7VD–TE This guide describes the HP StorageWorks Secure Path for Linux and Linux Workgroup edition software. It includes information about Secure Path technology, installation procedures, and management commands.
© Copyright 2003–2004 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 Contents About this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Intended audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Related documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 2 Hardware Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 Hardware setup overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Required components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Installing and configuring the storage systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Setting storage system parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The set command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . # spmgr set -a on | off [WWNN] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . # spmgr set -b on | off [WWNN] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . # spmgr set -p on | off [WWNN] .
Contents The passwd Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 spmgr passwd agent_password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 5 Removing/Upgrading Secure Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93 Removing Secure Path software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 4 5 6 7 8 9 10 11 12 Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Spmgr commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Spmgr common terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Controller states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 8 Secure Path v3.
about this guide About this Guide This installation and reference guide provides information to help you: ■ Understand Secure Path Technology About this Guide ■ Determine hardware and software prerequisites ■ Install Secure Path software ■ Manage Secure Path using spmgr ■ Contact technical support for additional assistance “About this Guide” topics include: ■ Overview, page 10 ■ Conventions, page 11 ■ Getting help, page 14 Secure Path v3.
About this Guide Overview This section covers the following topics: ■ Intended audience ■ Related documentation Intended audience This book is intended for use by system administrators who are experienced with the following: ■ Linux operating systems ■ EVA5000 ■ EVA3000 ■ RA/MA8000 ■ ESA/EMA12000 ■ MSA1000 Related documentation In addition to this guide, HP provides the HP StorageWorks Secure Path v3.0C for Linux and Linux Workgroup Edition Release Notes. 10 Secure Path v3.
About this Guide Conventions Conventions consist of the following: ■ Document conventions ■ Text symbols ■ Equipment symbols Document conventions This document follows the conventions in Table 1.
About this Guide Tip: Text in a tip provides additional help to readers by providing nonessential or optional techniques, procedures, or shortcuts. Note: Text set off in this manner presents commentary, sidelights, or interesting points of information. Equipment symbols The following equipment symbols may be found on hardware for which this guide pertains.
About this Guide Power supplies or systems marked with these symbols indicate the presence of multiple sources of power. WARNING: To reduce the risk of personal injury from electrical shock, remove all power cords to completely disconnect power from the power supplies and systems. Any product or assembly marked with these symbols indicates that the component exceeds the recommended weight for one individual to handle safely.
About this Guide Getting help If you still have a question after reading this guide, contact an HP authorized service provider or access our web site: http://www.hp.com. HP technical support Telephone numbers for worldwide technical support are listed on the following HP web site: http://www.hp.com/support/. From this web site, select the country of origin. Note: For continuous quality improvement, calls may be recorded or monitored.
Secure Path Technology 1 HP StorageWorks Secure Path is a server-based software product that enhances StorageWorks RAID array storage systems by providing automatic path recovery from server-to-storage system connection failures. Secure Path supports multiple 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 pending and subsequent I/O requests to an alternate path.
Secure Path Technology Overview Note: You must have root privileges to perform Secure Path installation or spmgr commands Secure Path is a high-availability software product that manages and maintains continuous data access to the following StorageWorks storage systems: ■ RA8000 ■ ESA12000 ■ MA8000 ■ EMA12000 ■ EVA5000 ■ EVA3000 ■ MSA1000 Secure Path eliminates the RAID controller, HBA, and interconnect hardware (cables, switches, and connectivity devices) as single points of failure in the
Secure Path Technology Figure 1 illustrates basic Secure Path hardware configurations. The physical connections define two separate paths. Each path originates at a unique SAN host bus adapter on a Linux server and ends at a port on a separate RAID controller on the storage system.
Secure Path Technology For HSG80, EVA5000, and EVA3000 storage systems, Secure Path enables dual StorageWorks RAID controllers to operate in an active/active LUN ownership implementation, 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.
Secure Path Technology Features Secure Path provides the following features: ■ Allows StorageWorks dual-controller RAID systems and host servers equipped with multiple HBAs redundant physical connectivity along independent Fibre Channel fabric paths ■ Monitors each path and automatically reroutes I/O to a functioning alternate path if a component failure occurs ■ Determines the availability of storage units and physical paths through path verification diagnostics ■ Monitors and identifies failed pat
Secure Path Technology Software components This section describes the Secure Path Software Kit for Linux software components. Drivers Secure Path drivers consists of the following three modules: ■ swsp_mod.o module—A virtual HBA driver that takes requests from Linux SCSI subsystem mid-layer and passes the requests to the hsx_mod.o module with the help of the path_mod.o modules. ■ path_mod.o module—Required to allow the hsx and swsp modules to communicate in the kernel. ■ hsx_mod.
Secure Path Technology Agent The Secure Path agent (spagent) is a daemon process that provides an interface for Secure Path applications and utilities to communicate to the multipath drivers. The spagent also provides notification of path change events through e-mail. The spagent is not required to be running for Secure Path drivers to configure and provide full failover functionality. However, it must be running if e-mail event notification is desired.
Secure Path Technology Controller ownership Storage systems that are multiple-bus capable generally contain a pair of redundant controllers and support one of the following basic operational models: ■ The MSA1000 uses the active/passive operational model. In the active/passive model, all storagesets are assigned ownership to one controller of the pair for I/O processing. The other controller is standby and is available as a substitute in case of failure on the original.
Secure Path Technology Path definition Within Secure Path, a path is defined as the collection (configuration) of physical interconnect components including HBAs, switches, cables, RAID controllers, and the ports on the controllers. Because the Secure Path driver component is positioned between the HBA driver and the system SCSI disk driver, the Secure Path driver can only distinguish physical paths when elements of the SCSI equivalent address are different.
Secure Path Technology Secure Path operation Path failover occurs automatically when a selected set of error conditions is detected. Secure Path normally performs path failover only when user I/O is active or if path verification is enabled. However, it is possible for Secure Path Manager to show some units with a common failed path in the failover state, while other units remain accessible through that path. Units remain in the failed path if there is no I/O or until they are polled.
Secure Path Technology Load balancing Secure Path supports the Load Balancing attribute. When enabled, Load Balancing allows multiple paths between a host and a specific storageset to be used in a round robin fashion. Using multiple paths spreads the load across all components in the RAID storage system. Load Balancing may not be used in environments that use device reservations as a lock mechanism because the RAID array controllers enforce reservations on a per-port basis.
Secure Path Technology Path management behavior summary Table 2 provides a summary of the path management behavior of Secure Path. Table 2: Path management behavior summary Feature Startup Behavior/Action 1. Chooses the Preferred path to the controller on which the LUN is online. 2. Marks the Preferred path Active. If no path is marked Preferred, select one and make it the Active Path. ■ Marks the Active path as Failed and fails to the Available path. ■ Redirects I/O through available paths.
Secure Path Technology Table 3 shows the default values with which Secure Path is enabled.
Secure Path Technology 28 Secure Path v3.
Hardware Setup 2 This chapter provides the following Secure Path hardware setup information: ■ Hardware setup overview, page 30 ■ Installing and configuring the storage systems, page 31 — Configuring StorageWorks enterprise virtual arrays, page 31 — Configuring StorageWorks MA8000/EMA12000 RAID arrays, page 33 — Configuring StorageWorks Modular Smart Array 1000, page 37 — Connecting storage to the server, page 39 Secure Path v3.
Hardware Setup Hardware setup overview The following procedure presents an overview of the hardware setup: 1. Ensure that all users have logged off the server and all array file systems have been backed up and unmounted, prior to setting up your hardware. 2. Verify that all the following hardware and software prerequisites have been met: — Supported Host Bus Adapters (HBAs) must be installed and working properly. — Supported version of Linux and with all required patches loaded.
Hardware Setup Installing and configuring the storage systems This section describes the steps required for installing and configuring RAID systems and Linux servers for Secure Path operation in fabric (FC-SW) mode. This section is divided into three parts, one for EVA5000/EVA3000 storage systems, one for setting up HSG80-based storage systems, and one for setting up the MSA1000-based storage systems. Before proceeding, you should have all Fibre Channel adapters installed in your Linux server.
Hardware Setup Note: Refer to the for HP StorageWorks Command View EVA online Help for information about these procedures. All of these procedures need to be completed for your host to use the virtual disks. 1. Initialize the storage system and create disk groups. When you first view the EVA5000/EVA3000 from the Command View EVA software, the storage pool is presented as uninitialized storage.
Hardware Setup Configuring StorageWorks MA8000/EMA12000 RAID arrays This section provides the steps to install and configure HSG80-based storage arrays. Caution: If you are installing Secure Path on an existing RAID storage system, stop all I/O to the RAID system and skip steps 1 and 2 below. For each RAID system in a production environment being converted to Secure Path operation, also make sure that all users have logged off the Linux servers.
Hardware Setup 4. Verify the configuration of the RAID system by entering either of the following commands: CLI > show this_controller CLI> show other_controller An example of the controller output (with reference line numbers appended) follows: Controller: 1. HSG80 ZG90305234 Software V86F-4, Hardware E08 2. NODE_ID 3. = 5000-1FE1-0000- 8920 ALLOCATION_CLASS = 0 4. SCSI_VERSION 5. = SCSI-3 Configured for MULTIBUS_FAILOVER with ZG90811309 In dual-redundant configuration 7.
Hardware Setup Mirrored Cache: 24. 128 megabyte write cache, version 0012 25. Cache is GOOD 26. No unflushed data in cache 27. Battery: 28. NOUPS 29. FULLY CHARGED 30. Expires: 16-DEC-2001 31. a. Configure the RAID system controllers for Multiple-bus Failover Mode, if the controllers are in Transparent Failover Mode (see line 6 of the example controller output). This procedure is documented in “Changing from Transparent Failover to Multiple-bus Failover mode” on page 108.
Hardware Setup An example of the show units output follows: D11 DVGRPR0 LUN ID: (partition) 6000-1FE1-0000-8920-0009-9030-5234-006E NOIDENTIFIER Switches: RUN NOWRITE_PROTECT READAHEAD_CACHE READ_CACHE WRITEBACK_CACHE MAXIMUM_CACHED_TRANSFER_SIZE = 32 Access: ALL State: ONLINE to this controller Not reserved NOPREFERRED_PATH Size: 8533749 blocks Geometry (C/H/S): (1680 / 20 / 254) As shown in this example, the state of the unit is online to this_controller and no preferred path has been assigne
Hardware Setup Configuring StorageWorks Modular Smart Array 1000 This section provides the steps required to install and configure MSA1000-based storage arrays. 1. Verify that you have a supported server with a supported Linux operating system installed prior to configuring your MSA1000. 2. Verify that a supported Fibre Channel Host Bus Adapter (HBA) is installed. 3. Install the MSA1000 Storage System in a rack, following instructions found in your rack documentation. 4.
Hardware Setup 13. Click Netscape and connect to http://127.0.0.1:2301. Refer to the documentation supplied in your Modular Smart Array 1000 Setup and Management kit for further details. Note: Before Installing Secure Path for Linux, you must enable the proper host mode setting using the ACU utility. Refer to the ACU documentation for steps to change the host mode. 38 Secure Path v3.
Hardware Setup Connecting storage to the server This section describes how to connect configured storage to your server. For more information on supported configurations, access the HP web site at: http://hp.com/country/us/eng/prodserv/storage.html. 1. Cable the Fibre Channel adapter and the RAID storage system controllers to the SAN Switches and HBAs, as shown in Figure 3. 2. Choose from the following options: a.
Hardware Setup 7 1 3 9 5 10 2 4 6 8 SHR-2462A Figure 3: Cabling two RAID controllers and two SAN switches 1 Top Controller 6 Bottom Controller, port 2 (to host via top switch) 2 Bottom Controller 7 FC cable to host bus adapter A 3 Top Controller, port 1 (to host via top switch) 8 FC cable to host bus adapter B 4 Bottom Controller, port 1 (to host via bottom switch) 9 SAN Switch (top) 5 Top Controller, port 2 (to host via bottom switch) 10 SAN Switch (bottom) 3.
Hardware Setup 4. Verify that the correct WWPNs have been mapped to targets using the following command. The correct WWPN is shown in the output displayed on line 2. Note: This example shows only partial output from the command. CLI> show this Host PORT_1: 1. Reported PORT_ID = 5000-1FE1-0000-8923 2. PORT_1_TOPOLOGY = FABRIC (fabric up) 3. Address = 021000 Host PORT_2: 4. 5. Reported PORT_ID = 5000-1FE1-0000-8924 6. PORT_2_TOPOLOGY = FABRIC (fabric up) 7.
Hardware Setup 6. Use the following command sequence after rebooting to check the RAID storage system to ensure that the connection operating system setting is Linux: a.
Installing Secure Path Software 3 This chapter describes how to install a new Secure Path software configuration. It contains the following information that is required for proper Secure Path installation and operation: ■ Installation prerequisites, page 44 ■ Installing Secure Path, page 45 ■ Configuration files added by Secure Path, page 54 ■ Using Secure Path persistence software, page 55 Note: Before attempting to install Secure Path software, read the Release Notes.
Installing Secure Path Software Installation prerequisites Note: HSG80 controllers are not supported with 64-bit machines. Before installing Secure Path v3.0C, verify the following requirements: 44 ■ The prerequisites listed in the HP StorageWorks Secure Path v3.0C for Linux Release Notes have been met. ■ The procedures in “Hardware Setup” on page 29 have been performed. ■ At least one unit is configured on the RAID storage system and is visible to the server from at least two paths.
Installing Secure Path Software Installing Secure Path Secure Path installation has been automated to use the Red Hat Package Management (RPM) utility installation. If the installation process cannot complete for any reason, you will be instructed how to proceed manually. Every effort has been made to make your Secure Path software installation as simple and straightforward as possible, but given the large variations possible in system setup, manual intervention may be required.
Installing Secure Path Software 3. Choose one of the following installations based on your operating system parameters: — To install Linux v3.0C or Linux v3.0C Workgroup Edition on 32-bit Red Hat operating systems, enter a command similar to the following: # rpm -ivh Secure-Path-3.0C.noarch.rpm For example: # rpm -ivh Secure-Path-3.0CFull-4.0.noarch.rpm — To install the Linux v3.0C or Linux v3.
Installing Secure Path Software The RPM checks to ensure that the QLA2300 module is loaded. If the QLA2300 module is not loaded, the following error message displays (Secure Path v3.0C for Linux is used as the example): ************************************************************ QLA2300 must be loaded to install this kit. ************************************************************ error: execution of %pre scriplet from Secure-Path -3.0CFull -3.
Installing Secure Path Software Note: The following error messages apply to 32-bit systems only. If you try to install the 32-bit RPM on a SUSE/UnitedLinux 64-bit system, the following message displays: ************************************************************ This is IA64 based system. This installation only supports 32bit based systems. Exiting.....
Installing Secure Path Software Note: The following error messages apply to 64-bit configurations only. I — If you do not have an IA64 base system, the following message displays: ************************************************************ This is an IA64 based system. This installation only supports 32bit based systems. Exiting... ************************************************************ — For Red Hat 3.0 IA64 with an unsupported errata version, but with a proper kernel version of 2.4.21-9.
Installing Secure Path Software — For the SUSE/UnitedLinux IA64 operating systems, if the kernel version is not valid the following message displays: ************************************************************ You do not have a supported version of this kernel (2.4.21-112-itanium2-smp). If you want to install anyway, please run the rpm with the --force command. (e.g. rpm -ivh --force Please see documentation for currently supported kernel versions. Exiting...
Installing Secure Path Software Automatically installing Secure Path You can choose to automatically install the software as follows: 1. Insert the Secure Path v3.0C CD-ROM into the CD-ROM drive. A sample command follows: # mount /dev/cdrom /mnt/cdrom 2. Enter the following command: # ./install_SPlinux.sh The automatic installation scans the system to determine what OS and kernel is running and prompts you for verification.
Installing Secure Path Software If you chose to continue, the installation is automatic from this point to completion. — For 32-bit SUSE/ UnitedLinux operating systems, the system displays the following message if the errata version is not valid: Your system is running UnitedLinux/SuSe 32bit. The kernel version is 2.4.21-169-smp. The system is not running the proper kernel (2.4.21-141-smp). The system is not running a proper kernel version.
Installing Secure Path Software If you choose N, the following message displays: You have chosen not to continue. Exiting... — The script displays the following for 32-Bit RHEL AS 3.0 if the errata version is not valid: Your system is running RHEL AS 32bit. The kernel version is 2.4.21. The system is not running the errata 9kernel (2.4.21-9.EL). The system is not running a supported errata version.
Installing Secure Path Software Configuration files added by Secure Path Table 4 lists the files added as part of the Secure Path v3.0C installation. Table 4: Configuration files File name Description hsx.conf Used by spagent to make preferred path settings persistence across reboots. Whenever you modify the preferred path setting, spagent modifies hsx.conf. After rebooting, spagent reads the file and sends an appropriate IOCTL call to mark the path to Preferred. swsp.
Installing Secure Path Software Using Secure Path persistence software After you have rebooted the system, you can find symbolic links to real devices in the /dev/spdev directory. These links were created by the Secure Path Persistence Software (sps), a LUN persistence program written to work with Secure Path. All disk operations should be done via these links and not the real device name. For a detailed explanation of sps and LUN persistence, refer to “Fibre Channel Device Software” on page 113.
Installing Secure Path Software 56 Secure Path v3.
Managing Secure Path 4 This chapter describes the user interface for the Secure Path v3.0C Management utility spmgr.
Managing Secure Path Secure Path Manager overview The Secure Path Manager (spmgr) utility lets you monitor and manage devices, storage systems, and paths to units that are in the Secure Path configuration. It also lets you modify the configuration to repair, replace, or reconfigure. The spmgr utility relies on spagent to handle calls to the driver (swsp). Adding or deleting LUNs Secure Path v3.0C for Linux does not support adding and deleting LUNs dynamically.
Managing Secure Path Spmgr commands Table 5 lists the spmgr command options. Their format and usage are presented and described in the sections following the tables. Table 5: Spmgr commands Command Options / Arguments Description spmgr alias alias_name old_name no argument Assigns an alias to an object.
Managing Secure Path Table 5: Spmgr commands (Continued) Command Options / Arguments Description spmgr restore -d device -r WWNN all Restores one or more devices to their preferred I/O path. spmgr select -a adapter [-d device] -c controller_ser_num [-d device] -p path_instance Selects a path for I/O. spmgr set -a on | off [WWNN] -b on | off [WWNN] -f interval -p on | off [WWNN] Enables or disables special driver functionality. spmgr unalias alias_name old_name Deletes an alias.
Managing Secure Path Spmgr common terms Table 6 describes the common spmgr terms. For a more complete list of Secure Path glossary terms, refer to page 119 in this book. Table 6: Spmgr common terms Term Definition Device The standard representation for a device or device link on a server, for example, spa Logical Unit A device that is managed by Secure Path and identified by its 32-digit World Wide LUN Identifier (WWLUNID). Adapter The operating system ID of the HBA.
Managing Secure Path Displaying configuration information Controller states Table 7 lists the possible controller states and their descriptions. Table 7: Controller states Controller states Description Failed This state may mean a failed or offline condition because the server cannot communicate with the other controller at this time. Operational The controller is available with a good status. Unknown The server cannot communicate with this controller.
Managing Secure Path Device states Table 9 lists and describes device states. Table 9: Device states and description Device States Description Critical Only one path remains available to the storage unit. Degraded At least one or more paths are failed to the storage unit. Operational All paths are available to the storage unit. Unknown Unable to communicate with the unit. This may indicate no available path or a failed device.
Managing Secure Path HSV110/HSV100 World Wide Node Name (WWNN): 5000-1FE1-0015-0AE0 World Wide LUN ID(WWLUNID): 6005-08B4-0001-40BF-0000-A000-1234-0000 Controller Serial Number: P4889B29LC01J In the HSG80 and HSV110/HSV100 examples, the location of the sequence 1234 in the WWLUNID examples is unique to each LUN and is in a different position in the array types.
Managing Secure Path For each of these command switches, this section presents: ■ Description ■ Syntax # spmgr display When you enter spmgr display, all information for the entire configuration is displayed. The amount of information displayed depends on the number of HBAs, storage systems, and paths to a unit on each storage system. The full display derives from the component portions described in this section.
Managing Secure Path P56350A9IMN19M no hsx_mod-1-0-0-2 Controller 2300-1 Path_Instance HBA no Preferred? Path_Status P56350A9IMN0XI YES hsx_mod-2-0-0-2 TGT/LUN 0/ 2 Device sph Controller 2300-2 no WWLUN_ID #_Paths HBA no hsx_mod-1-0-0-3 Path_Instance 2300-1 HBA Device 3 spi 2300-2 Path_Status Active #_Paths 6008-05F3-0000-6FD0-AA77-454F-E3C4-0023 Path_Instance hsx_mod-1-0-0-4 HBA Preferred? Path_Instance 2 Path_Status no 2300-1 HBA P56350A9IMN0XI hsx_mod-2-0-0-4 no WW
Managing Secure Path Example: # spmgr display -a Server: sensodyne Report Created: Fri, Jul 12 10:57:12 2002 Command: spmgr display -a Adapters in the Secure Path Configuration = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 2300-1, 2300-2 When the -av switch is used, the display contains a list of all adapters in the Secure Path configuration.
Managing Secure Path Example: # spmgr display -av 2300-0 Server: swsp91 Report Created: Thu, Oct 02 15:58:32 2002 Command: spmgr display -av 2300-0 = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Adapter: 2300-0 Version: v.6.04.00 # 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.
Managing Secure Path Controller: P56350A9IMN0XI Status: Operational Vendor: HP WWNN: 5008-05F3-0000-6FD0 WWPN1: 50001FE15000388C HBAs: 2300-1, 2300-2 Example: # spmgr display –c controller_serial_number Server: sensodyne Report Created: Fri, Jul 12 11:05:30 2002 Command: spmgr display -c P56350A9IMN0XI = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Controller: P56350A9IMN0XI Status: Operational Vendor: HP WWNN: 5008-05F3-0000-6FD0 HBAs: 2300-2 Example: # spmgr display -cv P5635
Managing Secure Path # spmgr display –d[v] [device] The -d switch displays device related information. If a parameter is supplied, it must be a device.
Managing Secure Path Note: Secure Path displays path states using the following convention: [total number of paths (active/failed/standby)]. Actual numerical equivalents replace the text.
Managing Secure Path HBAs: Item 2300-2 2300-4 Device Controller HBA Instance = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 0 spa ZG10506937 2300-2 hsx_mod-2-0-0-1 WWPN: 50001FE10015A374 1 spa ZG10707577 2300-2 WWPN: 50001FE10015A372 2 Path State: Active spa hsx_mod-2-0-1-1 Path State: Standby ZG10707577 2300-4 WWPN: 50001FE10015A374 hsx_mod-4-0-0-1 3 spa ZG10506937 2300-4 Path State: Standby WWPN: 50001FE10015A372 hsx_mod-4-0-1-1 Path State: Available # spmgr di
Managing Secure Path Example: # spmgr display –r Server: sensodyne Report Created: Fri, Jul 12 11:20:10 2002 Command: spmgr display -r = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Storage: 5008-05F3-0000-6FD0 Example: # spmgr display –rv Server: sensodyne Report Created: Fri, Jul 12 11:21:13 2002 Command: spmgr display -rv = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Storage: 5008-05F3-0000-6FD0 Load Balance: Off Auto-restore: Off Path Verify: On HBAs
Managing Secure Path Example: # spmgr display -rv WWNN Server: sensodyne Report Created: Fri, Jul 12 11:22:00 2002 Command: spmgr display -rv 5008-05F3-0000-6FD0 = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Storage: 5008-05F3-0000-6FD0 Load Balance: Off Path Verify: Auto-restore: Off On HBAs: 2300-1 Verify Interval: 30 Controller: 2300-2 P56350A9IMN19M, Operational P56350A9IMN0XI, Devices: spf TGT/LUN Device 0/ 0 spg spf Controller Operational sph WWLUN_ID 6008-0
Managing Secure Path P56350A9IMN19M no hsx_mod-1-0-0-3 Controller 2300-1 Path_Instance HBA P56350A9IMN0XI hsx_mod-2-0-0-3 no Preferred? Standby Path_Status YES 2300-2 no Active The alias and unalias commands Secure Path supports the use of aliases. Aliases substitute default names for custom names. Example: The World Wide Node Name (WWNN) of a storage system is 5000-1FE1-0005-3480. You can assign the alias Fire to replace the longer, less easy-to-remember WWNN 5000-1FE1-0005-3480.
Managing Secure Path # spmgr unalias To remove an alias from the alias table, invoke the spmgr unalias command and enter either the alias_name or the old_name. Syntax: # 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.
Managing Secure Path Setting storage system parameters The Secure Path v3.0C driver has options you can enable or disable on a storage system or global basis. These options may be turned off and on dynamically. These changes occur within 45 seconds. ■ The spmgr set command lets you enable storage system specific settings for the Secure Path driver. — Load Balancing− v3.0C of Secure Path implements a round-robin usage of all available paths to a unit for its I/O. The default for Load Balancing is disabled.
Managing Secure Path The set command Syntax: # spmgr set -a -b -p -f (on | off) [WWNN] (on | off) [WWNN] (on | off) [WWNN] verify_period # spmgr set -a on | off [WWNN] This command enables or disables the Auto-Restore feature of the driver. When Auto-Restore is enabled, it directs the driver to monitor the state of the paths. If the preferred path should fail and then later return to service, the driver automatically reroutes all I/O to the restored path.
Managing Secure Path The log command Syntax: # spmgr log -l (level 0, 1,2,3) -c (level 0, 1,2,3) -n (level 0, 3) The numerical level indicates the message severity. The levels of severity are: 1: Critical, 2: Warning, 3: Informational When you select a numerical level, messages of that severity and higher are delivered to the appropriate output. ■ If 3 is selected, then 3, 2, 1 are logged. ■ If 2 is selected, then 2, 1 are logged. ■ If 1 is selected, then 1 is logged.
Managing Secure Path # spmgr log -n [0, 3] This command enables or disables logging to the notify function. This option has two values, 0 and 3. The default is 3. Level 0 is provided for disabling all notification messages.
Managing Secure Path # spmgr notify add This command adds an e-mail address to the notification list. Syntax: # spmgr notify add severity_level email_address Example: # spmgr notify add 3 john.doe@oscar.edu.it Severity_level is 3 and the email_address is john.doe@oscar.edu.it. Note: A user is defined by a unique email_address. A user with more than one email_address may have multiple records, one for each unique address.
Managing Secure Path Path management Secure Path v3.0C supports up to 32 paths to a unit on a storage system. The spmgr utility lets you monitor and manage these paths. The path management tasks include: ■ Selecting paths ■ Setting preferred and unpreferred paths ■ Restoring preferred paths ■ Quiescing and restarting objects and paths The select command A path is a combination of all the components from server to the unit on the storage system.
Managing Secure Path # spmgr select -a HBA –d device This command selects the path with the indicated HBA and device and makes that path Active. Example: # spmgr select –a 2300-1 –d spa Result: The Secure Path driver selects one path from 2300-1 to unit spa and marks it selected. # spmgr select -c controller_serial_number This command selects the path with the indicated controller serial number and makes that path Active.
Managing Secure Path # spmgr select -p path_instance This command selects the indicated path and makes that path Active. This parameter, path_instance, satisfies the path equation because it contains the necessary components of HBA, controller port, and device. Therefore, no other switches or parameters are required to identify the path. Example: # spmgr select –p hsx-mod-1-0-0-2 Result: The Secure Path driver selects path hsx-mod-1-0-0-2 for I/O.
Managing Secure Path # spmgr prefer path_instance This command instructs the Secure Path driver to mark a designated path as Preferred. If load balance is disabled, this path becomes the active I/O path. Additionally, spmgr adds this path_instance to the Secure Path driver's configuration file and upon reboot of the server, the preferred paths will be restored.
Managing Secure Path ■ The configuration file for paths have this path marked as Preferred. Upon reboot, this path will be marked as Preferred and deployed as Preferred if and when Load Balancing is disabled. 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.
Managing Secure Path ■ If there is no preferred controller and — a preferred path on each controller, then the preferred path on the currently active controller becomes active — a preferred path only on the currently active controller, then the preferred path on that controller becomes active — a preferred path only on the nonactive controller, then the nonactive controller and the preferred path become active — no preferred paths, no change occurs Syntax: spmgr restore all -d device -r WWNN # spmgr res
Managing Secure Path # spmgr restore -r WWNN Restores a preferred path to the indicated storage system. Syntax: # spmgr restore -r WWNN Example: # spmgr restore –r 5000-1FE1-0010-5B00 The quiesce command Quiescing an object means to: ■ Move all active I/O from an object to an alternate path. ■ Mark all paths to the object as quiesced to temporarily remove the object from use. The objects that are supported for v3.0C of Secure Path are adapters and controllers.
Managing Secure Path Use this feature to move I/O to another adapter as the first step to replacing an HBA. Example: # spmgr quiesce -a 2300-1 # 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 will then be marked as quiesced, and no further I/O will be sent along that path until the controller is returned to service with the restart command.
Managing Secure Path Syntax: # spmgr restart all -a HBA -c controller -p path_instance # spmgr restart all When this command is invoked, spmgr verifies the existence of all components on quiesced paths and changes those paths to Available or Standby as appropriate. If the Auto-Restore feature is enabled and one or more of those paths are Preferred paths, those paths will be made the Active path.
Managing Secure Path The passwd Command Secure Path requires authentication before running commands to ensure that only authorized individuals have access to your storage environment. Use the passwd command to change the default password to a unique password. spmgr passwd agent_password To enter a new password, use the following spmgr passwd command. Syntax: spmgr passwd Note: After running this command, you must stop and restart the agent using spagent -k to stop and spagent to start.
Managing Secure Path 92 Secure Path v3.
Removing/Upgrading Secure Path 5 This chapter describes how to remove or update Secure Path software. The following topics are covered: ■ Removing Secure Path software, page 94 ■ Updating to Secure Path for Linux v3.0C, page 96 Secure Path v3.
Removing/Upgrading Secure Path Removing Secure Path software This section describes how to remove the Secure Path using the Red Hat Package Management (RPM) utility. 1. Unmount all Secure Path file systems before you remove Secure Path. 2. Choose the appropriate option to remove Secure Path v3.0C: For 32-bit machines: — To remove Secure Path v3.0C for Linux or Secure Path v3.0C for Linux Workgroup Edition, enter a command similar to the following: # rpm -e Secure-Path-3.
Removing/Upgrading Secure Path For Red Hat operating systems: Insertion point found in /etc/rc.d/rc.sysinit Removal of Secure Path complete. Please reboot system to unload Secure Path modules. Note: If the RAID storage system is to be used for single-path access by one or more servers, then the HSG80 dual-redundant controllers must be restored to Transparent Failover mode. Refer to “HSG80 Controller Failover Transitions” on page 105 to perform the transition to Transparent Failover mode.
Removing/Upgrading Secure Path Updating to Secure Path for Linux v3.0C The following sections describe the update rpms and requirements for 32-bit or 64-bit operating systems. 32-bit systems The system is not required to have previous versions of Secure Path (v3.0, v3.0A, or v3.0B) installed for the update to succeed. However, Secure Path v3.0, v3.0A, or v3.0B RPM must be located in the /tmp/securepathRPM directory so the update can be validated. To update from Secure Path v3.0, v3.0A, or v3.
Removing/Upgrading Secure Path Table 11 lists the update RPMs for 64-bit systems in this release of Secure Path: Table 11: Secure Path v3.0C 64-bit update RPMs For this operating system: To update this RPM: Use: Red Hat Secure-Path-3.0BFull64-4.0.noarch.rpm Secure-Path-3.0CFull64Update Red Hat Secure-Path-3.0Bc64-4.0.noarch.rpm Secure-Path-3.0Cwkgrp64 Update SUSE/ UnitedLinux Secure-Path-3.0BFullSuse64-4.0.noarch.rpm Secure-Path-3.0CFullUL64 Update SUSE/ UnitedLinux Secure-Path-3.0BcSuse64-4.
Removing/Upgrading Secure Path Updating the software This update procedure addresses both Secure Path v3.0C for Linux and Secure Path v3.0C for Linux Workgroup Edition. The Secure Path v3.0C for Linux update kit is available on the HP web site at http://h18000.www1.hp.com/products/sanworks/secure-path/index.html Use the following steps to update Secure Path: 1. Ensure that the Secure Path v3.0C top level directory includes: ■ Readme file ■ ./update_SPlinuxFull.sh and ./update_SPlinuxwkgrp.
Removing/Upgrading Secure Path — If you have an unsupported kernel version, the following message displays: ************************************************************ The kernel on this system is not supported. Please see documentation for supported kernel versions. Exiting..... ************************************************************ — If you are not running smp or an enterprise kernel.
Removing/Upgrading Secure Path — For 32- bit Red Hat 2.1 with a non-supported errata version, but with a proper kernel version of 2.4.9-e.35smp, the following error message displays: ************************************************************ The system is not running the errata kernel (2.4.9-e.35smp). The system is not running a supported errata kernel. Would you like to install anyway? [y/N] ************************************************************ — For 64-bit Red Hat 2.
Removing/Upgrading Secure Path For Secure Path v3.0 for Linux: ******************************************************* Secure-Path-3.0-8.0.noarch.rpm was not found in the /tmp/securepathRPM. Secure Path Linux 3.0 to 3.0C update unavailable on this system. Checking for valid update path from Secure Path Linux 3.0A to 3.0C... ******************************************************* For Secure Path v3.0A for Linux Workgroup Edition: ************************************************************ Secure-Path-3.
Removing/Upgrading Secure Path — The RPM update continues with the following message: This script will update Secure Path, saving important configuration files and restoring them upon completion. Note, that the current installation will be removed!!! Would you like to update Secure Path? Note: Current installation of Secure Path will be uninstalled! [y/N] — If you choose N, the following message displays and the installation ends: You have chosen not to continue.
Removing/Upgrading Secure Path 32-bit Example: ************************************************************ INVALID RPM: You must have a valid Secure-Path-3.0BFull-5.0.noarch.rpm in the /tmp/securepathRPM directory, to validate the update!!! Update failed. Exiting... ************************************************************ 64-bit Example: ************************************************************ INVALID RPM: You must have a valid Secure-Path-3.0BFull64-4.0.noarch.
Removing/Upgrading Secure Path 104 Secure Path v3.
HSG80 Controller Failover Transitions A This appendix describes how to set dual-redundant HSG80 controllers from one failover state to another. The failover states are Transparent Failover, Multiple-bus Failover, and No Failover.
HSG80 Controller Failover Transitions Establishing a serial connection to the controller Before changing failover states, you must establish a serial connection to the controller as follows: 1. Establish a serial connection to the controller with the serial line connected to the top controller. This controller will be referred to as this_controller. The second controller will be referenced as the other_controller. All HSG80 actions in the next steps are assumed to be through this serial connection. 2.
HSG80 Controller Failover Transitions Changing from Transparent Failover to no failover mode 1. Enter the following command at the CLI prompt: CLI> set nofailover This action causes the OTHER_CONTROLLER to shut down. 2. Enter the following command to verify the change to no failover. CLI> show this_controller Controller: HSG80 ZG83502145 Software V85F-0, Hardware NODE_ID = 5000-1FE1-0000-3350 ALLOCATION_CLASS = 0 SCSI_VERSION = SCSI-3 -> Not Configured for dual-redundancy E03 3.
HSG80 Controller Failover Transitions Changing from Transparent Failover to Multiple-bus Failover mode Regardless of whether you have defined UNITs for the RAID system, the following steps implement Transparent Failover to Multiple-bus Failover. 1. Enter the following command at the CLI prompt: CLI> set nofailover This action causes the OTHER_CONTROLLER to shut down. 2.
HSG80 Controller Failover Transitions After both controllers have restarted, the controller pair will be bound in Multiple-bus Failover mode with consistent views of all the RAID array information. 5. Verify that the controllers are now in Multiple-bus Failover: CLI> show this_controller Controller: HSG80 ZG83502145 Software V85F-0, Hardware E03 NODE_ID = 5000-1FE1-0000-3350 ALLOCATION_CLASS = 0 SCSI_VERSION = SCSI-3 -> Configured for MULTIBUS_FAILOVER with ZG80200290 -> In dual-redundant configuration 6.
HSG80 Controller Failover Transitions Changing from Multiple-bus Failover mode to no failover and then to Transparent Failover mode 1. Check for connections on the storage system. For HSG80 controllers, enter the following command: CLI> show connections 2. Delete all connections by entering the following command for each connection that is shown (if any): CLI> delete connection_name Note: The connections will be regenerated later. 3. Check for units on the storage system: CLI> show units 4.
HSG80 Controller Failover Transitions Controller: HSG80 ZG83502145 Software V85F-0, Hardware NODE_ID = 5000-1FE1-0000-3350 ALLOCATION_CLASS = 0 SCSI_VERSION = SCSI-3 -> Not Configured for dual-redundancy E03 7. Restart the OTHER_CONTROLLER by pressing the RESET button on the OTHER_CONTROLLER. The OTHER_CONTROLLER will sound an alarm as it discovers the second controller but detects that it is not bound in a failover mode.
HSG80 Controller Failover Transitions 10. Restore the UNIT to the storageset mapping that was recorded earlier by entering the following command: CLI> add unit dn storage_set_name Caution: Do not initialize the storagesets. This action will destroy data on the storagesets. 11. Restart both controllers by entering the following commands: CLI> restart other_controller CLI> restart this_controller Note: Restarting both controllers allows connections to be reacquired.
Fibre Channel Device Software B This chapter describes Secure Path persistence software. The following topics are covered: ■ Using Secure Path Persistence Software, page 114 — Linux SCSI layer overview, page 114 — Persistence defined, page 115 ■ The sps program conclusion, page 116 — Editing full Persistence data files, page 116 — Using a standard editor, page 117 ■ Summary of sps features and limitations, page 118 Secure Path v3.
Fibre Channel Device Software Using Secure Path Persistence Software Linux SCSI layer overview The Linux operating system does not provide built-in LUN persistence. Lack of LUN persistence means that if you add or delete physical LUNs or disks and reboot your system, there is a probability that the device mnemonics will change in an undesirable way.
Fibre Channel Device Software Persistence defined Persistence is the binding of a device mnemonic to a physical device regardless of the device’s location on the bus. Persistence is a very important concept, especially in Fibre Channel topologies. In a Fibre Channel fabric, devices come and go much the same way network attached devices, such as PCs, connect to and disconnect from a LAN. Normally, you will install a disk, create a filesystem on it, and mount it.
Fibre Channel Device Software The sps program conclusion Secure Path for Linux uses the sps program for maintaining device persistence. The program does the following: ■ Reads in a list of associations it knows about (physical -> logical -> symbolic). ■ Reads in a list of physical devices the hardware indicates is present at that time. ■ Compares the above and does the following: — Makes symbolic links for new devices. — Deletes symbolic links for nonexistent devices.
Fibre Channel Device Software Using a standard editor Note: Create a backup copy of the file prior to opening the sppf file. Using the editor of your choice, open the /etc/CPQswsp/sppf file and delete the lines that correspond to LUNs that are no longer available. Make sure you delete the entire line. Note: Editing a line is not recommended; doing so could corrupt your database and render it useless. After you have deleted the lines for non-existent LUNs, save and close the file.
Fibre Channel Device Software Summary of sps features and limitations The important points about the sps for Secure Path v3.0C for Linux program are as follows: 118 ■ Runs at boot time, normally. ■ Creates symbolic links in /dev/spdev, which should be used in place of the normal device driver files. ■ Tracks a device between reboots even if device moves to another bus or slot. ■ Can fill up persistence data file to a maximum of 128 LUNs.
glossary Glossary This glossary defines terms used in this guide or related to this product and is not a comprehensive glossary of computer terms. Glossary Controller A controller is a hardware device that facilitates communication between a host and one or more LUNs organized as an array. The HSG80, HSV110, HSV100 and MSA1000 controllers are supported for use with Secure Path.
Glossary HBA A Host Bus Adapter is an I/O device that serves as the interface connecting a host system to the SAN (Storage Area Network). LUN A Logical Unit Number is the actual unit number assigned to a device at the RAID system controller. Object The objects that are supported for v3.0C of Secure Path are adapters and controllers. Path A virtual communication route that enables data and commands to pass between a host server and a storage device.
index A active state 62 adapter, HBA selecting path 82 addresses delete 81 display 81 notify 81 agent 21 alias defining 75 displaying 76 attributes, paths 62 audience 10 authorized reseller, HP 14 automatic software installation 51 auto-restore, setting 78 available state 62 C Index Index # spmgr common terms 61 log -c 79 log -l 79 log -n 80 notify 81 notify delete 81 quiesce - a controller 89 quiesce - a HBA 88 quiesce - c controller 89 restart -a HBA 90 restart -p path_instance 90 restore all paths
Index conventions document 11 equipment symbols 12 text symbols 11 D defining, alias 75 device states 63 display command 64 displaying alias, an 76 configuration information 62 path states 71 document, conventions 11 drivers 20 dual RAID controllers 19 E enable notification, logging 80 Enterprise Virtual Arrays, configuring 31 equipment symbols 12 F failed state 62 failover operation 24 FC Arbitrated Loop mode installation 33 features, sps 118 G getting help 14 H HBA restart -a, # spmgr 90 restart -a,
Index O S offline state 62 operational state 62 overview, Linux SCSI layer 114 Secure Path basic configuration, illustrated 17 installing HSG80 storage arrays 33 HSVx storage arrays 31 MSA100 storage arrays 37 software automatic 51 manual 45 overview 16 Persistence Software, using 114 pre-installing 44 removing software 94 software components 20 technology 18 updating software 32-bit systems 96 64-bit systems 96 set commands auto-restore 78 load balancing 78 path verification 78 path verification interv
Index select -a HBA 82 select -p path_instance 84 set auto-restore 78 set load balancing 78 set path verification 78 set path verification interval 78 unprefer path_instance 85 sps 118 states controller 62 device 63 path 62 standby 62 symbols in text 11 on equipment 12 syslog 79 124 T technical support, HP 14 text symbols 11 U unknown, state 62 unpreferring a path 85 updating software 32-bit systems 96 64-bit systems 96 procedure 98 to 103 V verifying a path 25 W warnings RAID in production environmen
