emc navisphere host agent and cli for hp-ux version 6.x ......emc navisphere host agent and cli for...

1

This guide describes how to install and remove the EMC Navisphere® Host Agent and CLI (Command Line Interface) on a server running the Hewlett Packard HP-UX® operating system. It also explains how to edit the Host Agent configuration file to include specific information.

This document uses the term "Pre-FC4700" to refer to FC4500, FC5300, FC5500, FC5700, or C-Series storage system.

Navisphere is a member of the EMC ControlCenter™ family of products.

Topics include

◆ About EMC Navisphere Software ......................................................2◆ Finding Current Information...............................................................7◆ Host Agent and CLI Requirements.....................................................8◆ Preparing to Install Host Agent and/or CLI .....................................9◆ Installing the Host Agent and CLI.................................................... 11◆ Modifying User Login Scripts ...........................................................13◆ Configuring the Host Agent ..............................................................14◆ Using the Event Monitor Configuration File...................................19◆ Starting and Stopping the Host Agent .............................................19◆ Agent Status Log Files on the Host...................................................20◆ Removing the Host Agent..................................................................20◆ Removing the Navisphere CLI ..........................................................21◆ Manually Editing the Host Agent Configuration File ...................21◆ Configuring Storage Systems ............................................................33

EMC Navisphere Host Agent and CLI for HP-UX

Version 6.X

Installation GuideP/N 069001146

REV A06

October 20, 2003

2 EMC Navisphere Host Agent and CLI for HP-UX Version 6.X Installation Guide

About EMC Navisphere Software

About EMC Navisphere SoftwareThe EMC Navisphere software suite is composed of the following components:◆ Navisphere Host and SP Agents◆ Navisphere Manager◆ Navisphere Integrator◆ Navisphere Storage Management Server◆ Navisphere CLI◆ Navisphere Analyzer

Navisphere Host and SP AgentsAgents relay configuration and status requests from Navisphere clients (such as Manager or the CLI) to CLARiiON® storage systems. Agents also periodically retrieve information from CLARiiON storage systems, and forward it to Manager so that it can update the information it displays. Agents also monitor storage-system events and can notify personnel by e-mail, page, or modem when any designated event occurs.

Host Agents reside on attached hosts. SP Agents reside on the storage processors (SPs) of the most current storage systems (such as the CX700 or FC4700), and are installed at the factory.

Navisphere Manager

Manager is a centralized storage-system management tool for configuring and managing CLARiiON storage systems. It provides the following basic functionality:◆ Discovery of CLARiiON storage systems◆ Status and configuration information display◆ Event management◆ Storage configuration and allocation

Manager 6.X is a web-based user interface that lets you securely manage CLARiiON storage systems locally on the same LAN or remotely over the Internet, using a common browser. Manager 6.X resides on an FC4700-Series storage system or a CX-Series storage system or a Microsoft Windows Server™ 2003, Windows® 2000, or Windows NT® server that is running the Storage Management Server software, and is downloaded to the browser when the Storage Management Server software is accessed.

EMC Navisphere Host Agent and CLI for HP-UX Version 6.X Installation Guide 3


Navisphere IntegratorIntegrator allows Navisphere managed storage systems to be discovered and monitored through the leading enterprise management platforms (EMP). Integrator also enables the launch of Manager from the EMP. Integrator supports the following EMPs:◆ HP OpenView® management software ◆ Tivoli NetView® management software◆ CA Unicenter™ TNG Framework

Navisphere Integrator is installed and executed on a Windows server that also hosts the EMP.

Navisphere Storage Management ServerThe Storage Management Server software is provided with Manager 6.X, and is installed and executed on each SP in a CX-Series or FC4700-Series storage system, or a Windows Server 2003, Windows 2000, or Windows NT server. A storage system with this software installed is a storage management server. A server with this software installed is called a server portal. All CX-Series and currently shipping FC4700-Series storage systems leave the factory with the Storage Management Server software installed on the SPs.The Storage Management Server software performs the following functions:

◆ Receives and responds to requests from Navisphere Manager 6.X◆ Forwards requests to the local SP Agents for processing◆ Forwards status and configuration updates to Navisphere

Manager 6.X◆ Replicates user and domain information to all storage systems in

the domain◆ Authenticates user logins and authorizes user requests◆ Logs all user logins and actions

A system with Storage Management Server software installed can also act as a portal for managing storage systems that do not have the Storage Management Server software installed (such as FC5300 and FC4500 storage systems). As a portal, the system forwards requests to the SP or Host Agent that is managing the storage system, and also collects information from the SP or Host Agent and relays that information to Manager 6.X for display updates.



Navisphere CLIThe 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 host-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 AnalyzerNavisphere Analyzer 6.X is a web-based tool, using a common browser, that allows an administrator to graphically examine the performance characteristics of the logical and physical entities that make up a CLARiiON storage system. Analyzer supports immediate (real-time) data display, as well as the display of previously logged data. As a result, Analyzer lets you do immediate comparisons, long-term trend analysis, and off-site performance troubleshooting/analysis.

Analyzer 6.X requires that Navisphere Manager 6.X be installed. Like Manager, Analyzer resides on a CX-Series or FC-Series storage system or a Windows Server 2003, Windows 2000, or Windows NT server that is running the Storage Management Server software, and is downloaded to the browser when the Storage Management software is accessed.

Navisphere EnvironmentsYou start Manager 6.X in a supported browser on a Windows or UNIX® host by entering the IP address of an SP in the CX-Series or FC4700-Series storage system with Manager installed on it. The Management user interface (UI) is downloaded to the Windows or UNIX host and it runs within the browser. All requests from the UI go to the Storage Management Server software on the CX-Series or FC4700-Series storage systems, which communicates with the SP Agent. The SP Agent, in turn, communicates with the FLARE™ or Access Logix™ software on the SPs.

With Navisphere 6.X, you can set up a portal system to manage systems that do not have Storage Management Server software installed (such as FC5300, FC4500, and NAS systems). The portal can



be a storage system (storage-system portal), or a Windows Server 2003, Windows 2000, or Windows NT server (a server portal), and must have Storage Management Server software installed.

Figure 1 shows a sample Manager 6.X environment with a CX-Series and FC4700-Series storage system configured as a storage-system portal. You manage the storage systems without the Storage Management Server software (the two FC4500s in Figure 1) through this portal. The Storage Management Server software on the portal communicates with the Host Agents on the servers attached to the storage systems.

Figure 1 Sample Navisphere Manager 6.X Environment

EMC2386

WebBrowser

LAN

HP-UXServer

HP-UXServer

Host AgentOptional CLI



Windows 2000Server

Windows or UNIX Host

* Management portal to the two FC4500 Storage SystemsWithout the Storage Management Server Software

Legend: Management connection for CX-Series and FC4700-Series

CX-Series*

Access Logix

SP Agent

Storage ManagementServer Software

Manager 6.X

SP Agent

Storage ManagementServer Software

Access Logix Access Logix Access Logix

FC4700-Series FC4500 FC4500



Figure 2 shows a sample Manager 6.X environment with a Windows 2000 server configured as the portal. In this configuration, the portal server is managing the two FC4500 systems. The Storage Management Server software on the portal communicates with the Host Agents on the servers attached to the storage systems. The Host Agents communicate with the FLARE and Access Logix software on the SPs.

Figure 2 Sample Server Portal Environment

WebBrowser

LAN

HP-UXServer

Windows 2000Portal*

HP-UXServer


StorageManagement

ServerManager 6.X



Windows 2000Server

Windows or UNIX Host

EMC2387

FC4700-Series*

Access Logix

FC4500CX-Series*

Access LogixSP AgentStorage

ManagementServer Software

Manager 6.X

CX-Series*





FC5300

* These systems are in the same domain.

Access Logix


Finding Current Information

Finding Current Information

The most up-to-date information about the Navisphere Host Agent and CLI for HP-UX is posted on the EMC Powerlink website. We recommend that you download the latest information before you install the EMC Host Agent and CLI.

To access EMC Powerlink, use the following link:

http://powerlink.emc.com

After you log in, select Support > Document Library and find the following:

◆ Navisphere Host Agent and CLI Version 6.X Release Notes

◆ The latest version of this guide that is applicable to your software revision

◆ EMC Installation Roadmap for CX-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.

http://powerlink.emc.com


Host Agent and CLI Requirements

Host Agent and CLI RequirementsTo run the HP-UX Host Agent or the host-based CLI commands, your host must meet the following requirements:

◆ Run the HP-UX operating system.

◆ Have the HBA hardware and driver installed.

◆ Be connected to each SP in each storage system either directly or through a switch or hub.

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

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

• any Windows Server 2003, Windows 2000, or Windows NT host running Storage Management Server software

• any AIX, HP-UX, IRIX, Linux, NetWare, Solaris™, Windows Server 2003, Windows 2000, or Windows NT host running the CLI.

For information about the specific revisions of the host operating system and the storage-system FLARE or 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.


Preparing to Install Host Agent and/or CLI

Preparing to Install Host Agent and/or CLIThe following tasks must be performed when you are installing the Host Agent and/or CLI:

◆ Determine whether a previous version of the software is installed (refer to page 9)

◆ Mount the CD-ROM or DVD-ROM (refer to page 10)

◆ Install the Host Agent and CLI files (refer to page 11)

◆ Unmount the CD-ROM (refer to page 13)

Before proceeding, ensure that the disk-array storage system(s) is connected to the HP-UX server where you are installing Agent.

Checking for Previous Versions of the Host Agent

To check for a previous version of Host Agent, do the following:

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

2. On the tool bar at the bottom of the screen, click the terminal icon.An hpterm window opens.

3. At the command prompt (#) in the hpterm window, execute the following command:

/usr/sbin/swlist

4. When the list of currently installed software is displayed, examine the list to determine if any previous revision of Host Agent or CLI is present. If a previous revision of the software you want to install is present, remove it (see page 20) before proceeding; otherwise continue to the next section.


Preparing to Install Host Agent and/or CLI

Mounting the CD-ROM or DVD-ROM

If the CD-ROM or DVD-ROM drive is currently mounted, unmount the drive (see page 13) before proceeding.

1. Insert the CD into the host’s CD-ROM or DVD-ROM drive.

2. At the command prompt (#) in the hpterm or xterm window, execute the following command:

sam

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

3. Select the Peripheral Devices option. The Peripheral Devices menu opens.

4. Select the Device List option. The Device List dialog box opens with several menu choices at the top of the dialog box.

5. Select the line in the list that contains descriptions of "CD-ROM SCSI drives" or "DVD-ROM SCSI drives." (Note this phrase may be preceded by a manufacturer’s name.)

6. At the top of the Device List dialog box, open the Action pull-down menu and select Show Device Files. A list of device names appears. Note the device name for the CD-ROM or DVD-ROM; for example, /dev/dsk/c2t2d0. Click OK.

7. Exit the SAM utility.

At the command prompt (#) in an hpterm or xterm window, use the following command from the root directory to make sure the /cdrom or /dvdrom directory exists:

ls

If the /cdrom or /dvdrom directory exists, it will appear in the resulting list. If the /cdrom or /dvdrom directory does not exist, create it with the following command:

mkdir /cdrom

or

mkdir/dvdrom


Installing the Host Agent and CLI

8. Execute the following command to mount the CD-ROM or DVD-ROM:

mount devicename /cdrom

or

mount devicename /dvdrom

where devicename is the name you previously noted in step 6 above.

Installing the Host Agent and CLI The Navisphere Installation CD contains two Navisphere software packages: Navisphere Host Agent and Navisphere Command Line Interface (CLI). Use the following procedure to install the Host Agent, the CLI, or both the Host Agent and CLI. If you will install both, install the Host Agent first.

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

cd /cdrom

or

cd/dvdrom

2. List the contents of the CD by entering the command:

ls

Record the Source Depot Path to use in the next command.

3. At the command prompt (#) in an hpterm window, execute the following command to specify the CD-ROM or DVD-ROM as the source depot:

/usr/sbin/swinstall -s /cdrom/NAVIAGNT.DEP\;1 -x mount_all_filesystems=false

or

/usr/sbin/swinstall -s /dvdrom/NAVIAGNT.DEP\;1 -x mount_all_filesystems=false

where NAVIAGNT.DEP is the Source Depot Path.


Installing the Host Agent and CLI

4. The SD-Install Software Selection dialog box opens. In the software selection area of the SD-Install Software Selection dialog, select (highlight) one of the following:

NAVICLI (to install just the CLI)orNAVIAGENT (to install just the Host Agent)

5. From the taskbar in the SD-Install Software Selection dialog box, follow this path:

Actions > Install(analysis)

The Install Analysis dialog box opens.

6. When the installation analysis completes, click OK.

A confirmation dialog opens.

7. In the confirmation dialog box, click Yes.

The confirmation dialog box and the Install Analysis dialog box close, the Install dialog box opens, and the installation begins.

8. When the installation completes, click Done.

9. In the SD-Install Software Selection dialog box, perform one of the following two tasks:

a. If you just installed the Host Agent and also want to install the CLI:

– In the software selection area of the SD-Install Software Selection dialog box, select (highlight) NAVICLI.

– Return to step 4 of this procedure.b. If you do not want to install the CLI, from the taskbar in the

SD-Install Software Selection dialog box taskbar, follow this path: File >Exit.


Modifying User Login Scripts

Unmounting the CD-ROM or DVD-ROMAt the command prompt (#), execute the appropriate command for the drive you want to unmount.

To unmount a CD-ROM, enter the following commands:

cdumount /cdrom

To unmount a DVD-ROM, enter the following commands:

dvdumount /dvdrom

Before you can use the Navisphere Storage Management Server software, you must modify the user login scripts and the Host Agent configuration file. Modify these files using a text editor such as vi. Refer to the Modifying User Login Scripts and Configuring the Host Agent sections.

Modifying User Login ScriptsUse a text editor to modify your login scripts as described below:

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

DTSOURCEPROFILE=true

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

• add /opt/Navisphere/bin to PATH

• add /opt/Navisphere/man to MANPATH

• add /usr/lib:/usr/lib/X11R5:/opt/Navisphere/lib to SHLIB_PATH

You must export each path after you have modified it.


Configuring the Host Agent

Configuring the Host Agent Before you can use Navisphere Manager to manage 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.

A legacy system is a pre-FC4700 storage system or an FC4700 without the Navisphere Storage Management Server software.

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

The pathname to the 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 15

◆ Adding IP Addresses for a Portal System on page 15

◆ Adding Privileged Users on page 17

Information to Add to 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

Do not add a communication channel for an SP in a CX-Series or FC4700-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 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 below.

To add a privilege user - Continue to the next section, Adding Privileged Users on page 17.

Adding IP Addresses for a Portal System

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 CX-Series or FC4700-Series storage system (storage-system portal), or a Windows Server 2003, Windows 2000, or Windows NT 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 hosts 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.

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 File

To 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 CX-Series or FC4700-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 /etc/Navisphere/agent.config file using the following format:

user system@IPaddress

where

For example, once you have configured a Windows Server 2003, Windows 2000, or Windows NT 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

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

IPaddress is the IP address for the server portal



Using CLI to Edit the Host Agent Configuration File

Add 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 IP Addresses for a Portal System on page 15. If you are done editing the Host Agent configuration file, go to Saving the Host Agent Configuration File on page 18.

Adding Privileged Users

If 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,

1. Add a local or remote privileged user by adding the appropriate entry below:

For a local useruser name

For a remote useruser name@hostname

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

using

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



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

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:

# /sbin/init.d/agent stop# /sbin/init.d/agent start

What Next? For CX-Series and FC4700-Series storage systems - You are done editing the Host Agent configuration file.

For pre-FC4700 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 Navisphere CLI - Use the navicli remoteconfig command as described in the Navisphere CLI Reference.

Using a text editor (textedit, vi, or emacs) - Refer to Manually Editing the Host Agent Configuration File on page 21.


Using the Event Monitor Configuration File

Using the Event Monitor Configuration FileThe Navisphere Agents can monitor storage-system events and take such action as sending e-mail or paging you if specified events occur. Navisphere Manager provides an interactive way to define these events and actions. If you do not have Navisphere Manager, you can still define such events and actions by editing the Event Monitor configuration file:

/etc/Navisphere/Navimon.cfg

The file is documented internally; that is, text in it describes how to define events and the actions you want taken if the events occur. You can test the file after editing it using the Navisphere CLI command responsetest, as explained in the Navisphere CLI Version 6.X Reference.

Starting and Stopping the Host AgentOn an HP-UX host, the Host Agent starts automatically when you bring the host up to init level 3. When you first start the Host Agent, look at the system log for the host’s operating system to make sure the Host Agent started and no device errors occurred.

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

Log in as root and enter this command:

/sbin/init.d/agent start

Stopping the Host Agent

Log in as root and enter this command:

/sbin/init.d/agent stop


Agent Status Log Files on the Host

Agent Status Log Files on the HostThe operating system logs messages about Host Agent events and serious Host Agent errors into its system log (/var/adm/syslog/syslog.log). It logs messages about such Host Agent events as startup and shutdown, and errors such as the Host Agent’s inability to access a device in its configuration file. If you need information about the Host Agent’s status, look for system log messages about the Host Agent.

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

Removing the Host Agent


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

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

The removal process begins.

When the following message is displayed, the removal process is complete:

END swremove SESSION


Removing the Navisphere CLI

Removing the Navisphere CLI


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

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

The removal process begins.

When the following message is displayed, the removal process is complete:

END swremove SESSION

What Next? Set up the storage system as described in the Navisphere Manager manual. After LUNs are bound on unshared storage systems and/or in Storage Groups on shared storage systems, continue to the next section on Manually Editing the Host Agent Configuration File.

Manually Editing the Host Agent Configuration File

You need to edit the Host Agent configuration file only if you have pre-FC4700 storage systems connected to the server.

Before the Host Agent can communicate with the storage system, you must edit the Agent’s configuration file to include specific information. The pathname to the Agent configuration file is:

/opt/Navisphere/bin/agent.configor/etc/Navisphere/agent.config <link>

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

◆ Agent description and contact

◆ Communication channel(s) to the storage system(s)

◆ Alternate communication channels

◆ Users

◆ Polling frequency

◆ SP event log entries to transfer



Sample Agent Configuration File (agent.config)

############################ This file is used by Navisphere Agent to configure site #specific values.All entries in this file have this form: # object value-list# where "object" tells what sort of information is to be # configured, and "value-list" is a whitespace-separated # list of values to be configured.Samples, which should # be edited, appear below for all permissible types of # object.# White space (tabs, space, line-feeds, carriage-returns)# and blank lines are ignored; # To continue a line onto multiple lines 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-spec is the device name to open to # access the CLARiiON device. It can be a SCSI-2 file # name. If this is "auto", all attached arrays with bound# LUNs will be automatically configured.(Currently, dummy # arguments are required for name and description, when # using auto-configuration.) This can NOT be defaulted.## The name is the per-CLARiiON name that can be used to # identify each CLARiiON to the manager application. The # name is REQUIRED and cannot contain spaces (even if # surrounded by quotes). This can NOT be defaulted.## The description is a quoted string that contains a # brief description of the CLARiiON chassis being # managed. It defaults to "" if not specified, and to the # device name for auto-configuration.## SAMPLES:# device c0t0d0 NAVISPHERE-1 "NAVISPHERE-1"



# automatically detect manageable devices device auto auto

# The Navisphere Agent can now be configured to enable or # disable auto-trespass when it starts up. To enable # auto-trespass on Agent startup,enter the following line# OptionsSupported AutoTrespass# If this line is not present in the configuration file, # the default will be to disable auto-trespass.## User Specification.# The format of "user" objects is: user localUserId# OR user userId@hostname# These build a list of users who are allowed to perform# WRITE operations to the CLARiiON devices managed by # this agent.By default, as specified below, only root on # this machine has WRITE access. Others can be granted # access by including their login name and host which # they can access from.A null list prevents anyone,# including admin, from having write access.In order to # get write access,this file would have to be modified # and the Agent stopped and restarted to re-read the # configuration file,or an appropriate remote # configuration request would have to be sent to the # agent from an already-privileged user.#user root # only on this machine#user sblue@picasso # individual user "sblue" on host

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

"hannibal"## Poll Specification# The "poll" object takes a numerical count of seconds.# This specifies how often the agent solicits information # from the array, rather than using cached information. # The minimum is "10".#poll 60## Eventlog Specification# The eventlog object takes a numerical count of log # entries. This defines the maximum number of SP log # events received by the agent on startup, and received # by clients per poll. A value of 0 causes the device's # entire log to be read at startup. A minimum of 100 # events will be read on serial, and 2048 on fibre, # overriding any lower value configured below.#eventlog 100

#### end of configuration file



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

Specifying the AgentDescription

Either modify the clarDescr entry or add a new clarDescr entry.

A clarDescr entry has this format:

clarDescr [description]

where:

Specifying theContact Description

Either modify the clarContact entry or add a new clarContact entry.

The clarContact entry has this format:

clarContact [contact_info]

where:

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 e-mail address and phone number.



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

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

OptionsSupported Autotrespass

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

The sample agent configuration file contains OptionsSupported Autotrespass line as a comment, which means that the auto-trespassing is disabled. To enable auto-trespassing, you can either add the line or just uncomment it (delete the # from the beginning of the line).

Specifying Communication Channels to the SPsEach SP in a storage system is connected to the server by a Fibre Channel arbitrated loop (FC-AL) 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 Agent. The device entries in the Agent’s configuration file define the communication channels.

If a storage system has two SPs that are both connected to a host bus adapter in the same server, the server’s 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, then 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 a 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.



You need to know the FC-AL address IDs or SCSI target IDs of the storage system’s SP(s) and of the host’s HBAs to which the SP(s) are connected. The FC-AL address ID or the SCSI target ID of an SP is set by switches on the back of the storage system, as described in the storage-system installation and maintenance manual. In addition, you need to know the number for the LUN owned by each SP in the storage system.

To Specify aCommunication

Channel

Either modify the device entry, or add a new device entry.

The device entry uses the syntax:

device channel name ["description"]

where:

channel is a required field for the communication channel (device path, device name, or disk name) that the Agent uses to communicate with the storage system. The format is cDtSdL where:

For SCSI disks:

D is the number of the SCSI bus on the SCSI-2 adapter to which the storage system is connected.

S is the SCSI ID of the storage system’s SP that is connected to SCSI bus cD. If the adapter identified by cD provides a narrow SCSI bus, this SCSI ID can range from 0 through 7; and if the adapter provides a wide SCSI bus, this SCSI ID can range from 0 through 15.

L is the ID of a LUN owned by the SP identified by tS.

For Fibre Channel disks:

D, S, and L depend on the number of LUNs in the storage system and the setting of the FC-AL ID rotary switches on the SPs. You must use the ioscan utility and the CLI command systemtype to discover the device name, as explained in the following section.



Discovering theDevice Names ofCommunication

Channel LUNs

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

1. Enter the following commands to create special device files:

ioscan -fnC disk

insf -e

2. Enter the ioscan -fnC disk > orig.scan command:

This tells HP-UX to scan for disks and send the disk device names to a file, here orig.scan.

3. Print the orig.scan file to see device names similar to the following:

Class IH/W Path Driver S/W State H/W Type Description==============================================================================disk0 0/0/0.6.0 sdisk CLAIMED DEVICE SEAGATE ST34572WC

/dev/dsk/c0t6d0 /dev/rdsk/c0t6d0disk11 2/2/0.8.0.255.0.2.0 sdiskCLAIMED DEVICE DGC

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

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

/dev/dsk/c7t1d0 /dev/rdsk/c7t1d0_____________________________________________________________________________

name is a required description 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. The 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.



4. To determine which device should be specified as a communication channel in the Agent configuration file, look for device names of the DGC disks.

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

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

In the sample, the two DGC devices found are c6t2d0 and c7t1d0. Either could be connected to SP A or SP B. You can identify them using the FC-AL address IDs. These IDs are manually set with rotary switches (hard coded) on each SP. The switch settings appear in the two fields to the left of the LUN field in the hardware (H/W) path, as shown in the following listing for the first DGC device:

Assume that SP A is connected to c6t2d0 and SP B is connected to c7t1d0. In the Agent configuration file, you should specify two communication channels, one through each SP. For the first communication channel, you will specify c6t2d0 in the Agent configuration file. For the second channel, you will specify c7t1d0 in the file.

5. Enter the device names for the appropriate devices in the Agent configuration file.

6. Save the Agent file.

7. If the Agent is running, stop it (refer to the section Starting and Stopping the Host Agent on page 19). Then restart the Agent.

disk 11 2/2/0.8.0.255.0.2.0 sdisk CLAIMED DEVICE DGC/dev/dsk/c6t2d0 /dev/rdsk/c6t2d0

Setting of leftFC-AL switch

Setting of rightFC-AL switch



8. Type the CLI command systemtype to specify an HP-UX system type. As an argument to the command, if you are using the HP-UX PVLINKS feature, specify -config 2; if you are not using PVLINKS, specify -config a. As a device name, use one of the d0 device names you noted in the ioscan listing above. For example,

navicli -d c6t2d0 -h server1 systemtype -config 2

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

If you do not have a Model 5600/5700 or Model 4400/4500 storage system, you have finished the communication channel identifying procedure; skip to the next section.

For a Model 5600/5700 or Model 4400/4500 storage system, there are several additional steps, as follows.

10. Run the ioscan program again, specifying a different name for the output file; for example:

ioscan -fnC disk

insf -e

ioscan -fnC disk > second.scan

11. Print the new scan file.

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

Class IH/W Path Driver S/W State H/W Type Description==============================================================================disk0 0/0/0.6.0 sdisk CLAIMED DEVICE SEAGATE ST34572WC

/dev/dsk/c0t6d0 /dev/rdsk/c0t6d0disk15 2/2/0.8.0.2.0.0.0 sdiskCLAIMED DEVICE DGC C5600WDUNB

/dev/dsk/c9t0d0 /dev/rdsk/c9t0d0disk4 4/2/0.0.0 sdisk CLAIMED DEVICE TOSHIBA CD-ROM...

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

/dev/dsk/c10t0d0 /dev/rdsk/c10t0d0_____________________________________________________________________________



Notice that the listing for the communication channel devices has changed as follows:

Hardware path 2/2/0.8.0.255.0.2.0 DGC changed to 2/2/0.8.0.2.0.0.0 DGC C5400WDUNB, and device /dev/dsk/c6t2d0 changed to /dev/dsk/c9t0d0.

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

13. Edit the Agent configuration file again and change the original communication channel device names to those that appeared after you entered the systemtype command.

14. Restart the Agent.

Continue to the next section and resume editing the Agent configuration file.

Enabling an AlternateCommunication

Channel

You can configure the Host Agent to take advantage of the HP-UX Logical Volume Manager (LVM) alternate links (PVLINKS), allowing all configured LUNs in the storage system to be available to both SPs. Enable alternate path access by uncommenting the following line in the configuration file:

OptionsSupported AutoTrespass

Adding Users to the Agent Configuration FileAny user who can log in to a host 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 15. To add other privileged users, see Adding Privileged Users on page 17.



Specifying a Polling Frequency for the 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.

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 Agent configuration file:

poll n

where

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.



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

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.

To specify the number of SP event log entries to transfer, add the following line to the Agent configuration file:

eventlog n

where:

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


Configuring Storage Systems

Configuring Storage SystemsThe next step is to configure the storage systems connected to the server. EMC recommends that you use Navisphere Manager, instead of the CLI, to configure storage systems, as described in the EMC Navisphere Manager 6.X Administrator’s Guide.


Configuring Storage Systems

Copyright © 2002, 2003 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.Trademark Information

EMC2, EMC, CLARiiON, Navisphere, and PowerPath are registered trademarks and Access Logix, FLARE, EMC ControlCenter, SAN Copy, SnapView, and MirrorView are trademarks of EMC Corporation.HP-UX is a registered trademark of Hewlett-Packard Corporation.All other trademarks mentioned herein are the property of their respective owners.

emc navisphere host agent and cli for hp-ux version 6.x ......emc navisphere host agent and cli for...

Documents