HP SureStore E SAN Manager LUN Management Solaris Installation Guide H Edition 0900 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 Text displayed on the screen 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 E SAN Manager LUN Management (SAN Manager LM) software on Sun Solaris nodes. This guide is a supplement to the HP SureStore E SAN Manager LUN Management Administrator’s Guide and is intended for SAN Administrators with SAN Manager networks that include Sun Solaris nodes. This guide assumes that you have a working knowledge of the Solaris Operating System and its conventions.
Contents CONTENTS 1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 SAN Manager LM Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 SAN Manager LM Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mounting UFS File Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Mounting File Systems Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Using the vfstab File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 3 SAN Manager LM Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 SAN Manager LM Utilities . . . . . . . . . . . .
1 INSTALLATION Installation System Requirements SAN Manager LM Packages SAN Manager LM Components Pre-Installation Installing SAN Manager LM Configuration 7
System Requirements All SAN Manager LM Solaris nodes must meet the following system requirements: • Solaris Workstation or Server 2.6 or 7 Note SAN Manager LM works with Solaris 7 in 32-bit mode only. Solaris 7 in 64-bit mode is not supported.
SAN Manager LM Packages The SAN Manager LM installer includes the following packages: TRSANfcd: The SAN Manager LM software • TRSANdoc: Adobe Acrobat PDF versions of the SAN Manager LM for Solaris Installation Guide and the SAN Manager LM for Solaris Release Notes Note Installation • To view the electronic versions of the SAN Manager LM documentation, you must have Adobe Acrobat Reader installed. The Acrobat installer is available on the SAN Manager LM CD-ROM.
SAN Manager LM Components Table 1 SAN Manager LM Solaris Components File name Description sd_fcst Fibre Channel SCSI-Target driver with SAN Manager LM support tfc Qlogic Host Bus Adapter (HBA) driver TRSANManService SAN Manager LM Service S99TRService Starts the SAN Manager LM Service at boot time Note 10 Unless you choose a custom location, the SAN Manager LM application, service, and utilities are installed into the /opt/TRSANfcd/bin directory.
Pre-Installation Installation If you are installing SAN Manager LM on a node that is running Solaris 7, read the QLogic HBA driver section below. Otherwise, skip to the HBA installation section on page 12. On Solaris 7 Stations Only: Remove the QLogic HBA Driver Solaris 7 is packaged with an OEM software package that includes a QLogic HBA driver. If the OEM software package is installed, you must remove the OEM QLogic driver before installing SAN Manager LM.
Install a Fibre Channel HBA Card Into Each Computer 1. Verify that the computer functions properly before installing the HBA. 2. Shut down the computer. 3. Install the HBA. For instructions, see your HBA installation guide. 4. Cable each computer to the hub or switch. 5. Power up the computer. Caution For Solaris 7 nodes, remember to start up the computer in 32-bit mode. SAN Manager LM cannot be installed on a Solaris 7 node that is running in 64-bit mode.
Is SAN Manager LM licensed for Sun Solaris nodes? Run SAN Manager LM on a Windows NT node to check your licensing information. For more information about licensing, see the HP SureStore E SAN Manager LUN Management Administrator’s Guide. 7. Is the Fibre Channel network hardware (hubs, switch, etc.) powered up? 8. Are the optical/copper Fibre Channel cables properly connected to the HBAs, hubs or switches, and storage disk array enclosures? Installation 6.
Installing SAN Manager LM 1. For Solaris 7 nodes only: Start up the node in 32-bit mode. 2. Log in as superuser. 3. Insert the SAN Manager LM CD-ROM in the CD drive. By default, the CD-ROM mounts to the /cdrom/sanman directory. If the CD does not mount automatically, enter the following command: mount -F hsfs -o ro /vol/dev/dsk/c0t2d0 /cdrom/sanman Note 4. Mount points may vary depending on your system configuration.
When the SAN Manager LM software package has been added, the Console displays the following information as it loads the SAN Manager LM QLogic driver and Target driver: Hewlett-Packard TFC Driver Copyright 1999 Hewlett-Packard Company Installation Sparc Qlogic Driver version 1.0.0 (08:32:13, Nov 1 1999) TFC: Attaching pci1077,2100 instance 1 HP Sparc Fibre Target Driver version 1.0 Build 62 (10:10:18, Apr 27 2000) TFC Driver: loop 0 up The installation is now complete.
Configuration After SAN Manager LM is installed on a Sun Solaris node, the node 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 node, preferably one that is configured as a primary domain controller.
The Add Node dialog box appears. Installation 4. Select Node Name or IP Address. 5. Enter the host name or IP Address and click the Add Node button. 6. Add more nodes or click Close to close the Add Node dialog box. 7. Verify that the host name of the Solaris node is displayed in the main window of the SAN Manager Windows NT administration application. You are now ready to set up storage devices for use with SAN Manager LM.
Configuration
2 STORAGE MANAGEMENT Supported Partition Map Formats Preparing a Fibre Channel Disk for use with SAN Manager LM Storage Management Creating a UFS File System Mounting UFS File Systems Mounting File Systems Automatically 19
Supported Partition Map Formats Using the SAN Manager LM application on a Windows NT node, you can assign the following types of LUNs (devices) to Solaris nodes: Unknown/Raw, NTFS/FAT, and UPM format. If you intend to use these types of LUNs in a Solaris environment, the necessary Solaris file systems (UFS or VxFS) must be created. Unknown/Raw Unknown/raw disks are displayed with device names in /dev/rdsk and /dev/dsk on Solaris nodes.
Preparing a Fibre Channel Disk for use with SAN Manager LM 1. On a Windows NT SAN Manager LM node, run the administration application and assign the desired devices to the Solaris node. 2. To verify that the assigned SAN Manager LM disks are available, enter ls /dev/rdsk to list the available disk devices on the Solaris node. Storage Management The Solaris node creates eight slices (partitions) for every accessible device.
Disk Setup Issues • When selecting disks to partition, be careful not to select your internal disk. • To support third-party failover software products on dual controller single loop SANs, SAN Manager devices are listed twice as available disks when you run the Format utility. If you are using a dual controller single loop SAN, be careful to partition, create a file system, and mount only one instance of each SAN disk.
2. Enter the disk number and press Return. If there is no valid partition table, the Format utility prompts you to label the disk: Disk not labeled. Label it now? n 3. If you want to label the disk with the default partition table, enter y and press Return. If you want to set up the partition label manually, enter n and press Return. 4. At the format prompt, enter p to select (define) a partition table, and press Return. 5.
The partition information is displayed along with the enter partition ID tag prompt: partition> 0 Part 0 Tag root Flag wm Cylinders 0 - 51 Size 130.41MB Blocks (52/0/0) 267072 Enter partition id tag[root]: 7. Assign a partition id tag, or press Return to accept the default value. 8. When prompted with Enter partition permission flags[wm]:, press Return to accept the default setting. 9. When prompted with Enter new starting cyl, enter the starting cylinder number.
14. At the Ready to label disk, continue? prompt, enter y and press Return. At this point, the new partition table is written to the disk. If you view this disk’s Device Information in the SAN Manager LM administration application on a SAN Manager LM Windows NT node, the device will be listed with a Sun partition map. 15. At the partition prompt, enter q and press Return. 16. To partition another disk, choose disk from the format menu, press Return, and repeat steps 2 through 15, above. 17.
Creating a UFS File System Now that your disks are partitioned, create a UFS file system on each partition. 1. At the # prompt, enter ls /dev/rdsk/c1* and press Return. In this example, c1 is the Fibre Channel controller. Solaris lists all of the enabled physical and virtual LUNs on the Fibre Channel controller. For each device, all 8 slices are listed, regardless of whether they contain partitions.
2. At the # prompt, enter newfs options /dev/rdsk/slice_name, and press Return to create a UFS file system on the partition. Solaris prompts you to confirm the request: newfs: construct a new file system /dev/rdsk/slice_name: (y/n)? 3. Enter y and press Return. 4. Repeat steps 1 through 3 to create UFS file systems on additional partitions.
Mounting UFS File Systems 1. Create a mount point by entering the following command: mkdir /mount_point, where mount_point is any user-defined name. Note To streamline your SAN administration procedures, you may want to create a directory, and then create mount points for each Fibre Channel file system within that directory, for example: # mkdir /SAN # mkdir /SAN/fibre1 2. Enter mount /dev/dsk/slice_name /mount_point to mount a file system, for example: # mount /dev/dsk/c1t17d0s0 /SAN/fibre1 3.
Mounting File Systems Automatically To mount file systems automatically at startup, add them to the /etc/vfstab file. For example, to add slice c1t17d0s0, enter it into the vfstab file.
Using the vfstab File If you unassign a device that is listed in the vfstab file and then reboot the system, the vfstab file will report errors and cause the system boot process to terminate at single-user mode: /dev/rdsk/device_name: I/O error can’t open /dev/rdsk/device_name /dev/rdsk/device_name: CAN’T CHECK FILE SYSTEM /dev/rdsk/device_name: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY WARNING—Unable to repair one or more of the following filesystem(s): SAN devices will be listed here Run fsck manually (
3 SAN MANAGER LM UTILITIES SAN Manager LM Utilities get_wwn get_loop_state SAN Manager LM Utilities 31
SAN Manager LM Utilities SAN Manager LM for Solaris includes two utilities: • get_wwn • get_loop_state 32 SAN Manager LM Utilities
get_wwn The get_wwn utility lists all discovered devices and their worldwide names. The utility is found in the /opt/TRSANfcd/bin directory.
get_loop_state The get_loop_state utility checks to see that the Fibre Channel disks are available, and reports on the status of the loop: apollo:# get_loop_state loop0 is up loop1 is up 34 get_loop_state
4 TROUBLESHOOTING No SAN Devices are Available on a Solaris Node Error During Mounting: “Not a block device” A Fibre Channel Tape Library, CD-R Drive, or Other Device is not Showing Up A Solaris Node is not Discovered by a SAN Manager LM Administration Node A Device Cannot be Disabled from a Solaris Node Troubleshooting 35
No SAN Devices are Available on a Solaris Node If no SAN devices are listed on a Solaris node, find the cause below that best describes the situation, then attempt the solution. Symptom Cause/Solution Assigned SAN devices are not available on a Solaris node. 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.
Error During Mounting: “Not a block device” Symptom Cause/Solution When mounting a device, you get the following error message: mount: /dev/rdsk/ slice_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.
A Fibre Channel Tape Library, CD-R Drive, or Other Device is not Showing Up Symptom Cause/Solution A Fibre Channel device is not showing up on a SAN Manager LM Solaris node. SAN Manager uses an alternate SCSI disk driver, which allows SAN Manager to co-exist with the standard SCSI disk driver that controls things like internal SCSI buses. SAN Manager LM for Solaris has a separate driver class for the Qlogic host bus adapter driver: tran_scsi instead of scsi. If the driver.
A Solaris Node is not Discovered by a SAN Manager LM Administration Node When adding Solaris nodes to the SAN, the following errors may occur: • After adding a Solaris node to the SAN, it is not listed in the nodes pane of the SAN Manager administration application on a Windows NT node. • When using the Add Node command, the SAN Manager LM application reports that it “cannot resolve IP address to host name” or “cannot ping SAN Manager LM on the node.
A Device Cannot be Disabled from a Solaris Node Symptom Cause/Solution When unassigning a device from a Solaris node, the Windows NT administration node displays a 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 administration application. Disable Device Failed error message.
Index INDEX C Cautions Do not delete slice 2 information 24 Do not enter overlapping cylinder numbers 24 reformatting NTFS devices 20 Starting Solaris 7 nodes in 32-bit mode 12 components, SAN Manager LM 10 H HBA installing 12 I installation 32-bit mode, requirement for Solaris 7 14 default install location 10 pre-installation 12 procedure 14 system requirements 8 M mount point creating a mount point 28 mounting file systems 28 automatically with the vfstab file 29 VERITAS 28 N Notes Adding Sun nodes to
SAN Manager LM disks creating file systems 26 mounting file systems 28 slice names conventions 21 slices defined 21 naming convention 21 Solaris 7 32-bit mode, requirement 12 pre-installation issues 11 Solaris nodes getting the hostname 16 getting the IP address 16 Sun workstations adding to the SAN 11 Supported partition map formats NTFS 20 unknown/raw 20 UPM 20 supported partition map formats NTFS 20 unknown/raw 20 UPM 20 system requirements 8 T Tips Creating a directory for mount points 28 Locating the O
Reader Comment Sheet Hewlett-Packard [SAN Manager LM for Solaris 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-2299. 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\ 6RIWZDUH DQG 6$1 0DQDJHPHQW 2SHUDWLRQ )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\
