HP SureStore SAN Manager LUN Management HP-UX Installation Guide Edition 1000 Printed in U.S.A.
Notice Restricted Rights Legend © Hewlett-Packard Company, 1999, 2000. All rights reserved. 1999, 2000 Hewlett-Packard Company. All rights reserved. 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.
Format Conventions Denotes Caution A condition or situation that could damage or destroy the product or the user’s work Note Significant concepts or operating instructions this font Text to be typed verbatim: all commands, path names, file names, and directory names Buttons and tabs to click; for example, the Save button. this font Variables within HP-UX commands A submenu; for example, Database Scan For Devices means to select the Scan For Devices option in the Database menu.
Preface This installation guide explains how to install, use, and troubleshoot HP SureStore SAN Manager LUN Management (SAN Manager LM) software on HP-UX hosts. This guide is a supplement to the HP SureStore SAN Manager LUN Management Administrator’s Guide and is intended for SAN Administrators with SAN Manager LM networks that include HP-UX hosts. This guide assumes that you have a working knowledge of the HP-UX Operating System and its conventions.
Contents CONTENTS 1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 SAN Manager LM Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 INSTALLATION Installation System Requirements SAN Manager LM Bundles Components Pre-Installation Installing SAN Manager LM Starting SAN Manager LM Adding HP-UX Hosts to the SAN Database Uninstalling SAN Manager LM 7
System Requirements All SAN Manager LM HP-UX hosts must meet the following system requirements: • HP-UX 11.0 64-bit • The following bundles from the DART 51 HP-UX software release must be installed: Table 1 DART 51 Bundles Bundle ID Version Name A5158A B.11.00.05 HP PCI Tachyon TL Fibre Channel B7609BA A.03.20 Event Monitoring Service Note The Event Monitoring Service bundle is not required, but if it is present on the host, it must be version A.03.20 or later.
• A Windows NT computer with SAN Manager LM version 1.2 or later installed and configured, which is on the same SAN and LAN as the HP-UX host, and has a D8602B host bus adapter card installed. Note Installation Verify that you are using a qualified host bus adapter driver. For a list of qualified Windows NT HBA cards and drivers, see the SAN Manager LM for Windows NT Release Notes, or HP’s Customer Care website. See the Administrator’s Guide for the SAN Manager LM for Windows NT system requirements.
SAN Manager LM Bundles The SAN Manager LM installer includes the following bundles: • SANManLM-CORE: The SAN Manager LM software • SANManLM-DOC: Adobe Acrobat PDF versions of the SAN Manager LM for HP-UX Installation Guide and the SAN Manager LM for HP-UX Release Notes Note 10 To view the electronic versions of the SAN Manager LM documentation, you must have Adobe Acrobat Reader installed. The Acrobat Reader installer is available on the SAN Manager LM CD-ROM.
Components Table 2 SAN Manager LM HP-UX Components Description /sbin/TRSANManService The SAN Manager LM daemon, which is started at boot time. /sbin/TRSANManStarter This application is run early in the boot process to prepare the system for SAN Manager LM. /sbin/TRSANManInitrc The script that runs TRSANManStarter. This script is run by init early in the boot process. /sbin/SANManLM A directory that holds several run-time files. /opt/SANManLM/conf/LMreg.
Table 3 Files that are modified when SAN Manager LM is installed File Description /sbin/ioscan -- /sbin/LMscan The SAN Manager LM installer copies /sbin/ioscan to /sbin/LMscan, and then copies /opt/SANManLM/bin/ioscan to /sbin/ioscan. SAN Manager LM can then edit the results of ioscan to properly reflect the storage assigned to the host. /etc/inittab Table 4 This file is modified to force init to run /sbin/TRSANManInitrc early in the boot process.
Pre-Installation Install a Fibre Channel HBA Card Into Each Computer Installation 1. Verify that the computer functions properly before installing the HBA. 2. Shut down the computer. 3. Install the HBA. For instructions, see the documentation that came with the A5158A HBA. 4. Cable each computer to the hub or switch. 5. Power up the computer. Pre-Installation Checklist 1. Does the computer meet SAN Manager LM’s system requirements? 2. Is the HBA installed? 3.
6. Is SAN Manager LM licensed for HP-UX hosts? Run SAN Manager LM on a Windows NT host to check your licensing information. For more information about licensing, see the SAN Manager LM Administrator’s Guide. 7. Is the Fibre Channel network hardware (hubs, switch, etc.) powered up? 8.
Installing SAN Manager LM 1. The instructions in this section are for installing SAN Manager LM on HP-UX hosts with X Windows. For information on installing SAN Manager LM without X Windows, see the man pages for swinstall. Installation Note On the host where you will install SAN Manager LM, log in as superuser. Note If you have HP OpenView Software Distributor, you can install the software remotely. For more information, see your Software Distributor documentation. 2.
4. Do one of the following: – When installing from a local CD-ROM or a network directory, type swinstall and press Enter. – When installing from a remote CD-ROM or network directory, use the command swinstall remote machine:/depot location. For example, if the remote machine is called server1, and you are installing from a CD-ROM that is mounted to /cdrom, the command would be swinstall server1:/cdrom. The Specify Source dialog box appears. 5.
The installer lists the available software bundles. Installation 7. Select SANManLM-CORE and SANMan-DOC and choose Actions Install (analysis). The bundles selected in step 7 are reflected in the Software Selection dialog box.
Note In the Marked column, the SANManLM-CORE package will be listed as “Partial” instead of “Yes” because the bundle includes components that are not enabled for this release. During the install analysis step, the installer checks for an existing SAN Manager LM installation and verifies that installation prerequisites such as available disk space are met. The Install Analysis dialog box appears. 8. If the Status says Ready, click OK.
9. Click Yes. When the installation is done, the following dialog box appears: Installation Note For details about what was done during installation, read the Logfile. 10. Click Done. 11. Exit swinstall.
Starting SAN Manager LM The SAN Manager LM daemon starts at boot time. To avoid a reboot after installing SAN Manager LM on an HP-UX host, run ioscan to start the daemon. Since the standard ioscan utility was modified when you installed SAN Manager LM (see Table 3), running ioscan has additional functionality. When you run ioscan, if the SAN Manager LM daemon is not running, ioscan will start it.
Adding HP-UX Hosts to the SAN Database Installation After SAN Manager LM is installed on an HP-UX host, the host must be added to the SAN Manager LM database. This is done through the SAN Manager LM administration application, which must be run on a Windows NT host, preferably one that is configured as a primary domain controller. Adding a Host to the Database 1. On the HP-UX host that you want to add to the database, obtain the host name or IP address.
SAN Manager LM notifies you that the host was added to the SAN Manager LM database. 6. Click OK. 7. Add more hosts or click the Close button to close the Add Host dialog box. 8. Verify that the HP-UX host is listed in the Hosts pane of the SAN Manager LM Windows NT administration application. Note 22 To append the OS type to each host name in the SAN Manager LM administration application, choose View Append OS Type.
Uninstalling SAN Manager LM Do not uninstall SAN Manager LM from a host that will remain attached to the SAN. If SAN Manager LM is not installed on all attached hosts, SAN Manager LM’s exclusive storage assignments could be compromised. Installation Caution Before Uninstalling SAN Manager LM from an HP-UX Host 1. Stop I/O to any assigned Fibre Channel devices. 2. Close any open files and applications on assigned SAN devices, and unmount the devices. 3.
Uninstalling SAN Manager LM 1. Run swremove. 2. In the list of software bundles, select SANManLM-CORE and SANManLM-DOC. 3. Choose Actions Mark for Remove. 4. Confirm that the correct bundles are selected. 5. Select Actions Remove (analysis). 6. If the remove analysis status says Ready, click OK to continue. Note If the remove analysis does not return a Ready status, read the Logfile to determine the cause of the failure. 7. When prompted to confirm the software removal, click Yes. 8.
2 STORAGE MANAGEMENT Supported Partition Map Formats Assigning Fibre Channel Disks to HP-UX Hosts Storage Management Using Assigned Storage 25
Supported Partition Map Formats Using the SAN Manager LM application on a Windows NT host, you can assign the following types of LUNs (devices) to HP-UX hosts: Unknown/Raw, NTFS/FAT. If you intend to use these types of LUNs in an HP-UX environment, the necessary HP-UX file systems (HFS or VxFS) must be created. Note HFS and VxFS disks that have been formatted on HP-UX hosts are not displayed with a special icon badge in the SAN Manager LM administration application.
UPM Format SAN Manager LM’s Universal Partition Map (UPM) format is not supported on HP-UX hosts. If you try to assign any type of UPM partition to an HP-UX host, the following dialog box appears: Storage Management If you click Yes to All or Yes, the following dialog box appears: Click OK. If you want to assign this device to an HP-UX host, you must remove the UPM from the device. For instructions, see the section “Erasing a UPM” in Chapter 5 of the Administrator’s Guide.
Assigning Fibre Channel Disks to HP-UX Hosts When you run ioscan on an HP-UX host that has no assigned devices, all of the devices in the SAN Manager LM database are listed with the hardware path to each target. For example: 10/1/4/0 fc 10/1/4/0.8 HP Tachyon TL/TS Fibre Channel Mass Storage Adapter fcp 10/1/4/0.8.0.255.0 FCP Protocol Adapter ext_bus 10/1/4/0.8.0.255.0.0 target 10/1/4/0.8.0.255.0.2 target 10/1/4/0.8.0.255.0.3 target 10/1/4/0.8.0.255.0.4 target 10/1/4/0.8.0.255.0.
Listing Newly Assigned Devices To list the newly assigned Fibre Channel devices, type ioscan -k and press Enter. Note When you use the ioscan -k command, newly assigned devices are listed, but the HP-UX system does not scan for devices that have been added to the SAN since the last ioscan. When there are assigned devices, running ioscan will list the hardware paths to all of the SAN Manager LM targets plus the assigned LUNs. For example: 10/1/4/0 10/1/4/0.
Listing the Special File Names for Assigned LUNs To list all of the local and Fibre Channel disks that are accessible to an HP-UX system, type ioscan -knfC disk and press Enter. This command will list the hardware path and special file name of all local and Fibre Channel devices. Note In this command, k tells the system not to search for new targets, n includes special file names in the list, f is for a full listing of devices, and C disk tells the system that the class of the items to list is disks.
Using Assigned Storage Once Fibre Channel devices are assigned to an HP-UX host, they are ready to use. Storage management utilities such as System Administration Manager (SAM) or VERITAS Volume Manager should work normally on assigned SAN Manager LM devices. Note Storage management utilities can access all SCSI disks, but can only access Fibre Channel disks that have been assigned in the SAN Manager LM administration application. SAN disks that are not assigned are not accessible.
Using Assigned Storage
3 TROUBLESHOOTING Verifying that the Daemon is Running Viewing the LogFile An HP-UX Host is Grayed Out in the Administration Application No SAN Devices are Available on an HP-UX Host An Assigned Device Is Not Accessible to an HP-UX Host Error During Mounting: “Not A Block Device” Troubleshooting An HP-UX Host is not Discovered by a SAN Manager LM Administration Host A Device Cannot be Unassigned from an HP-UX Host 33
Verifying that the Daemon is Running To verify that the SAN Manager LM daemon is running, type ps -e | grep TR and press Enter. If the daemon is running, this command should return the following response: TRSANManServic. For example: sb-c3po# ps -e 14443 pts/0 |grep TR 0:00 TRSANManServic If the daemon is not running, check the logfile (/tmp/Service.log) for errors. To start the daemon, type ioscan and press Enter. If you want to verify that the daemon started successfully, check the logfile.
Viewing the LogFile The SAN Manager LM logfile (/tmp/Service.log) is a useful troubleshooting tool. The following example shows the logfile on a system where the service (daemon) initialized properly and found the SAN Manager LM database. sb-c3po# cat /tmp/Service.
An HP-UX Host is Grayed Out in the Administration Application The possible causes and solutions for this problem are listed in order from the most likely to the least likely cause. If one solution does not work, continue by investigating the next cause/solution in the list. Symptom Cause/Solution An HP-UX host is displayed with a gray missing host icon. The host’s status in the SAN Manager LM administration application is incorrect. Ping the host in the SAN Manager LM administration application.
Symptom Cause/Solution There is an IP connectivity problem. To verify IP connectivity between the hosts, ping both hosts. Enter the following command to ping the HP-UX host from the Windows NT host: c: ping -t hostname To ping a Windows NT host from an HP-UX host, enter the following command: ping ip_address if you cannot successfully ping both hosts, investigate and fix the IP connectivity problem, and then ping the missing host in the SAN Manager LM administration application.
No SAN Devices are Available on an HP-UX Host If no assigned SAN devices are listed on an HP-UX host, find the cause below that best describes the situation, then attempt the solution. Symptom Cause/Solution No assigned SAN devices are available on an HP-UX host. The host bus adapter (HBA) or drivers are not installed. Install the HBA or drivers. SAN-attached storage or other network hardware is powered off. Power on the drives or network hardware. Network cables are not connected properly.
An Assigned Device Is Not Accessible to an HP-UX Host Symptom Cause/Solution An assigned SAN device is not accessible on an HP-UX host. The LUN is outside of HP-UX’s addressing ability. If a device is in peripheral device LUN addressing mode and its LUN is greater than 7, HP-UX hosts will be unable to access the LUN. If possible, put the device into a different addressing mode, for example, volume set addressing mode. Note Some arrays call volume set addressing mode “HP-UX mode.
Error During Mounting: “Not A Block Device” Symptom Cause/Solution When mounting a device, you get the following error message: mount: /dev/rdsk/ disk_name not a block device There was an error in the mount command. This error occurs when you try to mount a disk by using the raw device name rather than the correct block device name.
An HP-UX Host is not Discovered by a SAN Manager LM Administration Host When adding HP-UX hosts to the SAN, the following errors may occur: • After adding an HP-UX host to the SAN, it is not listed in the hosts pane of the SAN Manager LM administration application on a Windows NT host. • When using the Add Host command, the SAN Manager LM application reports that it cannot resolve IP address to host name or cannot ping SAN Manager LM on the host.
Symptom Cause/Solution There is a connectivity problem between the HP-UX host and the SAN database. Check the following: – View the /tmp/Service.log file. If the file does not contain a line similar to the following example, the host did not find the SAN Manager LM database: Init DB found index 0 id 2009814699 Note In the previous example, 2009814699 is the ID number of the database. This number is different on every SAN. For more information about the logfile, see page 35.
A Device Cannot be Unassigned from an HP-UX Host Symptom Cause/Solution When unassigning a device from an HP-UX host, the administration application notifies you that the device cannot be unassigned. The device contains a mounted file system that is in use. Stop any processes that are using the file system, unmount the device, then unassign the device with the SAN Manager LM administration application.
A Device Cannot be Unassigned from an HP-UX Host
INDEX A Adobe Acrobat Reader 10 assigned SAN devices listing 29 B bundles SANManLM-CORE 10 SANManLM-DOC 10 C Cautions reformatting NTFS devices 26 uninstalling SAN Manager LM 23 components 11 D daemon starting 20 devices troubleshooting 38, 43 F Fibre Channel disks assigning to HP-UX hosts 28 H HBA installing 13 HP OpenView Software Distributor 15 HP-UX hosts adding to the SAN database 21 getting the hostname 21 getting the IP address 21 starting the daemon 20 troubleshooting 36, 41 I installation pre-ins
S SAN devices using assigned SAN storage 31 SAN Manager disks verifying availability 29 SAN Manager LM bundles 10 components 11 installation 15 pre-installation 13 preparing the FC disks 28 system requirements 8 uninstalling 23 SAN Manager LM bundles SANManLM-CORE 10 SANManLM-DOC 10 supported partition map formats NTFS 26 unknown/raw 26 System Administration Manager (SAM) 31 system requirements 8 T troubleshooting “not a block device” error 40 a device cannot be disabled from an HP-UX host 43 an HP-UX host
Reader Comment Sheet Hewlett-Packard SureStore SAN Manager LUN Management HP-UX Installation Guide We welcome your evaluation of this manual. Your comments and suggestions will help us improve our publications. Remove this page and mail or fax it to (916) 785-1679. Agree Disagree N/A The manual is well organized. The information is technically accurate. Information is easy to find. Step-by-step procedures are easy to perform.
12 3267$*( 1(&(66$5< ,) 0$,/(' ,1 7+( 81,7(' 67$7(6 %86,1(66 5(3/< 0$,/ ),567 &/$66 0$,/ 3(50,7 12 526(9,//( &$ 3267$*( :,// %( 3$,' %< $''5(66(( $WWHQWLRQ ,QIRUPDWLRQ (QJLQHHULQJ 06 +HZOHWW 3DFNDUG &RPSDQ\ 6$1 0DQDJHPHQW 6RIWZDUH 2UJDQL]DWLRQ )RRWKLOOV %RXOHYDUG 5RVHYLOOH &$ 9 9 Fold Here Tape Please Do Not Staple Tape
&RS\ULJKW +HZOHWW 3DFNDUG &RPSDQ\ 3ULQWHG LQ 8 6 $ )RU ,QWHUQDO 8VH 2QO\
