CLARiiON® Server Support Products for HP-UX Server ... · Products for HP-UX Server Installation Guide P/N 300–002–043, Revision A08 January 16, 2007 This guide describes how

EMC CLARiiON® Server SupportProducts for HP-UX Server

Installation GuideP/N 300–002–043, Revision A08

January 16, 2007

This guide describes how to install and remove the Navisphere® StorageSystem Initialization Utility, Navisphere Host Agent, Navisphere ServerUtility, Navisphere Command Line Interface (CLI), or admsnap softwareon a Hewlett Packard HP-UX operating system.

Note: This document uses the term CX3-series to refer to CX3 model 10 systems,CX3 model 20 systems, CX3 model 40 systems, and CX3 model 80 systems, and theterm CX-series to refer to CX200, CX300-series, CX400, CX500-series, CX600, andCX700 storage systems.

Topics include:

About EMC Navisphere Software................................................... 2Finding current information ........................................................... 6Installing and removing the Navisphere Storage System InitializationUtility .......................................................................................... 7Running the Navisphere Storage System Initialization Utility........... 11Determining whether to install the host agent or server utility........... 15Requirements for the host agent, server utility, and CLI ................... 17Installing or removing the Navisphere Host Agent and CLI ............. 18Configuring the Navisphere Host Agent ......................................... 23Using the Event Monitor configuration file...................................... 39Running the Navisphere Host Agent .............................................. 40Installing and removing the Navisphere Server Utility ..................... 43Running the Navisphere Server Utility ........................................... 46Installing and removing the Admsnap Utility.................................. 50Running the Admsnap Utility ........................................................ 54

1

About EMC Navisphere Software

The following EMC® server-based software is available on the serversupport CD that shipped with your storage system :

Navisphere® Storage System Initialization Utility

Navisphere Host Agent

Navisphere Server Utility

Admsnap Utility

Navisphere Command Line Interface (CLI)

About the Navisphere Storage System Initialization Utility

For CX3-series and CX-series Fibre Channel storage systems, use theutility to discover storage systems, and set network parameters (IPaddress, subnet mask, and default gateway).

Note: For CX-series storage systems, an authorized service provider mustinstall and run the Initialization Utility.

For AX-series storage systems, use the utility to discover storagesystems, set network parameters (IP address, subnet mask, and defaultgateway), and create management user accounts. In addition, forAX150 iSCSI storage systems, use the utility to set network parametersfor the storage system’s iSCSI data ports.

You can run the Navisphere Storage System Initialization Utility fromthe server support CD or you can install it on a server that is connectedto the storage system. We recommend that you install the utility on atleast one server that is connected to the storage system.

2 EMC CLARiiON® Server Support Products for HP-UX Server Installation Guide

Note: The Navisphere Initialization Utility runs on servers attached toCX3-series, CX700, CX500-series, CX300-series, and AX-series storage systems.CX3 model 10 systems must be running FLARE® OE 03.24.010.5.xxx or later.CX3 model 20 systems, CX3 model 40 systems, and CX3 model 80 systemsmust be running FLARE OE 03.22.xxx.5.yyy or later. CX700, CX500-series, andCX300-series systems must be running FLARE OE 02.16.xxx.5.yyy or later.

About the Navisphere Host Agent

The host agent registers the server’s HBA (host bus adapter) with theattached storage system when the host agent service starts. This actionsends the initiator records for each HBA to the storage system. Initiatorrecords are used to control access to storage-system data. For legacystorage systems, the host agent will send the initiator records only ifAccess Logix™ software is installed.

The agent can then retrieve information from the storage systemautomatically at startup or when requested by Manager or CLI.

The host agent can also:

Send drive mapping information to the attached CLARiiON®storage systems.

Monitor storage-system events and can notify personnel by email,page, or modem when any designated event occurs.

Retrieve LUN WWN (world wide name) and capacity informationfrom Symmetrix® storage systems.

The host agent runs on servers attached to CX3–series and CX–series.

About the Navisphere Server Utility

The server utility allows you to perform the following three functions:

Update server information to the storage system — This optionsends the server name and IP address to the storage system and,if needed later on, allows you to update or view this data. ForWindows servers running Navisphere Server Utility version 6.20 orhigher, if the Registration Service feature remains enabled after the

EMC CLARiiON® Server Support Products for HP-UX Server Installation Guide 3

installation of the server utility, the utility will automatically registerthe server’s NICs or HBAs with the storage system and updateserver information whenever there is a configuration change (forexample, when you mount new volumes or create new partitions).

Verify server high availability (HA) — Allows you to determine ifthe server is configured for high availability (HA) by verifying thatthe server has at least one connection path to each storage systemSP, and that PowerPath or some other failover software, such asDMP or PV Links, is running. The utility will not detect any othernative failover software, such as Sun StorEdge Traffic Manager orLinux native multipath (MPIO).

This feature is currently supported only on CX3–series and CX-seriesstorage systems.

You can run the Navisphere Server Utility from the CD or you caninstall it on the servers that are connected to the storage system. Westrongly recommend that you install the utility on each server that isconnected to the storage system.

Note: The server utility runs on servers attached to CX3-series, CX-series, andAX-series storage systems. CX3 model 10 systems must be running FLARE OE03.24.010.5.xxx or later. CX3 model 20 systems, CX3 model 40 systems, andCX3 model 80 systems must be running FLARE OE 03.22.xxx.5.yyy or later.CX200, CX300-series, CX400, CX500-series, CX600, and CX700 systems must berunning FLARE 02.16.xxx.5.yyy or later.

About the Admsnap Utility

The Admsnap Utility is an executable program that you can runinteractively or by a script to manage SnapView® clones and snapshots.The Admsnap Utility resides on the servers connected to the storagesystem with the SnapView driver installed.

Use admsnap commands to:

Scan for new storage devices

Make storage devices inaccessible to the server operating system

Flush cache data to disk


List current snapshot devices

Map and unmap to a SnapView session

Start and stop a SnapView session

Note: The Admsnap Utility runs on servers attached to CX3-series andCX-series. If you upgraded to Navisphere Manager and want to managesnapshots, you must use the SnapView software and the Admsnap Utility. Formore information on SnapView and admsnap, refer to the Navisphere Managerhelp and the EMC SnapView Command Line Interfaces Reference.

About the Navisphere CLI

The CLI complements or can be used as an alternative to Manager. Itprovides a command line interface for storage-system management,including storage provisioning, status and configuration informationretrieval, and control. You can use the CLI to automate managementfunctions through shell scripts and batch files. CLI commands formany functions are server-based and are provided with the host agent.The remaining CLI commands are web-based and are provided withsoftware that runs in the storage-system SPs. Navisphere CLI includesthe Secure (on supported operating systems), Classic, and Java CLIfunctionalities. For more information, refer to the EMC NavisphereCommand Line Interface (CLI) Reference Guide.

Note: The Navisphere CLI can run on servers or remote management stationsthat are attached to CX3-series and CX-series.


Finding current information

The most up-to-date information about the CLARiiON® serversoftware is posted on the EMC Powerlink® website. We recommendthat you download the latest information before you install any serversoftware.

To access EMC Powerlink, use the following link:

http://Powerlink.EMC.com

After you log in, select Support > Documentation/White Paper Libraryand find the following:

Navisphere Host Agent/CLI and Utilities Release Notes

EMC SnapView Command Line Interfaces Reference (P/N 069001181)

The latest version of this guide that is applicable to your softwarerevision. For information on FC4700 storage systems, refer torevision A04 of this guide.

EMC Installation Roadmap for CX3–Series, CX-Series, AX-Series,and FC-Series Storage Systems (P/N 069001166), which providesa checklist of the tasks that you must complete to install yourstorage system in a storage area network (SAN) or direct attachconfiguration.

For the most current management and security content forCX3–series, and CX-series storage systems, refer to the EMCNavisphere Manager help, which is available in the NavisphereManager UI and in the Documentation/White Paper Librarysection of the Powerlink website. For FC-series and C-seriesmanagement and security content, refer to the most recent versionsof EMC Navisphere Manager Administrator’s Guide (P/N 069001125)and EMC Navisphere Security Domains, Multi-Domains, and UserAccounts (P/N 069001124).

For CX3–series, and CX-series storage systems, refer to the latestversion of the EMC Navisphere Command Line Interface (CLI) Reference(P/N 300–003–628). For FC-series and C-series storage systems,refer to the most recent version of the EMC Navsphere Command LineInterface (CLI) Reference (P/N 069001038).



Installing and removing the Navisphere Storage System InitializationUtility

EMC recommends that you install the utility on the server; however,you can run the Navisphere Storage System Initialization Utility fromthe server support CD.

Installation prerequisites

To use the Storage System Initialization Utility on an HP-UX hostto initialize a storage system, the host must meet the followingrequirements:

Run a supported version of the operating system.

Be connected to the same subnet as the 10/100 management portsof the storage system that you want to initialize. This host may alsobe a server with Fibre Channel connections to the storage system.

If you have a previous revision installed, you must uninstall it beforeinstalling an updated version.

Installing the Navisphere Storage System Initialization Utility on an HP-UX host

EMC recommends that you install the most recent version of theNavisphere Storage System Initialization Utility software that isappropriate for your configuration. You can download the most recentversion from the software download page on the Powerlink website(CX3–series and CX-series). You can also install the software from theserver support CD (any storage system); however, the CD may notcontain the most recent version for your configuration.

1. On the HP-UX server, log in as superuser (root).

2. If any previous revision of the initialization utility is installed onthe server, remove it before continuing.

Note: To verify if the initialization utility is installed, enter the/usr/sbin/swlist command to get a list of the currently installed software.

3. To download the software for CX3–series or CX-series storagesystems, do the following:


a. On the Powerlink website, select Support > Downloadsand Patches and navigate to the Navisphere Storage SystemInitialization Utility download section, which may be in eitherthe CLARiiON Navisphere Storage System InitializationUtility section or the CLARiiON Navisphere Host BasedAgent/CLI HP/UX section.

b. Select the appropriate Navisphere Storage System InitializationUtility version and download the zip file to a Windows server.

c. Transfer the INITTOOL.dep file to the HP-UX server.

d. Install the INITTOOL.dep file on the HP-UX server.

4. To install the software from the server support CD (any storagesystem), do the following:

a. Insert the server support CD in the server’s drive.

b. At the command prompt (#) in the hpterm or xterm window,create and mount the CD or DVD directory:

c. Execute the following command:samThe system administration utility (SAM) top-level menu opens.

d. Click Return and select the Peripheral Devices option.

The Peripheral Devices menu opens.

e. Select the Cards and Devices option. The Cards and Devicesdialog box opens with several menu choices at the top of thedialog box.

f. Select the line in the list that contains descriptions of CD-ROMdrives or DVD-ROM drives. (Note this phrase may be precededby a manufacturer’s name.)

g. Click Enter. Note the device name for the CD or DVD; forexample, /dev/dsk/c2t2d0.

h. Exit the SAM utility.At the command prompt (#) in the hpterm or xterm window,use the following command from the root directory tomake sure the /cdrom or /dvdrom directory exists:lsIf the /cdrom or /dvdrom directory exists, it will appear in theresulting list. If the /cdrom or /dvdrom directory doesnot exist, create it with the following command:mkdir /cdrom



ormkdir /dvdrom

i. Execute the following command to mount the CD or DVD:mount devicename /cdromormount devicename /dvdromwhere devicename is the name you previously noted in step gabove.

j. At the command prompt (#) in the hpterm orxterm window, execute the following commandto change to the /cdrom or /dvdrom directory:cd /cdromorcd /dvdrom

k. Execute the following command to specify theCD or DVD as the source depot:/usr/sbin/swinstall -s /cdrom/hpux/INITTOOL.dep -xmount_all_filesystems=false INITTOOLor/usr/sbin/swinstall -s /dvdrom/hpux/INITTOOL.dep -xmount_all_filesystems=false INITTOOL

l. At the command prompt (#), execute the appropriatecommand for the drive you want to unmount.To unmount a CD, enter the following commands:cdumount /cdromTo unmount a DVD, enter the following commands:cdumount /dvdrom

m. Remove the CD from the server’s CD or DVD drive.

Removing the Storage System Initialization Utility on a HP-UX server

1. At the HP-UX server, log in as superuser (root).

2. Execute the following command to remove the Storage SystemInitialization Utility:

/usr/sbin/swremove -x mount_all_filesystems=false INITTOOL


The removal process begins. The removal process is completewhen there is no error and the following message is displayed:END swremove SESSION


Running the Navisphere Storage System Initialization Utility

You can run the storage system initialization utility from the host onwhich it is installed or from the server support CD. Before continuingmake sure that the storage system is powered up completely.

Starting and using the storage system initialization utility on a an HP-UX host

Note: Before using the Navisphere Storage System InitializationUtility, make sure that you know the static IP addresses forthe storage system SPs (for example, http://123.45.6.7 and123.45.6.8), the subnet mask, and the default gateway address.

For storage system initialization, connect the server from which you arerunning the utility and the storage system to the same network subnet. Onceyou have assigned an IP address to the storage system, the server and storagesystem can be on different subnets.

1. To start the utility from the host, enter:

/opt/Navisphere/bin /naviinittool

2. To start the utility from the CD:

a. In the server’s drive, insert the server support CD, whichshipped with the storage system or the upgrade kit (forAX-series systems upgrading to Navisphere Manager).

b. At the command prompt (#) in an hpterm window,enter the following command to create a CD directory:mkdir /cdrom

c. Identify the device file by executing the following command:ioscan -funC diskThis command lists all recognized drives and their associateddevice files. The filename will be similar to /dev/dsk/c1t2d0.

d. Mount the CD drive:mount /dev/dsk/device_filename /cdromwhere device_filename is the device filename from step c. Forexample, mount /dev/dsk/c1t2d0 /cdrom.

e. Run the initialization utility:/cdrom/hpux/naviinittool


http://123.45.6.7

3. Read the license agreement and enter y to accept it.

The utility automatically scans the subnet for supported storagesystems. When this storage-system discovery operation is complete,the utility lists, by hardware serial number, all uninitialized andinitialized storage systems it discovered. The hardware serialnumber (HW S/N XXX 000NNNNNNNN) is on a label on the rearof the chassis.

If the storage system you are installing was not discovered, verifythe cable connections between the storage system and the hostrunning the utility.

4. Enter the item number of the storage system you want to initializeand press Enter.

5. Using the information completed worksheet in the “Storage-SystemManagement Ports Worksheet” from the storage-systemconfiguration planning guide or planning worksheets document,follow the instructions on the screen to change the storage system’sname, if desired, and to set the following network parameters forthe storage-system management ports:

Using the information from the completed worksheet in the“Storage-System Management Ports” section of the Planning YourFibre Channel Storage-System Configuration in section A of thecompleted Administration Worksheet, follow the instructions on thescreen to change the storage system’s name, if desired, and to setthe following network parameters for the storage-system 10/100management ports:

Parameter Description

Storage Processor A - IPADDRESS

IP address for SP A management port. For a CX3–seriessystem, this IP address cannot be 128.221.1.250,128.221.1.251,192.168.1.1, or 192.168.1.2 becausethese addresses are reserved. For an AX-seriesstorage system, this IP address cannot be 192.168.1.1or 192.168.1.2 because these addresses are reserved.


Parameter Description

Storage Processor B - IPADDRESS

IP address for SP B management port. For a CX3–seriessystem, this IP address cannot be 128.221.1.250,128.221.1.251,192.168.1.1, or 192.168.1.2 becausethese addresses are reserved. For an AX-seriesstorage system, this IP address cannot be 192.168.1.1or 192.168.1.2 because these addresses are reserved.

Subnet Mask Subnet mask associated with the LAN to which thestorage-system management port is connected.

Default Gateway Default gateway address for the LAN to which thestorage-system management port is connected.

6. Enter the name you want for the storage system; it cannot exceed32 characters.

7. Using the information completed worksheet in the“Storage-System Management Ports Worksheet” from thestorage-system configuration planning guide or planningworksheets document, follow the instructions on the screen to setthe following management user account settings for the storagesystem:

Using the information from the completed worksheet in the“Storage-System Management Ports” section of the Planning YourFibre Channel Storage-System Configuration in section A of thecompleted Administration Worksheet, follow the instructions on thescreen to set the following management user account settings forthe storage system:

Account Setting Description

User name Username for the management port. A valid username muststart with a letter, can contain only letters and numbers,cannot exceed 32 characters, and is case–sensitive. Forexample, blindmice3 is a valid username and is different fromBLINDMICE3.


Account Setting Description

Password Password for the management port. A valid password cancontain only letters and numbers, cannot exceed 32 characters,and is case–sensitive. For example, mousetrap2 is a validpassword and is a different password from MOUSETRAP2.

Confirm Password Previously entered password for password verification.

8. When you have set the parameters to the values you want, applythe values by typing a.

9. Exit the utility by typing e.

For a CX3-series storage systemIf you entered an SP IP address for the first time or changed anSP IP address, the utility reboots the storage system, and the SPfault light on the back of each SP starts blinking. The reboot takesseveral minutes to complete. When it is completed, the SP faultlight (LEDs) on each SP stops blinking and remains off.

For a AX-series storage systemIf you entered an SP IP address for the first time or changed anSP IP address, the utility reboots the storage system and the SPBoot/Fault light on the back of each SP starts blinking. The reboottakes several minutes to complete. When it is completed, the SPBoot/Fault light on each SP stops blinking and remains off.


Determining whether to install the host agent or server utility

Depending on your application needs, you can install the host agent,server utility, or both on an attached server.

If you want to install both applications, you must install revision6.22.20 or later of the server utility either before or after you install thehost agent. The registration feature of the server utility will be disabledand the host agent will be used to register the server’s NICs or HBAs tothe storage system.

Note: Prior to revision 6.22.20 of the server utility, you could not install the hostagent and server utility on the same server. However, you could install themon different servers that are connected to the same storage system.

If you do not want to install both applications, but want to use someof the features available in the server utility, you can run the serverutility from the server support CD.

Table 1 describes the differences between the host agent and the serverutility on a server attached to a storage system.

Important: Depending on the revision of the server utility, some of the featureslisted in Table 1 may not be available.

Table 1 Differences between the host agent and the server utility

Function Host agent Server utility

Pushes LUN mappingand OS information to thestorage system.

Yes – LUN mapping information isdisplayed in the Manager UI next tothe LUN icon or with the CLI usingthe -lunmapinfo command.

CX3-series and CX-series storage systemsNo – LUN mapping information is not sent to the storage system. Onlythe host’s name, ID, and IP address are sent to the storage system.Note: The text Manually Registered appears next to the hostnameicon in the Manager UI indicating that the host agent was not used toregister this server.

Runs automatically tosend information to thestorage system.

Yes – No user interaction isrequired.

CX3-series and CX-series storage systems


Function Host agent Server utility

Provides high-availability(HA) validation

No – You can run the server utility’sHA validation feature from the CDwithout having to install the serverutility.

CX3-series and CX-series storage systemsYes – The HA validation feature verifies that failover soft-ware is installed on the server and that working paths exist betweenthe server and each SP in the storage system.

Requires networkconnectivity to the storagesystem.

Yes – Network connectivity allowsLUN mapping information to beavailable to the storage system.

CX3-series and CX-series storage systemsNo – LUN mapping information is not sent to the storagesystem. Note that if you are using the server utility to upload a highavailability report to the storage system, you must have networkconnectivity.

Requires installation. Yes – You must install the hostagent on the server.

CX3-series and CX-series storage systemsNo – You can run the server utility from the CD. However,we recommend that you install it on the server. You must install theutility to use the registration service feature (described above).

Note: If you install both the host agent and revision 6.22.20 or later of the server utility (the order of which does not matter), the serverutility’s registration service feature will not be installed. Prior to revision 6.22.20 of the server utility, you could not install the host agentand server utility on the same server.


Requirements for the host agent, server utility, and CLI

To run the host agent, CLI, or server utility, your server must meetthe following requirements:

Run a supported version of the HP-UX operating system.

Have the EMC CLARiiON supported HBA hardware and driverinstalled.

Be connected to each SP in each storage system either directly orthrough a switch or hub. Each SP must have an IP connection.

For the host agent and CLI only- Be on a TCP/IP network connectedto each SP in the storage system. The TCP/IP network connectionallows the server to send LUN mapping information to the storagesystem and it allows Navisphere Manager or CLI to communicatewith the storage system over the network.

Have a configured TCP/IP network connection to any remote hoststhat you will use to manage the server’s storage systems, including:

any host whose browser you will use to access Manager 6.X.

any Windows Server 2003, or Windows 2000 host runningStorage Management Server software.

any AIX, HP-UX, IRIX, Linux, NetWare, Solaris, WindowsServer 2003, or Windows 2000 host running the CLI.

If you want to use the CLI on the server to manage storage systems ona remote server, the server must be on a TCP/IP network connectedto both the remote server and each SP in the remote server’s storagesystem. The remote server can be running AIX, HP-UX, Linux, Solaris,or the Windows operating system.

Note: For information about the specific revisions of the server operatingsystem and the storage-system FLARE and Access Logix software that arerequired for your revision of the host agent, see the release notes for the hostagent on the EMC Powerlink website. To access this website, see Finding currentinformation, page 6 .


Installing or removing the Navisphere Host Agent and CLI

You can install both the host agent and CLI package or just theCLI package. If you will install both, install the host agent first.To modify an existing host agent configuration refer to the next section.

Note: If you want to install the host agent and use some of the features in theserver utility, see Determining whether to install the host agent or server utility,page 15.

Installing the host agent and/or CLI on an HP-UX server

EMC recommends that you install the most recent version of theNavisphere Host Agent/ CLI software that is appropriate for yourconfiguration. You can download the most recent version from eitherthe software download page on the Powerlink website (CX3–series andCX-series). You can also install the software from the server supportCD (any storage system); however, the CD may not contain the mostrecent version for your configuration.


2. If any previous revision of the host agent or CLI is installed on theserver, remove it before continuing.

Note: To verify if the host agent or CLI is installed, enter the /usr/sbin/swlistcommand to get a list of the currently installed software.


a. On the Powerlink website, select Support > Downloads andPatches and navigate to the CLARiiON Navisphere HostAgent/ CLI download section for HP-UX .

b. Select the appropriate Navisphere Host Agent/CLI version anddownload the zip file to a Windows server.

c. Transfer the NAVIAGNT.dep file to the HP-UX server.

d. Install the NAVIAGNT.dep file on the HP-UX server.











g. Click Enter. Note the device name for the CD or DVD, forexample, /dev/dsk/c2t2d0.

h. Exit the SAM utility.At the command prompt (#) in the hpterm or xterm window,use the following command from the root directory tomake sure the /cdrom or /dvdrom directory exists:lsIf the /cdrom or /dvdrom directory exists, it will appear in theresulting list. If the /cdrom or /dvdrom directory doesnot exist, create it with the following command:mkdir /cdromormkdir /dvdrom


j. At the command prompt (#) in the hpterm orxterm window, execute the following commandto change to the /cdrom or /dvdrom directory:


cd /cdromorcd /dvdrom

k. Execute the following command to specify theCD or DVD as the source depot:/usr/sbin/swinstall -s /cdrom/hpux/NAVIAGNT.dep -xmount_all_filesystems=false NAVICLI |NAVIAGENT | NAVICLI NAVIAGENTor/usr/sbin/swinstall -s /dvdrom/hpux/NAVIAGNT.dep -xmount_all_filesystems=false NAVICLI | NAVIAGENT |NAVICLI NAVIAGENT


m. Remove the CD from the server’s CD or DVD drive.

5. If you have a multihomed host (multiple NIC cards installed onthe host), create an agentID.txt file to ensure that the agent findsthe correct NIC card.

Note: A multihomed host machine has multiple IP addresses connected tonetworks; it is physically connected to multiple data links that can be on thesame or different networks. When you install Navisphere Host Agent on amultihomed host, the host agent, by default, binds to the first NIC in thehost. If your host is multihomed, for the host agent to successfully registerwith the desired CLARiiON storage system, you need to configure the hostagent to bind to a specific NIC. You do this by setting up an agentID.txt file.

a. Using a text editor that does not add special formatting, createor edit a file named agentID.txt (case sensitive) in either / (root)or in a directory of your choice.

b. Add the following two separate lines to the agentID.txt file,with no special formatting:


First line: Fullyqualified hostname of the host

Second line: IP address of the HBA/NIC port that you

want Navisphere agent to use

For example, if your host is named host28 on the domainmydomain.com and your host contains two HBAs/NICs,HBA1/NIC1 with IP address 192.111.222.2 and HBA2/NIC2with IP address 192.111.222.3, and you want the host agent touse NIC 2, you would configure agentID.txt as follows:

host28.mydomain.com192.111.222.3

Note: The agentID.txt file should contain only these two lines, withoutany formatting. The first line should contain the hostname and thesecond line should contain the IP address of the HBA/NIC port asdescribed above. Both lines should end with a carriage return. As aresult, the cursor will be on a third line but this line should not containany text.

c. Save the agentID.txt file.

d. If you created the agentID.txt file in a directory other thanroot, for host agent to restart after a system reboot using thecorrect path to the agentID.txt file, set the environment variableEV_AGENTID_DIRECTORY to point to the directory whereyou created agentID.txt.

e. If a HostIdFile.txt file is present in the directory shown for youroperating system, delete or rename it. The HostIdFile.txt file islocated in /etc/log/HostIdFile.txt.

f. Stop and then restart the host agent.

g. Once the host agent has restarted, verify that host agent is usingthe IP address that is entered in the agentID.txt file. To do this,view the new HostIdFile.txt file. You should see the IP addressthat is entered in the agentID.txt file.

Modifying user login scripts

Use a text editor to modify login scripts as described below:


If you are running Common Desktop Environment, remove thepound sign (#) from the beginning of the last line (uncomment thelast line) in $HOME/.dtprofile. The line should read:

DTSOURCEPROFILE=true

Make the following additions to the specified paths in$HOME/.profile or $HOME/.cshrc, and export each path:

add /opt/Navisphere/bin to PATH

add /opt/Navisphere/man to MANPATH

add /usr/lib:/usr/lib/X11R5:/opt/Navisphere/lib toSHLIB_PATH

Note: You must export each path after you have modified it.

What next?

For legacy storage systems — Go to the next section, go to Configuringthe Navisphere Host Agent, page 23.

For CX3-series or CX-series storage systems — If you are setting upa new server, go to Running the Navisphere Host Agent, page 40. If youare just upgrading the host agent or CLI on an existing system, you arefinished with the upgrade.

Removing the host agent or CLI


2. At the command prompt (#) in an hpterm window, execute theone of the following commands:

To remove the host agent enter:/usr/sbin/swremove -x mount_all_filesys-tems=false NAVIAGENT

To remove the CLI enter:/usr/sbin/swremove -x mount_all_filesys-tems=false NAVICLI

The removal process begins. The removal process is completewhen there is no error and the following message is displayed:END swremove SESSION


Configuring the Navisphere Host Agent

Configuring CX3–series or CX-series storage systems – Before youcan use the Navisphere CLI navicli register command to configure aCX3–series or CX-series storage system connected to a host agent, youmust make sure the host agent configuration file includes a privilegeduser, as described in Adding privileged users, page 26.

Note: The pathname of the host agent configuration file is /etc/Navi-sphere/agent.config .

Configuring legacy storage systems – Before you can use NavisphereManager or Navisphere CLI to configure legacy storage systemsconnected to a host agent, you must make sure the host agentconfiguration includes the information listed below.

Note: A legacy system is an FC-series or C-series storage system that is notrunning storage management server software.

Table 2 Information to add to the host agent configuration file for legacy storagesystems

Required forInformation to add to thehost agent configuration file(legacy storage systems only)

Manager CLI

Communication path for the host agent to thestorage system

Yes Yes

IP addresses of the portal system Yes No

Privileged user No Yes

What next?

Go to the appropriate selection below for the information you need toadd to the host agent configuration file.

Specifying a communication channel for legacy storage systems, page 24

Adding IP addresses for a portal system, page 24


Adding privileged users, page 26

Specifying a communication channel for legacy storage systems

Note: Do not add a communication channel for an SP in a CX3–series orCX-series storage system. Doing so will cause Navisphere Manager to displayan unnecessary unmanaged storage-system icon for the SP.

Each SP in a storage system is connected to the server by a FibreChannel arbitrated loop (FC-AL) or fabric connection to a FibreChannel adapter, sometimes called a host bus adapter (HBA). The pathfrom the adapter through the SP to one LUN in the storage system is acommunication channel to the storage system for the host agent. Thedevice entries in the agent configuration file define the communicationchannels. The fibre controllers use SCSI mapping.

To use automatic device scanning, which updates device entries eachtime the host agent starts, make sure the host agent configuration filehas a device entry with the following format:

device auto auto

This entry eliminates the need to enter specific devices in theconfiguration file and it is an entry in the default host agentconfiguration file.

What next?

To add IP addresses for a portal system — Continue to the next section,Adding IP addresses for a portal system, page 24.

To add a privileged user — Go to Adding privileged users, page 26.

Adding IP addresses for a portal system

Note: You must also use a portal system to centrally monitor storage systemevents. For detailed instructions, refer to the Navisphere Manager online help.

If you will use Navisphere Manager 6.X to configure the host agent andmanage legacy storage systems, you will use a portal system. A portalsystem is a CX3-series or CX-series storage system (storage-system


portal), or a Windows Server 2003, or Windows 2000 server (serverportal) running Storage Management Server software. WhenNavisphere 6.X requests information from a host agent, the request getsrouted through the storage management server on the storage-systemportal or the server portal to the host agent. For this reason, whenusing servers to monitor or perform management operations, you mustenter the IP address for both SPs of the storage-system portal and theIP address for the server portal to the privileged user’s list in the hostagent configuration file.

If you know the IP addresses for the portal system, you can add themto the host agent configuration file now.

Note: When using Navisphere Manager 6.X, failure to enter the correct IPaddresses, results in a Caller not priveleged error when attempting anoperation to those host agents.

To enter an IP address into the host agent configuration file, you caneither edit the host agent configuration file manually or use NavisphereCLI.

Using a text editor to edit the host agent configuration file

To enter an IP address into the host agent configuration file, do oneof the following:

If you are using a storage-system portal, add the IP address for eachSP in the portal to the /etc/Navisphere/agent.config file using thefollowing format:

user system@IPaddress

where IPaddress is the IP address for an SP in the portal storagesystem

For example, once you have configured a CX3-series or CX-seriesstorage system as the storage-system portal, you must add the IPaddress for each SP in the portal to the host agent configurationfile as follows:

user [email protected] [email protected]

If you are using a server portal, add the IP address for the server tothe /etc/Navisphere/agent.config file using the following format:


mailto:[email protected]


user system@IPaddress

where IPaddress is the IP address for the server portal.

For example, once you have configured a Windows Server 2003,or Windows 2000 server as the server portal, you must add the IPaddress for the server to the host agent configuration file as follows:

user [email protected]. 227

Using CLI to edit the host agent configuration file

Add the IP address for each SP in the storage-system portal, or the IPaddress for the server portal to the host agent configuration file usingthe following CLI command:

navicli remoteconfig -setconfig -adduser system@IPaddress

where IPaddress is the IP address for each SP in the storage-systemportal, or the IP address for the server portal.

For example, for a storage-system portal, you might enter the followingIP addresses:

navicli remoteconfig -setconfig -adduser [email protected] remoteconfig -setconfig -adduser [email protected]

For a server portal, you might enter the following IP address:

navicli remoteconfig -setconfig -adduser [email protected]

What next?

To add a privileged user, continue to the section, Adding privileged users,page 26. If you are done editing the host agent configuration file, go toSaving the host agent configuration file, page 27.

Adding privileged users

If you will use Navisphere CLI to configure any storage system, thehost agent configuration file must include an entry that defines theperson who will issue the CLI commands as a privileged user.

To define a privileged user, add a local or remote privileged user byadding the appropriate entry below.

For a local user:

user name






For a remote user:

user name@hostname

where name is the person’s account name and hostname is the name ofthe remote server the person will be using.

The default host agent configuration file includes a user root entry.

What next?

Continue to the next section, to save the host agent configuration file.

Saving the host agent configuration file

1. Save the host agent configuration file.

2. If you are done adding information to the hostagent configuration file, stop and restart the hostagent by entering the following commands:#/sbin/init.d/agent stop#/sbin/init.d/agent start

What next?

For CX3–series and CX-series storage systems — You are done editingthe host agent configuration file.

For legacy storage systems — You can now use Manager, CLI, or atext editor to edit the information for each managed storage system,such as the following:

Agent description and contact

Polling frequency

SP event log entries to transfer

Using Navisphere Manager — Use the remote agent configurationfeature as described in the Navisphere Manager help.

Using Navisphere CLI — Use the navicli remoteconfig command asdescribed in the Navisphere Command Line Interface (CLI) Reference.


Using a text editor (textedit, vi, or emacs) — Refer to Manually editingthe host agent configuration file (legacy storage systems only), page 28.

Manually editing the host agent configuration file (legacy storage systems only)

Before the host agent can communicate with a legacy storage system,you must edit the agent’s configuration file to include specificinformation. Normally, you use the remote agent configuration featureof Navisphere Manager to modify this file. However, before someonecan use this feature to configure the host agent, you must manually adda user entry for that person to the host agent’s configuration file.

Note: You need to edit the host agent configuration file only if you have legacystorage systems connected to the server.

You also need to edit the host agent configuration file if the initiatortype is set to autotrespass, refer to . If you leave the default initiatortype, then every time the host agent restarts, the initiator type will beset to HP no-autotrespass.

A previous section explained how to edit the file to add one privilegeduser who could configure storage systems, but this section explainsall the configuration file entries.

The pathname to the host agent configuration file is:

/opt/Navisphere/bin/agent.configor

/etc/Navisphere/agent.config

The configuration file contains the following information for eachstorage system to be managed:

Agent description and contact

Communication channel(s) to the SP

Users who can configure a managed storage system

Polling frequency

SP event log entries to transfer

The following sections show a sample configuration file and describehow to specify this information.


Sample host agent configuration file (agent.config)# Navisphere agent.config# ---------------------# This file is used by Navisphere Agent to configure# site specific values.## All entries in this file have this form:## object value-list## Where "object" tells what sort of information is to# be configured, and "value-list" is a# whitespace-separated list of values to be configured.# Samples, which should be edited, appear below for all# permissible types of objects.## White space (tabs, space, line-feeds,# carriage-returns) and blank lines are ignored;# To continue a line onto the next line, use "\" as the# last character of that line. The "\" is dropped when# the next line is concatenated to the continued line.############################## Description specification# -------------------------## The "clarDescr" object takes arbitrary text values# intended to describe the agent and its location.#clarDescr Navisphere Agent## The "clarContact" object takes arbitrary text values# intended to describe who is responsible for the# configured agent, and how to reach them.#clarContact John Smith, 800-555-1212## Device specification.# ----------------------## The format of "device" objects for CLARiiON devices# is:# devicedevice-specname "description"## where the device-specification is the device name to# open to access the CLARiiON device. It can be a# SCSI-2 file name. If this is "auto", all attached# arrays with bound LUNs will be automatically# configured. (Currently, dummy arguments are required# for name and description, when using# auto-configuration.) This can NOT be defaulted.## The name is the per CLARiiON name that can be used to# identify each CLARiiON to the manager application.# The name is REQUIRED and cannot contain spaces (even# if surrounded by quotes). This can NOT be defaulted.## The description is a quoted string that contains a# brief description of the CLARiiON chassis being# managed. It defaults to "" if not specified, and to


# the device name for auto-configuration.#

# SAMPLES:# device c0t0d0 NAVISPHERE-1 "NAVISPHERE-1"

## automatically detect manageable devicesdevice auto auto## The Navisphere Agent can now be configured to enable or# disable auto-trespass when it starts up. To enable# auto-trespass on Agent startup,enter the following line# OptionsSupported AutoTrespass# If this line is not present in the configuration file,# the default will be to disable auto-trespass.## User Specification.# ------------------## The format of "user" objects is"# user localUserId# OR# user userId@hostname## These build a list of users who are allowed to perform# WRITE operations to the CLARiiON devices managed by# this agent. By default, as specified below, only root# on this machine has WRITE access. Others can be# granted access by including their login name and host# which they can access from. A null list prevents# anyone, including admin, from having write access. In# order to get write access, this file would have to be# modified and the Agent stopped and restarted to# re-read the configuration file, or an appropriate# remote configuration file would have to be sent to the# agent from an already-priviledged user.user root # only on this machine#user sblue@picasso # individual user "sblue" on# host "picasso"#user lgreen@hannibal # individual user "lgreen" on# host "hannibal"## Poll specification# ------------------# The "poll" object takes a numerical count of seconds.## This specifies how often the agent solicits# information from the array, rather than using cached# information. The minimum is "10".#poll 60## Eventlog specification# ----------------------# The eventlog object takes a numerical count of log# entries.## This defines the maximum number of SP log events# received by the agent on startup, and received by# clients per poll. A value of 0 causes the device’s# entire log to be read at startup. A minimum of 100


# events will be read on serial, and 2048 on fibre,# overriding any lower value configured below.#eventlog 100#

##### end of configuration file###

Specifying the host agent description and contact

The host agent description (clarDescr) and contact (clarContact) entriesare optional informational text strings that Manager does not use. Youcan use the clarDescr entry to include information about the agent,such as its revision, and the clarContact entry to include informationabout the person to contact concerning any agent questions or problemsthat might occur.

To specify the host agent description, either modify the clarDescrentry or add a new clarDescr entry.

A clarDescr entry has this format:

clarDescr [description]

where description is a description of the host agent, such as thename of the agent and its revision; for example, Disk-Array Agent,revision x, where x is the revision of the agent you are running.

To specify the contact description, either modify the clarContactentry or add a new clarContact entry.

A clarContact entry has this format:

clarContact [contact_info]

where contact_info is any optional information you want to includeabout whom to contact should any questions or problems with theagent arise. You could include the name of a person to contact andthe person’s electronic mail address and phone number.

Enabling auto-trespass

Auto-trespassing is disabled by default, and it must remain disabledfor PowerPath or HP-UX without PV Links. If you are using HP-UXwith PV Links, you must enable it.

To enable auto-trespassing, add the following line to the agentconfiguration file:


OptionsSupported Autotrespass

To disable auto-trespassing either remove the above line from the agentconfiguration file or make sure it is commented out (has a # before it).

Note: The sample agent configuration file contains OptionsSupportedAutotrespass line as a comment, which means that the auto-trespassing isdisabled. To enable auto-trespassing, you can either add the line or justuncomment it (delete the # from the beginning of the line).

Specifying communication channels to the SPs

Each SP in a storage system is connected to the server by a FibreChannel arbitrated loop (FC-AL) or a fabric connection to a FibreChannel adapter, sometimes called a host bus adapter (HBA), or by aSCSI bus connected to a SCSI-2 adapter, also sometimes referred toas an HBA. The path from the adapter through the storage processorto one LUN in the storage system is a communication channel tothe storage system for the host agent. The device entries in the hostagent’s configuration file define the communication channels. The fibrecontrollers use SCSI mapping.

Storage systems with two SPs – If the storage system has two SPsthat are both connected to host bus adapters in the same server, asthey are in a dual-adapter/dual-SP configuration, the server’s hostagent configuration file must have a device entry (device) for thecommunication channel through each SP. If the SPs are connected tohost bus adapters in different servers, the host agent configuration filein each server must have a device entry for the communication channelthrough the SP connected to that server.

Adding a storage system to the server– If you add a storage system tothe server in the future, you must make sure that the host agentconfiguration file has a device entry for the communication channelthrough each storage processor in the new storage system. Youneed to know the FC-AL address IDs or the SCSI target IDs of eachstorage-system SP and host HBA to which the SP(s) are connected.The FC-AL address ID or the SCSI target ID of an SP is set by switcheson the back of the storage system, as described in the storage-systeminstallation and maintenance manual. In addition, you need to knowthe number for the LUN owned by each SP in the storage system.

To specify a communication channel


Note: Do not add a communication channel for an SP in a CX3-seriesor CX-series storage system. Doing so will cause Manager to display anunnecessary unmanaged storage-system icon for the SP.

Either modify the device entry or add a new device entry in the/etc/Navisphere/agent.config file.

The device entry must have one of the formats below:

For automatic device scanning on host agent startup:

device auto auto “auto”

With the device entry of device auto auto, the host agent willautomatically select the communication channel to one LUN perSP in each storage system every time the host agent starts. Thismethod is the easiest way to enter device information in the agentconfiguration file. Use it instead of explicitly entering devices withthe following format.

For access to a specific device:

device channel name [description]

where:

channel is a required field for the communication channel(device path, device name, or disk name) thatthe agent uses to communicate with the storagesystem. The format is cDtSdL where:For SCSI disks:D is the number of the SCSI bus on the SCSI-2adapter to which the storage system is connected.S is the SCSI ID of the storage system’s SP that is connected toSCSI bus cD. If the adapter identified by cD provides anarrow SCSI bus, this SCSI ID can range from 0through 7; and if the adapter provides a wide SCSIbus, this SCSI ID can range from 0 through 15.L is the ID of a LUN owned by the SP identified by tS.For Fibre Channel disks:D, S, and L depend on the number of LUNs in the storagesystem and the setting of the FC-AL ID rotary switches on theSPs. You must use the ioscan utility and the CLI commandsystemtype to discover the device name, as explainedin the following section


name is a required label for identifying the communicationchannel. We recommend that this name include a name for thestorage system, the SP, and the LUN. For example, if the nameof the storage system is cpc220, the SP is SP A, and the LUN is 0,you could use the name cpc220_spa_lun0. Navisphere Managerdoes not use this information, but the Navisphere CLI does.

[description] is an optional description of the connection tothe chassis. Be sure to enclose the description in quotationmarks. For example, Path from host img01 to cps220 SP A.The Navisphere Manager does not use this information, but theNavisphere CLI does. The information you specify here may becritically useful to anyone who maintains the storage systemsconnected to this server.

Discovering the device names of communication channel LUNs

To find out the device names of the LUNs that HP-UX sees, use theioscan program and complete the following steps.

1. Enter the following commands to create special device files:ioscan -fnC diskinsf -e

2. Enter the ioscan -fnC disk > orig.scan command. This tells HP-UXto scan for disks and send the disk device names to a file, hereorig.scan.

3. Print the orig.scan file to see device names similar to the following:Class IH/W Path Driver S/W State H/W Type Description==================================================================disk0 0/0/0.6.0 sdisk CLAIMED DEVICE SEAGATE ST34572WCdisk11 2/2/0.8.0.255.0.2.0 sdiskCLAIMED DEVICE DGC

/dev/dsk/c6t2d0 /dev/rdsk/c6t2d0disk4 4/2/0.0.0 sdisk CLAIMED DEVICE TOSHIBA CD-ROM...

/dev/dsk/c5t0d0 /dev/rdsk/c5t0d0disk14 6/0/0.8.0.255.0.1.0 sdiskCLAIMED DEVICE DGC

/dev/dsk/c7t1d0 /dev/rdsk/c7t1d0__________________________________________________________________

4. To determine which device should be specified as a communicationchannel in the agent configuration file, look for device names ofthe DGC disks.

You can specify any disk with DGC in its description as acommunication channel to an SP. Note from the listing that disk 0and disk 4 do not have DGC in the description and therefore neithercan be a communication channel to the storage system.


Note: If the storage system has more than one SP connected to the sameserver, include one (and only one) device entry for each SP. For each SP ineach storage system, use the device name for a device shown as d0. Wesuggest d0 because there will always be a device 0 in the storage system.

In the sample, the two DGC devices found are c6t2d0 and c7t1d0.Either could be connected to SP A or SP B. You can identify themusing the FC-AL address IDs. These IDs are manually set withrotary switches (hard coded) on each SP. The switch settings appearin the two fields to the left of the LUN field in the hardware (H/W)path, as shown in the following listing for the first DGC device:disk 11 2/2/0.8.0.255.0.2.0 sdisk CLAIMED DEVICE DGC/dev/dsk/c6t2d0 /dev/rdsk/c6t2d0

Assume that SP A is connected to c6t2d0 and SP B is connectedto c7t1d0. In the agent configuration file, you should specifytwo communication channels, one through each SP. For the firstcommunication channel, you will specify c6t2d0 in the agentconfiguration file. For the second channel, you will specify c7t1d0in the file.

5. Enter the device names for the appropriate devices in the agentconfiguration file.

6. Save the agent file.

7. If the agent is running, stop it (refer to the section Stopping the hostagent, page 40). Then restart the agent.

8. For CX200, CX400, CX600, and FC4700 storage systems withoutthe Access Logix enabler installed, type the CLI commandsystemtype to specify an HP-UX system type. As an argumentto the command, if you are using the HP-UX PVLINKSfeature, specify -config 2; if you are not using PVLINKS,specify -config a. As a device name, use one of the d0 devicenames you noted in the ioscan listing above. For example:navicli -d c6t2d0 -h server1 systemtype -config 2

9. Wait for the SPs to restart, as indicated when the disk status lightson the front of each disk stop flashing.

If you do not have a Model FC5600/5700 or Model FC4400/4500storage system, you have finished the communication channelidentifying procedure; skip to the next section. For a Model


FC5600/5700 or Model FC4400/4500 storage system, there areseveral additional steps, as follows.

10. Run the ioscan program again, specifying adifferent name for the output file; for example:ioscan -fnC diskinsf -eioscan -fnC disk > second.scan

11. Print the new scan file.

12. In the new ioscan listing, use the hardware (H/W) paths to comparecommunication channel device names to those in the originallisting. It is very likely that the communications channel devicenames will be different. For example, compared to the listing earlier:

Class IH/W Path Driver S/W State H/W Type Description==================================================================

/dev/dsk/c0t6d0 /dev/rdsk/c0t6d0disk15 2/2/0.8.0.2.0.0.0 sdiskCLAIMED DEVICE DGC C5600WDUNBdisk4 4/2/0.0.0 sdisk CLAIMED DEVICE TOSHIBA CD-ROM...

/dev/dsk/c5t0d0 /dev/rdsk/c5t0d0disk11 6/0/0.8.0.1.0.0.0 sdiskCLAIMED DEVICE DGC

/dev/dsk/c10t0d0 /dev/rdsk/c10t0d0__________________________________________________________________

Notice that the listing for the communication channel devices haschanged as follows: Hardware path 2/2/0.8.0.255.0.2.0 DGCchanged to 2/2/0.8.0.2.0.0.0 DGC C5400WDUNB, anddevice /dev/dsk/c6t2d0 changed to /dev/dsk/c9t0d0.

Hardware path 6/0/0.8.0.255.0.1.0 DGC changed to 6/0/0.8.0.1.0.0.0DGC C5400WDUNB and device /dev/dsk/c7t1d0changed to /dev/dsk/c10t0d0.

13. Edit the agent configuration file again and change the originalcommunication channel device names to those that appeared afteryou entered the systemtype command.

14. Restart the agent.

15.

Continue to the next section and resume editing the agent configurationfile.

Enabling an alternate communication channel

You can configure the host agent to take advantage of theHP-UX Logical Volume Manager (LVM) alternate links (PVLINKSper HP), allowing all configured LUNs in the storage system


to be available to both SPs. Enable alternate path access byuncommenting the following line in the configuration file:

OptionsSupported AutoTrespass

Adding users to the host agent configuration file

Any user who can log in to a server that is a Navisphere managementstation can monitor the status of its managed storage systems. However,a user must be a privileged user in the host agent configuration file tochange a managed storage system’s configuration.

If you will be using Navisphere Manager 6.X to configure the hostagent and manage your storage systems, you will be using a portalsystem for legacy storage systems. To add privileged users for a portalconfiguration, see Adding IP addresses for a portal system, page 24. To addother privileged users, see Adding privileged users, page 26.

Specifying a polling frequency for the host agent

Polling frequency sets the time interval for the agent to execute anautomatic hardware poll to the storage system and update the agent’simage of the storage system. Polling frequency determines how oftenthe storage system is polled. The default polling interval is 60 seconds.

Note: This background polling is automatic and occurs whether or not a clientis communicating with the storage system. Since polling uses storage-systemresources, setting the polling frequency value too low may affect performance.

Add the following line to the host agent configuration file:

poll n

where n is 0 or an integer specifying the number of seconds betweeneach poll of the host agent’s SP. The minimum value, other than 0, is10. We recommend that n be equal to or greater than 60 (the defaultvalue). If n is omitted, host agent polling is disabled and the SP isinaccessible. If n equals 0, the host agent will poll the SP every time itgets a poll request.

Specifying the number of SP events to read

The host agent reads event entries from the SP unsolicited event log atstartup. You specify the number of the most current event to read.


Since the complete log can contain as many as 16,800 entries, you maynot want to burden Navisphere agent with reading all of them.

Note: If you enter a small value, Navisphere Manager and Navisphere CLIusers will not be able to view the entire contents of the log without firststopping all applications, changing the value in the configuration file, savingthe configuration file, restarting the agent, and restarting the applications.

To specify the number of SP event log entries to transfer, add thefollowing line to the host agent configuration file:

eventlog n

where n is the number of log entries to transfer. For a serial connection,100 < n < 16,800. For a fibre connection, 2048 < n < 16,800. If n is 0, theentire log is read. If n is a positive integer in the specified range, thespecified number of entries are read.


Using the Event Monitor configuration file

The Navisphere Host Agent can monitor storage-system events andtake such action as sending email or paging you if specified eventsoccur. The Event Monitor that ships with Navisphere Managerprovides an interactive way to define these events and actions. If youdo not have Event Monitor, you can still define such events and actionsby editing the Event Monitor configuration file.

/etc/Navisphere/Navimon.cfg

The file is self-documenting; that is, text in it describes how to defineevents and the actions you want taken if the events occur. You cantest the file after editing it using the Navisphere CLI commandresponsetest, as explained in the Navisphere Command Line InterfaceReference.

What next?

If you are upgrading the host agent, you have finished the upgrade.

If you are setting up a new server, start the host agent, as described inStarting and stopping the Navisphere Host Agent, page 40.


Running the Navisphere Host Agent

This section describes how to test the host agent connections and howto start and stop the host agent.

Starting and stopping the Navisphere Host Agent

On an HP-UX server, the host agent starts automatically when youbring the server up to init level 2. When you first start the host agent,look at the system log for the server’s operating system to make surethe agent started and no device errors occurred. The system log islocated in /var/log/messages.

Note: When a storage system experiences heavy input/output traffic (that is,applications are using the storage system), information may not be reportedto the host agent in a timely manner, resulting in the host agent taking severalminutes to execute a storage-system management task. This behavior is mostevident when one host agent is managing multiple storage systems. Also, if theSP event log is large and the host agent configuration file is set up to read allthe events, it may take a few minutes for the host agent to start.

Starting the host agent

Log in as root and enter this command:

/sbin/init.d/agent start

Stopping the host agent

Log in as root and enter this command:

/sbin/init.d/agent stop

Testing the host agent connections

Before continuing, you should test the host agent connections asfollows:

1. Start the host agent as described on Starting and stopping theNavisphere Host Agent, page 40.

2. Look for any errors on the console and in the operating system logto make sure the agent started and no device errors occurred.


3. Verify that the host agent on the server can see the storage systemas follows:

a. Enter the following CLI command:navicli -d device -h hostname port -list -hba

where device is the device name for the storage system hostnameis the server name

For each HBA in the server, a listing similar to the following willbe displayed. For storage systems in a SAN (shared storage)environment, the listing includes HBAs in all connected hosts.Information about each HBA:HBA UID: 10:00:00:60:B0:3E:46:AC:10:00:00:60:B0:3E:46:ACServer Name: siux134Server IP Address: 128.221.208.134HBA Model Description:HBA Vendor Description:HBA Device Driver Name:Information about each port of this HBA:SP Name: spaHBA Devicename: sp0Trusted: NOLogged In: YESSource ID: 1Defined: YESInitiator Type: 0Storage Group Name:Storage Group 134

b. In the listing, examine the information for each HBA installed inthe host to verify the path from the HBA to the SP.

c. In the listing, check the information for each HBA to make sureit is logged into the appropriate SP in the storage system.

Host agent status and error logging

While the system is running, the operating system tracks informationabout host agent events and host agent errors, and places thisinformation in log files on the server.

The host agent error log tracks information about the host agent’sstartup, the host agent shutdown, and errors that might occur, such asthe host agent’s inability to access a device in the configuration file. Ifproblems occur, log files are a good place to start your troubleshooting.

Host agent events and errors are logged in /var/adm/syslog/syslog.log.


Note: Host agent events are also recorded in the /etc/log/agent.log file.


Installing and removing the Navisphere Server Utility

This section describes how to install the Navisphere Server Utility on aserver connected to a CX3-series or CX-series storage system.

Note: Do not install the server utility on a VMware Virtual Machine. You caninstall the utility on a VMware ESX Server.

Installing the Navisphere Server Utility on an HP-UX server

EMC recommends that you install the most recent version of theNavisphere Server Utility software that is appropriate for yourconfiguration. You can download the most recent version from thesoftware download page on the Powerlink website (CX3–series andCX-series). You can also install the software from the server supportCD (any storage system); however, the CD may not contain the mostrecent version for your configuration.


2. If any previous revision of the server utility is installed on theserver, remove it before continuing.

Note: To verify if the server utility is installed, enter the /usr/sbin/swlistcommand to get a list of the currently installed software.


a. On the Powerlink website, select Support > Downloads andPatches and navigate to the Navisphere Server Utility downloadsection, which may be in either the CLARiiON NavisphereServer Utility section or the CLARiiON Navisphere Managersection.

b. Select the appropriate Navisphere Server Utility version anddownload the zip file to a Windows server.

c. Transfer the HOSTUTIL.dep file to the HP-UX server.

d. Install the HOSTUTIL.dep file on the HP-UX server.











g. Click Enter. Note the device name for the CD or DVD, forexample, /dev/dsk/c2t2d0.

h. Exit the SAM utility.At the command prompt (#) in the hpterm or xterm window,use the following command from the root directory tomake sure the /cdrom or /dvdrom directory exists:lsIf the /cdrom or /dvdrom directory exists, it will appear in theresulting list. If the /cdrom or /dvdrom directory doesnot exist, create it with the following command:mkdir /cdromormkdir /dvdrom


j. At the command prompt (#) in the hpterm orxterm window, execute the following commandto change to the /cdrom or /dvdrom directory:


cd /cdromorcd /dvdrom

k. Execute the following command to specify theCD or DVD as the source depot:/usr/sbin/swinstall -s /cdrom/hpux/HOSTUTIL.dep -xmount_all_filesystems=false HOSTUTILor/usr/sbin/swinstall -s /dvdrom/hpux/HOSTUTIL.dep -xmount_all_filesystems=false HOSTUTIL


If you installed the server utility from the CD, remove the CDfrom the server’s CD or DVD drive.

Removing the server utility on an HP-UX server


2. Execute the following command to remove the server utility:/usr/sbin/swremove -x mount_all_filesystems=false HOSTUTILThe removal process begins. The removal process is completewhen there is no error and the following message is displayed:END swremove SESSION


Running the Navisphere Server Utility

This section describes how to start and use the server utility.

Starting the Navisphere Server Utility

You can run the server utility from the server or from the serversupport CD.

Starting the Navisphere Server Utility on an HP-UX server

1. Open a hpterm window.

2. Navigate to the Navisphere bin directory:cd /opt/Navisphere/bin

3. Run the server utility:./naviserverutil

Starting the Navisphere Server Utility for an HP-UX server on the CD

1. In the server’s drive, insert the server support CD that shippedwith your storage system.

2. At the command prompt (#) in anhpterm window, create a CD directory:mkdir /cdrom

3. Identify the device file:ioscan -funC diskThis command lists all recognized CD drives and their associateddevice files. The filename will be similar to /dev/dsk/c1t2d0.

4. Mount the CD drive:mount /dev/dsk/device_filename /cdromwhere device_filename is the device filename from step 3. Forexample, mount /dev/dsk/c1t2d0 /cdrom.

5. Navigate to the HP-UX directory:cd /cdrom/hpux


6. Run the server utility:./naviserverutil

Using the Navisphere Server Utility

The Navisphere Server Utility allows you to perform the followingfunctions:

Update server information on the storage system

Generate a high-availablity report

Updating server information on the storage system

The Update Server Information option allows you to send informationabout the server to all connected storage systems. To update serverinformation, select option 1 from the server utility’s Welcome screen,and follow the instructions on the utility.

Generating a high-availability report

The Generate high availability report option and the naviserverutilhav -upload command determine if the server is configured for highavailability by verifying that the server has at least one connection pathto each storage-system SP, and that PowerPath or some other failoversoftware, such as DMP or PV Links, is running. .

After the verification, the utility generates a summary report and savesit to the server. If you issue the naviserverutil hav -upload command,the utility also sends the report to the specified storage system.

Generate a high-availability report to:

check the status of a server.

prepare for a software installation on a storage system.

Checking the status of a serverTo periodically check the high availability status of a server, selectoption 3 from the server utility’s Welcome screen, and follow theinstructions on the utility to generate a high-availability report.

Preparing for a software installation on a storage systemIf you are generating a high-availability report as a prerequisite toupdating storage-system software, you need to upload this report to thestorage system prior to installing the software on the storage system.To generate and upload an HA report, issue the following commandfrom the directory to which you installed the utility:


naviserverutilcli hav -upload -ip IPaddress -user username -passworduserpassword -scope scopelevel -port 443/2163 [-directory outputdirectory]where:IPaddress is the IP address of an SP on the storage system to which youwill upload the report. username the login name for the storage system.userpassword is he password required for access to the storage system.scopelevel is the level of access this username and passwordhas to the storage system - 0 = global; 1 = local.outputdirectory is the directory to which you want to deposit the reporton the server. This switch is required only if you are running the serverutility from the CD. Otherwise the report is automatically saved to theNavisphere Server Utility installation directory.

Note: If the server utility is installed on your server and you specify a directory,the directory you specify will override the server utility’s installation directory.

After uploading the HA reportIn addition to running the server utility to validate server highavailability, we strongly recommend that you perform the followingmanual checks.

Verify support of software and hardware — Make sure thatyou have verified that all software and hardware is supportedand interoperable according to EMC’s E-Lab™ InteroperabilityNavigator and support matrices.

Note: This tool does not verify that you are running a supported switchfirmware, nor does it check that you are using redundant switches(recommended).

Upgrading storage–system software — If you are about to performa storage-system software online upgrade or you added an HBA, aLUN, or changed connectivity (added a path or changed zoning):

Make sure that you have validated all software and hardwareare supported and interoperable according to EMC E-LabInteroperability Navigator and support matrices.

Verify that all LUNs (virtual disks) that your servers will accessduring the upgrade are under path management softwarecontrol. For servers running PowerPath and DMP, see theFailover Software section on the Details tab of the report and


locate these LUNs. If they are not in the list, the server will loseaccess to those LUNs during the software upgrade.


Installing and removing the Admsnap Utility

EMC strongly recommends that you install admsnap on all serversconnected to a storage system that has the SnapView driver installed.

Important: If you are upgrading your storage system to FLARE OEversion 02.19.xxx.5.yyy or later, you must upgrade admsnap to version2.9.x or later. Before you upgrade FLARE, verify that your operatingsystem version supports admsnap version 2.9.x or later. Refer to theAdmsnap Release Notes or the EMC Support Matrix on Powerlink.

Note: For the supported versions of these operating systems, see the AdmsnapRelease Notes.

Installation prerequisites

Before you can install and use the Admsnap Utility, you must:

Install SnapView on a supported CLARiiON storage system. Fora list of supported storage systems, refer to the release notes forSnapView and admsnap.

Enable data access control on the same CLARiiON storage system.

Installing the Admsnap Utility on an HP-UX server

EMC recommends that you install the most recent version of theAdmsnap Utility software that is appropriate for your configuration.You can download the most recent version from the software downloadpage on the Powerlink website (CX3–series and CX-series). You canalso install the software from the server support CD (any storagesystem); however, the CD may not contain the most recent version foryour configuration.

1. On the toolbar at the bottom of the screen, click the terminal icon.An hpterm window opens.

2. At the command prompt (#) in the hpterm window, enter:

/usr/sbin/swlist

3. When the list of currently installed software is displayed, examinethe list to determine if any previous revision of admsnap is present.


4. If a previous revision is installed, remove it as described in Removingthe Admsnap Utility on an HP-UX server, page 53.


a. On the Powerlink website, select Support > Downloads andPatches and navigate to the Admsnap Utility download section,which may be in either the CLARiiON SnapView section orthe SnapView section.

b. Select the appropriate Admsnap Utility version to downloadand select the option to save the zip file to your server.

c. Select the appropriate Admsnap Utility version and downloadthe zip file to a Windows server.

d. Transfer the admsnap.dep file to the HP-UX server.

e. Install the admsnap.dep file on the HP-UX server.


a. If the CD or DVD drive is currently mounted, unmount it; forexample:

cd/unmount /cdrom

or

cd/unmount /dvdrom

b. Insert the server support CD into the server’s CD drive.

c. At the command prompt window, enter

sam

The system administration utility (SAM) top-level menu opens.


e. The Peripheral Devices menu opens.

f. Select the Cards and Devices option. The Cards and Devicesdialog box opens with several menu choices at the top of thedialog box.

g. Select the line in the list that contains descriptions of“CD-ROM SCSI drives” or “DVD-ROM drives”. (Note that a



manufacturer’s name may preced the phrase “CD-ROM SCSIdrives” or “DVD-ROM drives”.)

h. At the top of the Cards and Devices dialog box, open the Actionpull-down menu and select Show Device Files.

i. A list of device names appears.

j. Note the device name for the CD, for example, /dev/dsk/c2t2d0and click OK.

k. Exit the SAM utility.

l. At the command prompt (#) in an hpterm window, use thefollowing command from the root directory to make sure the/cdrom directory exists:

ls

m. If the cdrom directory exists, its name appears in the resultinglist. if the directory cdrom does not exist, create it with thefollowing command:

mkdir /cdrom

n. Type the following command to mount the CD:

mount devicename /cdrom

where devicename is the name you previously noted above.

o. At the command prompt (#) in an hpterm window, execute thefollowing command to change to the cdrom directory:

cd /cdrom/hpux

p. At the command prompt (#) in an hpterm window, execute thefollowing command to change to the cdrom directory:

/usr/sbin/swinstall —s /cdrom/hpux/admsnap.dep —xmount_all_filesystems=false admsnap

q. At the command prompt (#), execute the following commandsto unmount the CD or DVD:

cd/unmount /cdrom

or

cd/unmount /dvdrom


You have installed admsnap on your HP-UX server. Thesoftware is installed in the directory /usr/admsnap.

Removing the Admsnap Utility on an HP-UX server


2. Execute the following command to remove admsnap:/usr/sbin/swremove —x mount_all_filesystems=false admsnapThe removal process begins. The removal process is completewhen there is no error and the following message is displayed: ENDswremove SESSION.


Running the Admsnap Utility

Refer to the EMC SnapView Command Line Interfaces Reference forinformation on running admsnap commands.


Copyright© 2004–2007 EMC Corporation. All Rights Reserved.

EMC believes the information in this publication is accurate as of its publication date. Theinformation is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATIONMAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TOTHE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIEDWARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires anapplicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks onEMC.com

All other trademarks mentioned herein are the property of their respective owners.


Documents

CLARiiON® Server Support Products for HP-UX Server ... · Products for HP-UX Server Installation Guide P/N 300–002–043, Revision A08 January 16, 2007 This guide describes how