Top Banner
Here is Your Customized Document Your Configuration is: Attaching a server in a Block configuration Model - VNX5300 Storage Type - VNX for Block (SAN) Connection Type - Fibre Channel Switch or Boot from SAN Server Operating System - Linux Path Management Software - PowerPath Document ID -1319773864593 Reporting Problems To send comments or report errors regarding this document, please email: [email protected]. For Issues not related to this document, contact your service provider. Refer to Document ID: 1319773864593 Content Creation Date Thu Oct 27 23:51:50 EDT 2011
48
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: VNX Attach Server (Linux)

Here is Your Customized Document

Your Configuration is:Attaching a server in a Block configuration

Model - VNX5300Storage Type - VNX for Block (SAN)Connection Type - Fibre Channel Switch or Boot from SANServer Operating System - LinuxPath Management Software - PowerPathDocument ID -1319773864593

Reporting Problems

To send comments or report errors regarding this document,please email: [email protected] Issues not related to this document, contact your service provider.Refer to Document ID:1319773864593Content Creation Date Thu Oct 27 23:51:50 EDT 2011

Page 2: VNX Attach Server (Linux)

This document explains how to attach a Linux Server with EMC® PowerPath® to a VNX5300™in a Fibre Channel switch configuration.

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

If you are an EMCpartner, refer to the EMCServices Partnerwebsite to download theUnisphere™server software mentioned in this guide. The partner site is available from the Navigatordrop-down menu on Powerlink.

Important: If you will configure your system connections to your ESX or Hyper-V server, you must attachthe ESX or Hyper-V server to your system prior to performing the steps in this document. For informationon attaching an ESX or Hyper-V server to your system, generate a new document and select the appropriateESX or Hyper-V server version.

The main topics in this document are:

Before you start........................................................................................................................................................3Installing HBAs in the server.................................................................................................................................5Installing or updating the HBA driver.................................................................................................................7Installing or Updating PowerPath software........................................................................................................9Installing Unisphere server software..................................................................................................................13Connecting the VNX the server in a Fibre Channel switch configuration....................................................26Determining if your server has a supported configuration............................................................................32Registering the server with the system..............................................................................................................34Verifying system health........................................................................................................................................36Configuring your VNX system............................................................................................................................37Preparing LUNs to receive data..........................................................................................................................44Sending Linux disk information to the system.................................................................................................45Verifying your failover configuration with PowerPath...................................................................................46

EMC®

Attaching a Linux Server with EMCPowerPath to a VNX5300 in a Fibre Channel

Switch Configuration

Page 3: VNX Attach Server (Linux)

Before you start

Note: This document covers a Fibre Channel switch configuration only. For information on bootingfrom a SAN, refer to the appropriate Host Connectivity Guide or the EMC Support Matrix on the EMCOnline Support website.

◆ Read the release notes for your system, which are available on the EMC Online Supportwebsite.

◆ You must have a supported Windows host on the same network as the systemmanagement ports. You can use this host:

• As a client in which you launch the Unisphere™ software. This client was formerlyreferred to as the Navisphere®management station.

• To run the Unisphere Service Manager, which runs only on a Windows host.• As an EMC Secure Remote Support (ESRS) IP Client, whichmust be aWindows host,

but cannot be a server (that is, it cannot send I/O to the system data ports).

◆ Youmust have a Unisphere Server with a supported Internet browser that is on the samenetwork as the systemmanagement ports. TheUnisphere Server replaces theNavisphereManagement Server. This host can also be the server or a Unispheremanagement station(formerly referred to as the Navisphere off-array management station). For supportedInternet browsers, see the Unisphere release notes on the EMC Online Support website.

◆ Youmust have an a Linux host, that is or will be a server with Fibre Channel connectionsto the system. This server must have a supported server configuration; that is, it musthave all required updates, such as hot fixes or patches, installed.

◆ You must have one or more supported Fibre Channel host bus adapters (HBAs), whichmay already be installed in the server. These adapters must have the latest supportedBIOS and driver.

We recommend that you do not mix Fibre Channel HBAs from different vendors in thesame server.

◆ Each Fibre Channel front-end port that you will use on the system must have an opticalcable. These cablesmay already be connected for a configurationwith an existing systemor server. We strongly recommend you use OM3 50 μ m cables. For cable specifications,refer to the system's technical specifications. You can generate this user-customizeddocument from the learn link on the system support website(http://www.emc.com/vnxsupport).

◆ Youmust 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 alreadyconnected.We strongly recommend you useOM3 50 μm cables. For cable specifications,refer to system's Technical Specifications . You can generate this document using the usercustomized documentation learn link on the on the system support website(http://www.emc.com/vnxsupport).

Before you start 3

Before you start

Page 4: VNX Attach Server (Linux)

◆ Youmust have a method for writing data to a LUN on the system that will test the pathsfrom the server to the system. You can download an I/O simulator (Iometer) from thefollowing website: http://www.iometer.org/.

4 Attaching a server

Before you start

Page 5: VNX Attach Server (Linux)

Installing HBAs in the server

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

Before you start

To complete this procedure, you will need one or more supported HBAs with the latestsupported BIOS and drivers.

For information on supportedHBAs, BIOS, and drivers, refer to the E-Lab™ InteroperabilityNavigator on the EMC Online Support website.

Note: We recommend that you never mix HBAs from different vendors in the same server.

Installing HBAs

CAUTION

HBAs are very susceptible to damage caused by static discharge and need to be handledaccordingly. Before handling HBAs, observe the following precautions:

◆ Store HBAs in antistatic bags.

◆ Use a ground (ESD) strap whenever you handle HBAs.

◆ Never plug or unplug HBAs with the power on. Severe component damage can result.

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.

Installing HBAs in the server 5

Installing HBAs in the server

Page 6: VNX Attach Server (Linux)

c. If you installed a replacement HBA, reconnect the cables that you removed in theexact 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.

6 Attaching a server

Installing HBAs in the server

Page 7: VNX Attach Server (Linux)

Installing or updating the HBA driver

The server must run a supported operating system and a supported HBA driver. EMCrecommends that you install the latest supported version of the driver.

For information on the supportedHBAdrivers, refer to the E-Lab™ InteroperabilityNavigatoron EMC Online Support website.

Before you start

To complete this procedure, you will need:

◆ 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 maynot be the latest supported version.

For an Emulex driver - You can download the latest supported version and instructionsfor installing the Emulex HBA driver from the vendor’s website:

http://www.emulex.com/products/fibre-channel-hbas.html

For a QLogic driver - You can download the latest supported version and instructions forinstalling the HBA driverkernal driver from the vendor’s website:

http://support.qlogic.com/support/oem_emc.asp

For a Brocade driver - You can download the latest supported version and instructionsfor installing the Brocade HBA driver driver from the vendor’s website:

http://www.brocade.com/services-support/driversdownloads/HBA/HBA_EMC.page

◆ Anyupdates, such as hot fixes or patches to the server’s operating system that are requiredfor the HBA driver version you will install.

For information on any required updates, refer to one of the following:

• E-Lab™ Interoperability Navigator on the EMC Online Support website• The HBA vendor’s website

Installing the HBA driver

1. Install any updates, such as hot fixes or patches, to the server’s operating system that arerequired for the HBA driver version you are installing.

Installing or updating the HBA driver 7

Installing or updating the HBA driver

Page 8: VNX Attach Server (Linux)

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.

5. If the installation program did not prompt you to reboot, then reboot the server whenthe driver installation is complete.

8 Attaching a server

Installing or updating the HBA driver

Page 9: VNX Attach Server (Linux)

Installing or Updating PowerPath software

Important:

If you have a Hyper-V or ESX server, install PowerPath on your Hyper-V or ESX server. Do not installPowerPath on the virtual machine.

Install PowerPath by referring to the appropriate PowerPath Installation and AdministrationGuide for your operating system. This guide is available on the EMCOnline Supportwebsite.

Check the PowerPath software download section on the EMC Online Support website fora more recent version of PowerPath or a patch to the version of PowerPath installed on theserver. If a more recent version exists, install it, as described in the appropriate PowerPathInstallation and Administration Guide for your operating system. This guide is available onthe EMC Online Support website. If the server is running the most recent version and apatch exists for this version, install it, as described in the readme file that accompanies thepatch.

Before you install PowerPath

1. If the Unisphere™ Host Agent is running on the server, then before installing a fullPowerPath release or a PowerPath patch, stop the host agent:

/etc/inint.d/naviagent stop

2. Save your Linux kernel and back up your system.

3. Change the Linux kernel, as described in Changing the kernel on a Linux server on page9.

4. Change the Linux configuration files, as described in Modifying configuration files on aRed Hat server on page 10 or Modifying configuration files on a Linux SuSE server onpage 11.

Changing the kernel on a Linux server

1. If you load theHBAs driver as amodule, install its binary file in the appropriate location:

Red Hat Linux Location

/lib/modules/'uname -r'/drivers/addon/hba_driver

where

uname -r is the string returned to the console by the uname -r command

Installing or Updating PowerPath software 9

Installing or Updating PowerPath software

Page 10: VNX Attach Server (Linux)

hba_driver is the name of the HBA driver module.

SuSE Linux Location

/lib/modules/' uname -r'/drivers/scsi

where

uname -r is the string returned to the console by the uname -r command.

Note: If you have RedHat Linux 3.0 or SuSE Linux SLES 8 SP3 or later, you no longer need to buildthe HBA driver modules and copy them to the above location. The prebuilt kernel now includesthese modules.

2. Save your kernel change.

Modifying configuration files on a Red Hat server

Modify the configuration file on the server as follows:

For Brocade HBAs

Edit the /etc/modprobe.conf file as described in your HBA vendor documentation.

For QLogic HBAs

Edit the /etc/modprobe.conf file to make sure that the ql2xfailover and theConfigRequired parameters are set to 0:

options qla2xxx q12xfailover=0 ConfigRequired=0

Note: The variable x and xxx vary with the HBA model.

For Emulex HBAs

Edit the /etc/modprobe.conf file to set the value of the lpfc_nodev_tmo parameter to10:

options lpfc lpfc_nodev_tmo=10

Saving kernel changes on a Red Hat server

1. Run ls -l /boot and look at the line with initrd -> to determine which initrd file isused.

2. Run the uname -r to display the kernel version.

3. Enter:/sbin/mkinitrd -f -v initrd kernel

where

10 Attaching a server

Installing or Updating PowerPath software

Page 11: VNX Attach Server (Linux)

initrd is the configuration identified by ls -l /boot

kernel is the kernel version displayed by uname -r

For example,

/sbin/mkinitrd -f -v initrd-2.6.9-24.img 2.6.9-24

4. Verify that the .img file you created is under the /boot directory and that the initrdentry of /boot/grub/grub.conf specifies this .img file.

Verifying the HBA driver on a SuSE server

Verify that theHBAdriver is always loaded after the internal SCSI adapter driver as specifiedby the /etc/sysconfig/kernel file. For example, in the following file, driver_module(the HBA driver module for accessing the system) is always loaded after all internal SCSIdrivers are loaded:

INTINRD_MODULES="scsi_mod sd_mod cciss reiserfs driver_module_module "

Note: When loading HBA drivers into the ramdisk, make sure that the HBA module name used in/etc/sysconfig/kernel is the same as that used in the /etc/modules.conf file.

Modifying configuration files on a Linux SuSE server

For Brocade HBAs

Edit the /etc/modprobe.conf file as described in your HBA vendor documentation.

For Emulex HBAs

Edit the /etc/modprobe.conf.local file by setting the value of the lpfc_nodev_tmoparameter to 10:

options lpfc lpfc_nodev_tmo=10

For QLogic HBAs

Make sure that the ql2xfailover and the ConfigRequired parameters are set to 0:

options qla2xxx q12xfailover=0 ConfigRequired=0

Note: The variables x and xxx vary with the HBA model.

Saving kernel changes on a SuSE server

1. Run uname -r to display the kernel version.

Before you install PowerPath 11

Installing or Updating PowerPath software

Page 12: VNX Attach Server (Linux)

2. Run ls -l /boot to determine which initrd and vmlinuz files are used for the kernelversion.

The names of both the initrd and vmlinuz files include the kernel version.

3. Enter: /sbin/mk_initrd -k vmlinuz -i initrd

where vmlinuz and initrd correspond to the configuration identified by ls - boot forthe kernel version.

12 Attaching a server

Installing or Updating PowerPath software

Page 13: VNX Attach Server (Linux)

Installing Unisphere server software

This section describes how to install Unisphere server software.

If youplan to installNavisphereCLI orAdmsnap, youmust install themon a virtualmachine.For instructions on installing these software programs on a virtualmachine , generate a newdocument and select the operating system running on the virtual machine.

Before you begin

Refer to the sections below to determinewhich application to install for host registrationand the requirements for installing each of these applications.

◆ To run Unisphere server software, your server must meet the requirements outlinedin Requirements for Unisphere server software on page 13.

◆ To determinewhether to install theUnisphereHost Agent or Unisphere Server Utilityto register your HBAs with the system, refer to Determining whether to install theUnisphere Host Agent on page 14.

Installing Unisphere server software

Depending onwhichUnisphere server software you are installing, refer to the appropriatesection below.

◆ Unisphere Host Agent – see Installing the Unisphere Host Agent.

◆ Unisphere Server Utility – see Installing the Unisphere Server Utility.

◆ Navisphere CLI – see Installing Navisphere CLI.

◆ Admsnap Utility – see Installing the Admsnap Utility.

Requirements for Unisphere server software

To run Unisphere server software, your server must meet the following requirements:

◆ Run a supported version of the Linux operating system.◆ For Fibre Channel connections, have the EMCVNX supportedHBAhardware and driver

installed.◆ 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.◆ 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.

Installing Unisphere server software 13

Installing Unisphere server software

Page 14: VNX Attach Server (Linux)

The TCP/IP network connection allows the server to send LUNmapping information tothe system and it allows Unisphere or Navisphere CLI to communicate with the systemover the network.

◆ Have a configured TCP/IP network connection to any remote hosts that you will use tomanage the systems, including:

• any server whose browser you will use to access Unisphere,• a supported Windows server running Unisphere Server software (replaces the

Navisphere Management Server software),• any AIX, HP-UX, Linux, VMware ESX Server, NetWare, Solaris, or Windows server

running Navisphere CLI.

If you want to use Navisphere CLI on the server to manage systems on a remote server, theserver must be on a TCP/IP network connected to both the remote server and each SP in thesystem. The remote server can be running AIX, HP-UX, Linux, Solaris, or the Windowsoperating system.

Note: For information about the specific revisions of the server operating system and the systemFLAREand Access Logix™ software that are required for your version of the host agent, see the release notesfor 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:

◆ Monitor system events and notify personnel by e-mail, page, or modem when anydesignated event occurs.

◆ Retrieve LUN world wide name (WWN) and capacity information from Symmetrix®systems.

◆ Register the server’s HBAs with the system.

Alternatively, you can use the Unisphere Server Utility to register the server’s HBAswith the system. Table 1 on page 15 describes the host registration differences betweenthe host agent and the server utility.

14 Attaching a server

Installing Unisphere server software

Page 15: VNX Attach Server (Linux)

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

Unisphere Server UtilityUnisphere Host AgentFunction

No – LUN mapping information is not sent to thesystem. Only the server’s name, ID, and IP addressare sent to the system.

Yes – LUN mapping information isdisplayed in the Unisphere UI next tothe LUN icon or with the CLI usingthe lunmapinfo command.

Pushes LUN mapping and OSinformation to the system.

Note: The text Manually Registeredappears next to the hostname icon in the UnisphereUI indicating that the host agent was not used toregister this server.

No – You must manually update the information bystarting the utility or you can create a script to run

Yes – No user interaction is required.Runs automatically to send in-formation to the system.

the utility. Since you run the server utility on de-mand, you have more control as to how often orwhen the utility is executed.

No – LUN mapping information is not sent to thesystem. Note that if you are using the server utility

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

Requires network connectivityto the system.

to upload a high-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 a Linux server

We recommend that you download and install the most recent version of the UnisphereHost Agent software from the EMC Online Support website.

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

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 notfunction properly.

3. At a command line prompt, look for an existing host agent and CLI package using thefollowing command:

rpm -qa | grep navi

Installing the Unisphere Host Agent 15

Installing Unisphere server software

Page 16: VNX Attach Server (Linux)

If an earlier version of the naviagent or naviagentcli software package is listed, youmustremove it before installing the new host agent and CLI package.

4. Download the software:

a. From the EMC Online Support website, select the VNX Support by Product page andlocate the Software Downloads.

b. Select the UnisphereHost Agent, and then select the option to save the zip file to yourserver.

c. At the command line prompt, navigate to the directory where you saved the zip fileand unzip the file:

unzip Navi_Agent_CLI_Linux-version.zip

where version is the version listed in the filename.

5. Depending on which version you are installing, enter one of the following commandsto install the software:

◆ 32-bit server –

rpm -ivh UnisphereHostAgent-Linux-32-noarch-en_US-version-build.noarch.rpm

◆ 64-bit server –

rpm -ivh UnisphereHostAgent-Linux-64-x86-en_US--version-build.x86_64.rpm

where version and build are the version number and the build number of the software.

Note:

If you have an IA64 system, you must install the 32–bit package and 32–bit OS compatibilitypackages. The 64–bit package is currently supported on x86_64 systems only. Refer to the releasenotes for any updates.

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

6. Verify that host agent and/or CLI are installed: rpm -qa | grep navi

Note: Before you can use the host agent or CLI, youmustmodify the user login scripts and configurethe host agent configuration file.

16 Attaching a server

Installing Unisphere server software

Page 17: VNX Attach Server (Linux)

Modifying user login scripts

To use navicli command at the root prompt without typing a leading ./ before thecommands (for example, ./navicli getagent ), youmustmodify the $PATH environmentvariable in the user login script.

Follow the steps below to modify the environment variable PATH:

1. Add /opt/Unisphere/bin to $PATH: PATH=$PATH:/opt/Unisphere/bin; exportPATH

a. Verify the path with the command:

echo $PATH

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

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

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

3. If you are setting up a new server, go to Starting and stopping the Unisphere Host Agenton page 19.

If you are just upgrading the host agent or CLI on an existing system, you have finishedthe upgrade.

Configuring the Unisphere Host Agent

Verify that the host agent configuration file includes a privileged user, as described inAddingprivileged users on page 17

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 mustinclude an entry that defines the person who will issue the CLI commands as a privilegeduser.

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

Installing the Unisphere Host Agent 17

Installing Unisphere server software

Page 18: VNX Attach Server (Linux)

For a local user:

user name

For a remote user:

user name@hostname

where name is the person's account name and name@hostname is the name of the remoteserver the person will be using.

The default host agent configuration file includes a user root entry.

Saving the host agent configuration file

1. If you have finished adding information to the host agent configuration file, save thehost agent configuration file.

2. Stop and restart the host agent by entering the following commands:

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

Using the event monitor configuration file

TheUnisphereHost Agent canmonitor system events and take such action as sending e-mailor paging you if specified events occur.

The event monitor that ships with Unisphere provides an interactive way to define theseevents and actions. If you do not have event monitor, you can still define such events andactions 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 actionsyou want taken if the events occur. You can test the file after editing it using the NavisphereCLI command responsetest, as explained in theNavisphere Command Line Interface Reference.

18 Attaching a server

Installing Unisphere server software

Page 19: VNX Attach Server (Linux)

Running the Unisphere Host Agent

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

Starting and stopping the Unisphere Host Agent

The host agent starts automatically when you bring the server up to init level 3. When youfirst start the host agent, look at the system log for the server’s operating system to makesure the agent started and no device errors occurred.

The system log is located in /var/log/messages.

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 agenttaking several minutes to execute a systemmanagement task. This behavior is most evident when onehost agent is managing multiple systems. Also, if the SP event log is large and the host agentconfiguration file is set up to read all events, it may take a few minutes for the host agent to start.

Starting the host agent on a Linux server

◆ Log in as root and enter the following command: /etc/init.d/hostagent start

Stopping the host agent a Linux server

◆ Log in as root and enter the following command:

/etc/init.d/naviagent stop

Testing the host agent connections

Before continuing, you should test the host agent connections as follows:

1. Start the host agent as described in .

2. Look for any errors on the console and in the operating system log tomake sure the agentstarted 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).

Running the Unisphere Host Agent 19

Installing Unisphere server software

Page 20: VNX Attach Server (Linux)

-h hostname is the IP address of the SP.

For each HBA in the server, a listing similar to the following will be displayed. Forsystems in a SAN (shared storage) environment, the listing includes HBAs in allconnected hosts.

Information about each HBA:HBA UID: 10:00:00:60:B0:3E:46:AC:10:00:00:60:B0:3E:46:ACServer Name: siux134Server IP Address: 128.221.208.134HBA Model Description:HBA Vendor Description:HBA Device Driver Name:Information about each port of this HBA:SP Name: spaHBA Devicename: sp0Trusted: NOLogged In: YESSource ID: 1Defined: YESInitiator Type: 0Storage Group Name:Storage Group 134

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 agentevents 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 agentshutdown, and errors that might occur, such as the host agent’s inability to access a devicein the configuration file. If problems occur, log files are a good place to start yourtroubleshooting.

Host agent events and errors are logged in /var/log/agent.log. System events arelogged in /var/log/messages.

Installing the Unisphere Server Utility

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

Installing the Unisphere Server Utility on a Linux server

We recommend that you download and install the most recent version of the UnisphereServer Utility software from the applicable support by product page on the EMC OnlineSupport website.

1. Log in to the root account.

20 Attaching a server

Installing Unisphere server software

Page 21: VNX Attach Server (Linux)

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

rpm -qi naviserverutil or rpm -qi serverutilcli

3. If an earlier version of the software has been installed, you must remove it beforecontinuing.

rpm -e naviserverutil or rpm -qi serverutilcli

4. Download the software:

a. From the EMC Online Support website, select the VNX Support by Product page andlocate the Software Downloads.

b. Select the Unisphere Server Utility, and then select the option to save the zip file toyour server.

c. At the command line prompt, navigate to the directory where you saved the zip fileand unzip the file.

d. Install the software:

◆ 32-bit server –

rpm -ivh UnisphereServerUtil-Linux-32-x86-en_US-version–build.platform.rpm

where version and build are the version number and the build number of theserver utility and platform is your Linux platform number (for example, i386 oria64).

◆ 32-bit Power Linux server –

rpm -ivh UnisphereServerUtil-Linux-32-powerpc-en_US-version–build.ppc64.rpm

where version and build are the version number and the build number of thesoftware.

◆ 64-bit server –

rpm -ivh UnisphereServerUtil-Linux-64-x86-en_US-version–build.x86_64.rpm

where version and build are the version number and the build number of thesoftware.

Note:

If you have an IA64 system, you must install the 32–bit package. The 64–bit package iscurrently supported on x86_64 systems only. Refer to the release notes for any updates.

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

Installing Unisphere server software 21

Installing Unisphere server software

Page 22: VNX Attach Server (Linux)

◆ SuSE ia64 servers –

UnisphereServerUtil-Linux-32-suse-en_US-version-build.platform.rpm

where version and build are the version number and the build number of theserver utility and platform is your Linux platform number (for example, i386,ia64, or x86-64).

The installation process adds a line to the /etc/rc.d/rc.local file that starts the serverutility on reboot, provided root has execute permission for the /etc/rc.d/rc.local file.

Installing Navisphere Secure CLI

This section describes how to install Navisphere Secure CLI.

You can install Navisphere CLI on either the server or virtual machine.

Installing the Navisphere Secure CLI on a Linux server or Linux virtual machine

We recommend that you download and install the most recent version of the NavisphereSecureCLI software from the applicable support by product page on the EMCOnline Supportwebsite.

1. Log in to the root account.

2. If your server is behind a firewall, open the TCP/IP ports listed in Table 2 on page 22.

These ports are used by Navisphere CLI. If these ports are not opened, the software willnot function properly.

Table 2. TCP/IP ports

TCP/IP portsSoftware

443, 2163Secure CLI

3. At the command line prompt, look for any existing CLI by typing: rpm -qi navicli

If an earlier version of the software has been installed, you must remove it beforecontinuing.

4. Download the software:

a. From the EMC Online Support website, select the VNX Support by Product page andlocate the Software Downloads.

22 Attaching a server

Installing Unisphere server software

Page 23: VNX Attach Server (Linux)

b. Select the Navisphere Secure CLI, and then select the option to save the zip file toyour server.

c. At the command line prompt, navigate to the directory where you saved the zip fileand unzip the file.

d. Install the software:

◆ 32-bit server –

rpm -ivh NaviSecureCLI-Linux-32-noarch-language-version-build.noarch.rpm

◆ 32-bit Power Linux server –

rpm -ivh NaviSecureCLI-Linux-32-powerpc-language-version-build.ppc64.rpm

◆ 64-bit server –

rpm -ivh NaviSecureCLI-Linux-64-x86-language-version-build.x86_64.rpm

where

language is either en_US, when only the English version is available, or loc, whenthe localized versions are available (including English).

version and build are the version number and the build number of the software.

Note:

If you have an IA64 system, youmust install the 32–bit package. The 64–bit package is currentlysupported on x86_64 systems only. Refer to the release notes for any updates.

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

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

5. Verify that Navisphere Secure CLI is installed by using the rpm -qa | more command.

Installing the Admsnap Utility

To access snapshots of LUNs in the system, install the Admsnap Utility.

Installing the Admsnap Utility 23

Installing Unisphere server software

Page 24: VNX Attach Server (Linux)

You can install admsnap on the server or on the virtual machine.

Installation prerequisites

Before you can install and use the Admsnap Utility, you must install SnapView on asupported system.

For a list of supported systems, refer to the release notes for SnapView and admsnap.

Installing the Admsnap Utility on a Linux server or a Linux virtual machine

We recommend that you download and install the most recent version of the AdmsnapUtility software from the applicable support by product page on the EMC Online Supportwebsite.

1. Log in as root or as a member of an administrative group.

2. Open a terminal window and enter the following command to list any admsnap packagethat may be currently installed: rpm -qi admsnap

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

If an earlier version is installed, remove it.

4. Download the software:

a. From the EMC Online Support website, select the VNX Support by Product page andlocate the Software Downloads.

b. Select the Admsnap Utility version you want to download and select the option tosave the zip file to your server.

c. At the command line prompt, navigate to the directory where you saved the zip fileand unzip the file.

unzip admsnap_ version.zip

where version is the version listed in the filename.

d. Install the software:

◆ Linux server:

rpm -ivh admsnap-Linux-32-x86-en_US-version-build.rpm

◆ Power Linux server:

rpm -ivh admsnap-Linux-32-powerpcen_US-version-build.rpm

where version and build are the version number and the build number of thesoftware.

24 Attaching a server

Installing Unisphere server software

Page 25: VNX Attach Server (Linux)

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

The following files are installed in the /usr/admsnap directory:

/usr/admsnap/admsnap

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

/usr/admsnap/readme

5. Verify that the correct version of admsnap is installed by entering the following command:/usr/admsnap/admsnap help

This commanddisplays amessage about the help command,which includes the revisionnumber of the installed admsnap software.

6. Configure MANPATH to access the Linux man pages. Edit the /etc/man.config fileby adding the following lines: MANPATH /usr/admsnap/man

7. Configure sg devices by using the MAKEDEV utility.

For information on how to use theMAKEDEVutility, refer to theMAKEDEVmanpages.

Installing Unisphere server software 25

Installing Unisphere server software

Page 26: VNX Attach Server (Linux)

Connecting the VNX the server in a Fibre Channel switchconfiguration

Use optical cables to connect switch ports to the VNX Fibre Channel host ports and to FibreChannel 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 fromthe Learn about system link on the VNX support website or from EMC Online Supportwebsite.

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

Identifying VNX Fibre-Channel host ports for server connections

You can connect servers to the VNX onboard Fibre Channel host ports 2 and 3 and to anyports (0, 1, 2, 3) on the UltraFlex™ Fibre Channel I/O modules in slots A0 and B0 or A1 andB1. Figure 1 on page 27 shows the location of the onboard ports and of the slots for I/Omodule with host ports.

26 Attaching a server

Connecting the VNX the server in a Fibre Channel switch configuration

Page 27: VNX Attach Server (Linux)

Note: In a VNX Unified system or a VNX for File system the onboard Fibre Channel ports 4 and 5 arefor blade connections.

Figure 1. Onboard Fibre Channel host ports and slots for I/O modules with host ports in aVNX5300 (FC and iSCSI modules shown)

Module labels and FE port connectors

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

FE port connectivity

The Fibre FE ports on an 8 Gb/s Fibre Channel I/O module supports 2/4/8 Gb/sconnectivity. You cannot use the FE ports on an 8 Gb/s Fibre Channel I/O module in a 1Gb/s Fibre Channel environment.

Handling optical cables

Optical cables are susceptible to damage, so take the following precautions when handlingthem:

◆ Keep the covers on all optical cables until you are ready to insert them.◆ Avoid tight bends. If you need to make a 90° bend, do it over 6 to 12 inches.◆ Do not use optical cables to support weight (including their own unsupported weight if

they are long).◆ Do not pull long runs of cable; instead, lay the cable in place or pull only a few feet at a

time.◆ Place the cables where no one can step on them or roll equipment over them.

Handling optical cables 27

Connecting the VNX the server in a Fibre Channel switch configuration

Page 28: VNX Attach Server (Linux)

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 onthe switch and connect the same number of Fibre Channel host ports on SP B to ports onsame 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:

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 Unisphereonline help.

Note: The MirrorView/A and MirrorView/S applications require onboard port 2. The SAN Copyapplicationmay restrict or require the use of certain SP ports. Refer to the application documentationfor specific cabling information.

2. Remove the protective cover from the FC host port connector on the SP and from oneend of the optical cable, and plug the cable into the host port connector (Figure 2 on page29 and Figure 3 on page 29).

28 Attaching a server

Connecting the VNX the server in a Fibre Channel switch configuration

Page 29: VNX Attach Server (Linux)

3. Remove the protective cover from the optical connector on the switch port that you willuse and from the free end of the optical cable, and plug the cable into the switch port(Figure 2 on page 29 and Figure 3 on page 29).

Figure 2. Connecting an optical cable

Figure 3. Sample cabling between a VNX5300 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 portson the switch and connect the same number of HBA ports to ports on same switch or onanother switch, if two switches are available.

For each server HBA port that you will use for I/O with the VNX:

1. Remove the protective cover from the FC switch port connector and from one end of theoptical cable, and plug the cable into the connector.

Cabling the switch ports to the server HBA ports (if necessary) 29

Connecting the VNX the server in a Fibre Channel switch configuration

Page 30: VNX Attach Server (Linux)

2. Remove the protective cover fromthe server HBA port connector and from the free endof the optical cable, and plug the cable into the HBA port connector (Figure 4 on page30).

Figure 4. Sample cabling for a Fibre Channel switch configuration

Zoning the switches

Use switch management software to update switch software and zone switches that are nothard zoned.

We recommend single-initiator zoning as a best practice. In single-initiator zoning eachHBAport has a separate zone that contains it and the SP ports with which it communicates. Forinformation on Fibre Channel topologies, refer to the EMCNetworked Storage Topology Guideon the EMC Online Support website.

Important: For Linux servers, you must use single-initiator and single-target zoning. A single-initiatorsingle-target zone has HBA port and one VNX SP port. You can share SP ports among HBA ports,provided each HBA port is in its own zone.

To zone the switch:

1. Connect the switch management ports to the network from which you will manage theswitches.

30 Attaching a server

Connecting the VNX the server in a Fibre Channel switch configuration

Page 31: VNX Attach Server (Linux)

2. If the switches are not running the most recent supported firmware version, install thissoftware from the switch vendor's website.

Note: For information on the supported switch firmware versions, see the E-Lab™ InteroperabilityNavigator on the EMC Online Support website.

3. Use either the zoningwizardCD that shippedwith the switch or the switchmanagementsoftware to set up the appropriate switch zones.

a. To use the zoning wizard CD – Using the instructions provided with the CD, run thezoning wizard and select the zone configuration that is applicable to the way thatyou 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 switchmanagement software from the switch vendor's website, and follow the instructionsprovided for the software to setup the zones that are applicable to the way that youconnected the VNX Fibre ports and the server HBA ports to the switch.

Connecting the VNX the server in a Fibre Channel switch configuration 31

Connecting the VNX the server in a Fibre Channel switch configuration

Page 32: VNX Attach Server (Linux)

Determining if your server has a supported configuration

Before you can determine if your server has a supported configuration, you need to knowthe 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-LabInteroperabilityNavigator on page 32, . If you do not have this information, you can generatea server configuration report for your server using the Unisphere Server Utility.

Starting the Unisphere Server Utility on a Linux server

1. Open a console window.

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

/opt/Unisphere/bin/serverutilcli

Generating a high-availability report for a server

1. In the Unisphere Server Utility, select option 3 from the server utility's Welcome screento generate a resport of the server's environment.

This option detects if PowerPath® or some other failover software, such as DMP, isrunning. The utility will not detect any other native failover software, such as Linuxnative multipath (MPIO).After the verification, the utility generates a summary reportand saves it to the server.

2. In the summary report, select the Checklist tab to view the information about the serverthat you need to compare with the E-Lab™ Interoperability Navigator information.

Verifying a server's configuration with E-Lab Interoperability Navigator

1. From your web browser, go to the EMC Online Support website and log in.

2. If required, register and create a username and password.

3. Select E-Lab Interoperability Navigator on the EMC Online Support websiter from theTools menu on the right-side of the home page.

32 Attaching a server

Determining if your server has a supported configuration

Page 33: VNX Attach Server (Linux)

4. From the E-Lab Interoperability Navigator page, select Launch E-Lab InteroperabilityNavigator and then select the Wizards tab.

5. From the drop-down menu, select the CLARiiON Wizards.

6. In Select a wizard, select Host Attach Wizard.

7. For each step of thewizard, provide the requested information based onwhat is installedon the server or what you intend to install on the server.

If the configuration you entered is invalid, an additional step appears in the wizard anda Results, EMC Support Statements pane appears on the right with information to helpyou provide the requested information in the additional step.

If the configuration you entered is valid, a Results link appears on the right.

8. Click the Results link appears to view a report that contains information about theconfiguration you entered.

9. Print and/or save a copy of the report.

10. Close the E-Lab™ Interoperability Navigator.

11. Compare this report to either the information that you know about your server softwareor the checklist report you generated with the server utility.

12. If your server software versions and/or patches or hot fixes are not listed in the HostAttach Wizard report, you must upgrade to a supported version or patch beforecontinuing.

Note: TheHost Attach Wizard displays only options that EMC supports. If any of the configurationinformation on the server utility's high-availability report cannot be found in the wizard, thenEMC does not support it.

Determining if your server has a supported configuration 33

Determining if your server has a supported configuration

Page 34: VNX Attach Server (Linux)

Registering the server with the system

Important:

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

Youmust run the Unisphere Server Utility on each server connected to the system to registerthe server's HBAs with the system.

Running the Unisphere Server Utility on a Linux server

You can run the Unisphere Server Utility from the server.

Important:

If you have a Hyper-V or ESX server, perform this procedure on your Hyper-V or ESX server. Forupdates on SCSI pass through support for virtual machines with FC devices, refer to the E-LabInteroperability Navigator on the EMC Online Support website.

Starting the Unisphere Server Utility on a Linux server

1. Open a console window.

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

/opt/Unisphere/bin/serverutilcli

Registering the Linux server using the Unisphere Server Utility

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

3. In the server utility, enter u to register the server with each system the utility found.

34 Attaching a server

Registering the server with the system

Page 35: VNX Attach Server (Linux)

The utility sends the server’s name and IP address to each system. Once the server hasstorage on the system, the utility also sends the Linux device name and volume or filesystem 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.

Starting the Unisphere Host Agent

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

Starting the host agent on a Linux server

◆ Log in as root and enter the following command: /etc/init.d/hostagent start

Verifying HBA registration using Unisphere

1. From Unisphere, select All Systems ➤ System List.

2. From the Systems page, right-click the entry for the system for which you want to verifyHBA registration, and click Connectivity Status.

3. In the Host Initiators tab, select the initiator name, and then click Edit.

4. Verify that the server to SP port connection is displayed as Yes under the Registeredcolumns.

Once all HBAs belonging to the server are registered, you can assign the server to storagegroups.

5. Click Cancel and then OK to close the Connectivity Status dialog box.

Starting the Unisphere Host Agent 35

Registering the server with the system

Page 36: VNX Attach Server (Linux)

Verifying system health

Use the system verification wizard that is part of the Unisphere Service Manager (USM),which replaces the Navisphere Service Taskbar, to:

◆ Validate the connectivity of the system hardware components◆ Verify back-end functionality◆ Verify the status of all field-replaceable units◆ Analyze system logs

1. If you do not have the Unisphere Service Manager running:

a. Download and install the Unisphere Service Manager from the EMCOnline Supportwebsite to a Windows management station that is connected to the system'smanagement ports. If you do not have a Windows management station, your serviceprovider 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 theinstructions that appear.

4. Review the report that the wizard generates, and if it lists any problems, try to resolvethem.

36 Attaching a server

Verifying system health

Page 37: VNX Attach Server (Linux)

Configuring your VNX system

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

Starting Unisphere

1. Log in to a host (which can be a server) that is connected through a network to the system’smanagement 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 samedomain as the systems that you want to manage:

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

◆ A Unisphere management station with the most recent Unisphere Server and UIsinstalled

Note: If you do not have a supported version of the JRE installed, you will be directed to the Sunwebsite where you can select a supported version to download. For information on the supportedJRE versions for your version of Unisphere, refer to Environment and System Requirements in theUnisphere 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 usercredentials.

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 anexternal LDAP or Active Directory server for authentication. Username / password pairswhose roles are not mapped to the external directory will be denied access. If the usercredentials are valid, Unisphere stores them as the default credentials.

6. Select Options to specify the scope of the systems to be managed.

Configuring your VNX system 37

Configuring your VNX system

Page 38: VNX Attach Server (Linux)

Global (default) indicates that all systems in the domain and any remote domains can bemanaged. Local indicates that only the targeted system can be managed.

7. Click Login.

When the user credentials are successfully authenticated, Unisphere stores them as thedefault credentials and the specified system is added to the list of managed systems inthe 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 aUnisphere domain. If the system is the first one, create a domain for it. If you alreadyhave systems in a domain, you can either add the new systemto the existing domain orcreate a new domain for it. For details on adding the system to a domain, use theUnisphere help.

Configuring the system cache with Unisphere

1. From Unisphere, select All Systems ➤ System List.

2. From the Systems page, right-click the entry for the system forwhich youwant configurecache and select Properties.

3. Click the SP Memory tab.

4. Set the write cache memory size.

Note: Refer to the Unisphere online help for recommended write cache sizes.

5. Set the read cache memory size.

6. Click Apply.

7. Click the SP Cache tab, and select SP A Read Cache, SP B Read Cache, Write Cache(Enabled), and Enable Watermarks.

8. Set the low watermark to 60% and the high watermark to 80%.

9. Click Apply.

38 Attaching a server

Configuring your VNX system

Page 39: VNX Attach Server (Linux)

Enabling storage groups with Unisphere

You must enable storage groups using Unisphere if only one server is connected to thesystem and you want to connect additional servers to the system.

1. From Unisphere, select All Systems ➤ System List.

2. From the Systems page, right-click the icon for the system, and click Properties.

3. Click the General tab, and select Storage Groups.

4. Click OK.

Allocating storage on a new system with the Unisphere StorageProvisioning Wizard

Important:

If you have a Hyper-V or ESX server, perform this procedure on your Hyper-V or ESX server.

1. From Unisphere, select All Systems ➤ System List.

2. From the Systems page, select a system.

3. Select the Storage tab.

4. Under LUNs, select the Storage Provisioning Wizard.

5. On the Select Servers page, select Assign LUNs to the Servers, and select the servers thatwill have access to the new LUNs.

6. Select the system in which the new LUNs will reside.

7. Create a LUN:

a. Select a pool or RAID group in which to create a LUN, or create a new pool for theLUN.

We recommend you use an existing pool or create a pool instead of a RAID groupbecause a pool supports options, such as Fully Automated Storage Tiering (FAST)and Thin Provisioning, which a RAID group does not support.

Enabling storage groups with Unisphere 39

Configuring your VNX system

Page 40: VNX Attach Server (Linux)

b. If you are creating a pool LUN and you want the LUN to be a thin LUN, select ThinLUN.

The Thin LUN option is available only if the Thin Provisioning enabler is installed.To learn about pools and thin LUNs, click the ? icon next to Thin LUN.

c. Select the properties for the LUN.

d. Add the LUNs to a user-defined folder or do not place them in a folder.

e. Click Finish to create the LUN.

8. Verify that the serverwas assigned to the storage group containing the LUNs you created:

◆ If you know the name of the storage group inwhich the LUNs reside, fromUnisphere,select Storage ➤ Storage Groups.

◆ If you know the name of the server to which the storage group is assigned, fromUnisphere, select Storage ➤ LUNs and confirm that the new LUNs are listed.

If you do not see any of the LUNs you just created, youmay not have selected the AssignLUNs to a server option in the Select Servers page of the Storage Provisioning wizard.You can use the Storage Assignment wizard to assign the LUNs to a server.

9. Create a hot spare (a RAID group with a hot spare RAID Type) as described in theUnisphere online help.

Note: A pool LUN (thick or thin LUN) cannot be a hot spare.

A hot spare is a single disk that serves as a temporary replacement for a failed disk in aRAID 6, 5, 3, 1, or 1/0 storage pool. Data from the failed disk is reconstructed automaticallyon the hot spare from the parity or mirrored data on the working disks in the LUN, sothe data on the LUN is always accessible.

Allocating storage to an existing system with the Storage Provisioningwizard in Unisphere

Important:

If you have a Hyper-V or ESX server, perform this procedure on your Hyper-V or ESX server.

Use the Provisionwizard in theUnisphere to create system storage and provide server accessto this storage:

40 Attaching a server

Configuring your VNX system

Page 41: VNX Attach Server (Linux)

1. From Unisphere, select All Systems ➤ System List.

2. From the Systems page, select a system.

3. Select the Storage tab.

4. If you need additional LUNs for the server, use the Storage Provisioning wizard fromthe LUNs category to create them.

5. If you want to assign existing LUNs to the server, use the Storage Assignment wizardfrom the Storage Groups category to assign them.

Note: For high availability, a host can connect to only one storage group per system at a time. Ifyou connect a host that is already connected to another storage group, the host will disconnectfrom the first storage group. When you disconnect a host from a storage group, and then connectit to a different storage group, the host can no longer perform I/O to the first storage group.

6. Verify that the serverwas assigned to the storage group containing the LUNs you created.

◆ If you know the name of the storage group in which the LUNs reside —FromUnisphere, select Storage ➤ Storage Groups.

◆ If you know the name of the server to which the storage group is assigned —FromUnisphere, select Storage ➤ LUNs and confirm that the new LUNs are listed.

If you do not see any of the LUNs you just created, youmay not have selected the AssignLUNs to a server option in the Select Servers page of the Provision wizard. You can usethe Storage Assignment wizard to assign the LUNs to a server.

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 seethe new LUN until it is fully initialized (completely bound). The time the initializationprocess takes to complete varies with the size of the LUN and other parameters. While aLUN is initializing, it is in a transitioning state, and when the initialization is complete, itsstate becomes normal.

To determine the state of a LUN:

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 Normal before continuing.

Verifying that each LUN is fully initialized using Unisphere 41

Configuring your VNX system

Page 42: VNX Attach Server (Linux)

Creating a storage groups with Unisphere

If you do not have any storage groups created, create them now.

1. In the systems drop-down list on the menu bar, select a system.

2. Select Storage ➤ Storage Groups.

3. From the task list, under Storage Groups, select Create Storage Group.

4. In Storage Group Name, enter a name for the Storage Group to replace the default name.

5. Choose from the following:◆ Click OK to create the new Storage Group and close the dialog box, or◆ 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.

Making LUNs visible to a Linux server

To allow the Linux server to access the LUNs that you created, enter the following commands:

For a server with HBA connections to the system:

rmmod driver_module

modprobe driver_module (or insmod driver_module)

where driver_module is the driver module name.

Verifying your failover configuration with PowerPath for a Linux server

1. If you are connected to an existing system, stop all applications that are accessing thesystem and disable user logins to the server.

2. For each HBA connected to the system:

a. View the LUNs available to the server:

powermt display dev=all

42 Attaching a server

Configuring your VNX system

Page 43: VNX Attach Server (Linux)

b. Choose one available LUN to receive data (I/O) for the test.

c. View the paths to the chosen LUN:

powermt display dev=x every=2

where x is a pseudo device that represents the chosen LUN.

d. Start sending data to a LUN by writing data to it.

e. Identify the HBA sending data to the LUN by viewing the output of the

powermt display dev= x every=2

command, and disconnect the cable to that .

f. View the output of the

powermt display dev= x every=2

command, and verify that:

◆ The state of the uncabled paths becomes dead.◆ Data continues to be sent on the remaining paths to the LUN, indicating that the

failover path was successful and that PowerPath is working properly.

g. Reconnect the cable that you disconnected from the HBA.

h. If you caused any LUN to fail over, restore them to their original SP:

powermt restore

3. If you are connected to an existing system, restart any applications that you stopped andre-enable any user logins to the server that you disabled.

Configuring your VNX system 43

Configuring your VNX system

Page 44: VNX Attach Server (Linux)

Preparing LUNs to receive data

If you do not want to use a LUN as a raw disk or raw volume, then before Linux can senddata to a LUN, Linux must recognize the disk, and you must partition the disk and thencreate and mount a file system on it. For information on how to perform these tasks, referto your operating system documentation.

Before a virtual machine can send data to a virtual disk that is a VMFS volume, you mustdo the following:

Linux virtual machine

1. Partition the VMware virtual disk.

2. Create and mount a file system on the partition.

Windows virtual machine

1. Write a signature to the VMware virtual disk.

2. Either create partitions on a basic disk or create volumes on a dynamic disk.

44 Attaching a server

Preparing LUNs to receive data

Page 45: VNX Attach Server (Linux)

Sending Linux disk information to the system

If the Unisphere Host Agent is installed on the server, stop and then restart it to send thesystem the operating system’s device name and volume or file system information for eachLUN that the server sees. Unisphere displays this information in the LUN Properties — Hostdialog box for each LUN.

The Unisphere Server Utility does not send operating system LUN mapping informationto the system, so this procedure is not required.

Important:

Perform this procedure on your Hyper-V or ESX server.

Stopping the host agent a Linux server

◆ Log in as root and enter the following command:

/etc/init.d/naviagent stop

Starting the host agent

Log in as root and enter the following command:

/etc/init.d/naviagent start

Verifying that the system received the LUN information using Unisphere

1. From Unisphere, select All Systems ➤ System List.

2. From the Systems page, select a system that is attached to the host that you want toverify.

3. Select Hosts ➤ Hosts List.

4. Select a host and then, on the Details page, click the LUNs tab.

5. Verify that the LUNs tab displays a physical drive and logical drive name for each LUNon the host.

Sending Linux disk information to the system 45

Sending Linux disk information to the system

Page 46: VNX Attach Server (Linux)

Verifying your failover configuration with PowerPath

Perform the following tasks to verify that the server can send data to and receive data fromthe system and that PowerPath shows the paths from the server to the LUNs that you expectfor your configuration.

Note: You can download an I/O simulator (Iometer) for writing data to the system from the followingwebsite: http://www.iometer.org/

Verifying your failover configuration with PowerPath for a Linux server

1. If you are connected to an existing system, stop all applications that are accessing thesystem and disable user logins to the server.

2. For each HBA connected to the system:

a. View the LUNs available to the server:

powermt display dev=all

b. Choose one available LUN to receive data (I/O) for the test.

c. View the paths to the chosen LUN:

powermt display dev=x every=2

where x is a pseudo device that represents the chosen LUN.

d. Start sending data to a LUN by writing data to it.

e. Identify the HBA sending data to the LUN by viewing the output of the

powermt display dev= x every=2

command, and disconnect the cable to that .

f. View the output of the

powermt display dev= x every=2

command, and verify that:

◆ The state of the uncabled paths becomes dead.◆ Data continues to be sent on the remaining paths to the LUN, indicating that the

failover path was successful and that PowerPath is working properly.

g. Reconnect the cable that you disconnected from the HBA.

h. If you caused any LUN to fail over, restore them to their original SP:

46 Attaching a server

Verifying your failover configuration with PowerPath

Page 47: VNX Attach Server (Linux)

powermt restore

3. If you are connected to an existing system, restart any applications that you stopped andre-enable any user logins to the server that you disabled.

Verifying your failover configuration with PowerPath 47

Verifying your failover configuration with PowerPath

Page 48: VNX Attach Server (Linux)

Copyright © 2010 - 2011 EMC Corporation. All rights reserved.

Published September 2011

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

THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATIONMAKES NO REPRESENTATIONS ORWARRANTIES OF ANY KINDWITH RESPECT TOTHE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIEDWARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

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

For the most up-to-date regulatory document for your product line, go to the TechnicalDocumentation and Advisories section on EMC Powerlink.

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

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

Corporate Headquarters: Hopkinton, MA 01748-9103

48 Attaching a server