You are on page 1of 25

Here is Your Customized Document

Your Configuration is:

Attach a server
Operating System - HP-UX
Path Management Software - HP-UX native
Model - VNX5200
Connection Type - Fibre Channel Switch or Boot from SAN
Document ID - 1419189331309

Reporting Problems

To send comments or report errors regarding this document,


please email: mydocs@emc.com.
For Issues not related to this document, contact your service provider.
Refer to Document ID:
1419189331309
Content Creation Date December 21, 2014
EMC® VNX® Series

Attaching a Server to a Configuration

November, 2014

This document explains how to attach an HP-UX Server with Native Multipath Failover to a
VNX™ in a Fibre Channel switch configuration.
The main topics in this document are:
u Before you start..........................................................................................................2
u Installing HBAs in the server.......................................................................................3
u Installing or updating the HBA driver.......................................................................... 4
u Installing Unisphere server software.......................................................................... 4
u Connecting the VNX to the server in a Fibre Channel switch configuration................ 12
u Determining if your server has a supported configuration.........................................14
u Registering the iqn number with the system............................................................. 15
u Making SPs available to the HP-UX server................................................................ 16
u Registering the server with the system..................................................................... 16
u Verifying system health............................................................................................17
u Setting system failover values for the server initiators using Unisphere....................18
u Verifying your high-availability Fibre Channel configuration......................................19
u Configuring your VNX system....................................................................................19
u Preparing LUNs to receive data.................................................................................22
u Sending HP-UX disk information to the system......................................................... 22
u Verifying your HP–UX 11i v3 native multipath failover configuration.........................22
Before you start
Note

This document uses the term system to refer to your VNX.

Note

This document covers a Fibre Channel switch configuration only. For information on
booting from a SAN, refer to the appropriate Host Connectivity Guide or the EMC Support
Matrix on the EMC Online Support website.

If you are an EMC partner, refer to the EMC online support website to download the
software mentioned in ths guide (support.emc.com).
u Read the release notes for your system, which are available on the EMC Online
Support website.
u You must have a supported Windows host on the same network as the system
management ports. You can use this host:
l As a client in which you launch the Unisphere™ software.
l To run the Unisphere Service Manager, which runs only on a Windows host.
l As an EMC Secure Remote Support (ESRS) IP Client, which must be a Windows
host, but cannot be a server (that is, it cannot send I/O to the system data ports).
u You must have a Unisphere Server with a supported Internet browser that is on the
same network as the system management ports. This host can also be the server or a
Unisphere management station. For supported Internet browsers, see the Unisphere
release notes on the EMC Online Support website.
u You must have one or more supported HP-UX Fibre Channel host bus adapters
(HBAs), which may already be installed in the server. These adapters must have the
latest supported BIOS and drivers. For information on supported HBAs, BIOS, and
drivers, refer to Supported Configurations in the Technical descriptions section on
the system support website.

Note

We recommend that you do not mix Fibre Channel HBAs from different vendors in the
same server.
u Each storage-processor (SP) Fibre Channel port that you will use on the system must
have an optical cable. These cables may already be connected for a configuration
with an existing system or server. We strongly recommend you use OM3 50 μ m
cables. For cable specifications, refer to the system's technical specifications.
u You must have one or two Fibre Channel switch fabrics, which may already be
installed, and an optical cable for connecting each HBA port to a switch port, if not
already connected. We strongly recommend you use OM3 50 μ m cables. For cable
specifications, refer to system's Technical Specifications.
u You must have a method for writing data to a LUN on the system that will test the
paths from the server to the system.

2
Attaching a Server to a Configuration

Installing HBAs in the server


For the server to communicate with the system Fibre Channel data ports, it must have one
or more supported HBAs installed.

Before you start


To complete this procedure, you will need one or more supported HBAs with the latest
supported BIOS and drivers.
For information on supported HBAs, BIOS, and drivers, refer to the E-Lab™ Interoperability
Navigator on the EMC Online Support website.

Installing HBAs
CAUTION

HBAs are very susceptible to damage caused by static discharge and need to be handled
accordingly. Before handling HBAs, observe the following precautions:
u Store HBAs in antistatic bags.
u Use a ground (ESD) strap whenever you handle HBAs.
u Never plug or unplug HBAs with the power on. Severe component damage can result.

Procedure
1. If the server is powered up:
a. Shut down the server's operating system.
b. Power down the server.
c. Unplug the server's power cord from the power outlet.
2. Put on an ESD wristband, and clip its lead to bare metal on the server's chassis.
3. For each HBA that you are installing:
a. Locate an empty PCI bus slot or a slot in the server that is preferred for PCI cards.
b. Install the HBA following the instructions provided by the HBA vendor.
c. If you installed a replacement HBA, reconnect the cables that you removed in the
exact same way as they were connected to the original HBA.
4. Plug the server's power cord into the power outlet, and power up the server.
Results

Note

The HP-UX HBA driver software is bundled with the Solaris operating system software.

Installing HBAs in the server 3


Installing or updating the HBA driver
The server must run a supported operating system and a supported HBA driver. EMC
recommends that you install the latest supported version of the driver.
For information on the supported HBA drivers, refer to the E-Lab™ Interoperability
Navigator on EMC Online Support website.

Before you start


To complete this procedure, you will need:
u The latest supported version of the HBA driver.

Note
The HBA driver is also on the installation CD that ships with the HBA. However, this
version may not be the latest supported version.

If you have a QLogic driver, download the latest supported version and instructions
for installing the driver from the vendor’s website:
http://support.qlogic.com/support/oem_emc.asp
u Any updates, such as hot fixes or patches to the server’s operating system that are
required for the HBA driver version you will install.
For information on any required updates, refer to one of the following:
l E-Lab™ Interoperability Navigator on the EMC Online Support website
l The HBA vendor’s website

Installing the HBA driver


Procedure
1. Install any updates, such as hot fixes or patches, to the server’s operating system that
are required for the HBA driver version you are installing.
2. If the hot fix or patch requires it, reboot the server.
3. Install the driver following the instructions on the HBA vendor’s website.
4. Reboot the server when the installation program prompts you to do so. If the
installation program did not prompt you to reboot, then reboot the server when the
driver installation is complete.

Installing Unisphere server software


This section describes how to install Unisphere server software.

Before you begin


Refer to the sections below to determine which application to install for host registration
and the requirements for installing each of these applications.
u To run Unisphere server software, your server must meet the requirements outlined in
Requirements for Unisphere server software on page 5.
u To determine whether to install the Unisphere Host Agent or Unisphere Server Utility
to register your HBAs with the system, refer to Determining whether to install the
Unisphere Host Agent on page 5.

4
Attaching a Server to a Configuration

Installing Unisphere server software


Depending on which Unisphere server software you are installing, refer to the appropriate
section below.
u Unisphere Host Agent – see Installing the Unisphere Host Agent on page 6.
u Unisphere Server Utility – see Installing the Unisphere Server Utility on
page 10.
u Navisphere CLI – see Installing VNX for Block Secure CLI on page 10.
u Admsnap Utility – see Installing the Admsnap Utility on page 11.

Requirements for Unisphere server software


To run Unisphere server software, your server must meet the following requirements:
u Run a supported version of the HP-UX operating system.
u For Fibre Channel connections, have the EMC VNX supported HBA hardware and
driver installed.
u Be connected to at least one SP (two SPs for high availability) in each system either
directly or through a switch or hub. Each SP must have an IP connection.
u For the host agent and CLI only - Be on a TCP/IP network connected to at least one SP
(two SPs for high availability) in the system.
The TCP/IP network connection allows the server to send LUN mapping information to
the system and it allows Navisphere CLI to communicate with the system over the
network.
u Have a configured TCP/IP network connection to any remote hosts that you will use to
manage the systems, including:
l any server whose browser you will use to access Unisphere,
l a supported Windows server running Unisphere Server software,
l any AIX, HP-UX, Linux, VMware ESX Server, Solaris, or Windows server running
VNX for Block CLI.
If you want to use VNX for Block CLI on the server to manage 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 system. The remote server can be running AIX, HP-UX, Linux, Solaris, or the
Windows operating system.

Note

For information about the specific revisions of the server operating system, the system

VNX for Block OE, and Access Logix software that are required for your version of the
host agent, see the release notes for the host agent on the EMC Online Support website.

Determining whether to install the Unisphere Host Agent


Depending on your application needs, you can install the host agent to:
u Monitor system events and notify personnel by e-mail, page, or modem when any
designated event occurs.
u Retrieve LUN world wide name (WWN) and capacity information from VNX® systems.
u Register the server’s HBAs with the system.
Alternatively, you can use the Unisphere Server Utility to register the server’s HBAs
with the system. Host registration differences between the host agent and the

Requirements for Unisphere server software 5


server on page 6 describes the host registration differences between the host
agent and the server utility.

Table 1 Host registration differences between the host agent and the server utility

Function Unisphere Host Agent Unisphere Server Utility


Pushes LUN mapping Yes – LUN mapping No – LUN mapping information is not
and OS information to information is displayed in sent to the system. Only the server’s
the system. the Unisphere UI next to the name, ID, and IP address are sent to the
LUN icon or with the CLI system. The text Manually
using the Server - Registered appears next to the
volmap command. hostname icon in the Unisphere UI
indicating that the host agent was not
used to register this server.

Runs automatically to Yes – No user interaction is No – You must manually update the
send information to the required. information by starting the utility or you
system. 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.

Requires network Yes – Network connectivity No – LUN mapping information is not


connectivity to the allows LUN mapping sent to the system. Note that if you are
system. information to be available to using the server utility to upload a high-
the system. availability report to the system, you
must have network connectivity.

Installing the Unisphere Host Agent


This section describes how to install the Unisphere Host Agent.
To modify an existing host agent configuration, refer to the next section.

Installing the Unisphere Host Agent on an HP-UX server


We recommend that you download and install the most recent version of the Unisphere
Host Agent software from the EMC Online Support website.
Procedure
1. At the HP-UX server, log in as superuser (root).
2. If your server is behind a firewall, open TCP/IP port 6389.
This port is used by the host agent. If this port is not opened, the host agent will not
function properly.
3. If an earlier version of the host agent is installed on the server, remove it before
continuing.

Note

To verify if the host agent is installed, use the /usr/sbin/swlist command to get
a list of the currently installed software.

4. Download the software:

6
Attaching a Server to a Configuration

a. From the EMC Online Support website, select the appropriateVNX Series Support
by Product page and select Downloads.
b. Select the Unisphere Host Agent and download the zip file.
c. At the command line prompt, navigate to the directory where you saved the zip file
and unzip the file.
d. Install the software: HostAgent-HPUX-32-NA-version-build.dep
where version and build are the version number and the build number of the host
agent.
5. Use the swlist command to verify that the appropriate software was installed.

Edit the HP-UX host agent configuration file


Edit the HP-UX host agent configuration file (/etc/Unisphere/agent.config) as
follows:
Procedure
1. Add the following entry if it does not already exist: device auto auto
2. Add at least one local or remote privileged user:
For a local user:
user name

For a remote user:


user name@hostname

where name is the person’s account name and hostname is the name of the remote
server the person will be using.
The default host agent configuration file includes a user root entry.
3. Save the host agent configuration file.

Configuring the Unisphere Host Agent


Verify that the host agent configuration file includes a privileged user, as described in
Adding privileged users on page 7

Note

The pathname of the host agent configuration file is /etc/Unisphere/


agent.config

Adding privileged users


Before you begin
If you use Navisphere CLI to configure any 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:

Configuring the Unisphere Host Agent 7


user name@hostname

where name is the person's account name and name@hostname is the name of the
remote server the person will be using.
The default host agent configuration file includes a user root entry.

Saving the host agent configuration file


Procedure
1. If you have finished adding information to the host agent configuration file, save the
host agent configuration file.
2. Stop and restart the host agent by entering the following:
#/sbin/init.d/agent stop

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

Using the event monitor configuration file


The Unisphere Host Agent can monitor system events and take such action as sending e-
mail or paging you if specified events occur.
The event monitor that ships with Unisphere provides an interactive way to define these
events and actions. If you do not have event monitor, you can still define such events and
actions by editing the event monitor configuration file.
/etc/Unisphere/Navimon.cfg
The file is self-documenting; 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 Command
Line Interface Reference.

Running the Unisphere Host Agent


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

Starting the host agent on an HP-UX server


The host agent starts automatically when you bring the server up to init level 2. When you
first start the host agent, look at the system log for the server’s operating system to make
sure the agent started and no device errors occurred.
The system log is located in /var/adm/syslog/syslog.log.

Note

When a system experiences heavy input/output traffic (that is, applications are using the
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 system management task. This
behavior is most evident when one host agent is managing multiple systems. Also, if the
SP event log is large and the host agent configuration file is set up to read all events, it
may take a few minutes for the host agent to start.

Procedure
1. Log in as root or the equivalent.
2. Enter the following command: /sbin/init.d/agent start

8
Attaching a Server to a Configuration

Results
The host agent now start automatically at system startup.
It may take a few minutes for the host agent to start when:
u Applications are using the system, or
u The SP event log is large and the host agent configuration file is not set up.
u Applications are using the system, or
u The SP event log is large and the host agent configuration file is not set up.

Stopping the host agent on HP-UX server


Procedure
1. Log in as root or the equivalent.
2. Enter the following command:/sbin/init.d/agent stop

Testing the host agent connections


Before continuing, you should test the host agent connections as follows:
Procedure
1. Start the host agent.
2. Look for any errors on the console and in the operating system log to make sure the
agent started and no device errors occurred.
3. Verify that the host agent on the server can see the system as follows:
a. Enter the following CLI command: naviseccli |navicli [-d device]| -h
hostname port -list -hba

Note

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

where
[-d device] is the device name for the system (only supported with legacy
systems).
-h hostname is the IP address of the SP.
For each HBA in the server, a listing similar to the following will be displayed. For
systems in a SAN (shared storage) environment, the listing includes HBAs in all
connected hosts.
Information about each HBA:
HBA UID: 10:00:00:60:B0:3E:46:AC:10:00:00:60:B0:3E:46:AC
Server Name: siux134
Server IP Address: 128.221.208.134
HBA Model Description:
HBA Vendor Description:
HBA Device Driver Name:
Information about each port of this HBA:
SP Name: spa
HBA Devicename: sp0
Trusted: NO
Logged In: YES
Source ID: 1
Defined: YES
Initiator Type: 0
Storage Group Name:
Storage Group 134

Running the Unisphere Host Agent 9


b. In the listing, verify the path for each HBA installed in the host to the SP.

Host agent status and error logging


While the system is running, the operating system 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/adm/syslog/syslog.log.

Note

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

Installing the Unisphere Server Utility


This section describes how to install the Unisphere Server Utility on your server.

Installing the Unisphere Server Utility on an HP-UX server


We recommend that you download and install the most recent version of the Unisphere
Server Utility software from the applicable support by product page on the EMC Online
Support website.
Procedure
1. At the HP-UX server, log in as superuser (root).
2. If an earlier version of the server utility is installed on the server, remove it before
continuing.

Note

To verify if the server utility is installed, use the /usr/sbin/swlist command to


get a list of the currently installed software.

3. Download the software:


a. From the EMC Online Support website, select the VNX Series Support by Product
page and select Downloads.
b. Select the Unisphere Server Utility and download the zip file.
c. At the command line prompt, navigate to the directory where you saved the zip file
and unzip the file.
d. Install the software: ServerUtil-HPUX-32-NA-language-version-
build.dep
where
language is either en_US, when only the English version is available, or loc, when
the localized versions are available (including English).
version and build are the version number and the build number of the software.

Installing VNX for Block Secure CLI


This section describes how to install VNX for Block Secure CLI.

10
Attaching a Server to a Configuration

Installing VNX for Block Secure CLI on an HP-UX server


We recommend that you download and install the most recent version of the VNX for
Block Secure CLI software from the applicable support by product page on the EMC
Online Support website.
Procedure
1. At the HP-UX server, log in as superuser (root).
2. If an earlier version of the CLI is installed on the server, remove it before continuing.

Note

To verify if the VNX for Block Secure CLI is installed, enter the /usr/sbin/swlist
command to get a list of the currently installed software.

3. If your server is behind a firewall, open the TCP/IP ports listed in TCP/IP ports on page
11.
These ports are used by VNX for Block CLI. If these ports are not opened, the software
will not function properly.
Table 2 TCP/IP ports

Software TCP/IP ports


Secure CLI 443, 2163

4. Download the software:


a. From the EMC Online Support website, select the VNX Series Support by Product
page and select Downloads.
b. Select the VNX for Block Secure CLI and download the zip file.
c. At the command line prompt, navigate to the directory where you saved the zip file
and unzip the file.
d. Install the software: NaviCLI-HPUX-32-NA-en_US-version-build.dep
where version and build are the version number and the build number of the host
agent.
5. Use the swlist command to verify that the appropriate software was installed.

Installing the Admsnap Utility


To access snapshots of LUNs in the system, install the Admsnap Utility.
Installation prerequisites
Before you can install and use the Admsnap Utility, you must install SnapView on a
supported system.
For a list of supported systems, refer to the release notes for SnapView and admsnap.

Installing the Admsnap Utility on an HP-UX server


We recommend that you download and install the most recent version of the Admsnap
Utility software from the Downloads section of the VNX Series support by product page on
the EMC Online Support website.

Installing the Admsnap Utility 11


Procedure
1. Log in as superuser (root) on an HP-UX server that is on the same subnet as the
system.
2. Open an hpterm window and enter: /usr/sbin/swlist
3. When the list of currently installed software is displayed, examine the list to
determine if any previous revision of admsnap is present.
4. If a previous revision is installed, remove it.
5. Download the software:
a. From the EMC Online Support website, select the VNX Series Support by Product
page and select Downloads.
b. Select the Admsnap Utility version you want and download the zip file.
c. At the command line prompt, navigate to the directory where you saved the zip file
and unzip the file.
6. Install the software: admsnap-HPUX-32–en_US-version-build.dep
where version and build are the version number and the build number of the software.

Connecting the VNX to the server in a Fibre Channel switch


configuration
Use optical cables to connect switch ports to the VNX Fibre Channel host ports and to
Fibre Channel switch ports and to connect the switch ports to the server HBA ports.
For cable specifications, refer to the technical specifications for your VNX available from
the Learn about system link on the VNX support website or from EMC Online Support
website.

Note

A VNX host port is also called a VNX front-end data port.

Identifying VNX Fibre-Channel host ports for server connections


Module labels and FE port connectors
Each Fibre Channel I/O module has a 8 GB Fibre label on its handle and an optical small-
form factor pluggable (SFP) transceiver module in each of its Fibre FE ports.

Handling optical cables


Optical cables are susceptible to damage, so take the following precautions when
handling them:
u Keep the covers on all optical cables until you are ready to insert them.
u Avoid tight bends. If you need to make a 90° bend, do it over 6 to 12 inches.
u Do not use optical cables to support weight (including their own unsupported weight
if they are long).
u Do not pull long runs of cable; instead, lay the cable in place or pull only a few feet at
a time.
u Place the cables where no one can step on them or roll equipment over them.

12
Attaching a Server to a Configuration

Cabling the VNX Fibre Channel host ports to the switch ports (if necessary)
For highest availability, connect one or more Fibre Channel host ports on SP A to ports on
the switch and connect the same number of Fibre Channel host ports on SP B to ports on
same switch or on another switch, if two switches are available.
For each Fibre Channel (FC) host port on the VNX that you will use for I/O with the server:
Procedure
1. Locate the FC host port to which you will connect the switch port.
For information on identifying the host ports using Unisphere, refer to the Unisphere
online help.

Note

The MirrorView/A and MirrorView/S applications require onboard port 2. The SAN
Copy application may restrict or require the use of certain SP ports. Refer to the
application documentation for specific cabling information.

2. Remove the protective cover from the FC host port connector on the SP and from one
end of the optical cable, and plug the cable into the host port connector (Connecting
an optical cable on page 13 and Sample cabling between a VNX and two
switches on page 13).
3. Remove the protective cover from the optical connector on the switch port that you
will use and from the free end of the optical cable, and plug the cable into the switch
port (Connecting an optical cable on page 13 and Sample cabling between a VNX
and two switches on page 13).
Figure 1 Connecting an optical cable

CL4021

Figure 2 Sample cabling between a VNX and two switches

Cabling the switch ports to the server HBA ports (if necessary)
For highest availability in a multiple-HBA server, connect one or more HBA ports to ports
on the switch and connect the same number of HBA ports to ports on same switch or on
another switch, if two switches are available.
For each server HBA port that you will use for I/O with the VNX:
Procedure
1. Remove the protective cover from the FC switch port connector and from one end of
the optical cable, and plug the cable into the connector.

Cabling the VNX Fibre Channel host ports to the switch ports (if necessary) 13
2. Remove the protective cover from the server HBA port connector and from the free end
of the optical cable, and plug the cable into the HBA port connector (Sample cabling
for a Fibre Channel switch configuration on page 14).
Figure 3 Sample cabling for a Fibre Channel switch configuration

Zoning the switches


Use switch management software to update switch software and zone switches that are
not hard zoned.
We recommend single-initiator zoning as a best practice. In single-initiator zoning each
HBA port has a separate zone that contains it and the SP ports with which it
communicates. For information on Fibre Channel topologies, refer to the EMC Networked
Storage Topology Guide on the EMC Online Support website.
To zone the switch:
Procedure
1. Connect the switch management ports to the network from which you will manage the
switches.
2. If the switches are not running the most recent supported firmware version, install this
software from the switch vendor's website.

Note

For information on the supported switch firmware versions, see the E-Lab
Interoperability Navigator on the EMC Online Support website.

3. Use either the zoning wizard CD that shipped with the switch or the switch
management software to set up the appropriate switch zones.
a. To use the zoning wizard CD – Using the instructions provided with the CD, run the
zoning wizard and select the zone configuration that is applicable to the way that
you connected the VNX Fibre ports and the server HBA ports to the switch.
b. To use the switch management software – Download the latest version of the
switch management software from the switch vendor's website, and follow the
instructions provided for the software to setup the zones that are applicable to the
way that you connected the VNX Fibre ports and the server HBA ports to the switch.

Determining if your server has a supported configuration


Before you can determine if your server has a supported configuration, you need to know
the revision and patch level of the operating system on the server .
If you have this information, go to Verifying a server's configuration with E-Lab Navigator.
If you do not have this information, you can generate a server configuration report for
your server using the Unisphere Server Utility.

Starting the Unisphere Server Utility on an HP-UX server


Procedure
1. Open an hpterm window.
2. Navigate to the Unisphere bin directory:
cd /opt/Unisphere/bin

14
Attaching a Server to a Configuration

3. Run the server utility:


./serverutilcli

Generating a high-availability report for a server


Procedure
1. In the Unisphere Server Utility, select option 3 from the server utility's Welcome
screen to generate a resport of the server's environment.
This option detects if PowerPath® or some other failover software, such as DMP, PV
Links, or HP native failover for 11iV3, is running. After the verification, the utility
generates a summary report and saves it to the server.
2. In the summary report, select the Checklist tab to view the information about the
server that you need to compare with the E-Lab™ Navigator information.

Registering the iqn number with the system


This section describes how to register the iqn number with the system using the
Unisphere Server Utility or the Unisphere Host Agent (systems with Unisphere only).

Registering the iqn number using the Unisphere Host Agent


If you have the host agent installed, use it to register the iqn number.
Procedure
1. Start the Unisphere Host Agent:
/sbin/init.d/agent start
2. Reboot the server.

Registering the iqn number using the Unisphere Server Utility


If you have the server utility installed, use it to register the iqn number.

Starting the Unisphere Server Utility on an HP-UX server


Procedure
1. Open an hpterm window.
2. Navigate to the Unisphere bin directory:
cd /opt/Unisphere/bin
3. Run the server utility:
./serverutilcli

Registering the HP-UX server using the Unisphere Server Utility


Procedure
1. If the host agent is running, stop the host agent service.
2. In the server utility, enter 1 to select Update Server Information.
The utility automatically scans for connected systems, and displays a list of the ones
it finds.
3. In the server utility, enter u to register the server with each system the utility found.

Generating a high-availability report for a server 15


The utility sends the server’s name and IP address to each system. Once the server
has storage on the system, the utility also sends the HP-UX device name and volume
or file system information for each LUN (virtual disk) in the system that the server
sees.
4. Enter c (cancel) to stop the utility.
5. If you stopped the host agent, restart it.
6. Reboot the server.

Making SPs available to the HP-UX server


Verify that each HBA sees only the SPs (targets) to which it is connected using the
following commands:ioscan -fnC diskinsf -e

Registering the server with the system


NOTICE

Booting from a SAN configuration - If you are booting from a SAN, do not register you
server using the Unisphere Host Agent or Unisphere Server Utility. You will perform a
manual registration in the next section.

You must run the Unisphere Server Utility on each server connected to the system to
register the server's HBAs with the system.

Running the Unisphere Server Utility on an HP-UX Server


You can run the Unisphere Server Utility for HP-UX from the server.

Starting the Unisphere Server Utility on an HP-UX server


Procedure
1. Open an hpterm window.
2. Navigate to the Unisphere bin directory:
cd /opt/Unisphere/bin
3. Run the server utility:
./serverutilcli

Registering the HP-UX server using the Unisphere Server Utility


Procedure
1. If the host agent is running, stop the host agent service.
2. In the server utility, enter 1 to select Update Server Information.
The utility automatically scans for connected systems, and displays a list of the ones
it finds.
3. In the server utility, enter u to register the server with each system the utility found.
The utility sends the server’s name and IP address to each system. Once the server
has storage on the system, the utility also sends the HP-UX device name and volume
or file system information for each LUN (virtual disk) in the system that the server
sees.

16
Attaching a Server to a Configuration

4. Enter c (cancel) to stop the utility.


5. If you stopped the host agent, restart it.
6. Reboot the server.

Starting the Unisphere Host Agent


Starting the host agent on a server automatically registers the server’s HBAs with the
system.

Verifying HBA registration using Unisphere


Procedure
1. From Unisphere, select your system, then Hosts > Initiators.
2. In the Initiators list, select the initiator name, and tverify that the SP port connection
is displayed as Registered.
Once all HBAs belonging to the server are registered, you can assign the server to
storage groups.

Verifying system health


Use the system verification wizard that is part of the Unisphere Service Manager (USM)
to:
u Validate the connectivity of the system hardware components
u Verify back-end functionality
u Verify the status of all field-replaceable units
u Analyze system logs
Procedure
1. If you do not have the Unisphere Service Manager running:
a. Download and install the Unisphere Service Manager from the EMC Online Support
website to a Windows management station that is connected to the system's
management ports. If you do not have a Windows management station, your
service provider can run this wizard.
b. Start the Unisphere Service Manager by doing one of the following:
– Click the Unisphere Service Manager icon on your desktop,
or
– Select Start > All Programs or Start > Programs, then select EMC > Unisphere >
Unisphere Service Manager > Unisphere Service Manager
2. Log in to your system.
3. From the System screen, select Diagnostics > Verify Storage System and follow the
instructions that appear.
4. Review the report that the wizard generates, and if it lists any problems, try to resolve
them.

Starting the Unisphere Host Agent 17


Setting system failover values for the server initiators using
Unisphere
Use the Unisphere™ Failover Setup wizard to set the system failover values for all HBA
initiators belonging to the server:
Procedure
1. From Unisphere, select your system from the drop-down list.
2. Select the Hosts tab.
3. Under Wizards, select Failover Wizard.
4. In the Start Wizard dialog box, read the introduction, and then click Next.
5. In the Select Host dialog box, select the server you just connected to the system, and
click Next.
6. In the Select Storage Systems dialog box, select the system, and click Next.
7. In the Specify Settings dialog box, set the following values for the type of software
running on the server.

NOTICE

If you enter incorrect values the system could become unmanageable and
unreachable by the server, and the server's failover software could stop operating
correctly.

For an HP-UX server with native multipath failover, set


l Initiator Type to HP No AutoTrespass
l Array commPath to Enabled
l Failover mode to 1 or 2 if your failover version does not support ALUA (HP-UX
version 11i V1 and 11i V2)
l Failover mode to 4 if your failover version does support ALUA

Note

For more information on supported failover modes for your operating system version
and failover software, refer to EMC Knowledgebase solution emc99467.

8. In the Configuration Summary screen, review the configuration and all settings.
9. If the settings are correct, click Next, and if the settings are incorrect, click Back until
you return to the dialog box in which you need to re-enter the correct values.
If you clicked Next, the wizard displays a confirmation dialog box.
10.In the confirmation dialog box, click Yes.
The wizard displays a summary of the values you set for the system.
11.If the operation failed, rerun the wizard.
12.When the operation is successful, click Finish to close the wizard.
13.Reboot the server for the initiator records to take affect.

18
Attaching a Server to a Configuration

Verifying your high-availability Fibre Channel configuration


Use the server high-availability feature in the Unisphere Server Utility to verify your Fibre
Channel configuration is highly available (that is, each Fibre Channel HBA has at least
one active path to each storage processor) and path management software is installed
and running on the server.

Starting the Unisphere Server Utility on an HP-UX server


Procedure
1. Open an hpterm window.
2. Navigate to the Unisphere bin directory:
cd /opt/Unisphere/bin
3. Run the server utility:
./serverutilcli

Using the server utility to verify your high-availability configuration


Procedure
1. From the Unisphere Server Utility's Welcome screen, select option 3 to generate a
report of the server's environment.
The utility determines if the server is configured for high-availability by verifying that
the server has at least one connection path to each system SP, and that PowerPath or
some other failover software, such as DMP, PVLinks, or HP native failover for 11iV3 is
running.
2. Review and resolve any issues reported on the Issues tab of the generated report
before continuing with the installation process.

Configuring your VNX system


To configure your VNX system, use either the Unisphere Service Manager wizards or
Unisphere.

Starting Unisphere
Procedure
1. Log in to a host (which can be a server) that is connected through a network to the
system’s management ports and that has an Internet browser: Microsoft Internet
Explorer, Netscape, or Mozilla.
2. Start the browser.
3. In the browser window, enter the IP address of one of the following that is in the same
domain as the systems that you want to manage:
l A system SP with the most recent version of the VNX Operating Environment (OE)
installed

Note

This SP can be in one of the systems that you want to manage.

Verifying your high-availability Fibre Channel configuration 19


l A Unisphere management station with the most recent Unisphere Server and UIs
installed

Note

If you do not have a supported version of the JRE installed, you will be directed to the
Sun website where you can select a supported version to download. For information
on the supported JRE versions for your version of Unisphere, refer to Environment and
System Requirements in the Unisphere release notes on the EMC Online Support
website.
4. Enter your user name and password.
5. Select Use LDAP if you are using an LDAP-based directory server to authenticate user
credentials.
If you select the Use LDAP option, do not include the domain name.
When you select the LDAP option, the username / password entries are mapped to an
external LDAP or Active Directory server for authentication. Username / password
pairs whose roles are not mapped to the external directory will be denied access. If
the user credentials are valid, Unisphere stores them as the default credentials.
6. Select Options to specify the scope of the systems to be managed.
Global (default) indicates that all systems in the domain and any remote domains can
be managed. Local indicates that only the targeted system can be managed.
7. Click Login.
When the user credentials are successfully authenticated, Unisphere stores them as
the default credentials and the specified system is added to the list of managed
systems in the Local domain.
8. If you are prompted to add the system to a domain, add it now.
The first time that you log in to a system, you are prompted to add the system to a
Unisphere domain. If the system is the first one, create a domain for it. If you already
have systems in a domain, you can either add the new system to the existing domain
or create a new domain for it. For details on adding the system to a domain, use the
Unisphere help.

Committing VNX for Block Operating Environment (OE) software with Unisphere
If you did not install a VNX for Block OE update on the system, you need to commit the
VNX for Block OE software now.
Procedure
1. From Unisphere, select All Systems > System List.
2. From the Systems page, right-click the entry for the system for which you want commit
the VNX for Block OE and select Properties.
3. Click the Software tab, select VNX-Block-Operating-Environment, and click Commit.
4. Click Apply.

Verifying that each LUN is fully initialized using Unisphere


Although the storage group with a new LUN is assigned to the server, the server cannot
see the new LUN until it is fully initialized (completely bound). The time the initialization
process takes to complete varies with the size of the LUN and other parameters. While a
LUN is initializing, it is in a transitioning state, and when the initialization is complete, its
state becomes ready.

20
Attaching a Server to a Configuration

To determine the state of a LUN:


Procedure
1. From Unisphere, navigate to the LUN you want to verify (Storage > LUNs).
2. Right-click the LUN and click Properties.
3. Verify that the state of the LUN is Normal.
If the state is Transitioning, wait for the state to change to Ready before continuing.

Creating storage groups with Unisphere


If you do not have any storage groups created, create them now.
Procedure
1. In the systems drop-down list on the menu bar, select a system.
2. Hosts > Storage Groups.
3. Under Storage Groups, select Create.
4. In Storage Group Name, enter a name for the Storage Group to replace the default
name.
5. Choose from the following:
l Click OK to create the new Storage Group and close the dialog box, or
l Click Apply to create the new Storage Group without closing the dialog box. This
allows you to create additional Storage Groups.
6. Select the storage group you just created and click the Connect hosts.
7. Move the host from Available host to Host to be connected and click OK.

Replacing WWNs of LUNs on an HP-UX 11iv3 server


Procedure
1. On an HP-UX server running 11i v3, discover the names of devices that require new
WWNs with the following command: ioscan -NfnC disk
2. Examine the output of ioscan command for devices with a status NO_HW and
description DGC, and record the /dev/rdisk/devicename entries for each one.
3. For each of the /dev/rdisk/devicename entries you recorded, execute the
following command to replace their WWNs: scsimgr -f replace_wwid -
D /dev/rdisk/devicename

Making LUNs visible to the HP-UX server


To allow the HP-UX server to access LUNs that you created, you must verify that HP-UX
can recognize the LUNs with the following commands: ioscan -fnC disk insf -
eioscan -kfnC disk
If HP-UX does not recognize any LUNs , verify the server's connection to the storage group
with the LUNs.

Verifying that HP-UX native multipath failover sees all paths to the LUNs
Procedure
1. Rescan for disks (LUNs): ioscan –NfC diskinsf -e

Creating storage groups with Unisphere 21


2. View the LUNs available to the server: ioscan –NfnC disk
3. Verify that all of the paths to the system are CLAIMED.

Preparing LUNs to receive data


If you do not want to use a LUN as a raw disk or raw volume, then before HP-UX can send
data to a LUN, HP-UX must recognize the disk, and you must create a volume group on it.
For information on how to perform these tasks, refer to your operating system
documentation.

Sending HP-UX disk information to the system


If the Unisphere Host Agent is installed on the server, stop and then restart it to send the
system the operating system’s device name and volume or file system information for
each LUN that the server sees. Unisphere displays this information in the LUN Properties
— Host dialog box for each LUN.
The Unisphere Server Utility does not send operating system LUN mapping information to
the system, so this procedure is not required.

Starting the host agent


Log in as root and enter the following command:/sbin/init.d/agent start

Verifying that the system received the LUN information using Unisphere
Procedure
1. From Unisphere, select your system.
2. Select Hosts > Hosts List.
3. Select a host and then, on the Details page, click the LUNs tab.
4. Verify that the LUNs tab displays a physical drive and logical drive name for each LUN
on the host.

Verifying your HP–UX 11i v3 native multipath failover


configuration
Before you store data on LUNs, use the procedure in this section to verify that:
u The server can send data to and receive data from the system.
u Native multipath failover shows the paths from the server to the LUN that you expect
for your configuration.

Verifying your dual-SP failover configuration with native multipath software


This test applies to a server with at least one HBA path to each SP on a dual-SP system.

22
Attaching a Server to a Configuration

CAUTION

This test requires that you disconnect all optical cables from the Fibre Channel ports one
of the SPs on the system. When you disconnect the optical cables from one of the SPs,
all LUNs on that SP fail over to the other SP (trespass), which makes the other SP the
only point of data access for all servers connected to the system. Servers without
failover software configured and at least one additional path to the other SP lose access
to their data. To ensure that all servers connected to this system maintain access to their
LUNs during this test, verify through your failover software or Unisphere> that the
servers have at least one path to each SP. To verify that your failover software is
configured to maintain access to data, refer to your operating system documentation for
servers running native failover. For each LUN that fails over to the other SP, you must
manually restore the LUN to its original SP.

Procedure
1. If you are connected to an existing system, stop all applications that are accessing the
system and disable user logins to the server.
2. For each HBA connected to the system:
a. View the LUNs available to the server:ioscan –NfnC disk
b. Choose one available LUN to receive data (I/O) for the test.
c. View the paths device special files (DSF) to the chosen LUN:ioscan –NfnC
lunpath | grep diskdevice
where device is a device name that represents the chosen LUN.
d. Start sending data to a LUN by writing data to it.
e. Identify the path device special file sending data to the LUN by viewing the output
of the iostat –L 5 | grep diskdevice command, and disconnect the
cable to that HBA.
f. View the output of the iostat –L 5 | grep diskx command, and verify
that:
– Data is no longer sent to the affected paths.
– Data continues to be sent on the remaining path to the LUN, indicating that the
failover path was successful and that multipath is working properly.
g. Reconnect the cable that you disconnected from the HBA.
3. If you are connected to an existing system, restart any applications that you stopped
and re-enable any user logins to the server that you disabled.

Verifying your dual-SP failover configuration with native multipath software 23


Copyright © 2010-2014 EMC Corporation. All rights reserved. Published in USA.

Published November, 2014

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.

EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries.
All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).

24