clariion server support products for vmware esx servers ... · emc clariion server support products...

EMC CLARiiON Server SupportProducts for VMware ESX

Servers and Virtual MachinesInstallation Guide

P/N 300–004–281, Revision A08

October 3, 2008

This guide describes how to install and remove the EMC® Navisphere®Host Agent, Navisphere Storage System Initialization Utility, NavisphereServer Utility, Navisphere Command Line Interface (CLI), and admsnapsoftware on a VMware ESX Server and VMware Virtual Machines.

This document uses the term “VMware ESX Server” to refer to ESX Server 3i, ESXServer 3.x, and ESX Server 2.5.

For information on supported operating system versions and serversoftware with a CX4 series, CX3 UltraScale™series, or a CX series storagesystem, refer to the E-Lab™ Interoperability Navigator on the Powerlink®website. For AX4–5 series or AX150 series storage systems, refer to theSupport Matrix link on the Install page of the storage-system supportwebsite. For AX100 series systems, refer to the Supported Configurations inthe “Technical descriptions” section, of the storage-system support website.

Topics include:

Storage system terminology ............................................................. 3About EMC Navisphere server software ........................................... 4Software for your storage system...................................................... 7Software for your VMware ESX Server.............................................. 8Finding current information ............................................................. 9Installing and removing the Navisphere Storage System InitializationUtility .......................................................................................... 10Running the Navisphere Storage System Initialization Utility ........... 22Determining whether to install the host agent or server utility.................................................................................................... 32

Requirements for the host agent, server utility, and CLI ................... 35Installing or removing the Navisphere Host Agent and CLI ............. 37Configuring the Navisphere Host Agent ........................................ 64

1

http://Powerlink.EMC.com

Using the Event Monitor configuration file ..................................... 66Running the Navisphere Host Agent ............................................. 67Installing and removing the Navisphere Server Utility .................... 71Running the Navisphere Server Utility ........................................... 78Installing and removing the Admhost Utility .................................. 85Running the Admhost Utility ........................................................ 88Installing and removing the Admsnap Utility ................................. 91Running the Admsnap Utility ....................................................... 102

2 EMC CLARiiON Server Support Products for VMware ESX Servers and Virtual Machines InstallationGuide

Storage system terminology

This document uses the following storage system terms:

CX4 series — refers to CX4-120, CX4-240, CX4-480, and CX4-960storage systems

CX3 series — refers to CX3 model 10 systems, CX3 model 20systems, CX3 model 40 systems, and CX3 model 80 storage systems

CX series — refers to CX300 series, CX500 series, and CX700 storagesystems

AX4-5 series — refers to AX4-5SC, AX4-5SCi, AX4-5, AX4-5i storagesystems

AX150 series — systems include the AX150SC, AX150SCi, AX150,and AX150i. AX100 series systems include the AX100SC, AX100SCi,AX100, and AX100i

AX series — to refer to AX150 series and AX100 series storagesystems

EMC CLARiiON Server Support Products for VMware ESX Servers and Vir-tual Machines Installation Guide

3

About EMC Navisphere server software

The EMC server-based software listed below is available on the serversupport CD that shipped with your storage system.

For information on the server software supported with yourCLARiiON® storage system and the minimum FLARE® versionrequired, refer to Software for your storage system, page 7.

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 Fibre Channel storage systems, use the Navisphere® Initializationutility to discover storage systems and set network parameters (IPaddress, subnet mask, and default gateway). In addition, for iSCSIstorage systems with iSCSI data ports attached to Windows servers, usethe utility to set network parameters for these ports.

For CX series storage systems, an authorized service provider must install andrun the initialization utility.

You can run the initialization utility from the server support CD or youcan install it on a server or other host such as a Navisphere off-arraymanagement station. The only requirement is that the host be connectedto the same network subnet as the storage-system management ports.

About the Navisphere Host Agent

The host agent registers the server’s host bus adapter (HBA) 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.

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 operating system drive mapping information to the attachedCLARiiON® storage systems.

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

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

About the Navisphere Server Utility

The server utility allows you to perform the following functions:

Update server information to the storage system — Lets you sendthe server name and IP address to the storage system and, if neededlater on, allows you to update or view this data.

Verify server high availability (HA) — Lets you determine if theserver 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 asVMware native, DMP, PV Links, or HP native failover for 11iV3is running. The utility does not detect any other native failoversoftware, such as Sun StorEdge Traffic Manager or Linux nativemultipath (MPIO).

Use the snapshot feature — On storage systems with NavisphereExpress, you can start and stop a snapshot on the source server(server assigned to the source virtual disk or source LUN), or youcan allow or remove access to the snapshot by the secondary server(server assigned to the snapshot).

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.


5

On AX4–5 series storage systems with Navisphere Manager, you cannot usethe server utility to manage snapshots. Instead, you must install and use theadmsnap utility.

About the Admsnap Utility

The Admsnap Utility is an executable program that you can runinteractively or with a script to manage SnapView® clones andsnapshots. The Admsnap Utility resides on the servers connected tothe storage system 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

If you upgraded to Navisphere Manager and want to manage snapshots,you must use the SnapView software and the Admsnap Utility. For moreinformation on SnapView and admsnap, refer to the Navisphere Manager helpand the EMC SnapView Command Line Interfaces Reference.

About the Navisphere CLI

The CLI complements, or is an alternative to Manager. It provides acommand line interface for storage-system management, includingstorage provisioning, status and configuration information retrieval,and control. You can use the CLI to automate management functionsthrough shell scripts and batch files. For more information, refer to theEMC Navisphere Command Line Interface (CLI) Reference Guide.


Software for your storage system

Table 1 lists the minimum FLARE version that your CLARiiON storagesystem requires and the server software that it supports.

Table 1 Minimum FLARE versions and supported software

Storage system Minimum FLARE version Supported server software

AX4-5 series 02.23.050.5.5xx (NavisphereExpress or Navisphere Manager)

AX4-5 series 02.23.050.5.xxx (NavisphereExpress only)

AX150 series 02.20.xxx.5.yyy

AX100 series 02.16.xxx.5.yyy

Storage systems with Navisphere Express— Navisphere Storage System Initialization Utility— Navisphere Server Utility— Navisphere CLIStorage systems with Navisphere Manager— Navisphere Storage System Initialization Utility— Navisphere Host Agent— Navisphere Server Utility— Admsnap Utility— Navisphere CLI

CX4–120, CX4–240, CX4–480,and CX4–960

04.28.000.5.xxx

CX3–10c 03.24.010.5.xxx

CX3 model 20 systems, CX3model 40 systems, and CX3model 80 systems

03.22.xxx.5.yyy

CX700, CX500 series, andCX300 series

02.16.xxx.5.yyy

Storage systems with Navisphere Manager— Navisphere Storage System Initialization Utility— Navisphere Host Agent— Navisphere Server Utility— Admsnap Utility— Navisphere CLI


7

Software for your VMware ESX Server

Table 2 lists the server software supported for your VMware ESX Server.

Table 2 Supported server software for VMware ESX Servers

ESX Server version Supported server software

ESX Server 3i Software supported on Virtual Machines— Navisphere Storage System Initialization Utility— Admsnap Utility— Admhost Utility— Navisphere CLISoftware supported on Windows Virtual Machines with the iSCSI initiator softwareinstalled (limited configurations only*)— Navisphere Host Agent (version 6.26.7 or later)— Navisphere Server Utility (version 6.26.7 or later)*Refer to the ESX Server compatibility guides for supported Windows and iSCSI initiatorversions.

ESX Server 3.x

ESX Server 2.5

Software supported on the ESX Server— Navisphere Storage System Initialization Utility— Navisphere Host Agent— Navisphere Server Utility— Navisphere CLISoftware supported on Virtual Machines— Navisphere Storage System Initialization Utility— Admsnap Utility— Admhost Utility— Navisphere CLISoftware supported on Windows Virtual Machines with the iSCSI initiator softwareinstalled (limited configurations only*)— Navisphere Host Agent (version 6.26.7 or later)— Navisphere Server Utility (version 6.26.7 or later)*Refer to the ESX Server compatibility guides for supported Windows and iSCSI initiatorversions.


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:


After you log in, select Support > Technical Documentation andAdvisories and find the following:

Navisphere Host Agent/CLI and Utilities Release Notes.

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

Installation Roadmap for CLARiiON Storage Systems (P/N 069001166),which provides a checklist of the tasks that you must complete toinstall your storage system in a storage area network (SAN) ordirect attach configuration.

For the most current management and security content, refer to theEMC Navisphere Manager help.

For Navisphere CLI commands, refer to the latest revision ofthe EMC Navisphere Command Line Interface (CLI) Reference (P/N300–003–628).


9


Installing and removing the Navisphere Storage System InitializationUtility

You can install the initialization utility on an ESX Server 3.x or 2.5 hostor on a VMware Virtual Machine. If you have an ESX Server 3i host, youcan only install the initialization utility on a VMware Virtual Machine.

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 initialize a storage system using the Navisphere Storage SystemInitialization Utility, the server must meet the following requirements:

Run a supported version of the operating system.

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

If you have an earlier version of the storage system initialization utilityinstalled, you must uninstall it before installing an updated version.

Installing the Navisphere Storage System Initialization Utility on an ESX Server 2.5 or3.x 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 mostrecent version from the software download page on the Powerlinkwebsite (CX4 series, CX3 series, CX series, and AX4-5 series) or on thestorage-system support website (AX series). You can also install thesoftware from the server support CD (any storage system); however,the CD may not contain the most recent version for your configuration.

1. Log in to the root account of a VMware ESX Server Service Consolethat is on the same subnet as the storage system.

2. At the command line prompt, look for an existing initializationutility:


rpm -qi naviinittool

3. If an earlier version of the software has been installed, you mustremove it before continuing.

4. To download the software for CX4 series, CX3 series, CX series, orAX4–5 series storage systems, do the following:

a. From the Navigator drop-down menu at the top right of thePowerlink website, select Software Downloads and Patches.

b. Select the appropriate initialization utility version to downloadand select the option to save the zip file to your server.

c. At the command line prompt, navigate to the directory whereyou saved the zip file and unzip the file.

unzip Linux-INITTOOL-version.zip

where version is the version listed in the filename.

5. To download the software for AX series storage systems, do thefollowing:

a. On the storage-system support website, select the link todownload software.





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

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

b. From a console window, mount the CD using the mountcommand for your operating system version.

c. From the CD directory, change to the Linux directory:


11


cd linux

This directory contains the VMware ESX Server install packages.

7. Install the initialization utility on the ESX Server Service Console:

./ESX_install.sh naviinttool

8. If you are installing the initialization utility on ESX Server 3.0 orlater or an ESX Server 3i, the script prompts you to open the TCP/IPports used by the initialization utility. The default firewall settingson the ESX Server 3.0 Service Console block these ports.

9. Enter y for the script to open the ports listed, or enter n to manuallyopen the ports after the installation (see Manually opening theTCP/IP ports, page 12).

If these ports are not opened, the initialization utility will not functionproperly.

When the installation is complete, the script copies theESX_uninstall.sh file to the /opt/Navipshere/bin directory for useduring the uninstall process.

10. If you installed the initialization utility from the server support CD,unmount the CD, and then remove the CD from the CD drive.

Manually opening the TCP/IP ports

To manually open TCP/IP port 2162 (outgoing) and port 2163(incoming), do the following:

If, during the installation, you entered y to open the ports, you do not needto perform the steps below.

1. Verify that you are logged in as root.

2. Enter the command:

esxcfg-firewall -o |- -openPort port,protocol,direction,application


For example, esxcfg-firewall -o 2163,udp,in,naviInitTool

where:

port is the port number. For the initialization utility, the port numbers are2162 and 2163.

protocol is udp

direction is the traffic direction. Use in for incoming traffic or out for outgoingtraffic.

application is naviInitTool for the storage system initialization utility.

Installing the Navisphere Storage System Initialization Utility on a Linux virtual machine


1. Log in to the root account of a Linux virtual machine that is on thesame subnet as the storage system.

2. At the command line prompt, look for an existing initializationutility:

rpm -qi naviinittool

If an earlier version of the software has been installed, you mustremove it before continuing.





13





d. Enter the following command to install the initialization utilitypackage:

rpm -ivh naviinittool-version-build.noarch.rpm

where version and build are the version number and the buildnumber of the initialization utility.

If you are upgrading the utility on the server, use -U in place of -i.


a. On the storage-system support website select the link todownload software.

b. Select the appropriate Navisphere Storage System InitializationUtility version to download and select the option to save thezip file to your server.





rpm -ivh naviinittool-version-build.noarch.rpm

where version and build are the version number and the buildnumber of the initialization utility.




a. In the drive of an ESX Server host with the Linux virtualmachine, insert the server support CD, which shipped with thestorage system or the upgrade kit (for AX4-5 series or AX seriessystems upgrading to Navisphere Manager).


c. From the CD directory, change to the Linux directory:

cd linux

This directory contains the Linux install packages.

d. Install the initialization utility:

rpm -ivh naviinittool.noarch.rpm


e. When installation is complete, remove the CD from the server’sCD drive.

Installing the Navisphere Storage System Initialization Utility on a Solaris virtual machine


1. Log in as superuser (root) on an ESX Server host with the Solarisvirtual machine that is on the same subnet as the storage system.


15

2. If an earlier version of the initialization utility is installed on theserver, remove it before continuing.

To verify if the initialization utility is installed, enter the pkginfo | grepHOST command.





unzip Sun-INITTOOL-version.zip



pkgadd -d INITTOOL.pkg



b. Select the appropriate Navisphere Storage System InitializationUtility version to download and select the option to save thezip file to your server.


unzip Sun-INITTOOL-version.zip





pkgadd -d INITTOOL.pkg



b. From a console window, mount the CD:

mount /mnt/cdrom

c. Install the Navisphere Storage System Initialization Utility:

/cdrom/cdrom0/solaris

pkgadd -d ./solaris/INITTOOL.pkg

6. At the prompt to select the packages to process, enter 1 to selectINITTOOL.

7. At the prompt about scripts that execute with superuser permissionduring the installation, enter y.

The screen displays information about the installation.

8. When installation is complete, exit the /cdrom directory by enteringcd /.

9. If you installed the initialization utility from the CD, remove theCD from the server’s CD drive.

Installing the Navisphere Storage System Initialization Utility on a ESX Server with theWindows virtual machine

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 mostrecent version from the software download page on the Powerlinkwebsite (CX4 series, CX3 series, CX series, and AX4-5 series) or on thestorage-system support website (AX series). You can also install the


17

software from the server support CD (any storage system); however,the CD may not contain the most recent version for your configuration.

1. Log in as the administrator (or someone who has administrativeprivileges) to the ESX Server with the Windows virtual machinethat is on the same subnet as the storage system.



b. Select the appropriate Navisphere Storage System InitializationUtility version to download and select the option to save thesoftware to your server.

c. In the directory where you saved the software, double-click theexecutable file to start the installation wizard.



b. Navigate to the Navisphere Storage System Initialization Utilitydownload section and select the option to save the softwareto your server.



a. In the drive of ESX Server with the Windows virtual machine,insert the server support CD, which shipped with the storagesystem or the upgrade kit (for AX4-5 series or AX series systemsupgrading to Navisphere Manager).

The server support menu opens. If you do not see the serversupport menu, follow the steps below to open it.

From the Windows taskbar, select:

Start > Run

In the Run dialog box, enter:

drive:\locales\en_US\start.html



where drive is the letter for the CD drive. Click OK.

b. Select your language, if prompted for it.

c. From the main menu, click Install Products on Server.

d. From the Install Products menu, click Navisphere StorageSystem Initialization Utility to open the installation wizard.

5. Follow the instructions on the installation screens to install theinitialization utility.

A user interface (UI), a text-based, and a command line version ofthe utility are installed.

6. When the installation is complete, click Done to exit the wizard.

7. If you installed the initialization utility from the CD, close the serversupport menu by selecting Main Menu and then Exit. You can nowremove the CD from the server’s CD drive.

Removing the Navisphere Storage System Initialization Utility on an ESX Server 3.x or2.5 host

1. Log in to the VMware ESX Server Service Console as root or as amember of an administrative group.

2. Navigate to the Navisphere bin directory:

cd /opt/Navisphere/bin

3. Enter the following command to remove the storage systeminitialization utility:

./ESX_uninstall.sh naviinttool

If you are removing the initialization utility on an ESX Server 3.0or later, the script notifies you about the TCP/IP ports that wereopened by the installation of the initialization utility. If no othersoftware on the ESX Service Console is using the ports listed, werecommend that you close these ports by entering the followingcommand:

esxcfg-firewall -c port,protocol,direction,application


19

where:

port is the port number. For the initialization utility, the port numbers are2162 and 2163.

protocol is udp


application is naviInitTool for the storage system initialization utility.

Removing the Navisphere Storage System Initialization Utility on a Linux virtual machine

1. Log in to the server as root or as a member of an administrativegroup.

2. Open a terminal window and enter the following command toremove the Storage System Initialization Utility:

rpm -e naviinittool

Removing the Navisphere Storage System Initialization Utility on a Solaris virtualmachine

1. At the Solaris server, log in as superuser (root).

2. Execute the pkgrm INITTOOL.pkg command to remove thestorage system initialization utility and confirm if prompted byentering y and y. If the initialization utility is not installed, you willreceive a Not found error message.

Removing the Navisphere Storage System Initialization Utility on a Windows virtualmachine

1. On the Windows virtual machine running the Storage SystemInitialization Utility that you want to remove, log in as theadministrator or the equivalent.

2. Open Control Panel by selecting Start > Settings > Control Panelor Start > Control Panel.

3. On the Control Panel pane, double-click Add/Remove Programs orProgram and Features.


4. Select Navisphere Storage System Initialization Utility and clickChange/Remove or Uninstall/Change.

5. If asked to confirm the removal, click OK and follow the steps toremove the software program.

EMC CLARiiON Server Support Products for VMware ESX Servers and Vir-tual Machines Installation Guide 21

Running the Navisphere Storage System Initialization Utility

You can start the storage system initialization utility from theserver on which it is installed or from the server support CD. Thestorage system initialization utility has three methods for executingcommands — a user interface (UI) version, a command line interfacethat can be scripted, or a text-based utility that cannot be scripted.Before continuing, make sure that the storage system is powered upcompletely.

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.

Starting the initialization utility on an ESX Server 2.5 or 3.x host or a Linux virtual machinea Linux virtual machinean ESX Server 2.53.x host or a Linux virtual machine

To start the text-based version of the utility, enter:

/opt/Navisphere/bin/naviinittoolcli

To start the command line version of the utility, enter:

/opt/Navisphere/bin/naviinittoolcli and any of the command lineswitches in Using the command line initialization utility, page 28.

Starting the initialization utility on an ESX Server 3.x or 2.5 host from the CD

To start the text-based or command line version of the initializationutility from the CD, do the following:

1. On ESX Server, log in to the root account.

2. In the server’s drive, insert the server support CD, which shippedwith the storage system or the upgrade kit (for AX4-5 series or AXseries systems upgrading to Navisphere Manager).

3. If you are running the initialization utility on an ESX Server 3.0 (orlater) Service Console, open the TCP/IP port 2162 (outgoing) andport 2163 (incoming).


These ports are used by the initialization utility and the defaultfirewall settings on the ESX Server 3.0 (or later) Service Consoleblock these ports. The initialization utility will not functionproperly if these TCP/IP ports are closed.

To open the TCI/IP ports:

a. Log in as root.

b. Enter the command:esxcfg-firewall -o port,protocol,direction,applicationwhere:port is the port number. For the initializationutility the port numbers are 2162 and 2163.protocol is udpdirection is in for incoming is out for outgoingapplication is naviInitTool for the initialization utility.

4. From a console window, mount the CD-ROM drive by enteringthe following command:

mount /mnt/cdrom

5. Change to the CD-ROM directory by entering the followingcommand:

cd /mnt/cdrom

6. Run the Navisphere Storage System Initialization Utility:

cd linux

7. Depending on which version of the initialization utility you want tostart and run from the CD, enter the appropriate command:

Text-based version — ./naviinittoolcli


23

Command line version — ./naviinittoolcli and any of the commandline switches in Using the command line initialization utility, page 28.

Starting the initialization utility on a Linux virtual machine from the CD


1. On the server, log in to the root account.


3. From a console window, mount the CD-ROM drive by enteringthe following command:

mount /mnt/cdrom

4. Change to the CD-ROM directory by entering the followingcommand:

cd /mnt/cdrom

5. Navigate to the Linux directory:

cd Linux


Text-based version — ./naviinittoolcli

Command line version — ./naviinittoolcli and any of the commandline switches in Using the command line initialization utility, page 28.

Starting the initialization utility on a Solaris virtual machine

To start the text-based version of the utility, enter:

/opt/Navisphere/bin/naviinittool

To start the command line version of the utility, enter:


/opt/Navisphere/bin/naviinittool and any of the command lineswitches in Using the command line initialization utility, page 28.

Starting the initialization utility on a Solaris virtual machine from the CD



2. Navigate to the Solaris directory:

cd /cdrom/cxseries/solaris


Text-based version — ./naviinittool

Command line version — ./naviinittool and any of the commandline switches in Using the command line initialization utility, page 28.

Starting the initialization utility UI on a Windows virtual machine

To start the UI version of the initialization utility from the server,select Start > Programs > EMC > Navisphere > Navisphere StorageSystem Initialization or Start > All Programs > EMC > Navisphere> Navisphere Storage System Initialization.

Starting the text-based or command line initialization utility on a Windows virtualmachine

To start the text-based version, at a command prompt enter cdC:\Program Files\EMC\Navisphere Storage System InitializationWizard or cd C:\Program Files (x86)\EMC\Navisphere StorageSystem Initialization Wizard; then enter NaviInitToolCLI.exe.

To start the command line version, at a command prompt enter cdC:\Program Files\EMC\Navisphere Storage System InitializationWizard or cd C:\Program Files (x86)\EMC\Navisphere StorageSystem Initialization Wizard; then enter ./naviinittoolcli and any


25

of the command line switches in Using the command line initializationutility, page 28.

Starting the initialization utility on a Windows virtual machine from the CD

1. Log in to the Windows server as the administrator or someone whohas administrative privileges.

2. In the server’s drive, insert the server support CD, which shippedwith the storage system or the upgrade kit (for AX4-5 series or AXseries systems upgrading to Navisphere Manager). The serversupport menu opens. If you do not see the server support menu,follow these steps to open it:


Start > Run




3. From the main menu select Run Products from CD. The RUNPRODUCTS page opens.

4. To start the utility, select Navisphere Storage System InitializationUtility.

Using the UI version of the initialization utility on a Windows virtual machine

After you start the utility, it automatically scans the subnet forsupported storage systems. When this storage-system discoveryoperation is complete, the utility lists, by hardware serial number,all uninitialized and initialized storage systems it found. Thestorage-system serial number is on a blue label located on the SPEchassis behind the front bezel.The hardware serial number is on a bluelabel on the rear of the chassis.The hardware serial number is on ahanging tag at the rear of the storage system.

If the discovery operation did not find the storage system youare installing, verify that the storage system’s management portsare properly cabled to the LAN on which the server resides. Themanagement ports and the server must both reside on the same subnet.


Proceed through the wizard screens, providing information whererequired. For more information about completing the wizard, clickHelp in the wizard’s menu bar.

For a CX4 and CX3 series storage systemsIf you entered an SP IP address for the first time or changed an SP IPaddress, the utility reboots the storage system, and the SP fault light onthe back of each SP starts blinking. The reboot takes several minutesto complete. When it has completed, the SP fault light (LEDs) on eachSP stops blinking and remains off.

For an AX4-5 series storage systemIf you entered an SP IP address for the first time or changed an SP IPaddress, the utility reboots the storage system, and green lights flash toindicate activity. The reboot takes 5 to 6 minutes to complete. Whenit has completed, the power button on each SP remains solid/steadygreen.

For an AX series storage systemIf you entered an SP IP address for the first time or changed an SP IPaddress, the utility reboots the storage system and the SP boot/faultlight on the back of each SP starts blinking. The reboot takes severalminutes to complete. When it has completed, the SP boot/fault light oneach SP stops blinking and remains off.

Using the text-based initialization utility on an ESX Server 2.5 or 3.x host or a Linux orSolaris virtual machine

After you start the utility, it automatically scans the subnet forsupported storage systems. When this storage-system discoveryoperation is complete, the utility lists, by hardware serial number, alluninitialized and initialized storage systems it found. The hardwareserial number for CX4 series storage systems is on a hanging tag at therear of the storage system.The hardware serial number for CX3 andCX series storage systems is on a blue label located on the SPE chassisbehind the front bezel.The hardware serial number for AX4-5 and AXseries storage systems is on a blue label on the rear of the chassis.

If the storage system you are installing was not discovered, verify thecable connections between the storage system and the host runningthe utility.

Use the information in the “Storage-System Management Ports”worksheet from the storage-system configuration planning guide,


planning worksheets document, or the administration worksheet, andfollow the instructions on the screen to change the storage system’sname, to set the network parameters for the storage-system 10/100management ports, and to set the storage system’s management useraccount settings.

For a CX4 or CX3 series storage systemIf you entered an SP IP address for the first time or changed an SP IPaddress, the utility reboots the storage system, and the SP fault light onthe back of each SP starts blinking. The reboot takes several minutesto complete. When it is completed, the SP fault light (LEDs) on eachSP stops blinking and remains off.

For an AX4-5 series storage systemIf you entered an SP IP address for the first time or changed an SPIP address, the utility reboots the storage system, and green activitylights flash. The reboot takes 5 to 6 minutes to complete. When it hascompleted, the power button on each SP remains solid/steady green.

For an AX series storage systemIf you entered an SP IP address for the first time or changed an SP IPaddress, the utility reboots the storage system and the SP Boot/Faultlight on the back of each SP starts blinking. The reboot takes severalminutes to complete. When it is completed, the SP Boot/Fault light oneach SP stops blinking and remains off.

Using the command line initialization utility

After you start the command line version of the initialization utility,use any of the switches below with the naviinittoolcli command (ESXServer 3.x or 2.5 host or a Linux or Windows virtual machine) or thenaviinittool command (Solaris virtual machine).

eula [-language language]

discover [-all] [-xml]

configure –serial serialnumber [-file filename] [–ipaspAIpaddress|–sphosta spAhostname] [-ipb spBIpaddress|–sphostb spBhostname] [–mask subnetmask] [–gateway gatewayaddress][-user username] [–password password] [–storagename storageName][-ipv6mode |automatic|disable| [manual [-globalprefix prefix[-ipv6gateway ipv6gateway]] [ -help]

where:


eula

Displays the EMC end-user license agreement (EULA) in the specified language.

-language language The default language is English.Currently, the only valid languageis English.

discover

Discovers and displays a list of partially initialized storage systems.

-all Discovers and displays a list ofinitialized and partially initializedstorage systems.

-xml Specifies that the output is in xmlformat.


configure

Specifies the network parameters for the specified storage system.

-serial serialnumber Specifies the serial number ofthe storage system you want toinitialize.

-file filename Specifies the name of the filethat will store all the networkparameters.

-ipa spAipaddress |-sphosta spAhostname Specifies the IP address of SP A,or the server name for SP A for thespecified storage system.

-ipb spBipaddress |-sphostb spBhostname Specifies the IP address of SP B,or the server name for SP B for thespecified storage system.

-mask subnetmask Specifies the subnet mask for thespecified storage system.

-gateway gateway Specifies the gateway for thespecified storage system.

-user username Specifies the storage-system loginusername.

-password password Specifies the storage-system loginpassword.

-storagename storagename Specifies the name for the specifiedstorage system.

-help Displays the help screen and doesnot start the initialization process

-ipv6mode automatic | disable |[manual –globalprefix prefix–ipv6gateway ipv6gateway]

Specifies the configuration type forthe IPv6 network. Refer to the IPv6configuration type table below fordetails. IPv6 is supported with CX4series systems only.


Table 3 IPv6 parameter values based on IPv6 configuration type (CX4 seriessystems only)

Existing configuration type(What you see when you open the

initialization utility)

New configuration type(What you see after changing the configuration type)

Disabled Auto Manual

Link Local: TBD*

Global IP: TBD*

GlobalPrefix:

Blank/editable

Disabled All IPv6 parameteers areblank and grayed out.IPv4 will be used

All IPv6parametersare set toTBD*

Gateway: blank/editable

Link Local: visible**

Global IP: visible**

GlobalPrefix:

visible/editable**

Auto Current IPv6 parameters arevisible but not editable.

All IPv6 parametersare blank andgrayed out *IPv4 will be used

Gateway: visible/editable**

Link Local: visible

Global IP: visible

GlobalPrefix:

visible/ed-itable

Manual

Gateway: visible/ed-itable

All IPv6 parametersare blank andgrayed out * IPv4will be used

Current IPv6Link Localparameter isvisible. Allothers are setto TBD **

* After changing the configuration type from Disabled to Auto or Manual, or from Auto or Manual to Disabled, the new values will be setafter the automatic reboot of the storage system. After the reboot completes, open the initialization utility again to view the new IPv6 values.** After changing the configuration type from Manual to Auto or from Auto to Manual, a reboot is not required.


31

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 version 6.22.20or later of the server utility either before or after you install the hostagent. The registration feature of the server utility will be disabledand the host agent will be used to register the server’s NICs or iSCSIHBAs to the storage system.

Prior to version 6.22.20 of the server utility, you could not install the host agentand server utility on the same server. However, you could install them ondifferent 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.

If you have an AX4-5 series or AX series storage system runningNavisphere Express, you can only install the server utility. The hostagent is supported only on CX4 series, CX3 series, CX series, AX4-5series, and AX series storage systems running Navisphere Manager.

If you have VMware ESX Server with native multipathing software installed,the server utility will not display all paths to the storage system. However, atleast one path to the storage system will always be displayed.

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

Depending on the version of the server utility, some of the features listed inTable 4 may not be available.


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

AX4–5 series and AX series storage systemsYes – LUN mapping information is displayed in theManager UI next to the LUN icon, or with the CLI usingthe -lunmapinfo command. In Navisphere Express thisinformation is displayed in the Manage Virtual Disks page.Note: The text Manually Registered appears next to thehostname icon in the Manager UI indicating that the host agent wasnot used to register this server.CX4 series, CX3 series, and CX series storage systemsNo – LUN mapping information is not sent to the storage system. Onlythe server’s name, ID, and IP address are sent to the storage system.Note: The text Manually Registered appears next to thehostname icon in the Manager UI indicating that the host agent wasnot used to register this server.

Runs automatically tosend information to thestorage system.

Yes – No user interaction isrequired.

AX4–5 series and AX series storage systemsNo – You must manually update the information by startingthe utility or you can create a script to run the utility. Since you runthe server utility on demand, you have more control as to how oftenor when the utility is executed.CX4 series, CX3 series, and CX series storage systemsNo – You must manually update the information by starting the utilityor you can create a script to run the utility. Since you run the serverutility on demand, you have more control as to how often or when theutility is executed.

Provides high-availability(HA) validation.

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

AX4–5 series and AX series storage systemsCurrently not supported.CX4 series, CX3 series, and CX series storage systemsYes – The HA validation feature verifies that failover software isinstalled on the server and that working paths exist between theserver and each SP in the storage system.

Requires networkconnectivity to the storagesystem.

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

AX4–5 series and AX series storage systemsNo – LUN mapping information is sent through a data pathto the storage system.CX4 series, CX3 series, and CX series storage systemsNo – LUN mapping information is not sent to the storage system.Note that if you are using the server utility to upload a high availabilityreport to the storage system, you must have network connectivity.


33

Function Host agent Server utility

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

AX4–5 series and AX series storage systemsNo – You can run the server utility from the CD. However,we recommend that you install it on the server.CX4 series, CX3 series, and CX series storage systemsNo – You can run the server utility from the CD. However, werecommend that you install it on the server.

Note: If you install the host agent and then version 6.22.20 or later of the server utility, the server utility’s registration service feature willnot be installed. Prior to version 6.22.20 of the server utility, you could not install the host agent and server utility on the same server.


Requirements for the host agent, server utility, and CLI

The host agent and server utility are not supported with ESX Server 3i.

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

Run a supported version of the VMware ESX Server operatingsystem.

For Fibre Channel connections, have the EMC CLARiiONsupported HBA hardware and driver installed.

Be connected to at least one SP (two SPs for high-availability) ineach storage system either directly or through a switch or hub. EachSP must have an IP connection.

For the host agent and CLI only - Be on a TCP/IP network connectedto at least one SP (two SPs for high-availability) in the storagesystem. The TCP/IP network connection allows the server to sendLUN mapping information to the storage system and it allowsNavisphere Manager or CLI to communicate with the storagesystem 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 server whose browser you will use to access Manager 6.X.

any Windows Server 2008, 2003, or Windows 2000 serverrunning Storage Management Server software.

any AIX, HP-UX, Linux, VMware ESX Server, NetWare, Solaris,Windows Server 2003, or Windows 2000 server 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.


35

For information about the specific revisions of the server operating systemand the storage-system FLARE and Access Logix software that are requiredfor your version of the host agent, see the release notes for the host agenton the EMC Powerlink website. To access this website, see Finding currentinformation, page 9.


Installing or removing the Navisphere Host Agent and CLI

You can install both the host agent and CLI, or you can install themseparately. If you will install both, install the host agent first.

You can install version 6.26.7 or later of the host agent on a Windowsvirtual machine that has the iSCSI initiator software installed. Refer tothe ESX Server compatibility guides for supported Windows and iSCSIinitiator versions.

If you have an ESX Server 3.x or 2.5 host you can install the host agenton the ESX Server. The host agent is not supported on an ESX Server 3ihost because the ESX Server 3i has no Service Console to install or runthis software program. Registration of the CLARiiON storage systemhappens automatically when the ESX Server 3i reboots or when yourescan the host bus adapters. Therefore, manual registration is notnecessary.

You can install Navisphere CLI on either an ESX Server 3.x or 2.5 hostor a virtual machine. If you have an ESX Server 3i host, you can onlyinstall the Navisphere CLI on the virtual machine.

To modify an existing host agent configuration refer to the next section.

If you want to install the host agent and use some of the features in the serverutility, see Determining whether to install the host agent or server utility , page 32.

Installing the host agent and CLI on an ESX Server 2.5 or 3.x host

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 (CX4 series, CX3series, CX series, and AX4-5 series) or on the storage-system supportwebsite (AX series). You can also install the software from the serversupport CD; however, the CD may not contain the most recent versionfor your configuration.

1. On the VMware ESX Server Service Console, log in to the rootaccount.


37

2. At a command line prompt, look for an existing host agent and CLIpackage by entering one of the following commands:

rpm -qa | grep navi

If an earlier version of the naviagentcli or naviagent softwarepackage is listed, you must remove it before installing the new hostagent and CLI package.

3. To download the software for CX4 series, CX3 series, CX series, orAX4–5 series storage systems with Navisphere Manager, do thefollowing:


b. Select the appropriate Navisphere Host Agent/CLI version todownload and select the option to save the zip file to your server.


unzip Navi_Agent_CLI_Linux-version.zip


4. To download the software for AX series storage systems withNavisphere Manager, do the following:


b. Navigate to the Navisphere Host Agent/CLI download andselect the option to save the software to your server.



a. In the server’s drive, insert the server support CD that shippedwith your storage system or the upgrade kit (for AX4-5 series orAX series systems upgrading to Navisphere Manager).




c. From the CD directory, change to the Linux directory byentering the following command:

cd linux


6. Install both the host agent and CLI on the ESX Server ServiceConsole:

./ESX_install.sh naviagentcli

If you are installing the host agent and CLI on an ESX Server 3.0 orlater, the script prompts you to open the TCP/IP ports used by thehost agent and CLI. The default firewall settings on the ESX Server3.0 Service Console block these ports.

7. Enter y for the script to open the ports listed, or enter n to manuallyopen the ports after the installation (see Manually opening theTCP/IP ports at the end of this procedure).

If these ports are not opened, the host agent and CLI will not functionproperly.

8. When the installation is complete, the script copies theESX_uninstall.sh file to the /opt/Navipshere/bin directory for useduring the uninstall process.

9. If you installed the host agent/CLI from the server support CD,unmount the CD, and then remove the CD from the CD drive.

10. Verify that Navisphere Agent and/or CLI are installed by using therpm -qa | grep navi command.

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


39

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

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 otherthan root, for subsequent agent restarts to use the correctpath to the agentID.txt file, set the environment variable


EV_AGENTID_DIRECTORY to point to the directory whereyou created agentID.txt.

e. If a HostIdFile.txt file is present in the /var/log/ directory, deleteor rename it.

f. Reboot the VMware ESX server.

g. Start the host agent.

h. Once the host agent has restarted, verify that the host agent isusing the IP address that is entered in the agentID.txt file. Todo this, view the new HostIdFile.txt file, which is located in the/var/log/ directory. You should see the IP address that is enteredin the agentID.txt file.


To manually open the TCP/IP ports listed in Table 5, which are usedby the host agent and CLI on an ESX Server 3.0 or later, follow theprocedure below.

Table 5 TCP/IP ports for host agent and CLI

Application name Ports used Direction

Host agent 6389 Incoming

6389, 443, 2163 OutgoingCLI

6390, 6391, 6392 Incoming





For example, esxcfg-firewall -o 6389,tcp,in,naviagent

where:


41

port is the port number (see Table 5).

protocol is tcp


application is naviagent for the host agent and navicli for the CLI.

Installing the Navisphere CLI on an ESX Server 3.x or 2.5 host

EMC recommends that you install the most recent version of theNavisphere CLI software that is appropriate for your configuration.You can download the most recent version from the software downloadpage on the Powerlink website (CX4 series, CX3 series, CX series, andAX4-5 series) or on the storage-system support website (AX series).You can also install the software from the server support CD (anystorage system); however, the CD may not contain the most recentversion for your configuration.


2. At the command line prompt, look for any existing CLI by typing:

rpm -qi navicli




b. Select the appropriate Navisphere CLI version to download andselect the option to save the zip file to your server.


unzip Linux_navicli-version.zip




4. To download the software on AX series storage systems withNavisphere Manager, do the following:






b. From a console window, enter the following command:

mount /mnt/cdrom

The CD can also be mounted from either the Gnome or KDE desktop.

c. Change to the CD directory by entering the following command:

cd /mnt/cdrom

d. Change to the Linux directory by entering the followingcommand:

cd linux


6. Install the CLI on the ESX Server Service Console:

./ESX_install.sh navicli

7. If you are installing the CLI on an ESX Server 3.0 or later, the scriptprompts you to open the TCP/IP ports used by the CLI. The defaultfirewall settings on the ESX Server 3.0 Service Console block theseports.


43

8. Enter y for the script to open the ports listed, or enter n to manuallyopen the ports after the installation (see Manually opening theTCP/IP ports, page 44).

If these ports are not opened, the CLI will not function properly.

When the installation is complete, the script copies theESX_uninstall.sh file to the /opt/Navipshere/bin directory for useduring the uninstall process.

9. If you installed the Navisphere CLI from the server support CD,unmount the CD, and then remove the CD from the CD drive.


To manually open the TCP/IP ports listed in Table 6, which are used bythe CLI on an ESX Server 3.0 or later, follow the procedure below.

Table 6 TCP/IP ports for CLI



6390, 6391, 6392 Incoming





For example, esxcfg-firewall -o 6389,tcp,out,navicli

where:



protocol is tcp


application is navicli for the Navisphere CLI.

Installing the Navisphere CLI on a Linux virtual machine


1. On the Linux virtual machine, log in to the root account.

If you are installing the CLI on an ESX Server 3.x or 2.5 host, refer to theESX section.

2. At the command line prompt, look for any existing CLI by typing:

rpm -qi navicli







45




d. Enter the following command to install the CLI package:

rpm -ivh navicli-version-build.noarch.rpm

where version and build are the version and build number for theNavisphere CLI.

The system displays the word navicli and a series of pound(#) signs. When the installation is complete, the system promptreappears.








rpm -ivh navicli-version-build.noarch.rpm

where version and build are the version and build number for theNavisphere CLI.





b. From a console window, enter the following command:

mount /mnt/cdrom

The CD can also be mounted from either the Gnome or KDE desktop.

c. Change to the CD directory by entering the following command:

cd /mnt/cdrom

d. Change to the Linux directory by entering the followingcommand:

cd linux


e. Enter the following command to install the CLI package:

rpm -ivh navicli.noarch.rpm


f. If the File Manager window is open to the /mnt/cdrom directory,you need to close this window first before attempting tounmount the CD. Then enter the following commands:

cdumount /mnt/cdrom


47

6. Verify that Navisphere CLI is installed by using the rpm -qa | morecommand.

Modifying user login scripts

To use navicli commands at the root prompt without typing a leading./ before the commands (for example, ./navicli getagent), you mustmodify the $PATH environment variable in the user login script.

Follow the steps listed below to modify the environment variablePATH:

1. Add /opt/Navisphere/bin to $PATH:

PATH=$PATH:/opt/Navisphere/bin export PATH

To verify the path enter:

echo $PATH

2. Set the environment variable $PATH for all login sessions:

a. For the user profile, edit $HOME/.bash_profile

b. For the user startup script, edit $HOME/.bashrc

3. If you are setting up a new server, go to Running the Navisphere HostAgent , page 67. If you are just upgrading the host agent or CLI onan existing system, you have finished the upgrade.

Installing the Navisphere CLI on a Solaris virtual machine

This section applies to version 6.26 or later of the Navisphere CLIsoftware package.


1. At the Solaris server, log in as superuser (root).


2. If an earlier version of the CLI is installed on the server, remove itbefore continuing.

To verify if a previous version is installed, enter the pkginfo |grep HOSTcommand.





unzip Sun-NAVICLI-version.zip



pkgadd -d NAVICLI.pkg





unzip Sun-NAVICLI-version.zip




49


pkgadd -d NAVICLI.pkg



b. In a shell, enter the following command:

cd /cdrom/cdrom0/solaris pkgadd -d /solaris/NAVICLI.pkg

6. Select the packages that you want to install by doing one of thefollowing:

Enter 1 (to install classic CLI)

Enter 2 (to install secure CLI)

Enter All (to install both)

7. When the installation of the CLI is complete, a successful messageis displayed.

8. If you installed the CLI from the server support CD, wheninstallation is complete, exit the /cdrom directory by entering cd /,and then remove the CD from the server’s CD drive.

Any user who can access the management station can change or delete theNavisphere files you just installed. You may want to change permissionson these files to restrict access to them.

9. Verify the installation by entering the command pkginfo -l | grepNAVI*.

Depending on what you installed, some of the following may bedisplayed:

NAVICLI: Navisphere Disk Array Management Tool (CLI)

NAVISCLI: Navisphere Disk Array Management Tool (CLI)

Installing the Navisphere Host Agent on a Windows virtual machine

To install the host agent on a Windows virtual machine, you mustinstall version 6.26.7 or later and the virtual machine must have iSCSI


initiator software installed. Prior to version 6.26.7, you could notinstall the host agent on a Windows virtual machine. Refer to the ESXServer compatibility guides for supported Windows and iSCSI initiatorversions.

EMC recommends that you install the most recent version ofthe Navisphere Host Agent software that is appropriate for yourconfiguration. You can download the most recent version from thesoftware download page on the Powerlink website (CX4 series, CX3series, CX series, and AX4-5 series) or on the storage-system supportwebsite (AX series). You can also install the software from the serversupport CD (any storage system); however, the CD may not containthe most recent version for your configuration.

1. Log in to the Windows server as the administrator or a user whohas administrative privileges.

2. If you are running a version prior to 6.26 of the host agent, youmust remove it before continuing with the installation.



b. Select the appropriate Navisphere Host Agent version todownload and select the option to save the software to yourserver.








51





Start > Run




b. From the main menu select Install Products on Server.

The INSTALL PRODUCTS page opens.

c. Select Navisphere Host Agent.

6. Follow the instructions on the installation screens to install theNavisphere Host Agent.

The Navisphere Host Agent software is installed on the Windowsserver. If you selected the default destination folder, the softwareis installed in the C:\Program Files\EMC\Navisphere Agentdirectory on Windows Server 2008 and 2003 (32-bit) or Windows2000 systems, or the C:\Program Files (x86)\EMC\NavisphereAgent directory on Windows Server 2008 and 2003 (64-bit) systems.

Once the Navisphere Host Agent installation is complete, theInitialize Privileged User List dialog box is displayed.

7. In the Initialize Privileged User List dialog box, perform one ofthe following:

If the Config File field contains a file entry, then a hostagent configuration file already exists on the server from aprevious agent installation. Select Use Existing File to use thisconfiguration file or select Browse to use a different file. Thehost agent configuration file contains a list of login names forthis server. Only users logged in as listed in the Privileged UserList can send CLI commands to the storage system.


If the Config File field does not contain a file entry, a hostagent configuration file does not exist on the server. SelectCreate/Overwrite File and browse to the agent.config file. Youwill then need to add users to the Privileged User List (loginnames for this server). Only users logged in as listed in thePrivileged User List can send CLI commands to the storagesystem.

There must be at least one entry in the Privileged User List or an errormessage will appear.

To add a user to the list

Click Add to open the Add Privileged User dialog box.

In the Add Privileged User dialog box, under User Name, enterthe person’s account username, for example, Administrator.

Under System Name, enter the name of the host runningNavisphere Manager (for example, Host4) and click OK.

To remove a privileged user from the listSelect the privileged username, and click Remove.

8. Click OK to save the new privileged user list and/or the newconfiguration file.

The program saves the host agent configuration file with the newprivileged user entries and starts the host agent.

9. In the Navisphere Agent Setup dialog box, click Finish.

A command line window opens indicating that the host agentservice is starting.

10. If you are prompted to reboot the server, click Yes.

If you do not reboot before you run the Microsoft iSCSI SoftwareInitiator, the NIC initiators cannot log in to the storage system.

11. If you updated the host agent and were using event monitor,restore the event monitor configuration from a previously copiedNavimon.cfg file:

a. Stop the agent:


53

At the Windows server, log in as the administrator or theequivalent.

Open the Services pane.

From the desktop, right-click My Computer and selectManage > Services and Applications > Services.or

Select Start > Administrative Tools > ComputerManagement > Services and Applications > Services.

The Services pane opens.

In the Services pane, right-click Navisphere Agent andselect Stop.

If asked to confirm your request to stop the agent service,click Yes, and close the Services pane or dialog box.

b. Move or copy the saved Navimon.cfg to the real Navimon.cfgfile.

c. Start the agent:

At the Windows server, log in as the administrator or theequivalent.

Open the Services pane.




In the Services pane, right-click Navisphere Agent andselect Start.

If you want the host agent to start automatically at systemstartup:

Right-click Navisphere Agent and select Properties.

The Navisphere Agent Properties dialog box opens.

Select the General tab.

In Startup Type, select Automatic.


The host agent will now start automatically at systemstartup.

Close Computer Management.

It may take a few minutes for the host agent to start if eitherapplications are using the storage system or the SP event logis large and the host agent configuration file is not set up.

12. Click Done to exit the installation wizard.

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

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, create afile named agentID.txt (case sensitive). Save this file by doingone of the following:

Set the EV_AGENTID_DIRECTORY environmentalvariable to the location you want to save the agentID.txtfile. The Navisphere Host Agent will then look for theagentID.txt file in the location you specified.

If you do not specify a location in the EV_AGENTID_DI-RECTORY environmental variable, Navisphere Host Agentwill look for the agentID.txt file in the location specifiedby the registry entry HKEY_LOCAL_MACHINE\SOFT-WARE\EMC\Agent\1.0\ConfigPath. This location isusually C:\Program Files\emc\ Navisphere Agent.

If EV_AGENTID_DIRECTORY or HKEY_LOCAL_MA-CHINE\SOFTWARE\EMC\Agent\1.0\ConfigPath doesnot exist, create the agentID.txt file in the C:\ directory.

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


55

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

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. Restart the host agent.

e. Once the host agent has restarted, verify that the host agent isusing the correct IP address that is entered in the agentID.txtfile by doing one of the following:

In Navisphere Manager, verify that the host IP address is thesame as the IP address that you entered in the agentID.txtfile. If the address is the same, the agentID.txt file isconfigured correctly.

View the new HostIdFile.txt file. You should see the IPaddress that is entered in the agentID.txt file.

14. If you installed the host agent from the CD, close the server supportmenu by selecting Main Menu and then Exit. You can now removethe CD from the server’s CD drive.


15. Verify that Navisphere Agent is installed using the Add/RemovePrograms dialog box.

Installing Navisphere CLI on a Windows virtual machine


1. Log in to the Windows virtual machine as the administrator orsomeone who has administrative privileges.

2. If an earlier version of the CLI is already installed, you must removeit before continuing with the installation. The installation programdoes not let you overwrite an existing version.



b. Select the appropriate Navisphere Host Agent/CLI version todownload and select the option to save the software to yourserver.




b. Navigate to the Navisphere CLI download and select the optionto save the software to your server.




57





Start > Run




b. From the main menu select Install Products on Server. TheINSTALL PRODUCTS page opens.

c. Select Navisphere CLI.

If you did not remove a previously installed version of the CLI, amessage appears indicating that the software discovered a previousversion and cannot continue with the installation until it is removed.

6. Follow the instructions on the installation screens to install theNavisphere CLI.


You have installed the Navisphere CLI software on a Windowsserver. If you selected the default destination folder, the software isinstalled in one of the following locations:

On Windows Server 2008 and 2003 (32-bit) or Windows 2000systems

C:\Program Files\EMC\Navisphere CLI

On Windows Server 2008 and 2003 (64-bit) systems

C:\Program Files (x86)\EMC\Navisphere CLI

8. If you installed the Navisphere CLI from the CD, close the serversupport menu by selecting Main Menu and then Exit. You can nowremove the CD from the server’s CD drive.


9. Verify that Navisphere CLI is installed using the Add/RemovePrograms dialog box.

Removing the host agent and CLI on an ESX Server 3.x or 2.5 host

To remove just the Navisphere CLI, refer to the next section.

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




3. Enter the following command to remove the host agent and CLI:

./ESX_uninstall.sh naviagentcli

If you are removing the host agent and CLI on an ESX Server 3.0or later, the script notifies you about the TCP/IP ports that wereopened by the installation of the host agent and CLI.

4. If no other software on the ESX Service Console is using the portslisted in Table 7, we recommend that you close these ports byfollowing the procedure below.

Table 7 TCP/IP ports for host agent and CLI


Host agent 6389 Incoming


6390, 6391, 6392 Incoming

a. Log in as root.

b. Enter the command:



59

where:


protocol is tcp

direction is the traffic direction. Use in for incoming traffic or out foroutgoing traffic.

application is naviagent for the host agent and navicli for the NavisphereCLI.

Removing the Navisphere CLI on an ESX Server 3.x or 2.5 host




3. Enter the following command to remove the CLI:

./ESX_uninstall.sh navicli

The system removes all files required to run Navisphere CLI.

4. If you are removing the CLI on an ESX Server 3.0 or later, thescript notifies you about the TCP/IP ports that were opened bythe installation of the CLI.

If no other software on the Service Console is using the ports listedin Table 8, we recommend that you close these ports as describedbelow.

Table 8 TCP/IP ports for CLI



6390, 6391, 6392 Incoming

a. Log in as root.

b. Enter the command:



where:


protocol is tcp

direction is the traffic direction. Use in for incoming traffic or out foroutgoing traffic.

application is navicli for the Navisphere CLI.

Removing the Navisphere CLI on a Linux virtual machine

1. Log in to the Linux virtual machine as root or as a member of anadministrative group.

2. Open a terminal window and enter the following command toremove CLI:

rpm -e navicli

The system removes all files required to run Navisphere CLI.

Removing Navisphere CLI on a Solaris virtual machine

1. Log in to the server as superuser (root) and start the X WindowSystem if it is not started.

2. At the command line in an X Window terminalemulator, enter the following commands:/etc/init.d/agent stopcd pkgrm package

where:

package is NAVICLI (this name must be capitalized)

3. Enter y and y to remove the program.


61

The removal program removes only the files that were installed from theinstallation CD. Files that the CLI creates (for example, log files) are notremoved.

Removing the host agent on a Windows virtual machine

To avoid losing site-specific information, copy the host agent configuration file(agent.config) and the event monitor configuration file (Navimon.cfg) to a safelocation or rename it before removing any Navisphere software.

1. On the Windows server running the host agent that you want toremove, log in as the administrator or the equivalent.

2. Stop the host agent service as follows:

a. Open the Services pane.




b. Stop the host agent:

In the Services pane, right-click Navisphere Agent andselect Stop.

If asked to confirm your request to stop the agent service,click Yes.

c. Close the Services pane.



5. Select Navisphere Host Agent and click Change/Remove orUninstall/Change.


6. When asked to remove the entire Navisphere Agent directory,click Yes or No. If you select Yes, the software removes the entireNavisphere agent directory, which includes the agent.configand Navimon.cfg files. This file contains all site-specific agentconfigurations from the server. If you click Yes, a confirmationdialog opens asking if you want to proceed.

7. Click Yes, to proceed and remove the entire Navisphere agentdirectory or click No, to cancel the removal of this directory.

Removing Navisphere CLI on a Windows virtual machine

1. On the Windows virtual machine that is running the CLI that youwant to remove, log in as the administrator or the equivalent.



4. Select Navisphere CLI and click Change/Remove orUninstall/Change.



63

Configuring the Navisphere Host Agent

Before you can use the Navisphere CLI navicli register command toconfigure your storage system, you must make sure the host agentconfiguration file includes a privileged user, as described in Addingprivileged users, page 64.

The pathname of the host agent configuration file is /etc/Navisphere/agent.con-fig.

If you are configuring a legacy storage system, refer to revision A03 ofthis guide.

A legacy system is an FC series storage system that is not running storagemanagement server software.

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.

Saving the host agent configuration file

1. Save the host agent configuration file.


2. If you have finished adding information to the host agentconfiguration file, stop and restart the host agent by entering thefollowing commands:

/etc/init.d/naviagent stop/etc/init.d/naviagent start


65

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.


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

The host agent starts automatically when you bring the server up toinit level 3. When you first start the host agent, look at the system logfor the server’s operating system to make sure the agent started and nodevice errors occurred. The system log is located in /var/log/messages.

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 allevents, it may take a few minutes for the host agent to start.

Starting the host agent on an ESX 2.5 or 3.x host

Log in as root and enter this command:

/etc/init.d/naviagent start

Stopping the host agent on an ESX 2.5 or 3.x host

Log in as root and enter this command:

/etc/init.d/naviagent stop

Starting the host agent on a Windows virtual machine

1. At the Windows virtual machine, log in as the administrator orthe equivalent.

2. Open the Services pane.



67

Select Start > Administrative Tools > Computer Management> Services and Applications > Services.


3. In the Services pane, right-click Navisphere Agent and select Start.

4. If you want the host agent to start automatically at system startup:

a. Right-click Navisphere Agent and select Properties.

The Navisphere Agent Properties dialog box opens.

b. Select the General tab.

c. In Startup Type, select Automatic.

5. Close Computer Management.

The host agent will now start automatically at system startup.

It may take a few minutes for the host agent to start when:

Applications are using the storage system, or

The SP event log is large and the host agent configuration file isnot set up.

Stopping the host agent on a Windows virtual machine

1. At the Windows virtual machine, log in as the administrator orthe equivalent.

2. Open the Services pane.


Select Start > Administrative Tools > Computer Management> Services and Applications > Services.


3. In the Services pane, right-click Navisphere Agent and select Stop.

4. If asked to confirm your request to stop the agent service, click Yes,and close the Services pane or dialog box.

Testing the host agent connections

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


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

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:naviseccli |navicli [-d device]| -h hostname port-list -hba

You cannot specify both the –d switch and –h switch.

where:

[-d device] is the device name for the storage system (onlysupported with legacy systems).

-h hostname is the IP address of the SP.

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


69

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

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/log/agent.log. Systemevents are logged in /var/log/messages.


Installing and removing the Navisphere Server Utility

This section describes how to install the Navisphere Server Utility.

If you have an ESX Server 3.x or 2.5 host you can install the serverutility on the ESX Server. The server utility is not supported on anESX Server 3i host because the ESX Server 3i has no Service Consoleto install or run this software program. Registration of the CLARiiONstorage system happens automatically when the ESX Server 3ireboots or when you rescan the host bus adapters. Therefore, manualregistration is not necessary.

If you have the iSCSI initiator software installed on a Windows virtualmachine, you can install version 6.26.7 or later of the server utility .Refer to the ESX Server compatibility guides for supported Windowsand iSCSI initiator versions.

If you want to generate a high availability report of your ESX Server,you can install version 6.28 or later of the Windows server utility onany supported Windows server.

Installing the Navisphere Server Utility on an ESX Server 2.5 or 3.x host

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 (CX4 series, CX3series, CX series, and AX4-5 series) or on the storage-system supportwebsite (AX series). You can also install the software from the serversupport CD (any storage system); however, the CD may not containthe most recent version for your configuration.


2. At the command line prompt, look for any existing server utility:

rpm -qi naviserverutil

If you have an AX100 series storage system and a previous version was notdetected with the command above, try entering rpm -qi axnaviserverutil.


71

3. If an earlier version of the software has been installed, you mustremove it before continuing.

rpm -e naviserverutil



b. Select the appropriate Navisphere Server Utility version todownload and select the option to save the zip file to your server.


unzip Linux_HOSTUTIL-version.zip


d. Install the Navisphere Server Utility on the server:

rpm -ivh naviserverutil.platform.rpm

If you are upgrading the utility on the server, use -U in place of -ivh.

The installation process adds a line to the /etc/rc.d/rc.local filethat starts the server utility on reboot, provided root has executepermission for the /etc/rc.d/rc.local file.



b. Select the appropriate Navisphere Server Utility version todownload and select the option to save the zip file to your server.


unzip Linux_HOSTUTIL-version.zip



where version is the version listed in the filename youdownloaded.









cd linux







73

e. Remove the CD from the server’s CD drive.

Installing the Navisphere Server Utility on a Windows server or Windows virtual machine

If you will generate a high-availability report of your ESX Server, install version6.28 or later of the Navisphere Server Utility on any supported Windows server.

To install the server utility on a Windows virtual machine, you mustinstall version 6.26.7 or later and the virtual machine must have iSCSIinitiator software installed. Prior to version 6.26.7, you could not installthe server utility on a Windows virtual machine. Refer to the ESXServer compatibility guides for supported Windows and iSCSI initiatorversions.

IMPORTANT

To discover Microsoft iSCSI initiators on a Windows 64–bit operatingsystem, you must run version 6.28 or later (Windows Server 2008 hosts)or version 6.26 or later (Windows Server 2003 hosts) of the NavisphereServer 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 (CX4 series, CX3series, CX series, and AX4-5 series) or on the storage-system supportwebsite (AX series). You can also install the software from the serversupport CD (any storage system); however, the CD may not containthe most recent version for your configuration.

If you are running PowerPath 4.6 or later, you must install version 6.22.20 orlater of the Navisphere Server Utility. If your server is connected only to anAX100 series storage system running Navisphere Server Utility version 2.19 orearlier, and you are adding an AX150 series storage system, you must installthe version that shipped with your AX150 series system.





b. Select the appropriate Navisphere Server Utility version todownload and select the option to save the software to yourserver.




b. Navigate to the Navisphere Server Utility download and selectthe option to save the software to your server.



a. In the server’s drive, insert the server support CD, whichshipped with the storage system or the upgrade kit (forupgrading AX4-5 series or AX series systems to NavisphereManager).



Start > Run




b. Select your language, if prompted for it.

c. From the main menu, click Install Products on Server.

d. From the Install Products menu, click Navisphere ServerUtility to open the installation wizard.


75


5. Follow the instructions on the installation screens and accept allthe defaults.

If you do not have the host agent installed, do not disable the registrationservice feature (it is enabled by default). The registration service featureautomatically registers the server’s NICs or HBAs with the storage systemafter the installation and updates server information to the storage systemwhenever the server configuration changes (for example, when you mountnew volumes or create new partitions).

If you have the host agent installed and you are installing version 6.22.20or later of the server utility, the server utility’s registration service featurewill be disabled by default and we recommend that you do not installit. Prior to version 6.22.20 of the server utility, you could not install bothapplications on the same server.

6. If you are installing the server utility on a server that is using theMicrosoft iSCSI initiator to connect to the storage system, selectYes when prompted.


8. If you installed the server utility from the CD, close the serversupport menu by selecting Main Menu and then Exit. You can nowremove the CD from the server’s CD drive.

Removing the server utility on an ESX Server 3.x or 2.5 host

1. Log in to the VMware ESX Server 3.x or 2.5 host or Linux virtualmachine as root or as a member of an administrative group.

2. Open a terminal window and, depending on which version of theserver utility is installed, enter the appropriate command to removethe server utility:

rpm -e naviserverutilorrpm -e axnaviserverutil


To determine which version is installed, enter rpm -qi naviserverutil orrpm -qi axnaviserverutil. If the utility is installed, information about theutility is displayed.

Removing the server utility on a Windows server or a Windows virtual machine

1. On the Windows server or a Windows virtual machine running theserver utility that you want to remove, log in as the administratoror the equivalent.



4. Select Navisphere Server Utility and click Change/Remove orUninstall/Change.


If you are prompted to save HAV report files, and you click No, all the highavailability report files generated will be deleted.


77

Running the Navisphere Server Utility

This section describes how to start and use the server utility. You canrun the server utility from the server or from the server support CD.

Starting the Navisphere Server Utility on an ESX Server 2.5 or 3.x host

1. Open a console window.

2. Navigate to the Navisphere bin directory and run the server utility:

/opt/Navisphere/bin/naviserverutilcli

Starting the Navisphere Server Utility on an ESX Server 2.5 or 3.x host from the CD

1. On the ESX Server or a Linux virtual machine, log in to the rootaccount.


3. From a console window, mount the CD using the mount commandfor your operating system version.

4. From the CD directory, change to the Linux directory by enteringthe following command:

cd linux


5. Run the server utility:

./naviserverutilcli

Starting the Navisphere Server Utility on a or a Windows virtual machine

1. Run the Navisphere Server Utility by selecting Start > Programs> EMC > Navisphere > Navisphere Server Utility or Start > AllPrograms > EMC > Navisphere > Navisphere Server Utility.

2. Select your language, if prompted for it.


A text-based version of the utility is installed automatically when youinstall the utility. To start the text-based version, at a command promptenter cd C:\Program Files\EMC\Navisphere Server Utility or cdC:\Program Files (x86)\EMC\Navisphere Server Utility, then enterNaviServerUtilCLI.exe.

Starting the Navisphere Server Utility on a or a Windows virtual machine from the CD



The server support menu opens. If you do not see the serversupport menu, open it:


Start > Run




3. From the main menu select Run Products from CD.

The RUN PRODUCTS page opens.

4. Select Navisphere Server Utility.

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


79

IMPORTANTTo generate a high availability report of your ESX Server, you must useversion 6.28 or later of the Windows server utility on any supportedWindows server.

For information on using the Windows Navisphere Server Utility togenerate a high availability report, including how to perform manualchecks after generating a high availability report, click Help from theutility’s Help menu or if you are running the text-based version of theutility, select Start > Programs> EMC > Navisphere > NavisphereServer Utility Help or Start > All Programs > EMC > Navisphere >Navisphere Server Utility Help. To generate a high availability reportusing the command line, continue to the next section.

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 using the command line

The high availability option determines if the server is configured forhigh availability by verifying that the server has at least one connectionpath to each storage-system SP, and that PowerPath or some otherfailover software, such as VMware native. The utility will not detectany other native failover software, such as Windows Server 2008.

To generate a high availability report using the command line, open acommand window and enter one of the following commands:

cd C:\Program Files\EMC\Navisphere Server Utilityorcd C:\Program Files (x86)\EMC\Navisphere Server Utility,then enter naviserverutilcli hav.

After the verification, the utility generates a summary report andsaves it to the server. If you issue the -upload switch with thenaviserverutilcli hav command, the utility also sends the report to thespecified storage system.

Generate a high-availability report to:

check the status of a server.


prepare for a software installation on a storage system.

For AX4 systems only — Use the -upload switch to upload the HA reportto the storage system only if you will use the Navisphere Software Assistantto install new software. We strongly recommend that you use the SoftwareAssistant, and not the -ndu install command to update your software. The-ndu install command does not perform the same pre-install validation checksas the Software Assistant. The Software Assistant is included in the NavisphereService Taskbar.

Checking the status of a serverTo use the command line to periodically check the high-availabilitystatus of a server, issue the naviserverutilcli hav[-directory | -doutputdirectory] -esx ipaddress -virtualcenter ipaddress -vmuser username-vmpassword password command.

where:

-directory | -doutputdirectory

Specifies the directory to which you want to deposit the report onthe 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.If the server utility is installed on your server and you specify a directory,the directory you specify will override the server utility’s installationdirectory.

-esx ipaddress Specifies the IP address of the VMware ESX Server’s environment forwhich you want to generate a report.

-virtualcenteripaddress

Specifies the IP address of the Virtual Center. You must also specify the-esx ipaddress for which you want to generate a report.

-vmuserusername

Specifies the username for the ESX Server or Virtual Center.

-vmpasswordpassword

Specifies the password for the ESX Server or Virtual Center.

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 in which you installed the utility:


81

naviserverutilcli hav -upload -ip IPaddress |-hIPaddress|network_name -user|-u username -password|-puserpassword -scope|-s scopelevel -secfilepath securityfilepath -port443|2163 [-directory | -d outputdirectory] -esx ipaddress-virtualcenter ipaddress -vmuser username -vmpassword password

where:

-ip IPaddress Specifies the IP address of an SP on the storage system to which youwill upload the report. You cannot use this switch in conjunction withthe -h switch.

-h IPaddress |network_name

Specifies the IP address or the network name of an SP on the storagesystem to which you will upload the report. You cannot use this switchin conjunction with the -ip switch.

-user | -uusername

Specifies the login name for the storage system. You must use this switchin conjunction with the -password | -p and -scope | -s switches. Youcannot use this switch in conjunction with the -secfilepath switch.

-password | -puserpassword

Specifies the password required for access to the storage system. Youmust use this switch in conjunction with the -user | -u and -scope | -sswitches. You cannot use this switch in conjunction with the -secfilepathswitch.

-scope | -sscopelevel

Specifies the level of access this username and password has to thestorage system: 0 = global; 1 = local; 2 = LDAP. You must use this switchin conjunction with the -user | -u and -password | -p switches. Youcannot use this switch in conjunction with the -secfilepath switch.

-secfilepathsecurityfilepath

Searches the security file for the specified IP address. If the utility doesnot find the specified IP address, then the utility will use the default entryin the security file.A security file is required to run this switch. For information on how tocreate a security file, refer to the EMC Navisphere Command Line (CLI)Reference guide.


You cannot use this switch in conjunction with the -user | -u, -password |-p , and -scope | -s switches.

-port 443 | 2163 Specifies the Navisphere Management Server port number. The defaultis 443.

-directory | -doutputdirectory

Specifies the directory to which you want to deposit the report onthe 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.If the server utility is installed on your server and you specify a directory,the directory you specify will override the server utility’s installationdirectory.

-esx ipaddress Specifies the IP address of the VMware ESX Server’s environment forwhich you want to generate a report.

-virtualcenteripaddress

Specifies the IP address of the Virtual Center. You must also specify the-esx ipaddress for which you want to generate a report.

-vmuserusername

Specifies the username for the ESX Server or Virtual Center.

-vmpasswordpassword

Specifies the password for the ESX Server or Virtual Center.

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 supportedaccording to the EMC E-Lab™ Interoperability Navigator andsupport matrices.

This tool does not verify that you are running supported switch firmware,nor that you are using redundant switches (recommended).

Upgrading storage–system software — If you are about to performa storage-system online software 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 hardwarethat are supported and interoperable according to EMC E-LabInteroperability Navigator and support matrices.


83

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 Admhost Utility

The Admhost Utility is supported only on the following MicrosoftWindows platforms: Windows Server 2008, Windows Server 2003, orWindows 2000.

You can only install the Admhost Utility on the VMware WindowsVirtual Machine.

For the supported versions of these operating systems, see the Admhost ReleaseNotes.

Installing the Admhost Utility on a Windows virtual machine

EMC recommends that you install the most recent version of theAdmhost Utility software that is appropriate for your configuration.You can download the most recent version from the software downloadpage on the Powerlink website (CX4 series, CX3 series, CX series, andAX4-5 series) or on the storage-system support website (AX series).You can also install the software from the server support CD (anystorage system); however, the CD may not contain the most recentversion for your configuration.

1. Log in to the Windows Virtual Machine as the administrator or assomeone who has administrator privileges.

2. You cannot install admhost over an existing version. If you thinkadmhost is already installed, see Removing the Admhost Utility on aWindows virtual machine, page 87.



b. Select the appropriate Admhost Utility version to downloadand select the option to save the software to your server.

c. In the folder where you saved the software, double-click theexecutable file to start the installation wizard.



85



b. Select the appropriate Admhost Utility version to downloadand select the option to save the software to your server.

c. In the folder where you saved the software, double-click theexecutable file to start the installation wizard.


a. In the server’s drive, insert the server support CD that shippedwith your storage system or the upgrade kit (for upgradingAX4-5 series or AX series systems to Navisphere Manager).


From the Windows taskbar, select:Start > Run






c. Select Admhost Utility and then select the Windows operatingsystem running on the server. The following three options areavailable:

Admhost Windows Server 2008

Admhost Windows Server 2003

Admhost Windows 2000

6. Follow the instructions on the installation screens to install theAdmhost Utility.

7. When the installation is complete, click Finish to exit the wizard.

You have installed the admhost software. If you selected thedefault destination folder, admhost is installed in the directory


C:\Program Files\EMC\Navisphere Admhost or C:\ProgramFiles (x86)\EMC\Navisphere Admhost.

8. If you installed the Admhost Utility from the CD, close the serversupport menu by selecting Main Menu and then Exit. You can nowremove the CD from the server’s CD drive.

Removing the Admhost Utility on a Windows virtual machine



3. Select Navisphere Admhost and click Change/Remove orUninstall/Change.



87

Running the Admhost Utility

The following table lists the admhost commands and describes theirfunction in SAN Copy sessions.

Table 9 Admhost functions and descriptions

Function Description Syntax and examples

admhostlun_activate

The admhost lun_activatecommand scans the bus for newdevices and assigns a drive letterto all Symmetrix and CLARiiONdevices that do not already haveone.Use the -l and -d switches toscan the bus for new devices andassign a drive letter to a devicethat has a specific world widename (WWN). This commanddoes not assign drive letters toany other devices.If admhost_activate is used andno new devices are found, anddrive letters are already assignedto the CLARiiON and Symmetrixlogical units, admhost reports anerror message.

admhost lun_activate [-llun_wwn -d driveletter][-h]where-l lun_wwn specifies the WWNof the LUN to which you want toassign a drive letter (requires the-d switch).-d driveletter specifies the driveletter you want to assign to thespecified LUN (requires the -lswitch).-h displays the help message.If the admhost lun_activatecommand activates more thanone device, the drive letter isassigned to the first device in thelist.



admhostlun_deactivate

The admhost lun_deactivatecommand attempts to takedevices offline and make theminaccessible to the operatingsystem. The command deletesthe drive letter and dismounts thedevice.Use the admhost lun_activatecommand to bring the volumeback online.

admhost lun_deactivate -oobjectName [-t object type][-h]where-o objectName specifies the driveletter of the device you want todeactivate. If you specify thedevice name, admhost finds thedevice, deletes its drive letter,dismounts it, and then takes thedevice offline.-t object_type is an optionalswitch that specifies the objecttype (device or driveletter) of thedevice you want to deactivate.-h displays the help message.

admhost lun_flush The admhost lun_flushcommand flushes all write cachedata, for the specified device(object_name) to disk.

admhost lun_flush [-h] -oobject_name [-t object_typedevice|driveletter]where-h displays a help message.-o object_name specifies thename or drive letter of the deviceyou want to flush.-t object_type is an optionalswitch that specifies the objecttype (device or driveletter) of thedevice you want to flush.If you specify the devicename, admhost identifies thecorresponding device and driveletter.


89


admhost lun_list The admhost lun_list commandlists the drive letters and WWNsfor all server devices.

admhost lun_list [-h] [-llun_wwn] [-d object_name] [-aoutput_style]where-h displays a help message.-l lun_wwn specifies the WWN ofthe device you want to list.-d object_name specifies thedrive letter or name of the deviceyou want to list.-a output_style specifies analternative output style for thelist output. The default style liststhe drive letter and WWN for thelogical unit. The -a switch letsyou specify physicaldrive as theoutput style.

admhost help This admhost help commanddisplays the syntax for eachadmhost command and theversion number of the AdmhostUtility.Output for admhost helpcommand is shown below:Revision number:

V1.1.0.0.0 - 0

Valid operations

include: lun_flush,

lun_activate,

lun_deactivate,

lun_list, and

help. Valid types

include: device and

driveletter.

admhost help


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.

You can only install the Admsnap Utility on the VMware VirtualMachine.

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.

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 a Linux virtual machine

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 (CX4 series, CX3 series, CX series, andAX4-5 series) or on the storage-system support website (AX series).You can also install the software from the server support CD (anystorage system); however, the CD may not contain the most recentversion for your configuration.

1. On the VMware Linux Virtual Machine, log in as root or as amember of an administrative group.

2. Open a terminal window and enter the following command to listany admsnap package that may be currently installed:

rpm -qi admsnap

3. Examine the list for an earlier version of admsnap.


91

If an earlier version is installed, remove it as described in Removingthe Admsnap Utility on a Linux Virtual Machine, page 100.



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


unzip admsnap_version.zip


d. Install admsnap using the rpm -ivh command (Red Hat) or theyast command (SuSe).

Red Hat Linux users — use the following command:

rpm -ivh admsnap-version-build.platform.rpm

where version and build are the version number and the buildnumber of the Admsnap Utility and platform is your Linuxplatform number.

SuSe Linux users — use the following command:

yast -l SuSe_admsnap-version-build.platform.rpm


The software is installed in the directory /usr/admsnap withthe following files:

/usr/admsnap/admsnap/usr/admsnap/man/man1/admsnap.1/usr/admsnap/readme

5. To install the software for AX series storage systems withNavisphere Manager, do the following:




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




d. Install admsnap using the rpm -ivh command (Red Hat) or theyast command (SuSe).


rpm -ivh admsnap-version-build.platform.rpm



yast -i SuSe_admsnap-version-build.platform.rpm

where version and build are the version number and the buildnumber of the Admsnap Utility and platform is your Linuxplatform number (see the Red Hat examples above).




a. In the server’s drive, insert the server support CD that shippedwith your storage system or the upgrade kit (for upgradingAX4-5 series or AX series systems to Navisphere Manager).



93


cd linux


d. List the filenames on the CD:

ls

You will see four admsnap rpm packages for different platforms.These rpm packages are for the Intel 64-bit platform (ia64), AMDprocessor-based Linux or Intel Xeon-based Linux platform(x86_64), Intel 32-bit Linux platform (i386), and SuSE Linuxplatform (ia64).

e. Install admsnap using the rpm -ivh command (Red Hat) or theyast command (SuSe).


rpm -ivh admsnap.platform.rpm

where platform is your Linux platform number.

For example:

rpm -ivh admsnap.i386rpmrpm -ivh admsnap.ia64.rpmrpm -ivh admsnap.x86_64.rpm


yast -i admsnap.platform.rpm

where platform is your Linux platform number (see the RedHat examples above).




f. Unmount (umount) the CD file system by entering:cdumount /dev/cdrom

g. Remove the CD from its drive.

You have installed admsnap on a Linux server.

7. Verify that the correct version of admsnap is installed by enteringthe following command:

/usr/admsnap/admsnap help

This command displays a message about the help command, whichincludes the revision number of the installed admsnap software.

8. Configure MANPATH to access the Linux man pages. Editthe /etc/man.config file by adding the following lines:MANPATH /usr/admsnap/man

9. Configure sg devices by using the MAKEDEV utility. Forinformation on how to use the MAKEDEV utility, refer to theMAKEDEV man pages.

Installing the Admsnap Utility on a Solaris virtual machine


1. Log in to the Solaris virtual machine as a superuser, such as root.

2. If a previous revision is installed, remove it as described in Removingthe Admsnap Utility on a Solaris virtual machine, page 100.




95






d. Load the admsnap package:

/usr/sbin/pkgadd -d ADMSNAP.pkg







d. Load the admsnap package:

/usr/sbin/pkgadd -d ADMSNAP.pkg


a. In the server’s drive, insert the server support CD that shippedwith your storage system or your upgrade kit (for upgradingAX4-5 series or AX series systems to Navisphere Manager).

The CD is mounted automatically on /cdrom/admsnap, whichis linked to /cdrom/cdrom0.


If the CD does not mount automatically, then mount the CDusing the mount/dev/cdrom command.

The File Manager Admsnap window appears withADMSNAP.pkg displayed.

b. Load admsnap from the CD by typing:

/usr/sbin/pkgadd —/cdrom/cdrom0/solaris/ADMSNAP.pkg

The following messages appear:The following packages are available:1 ADMSNAP Navisphere Admsnap

(sparc) X.X.X.X.XSelect package(s)...to process (or "all" to process allpackages). (default: all) [?, ??, q]:

6. When prompted, enter y to install the admsnap package and yagain to continue the installation.

The installation script executes, listing the files installed, and oncompletion, displays the message: Installation of <ADMSNAP>

was successful.

The information described in the admsnap help and man pages does notapply to servers connected to an AX100 series storage system. Use only theadmsnap commands described in this document.

7. Use the pkginfo command to verify the installation. Enter/usr/sbin/pkginfo-1 ADMSNAP.

Messages similar to the following appear:

PKGINST: ADMSNAPNAME ...CATEGORY: applicationVERSION X.X.X.X.XPSTAMP: Navisphere: 2000:10:28:13:03:01INSTDATE: November 20 2000 13:03STATUS: Completely installedFILES: xxxxxxx

xxxxxxxx xxxxxx


97

When you see the error-free pkginfo message, admsnap softwareinstallation is complete. The software is installed in the directory/usr/admsnap.

8. Unmount the CD by entering the unmount/dev/cdrom command.

9. Remove the CD from its drive.

Installing the Admsnap Utility on a Windows virtual machine


1. Log in to the Windows virtual machine as the administrator or assomeone who has administrative privileges.

2. If admsnap is already installed, refer to Removing the AdmsnapUtility on a Windows virtual machine, page 100.

The remove step is needed because the installation program will not letyou install admsnap over an existing revision.



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

c. In the folder where you saved the software, double-click theexecutable file for your operating system to start the installationwizard.





b. Navigate to the Admsnap Utility download section and selectthe option to save the software to your server.

c. In the folder where you saved the software, double-click theexecutable file for your operating system to start the installationwizard.


a. In the server’s drive, insert the server support CD, whichshipped with the storage system or the upgrade kit (forupgrading AX4-5 series or AX series systems to NavisphereManager).


From the Windows taskbar, select:Start > Run






c. Select Admsnap Utility and then select the Windows operatingsystem running on the server. The following options areavailable:

Admsnap Windows Server 2008

Admsnap Windows Server 2003

Admsnap Windows 2000

6. Follow the instructions on the installation screens to install theAdmsnap Utility.

7. When the installation is complete, click Finish to exit the wizard.

If you selected the default destination folder, admsnap is installedin one of the following:


99

On Windows Server 2008 and 2003 (64-bit) systems

C:\Program Files (x86)\EMC\ Navisphere Admsnap

On Windows Server 2008 and 2003 (32-bit) or Windows 2000systems

C:\Program Files\EMC\Navisphere Admsnap

8. If you installed the Admsnap Utility from the CD, close the serversupport menu by selecting Main Menu and then Exit. You can nowremove the CD from the server’s CD drive.

Removing the Admsnap Utility on a Linux Virtual Machine

1. Log in to the VMware Linux Virtual Machine as root or as a memberof an administrative group.

2. Open a terminal window and enter the following commandto list any admsnap package that is currently installed:rpm -q admsnap

3. To remove the previous version of the admsnap software, enter:

rpm -e namewhere name is the admsnap program name displayedby the command in step 2.

Removing the Admsnap Utility on a Solaris virtual machine

1. Log in to the server as a superuser, such as root.

2. Remove the existing admsnap software by entering:

pkgrm ADMSNAP (uppercase ADMSNAP)

Then confirm, if prompted, by entering y and y. If admsnap is notinstalled, you will receive a Not found error message; continue.

Removing the Admsnap Utility on a Windows virtual machine




3. Select Navisphere Admsnap and click Change/Remove orUninstall/Change.



101

Running the Admsnap Utility

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


Copyright© 2006–2008 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 regulatory document for your product line, go to the TechnicalDocumentation and Advisories section on EMC Powerlink.

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.


103

clariion server support products for vmware esx servers ... · emc clariion server support products...

Documents