clariion server support products for linux and vmware esx ... · system initialization utility,...

1

This document explains how to install the EMC® Navisphere® Storage System Initialization Utility, Host Agent, Navisphere Server Utility, CLI (Command Line Interface), and admsnap software on a server running the Linux or VMware ESX Server operating system. All CLARiiON server-based applications are supported on servers attached to CX3 UltraScale™ series, CX-series, and AX-series storage systems running Navisphere Manager. Only the Navisphere Storage System Initialization Utility and the Navisphere Server Utility are supported on AX-series storage systems running Navisphere Express.

Note: This document uses “CX3-series” to refer to CX3-20, CX3-20c, CX3-40, CX3-40c, and CX3-80 storage systems and "CX-series" to refer to CX200, CX300, CX300i, CX400, CX500, CX500i, CX600, and CX700 storage systems.

Topics include:◆ About EMC Navisphere software...................................................... 2◆ Finding current information ............................................................... 7◆ Installing and removing the Navisphere Initialization Utility ...... 8◆ Determining whether to install the Host Agent or Server Utility 14◆ Requirements for the Host Agent, CLI, or Server Utility ............. 16◆ Installing, configuring, and removing the Host Agent and CLI . 17◆ Installing, removing, and using the Navisphere Server Utility... 46◆ Installing and removing the Admsnap Utility............................... 52

EMC CLARiiONServer Support Products for Linux and

VMware ESX Server

Installation GuideP/N 300-002-041

REV A08

July 19, 2006

2 EMC CLARiiON Server Support Products for Linux and VMware ESX Server Installation Guide

About EMC Navisphere software

About EMC Navisphere softwareThe following EMC server-based software is available on the server support CD that shipped with your storage system or your upgrade kit (for AX-series systems upgrading to Navisphere Manager):

◆ Navisphere Storage System Initialization Utility

◆ Navisphere Host Agent

◆ Navisphere Server Utility

◆ Admsnap Utility

◆ Navisphere CLI

Navisphere Storage System Initialization UtilityYou must initialize the storage system in order to register the server HBAs and NICs with the storage system and have access to the storage system's data.

For CX3-series and CX-series Fibre Channel storage systems, use the utility to discover storage systems, and set network parameters (IP address, subnet mask, and default gateway). In addition, for CX3-series storage systems with iSCSI data ports, use the utility to set network parameters for the these data ports.

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

For AX-series storage systems, use the utility to discover storage systems, set network parameters (IP address, subnet mask, and default gateway), and create management user accounts. In addition, for AX150 iSCSI storage systems, use the utility to set network parameters for the storage system's iSCSI data ports.

Note: The Navisphere Initialization Utility runs on servers attached to CX3-series, CX700, CX500-series, CX300-series, and AX-series storage systems. CX3-series systems must be running FLARE OE 03.22.xxx.5.yyy or later. CX700, CX500-series, CX300-series, and AX100-series systems must be running FLARE OE 02.16.xxx.5.yyy or later. AX150-series systems must be running FLARE 02.20.xxx.5.yyy or later.

EMC CLARiiON Server Support Products for Linux and VMware ESX Server Installation Guide 3


Navisphere Host AgentThe Navisphere Host Agent registers the server’s HBA (host bus adapter) with the attached storage system when the Host Agent service starts. This action sends the initiator records for each HBA to the storage system. Initiator records are used to control access to storage-system data. For legacy storage systems, the Host Agent will send the initiator records only if Access Logix™ software is installed.

The Host Agent can then retrieve information from the storage system automatically at startup or when requested by Manager or CLI.

The Host Agent can also:

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

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

◆ Retrieve LUN World Wide Name (WWN) and capacity information from Symmetrix® storage systems.

Note: The Host Agent runs on servers attached to CX3-series, CX-series, and AX-series storage systems that have been upgraded to Navisphere Manager, that is, that have the Navisphere Manager enabler installed.



Navisphere Server UtilitySimilar to the Navisphere Host Agent, the Navisphere Server Utility registers the server’s host bus adapter (HBA) or network interface card (NIC) with the attached storage system; however, unlike the Host Agent, the Server Utility on a Linux or ESX Server does not:

◆ Send LUN mapping information back to a CX3-series or CX-series storage system. This information will not be displayed in the Manager UI or CLI. To see LUN mapping information in the Manager UI or CLI for a CX3-series or CX-series storage system, you must use the Host Agent instead of the Server Utility.

Note: LUN mapping information is sent to AX-series storage systems. In Navisphere Manager, this information is displayed in the Manager UI or with the CLI -lunmapinfo command. In Navisphere Express, this information is displayed on the Manage Virtual Disks page.

◆ Automatically retrieve information from storage systems, and forward it to Navisphere Manager or Navisphere Express. With the Server Utility, you must manually update the information by starting the utility or you can create a script to run the utility.

◆ Require network connectivity to the storage system.

◆ Require that you install the utility; you can run it from the CD. However, we recommend that you install it on the server.

With the Server Utility you can perform the functions listed below.

Note: If you want to install the Host Agent and use some of the features in the Server Utility, see “Determining whether to install the Host Agent or Server Utility” on page 14.

◆ Fibre Channel connections can determine if the server is configured for high availability (HA) by verifying that the server has at least one connection path to each storage-system SP, and that PowerPath® or some other failover software is running.

◆ AX-series storage systems running Navisphere Express can use the utility to manage snapshots. If you are managing your AX-series storage system with Navisphere Manager or if you have a CX3-series or CX-series storage system, you must use SnapView and the admsnap utility to manage snapshots. For



more information on SnapView and admsnap, refer to the EMC SnapView for Navisphere Administrator’s Guide and the EMC SnapView Command Line Interfaces Reference.

Note: The Server Utility runs on servers attached to CX3-series, CX-series, and AX-series storage systems. CX3-series systems must be running FLARE OE 03.22.xxx.5.yyy or later. CX200, CX300-series, CX400, CX500-series, CX600, CX700, and AX100-series systems must be running FLARE OE 02.16.xxx.5.yyy or later. AX150-series systems must be running FLARE OE 02.20.xxx.5.yyy or later.

Admsnap UtilityThe Admsnap Utility is an executable program that you can run interactively or by a script to manage SnapView clones and snapshots. The Admsnap Utility resides on the servers connected to the 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

Note: The Admsnap Utility runs on servers attached to CX3-series, CX-series, and AX-series storage systems that have been upgraded to Navisphere Manager, that is, that have the Navisphere Manager enabler installed. If you upgraded to Navisphere Manager and want to manage snapshots, you must use the SnapView software and the Admsnap Utility. For more information on SnapView and admsnap, refer to the EMC SnapView for Navisphere Administrator’s Guide and the EMC SnapView Command Line Interfaces Reference.



Navisphere CLI The CLI complements or can be used as an alternative to Manager. It provides a command line interface for storage-system management, including storage provisioning, status and configuration information retrieval, and control. You can use the CLI to automate management functions through shell scripts and batch files. CLI commands for many functions are server-based and are provided with the Host Agent. The remaining CLI commands are web-based and are provided with software that runs in the storage-system SPs. Navisphere CLI includes the Secure (on supported operating systems), Classic, and Java CLI functionalities. For more information, refer to the EMC Navisphere Command Line Interface (CLI) Reference Guide.

Note: The Navisphere CLI runs on servers attached to CX3-series, CX-series, and AX-series storage systems that have been upgraded to Navisphere Manager, that is, that have the Navisphere Manager enabler installed.


Finding current information

Finding current informationThe most up-to-date information about the CLARiiON® server software for Linux and VMware is posted on the EMC Powerlink™ website. We recommend that you download the latest information before you install any server software.

To access EMC Powerlink, use the following link:

http://Powerlink.EMC.com

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

◆ Navisphere Host Agent/CLI and Utilities Release Notes

◆ EMC SnapView for Navisphere Administrator’s Guide (P/N 069001180)

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

◆ The latest version of this guide that is applicable to your software revision. For information on FC4700 storage systems, refer to revision A05 of this guide.

◆ EMC Installation Roadmap for CX3-series, CX-series, AX-Series, and FC-Series Storage Systems, which provides a checklist of the tasks that you must complete to install your storage system in a storage area network (SAN) or direct attach configuration.

◆ For the most current management and security content for CX3-series or CX-series and supported AX-series storage systems, refer to the EMC Navisphere Manager Administrator's Guide (P/N 300-003-511). For FC-series and C-series management and security content, refer to the most recent versions of EMC Navisphere Manager Administrator's Guide (P/N 069001125) and EMC Navisphere Security Domains, Multi-Domains and User Accounts Administrator’s Guide (P/N 069001124).

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

http://powerlink.emc.com


Installing and removing the Navisphere Initialization Utility

Installing and removing the Navisphere Initialization UtilityEMC recommends that you install the Navisphere Storage System Initialization Utility on the host; however, you can run the utility from the server support CD, as described in “Running the Storage System Initialization Utility” on page 11.

PrerequisitesTo use the Storage System Initialization Utility on a Linux host to initialize a storage system, the client or host must meet the following requirements:

◆ Run a supported version of the Linux operating system.

◆ Be connected to the same subnet as the 10/100 management ports of the storage system that you want to initialize. This host may also be a server with Fibre Channel or iSCSI connections to the storage system.

Installing the Storage System Initialization Utility on an ESX Server 1. On the VMware ESX Server Service Console, log in to the root

account.

2. In the server’s drive, insert the server support CD that shipped with your storage system or your upgrade kit (for AX-series systems upgrading to Navisphere Manager).

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

mount /mnt/cdrom

Note: The CD-ROM can also be mounted from either the Gnome or KDE desktop.

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

cd /mnt/cdrom

5. Change to the Linux directory by entering the following command: cd linux

This directory contains the Linux install packages.



6. Install the Navisphere Storage System Initialization Utility on the ESX Server Service Console:

./ESX_install.sh naviinttool

If you are installing the Initialization Utility on an ESX Server 3.0 or later, the script prompts you to open the TCP/IP ports used by the Initialization Utility. The default firewall settings on the ESX Server 3.0 Service Console block these ports.

7. Enter y for the script to open the ports listed. or Enter n, to manually open the ports after the installation (see step 10).

Note: If these ports are not opened, the Initialization Utility will not function properly.

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

9. Remove the CD from the CD drive.

10. To manually open TCP/IP port 2162 (outgoing) and port 2163 (incoming), which are used by the Initialization Utility on an ESX Server 3.0 or later, do the following:

a. Log in as root.

b. Enter the command:

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

where:

port is the port number. For the Initialization Utility, the port numbers are 2162 and 2163.

protocol is udp

direction is in for incomingis out for outgoing

application is naviInitTool for the Storage System Initialization Utility



Installing the Storage System Initialization Utility on a Linux Server1. On the Linux server or VMware Linux Virtual Machine, log in to

the root account.

Note: If you are installing the Initialization Utility on an ESX Server, refer to the previous section.



mount /mnt/cdrom



cd /mnt/cdrom



6. Install the Navisphere Storage System Initialization Utility on the server:

rpm -i naviinittool.rpm

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

7. When the installation is complete, remove the CD from the CD drive.



Running the Storage System Initialization UtilityYou can run the Storage System Initialization Utility from the server on which you installed it or from the server support CD.

Running the utility from the serverOpen a console window and enter:

/opt/Navisphere/bin/naviinittoolcli

Running the utility from the CD1. On the Linux server, VMware Linux Virtual Machine, or ESX

Server, log in to the root account.

2. If you are running the Initialization Utility on an ESX Server 3.0 (or later) Service Console, open the TCP/IP port 2162 (outgoing) and port 2163 (incoming). These ports are used by the Initialization Utility and the default firewall settings on the ESX Server 3.0 (or later) Service Console block these ports.

Note: The Initialization Utility will not function properly if the TCP/IP ports it uses are closed.

a. Log in as root.


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

where:



protocol is udp





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

mount /mnt/cdrom


cd /mnt/cdrom

6. Navigate to the Linux directory:

cd linux

7. Run the Navisphere Storage System Initialization Utility:

./naviinittoolcli



Removing the Storage System Initialization Utility on an ESX Server1. Log in to the VMware ESX Server Service Console as root or as a

member of an administrative group.

2. Navigate to the Navisphere bin directory:

cd /opt/Navisphere/bin

3. Enter the following command to remove the Storage System Initialization Utility:

./ESX_uninstall.sh naviinttool

4. If you are removing the Initialization Utility on an ESX Server 3.0 or later, the script notifies you about the TCP/IP ports that were opened by the installation of the Initialization Utility.

If no other software on the ESX Service Console is using the ports listed, we recommend that you close these ports by entering the following command:

esxcfg-firewall -c port,protocol,direction

where:

Removing the Storage System Initialization Utility on a Linux server1. Log in to the server as root or as a member of an administrative

group.

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

rpm -e naviinittool


protocol is udp




Determining whether to install the Host Agent or Server Utility

Determining whether to install the Host Agent or Server UtilityDepending on your application needs, you can install the Host Agent, Server Utility, or both on an attached Linux or ESX Server.

If you want to install both applications, you must install revision 6.22.20 or later of the Server Utility. The registration feature of the Server Utility will be disabled and the Host Agent will be used to register the server’s HBAs to the storage system.

Note: Prior to revision 6.22.20 of the Server Utility, you could not install the Host Agent and Server Utility on the same server; however, you could install them on different servers that were connected to the same storage system.

If you do not want to install both applications, but want to use some of the features available in the Server Utility, you may run the Server Utility from the server support CD.

If you have an AX-series storage system running Navisphere Express, you must install the Server Utility; the Host Agent is supported only on AX-series storage systems running Navisphere Manager.

Note: If you have VMware ESX Server with native multipathing software installed, the Server Utility will not always display all paths to the storage system. However, at least one path to the storage system will always be displayed.

Table 1 on page 15 describes the differences between the Host Agent and the Server Utility on a Linux or ESX Server attached to a CX3-series, CX-series, or AX-series storage system running Navisphere Manager.


Determining whether to install the Host Agent or Server Utility

Table 1 Differences between the Host Agent and the Server Utility

Function Host agent

Server Utility

AX series CX series

Pushes LUN mapping and OS information to the storage system.

Yes – LUN mapping information is displayed in the Navisphere Manager UI, next to the LUN icon, or with the CLI using the -lunmapinfo command.

Yes – LUN mapping information is displayed in the Navisphere Manager UI, next to the LUN icon, or with the CLI using the -lunmapinfo command. Note: The text Manually Registered appears next to the hostname icon in the Manager UI indicating that the Host Agent was not used to register this server.

No – LUN mapping information is not sent to the storage system. Only the host’s name, ID, and IP address are sent to the storage system. Note: The text Manually Registered appears next to the hostname icon in the Manager UI indicating that the Host Agent was not used to register this server.

Runs automatically to send information to the storage system.

Yes – No user interaction is required.

No – You must manually update the information by starting the utility or you can create a script to run the utility. Since you run the Server Utility on demand, you have more control as to how often or when the utility is executed.

No – You must manually update the information by starting the utility or you can create a script to run the utility. Since you run the Server Utility on demand, you have more control as to how often or when the utility is executed.

Provides high-availability (HA) validation

No – You can run the Server Utility’s HA validation feature from the CD without having to install the Server Utility.

Currently not supported. Yes – The HA validation feature verifiesthat failover software is installed on the server and that working paths exist between the server and each SP in the storage system.

Requires network connectivity to the storage system.

Yes – Network connectivity allows LUN mapping information to be available to the storage system.

No – LUN mapping information is sent through a data path to the storage system.

No – LUN mapping information is not sent to the storage system. Note: If you are using the Server Utility to upload a high-availabilty report to the storage system, you must have network connectivity.

Requires installation. Yes – You must install the Host Agent on the server.

No – You can run the Server Utility from the CD. However, we recommend that you install it on the server.

No – You can run the Server Utility from the CD. However, we recommend that you install it on the server.


Requirements for the Host Agent, CLI, or Server Utility

Requirements for the Host Agent, CLI, or Server UtilityTo run the Linux Host Agent or Server Utility, or the Linux or VMware CLI, your server must meet the following requirements:

◆ Run a supported version of the Linux operating system.

◆ Have the EMC CLARiiON supported HBA hardware and driver installed.

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

◆ For the Host Agent and CLI only – Be on a TCP/IP network connected to each SP in the storage system. The TCP/IP network connection allows the server to send LUN mapping information to the storage system and it allows Navisphere Manager or CLI to communicate with the storage system over the network.

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

Note: For information about the specific revisions of the server operating system and the storage-system FLARE and Access Logix software that are required for your revision of the Host Agent, see the release notes for the Host Agent on the EMC Powerlink website. To access this website, see “Finding current information” on page 7.


Installing, configuring, and removing the Host Agent and CLI

Installing, configuring, and removing the Host Agent and CLIYou can install both the Host Agent and CLI package (see page 18 for an ESX Server or page 20 for a Linux server) or just the CLI package (see page 21 for an ESX Server or page 23 for a Linux server).

Note: If you want to install the Host Agent and use some of the features in the Server Utility, see “Determining whether to install the Host Agent or Server Utility” on page 14.

You can install the Host Agent on a VMware ESX Server, but do not install the Host Agent on a VMware Linux Virtual Machine. You can install Navisphere CLI on the ESX Server or on the VMware Linux Virtual Machine.

To modify an existing Host Agent configuration or to remove the Host Agent and/or CLI, refer to the appropriate section below; otherwise, the installation will guide you through the initial configuration.

Modifing an existing Host Agent configuration

◆ Modifying user login scripts ....................................................... 25

◆ Configuring the Host Agent........................................................ 26

◆ Manually editing the Host Agent configuration file ............... 32

◆ Starting and stopping the Host Agent....................................... 41

◆ Host Agent status and error logging ......................................... 41

Removing the Host Agent and/or CLI

◆ Removing the Host Agent and CLI on an ESX Server ............ 42

◆ Removing the Host Agent and CLI on a Linux server............ 43

◆ Removing the CLI on an ESX Server ......................................... 44

◆ Removing the CLI on a Linux server ......................................... 45



Installing the Host Agent and CLI on an ESX Server1. On the VMware ESX Server Service Console, log in to the root

account.


3. From a console window, enter the following command to mount the CD-ROM:

mount /mnt/cdrom



cd /mnt/cdrom



6. Install the Host Agent and CLI on the ESX Server Service Console:

./ESX_install.sh naviagentcli

If you are installing the Host Agent and CLI on an ESX Server 3.0 or later, the script prompts you to open the TCP/IP ports used by the Host Agent and CLI. The default firewall settings on the ESX Server 3.0 Service Console block these ports.

7. Enter y for the script to open the ports listed,or enter n, to manually open the ports after the installation (see step 10).

Note: If these ports are not opened, the Host Agent and CLI will not function properly.





10. To manually open the TCP/IP ports listed in Table 2, which are used by the Host Agent and CLI on an ESX Server 3.0 or later, follow the procedure below.

a. Log in as root.

b. Enter the command:esxcfg-firewall -c port,protocol,direction

where:

Table 2 TCP/IP ports used by the Navisphere Host Agent and CLI applications

Application name Ports used Direction

Host Agent 6389 Incoming

CLI 6389, 443, 2163 Outgoing

6390, 6391, 6392 Incoming

port is the port number (see Table 2).

protocol is tcp


application is naviagent for the Host Agentis navicli for the CLI



Installing the Host Agent and CLI on a Linux server1. On the Linux server, log in to the root account.

Note: If you are installing the Host Agent and CLI on an ESX Server, refer to the previous section.


3. From a console window, enter the following command to mount the CD-ROM:

mount /mnt/cdrom


4. At a command line prompt, look for an existing Host Agent and CLI package by entering one of the following commands:

rpm -qa | grep navi

If a previous version of the naviagentcli or naviagent software package is not listed go to step 5.

If a previous version of the software package is listed, you must remove it before installing the new Host Agent and CLI package. To remove a previous version of the software package, refer to “Removing the Host Agent and CLI on a Linux server” on page 43.


cd /mnt/cdrom



7. Enter the following command to install both the Host Agent and CLI packages:

rpm -ivh naviagentcli.rpm



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

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

cd umount /mnt/cdrom

You have installed the Host Agent and CLI.

What next? Before you can use the Host Agent or CLI, you must modify the user login scripts and configure the Host Agent configuration file. Refer to “Modifying user login scripts” on page 25 and “Configuring the Host Agent” on page 26.

Installing the Navisphere CLI on an ESX Server1. On the VMware ESX Server Service Console, log in to the root

account.



mount /mnt/cdrom



cd /mnt/cdrom





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

./ESX_install.sh navicli

If you are installing the CLI on an ESX Server 3.0 or later, the script prompts you to open the TCP/IP ports used by the CLI. The default firewall settings on the ESX Server 3.0 Service Console block these ports.

7. Enter y for the script to open the ports listed,or enter n, to manually open the ports after the installation (see step 10).

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



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

a. Log in as root.



where:

Table 3 TCP/IP ports used by Navisphere CLI


CLI 6389, 443, 2163 Outgoing

6390, 6391, 6392 Incoming


protocol is tcp


application is navicli for the CLI



Installing the Navisphere CLI on a Linux server1. On the Linux server or VMware Linux Virtual Machine, log in to

the root account.

Note: If you are installing the CLI on an ESX Server, refer to the previous section.



mount /mnt/cdrom


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

rpm -qi navicli

If a previous version of the software has not been installed, the system will respond with the following message:

Package navicli is not installed

If you see the above message, go to step 6. If a previous version of the software has been installed, the system displays information about the existing CLI that is similar to the following:

Name: navicli Relocations: (not relocateable)Version: x.x.x.x.xx Vendor: EMC Corp.

Note: If a previous version is installed, you must remove it before installing a new CLI.

5. To remove a previous version of the software, refer to “Removing the Server Utility” on page 51.


cd /mnt/cdrom



7. Change to the Linux directory by entering the following command:

cd /linux


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

rpm -ivh navicli.rpm

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

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


You have installed the CLI.

What next? Before you can use the Storage Management Server software, you must modify the user login scripts and the Host Agent configuration file. Refer to “Modifying user login scripts” on page 25 and “Configuring the Host Agent” on page 26.



Modifying user login scriptsTo use navicli commands at the root prompt without typing a leading ./ before the commands (as, for example, ./navicli getagent), you must modify the user login script.

Follow the steps listed below to modify the environment variable PATH:

1. To set the environment variable PATH during this login session, enter the command:

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

To verify the path enter:

echo $PATH

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

Add /opt/Navisphere/bin to the environment variable PATH.

What next? For legacy storage systems — Go to the next section, “Configuring the Host Agent” on page 26.

For CX3-series, CX-series, and AX-series storage systems — If you are setting up a new server, go to “Starting and stopping the Host Agent” on page 41. If you are just upgrading the Host Agent or CLI on an existing system, you are finished with the upgrade.



Configuring the Host Agent Before you can use Navisphere Manager or Navisphere CLI to configure legacy storage systems connected to a Host Agent, you must make sure the Host Agent configuration includes the information listed below.

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

Before you can use the CLI navicli register command to configure a CX3-series, CX-series, or AX-series storage system connected to a Host Agent, you must make sure the Host Agent configuration file includes a privileged user.

The pathname of the Host Agent configuration file is /etc/Navisphere/agent.config

What next? Go to the appropriate selection below for the information you need to add to the Host Agent configuration file:

◆ “Specifying a communication channel for legacy storage systems” on page 27

◆ “Adding IP addresses for a portal system” on page 27

◆ “Adding privileged users” on page 30

Information to add to the Host Agent configuration file for legacy storage systems

Required for

Manager CLI

Communication path for the Host Agent to the storage system

Yes Yes

IP addresses of the portal system Yes No

Privileged user No Yes



Specifying a communication channel for legacy storage systems

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

Each SP in a storage system is connected to the server by a Fibre Channel arbitrated loop (FC-AL) or fabric connection to a Fibre Channel adapter, sometimes called a host bus adapter (HBA). The path from the adapter through the SP to one LUN in the storage system is a communication channel to the storage system for the Host Agent. The device entries in the Host Agent configuration file define the communication channels. The fibre controllers use SCSI mapping.

To use automatic device scanning, which updates device entries each time the Host Agent starts, make sure the Host Agent configuration file has a device entry with the following format:

device auto auto

This entry eliminates the need to enter specific devices in the configuration file and it is an entry in the default Host Agent configuration file.

What next? To add IP addresses for a portal system — Go to “Adding IP addresses for a portal system” on page 27.

To add a privileged user — Continue to the section, “Adding privileged users” on page 30.

Adding IP addresses for a portal system

Note: You must also use a portal system to centrally monitor storage-system events. For detailed instructions, refer to the EMC Navisphere Manager Administrator's Guide, P/N 300-003-511.

If you will use Navisphere Manager 6.X to configure the Host Agent and manage legacy storage systems, you will use a portal system. A portal system is a CX3-series or CX-series storage system (storage-system portal), or a Windows Server 2003, or Windows 2000 server (server portal) running Storage Management Server software. When Navisphere 6.X requests information from a Host Agent, the request gets routed through the storage management server on the storage-system portal or the server portal to the Host Agent. For this reason, when using servers to monitor or perform management



operations, you must enter the IP address for both SPs of the storage-system portal and the IP address for the server portal to the privileged user’s list in the Host Agent configuration file.

If you know the IP addresses for the portal system, you can add them to the Host Agent configuration file now.

Note: When using Navisphere Manager 6.X, failure to enter the correct IP addresses results in a Caller not privileged error when attempting an operation to those Host Agents.

To enter an IP address into the Host Agent configuration file, you can either edit the Host Agent configuration file manually or use Navisphere CLI.

Using a text editor to edit the Host Agent configuration fileTo enter an IP address into the Host Agent configuration file, do one of the following:

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

user system@IPaddress

where:

For example, once you have configured a CX3-series or CX-series storage system as the storage-system portal, you must add the IP address for each SP in the portal to the Host Agent configuration file as follows:

user [email protected] [email protected]

◆ If you are using a server portal, add the IP address for the server to the sys:\emc\agent\agent.cfg file using the following format:

user system@IPaddress

where:

IPaddress is the IP address for an SP in the portal storage system

IPaddress is the IP address for the server portal

mailto:[email protected]




For example, once you have configured a Windows Server 2003, or Windows 2000 server as the server portal, you must add the IP address for the server to the Host Agent configuration file as follows:

user [email protected]. 227

Using the CLI to edit the Host Agent configuration fileAdd the IP address for each SP in the storage-system portal, or the IP address for the server portal to the Host Agent configuration file using the following CLI command:

navicli remoteconfig -setconfig -adduser system@ IPaddress

where:

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

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

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

navicli remoteconfig -setconfig -adduser [email protected]

What next? To add a privileged user, continue to the next section, “Adding privileged users” on page 30. If you are done editing the Host Agent configuration file, go to “Saving the Host Agent configuration file” on page 31.

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







Adding privileged usersIf you will use Navisphere CLI to configure any storage system, the Host Agent configuration file must include an entry that defines the person who will issue the CLI commands as a privileged user.

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

For a local user:user name

For a remote user:user name@hostname

where:

name is the person’s account namehostname is the name of the remote server the person will be

using

The default Host Agent configuration file includes a user root entry.

What next? Continue to the next section, “Saving the Host Agent configuration file” on page 31.



Saving the Host Agent configuration file1. Save the Host Agent configuration file.

2. If you are done adding information to the Host Agent configuration file, stop and restart the Host Agent by entering the following commands:

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

What next? For CX3-series, CX-series, and AX-series storage systems — You are done editing the Host Agent configuration file.

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

◆ Agent description and contact◆ Polling frequency◆ SP event log entries to transfer

Using Navisphere Manager — Use the remote agent configuration feature as described in the Navisphere Manager Administrator’s Guide.

Using CLI — Use the navicli remoteconfig command as described in the Navisphere Command Line Interfaces (CLI) Reference.

Using a text editor (textedit, vi, or emacs) — Refer to “Manually editing the Host Agent configuration file” on page 32.



Manually editing the Host Agent configuration fileThis section describes how to manually configure the agent.config file using a text editor, such as vi, emacs, or textedit. You need to edit the Host Agent configuration file only if you have legacy storage systems connected to the server.

A previous section explained how to edit the file to add one privileged user who could configure storage systems, but this section explains all the configuration file entries.

Note: Any user who can log in to a server that is a Navisphere management station can monitor the status of any of the managed storage systems.

The pathname to the Host Agent configuration file is:

/etc/Navisphere/agent.config

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

• Agent description and contact

• Communication channel(s) to the SP

• Users who can configure a managed storage system

• Polling frequency

• SP event log entries to transfer

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

Sample Host Agent configuration file (agent.config)# Navisphere agent.config# ---------------------# This file is used by Navisphere Agent to configure# site specific values.## All entries in this file have this form:## object value-list## Where "object" tells what sort of information is to# be configured, and "value-list" is a # whitespace-separated list of values to be configured.# Samples, which should be edited, appear below for all # permissable types of object#



# White space (tabs, space, line-feeds,# carriage-returns) and blank lines are ignored;# To continue a line onto the next line, use "\" as the # last character of that line. The "\" is dropped when # the next line is concatenated to the continued line.############################## Description specification# -------------------------## The "clarDescr" object takes arbitrary text values # intended to describe the agent and its location.#clarDescr Navisphere Agent## The "clarContact" object takes arbitrary text values# intended to describe who is responsible for the # configured agent, and how to reach them.#clarContact John Smith, 800-555-1212## Device specification.# ----------------------## The format of "device" objects for CLARiiON devices# is:# devicedevice-specname "description"## where the device-specification is the device name to# open to access the CLARiiON device. It can be a# SCSI-2 file name. If this is "auto", all attached# arrays with bound LUNs will be automatically# configured. (Currently, dummy arguments are required# for name and description, when using# auto-configuration.) This can NOT be defaulted.## The name is the per clariion name that can be used to# identify each CLARiiON to the manager application. # The name is REQUIRED and cannot contain spaces (even # if surrounded by quotes). This can NOT be defaulted.# ## The description is a quoted string that contains a# brief description of the CLARiiON chassis being# managed. It defaults to "" if not specified, and to# the device name for auto-configuration.# # SAMPLES:#device sga NAVISPHERE-8 "NAVISPHERE-8"#device sgb NAVISPHERE-1 "NAVISPHERE-1"#device sgc NAVISPHERE-2 "NAVISPHERE-2"#device sgd NAVISPHERE-3 "NAVISPHERE-3"



#device sge NAVISPHERE-4 "NAVISPHERE-4"#device sgf NAVISPHERE-5 "NAVISPHERE-5"#device sgg NAVISPHERE-6 "NAVISPHERE-6"#device sgh NAVISPHERE-7 "NAVISPHERE-7"#device sg0 NAVISPHERE-0 "NAVISPHERE-0"#device sg1 NAVISPHERE-1 "NAVISPHERE-1"#device sg2 NAVISPHERE-2 "NAVISPHERE-2"#device sg3 NAVISPHERE-3 "NAVISPHERE-3"#device sg4 NAVISPHERE-4 "NAVISPHERE-4"#device sg5 NAVISPHERE-5 "NAVISPHERE-5"#device sg6 NAVISPHERE-6 "NAVISPHERE-6"#device sg7 NAVISPHERE-7 "NAVISPHERE-7"## automatically detect manageable devicesdevice auto auto## User Specification.# ------------------## The format of "user" objects is"# user localUserId# OR# user userId@hostname## These build a list of users who are allowed to perform # WRITE operations to the CLARiiON devices managed by # this agent. By default, as specified below, only root # on this machine has WRITE access. Others can be # granted access by including their login name and host# which they can access from. A null list prevents # anyone, including admin, from having write access. In # order to get write access, this file would have to be# modified and the Agent stopped and restarted to # re-read the configuration file, or an appropriate # remote configuration file would have to be sent to the # agent from an already-priviledged user.

user root # only on this machine#user sblue@picasso # individual user "sblue" on

# host "picasso"#user lgreen@hannibal # individual user "lgreen" on

# host "hannibal"## Poll specification# ------------------# The "poll" object takes a numerical count of seconds.# # This specifies how often the agent solicits # information from the array, rather than using cached# information. The minimum is "10".#poll 60



## Eventlog specification# ----------------------# The eventlog object takes a numerical count of log # entries.# # This defines the maximum number of SP log events# received by the agent on startup, and received by # clients per poll. A value of 0 causes the device’s # entire log to be read at startup. A minimum of 100# events will be read on serial, and 2048 on fibre,# overriding any lower value configured below.#eventlog 100## Baud Rate specification# -----------------------# If the agent is using a serial port to manage a # device, the next entry can specify either 9600 baud# or 19200 baud.#baud 9600# # linux currently can’t handle this# nomegapoll##### end of configuration file###

Specifying the Host Agent description and contactThe Agent description (clarDescr) and contact (clarContact) entries are optional informational text strings that Manager does not use. You can use the clarDescr entry to include information about the Agent, such as its revision, and the clarContact entry to include information about the person to contact concerning any Agent questions or problems that might occur.

Host Agent descriptionEither modify the clarDescr entry or add a new clarDescr entry.

A clarDescr entry has the following format:

clarDescr [description]



where:

Contact descriptionEither modify the clarContact entry or add a new clarContact entry.

The clarContact entry has the following format:

clarContact [contact_info]

where:

Communication channels to the SPsEach SP in a storage system is connected to the server by a Fibre Channel arbitrated loop (FC-AL) or a fabric connection to a Fibre Channel adapter, sometimes called a host bus adapter (HBA). The path from the adapter through the SP to one LUN in the storage system is a communication channel to the storage system from the Host Agent. The device entries in the Agent’s configuration file define the communication channels used for management. The HBAs use SCSI mapping.

If the storage system has two SPs that are both connected to host bus adapters in the same server, the server’s Host Agent configuration file must have a device entry (device) for the communication channel through each SP. If the SPs are connected to host bus adapters in different servers, the Agent configuration file in each server must have a device entry for the communication channel through the SP connected to that server.

If you add another storage system to the server in the future, you must make sure that the Agent configuration file has a device entry for the communication channel through each SP in the new storage system.

description is an optional description of the Agent, such as the name of the Agent and its revision. For example, Disk-Array Agent, revision x, where x is the revision of the Agent you are running.

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



With the device entry of device auto "auto", the Host Agent will automatically select the communication channel to one LUN per SP in each storage system. This method is the easiest way to enter device information in the Agent configuration file.

If you do not use device auto "auto", then to specify a communication channel per SP, you need to know the FC-AL address IDs or SCSI target IDs of the storage system’s SP(s) and of the server’s HBAs to which the SPs are connected. The FC-AL address ID or the SCSI target ID of an SP may be set by switches on the back of the storage system, as described in the storage-system hardware reference manual. In addition, you need to know the number for the LUN owned by each SP in the storage system.

Specifying a communication channel

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

Either modify the device entry or add a new device entry in drive:\Program Files\EMC\Navisphere Agent\agent.config file.

The entry must have one of the following formats.

For automatic device scanning on Host Agent startup

device auto auto “auto”

This entry causes the device entries to update every time the Host Agent starts. Use it instead of explicitly entering devices with the following format. Device entries with these formats remain constant when the Host Agent restarts.

For access to a specific device

The device entry uses the following syntax:

device channel name ["description"]



where:

Adding users to the Host Agent configuration fileAny user who can log in to a server that is a Navisphere management station can monitor the status of its managed storage systems. However, a user must be a privileged user in the Host Agent configuration file to change a managed storage system’s configuration.

If you will be using Navisphere Manager 6.X to configure the Host Agent and manage your storage systems, you will be using a portal system for legacy storage systems. To add privileged users for a portal configuration, see “Adding IP addresses for a portal system” on page 27. To add other privileged users, see “Adding privileged users” on page 30.

channel is a required field for the communication channel: the device name that the Agent uses to communicate with the storage system. The format is:

sgX

where X is the letter or number that identifies the sg device.

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

"description" is an optional description of the connection to the chassis. Be sure to enclose the description in quotation marks. For example, "Path from host img01 to cps220 SP A". The Navisphere Manager does not use this information, but the Navisphere CLI does. The information you specify here may be critically useful to anyone who maintains the storage systems connected to this server.



Specifying a polling frequency for the Host AgentPolling frequency sets the time interval for the Agent to execute an automatic hardware poll to the storage system and update the Agent’s image of the storage system. Polling frequency determines how often the storage system is polled. The default polling interval is 60 seconds.

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

Add the following line to the /etc/Navisphere/agent.config file:

poll n

where:

Specifying the number of SP events to readThe Agent reads event entries from the SP unsolicited event log at startup. You specify the number of the most current event to read. Since the complete log can contain as many as 16,800 entries, you may not want to burden the Agent with reading all of them.

Note: If you enter a small value, Navisphere Manager and Navisphere CLI users will not be able to view the entire contents of the log without first stopping all applications, changing the value in the configuration file, saving the configuration file, restarting the Agent, and restarting the applications.

For a nondefault value, add a line of the following form to the configuration file:

eventlog n

n is 0 or an integer specifying the number of seconds between each poll of the Agent’s SP. The minimum value, other than 0, is 10. We recommend that n be equal to or greater than 60 (the default value). If n is omitted, Agent polling is disabled and the SP is inaccessible. If n equals 0, the Agent will poll every time it gets a request.



where:

You have finished editing the host configuration file. Save the file and test the configuration by starting the Agent as explained next.

To start the Agent, from the root account, enter the following command:

/etc/init.d/naviagent start

To stop the Agent, from the root account, enter the following command:

/etc/init.d/naviagent stop

Specifying the serial port baud rateInstead of managing a storage system connected from a Navisphere management station, you can manage it using Navisphere applications running on a laptop or PC connected to the serial port of an SP in the storage system. The baud entry in the Host Agent configuration file specifies the baud rate for the serial ports on the SPs in storage systems connected to the server.

Add the following line to the /etc/Navisphere/agent.config file:

baud n

where:

What next? For detailed information on starting, stopping, or removing the Host Agent, continue to the next section.

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

n is either 9600 or 19200.



Starting and stopping the Host AgentOn a Linux server, the Host Agent starts automatically when you bring the server up to init level 3. When you first start the Host Agent, look at the system log for the server’s operating system to make sure the Host Agent started and no device errors occurred. The system log is located in /var/log/messages.

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

Starting the Host Agent From the root account, enter the following command:

/etc/init.d/naviagent start

Stopping the Host Agent From the root account, enter the following command:

/etc/init.d/naviagent stop

Host Agent status and error loggingWhile the system is running, Linux tracks information about Host Agent events and Host Agent errors, and places this information in log files on the server.

The Host Agent error log tracks information about the Host Agent’s startup, the Host Agent shutdown, and errors that might occur, such as the Host Agent’s inability to access a device in the configuration file. If problems occur, log files are a good place to start your troubleshooting.

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

System events are logged in /var/log/messages.



Removing the Host Agent and CLI on an ESX Server

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

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



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.0 or later, the script notifies you about the TCP/IP ports that were opened by the installation of the Host Agent and CLI.

4. If no other software on the ESX Service Console is using the ports listed in Table 4, we recommend that you close these ports by entering the following the procedure below.

a. Log in as root.

b. Enter the command:esxcfg-firewall -c port,protocol,direction

where:

Table 4 TCP/IP ports used by the Navisphere Host Agent and CLI applications


Host Agent 6389 Incoming

CLI 6389, 443, 2163 Outgoing

6390, 6391, 6392 Incoming


protocol is tcp


application is naviagent for the Host Agentis navicli for the CLI



Removing the Host Agent and CLI on a Linux server

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

1. Log in to the Linux server as root or as a member of an administrative group.

2. Open a terminal window and depending on which revision you are running, enter one of the following commands to stop the Host Agent, and then uninstall the Host Agent and CLI files.

• Revision 6.16.x.x.x (or later)

/etc/init.d/naviagent stop rpm -e naviagentcli

• Revision 6.7.0.4.7

/etc/init.d/naviagent stop rpm -e naviagentcli-version

For example, rpm -e naviagentcli-6.7.0.4.7-1

• Revision 6.7.0.4.7 (or earlier)

/etc/init.d/naviagent stop rpm -e naviagent-version

For example, rpm -e naviagent-6.6.0.4.7-1

The system removes all files required to run the Host Agent and CLI.

Note: A backup copy of the configuration file is saved in /etc/Navisphere/agent.config.rpmsave.



Removing the CLI on an ESX Server 1. Log in to the VMware ESX Server Service Console as root or as a




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, the script notifies you about the TCP/IP ports that were opened by the installation of the CLI.

If no other software on the Service Console is using the ports listed in Table 5, we recommend that you close these ports as described below.

a. Log in as root.



where:

Table 5 TCP/IP ports used by Navisphere CLI


CLI 6389, 443, 2163 Outgoing

6390, 6391, 6392 Incoming


protocol is tcp


application is navicli for the CLI



Removing the CLI on a Linux server1. Log in to the Linux server or VMware Linux Virtual Machine as

root or as a member of an administrative group.

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

rpm -e navicli

The system removes all files required to run Navisphere CLI.


Installing, removing, and using the Navisphere Server Utility

Installing, removing, and using the Navisphere Server UtilityThis section describes how to install, run, use, and remove the Navisphere Server Utility on a Linux server or VMware ESX Server connected to a CX3-series, CX-series, or AX-series storage system.

Note: If your server is running the Host Agent and you want to use some of the features in the Server Utility, see “Determining whether to install the Host Agent or Server Utility” on page 14.

Do not install the Server Utility on a VMware Linux Virtual Machine. You can install the utility on a VMware ESX Server system.

Installing the Server Utility1. On the Linux server or VMware ESX Server, log in to the root

account.



mount /mnt/cdrom


4. At the command line prompt, look for any existing Server Utility by typing:

rpm -qi naviserverutil

or

rpm -qi axnaviserverutil



If a previous version of the software has not been installed, the system will respond with one of the following messages:

Package naviserverutil is not installed

or

Package axnaviserverutil is not installed

If you see one of the above messages, go to step 6. If a previous version of the software has been installed, the system displays information about the existing Server Utility that starts with the following:

Name: naviserverutil Relocations: (not relocateable)Version: x.x.x.x.xx Vendor: EMC Corp.

5. To remove a previous version of the software, refer to “Removing the Server Utility” on page 51.


cd /mnt/cdrom


cd linux


8. Enter the following command to install the Server Utility:

rpm -i naviserverutil-version-build.platform.rpm

Note: For a SuSE ia64 system, use the following command: rpm -i naviserverutil_suse-version-build.platform.rpm

where:

version and build are the version number and the build number for the Navisphere Server Utility on the CD, for example, 6.20.2.2.27-1.

platform is your Linux platform number, for example, i386, ia64, or x86-64.

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



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


10. Remove the CD from the server’s CD-ROM drive.

Running the Server UtilityYou can run the Server Utility from the server or from the server support CD.

Running the Server Utility from the server1. Open a console window.



3. Run the Server Utility:

./naviserverutilcli

Running the Server Utility from the CD1. On the Linux server or VMware ESX Server, log in to the root

account.


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

mount /mnt/cdrom


cd /mnt/cdrom

5. Navigate to the Linux directory:

cd linux

6. Run the Navisphere Server Utility:

./naviserverutilcli



Using the Server UtilityThe Linux version of the Navisphere Server Utility allows you to perform the following functions:

◆ Update server information

◆ Perform snapshot tasks (Navisphere Express only)

◆ Generate a high-availablity report

Updating server informationThe Update Server Information option allows you to send information about the server to all connected storage systems. To update server information, select option 1 from the Server Utility’s Welcome screen, and follow the instructions on the utility.

Performing snapshot tasksFor information on using the snapshot tasks option, refer to the Navisphere Express online help.

Generating a high-availability reportThe Generate high availability report option and the naviserverutil hav -upload command determine if the server is configured for high availability by verifying that the server has at least one connection path to each storage-system SP, and that PowerPath or some other failover software is running. After the verification, the utility generates a summary report and saves it to the server. If you issue the naviserverutil hav -upload command, the utility also sends the report to the specified storage system.

Generate a high-availability report to:

◆ check the status of a server.

◆ prepare for a software installation on a storage system.

Checking the status of a serverTo periodically check the high availability status of a server, select option 3 from the Server Utility’s Welcome screen, and follow the instructions on the utility to generate a high-availability report.

Preparing for a software installation on a storage systemIf you are generating a high-availability report as a prerequisite to updating storage-system software, you need to upload this report to the storage system prior to installing the software on the storage system.



To generate and upload an HA report, issue the following command from the directory to which you installed the utility:

naviserverutilcli hav -upload -ip IPaddress -user username -password userpassword -scope scopelevel -port 443/2163 [-directory outputdirectory]

where:

After uploading the HA report — In addition to running the Server Utility to validate server high availability, we strongly recommend that you perform the following manual checks.

◆ Make sure that you have verified that all software and hardware is supported and interoperable according to EMC's E-Lab™ Interoperability Navigator and support matrices.

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

IPaddress the IP address of an SP on the storage system to which you will upload the report.

username the login name for the storage system.

userpassword the password required for access to the storage system.

scopelevel the level of access this username and password has to the storage system - 0 = global; 1 = local.

outputdirectory the directory to which you want to deposit the report on the server. This command is required only if you are running the Server Utility from the CD. Otherwise the report is automatically saved to the Navisphere Server Utility installation directory.

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



◆ If you are about to perform a storage-system software online upgrade or you added an HBA, a LUN, or changed connectivity (added a path or changed zoning):• Make sure that you have validated all software and hardware

are supported and interoperable according to EMC E-Lab Interoperability Navigator and support matrices.

• Verify that all LUNs (virtual disks) that your servers will access during the upgrade are under path management software control. For servers running PowerPath and DMP, see the Failover Software section on the Details tab of the report and locate these LUNs. If they are not in the list, the server will lose access to those LUNs during the software upgrade.

Removing the Server Utility1. Log in to the Linux server or VMware ESX Server as root or as a


2. Open a terminal window and, depending on which version of the Server Utility is installed, enter the appropriate command to remove the Server Utility:

rpm -e naviserverutil

or

rpm -e axnaviserverutil

Note: To verify which version is installed, enter rpm -qi naviserverutil or rpm -qi axnaviserverutil. If the utility is installed, information about the utility is displayed.


Installing and removing the Admsnap Utility

Installing and removing the Admsnap UtilityWe strongly recommend that you install admsnap on all Linux servers connected to a CX3-series or CX-series storage system that has the SnapView driver installed.

Important If you are upgrading your storage system to FLARE OE version 02.19.xxx.5.yyy or later, you must upgrade admsnap to version 2.9.x or later. Before you upgrade FLARE, verify that your operating system version supports admsnap version 2.9.x or later. Refer to the Admsnap Release Notes or the EMC Support Matrix on the Powerlink website.

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

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

◆ SnapView on a supported CLARiiON storage system. For a list of supported storage systems, refer to the release notes for SnapView and admsnap.

◆ Access Logix on the same CLARiiON storage system.



To install Admsnap Utility

Note: If you have VMware ESX Server, install the admsnap utility on the VMware Linux Virtual Machine.

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

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

rpm -qi admsnap

3. Examine the list for any previous revision of admsnap.

4. If a previous revision is installed, remove it as described in “To remove the Admsnap Utility” on page 55. If not, go to step 5.


6. Mount the CD-ROM file system by entering the following command:

mount /mnt/cdrom

7. Change the directory to the CD-ROM drive by entering the following command:

cd /mnt/cdrom


cd linux


9. List the filenames on the CD-ROM:

ls

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



10. Install admsnap using the rpm -ivh command (Red Hat) or the yast command (SuSe).

• Red Hat Linux users — use the following command:

rpm -ivh admsnap.platform.rpm

where platform is your Linux platform number.

For example:

rpm -ivh admsnap.i386rpm

rpm -ivh admsnap.ia64.rpm

rpm -ivh admsnap.x86_64.rpm

• SuSe Linux users — use the following command:

yast -l admsnap.platform.rpm

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

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

/usr/admsnap/admsnap

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

/usr/admsnap/readme

11. Unmount (umount) the CD-ROM file system by entering:

cdumount /dev/cdrom

12. Remove the CD-ROM from its drive.

You have installed admsnap on a Linux server.

13. Verify that the correct version of admsnap is installed by entering the following command:

/usr/admsnap/admsnap help

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

14. Configure MANPATH to access the Linux man pages. Edit the /etc/man.config file by adding the following line:

MANPATH /usr/admsnap/man



15. Configure sg devices by using the MAKEDEV utility. For information on how to use the MAKEDEV utility, refer to the MAKEDEV man pages.

What next? Refer to the EMC SnapView Command Line Interfaces Reference for information on using the Admsnap Utility.

To remove the Admsnap Utility1. Log in to the Linux server or VMware Linux Virtual Machine as

root or as a member of an administrative group.

2. Open a terminal window and enter the following command to list any admsnap package that is currently installed:

rpm -q admsnap*

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

rpm -e name

where name is the admsnap program name displayed by the command in step 2.



Copyright © 2004 - 2006 EMC Corporation. All rights reserved.

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

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

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

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

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

clariion server support products for linux and vmware esx ... · system initialization utility,...

Documents