clariion® server support products for aix server ... clariion® server support products for aix...

EMC CLARiiON® ServerSupport Products for AIX Server

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

January 16, 2007

This guide describes how to install and remove the Navisphere Host Agent,Navisphere Server Utility, Navisphere Command Line Interface (CLI), oradmsnap software on an IBM server with the AIX 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 ........................................................... 5Determining whether to install the host agent or server utility........... 6Requirements for the host agent, server utility, and CLI ................... 8Installing or removing the Navisphere Host Agent and CLI ............. 9Configuring the Navisphere Host Agent ......................................... 19Using the Event Monitor configuration file...................................... 32Running the Navisphere Host Agent .............................................. 33Installing and removing the Navisphere Server Utility ..................... 35Running the Navisphere Server Utility ........................................... 40Installing and removing the Admsnap Utility.................................. 43Running the Admsnap Utility ........................................................ 48

1

About EMC Navisphere Software

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

Navisphere Host Agent

Navisphere Server Utility

Admsnap Utility

Navisphere Command Line Interface (CLI)

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. For

2 EMC CLARiiON® Server Support Products for AIX Server Installation Guide

Windows servers running Navisphere Server Utility version 6.20 orhigher, if the Registration Service feature remains enabled after theinstallation 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

EMC CLARiiON® Server Support Products for AIX Server Installation Guide 3

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).



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 AIX 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 5 .


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 6 .

Installing the host agent and CLI on an RS/6000 system

To install the Navisphere agent and/or CLI, you must:

Determine whether a previous version of the software you want toinstall (host agent and/or CLI) is currently installed on the hostand, if so, remove it.

Install the Navisphere agent files and/or the CLI files. Beforeinstalling the host agent, make sure that the disk-array storagesystem is connected to the AIX server on which you are installingNavisphere agent.

Determining if a previous revision is installed

1. On the AIX host, log in as superuser (root).

2. Open an xterm window and enter the following command to listcurrently installed Navisphere software:

lslpp -L | grep NAV

3. Examine the list of software to determine if any previous revision ofNavisphere agent or CLI is present. If a previous revision is present,remove it before continuing to the next section.

Installing the agent and/or CLI files

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 thesoftware download page on the Powerlink website (CX3–series and


CX-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.

Use the following procedure to install the host agent, the CLI, or boththe host agent and CLI using the server support CD.

1. Log in to the AIX server as the administrator or someone who hasadministrative privileges.

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

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

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

c. Transfer the .lpp file to the usr/sys/inst.images folder on an AIXserver.

3. To install the software from the server support CD (any storagesystem), insert the CD into the host’s CD drive and use thefollowing command to mount the CD:

mount -v cdrfs -o ro /dev/cd0 /cdrom

4. If the SMIT (System Management Interface Tool) SystemManagement is not already open, enter the following commandto open it:

smit

5. From the SMIT System Management window, follow the path:

Software Installation and Maintenance > Install and UpdateSoftware > Install and Update from ALL Available Software

The Install and Update from ALL Available Software windowopens.

6. In the Install and Update from ALL Available Software window,either select List and then the directory that contains the Navispheresoftware, or enter the directory path in the Input device/directoryfor Software field.

7. Click OK and at the confirmation prompt and click OK again.



8. On the line, SOFTWARE to install, select List .

9. From the list that appears, select the Navisphere software that youwant to install (NAVIAGENT or NAVICLI or both), and click OK.

10. Click OK in the ALL Available Software window.

11. When the confirmation window is displayed, click OK.

The installation process begins and the progress of the installationappears in the Install and Update from ALL Available Softwarewindow. When the installation completes, the same windowindicates that the installation was successful.

Note: You may need to scroll down to the bottom of the output windowto view the Installation Summary.

12. Using SMIT, verify that the Navisphere Agent and/or CLI softwareare installed.

13. Configure the LUNZ device for AIX using the cfgmgr command.

14. 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 Navisphereagent to use NIC 2, you would configure agentID.txt as follows:host28.mydomain.com192.111.222.3

The agentID.txt file should contain only these two lines, without anyformatting. The first line should contain the hostname and the secondline should contain the IP address of the HBA/NIC port as describedabove. Both lines should end with a carriage return. As a result, thecursor will be on a third line but this line should not contain any 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.

What next?

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

For CX3-series or CX-series storage systems — If you are setting upa new server, go to Running the Navisphere Host Agent, page 33. If you


are just upgrading the host agent or CLI on an existing system, you arefinished with the upgrad

Installing the host agent and CLI on an RS/6000 SP system

The following sections describe the procedures for installing the hostagent and CLI on an SP system. These procedures install the softwarefrom the control workstation on all nodes simultaneously.

Use the following procedure to install the host agent, the CLI, or boththe host agent and CLI. If you will install both, install the host agentfirst.

Hardware and software requirementsTo run the host agent and/or CLI, the following software must berunning on the control workstation and SP nodes:

RS/6000 SP Parallel System Support Programs.

HACMP for AIX (optionally if HACMP support software is to beinstalled).


1. At the control workstation, log in as superuser (root).

2. Open an xterm window and enter the following com-mand to list currently installed Navisphere software:dsh lslpp -L | grep NAV

3. Examine the list of software to determine if a previous version ofthe software you want to install (host agent and/or CLI) is currentlyinstalled on the host and, if so, remove it.

Installing the agent and/or CLI files

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 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.

Follow the steps below to install the Navisphere agent/CLI softwareusing the server support CD. This procedure installs the software on allSP nodes at once from the control workstation.


! CAUTION

When performing this procedure, it is important to be in the controlworkstation window, and not a node or other window.

Creating a directory for the Navisphere agent/CLI software

1. Verify that you are logged in as superuser (root).

2. On the control workstation, change directories to:

/spdata/sys1/install/pssplpp/PSSP-3.1.1

3. Create the subdirectory Navisphere, using the following command:

mkdir Navisphere

Copying the Navisphere agent/CLI software to the new lppsource directoryUse the following procedure to copy the agent/CLI software (usingSMIT) to the new lpp source directory:


a. On the Powerlink website, select Support > Downloadsand Patches and navigate to the navigate to the CLARiiONNavisphere Host Agent/CLI download section for AIX

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


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

a. Insert the CD into the control workstation’s CD-ROM drive.

b. Enter this command at the AIX shell prompt:

smit bffcreate

c. SMIT displays the Copy Software to Hard Disk for FutureInstallation screen and prompts for an input device.

d. On the screen that appears, select the source directory (eitherthe CD-ROM device or directory) by clicking List at the Inputdevice field.



e. From the list that appears, select the input device or drive. Forexample, for the CD-ROM, select /dev/cd0 (SCSI MultimediaCD-ROM Drive).

f. At the SOFTWARE package to copy field, click all.

g. At the DIRECTORY for storing software package field, enter/spdata/sys1/install/pssplpp/PSSP-3.1.1/Navisphere

h. At the DIRECTORY for temporary storage during copyingfield, select /tmp.

i. At the EXTEND file systems if space needed? field, select yes.

j. At the Process multiple volumes? field, select yes.

Installing Navisphere agent/CLI software

Note: Using SMIT requires you to install the Navisphere agent/CLI softwareon each SP node individually and is not recommended for installation.

1. Using NFS, mount the image directory from specified SP nodes:dsh mountcwsname:/spdata/sys1/install/pssplpp/PSSP-3.1.1/mnt

2. Run the installp command on all nodesfrom the Navisphere directory:dsh installp -agXd /mnt/Navisphere NAVIAGENTNAVICLI


4. 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 Navisphereagent to use NIC 2, you would configure agentID.txt as follows:host28.mydomain.com192.111.222.3

The agentID.txt file should contain only these two lines, without anyformatting. The first line should contain the hostname and the secondline should contain the IP address of the HBA/NIC port as describedabove. Both lines should end with a carriage return. As a result, thecursor will be on a third line but this line should not contain any 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.

5. Using SMIT, verify that the Navisphere Agent and/or CLI softwareare installed.


What next?

Before you can use the host agent, you must edit the host agentconfiguration file.

Removing the Navisphere agent and/or CLI on an RS/6000 system

Note: To avoid losing site-specific information, copy the Navisphere agentconfiguration file (agent.config) to a safe location before removing anyNavisphere software.

1. On the AIX host, log in as superuser (root).

2. At the AIX shell prompt in an xterm window, start SMIT:smitThe SMIT System Management window opens.

3. From the SMIT System Management window, follow this path:Software Installation and Maintenance > SoftwareMaintenance and Utilities > Remove Installed SoftwareThe Remove Installed Software window opens.

4. In the Remove Installed Software window, click the List buttonfor Software name.

5. From the list that appears, select the Navisphere software you wantto remove (NAVIAGENT, NAVICLI, or both), and click OK.

6. In the Remove Installed Software window, click the List button forPREVIEW only? (The remove operation will NOT occur).

7. From the list that appears, click no.

8. In the Remove Installed Software window, click the List button forREMOVE dependent software?

9. From the list that appears, click yes.

10. In the Remove Installed Software window, click OK.


11. When the confirmation window is displayed, click OK. The files areremoved. The removal process is complete when you see a successmessage.

Removing the Navisphere agent and/or CLI on an RS/6000 SP system

Note: To avoid losing site-specific information, copy the Navisphere agentconfiguration file (agent.config) to a safe location before removing anyNavisphere software.

Uninstall existing agent and CLI software on specified nodes:dsh installp -u NAVIAGENT NAVICLI


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 22.

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 20

Adding IP addresses for a portal system, page 20


Adding privileged users, page 22

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 20.

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

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 22. If you are done editing the host agent configuration file, go toSaving the host agent configuration file, page 23.

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 host agentconfiguration file, stop and restart the hostagent by entering the following commands:rc.agent stoprc.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 24.

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.

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.

Note: The host agent configuration file does not require any device entries forCX3-series or CX-series storage systems, and none of the other parametersdefined in the file affect the storage systems.

The pathname to the host agent configuration file is:

/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 sp0 NAVISPHERE-0 "NAVISPHERE-0"#device sp1 NAVISPHERE-1 "NAVISPHERE-1"#device sp2 NAVISPHERE-2 "NAVISPHERE-2"#device sp3 NAVISPHERE-3 "NAVISPHERE-3"#device sp4 NAVISPHERE-4 "NAVISPHERE-4"#device sp5 NAVISPHERE-5 "NAVISPHERE-5"## automatically detect manageable devicesdevice auto auto#

# 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.

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 host


agent’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.

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 20. To addother privileged users, see Adding privileged users, page 22.

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 33.


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 AIX server, the host agent starts automatically when you bringthe server up to init level 2. When you first start the host agent, look atthe system log for the server’s operating system to make sure the agentstarted and no device errors occurred. The system log is located 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:

rc.agent start

Stopping the host agent

Log in as root and enter this command:

rc.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 33.

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 /etc/log/agent.log.


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 RS/6000 system

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


1. At the AIX host, log in as superuser (root).

2. Open an xterm window and enter the following com-mand to list currently installed Navisphere software:lslpp -L | grep HOST

3. Examine the list of software to determine if any previous revisionof Navisphere Server Utility is present. If a previous revision ispresent, remove it before continuing.

Installing the Navisphere Server Utility

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.

1. Log in to the AIX server as the administrator or someone who hasadministrative privileges.


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



Server Utility section or the CLARiiON Navisphere Managersection.

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



a. Insert the CD into the server’s CD-ROM driveand use the following command to mount the CD:mount -v cdrfs -o ro /dev/cd0 /cdrom

4. If you are not in the SMIT (System Management In-terface Tool) System Management window, openthis window by entering the following command:smit

5. From the SMIT System Management window, follow this path:Software Installation and Maintenance > Install and UpdateSoftware > Install and Update from ALL Available SoftwareThe Install and Update from ALL Available Software windowopens.

6. In the Input device/directory for Software field in the Install andUpdate from ALL Available Software window, enter the path:

/cdrom/AIX/usr/sys/inst.images

Click OK.

7. In the Install and Update from ALL Available Software window,click the List button for SOFTWARE to install.

8. From the list that appears, select the HOSTUTIL, and click OK.

9. Click OK in the ALL Available Software window.

10. When the confirmation window is displayed, click OK. Theinstallation process begins and the progress of the installationappears in the Install and Update from ALL Available Softwarewindow.

The installation is complete when you see an installation summarymessage.

11. If you installed the software from the CD, unmount the CD or DVDand then remove he CD from the server’s CD or DVD drive:


unmount /cdrom

unmount /dvdrom

Installing the Navisphere Server Utility on an RS/6000 SP system

This section describes how to install the Navisphere Server Utility onan RS/6000 SP system connected to a CX3-series or CX-series storagesystem.

Follow these steps to install the Navisphere Server Utility using theinstallp command. This procedure installs the software on all SP nodesall at once from the control workstation.

Note: Using SMIT requires you to install the Navisphere Server Utility on eachSP node individually and is not recommended for installation.

Creating a directory for the Navisphere Server Utility

1. Verify that you are logged in as superuser (root).

2. On the control workstation, change directories to the following:

/spdata/sys1/install/pssplpp/PSSP-3.1.1

3. Create the subdirectory Navisphere, using the following command:

mkdir Navisphere

Copying the Navisphere Server Utility to the new lpp sourcedirectory

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.


To download the software for CX3–series or CX-series storage systems, on thePowerlink website, select Support > Downloads and Patches and navigate tothe Navisphere Server Utility download section, which may be in either theCLARiiON Navisphere Server Utility section or the CLARiiON NavisphereManager section. Select the appropriate Navisphere Server Utility version,download the zip file to a Windows server, and transfer the .llp files to theAIX server.

Use the following procedure to copy the server utility (using SMIT)to the new lpp source directory:

1. Insert the CD-ROM into the control workstation’s CD drive.

2. Enter this command at the AIX shell prompt:smit bffcreateSMIT displays the Copy Software to Hard Disk for FutureInstallation screen and prompts for an input device.

3. Select the CD drive as follows:

a. At the Input device field, click List. The SMIT Single Selectlistscreen appears.

b. Select /dev/cd0 (SCSI Multimedia CD-ROM Drive) from thelist that appears. The SMIT Copy Software to Hard Disk forFuture Installation screen appears again.

c. Click OK. A second SMIT Copy Software to Hard Disk forFuture Installation screen appears.

4. Select the software to copy as follows:

a. At the SOFTWARE package to copy field, click all.

b. At the DIRECTORY for storing software package field, enter/spdata/sys1/install/pssplpp/PSSP-3.1.1/Navisphere.

c. At the DIRECTORY for temporary storage during copyingfield, select /tmp.

d. At the EXTEND file systems if space needed? field, select yes.

e. At Process multiple volumes? field, select yes.

f. Click OK. The software is copied to the directory.

g. Click Done.

h. Click Cancel on the Copy Software to Hard Disk for FutureInstallation screen.



Installing the Navisphere Server Utility

1. Using NFS, mount the image directory on all SP nodes:

Note: cwsname in the command below refers to the actual cws name (thatis, CWS 104684).

dsh mount cwsname:/spdata/sys1/install/pssplpp/PSSP-3.1.1 /mnt

2. Run the installp command on allnodes from the Navisphere directory.dsh installp -agXd /mnt/Navisphere HOSTUTIL


Removing the server utility on an AIX server

1. At the root directory, start SMIT by entering:smitThe SMIT System Management window opens.

2. From the SMIT System Management window, follow this path:Software Installation and Maintenance > SoftwareMaintenance and Utilities > Remove Installed SoftwareThe Remove Installed Software window opens.


4. From the list that appears, select HOSTUTIL, and click OK.

5. Click the List button for PREVIEW only? (remove operation

will NOT occur).


7. Click the List button for REMOVE dependent software.


9. Then click OK.

10. When the confirmation window appears, click OK. The files areremoved.


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 AIX server

1. Open a shell window.

2. Navigate to the HOSTUTIL directory:

cd /usr/lpp/HOSTUTIL

3. Run the server utility:

./naviserverutil

Starting the Navisphere Server Utility for an AIX server on the CD

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

2. At the AIX shell prompt, create a CD directory:mkdir /cdrom

3. Mount the CD drive:mount -v cdrfs -p -r /dev/cd0 /cdrom

4. Navigate to the following AIX directory:cd /cdrom/aix/usr/sys/inst.images

5. 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 server


utility 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 andlocate 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 AIX RS/6000 system

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 AIX server, log in as superuser (root).

2. Open an xterm window and enter the following com-mand to list currently installed admsnap software:lslpp - L admsnap

3. Examine the list to determine if any previous revision of admsnap ispresent. If a previous revision is present, remove it as described inRemoving the Admsnap Utility from an AIX RS/6000 system, page 46.



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 and downloadthe zip file to a Windows server.



a. Insert the server support CD into the server’s CD or DVD drive.

b. Enter the following command at the AIX shell prompt:crfs -v cdrfs -p ro -d cd0 -m /cd_tmp

c. Type the following commands to mount the CD, go to theCD directory, copy the admsnap files to the correct hard diskdirectory, and recreate the table of constant:

mount /cd_tmpcd cd_tmp/AIX/admsnap/AIX5.xcp * /usr/sys/inst.imagescd /usr/sys/inst.imagesrm .tocinutoc

6. If you are not in the SMIT (System Management Interface Tool)System Management window, open this window by entering:smit

7. From the SMIT System Management window, follow this path:Software Installation and Maintenance > Install and UpdateSoftware > Install and Update from ALL Available Software

The Install and Update from LATEST Available Software windowopens.

8. In this window, click List.

9. From the displayed list select the usr/sys/inst.images directory.

10. In the Install and Update from ALL Available Software window,click OK.



11. Click the List button for SOFTWARE to Install.

12. From the list that appears, select the software that you want toinstall (admsnap) and click OK.

13. Click OK in the LATEST Available Software window.

14. When the confirmation window appears, click OK.

The installation process begins and the progress of theinstallation appears in the Install and Update fromALL Available Software window. The installation iscomplete when you see a message similar to the following:

Name Level Part Event Resultadmsnap XXXXX USR INSTALL Success

The software is installed in the directory /usr/admsnap.

Your installation is complete.

Installing the Admsnap Utility on an AIX RS/6000 SP system

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 control workstation, log in as superuser (root).

2. Open an Xterm window and enter the following com-mand to list currently installed admsnap software:dsh lslpp -L admsnap*

3. Examine the list to determine if any previous revision of admsnapis present. If a previous revision is present, remove it as describedin Removing the Admsnap Utility from an AIX RS/6000 SP system,page 47.

! CAUTION

When performing the next procedure you must be in the controlworkstation window, and not in a node or other window.


4. On the control workstation, change directories as follows:cd /spdata/sys1/install/pssplpp/PSSP-3.1.1

5. Create the subdirectory admsnap, using the following command:mkdir admsnap

6. Enter the following command at the AIX shell prompt:crfs -v cdrfs -p ro -d cd0 -m /cd_tmp


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 and downloadthe zip file to a Windows server.

c. Transfer the .lpp files to the AIX server.


a. Insert the server support CD in the control workstation’s CDor DVD drive.

b. Type the following commands:

mount /cd_tmpcd /cd_tmp/aixcp * /spdata/sys1/install/pssplpp/PSSP-3.1.1/admsnapinutoc /spdata/sys1/install/pssplpp/PSSP-3.1.1/admsnap

9. Using NFS, mount the image directory on allSP nodes using the following command form:dsh mountcwsname:/spdata/sys1/install/pssplpp/PSSP-3.1.1 /mnt

where cwsname is the actual cws name (for example, CWS104684).

10. Run the installp command on all nodesfrom the Navisphere® directory by entering:dsh installp –agXd /mnt/admsnap all

The software is installed in the directory /usr/admsnap.

Removing the Admsnap Utility from an AIX RS/6000 system

1. At the root directory, start SMIT by entering:



smit

The SMIT System Management window opens.

2. From the SMIT System Management window, follow this path:

Software Installation and Maintenance > Software Maintenanceand Utilities > Remove Installed Software

The Remove Installed Software window opens.


4. From the list that appears, select ADMSNAP, and click OK.

5. Click the List button for PREVIEW only? (remove operation willNOT occur).


7. Next, click the List button for REMOVE dependent software.


9. Then click OK.

10. When the confirmation window appears, click OK.

The files are removed. The removal process is complete when yousee a message similar to the following displayed in the bottom ofthe window:

Name Level Part Event Resultadmsnap XXXXX USR DEINSTALL Success

Removing the Admsnap Utility from an AIX RS/6000 SP system

To uninstall existing admsnap software on all nodes, enter the followingcommand:

dsh installp -u admsnap


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.


clariion® server support products for aix server ... clariion® server support products for aix...

Documents