Академический Документы
Профессиональный Документы
Культура Документы
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
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
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
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.
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
4
Attaching a Server to a Configuration
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.
Table 1 Host registration differences between the host agent and the server utility
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.
Note
To verify if the host agent is installed, use the /usr/sbin/swlist command to get
a list of the currently installed 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.
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.
Note
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.
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.
Note
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
Note
Note
10
Attaching a Server to a Configuration
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
Note
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
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
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.
14
Attaching a Server to a Configuration
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.
16
Attaching a Server to a Configuration
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.
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
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
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.
20
Attaching a Server to a Configuration
Verifying that HP-UX native multipath failover sees all paths to the LUNs
Procedure
1. Rescan for disks (LUNs): ioscan –NfC diskinsf -e
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.
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.
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