Installation and Maintenance Guide HP OpenView Continuous Access Storage Appliance Product Version: 5.7 Fourth Edition (May 2004) Part Number: AA–RTD6D–TE This guide describes how to install, configure, and maintain the HP OpenView Continuous Access Storage Appliance (CASA), which uses two ProLiant servers.
© Copyright 2000–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 Managing remote access to ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 List of network ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 Configuring remote access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 Resetting security for all ports . . . . . . . . . . . . . .
Contents Installing PowerPath. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 Downloading the 3.0.5 patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 Installing version 3.0.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 Installing version 3.0.5. . . . .
Contents A IP Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Managing worker threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128 Worker threads overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128 Adjusting the number of worker threads . . . .
Contents Host events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154 Host addition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154 Host name registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154 Host removal . . . . . . . . . . . . . .
Contents Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176 mod vsmpollingint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177 Syntax. . . . . .
about this guide About this Guide This guide provides information to help you: ■ Identify the shipment contents. About this Guide ■ Understand the tasks that HP Manufacturing completes before shipping the Continuous Access Storage Appliance (CASA). ■ Complete the appliance setup in a customer environment. ■ Configure the hosts and storage arrays connected to the appliance. ■ Wire the appliance. ■ Replace and reconfigure appliance components.
About This Guide Overview This section describes the following topics: ■ Intended audience ■ Related documentation Intended audience This guide is intended for HP authorized service and support personnel.
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 Equipment symbols The following equipment symbols may be found on hardware to which this guide pertains. They have the following meanings: Any enclosed surface or area of the equipment marked with these symbols indicates the presence of electrical shock hazards. Enclosed area contains no operator serviceable parts. WARNING: To reduce the risk of personal injury from electrical shock hazards, do not open this enclosure.
About This Guide Rack stability Rack stability protects personnel and equipment. WARNING: To reduce the risk of personal injury or damage to the equipment, be sure that: ■ The leveling jacks are extended to the floor. ■ The full weight of the rack rests on the leveling jacks. ■ In single rack installations, the stabilizing feet are attached to the rack. ■ In multiple rack installations, the racks are coupled. ■ Only one rack component is extended at any time.
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.
Unpacking the Appliance 1 HP Manufacturing ships the appliance components in one of two ways: ■ Preinstalled in the standard HP rack. ■ Packaged in separate boxes. You must install the appliance components in the rack that the customer is using.
Unpacking the Appliance Shipment contents The shipment contents contain the following items (see “Appliance Components” on page 137 for detailed specifications): ■ Nodes — Two ProLiant ML370G3 servers with the following components: — Two standard–bracket, dual–port HP/Intel Gigabit Ethernet cards (PWLA8492MTG1P20, MM# 844154) — Six QLogic 2344F four–port full–profile host bus adapters (HBAs) ■ Peer node storage — One HP StorageWorks Virtual Array, model 7110 (VA7110)—dual–controller, 1024MB cache — Five
Unpacking the Appliance Preinstalled version The preinstalled version of the appliance is shipped as one unit with all components installed in the rack. HP Manufacturing completes the following tasks before shipping the appliance: ■ On the appliance nodes: — Installs the appliance software (SANOS). — Installs and configures the Gigabit Ethernet card and the QLogic HBAs. — Disables the Automatic Server Recovery and Automatic Server Restart parameters.
Unpacking the Appliance Identifying the node components Figure 1 lists the node components, including the location of the initiator and target ports: ■ Dual–port Gigabit Ethernet card (1) — Port A—MirrorLink — Port B—InterLink ■ Four–port HBA card (2) — Port 0—Target 2 — Port 1—Target 3 — Port 2—Initiator 2 — Port 3—Initiator 3 ■ Four–port HBA card (3) — Port 0—Target 4 — Port 1—Target 5 — Port 2—Initiator 4 — Port 3—Initiator 5 ■ Four–port HBA card (4) — Port 0—Target 0 — Port 1—Target 1 — Port 2—I
Unpacking the Appliance Figure 1: Node components (rear view) Continuous Access Storage Appliance Installation and Maintenance Guide 19
Unpacking the Appliance Connecting the nodes and the shared storage array If you are installing the packaged version, connect the nodes to the shared storage array (Figure 2). HP Manufacturing completes these connections on the preinstalled version before shipment.
Unpacking the Appliance What to do next After you unpack the appliance: 1. Connect all cables on the appliance. 2. Power on the appliance. 3. Set the current date and local time on the nodes (and switches, if applicable). (See “Setting the current date and local time” on page 31.) 4. Set the network properties using the CASA Setup Utility. (See “Setting network properties” on page 42.) 5. Initialize the user database to authenticate the user interface and the command line interface (CLI).
Unpacking the Appliance 22 Continuous Access Storage Appliance Installation and Maintenance Guide
Completing the Appliance Setup 2 This chapter describes how to complete the appliance setup after unpacking the appliance.
Completing the Appliance Setup Navigating the CASA console When you first power on the appliance monitor, the hp OV CASA Console window for the current node opens in viewer mode (Figure 3). Customers can only use the console in viewer mode. The CPU, MEM, and NET indicators are updated dynamically and indicate the status of the node’s central processing unit, memory, and network activity, respectively. The current time is displayed automatically. Click the time to display the date.
Completing the Appliance Setup Viewer mode In viewer mode, the hp OV CASA Console window contains the following options: ■ status—View the worldwide names of the appliance node’s initiator ports and the status of the network interface card (NIC) ports, power supplies, and CPU fan. ■ node—Display the appliance node’s ID number (either 0 or 1) of the appliance node. ■ system info—Display the appliance node’s available disk space and memory, uptime, and IP address.
Completing the Appliance Setup Administrative mode In administrative mode, the hp OV CASA Console window includes the viewer mode options, as well as the following options: ■ service viewer—Display and manage the software services running on the appliance node. ■ setup—Open the CASA setup utility window to set network properties. ■ switchui—Switch the console display to the Windows NT desktop. (See “Using switchui” on page 28 for more information.) ■ logoff—Log off the appliance node.
Completing the Appliance Setup Accessing administrative mode To access administrative mode: 1. When the hp OV CASA Console window is open in viewer mode, press Ctrl+Alt+Shift+Esc. 2. At the password prompt, enter adm and click OK. The hp OV CASA Console window opens in administrative mode (Figure 4). To return to viewer mode: 1. Press Ctrl+Alt+Shift+Esc. The following prompt is displayed: Exiting Administrative mode, click YES to continue. 2. Click Yes. The hp OV CASA Console window opens in viewer mode.
Completing the Appliance Setup Using switchui To switch from the console window to the Windows NT desktop: 1. When the hp OV CASA Console window is open in administrative mode, click switchui. The CASA Switch UI Utility dialog box opens (Figure 5). 2. Select the Force appliance reboot check box, if applicable. (See “Using the Force appliance reboot check box.”) 3. Click Yes. The Windows NT desktop opens. 4. If you click No, the operation is cancelled and the console window opens in administrative mode.
Completing the Appliance Setup Figure 5: CASA Switch UI Utility dialog box Using a command prompt window Throughout this guide, always use a command prompt window when instructed. Do not use Windows Explorer.
Completing the Appliance Setup Known console window issues The console window issues are as follows: ■ If you open the Control Panel window from a command prompt window, the system displays the following error message: Cannot find the file '(null') (or one of its components). Make sure the path and filename are correct and that all required libraries are available. ■ You cannot change service login information using the service viewer option in the console window.
Completing the Appliance Setup Setting the current date and local time HP Manufacturing does not set the current date or local time before shipping the appliance. After you power on the appliance nodes, check the date and time on each node. Verify with the customer that the date and time reflect the correct time zone. Having the correct date and time is helpful when generating logs to troubleshoot issues. To view or set the the current date and time on the appliance nodes: 1.
Completing the Appliance Setup Disabling Automatic Server Recovery HP Manufacturing installs the ProLiant management agents on the appliance nodes before shipping the appliance. However, installing these agents may result in unexplained, intermittent reboots. To prevent these reboots, HP Manufacturing also disables the Automatic Server Recovery (ASR) parameter prior to shipment. To disable Automatic Server Recovery: 1. While the node is booting up, press F9. The BIOS options window opens. 2.
Completing the Appliance Setup Identifying the network connections This section identifies the hardware and software ports on the nodes and describes how to manage access to these ports.
Completing the Appliance Setup Figure 6: Network interface ports on the node Software ports The appliance has several software ports. The customer’s network administrator must modify the local name–to–port–number tables to include the port names and numbers listed in Table 2. The network administrator must have these names to open the ports in the firewall and allow IP mirror traffic to flow through the network.
Completing the Appliance Setup Managing remote access to ports This section describes the following topics: ■ List of network ports ■ Configuring remote access List of network ports To protect the appliance nodes from viruses, HP Manufacturing sets the port access for the ethernet adapters on the appliance nodes before shipping the appliance.
Completing the Appliance Setup Table 3: Network ports Application Protocol Port number Remote access RPIC Data Propagation Framework (DPF) service UDP 1028 Enabled (do not change) UDP 1029 Enabled (do not change) UDP 2001 Enabled (do not change) TCP 1030–1233 Enabled (do not change) TCP 4050 Enabled (do not change) TCP 4051 Enabled (do not change) TCP 4098 Enabled (do not change) TCP 4099 Enabled (do not change) TCP kpop Enabled (do not change) TCP securepath Enabled (do no
Completing the Appliance Setup Table 3: Network ports Application Protocol Port number Remote access System TCP 137 Enabled (do not change) TCP 138 Disabled TCP 161 Disabled TCP 1029 Disabled TCP 1028 Disabled TCP 1235 Disabled TCP 1236 Disabled TCP 1237 Disabled TCP 1671 Disabled TCP 1678 Disabled TCP 1770 Disabled TCP 2001 Disabled TCP nbsession Disabled UDP 137 Enabled (do not change) UDP nbdatagram Disabled UDP nbname Disabled Continuous Access Storag
Completing the Appliance Setup Configuring remote access If corruption occurs and you need to configure remote access for the ports, you can: ■ Reset security for all ports. (See “Resetting security for all ports.”) ■ Manually configure access for individual ports. (See “Manually configuring port access.”) Resetting security for all ports To reset security for all ports listed in Table 3: 1. Ensure the hp OV CASA Console window is open in administrative mode. 2.
Completing the Appliance Setup Manually configuring port access To manually configure port access: 1. Ensure the hp OV CASA Console window is open in administrative mode. 2. Click switchui to open the Windows NT desktop. See “Using switchui” on page 28 for instructions. 3. Click Start > Settings > Control Panel. The Control Panel window opens. 4. Click Network. The Network dialog box opens (Figure 7). 5. Click the Protocols tab, click TCP/IP Protocol, and then click Properties.
Completing the Appliance Setup Figure 8: Microsoft TCP/IP Properties dialog box Figure 9: Advanced IP Addressing dialog box 40 Continuous Access Storage Appliance Installation and Maintenance Guide
Completing the Appliance Setup Figure 10: TCP/IP Security dialog box Continuous Access Storage Appliance Installation and Maintenance Guide 41
Completing the Appliance Setup Setting network properties Before shipping the appliance, HP Manufacturing enters information for each appliance node using the CASA setup utility window. This information enables the appliance nodes to identify and communicate with each other. Table 4 lists the information entered for node 0; Table 5 lists the information entered for node 1. At the customer site, you must update the LAN Interface network information.
Completing the Appliance Setup Table 5: Settings for node 1 Field Value Peer Node General – Settings Host name Node 1 Node id 1 Serial id CCSYYWWXXX Peer IP address 10.0.1.1 LAN Interface IP Address 10.100.70.131 Subnet Mask 255.255.255.0 Default Gateway 10.100.70.1 MirrorLink IP Address 10.0.2.2 Subnet Mask 255.255.255.0 Default Gateway blank InterLink IP Address 10.0.1.2 Subnet Mask 255.255.255.
Completing the Appliance Setup Stopping the software services The software services are: ■ Identification and Authorization Server (INA)—Performs the security operations for the appliance. ■ RPIC DPF—Performs all tasks (other than security) for the appliance. RPIC DPF is the core component of the appliance software. ■ sv3000 Management Server (SMS)—Serves as an interface to the Data Propagation Framework (DPF).
Completing the Appliance Setup Running the CASA setup utility To run the CASA setup utility: 1. Set the console display to node 0. The hp OV CASA Console window opens. 2. Ensure that the hp OV CASA Console window is open in administrative mode. 3. Click setup. The CASA setup utility window opens (Figure 11). 4. Do either of the following: ■ If the Peer Node Settings - General box is populated with values, do not change the IP address in the Peer IP Address box.
Completing the Appliance Setup Figure 11: CASA setup utility window 46 Continuous Access Storage Appliance Installation and Maintenance Guide
Completing the Appliance Setup Starting the software services To start the software services: 1. Set the console display to node 0. The hp OV CASA Console window opens. 2. Ensure that the hp OV CASA Console window is open in administrative mode. 3. Click service viewer. The Services window opens. 4. Select the RPIC DPF service and set it to Automatic. 5. Click Apply and then click Start. Note: It may take a few minutes for the RPIC DPF service to start. 6.
Completing the Appliance Setup Initializing the user database Before you or the customer can manage the appliance using the command line interface (CLI) or the user interface, you must initialize the user database by completing the following procedures in the order shown: ■ Creating the initial administrator account ■ Initializing the services ■ Updating HBA information Creating the initial administrator account To create the initial administrator account on the appliance nodes: 1.
Completing the Appliance Setup Initializing the services The next procedure for initializing the user database is to initialize the following services: ■ slsnmp—Gathers information from the SMS service and formats it for SNMP ■ slsemi—Enables HP software products to identify HP hardware and gather information about HP products ■ slstat—Gathers statistics from the SMS service for LUNs connected to the appliance Note: You must perform the following steps in the order shown to ensure that the slsnmp, sl
Completing the Appliance Setup Downloading and installing diagnostic software There is diagnostic software available for the ProLiant ML370G3 servers, but it is not pre-installed by HP Manufacturing. There are two components of the diagnostic software: ■ HP Server Diagnostics ■ Diagnostics for Windows Note: Downloading and installing diagnostic software is not required to complete the appliance setup. You should complete these tasks if you need to troubleshoot issues on the appliance nodes.
Completing the Appliance Setup 10. After you create the diskette, you can delete the download utility and all folders and files associated with it. 11. Power down the appliance node. 12. Insert the Diagnostics diskette in the a:\ drive and power on the appliance node. The appliance node boots in to the HP Server Diagnostics software. Diagnostics for Windows Use the Diagnostics for Windows software for online diagnostics.
Completing the Appliance Setup What to do next To continue with the appliance setup: 1. Configure the hosts and storage arrays that you connect to the appliance. (See “Configuring Hosts and Storage Arrays” on page 53.) 2. Implement path failover, if applicable. (See Implementing Path Failover on page 69.) 3. Complete the wiring between the appliance and the hosts and storage arrays. (See “Connecting the Appliance to Hosts and Storage Arrays” on page 81.
Configuring Hosts and Storage Arrays 3 This chapter describes how to configure the hosts and storage arrays that you connect to the appliance: ■ Host configuration overview, page 54 ■ Installing HP StorageWorks Auto Path, page 55 ■ Configuring HBA drivers, page 56 ■ Using execution throttles, page 58 ■ Replacing host HBAs, page 62 ■ Expanding LUNs with the Windows diskpart utility, page 63 ■ Configuring appliance LUNs for Solaris hosts, page 65 ■ Configuring storage arrays, page 67 ■ What
Configuring Hosts and Storage Arrays Host configuration overview You must configure the hosts connected to the appliance to ensure proper communication. To configure the hosts: 1. Install the HBA driver for the operating system running on the host. 2. Set the execution throttle of the HBA driver for proper load balancing. See “Using execution throttles” on page 58 for more information.
Configuring Hosts and Storage Arrays Installing HP StorageWorks Auto Path The Auto Path software is an optional upgrade for the appliance. Install it only if the customer has purchased the Auto Path license. You install Auto Path using an automated installation program. When the installation is complete and the software is running on the host, users can access Auto Path from any PC connected to the host on which Auto Path is installed.
Configuring Hosts and Storage Arrays Configuring HBA drivers This section describes the HBA drivers you can configure and the operating systems that support them. To determine which version of the HBA driver the appliance supports: 1. Access the following internal HP web site: http://turbo.rose.hp.com/spock/ 2. Locate the Storage Virtualization section. 3. Select the appropriate support matrix for the appliance. QLogic HBAs The following operating systems support QLogic HBAs: ■ Netware 5.1, 6.0, and 6.
Configuring Hosts and Storage Arrays Emulex HBAs The following operating systems support Emulex HBAs: ■ IBM-AIX 4.3.3 ■ RedHat 8.0 (Kernel 2.4.18) ■ RedHat AS 2.1 (Kernel 2.4.9-e.16) ■ Solaris 2.9 ■ Veritas Cluster Server v2.0 ■ Windows 2000 ■ Windows 2000 Advanced Server Cluster ■ Windows NT 4.0 ■ Windows NT 4.0 Cluster Server ■ Windows Server 2003 32 bit ■ Windows Server 2003 64 bit After you determine which HBA driver to install, go to the Emulex web site (www.emulex.
Configuring Hosts and Storage Arrays Using execution throttles This section describes how to calculate the execution throttle for an HBA driver and lists the procedures to set the execution throttle for specific HBA drivers: ■ Calculating execution throttles ■ Setting the execution throttle for QLogic HBAs ■ Setting the execution throttle for Emulex HBAs Calculating execution throttles Execution throttles enable you to balance the workload on the appliance.
Configuring Hosts and Storage Arrays Setting the execution throttle for QLogic HBAs This section describes how to set the execution throttle for QLogic HBA drivers on the following operating systems: ■ Windows 2000 and Windows NT ■ Solaris Windows 2000 and Windows NT To set the execution throttle for a QLogic HBA driver on a Windows 2000 or Windows NT host: 1. Power off and then power on the host. 2. Press Ctrl+Q when prompted. The Select Host Adapter menu opens. 3. Select an adapter and press Enter.
Configuring Hosts and Storage Arrays Figure 12: Fast!UTIL Options menu Figure 13: Configuration settings modified menu Figure 14: ExitFast!UTIL menu Solaris To set the execution throttle for a QLogic HBA driver on a Solaris host: 1. From the host, enter cd /kernel/drv. 2. To open the ql2x00.conf file, enter: vi ql2x00.conf 3. Locate the hba0_execution_throttle = parameter. 4. Set the parameter to the desired execution throttle value. 5. Save and close the ql2x00.conf file. 6. Reboot the host.
Configuring Hosts and Storage Arrays Setting the execution throttle for Emulex HBAs This section describes how to set the execution throttle for Emulex HBAs on the following operating systems: ■ Windows 2000 and Windows NT ■ IBM-AIX Windows 2000 and Windows NT To set the execution throttle for an Emulex HBA on a Windows 2000 or Windows NT host: 1. To open the registry editor, enter: Start RegEdit32.exe. 2.
Configuring Hosts and Storage Arrays Replacing host HBAs The following procedure applies to all hosts connected to the appliance. To replace a host HBA: 1. From the console window, click sanos admin > launch. The sanosadmin window opens. 2. Log in to sanosadmin. 3. To identify the host that requires an HBA replacement, enter: get host 4. To identify the LUNs mapped to the host, enter: get map 5. Record the LUNs and the node target ports used to map the LUNs to the host. 6.
Configuring Hosts and Storage Arrays Expanding LUNs with the Windows diskpart utility This section describes how to use the Microsoft diskpart utility. This utility enables you to expand a LUN that is mapped to a Windows 2000 host without corrupting the data on the LUN. This utility is required for LUNs connected to Windows 2000 hosts because Microsoft does not allow Basic disks (LUNs) to be changed dynamically.
Configuring Hosts and Storage Arrays 10. Open Disk Administrator on the host. Verify that the additional disk space appears at the end of the LUN you want to expand. 11. Open the WinZip file that contains the diskpart utility. Select the utility and click Actions > Install to install the utility on the host. 12. Open a command prompt window on the host. 13. Go to the directory in which you installed the diskpart utility. If you used the default directory, go to c:\program files\resource kit. 14.
Configuring Hosts and Storage Arrays Configuring appliance LUNs for Solaris hosts If the appliance connects to Solaris hosts, you must configure the appliance LUNs to ensure the Solaris hosts can detect the LUNs. The configuration procedures depend on whether or not Veritas Volume Manager (DMP) is installed on hosts.
Configuring Hosts and Storage Arrays Configuring appliance LUNs with Veritas Volume Manager This procedure assumes that Veritas Volume Manager (DMP) is installed and the local hard disk drive has been added to Volume Manager as the root disk. To configure appliance LUNs for a Solaris host with Veritas Volume Manager: 1. From the Solaris host, go to the /kernel/drv directory and use vi to edit the vxdmp.conf file. 2. Change the parameter jbod_dmp = “Hitachi” to jbod_dmp= “HP.” 3. Save and exit the vxdmp.
Configuring Hosts and Storage Arrays Configuring storage arrays You must configure the storage arrays before you connect them to the appliance. Refer to the appropriate vendor documentation for the configuration procedures. To determine which storage arrays the appliance supports: 1. Access the following internal HP web site: http://turbo.rose.hp.com/spock/ 2. Locate the Storage Virtualization section. 3. Select the appropriate support matrix for the appliance.
Configuring Hosts and Storage Arrays What to do next To complete the appliance setup: 1. Implement path failover software, if applicable. (See “Implementing Path Failover” on page 69.) 2. Connect the appliance to the hosts and storage arrays. (See “Connecting the Appliance to Hosts and Storage Arrays” on page 81.
Implementing Path Failover 4 This chapter describes how to implement path failover for the hosts and storage connected to the appliance: ■ Installing HP StorageWorks Secure Path for Windows, page 70 ■ Installing PowerPath, page 76 ■ Installing ATF software, page 80 ■ What to do next, page 80 Continuous Access Storage Appliance Installation and Maintenance Guide 69
Implementing Path Failover Installing HP StorageWorks Secure Path for Windows This section describes how to install and use HP StorageWorks Secure Path: ■ Secure Path overview ■ Installing the Secure Path Agent ■ Installing Secure Path Manager ■ Configuring Secure Path Manager ■ Using Secure Path Manager Secure Path overview The appliance installation CD contains the Secure Path for Windows failover software and license agreement, which states that Secure Path is licensed for use with the applian
Implementing Path Failover Installing the Secure Path Agent The Secure Path Agent is installed on the appliance nodes when the appliance software is installed. To configure Secure Path Agent on the appliance node: 1. Ensure the hp OV CASA Console window is open in administrative mode. 2. Click switchui. The CASA UI Switch Utility dialog box opens. 3. Click Yes to continue. The Windows NT desktop opens. 4. Click Start > Programs > Securepath >SecurePathCfg. The Secure Path Configuration window opens. 5.
Implementing Path Failover Installing Secure Path Manager Ensure the host meets the following requirements before installing Secure Path Manager: ■ Internet Explorer ■ IP connectivity to the appliance node ■ JAVA version 1.3.1 only ■ Supported Secure Path Manager version (confirm with CASA support team) To install Secure Path Manager on a host: 1. Copy the following executable to the host on which you want to install Secure Path Manager: SPM_V40_xx.
Implementing Path Failover Configuring Secure Path Manager To configure Secure Path Manager on the host: 1. Ensure the hp OV CASA Console window is open in administrative mode. 2. Click switchui. The CASA UI Switch Utility dialog box opens. 3. Click Yes to continue. The Windows NT desktop opens. 4. Click Start > Programs > Securepath >SecurePathCfg. The Secure Path Configuration Utility window opens (Figure 15). 5. Click Clients. The Client Access Configuration window opens (Figure 16). 6.
Implementing Path Failover Figure 15: Secure Path Agent Configuration Utility window Figure 16: Client Access Configuration window 74 Continuous Access Storage Appliance Installation and Maintenance Guide
Implementing Path Failover Using Secure Path Manager To use Secure Path Manager on a host: 1. Open Internet Explorer. 2. Enter the URL in the Address box using the following format: http:// xxx.xxx.xxx.xxx:2301 (xxx.xxx.xxx.xxx is the IP address of the host on which Secure Path Manager is installed.) 3. Log in using the following information: ■ User name—administrator ■ Password—administrator 4. Once Secure Path Manager is running, click File > New Profile. 5. Enter a name for the profile and click OK.
Implementing Path Failover Installing PowerPath This section describes how to install PowerPath version 3.0.5 on the appliance nodes. Use this software if there are EMC storage arrays connected to the appliance. This section describes the following topics: ■ Downloading the 3.0.5 patch ■ Installing version 3.0.0 ■ Installing version 3.0.5 Note: If Secure Path is already installed on the appliance nodes, do not install PowerPath.
Implementing Path Failover Installing version 3.0.0 Note: Ensure that you stop the RPIC DPF and SMS services before installing PowerPath. To install PowerPath version 3.0.0 on node 0: 1. Insert the EMC PowerPath version 3.0.5 for windows CD into the CD-ROM drive. 2. Ensure that the hp OV CASA Console window is open in administrative mode. 3. Click service viewer. The Services window opens. 4. Select the RPIC DPF service, set it to Manual, and click Apply. 5.
Implementing Path Failover Installing version 3.0.5 To install PowerPath version 3.0.5 on node 0: 1. Ensure that the hp OV CASA Console window is open in administrative mode. 2. Press Alt+C to open a command prompt window. 3. To execute the 3.0.5 patch, enter: c:\EMCPP.NT4.3.0.5.Patchb086\setup.exe The EMC PowerPath 3.0.5. – Install Shield Wizard Welcome window opens. 4. Click Next. 5. Enter the customer’s name and organization and click Next. 6.
Implementing Path Failover 23. To update the appliance configuration with the EMC LUNs, enter: mod lun –rescan 24. To verify that the appliance can detect the EMC LUNs: ■ In sanosdamin, enter get lun. ■ In the user interface, click LUNs to open the view LUNs window. 25. Close sanosadmin and the user interface. 26. Ensure that the console window is open in administrative mode. 27.
Implementing Path Failover Installing ATF software Note: This procedure only applies if the customer uses EMC CLARiiON storage, which requires that you install the Application Transparent Failover (ATF) software on the appliance nodes. The ATF installer will fail if you execute it from the the hp OV CASA Console window. If that occurs, perform the following steps: 1. Ensure that the hp OV CASA Console window is open in administrative mode. 2. Click switchui. 3.
Connecting the Appliance to Hosts and Storage Arrays 5 Connecting the appliance to hosts and storage depends on the customer’s network configuration. This chapter describes how to connect the appliance in three standard configurations. It also provides a sample cascaded appliance configuration for cross-appliance mirroring.
Connecting the Appliance to Hosts and Storage Arrays Directly connecting hosts and storage to the appliance Figure 17 shows three hosts and two storage arrays directly connected to the appliance. In this example, assume the following: ■ I0 from each peer node connects to the shared storage array. ■ From host 1, HBA 1 connects to T0 on peer node 0, and HBA 2 connects to T0 on peer node 1. ■ From host 2, HBA 1 connects to T2 on peer node 0, and HBA 2 connects to T2 on peer node 1.
Connecting the Appliance to Hosts and Storage Arrays Figure 17: Hosts and storage directly connected to the appliance Continuous Access Storage Appliance Installation and Maintenance Guide 83
Connecting the Appliance to Hosts and Storage Arrays Connecting hosts and storage arrays through switches Figure 18 shows two hosts and two storage arrays connected to the appliance through Fibre Channel switches. Adding switches as a layer between the appliance and the hosts and storage arrays enables you to connect more hosts and storage arrays to the appliance. In this example, assume the following: ■ Two Fibre Channel switches on the front end connect the two peer nodes to two hosts.
Connecting the Appliance to Hosts and Storage Arrays Figure 18: Hosts and storage arrays connected through Fibre Channel switches Continuous Access Storage Appliance Installation and Maintenance Guide 85
Connecting the Appliance to Hosts and Storage Arrays Connecting hosts and EVAs through switches Figure 19 shows two hosts and two HP StorageWorks Enterprise Virtual Arrays (EVAs) connected to the appliance through Fibre Channel switches. The controllers on each array in Figure 18 have one port. Each controller on the EVA has two ports. As a result, the EVAs require an additional connection to the back-end switches.
Connecting the Appliance to Hosts and Storage Arrays Connecting two appliances through a WAN Figure 20 shows two appliances connected through a wide area network (WAN). This configuration includes the optional IP mirroring functionality. In this example, assume the following: ■ Each peer node on the local and remote appliances connects to a Gigabit Ethernet router (or switch), that connects to the WAN. ■ The host and storage array connections described on page 84 also apply to this example.
Connecting the Appliance to Hosts and Storage Arrays Connecting cascaded appliances You can directly connect or interconnect (using zoned Fibre Channel switches) two appliances and create a cascaded configuration. A cascaded configuration enables cross-appliance mirroring, which means you can mirror data from storage on one appliance to storage on another appliance through a Fibre Channel cable.
Connecting the Appliance to Hosts and Storage Arrays Figure 21: Two directly connected cascaded appliances Continuous Access Storage Appliance Installation and Maintenance Guide 89
Connecting the Appliance to Hosts and Storage Arrays Connecting cascaded appliances through switches and fabrics Figure 22 shows two cascaded appliances connected through switches and fabrics. In this example, assume the following: ■ CASA A on site A has peer nodes 0 and 1 (CAP0, CAP1). Five targets (T0, T1, T2, T3, and T4) and two initiators (I1 and I4) from each node connect to the Fibre Channel switches as described on page 91. ■ CASA B on site B has peer nodes 0 and 1 (CBP0, CBP1).
Connecting the Appliance to Hosts and Storage Arrays Creating the fabric zones for CASA A This section describes the fabric zones and port connections for CASA A.
Connecting the Appliance to Hosts and Storage Arrays Creating the fabric zones for CASA B This section describes the fabric zones and port connections for CASA B.
Connecting the Appliance to Hosts and Storage Arrays Figure 22 shows two cascaded appliance connected through fabrics and switches. .
Connecting the Appliance to Hosts and Storage Arrays Creating zones for the switches This section describes a configuration in which two switches connect to the front end of the appliance and two switches connect to the back end of the appliance, enabling failover and recovery (See Figure 18 and Figure 19.) This configuration allows multiple host connections on the front end and multiple storage connections on the back end.
Connecting the Appliance to Hosts and Storage Arrays Figure 23: Six zones for the first host initiator Figure 24: Six zones for the second host initiator Continuous Access Storage Appliance Installation and Maintenance Guide 95
Connecting the Appliance to Hosts and Storage Arrays Zones for back-end switches Create zones that have one appliance initiator and one storage controller port. Storage arrays may have one port per controller (Figure 18) or two ports per controller (Figure 19). The two appliance initiators connect to the switches as follows: ■ From node 0: — I1 connects to port 0 on back-end switch 1. — I2 connects to port 1 on back-end switch 2. ■ From node 1: — I1 connects to port 0 on back-end switch 2.
Connecting the Appliance to Hosts and Storage Arrays Table 7: Storage zones for back–end switches Storage zone 0 21 1 28 5 6 7 8 9 10 11 12 13 14 15 X X X X X X 26 27 4 X 24 25 3 X 22 23 2 Switch ports X X X X X X X X Figure 25: Four zones for each storage controller port Continuous Access Storage Appliance Installation and Maintenance Guide 97
Connecting the Appliance to Hosts and Storage Arrays 98 Continuous Access Storage Appliance Installation and Maintenance Guide
Replacing and Configuring Appliance Components 6 This chapter describes how to replace and/or configure appliance components: ■ Creating and collecting logs, page 100 ■ Reconfiguring the shared storage array, page 101 ■ Replacing the hard disk drive, page 108 ■ Reconfiguring the host bus adapters, page 112 ■ Reconfiguring the Gigabit Ethernet card, page 118 ■ Reconfiguring the console switch user interface, page 121 Continuous Access Storage Appliance Installation and Maintenance Guide 99
Replacing and Configuring Appliance Components Creating and collecting logs If you need to replace an appliance component, the CASA support team may ask you to create and collect the appliance software logs. To do this, you must have network access to the appliance from either a customer workstation or your laptop. If you connect your laptop to the appliance node using a crossover Ethernet cable, ensure that your laptop has an IP address on the same subnet as the appliance nodes.
Replacing and Configuring Appliance Components Reconfiguring the shared storage array To replace the HP StorageWorks Virtual Array that serves as the shared storage between the peer nodes, refer to the HP StorageWorks Virtual Arrays va7000 Family User and Service Guide for instructions. This guide is available on the following HP web site: http://h20015.www2.hp.com/content/common/manuals/lpg60187/lpg60187.
Replacing and Configuring Appliance Components 9. Enter the following command: mgr –os nt -t 1 –c 1 -S 2 -hp 1 (for controller 1 on host port 1) 10. When you see the following message, enter n: Topology will be set to: Private Loop. Change will take effect after a reset. Do you wish to reset now? (y/n) 11. Enter the following command: mgr –os nt -t 1 –c 2 -S 2 -hp 1 (for controller 2 on host port 1) 12. When you see the following message, enter y: Topology will be set to: Private Loop.
Replacing and Configuring Appliance Components Creating a LUN After the peer node detects the shared storage array, create LUN 0 using the entire space on the array. Use the CommandView software or Hyper Terminal to create the LUN. Using CommandView To use CommandView to create LUN 0, you must first access the CommandView software. Note: Complete this procedure on the peer node used in “Detecting the array.” Accessing CommandView To access CommandView: 1.
Replacing and Configuring Appliance Components Creating LUN 0 using CommandView To create LUN 0 using CommandView: Note: Complete this procedure on the peer node used in “Detecting the array.” 1. Ensure the hp OV CASA Console window is open in administrative mode. 2. Press Alt+C to open a command prompt window. 3. Enter the following command to start the CommandView services and to discover the disks: c:\rpic\utilities\StartCommandView 4.
Replacing and Configuring Appliance Components Using Hyper Terminal Note: Perform this procedure on one controller of the array only. To create a LUN using Hyper Terminal: 1. Ensure that the hp OV CASA Console window is open in administrative mode. 2. Right-click on the window and click Programs > Accessories > Hyperterminal > Hyper Terminal. The Connection Description window opens. 3. Enter a name for the serial port connection and click OK. The Connect To window opens. 4. Click COM1 and click OK.
Replacing and Configuring Appliance Components Creating partitions on the shared storage array The shared storage array stores configuration information for both appliance nodes. The array also enables the appliance nodes to monitor communication between its peer node and the shared storage array. You must create seven partitions on the array in which to store to configuration information.
Replacing and Configuring Appliance Components Creating the partitions You can perform this procedure from the appliance or from your laptop if it is connected to the same network as the appliance. To create partitions on the shared storage array: 1. On node 0, ensure the hp OV CASA Console window is open in administrative mode. 2. Click service viewer. The Services window opens.
Replacing and Configuring Appliance Components Replacing the hard disk drive Before you replace the hard disk drive, ensure you have the following: ■ Latest SANOS image CD ■ PowerPath patch, if using EMC storage ■ Hard disk drive with the following specifications: — Part number—289241-001 — Description—SPS-DRV, HD, 36GB, U320, 15K, HP — Assembly number—286780-001 Verify that the customer has backed up the appliance configuration regularly.
Replacing and Configuring Appliance Components 7. Follow steps 1 through 21 in “Reinstalling the appliance software” on page 124 through page 128 to reinstall the appliance software. 8. Set the console display to the peer node. Ensure the hp OV CASA Console window on the peer node is open in administrative mode. 9. Press Alt+C to open a command prompt window and enter: cd \ 10. To access the registry editor, enter: regedit The Registry Editor window opens (Figure 26). 11.
Replacing and Configuring Appliance Components 25. Press Alt+C to open a command prompt window and enter: cd \ copy \\PeerInterLinkAddress\C$\tempPeerReg.reg regedit The Registry Editor window opens. 26. Click Registry > Import Registry File. The Import Registry File dialog box opens. 27. Select the tempPeerReg.reg file from the c:\ drive and click Open. 28. Click OK when the Registry Editor window opens. 29. Close the Registry Editor window. 30.
Replacing and Configuring Appliance Components Figure 26: Registry Editor window Figure 27: Export Registry File dialog box Continuous Access Storage Appliance Installation and Maintenance Guide 111
Replacing and Configuring Appliance Components Reconfiguring the host bus adapters This section describes the procedures for: ■ Replacing an HBA ■ Resetting the firmware parameters for an initiator HBA ■ Updating the HBA firmware Replacing an HBA This section describes the procedures for: ■ Replacing the shared storage initiator HBA ■ Replacing a target/initiator HBA The HBA replacement specifications follow: ■ Part number—A7546-69001 ■ Description—QLogic 2344F four–port full– profile HBA ■
Replacing and Configuring Appliance Components This command displays the contents of the sanlink log, including the search string and a four–digit number as follows: verifySharedDiskScsiAddress – Shared Disk found at 4 0 0 0. 11. Search the log to find a four–digit number that is not equal to 4 0 0 0, such as: verifySharedDiskScsiAddress – Shared Disk found at 6 0 0 0. 12. Record the number that you find. 13. To open the sanlink.cfg file in Notepad, enter: cd c:\Rpic notepad sanlink.cfg 14.
Replacing and Configuring Appliance Components Replacing a target/initiator HBA To replace a target or initiator HBA: 1. Power down the appliance node with the defective adapter. 2. Disconnect the shared storage Fibre Channel cables from the defective adapter. 3. Replace the defective adapter. 4. Power up the appliance node. Note: Ensure that the new adapter’s BIOS complies with the current SANOS version.
Replacing and Configuring Appliance Components Resetting the firmware parameters for an initiator HBA To reset an initiator HBA’s firmware parameters: Note: The firmware parameters for the target HBAs are set when the target driver loads during RPIC DPF setup. 1. Reboot or turn on the appliance node. 2. When prompted, press Ctrl+Q. The Select Host Adapter menu opens, listing the available HBAs in scan order. 3. Select the first adapter and press Enter. The Fast!UTIL Options menu opens. 4.
Replacing and Configuring Appliance Components 9. To select a parameter, highlight the parameter name and press Enter. Then specify the value for the parameter listed below.
Replacing and Configuring Appliance Components Updating the HBA firmware You may need to update the firmware of the node’s HBAs if a bug is found in the firmware. Before updating the firmware: 1. Verify the firmware version supported on the appliance: a. Access the following internal HP web site: http://turbo.rose.hp.com/spock/ b. Locate the Storage Virtualization section. c. Select the appropriate support matrix for the appliance. 2. Format a bootable disk from your desktop: a.
Replacing and Configuring Appliance Components Reconfiguring the Gigabit Ethernet card This section describes the procedures for: ■ Replacing the Gigabit Ethernet card ■ Reconfiguring the driver The Gigabit Ethernet card replacement specifications as follows: ■ Part number—A7547-69001 ■ Description—Dual–port Gigabit Ethernet Card ■ Assembly number—A7547-60001 Replacing the Gigabit Ethernet card To replace the Gigabit Ethernet card: 1.
Replacing and Configuring Appliance Components 19. Repeat step 18 for the SMS service. 20. Close the Services window. 21. Reboot the appliance node. 22. Verify that all services have started successfully. 23. From the console window, click sanos admin > launch. 24. Log in to sanosadmin. 25. To verify that the peer node information is correct, enter the following command: get node 26. Repeat step 25 on the peer node. 27.
Replacing and Configuring Appliance Components Reconfiguring the driver If you update the driver of the Gigabit Ethernet card, you must reconfigure the driver. Note: You do not have to reconfigure the driver if the Gigabit Ethernet card is being replaced. To reconfigure the driver: 1. Power on the appliance node. 2. Ensure that the hp OV CASA Console window is open in administrative mode. 3. Right click the console window and click Network Neighborhood > Properties. The Properties window open. 4.
Replacing and Configuring Appliance Components Reconfiguring the console switch user interface You use the HP console switch to move between appliance nodes and to run configuration procedures. When you replace the console switch, you must reconfigure the user interface for the console switch. To reconfigure user interface, which is called the HP ID window: 1. Press Ctrl twice to access the console switch user interface. 2. Press Ctrl four times to access the Administrator Command menu. 3.
Replacing and Configuring Appliance Components 122 Continuous Access Storage Appliance Installation and Maintenance Guide
Reinstalling the Appliance Software 7 This chapter describes how to reinstall the appliance software. You may need to reinstall the appliance software if one of the appliance nodes does not boot properly and troubleshooting efforts have not corrected the problem. Note: Perform a reinstallation only if the CASA support team instructs you to do so.
Reinstalling the Appliance Software Reinstalling the appliance software Use the image CD provided by HP support to reinstall the appliance software on the defective appliance node: Caution: Disconnect the cables between the initiator ports on the defective appliance node and the external storage arrays. 1. Insert the image CD into the CD-ROM drive and reboot. The following prompt is displayed: WARNING! All partitions on this system will be deleted. Strike a key when ready...
Reinstalling the Appliance Software 8. Enter the network information for the appliance node and click OK. (See “Setting network properties” on page 42 for instructions.) 9. Click OK when the following message is displayed: The operation completed successfully. Please reboot this machine for the changes to take effect. Note: Do not reboot the appliance node at this time. Caution: Follow steps 11 through 14 carefully. Failure to do so may cause the appliance nodes to become inoperable. 10.
Reinstalling the Appliance Software 16. Ensure that the following services are set to Automatic: ■ Identification and Authorization Server ■ RPIC DPF ■ sv3000 Management Server (SMS) ■ Tomcat ■ VA Status Monitor (VSM) ■ WebServer 17. Reboot the appliance node. 18. On the console window, click sanos admin > initialize. 19. When prompted, enter the user name and password for the administrator account. Reenter the password when prompted. 20.
IP Mirroring A This appendix provides information to help you implement and support IP mirroring at the customer site. For an overview of IP, refer to “Managing IP Mirrors” in the HP OpenView Continuous Access Storage Appliance System Administrator’s Guide.
IP Mirroring Managing worker threads This section describes worker threads and how to use them for IP mirroring requests. It describes the following topics: ■ Worker threads overview ■ Adjusting the number of worker threads ■ Using worker threads for many-to-one IP mirroring Worker threads overview The appliance software uses worker threads to process I/O requests.
IP Mirroring Using worker threads for many-to-one IP mirroring When implementing many-to-one IP mirroring, you must reduce the number of IP mirroring worker threads; otherwise, IP mirroring will not function properly. The total number of IP mirroring worker threads for all source appliances cannot exceed 200. When calculating this number, count by appliance, not appliance node because only one appliance node can process IP mirroring requests at a time.
IP Mirroring Processing synchronous IP mirroring requests This section describes how the appliance software processes synchronous IP mirroring requests. It describes the following topics: ■ Synchronous IP mirroring process ■ IP mirroring performance Synchronous IP mirroring process Processing synchronous IP mirroring requests involves the following steps (Figure 28): 1. The host sends a request to the local LUN. 2.
IP Mirroring IP mirroring performance In Figure 28, T0 indicates the time at which the host sends I/O to the local LUN, initiating the IP mirroring request. T1 indicates the time at which the host receives a completion message from the local LUN, ending the IP mirroring request. T0 and T1 are measured in milliseconds. For example, T0 is 10:35:02:15 and T1 is 10:35:03:20. To calculate IP mirroring performance, subtract T0 from T1.
IP Mirroring Processing asynchronous IP mirroring requests Processing asynchronous IP mirroring requests involves the following steps (Figure 29): 1. The host sends a request to the local LUN. 2. A worker thread receives the request on the local LUN and completes the request. 3. Another worker thread adds the replication request data to the asynchronous IP mirroring (AIPM) queue. 4. The first worker thread waits for the second worker thread to confirm that the request has been added to the AIPM queue.
IP Mirroring Understanding resynchronization This section describes the differences between resynchronizing synchronous and asynchronous IP mirrors. It describes the following topics: ■ Synchronous IP mirrors ■ Asynchronous IP mirrors ■ Common resynchronization issues Synchronous IP mirrors If the network goes down, synchronous IP mirroring (and all other network activity) stops. During this down time, the appliance software tracks replication requests in the source LUN’s journal file.
IP Mirroring Common resynchronization issues A description of common resynchronization issues follows: ■ After you power off the resynchronizing node, synchronous IP mirrors disconnect. Temporarily disconnecting the IP mirrors starts resynchronization on the new resynchronizing node, (the peer node that is working). Resynchronizing ensures that the data on the source and target LUNs of the mirrors is current.
IP Mirroring Troubleshooting IP mirroring A description of common IP mirroring situations follows: ■ I/O stops on the hosts after disconnecting the InterLink and MirrorLink. If you disconnect the InterLink and MirrorLink, the appliance loses all connectivity to the mirror site and enters arbitration. The appliance cannot enter arbitration until all I/O times out. To prevent I/O from timing out, increase the value of the I/O time–out parameter (for example, 10 minutes).
IP Mirroring 136 Continuous Access Storage Appliance Installation and Maintenance Guide
Appliance Components B This appendix describes each appliance component and lists its physical dimensions, technical specifications, and environmental operating conditions: ■ HP ProLiant ML370G3 server, page 138 ■ HP StorageWorks Virtual Array 7110, page 139 ■ HP rack system/E, page 140 ■ HP rackmount console switch, page 141 ■ HP rackmount keyboard and monitor, page 142 ■ QLogic SANBlade QLA2344 series host bus adapters, page 144 ■ Intel PRO/1000 MT dual–port server adapter, page 145 Contin
Appliance Components HP ProLiant ML370G3 server Each appliance uses two servers, also called nodes. Each node is an HP ProLiant ML370G3 server; the appliance software is installed before it ships. The nodes are defined as peer nodes in an active-active configuration, which means that both nodes actively monitor and maintain the storage network. For more information on this server, refer to the ProLiant ML370 Generation 3 Server Setup and Installation Guide.
Appliance Components HP StorageWorks Virtual Array 7110 The Virtual Array 7110 (va7110) is the shared storage array between the two nodes. It contains the configuration information that both nodes monitor and maintain. To avoid data corruption, a file–sharing system ensures that only one node has write access to the array at any time. For more information on the array, refer to the HP StorageWorks Virtual Arrays va7000 Family User and Service Guide.
Appliance Components HP rack system/E The HP rack system/E (part number J1500A) holds the appliance components. Rack specifications Type Weight Supported weight Empty rack: 162 pounds ■ Packaged rack: 314 pounds ■ Rear door: 29 pounds Load capacity: ■ On shipping pallet: 1800 pounds (816 kg) ■ Off shipping pallet: 2000 pounds (907 kg) ■ Casters rating: 1000 pounds (453.6 kg) per caster) Rack size 41U1 Rack dimensions W x D x H (inches) 23.5 x 36.5 x 77.
Appliance Components HP rackmount console switch The HP rackmount console switch enables you to switch between nodes from the appliance monitor. You can use either the four-port console (part number J1473A) or the eight-port console (part number J1474A). Specifications Type Description Height 1.75 inches (44.4 mm) Width 17.2 inches (436.9 mm) Length 6.5 inches (165.1 mm) Weight 4.
Appliance Components HP rackmount keyboard and monitor The appliance is installed with one of the following HP rackmount keyboard and monitor sets: ■ J1470A—Requires 2U1 (EIA units) of space ■ TFT5600RKM—Requires 1U of space J1470A specifications Type Description Display 15 inches Type Active matrix TFT Resolution 1024 x 768 Weight 12.5 lbs (15.6 kg) Horizontal dot pitch 0.297 mm Brightness 220 nits (cd/m2) Display colors 16.7 million Pixel pitch (horizontal x vertical) 0.297 x 0.
Appliance Components TFT5600RKM specifications Type Description Display 15 inches Type Active matrix TFT LCD Resolution 1024 x 768 Weight 13.75 lbs (6.25 kg) Horizontal dot pitch 0.29 mm Horizontal frequency (LCD) 48.2 KHz Vertical frequency (LCD) 60 Hz Pixel clock speed 65 MHz Dimensions (length x width x depth) 17 x 1.7 x 15.6 inches (4.32 x 39.6 x 43.
Appliance Components QLogic SANBlade QLA2344 series host bus adapters The appliance has three (3) QLogic 2344 host bus adapters (HBAs) per appliance node, for a total of six HBAs per appliance.
Appliance Components Intel PRO/1000 MT dual–port server adapter The appliance has one dual–port Gigabit Ethernet card per appliance node. The top port is for the MirrorLink connection (IP mirroring); and the bottom port is for the InterLink connection between the nodes.
Appliance Components 146 Continuous Access Storage Appliance Installation and Maintenance Guide
Service Messages C This appendix describes the various messages that the appliance software services generate: ■ Reading DPF messages, page 148 ■ Reading SNMP traps, page 156 ■ Reading VSM states, page 158 ■ Setting node logging levels, page 160 Continuous Access Storage Appliance Installation and Maintenance Guide 147
Service Messages Reading DPF messages This section describes the messages generated by the RPIC Data Propagation Framework (DPF) service: ■ Overview ■ I/O events ■ Network events ■ LUN mapping events ■ Host events Overview Click event viewer on the hp OV CASA Console window to view these messages Refer to “Using the CASA console” in the HP OpenView Continuous Access Storage Appliance System Administrator’s Guide for more information. Note: The messages shown in this appendix are examples only.
Service Messages I/O events This section describes the messages generated by I/O events between the appliance and the storage network components, including storage arrays, routers, and switches: ■ I/O timeout ■ I/O failure ■ Hardware device failure ■ Hardware device recovery I/O timeout An I/O timeout, which is defined as an instance when a confirmation for a data packet transmission is not received by the appliance within a configured time period, causes the following error message to appear: RPIC
Service Messages Hardware device failure When a storage device fails, it is marked as failed by the appliance and monitored for recovery. A hardware device failure, which occurs when a storage device develops a physical defect, causes the following error message to appear: RPIC DPF : IOFD dvfd : Device hardware failure : adapter %d bus %d SCSI %d LUN %d : DPF Lun %d : Status %x Sense %x ASC %x ASCQ %x This error condition is recorded in the event log.
Service Messages Network events This section describes messages generated by status changes to nodes within the storage network: ■ Network node failure ■ Network node time out ■ Network node recovery Network node failure When a network node is detected to be non-operational, the following error message is reported: RPIC DPF : NETW nddn : Network node marked down : [failover | mirror] : %d.%d.%d.%d This error condition is recorded in the event log.
Service Messages Network node recovery When a network node that was previously detected to be down or unreachable due to time out conditions, is detected to once again be operational, a network node recovery message is generated. This message appears in the following format: RPIC DPF : NETW ndup : Network node marked up : ["failover" | "mirror"] : %d.%d.%d.%d This error condition is recorded in the event log.
Service Messages LUN mapping events This section describes messages generated when the LUN mapping for a host changes: ■ LUN mapping enabled ■ LUN mapping disabled LUN mapping enabled When a LUN is mapped to a host, a LUN mapping enabled confirmation message is generated. This message appears in the following format: RPIC DPF : LMAP emap : Lun mapping enabled : Lun %d : Host %d : Visible Lun %d : HBA %d This message is recorded in the event log.
Service Messages Host events This section describes the messages generated by host registration or other host activity within the storage network: ■ Host addition ■ Host name registration ■ Host removal ■ Host activity on new host bus adapter (HBA) Host addition When a new host is configured for use within the storage network, a host addition confirmation message is generated.
Service Messages Host removal When a host is removed from the storage network, a confirmation message is generated. This message appears in the following format: RPIC DPF : HOST hrem : Host removed from lookup table : Index %d : WWN %s This message is recorded in the event log. The first number, which is represented in decimal format, indicates the table index at which the host had appeared within the lookup table.
Service Messages Reading SNMP traps After you run the initservice slsemi,slsnmp, sltat command when initializing the user database (see page 48), the slsnmp module gathers information from the sv3000 Management Server (SMS) service and formats it in SNMP. Table 8 lists the SNMP traps generated by SMS.
Service Messages Table 8: SNMP trap descriptions Number Type Variables Message 61 remoteMirrorAdded remoteMirrorSourceLunNumber, remoteMirrorTargetLunNumber Appliance remote mirror with source LUN %d, target LUN %d, has been added. 62 remoteMirrorStateChange remoteMirrorSourceLunNumber, remoteMirrorTargetLunNumber, remoteMirrorState Appliance remote mirror with source LUN %d, target LUN %d, has changed state to %d.
Service Messages Reading VSM states Figure 9 lists the states that the VA Status Monitor (VSM) service gathers from the appliance’s shared storage array. Table 9: VSM states Value Name Description 0 Ready The subsystem is fully functional and ready to provide storage to meet the host's needs. The subsystem has completed its power up sequence prior to reaching this state. 1 Warning The subsystem encountered an error requiring attention but the error does not prevent access to data.
Service Messages Table 9: VSM states Value Name Description 10 Shutdown Warning The subsystem was shut down but problems were detected that make it unsafe to change the system configuration (for example, you should not add or remove DIMMs). 11 Reserved Reserved 12 Mismatched Code The two controllers have different firmware versions and are operating independently. To resolve this error, download the latest code on the primary controller, which enables the download on the other controller.
Service Messages Setting node logging levels The health monitor issues SNMP requests to the ProLiant insight management agents installed on the appliance nodes. The status information gathered by the health monitor displays in the status info section of the hp OV CASA Console window (See Navigating the CASA console on page 24 for more information.) The health monitor uses a logger to assist with troubleshooting. You can modify the logging levels using the logging_level parameter contained in the logger.
Miscellaneous Commands D This appendix describes the command line interface (CLI) commands that are intended for HP personnel use only.
Miscellaneous Commands add trapdest Syntax add trapdest -ip IPADDRESS1,...,IPADDRESSN -community COMMUNITY_NAME Example Command add trapdest -ip 16.129.99.70 -community private Purpose Adds a trap recipient so it can receive traps from the appliance nodes. Output Trap destination 16.129.99.70 added to community PRIVATE.
Miscellaneous Commands build Syntax build Example Command build Purpose Displays the version of the sv3000 Management Server (SMS) service with which sanosadmin is communicating. Output Apr 28 2004 19:07:48, SMS Version: 4.
Miscellaneous Commands del trapdest Syntax del trapdest -ip IPADDRESS1,...,IPADDRESSN [-community COMMUNITY_NAME] Example Command del trapdest -ip 196.26.99.70 Purpose Deletes a trap recipient so it no longer receives traps from the appliance nodes. If you do not include the -community parameter, the specified trap recipient is deleted from all communities. Output Trap destination 196.26.99.70 deleted successfully from PRIVATE.
Miscellaneous Commands get pollint Syntax get pollint Example Command get pollint Purpose Displays the time interval (in minutes) that passes before the LUN statistics cache in the slstat SNMP agent is refreshed.
Miscellaneous Commands get protocol_version Syntax get protocol_version [-ina] [-sms] Example Command get protocol_version -ina Purpose Displays the version of the Identification and Authorization (INA) service that is currently running on the local node. Output INA: 2.0 Command get protocol_version -sms Purpose Displays the version of the sv3000 Management Server (SMS) service that is currently running on the local node. Output SMS: 4.
Miscellaneous Commands get trapdest Syntax get trapdest [-community COMMUNITY_NAME] Example Command get trapdest Purpose Displays the IP address and community name of the servers receiving traps from the appliance nodes. If you do not include the -community parameter, the output includes the trap recipients for all communities. Output Community _________ IP _______________ private 16.129.99.70 public 16.129.12.
Miscellaneous Commands get version Syntax get version Example Command get version Purpose Displays the version of SANOS that is running on the node you are accessing. Output SAN.OS Version --------------5.7.0.
Miscellaneous Commands get vsmpollingint Syntax get vsmpollingint Example Command get vsmpollingint Purpose Displays the amount of time (in seconds) that the VA Status Monitor (VSM) service waits before sending the next query for status to the appliance’s shared storage array.
Miscellaneous Commands get vsmremindint Syntax get vsmremindint Example Command get vsmremindint Purpose Displays the amount of time (in seconds) that the VA Status Monitor (VSM) service waits before posting a duplicate warning event if the corresponding error condition has not changed.
Miscellaneous Commands mod cache Syntax mod cache -name NAME1,...,NAMEN -refresh where NAME is expansion, partition, ptimage, fcpmirror, ipmirror, host, node, lun, lunmap, all Example Command mod cache -name all -refresh Purpose Updates the specified data in SMS (the service for the user interface) by gathering the latest data from DPF (the core component of the SANOS software).
Miscellaneous Commands mod node Syntax mod node -peer HOSTNAME | IPADDRESS [-newname NAME | IPADDRESS] | [-secondary NAME | IPADDRESS] or mod node -mirror HOSTNAME | IPADDRESS [-newname NAME | IPADDRESS ] | [-secondary NAME | IPADDRESS -proxy] or mod node -mgmt HOSTNAME | IPADDRESS -newname NAME | IPADDRESS Note: You can only modify a node using the CLI. Examples Command mod node 11.0.0.1 -peer -newname 11.0.0.
Miscellaneous Commands Command mod node 10.0.0.3 -mirror -newname 10.0.0.1 -secondary 11.0.0.4 -proxy Purpose Before using this command, use the CASA setup utility to change the mirror node’s name or IP address. This enables the Windows operating system to identify the node by its new name or IP address. Next, use the mod node command to change the node’s information to enable the appliance software to identify the node by its new name or IP address.
Miscellaneous Commands mod pollint Syntax mod pollint -interval INTERVAL Example Command mod pollint -interval 15 Purpose Sets the time interval (in minutes) that passes before the slstat SNMP agent refreshes the LUN statistic cache. Output Polling interval 15 was successfully set in the registry.
Miscellaneous Commands mod trapdest Syntax mod trapdest -oldip IPADDRESS -newip IPADDRESS [-community COMMUNITY_NAME] Example Command mod trapdest -oldip 16.129.99.70 -newip 16.129.99.75 Purpose Modifies the IP address and/or the community name of the trap recipient. If you do not include the -community parameter, the community name is associated with the new IP address. Output Trap destination 16.129.99.70 successfully changed to 16.129.99.75 in community PRIVATE.
Miscellaneous Commands mod updatedb Syntax mod updatedb -old old_hostname -new new_hostname Example This command applies to version 5.0.4 or earlier of the appliance. If the IP address of one of the nodes changes and you are running version 5.0.4 or earlier, you must run this command to update the database with the new node information. Command mod updatedb -old 14.1.195.23 -new 13.1.194.24 Purpose Updates the database with the new IP address specified for the node. Output Database updated successfully.
Miscellaneous Commands mod vsmpollingint Syntax mod vsmpollingint -interval VALUE Example Command mod vsmpollingint -interval 8 Purpose Modifies the amount of time (in seconds) that the VA Status Monitor (VSM) service waits before sending the next query for status to the appliance’s shared storage array. Output VSM polling interval changed to 8.
Miscellaneous Commands mod vsmremindint Syntax mod vsmremindint -interval VALUE Example Command mod vsmremindint -interval 20 Purpose Modifies the amount of time (in seconds) that the VA Status Monitor (VSM) service waits before posting a duplicate warning event if the corresponding error condition has not changed. Output VSM reminder interval changed to 20.
index CASA setup utility 17, 108, 118, 124, 172 node 0 settings 42 node 1 settings 43 running 45 cascaded appliances connecting 88 creating fabric zones 91, 92 dedicated ports 88 collecting logs 100 command prompt window, using 29 commands add trapdest 162 build 163 del trapdest 164 get pollint 165 get protocol_version 166 get trapdest 167 get version 168 get vsmpollingint 169 get vsmremindint 170 mod cache 171 mod node 172 mod pollint 174 mod trapdest 175 mod updatedb 176 mod vsmpollint 177 mod vsmremindi
Index configuring storage arrays 67 configuring the shared storage array creating LUN 0 104, 105 creating partitions 107 detecting the array 102 connecting cascaded appliances 88 cascaded appliances directly 88 cascaded appliances through switches and fabrics 90 hosts and EVAs through switches 86 hosts and storage directly 82 hosts and storage through switches 84 nodes to shared storage 20 two appliances through a WAN 87 console administrative mode 26 known issues 30 navigating 24 setting the console displ
Index technical support 14 HP fiber card drivers supported operating systems 56 HP rack system/E, specifications 140 HP rackmount console switch, specifications 141 HP rackmount keyboard and monitor, specifications 142 HP Server Diagnostics, for ProLiant servers 50 Hyper Terminal 105 I I/O events 149 Identification and Authorization Server (INA) 44 identifying node components 18 implementing path failover 69 initializing services 49 initializing user database 48 initiator HBA replacing 114 resetting firmw
Index for Solaris hosts 60 for Windows hosts 59 supported operating systems 56 QLogic HBAs, specifications 144 R rack stability, warning 13 reconfiguring console switch user interface 121 Gigabit Ethernet card driver 120 HBA firmware 117 shared storage array 101 Registry Editor 109 reinstalling the appliance software 124 related documentation 10 replacing Gigabit Ethernet card 118 hard disk drive 108 host HBAs 62 shared storage array 101 shared storage initiator HBA 112 target/initiator HBA 114 resetting
Index V VA Status Monitor (VSM) 44 Veritas Volume Manager 65, 66 viewer mode 25 Virtual Array 7110 16 specifications 139 VSM states 158 W warning rack stability 13 symbols on equipment 12 web sites CASA Support Team 14 HP storage 14 Workforce Development 14 Continuous Access Storage Appliance Installation and Maintenance Guide WWW Storage Support Knowledge Portal 14 WebServer 44 Windows diskpart utility 63 wiring the appliance 81 cascaded appliances 88 directly connecting hosts and storage 82 hosts and
Index 184 Continuous Access Storage Appliance Installation and Maintenance Guide