Attaching Server to Storage System- Master

Here is Your Customized DocumentYour Configuration is:

Action to Perform - Attach serverStorage-System Model - CX4-960Storage-System Status - ExistingConnection Type - Fibre Channel Switch or Boot from SANServer Status - NewServer Operating System - Linux - Red HatPath Management Software - EMC PowerPathManagement Tool - EMC Navisphere Manager

Reporting ProblemsTo send comments or report errors regarding this document, please email:[email protected]. For issues not related to this document, contactyour service provider.Refer to Document ID: 1430479

Content Creation Date 2010/10/20

Content Creation Date 2010/10/20

Attaching a Linux Server withEMC PowerPath to a CX4-960

Storage System in a Fibre ChannelSwitch Configuration

This document explains how to attach a Linux server with EMCPowerPath to a CX4-960 in a Fibre Channel switch configuration.

If you are an EMC partner, refer to the EMC Services Partner website todownload the Unisphere server software mentioned in this guide. Thepartner site is available from the Navigator drop-down menu on Powerlink.

IMPORTANT

Some of the procedures in this document apply only to the server, only tothe virtual machine, or to both the server and the virtual machine. Readeach section carefully to determine where to perform the procedure. If youwill configure your storage-system connections to your ESX or Hyper-Vserver, you must attach the ESX or Hyper-V server to your storage systembefore performing the steps in this document. For information on attachingan ESX or Hyper-V server, generate a new host attach document and selectthe appropriate ESX or Hyper-V server version.

The main topics in this document are:

Before you start ............................................................................. 3 Determining if your server has a supported configuration................ 5 Installing HBAs in the server.......................................................... 7 Installing or updating the HBA driver ............................................ 9 Installing PowerPath software ....................................................... 11 Installing Unisphere server software............................................... 14 Connecting the storage system to the server in a Fibre Channel

switch configuration ..................................................................... 27 Registering the server with the storage system ................................ 34 Verifying storage-system health...................................................... 36 Setting storage-system failover values for the server initiators with

Navisphere Manager..................................................................... 38

1

Verifying your high-availability Fibre Channel configuration ........... 40 Configuring an existing storage system........................................... 41 Preparing LUNs to receive data ...................................................... 47 Sending Linux disk information to the storage system ..................... 48 Verifying your failover configuration with PowerPath ..................... 49

2Attaching a Linux Server with EMC PowerPath to a CX4-960 Storage System in a Fibre ChannelSwitch Configuration

Before you start

This document covers a Fibre Channel switch configuration only. Forinformation on booting from a SAN, refer to the appropriate Host ConnectivityGuide or the EMC Support Matrix on the Powerlink website.

Read the release notes for your storage system, which are availablein the Technical Documentation and Advisories section on thePowerlink website.

If you have not done so already, complete the configurationplanning worksheets (administrative worksheets) in thestorage-system configuration planning guide or planningworksheets document. You can generate an up-to-date version ofthe planning guide customized for your installation from the Planlink on the storage-system support website.

You must have a supported Windows host on the same network asthe storage-system management ports. You can use this host:

z As a client in which you launch the Navisphere Manager. Thisclient was formerly referred to as the Navisphere managementstation.

z To run the Unisphere Service Manager, which runs only ona Windows host.

z As an EMC Secure Remote Support (ESRS) IP Client, whichmust be a Windows host, but cannot be a server (that is, itcannot send I/O to the storage-system data ports).

You must have a Unisphere Server with a supported Internetbrowser that is on the same network as the storage-systemmanagement ports. The Unisphere Server replaces the NavisphereManagement Server. This host can also be the server or a Unispheremanagement station (formerly referred to as the Navisphereoff-array management station). For supported Internet browsers,see the Manager release notes in the Technical Documentation andAdvisories section of the Powerlink website.

You must have a Linux host that is or will be a server with FibreChannel connections to the storage system. This server must havea supported server configuration; that is, it must have all requiredupdates, such as hot fixes or patches, installed.

Attaching a Linux Server with EMC PowerPath to a CX4-960 Storage Systemin a Fibre Channel Switch Configuration 3

You must have one or more supported Fibre Channel host busadapters (HBAs), which may already be installed in the server.These adapters must have the latest supported BIOS and driver.

We recommend that you do not mix Fibre Channel HBAs from differentvendors in the same server.

Each Fibre Channel front-end port that you will use on the storagesystem must have an optical cable. These cables may already beconnected for a configuration with an existing storage systemor server. We strongly recommend you use OM3 50 m cables.For cable specifications, refer to the storage-systems technicalspecifications. You can generate this user-customized documentfrom the Learn about storage system link on the storage-systemsupport website (www.emc.com/clariionsupport).

You must have one or two Fibre Channel switch fabrics, whichmay already be installed, and an optical cable for connecting eachHBA port to a switch port, if not already connected. We stronglyrecommend you use OM3 50 m cables. For cable specifications,refer to storage-systems Technical Specifications. You can generatethis document using the user customized documentation Learnabout storage system link on the storage-system support website(www.emc.com/clariionsupport).

You must have a method for writing data to a LUN on the storagesystem that will test the paths from the server to the storage system.You can download an I/O simulator (Iometer) from the followingwebsite: http://www.iometer.org/.


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 systemon the server.If you have this information, go to Verifying a serversconfiguration with E-Lab Interoperability Navigator, page 5 . If you do nothave this information, you can generate a server configuration reportfor 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 serverutilitys Welcome screen to generate a report of the serversenvironment.

This option detects if PowerPath or some other failover software,such as DMP, is running. The utility will not detect any other nativefailover software, such as Linux native multipath (MPIO). After theverification, the utility generates a summary report and saves itto the server.

2. In the summary report, select the Checklist tab to view theinformation about the server that you need to compare with theE-Lab Interoperability Navigator information.

Verifying a servers configuration with E-Lab Interoperability Navigator

1. From your web browser, go to the Powerlink website and log in.

2. If you are not registered with Powerlink, register and create ausername and password.

3. Select E-Lab Interoperability Navigator from the Tools menu onthe right-side of the home page.


4. From the E-Lab Interoperability Navigator page, select LaunchE-Lab Interoperability Navigator 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 the wizard, provide the requested informationbased on what is installed on the server or what you intend toinstall on the server.

If the configuration you entered is invalid, an additional stepappears in the wizard and a Results, EMC Support Statementspane appears on the right with information to help you provide therequested information in the additional step.

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

8. Click the Results link appears to view a report that containsinformation about the configuration 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 software or the checklist report you generated withthe server utility.

12. If your server software versions and/or patches or hot fixes are notlisted in the Host Attach Wizard report, you must upgrade to asupported version or patch before continuing.

The Host Attach Wizard displays only options that supports EMC. If any ofthe configuration information on the server utilitys high-availability reportcannot be found in the wizard, then EMC does not support it.


Installing HBAs in the server

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

Before you start

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

For information on supported HBAs, BIOS, and drivers, refer to theE-Lab Interoperability Navigator on the Powerlink website.

We recommend that you never mix HBAs from different vendors in the sameserver.

Installing HBAs

! CAUTIONHBAs are very susceptible to damage caused by static discharge andneed to be handled accordingly. Before handling HBAs, observethe 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 servers operating system.

b. Power down the server.

c. Unplug the servers power cord from the power outlet.

2. Put on an ESD wristband, and clip its lead to bare metal on theservers chassis.


3. For each HBA that you are installing:

a. Locate an empty PCI bus slot or a slot in the server that ispreferred for PCI cards.

b. Install the HBA following the instructions provided by the HBAvendor.

4. Plug the servers power cord into the power outlet, and power upthe server.


Installing or updating the HBA driver

The server must run a supported operating system and HBA driver.EMC recommends that you install the latest supported version of thedriver. For information on the supported HBA drivers, refer to theE-Lab Interoperability Navigator on the Powerlink website.

Before you start

To complete this procedure, you will need:

The latest supported version of the HBA driver.

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

For an Emulex driverYou can download the latest supported version and instructionsfor installing the Emulex HBA driver from the vendors website:http://www.emulex.com/products/fibre-channel-hbas.html.

For a Qlogic driverYou can download the latest supported version and instructionsfor installing the QLogic HBA driver from the vendors website:http://support.qlogic.com/support/oem_emc.asp.

For a Brocade driverYou can download the latest supported version and instructions forinstalling the Brocade HBA driver driver from the vendors website:

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

Any updates, such as hot fixes or patches to the servers operatingsystem that are required for the HBA driver version you will install.

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

z E-Lab Interoperability Navigator on the Powerlink website


z The HBA vendors website

Installing the HBA driver

1. Install any updates, such as hot fixes or patches, to the serversoperating system that are required for the HBA driver version youare installing.

2. If the hot fix or patch requires it, reboot the server.

3. Install the driver following the instructions on the HBA vendorswebsite.

4. Reboot the server when the installation program prompts you todo so.

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


Installing PowerPath software

IMPORTANT

If you have a Hyper-V or ESX server, install PowerPath on yourHyper-V or ESX server. Do not install PowerPath on the virtualmachine.

Install PowerPath by referring to the appropriate PowerPathInstallation and Administration Guide for your operating system. Thisguide is available in the Technical Documentation and Advisoriessection on the Powerlink website.

Before you install PowerPath

Save your Linux kernel and back up your system. Change the Linux kernel, as described in Changing the kernel on a

Linux server, page 11.

Change the Linux configuration files, as described in Modifyingconfiguration files on a Red Hat server, page 12 or .

Changing the kernel on a Linux server

1. If you load the HBA driver as a module, install its binary file inthe 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 -rcommand

hba_driver is the name of the HBA driver module

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


If you have Red Hat Linux 3.0 or later, you no longer need to build theHBA driver modules and copy them to the above location. The prebuiltkernel now includes these 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 HBAsEdit the /etc/modprobe.conf file as described in your HBA vendordocumentation.

For QLogic HBAsEdit the /etc/modprobe.conf file to make sure that theql2xfailover and the ConfigRequired parameters are set to 0:options qla2xxx q12xfailover=0 ConfigRequired=0

The variable x andxxx vary with the HBA model.

For Emulex HBAsEdit the /etc/modprobe.conf file to set thevalue of the lpfc_nodev_tmo parameter to 10: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 determinewhich initrd file is used.

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

3. Enter:

/sbin/mkinitrd -f -v initrd kernel

where

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 andthat the initrd entry of /boot/grub/grub.conf specifies this .img file.


Installing Unisphere server software

IMPORTANT

If you have a Hyper-V or ESX server, you must install the host agentor server utility on your Hyper-V or ESX server. Do not install theseprograms on your virtual machine.

This section describes how to install Unisphere server software, whichwas previously referred to as the CLARiiON server software orNavisphere server software.

If you plan to install Navisphere CLI or Admsnap, you must installthem on a virtual machine. For instructions on installing these softwareprograms on a virtual machine, generate a new document and selectthe operating system running on the virtual machine.

Before you beginRefer to the sections below to determine which application to installfor host registration and the requirements for installing each of theseapplications.

To run CLARiiON server software, your server must meetthe requirements outlined in Requirements for Unisphere serversoftware, page 15.

To determine whether to install the Unisphere Host Agent orUnisphere Server Utility to register your HBAs with the storagesystem, refer to Determining whether to install the Unisphere HostAgent , page 16.

Installing Unisphere server softwareDepending on which Unisphere server software you are installing,refer to the appropriate section below.

Unisphere Host Agent see Installing the Unisphere Host Agent, page17.

Unisphere Server Utility see Installing the Unisphere Server Utility, page 22.

Navisphere CLI see Installing Navisphere CLI , page 23


Admsnap Utility see Installing the Admsnap Utility , page 25.

Requirements for Unisphere server software

To run Unisphere server software, your server must meet the followingrequirements:

Run a supported version of the Linux operating system. For Fibre Channel connections, have the EMC CLARiiON

supported HBA hardware and driver installed.

Be connected to at least one SP (two SPs for high availability) ineach storage system either directly or through a switch or hub. EachSP must have an IP connection.

For the host agent and CLI only - Be on a TCP/IP network connectedto at least one SP (two SPs for high availability) in the storagesystem. The TCP/IP network connection allows the server to sendLUN mapping information to the storage system and it allowsNavisphere Manager or Navisphere CLI to communicate with thestorage system over the network.

Have a configured TCP/IP network connection to any remote hoststhat you will use to manage the servers storage systems, including:

z any server whose browser you will use to access NavisphereManager,

z a supported Windows server running Unisphere Server software(replaces the Navisphere Management Server software),

z 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 storagesystems on a remote server, the server must be on a TCP/IP networkconnected to both the remote server and each SP in the remote serversstorage system. The remote server can be running AIX, HP-UX, Linux,Solaris, or the Windows operating system.


For information about the specific revisions of the server operating systemand the storage-system FLARE and Access Logix software that are requiredfor your version of the host agent, see the release notes for the host agent onthe EMC Powerlink website.

Determining whether to install the Unisphere Host Agent

Depending on your application needs, you can install the host agent to:

Monitor storage-system events and notify personnel by e-mail,page, or modem when any designated event occurs.

Retrieve LUN world wide name (WWN) and capacity informationfrom Symmetrix storage systems.

Register the servers HBAs with the storage system. Alternatively,you can use the Unisphere Server Utility to register the serversHBAs with the storage system. Table 1 describes the hostregistration differences between the host agent and the server utility.

Table 1 Host registration differences between the host agent and the serverutility

Function Unisphere Host Agent Unisphere Server Utility

Pushes LUN mappingand OS information to thestorage system.

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

CX4 series, CX3 series, and CX series storage systemsNo LUN mapping information is not sent to the storage system. Onlythe servers name, ID, and IP address are sent to the storage system.Note: The text Manually Registered appears next to thehostname icon in the Manager UI indicating that the host agent wasnot used to register this server.


Function Unisphere Host Agent Unisphere Server Utility

Runs automatically tosend information to thestorage system.

Yes No user interaction isrequired.

CX4 series, CX3 series, and CX series storage systemsNo You must manually update the information by starting the utilityor you can create a script to run the utility. Since you run the serverutility on demand, you have more control as to how often or when theutility is executed.

Requires networkconnectivity to the storagesystem.

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

CX4 series, CX3 series, and CX series storage systemsNo LUN mapping information is not sent to the storage system.Note that if you are using the server utility to upload a high-availabilityreport to the storage system, you must have network connectivity.

Installing the Unisphere Host Agent

This section describes how to install the Unisphere Host Agent.

Installing the Unisphere Host Agent on a Linux server

We recommend that you download and install the most recent versionof the Unisphere Host Agent software from the software downloadspage on the Powerlink 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. Thisport is used by the host agent. If this port is not opened, the hostagent will not function properly.

3. Download the software:

a. From the Powerlink website, select Support > SoftwareDownloads and Licensing > Downloads T-Z > UnisphereServer Software.

b. Select the Unisphere Host Agent, and then select the option tosave the zip file to your server.

c. At the command line prompt, navigate to the directory whereyou saved the zip file and unzip the file.

unzip Navi_Agent_CLI_Linux-version.zip

where version is the version listed in the filename.

d. Depending on which version you are installing, enter one of thefollowing commands to 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 buildnumber of the software.

If you have an IA64 system, you must install the 32bit package. The64bit package is currently supported on x86_64 systems only. Refer tothe release notes for any updates.

4. Verify that host agent and/or CLI are installed:

rpm -qa | grep navi

Before you can use the host agent or CLI, you must modify the user loginscripts and configure the host agent configuration file.

Modifying user login scripts

To use navicli commands at the root prompt without typing a leading./ before the commands (for example, ./navicli getagent), you mustmodify the $PATH environment variable 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 export PATH

To verify the path enter:

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 Running the Unisphere HostAgent , page 20. If you are just upgrading the host agent or CLI onan existing system, you have finished the upgrade.

Configuring the Unisphere Host Agent

Before you can use the Navisphere CLI navicli register command toconfigure your storage system, you must make sure the host agentconfiguration file includes a privileged user, as described in Addingprivileged users, page 19.

The pathname of the host agent configuration file is /etc/Unisphere/agent.con-fig.

Adding privileged users

If you use Navisphere CLI to configure any storage system, the hostagent configuration file must include an entry that defines the personwho will issue the CLI commands as a privileged user.

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

For a local user:

user name

For a remote user:

user name@hostname

where name is the persons account name and hostname is the name ofthe remote server 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 agentconfiguration file, save the host 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

The Unisphere Host Agent can monitor storage-system events and takesuch action as sending e-mail or paging you if specified events occur.The event monitor that ships with Navisphere Manager provides aninteractive way to define these events and actions. If you do not haveevent monitor, you can still define such events and actions by editingthe event monitor configuration file.

/etc/Unisphere/Navimon.cfg

The file is self-documenting; that is, text in it describes how to defineevents and the actions you want taken if the events occur. You cantest the file after editing it using the Navisphere CLI commandresponsetest, as explained in the Navisphere Command Line InterfaceReference.

Running the Unisphere Host Agent

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

Starting and stopping the Unisphere Host Agent

The host agent starts automatically when you bring the server up toinit level 3. When you first start the host agent, look at the system logfor the servers operating system to make sure the agent started and nodevice errors occurred. The system log is located in /var/log/messages.

When a storage system experiences heavy input/output traffic (that is,applications are using the storage system), information may not be reportedto the host agent in a timely manner, resulting in the host agent taking severalminutes to execute a storage-system management task. This behavior is mostevident when one host agent is managing multiple storage systems. Also, if theSP event log is large and the host agent configuration file is set up to read allevents, it may take a few minutes for the host agent to start.

Starting the host agent

Log in as root and enter the following command:

/etc/init.d/hostagent start


Stopping the host agent


/etc/init.d/naviagent stop

Testing the host agent connections

Before continuing, you should test the host agent connections asfollows:

1. Start the host agent as described in Starting and stopping theUnisphere Host Agent, page 20.

2. Look for any errors on the console and in the operating system logto make sure the agent started and no device errors occurred.

3. Verify that the host agent on the server can see the storage systemas follows:

a. Enter the following CLI command:naviseccli |navicli [-d device]| -h hostname port-list -hba

You cannot specify both the d switch and h switch.

where:

[-d device] is the device name for the storage system (onlysupported with legacy systems).

-h hostname is the IP address of the SP.

For each HBA in the server, a listing similar to the following willbe displayed. For storage 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: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: sp0


Trusted: 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 hostto the SP.

Host agent status and error logging

While the system is running, the operating system tracks informationabout host agent events and host agent errors, and places thisinformation in log files on the server.

The host agent error log tracks information about the host agentsstartup, the host agent shutdown, and errors that might occur, such asthe host agents inability to access a device in the configuration file. Ifproblems occur, log files are a good place to start your troubleshooting.

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

Installing the Unisphere Server Utility

This section describes how to install the Unisphere Server Utility.

Installing the Unisphere Server Utility on a Linux server

We recommend that you download and install the most recent versionof the Unisphere Server Utility software from the software downloadspage on the Powerlink website.

1. Log in to the root account.


a. From the Powerlink website, select Support > SoftwareDownloads and Licensing > Downloads T-Z > UnisphereServer Software.

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


d. Install the software:


32-bit server rpm -ivh UnisphereServerUtil-Linux-32-x86-en_US-versionbuild.platform.rpm

32-bit Power Linux server rpm -ivh UnisphereServerUtil-Linux-32-powerpc-en_US-versionbuild.ppc64.rpm


64-bit server rpm -ivh UnisphereServerUtil-Linux-64-x86-en_US-versionbuild.x86_64.rpm


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

The installation process adds a line to the /etc/rc.d/rc.local filethat starts the server utility on reboot, provided root has executepermission for the /etc/rc.d/rc.local file.

Installing Navisphere CLI

This section describes how to install Navisphere CLI. You can installNavisphere CLI on either the server or virtual machine.

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

We recommend that you download and install the most recent versionof the Navisphere CLI software from the software downloads pageon the Powerlink website.

1. Log in to the root account.

2. If your server is behind a firewall, open the TCP/IP ports listed inTable 2. These ports are used by Navisphere CLI. If these ports arenot opened, the software will not function properly.


Table 2 TCP/IP ports

Software TCP/IP ports

Classic CLI 6390, 6391, 6392

Secure CLI 443, 2163


a. From the Powerlink website, select Support > SoftwareDownloads and Licensing > Downloads J-O > NavisphereServer Software.

b. Select the Navisphere CLI, and then select the option to save thezip file to your server.



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 Englishversion is available, or loc, when the localizedversions are available (including English).

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

If you have an IA64 system, you must install the 32bit package. The64bit package is currently supported on x86_64 systems only. Refer tothe release notes for any updates.


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

4. Verify that Navisphere CLI is installed by using the rpm -qa | morecommand.

Installing the Admsnap Utility

To access snapshots of LUNs in the storage system, install the AdmsnapUtility.

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

IMPORTANT

Currently, you cannot install admsnap on your virtual machine if yourvirtual machine is connected to Fibre Channel storage; you must installit on the Hyper-V server. For any updates, refer to the Admsnap ReleaseNotes.

Installation prerequisites

Before you can install and use the Admsnap Utility, you must installSnapView on a supported CLARiiON storage system. For a list ofsupported storage systems, refer to the release notes for SnapViewand admsnap.

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

We recommend that you download and install the most recent versionof the Admsnap Utility software from the software downloads pageon the Powerlink website.

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


a. From the Powerlink website, select Support > SoftwareDownloads and Licensing > Downloads S > SnapView.

b. Select the Admsnap Utility version you want to download andselect the option to save the zip file to your server.



unzip admsnap_version.zip

where version is the version listed in the filename.


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

Power Linux server: rpm -ivh admsnap-Linux-32-powerpc-en_US-version-build.rpm


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

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

3. Verify that the correct version of admsnap is installed by enteringthe following command:

/usr/admsnap/admsnap help

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

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

MANPATH /usr/admsnap/man

5. Configure sg devices by using the MAKEDEV utility. Forinformation on how to use the MAKEDEV utility, refer to theMAKEDEV man pages.

Running the Admsnap Utility

Refer to the EMC SnapView Command Line Interface Reference forinformation on running admsnap commands.


Connecting the storage system to the server in a Fibre Channelswitch configuration

Use optical cables to connect the storage-system Fibre Channelfront-end data ports to the Fibre Channel switch ports and to connectthe switch ports to the server HBA ports.

Applications such as MirrorView/A, MirrorView/S, or SAN Copysoftware may restrict or require the use of certain SP ports. Refer to theapplication documentation for specific cabling information.

Before you start

To complete this procedure, you will need an optical cable for eachswitch port you will use. We strongly recommend you use OM3 50 mcables for all optical connections.

Specifications for the optical cables that connect the switch to thestorage system are in the storage systems technical specifications in thedocumentation section of Powerlink.

Identifying storage-system Fibre Channel front-end ports

The number and location of the SP Fibre Channel front-end ports forthe storage system depend on the UltraFlex Fibre Channel I/Omodules installed in the I/O module slots (Figure 1):

A0 through A5 for SP A B0 through B5 for SP BSP A and SP B must have the same type of I/O module in the same slots.


CL4126

0 1 2 3

0 1 2 3

A0 A1 A2 A3

B0 B1 B2 B3

B4 B5 A4 A5

Figure 1 I/O module slots (only standard I/O modules shown)

Standard Fibre Channel I/O modules with Fibre FE portsYour storage system has two 4 or 8 Gb Fibre Channel I/O modulesper SP each with two Fibre back-end (BE) ports (0, 1) and two FibreFE ports (2, 3). These modules are either all 4 Gb modules or all 8 Gbmodules. One of these modules is always in slots A0 on SP A and inslot B0 in SP B. The other modules can be in any available slot, unlessthe storage system has the expansion option and is running a FLAREOE version earlier than 04.28.000.5.5xx, in which case, they cannot bein slots A5 and B5.

The 8 Gb modules require FLARE OE version 04.28.000.5.7xx or later.

Optional Fibre Channel I/O modules with Fibre FE portsYour storage system may have the following optional Fibre ChannelI/O modules with Fibre FE ports:

For a base system without the expansion option One or twooptional 4 or 8 Gb Fibre Channel I/O modules per SP each withfour Fibre FE ports (0, 1, 2, 3) in any available slots.

For a base system with the expansion option and running FLAREOE version 04.28.000.5.5xx or later One or two optional 4 or 8 GbFibre Channel I/O modules per SP each with four Fibre FE ports(0, 1, 2, 3) in any available slots.

For a base system with the expansion option and running aFLARE OE version earlier than 04.28.000.5.5xx One optional 4 GbFibre Channel I/O module per SP each with four Fibre FE ports (0,1, 2, 3) in any available slots except slots A5 and B5.


The 8 Gb modules require FLARE OE version 04.28.000.5.7xx or later.

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

FE port connectivityThe Fibre FE ports on a 4 Gb/s Fibre Channel I/O module supports1/2/4 Gb/s connectivity, and the Fibre FE ports on an 8 Gb/s FibreChannel I/O module supports 2/4/8 Gb/s connectivity. You cannotuse the FE ports on an 8 Gb/s Fibre Channel I/O module in a 1 Gb/sFibre Channel environment. You can use the FE ports on a 4 Gb/s FibreChannel I/O module in an 8 Gb/s FC environment if the FC switchports to which the modules FE ports connect auto-adjust their speedto 4 Gb/s.

Cabling the Fibre Channel front-end data ports to the switch ports (if necessary)

For highest availability, connect one or more Fibre Channel front-enddata ports on SP A to ports on the switch and connect the same numberof Fibre Channel front-end data ports on SP B to ports on same switchor on another switch, if two switches are available.

Customer-installable switches are easily configured. Some are preconfiguredto use only ports 0 and 4 for SP connections and only ports 1-3 and 5-15 forHBA connections. With switches set up in such hard zones, you can connectthe fibre ports only to ports 0 and 4 and HBAs only to ports 13 and 515. Forhighest availability with one of these hard zoned switches and a multiple-HBAserver, connect either fibre port on SP A to switch port 0 and either FE port onSP B to switch port 4.

For each Fibre Channel (FC) front-end data port on the storage systemthat you will use for I/O with the server:

1. Locate the FC front-end data port to which you will connect theswitch port.

For information on identifying the front-end ports using NavisphereManager, refer to the Navisphere Manager online help.


Applications such as MirrorView/A, MirrorView/S, or SAN Copy softwaremay restrict or require the use of certain SP ports. Refer to the applicationdocumentation for specific cabling information.

2. Remove the protective cover from the FC front-end data portconnector on the SP and from one end of the optical cable, and plugthe cable into the data port connector (Figure 2 and Figure 3).

3. Remove the protective cover from the optical connector on theswitch port that you will use and from the free end of the opticalcable, and plug the cable into the switch port (Figure 2 and Figure 3).

CL4021

Figure 2 Connecting an optical cable


CL4186 CL4186

! !

Figure 3 Sample cabling between a storage system and two switches

Cabling the switch ports to the server HBA ports

For the highest availability in a multiple-HBA server, connect one ormore HBA ports to ports on the switch and connect the same numberof HBA ports to ports on the same switch or on another switch, if twoswitches are available.

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

1. Remove the protective cover from the FC switch port connectorand from one end of the optical cable, and plug the cable into theconnector.

2. Remove the protective cover from the server HBA port connectorand from the free end of the optical cable, and plug the cable intothe HBA port connector (Figure 4).


! !

CL4044

Figure 4 Sample cabling for a Fibre Channel switch configuration

Zoning the switches

Use switch management software to update switch software and zoneswitches that are not hard zoned.

We recommend single-initiator zoning as a best practice. Insingle-initiator zoning each HBA port has a separate zone that containsit and the SP ports with which it communicates. For information onFibre Channel topologies, refer to the EMC Networked Storage TopologyGuide on Powerlink.

IMPORTANT: For Linux servers, you must use single-initiator andsingle-target zoning. A single-initiator single-target zone has HBA port and onestorage-system SP port. You can share SP ports among HBA ports, providedeach HBA port is in its own zone.


To zone the switch:

1. Connect the switch management ports to the network from whichyou will manage the switches.

2. If the switches are not running the most recent supported firmwareversion, install this software from the switch vendors website.

For information on the supported switch firmware versions, see theE-Lab Interoperability Navigator on Powerlink.

3. Use either the zoning wizard CD that shipped with the switch orthe switch management software to set up the appropriate switchzones.

a. To use the zoning wizard CD Using the instructions providedwith the CD, run the zoning wizard and select the zoneconfiguration that is applicable to the way that you connectedthe storage-system Fibre ports and the server HBA ports to theswitch.

b. To use the switch management software Download the latestversion of the switch management software from the switchvendors website, and follow the instructions provided for thesoftware to setup the zones that are applicable to the way thatyou connected the storage-system Fibre ports and the serverHBA ports to the switch.


Registering the server with the storage system

IMPORTANT

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

You must run the Unisphere Server Utility or Unisphere Host Agent oneach server connected to the storage system to register the serversHBAs with the storage 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 yourHyper-V or ESX server. For updates on SCSI pass through support forvirtual machines with FC devices, refer to the E-Lab InteroperabilityNavigator on Powerlink.





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 storage systems, anddisplays a list of the ones it finds.

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


The utility sends the servers name and IP address to each storagesystem. Once the server has storage on the storage system, theutility also sends the Linux device name and volume or file systeminformation for each LUN (virtual disk) in the storage system thatthe 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 serversHBAs with the storage system.




Verifying HBA registration with Navisphere Manager

1. From the Navisphere Manager Storage tree, right-click the icon forthe storage system for which you want to verify HBA registration,and click Connectivity Status.

The Connectivity Status dialog box opens.

2. Verify that the server to SP port connection is displayed as Yesunder the Registered columns.

If not, refer to the Troubleshooting Flowcharts section on theCLARiiON Tools page on the Powerlink website.

To access the CLARiiON Tools page, use the Navigator drop-down menuat the top right of the Powerlink home page.

Once all HBAs belonging to a server are registered, you can assignthe server to storage groups.


Verifying storage-system health

Use the storage-system verification wizard that is part of the UnisphereService Manager (USM), which replaces the Navisphere ServiceTaskbar, to:

Validate the connectivity of the storage-system hardwarecomponents

Verify back-end functionality Verify the status of all field-replaceable units Analyze storage-system logs

Download the USM from a link on the CLARiiON Tools page of thePowerlink website to a Windows management station that is connected to thestorage-systems management ports. If you do not have a Windowsmanagement station, your service provider can run this wizard.

To access the CLARiiON Tools page, use the Navigator drop-down menu atthe top right of the Powerlink home page.

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

a. Download and install the Unisphere Service Manager from theCLARiiON Tools page on the Powerlink website to a WindowsUnisphere server that is connected to the storage-systemsmanagement ports.

To access the CLARiiON Tools page, use the Navigator drop-downmenu at the top right of the Powerlink home page.

b. Start the Unisphere Service Manager by doing one of thefollowing:

Click the Unisphere Service Manager icon on your desktop,or

Select Start > All Programs or Start > Programs, thenselect EMC > Unisphere > Unisphere Service Manager >Unisphere Service Manager

2. Log in to your system.


3. From the System screen, select Diagnostics > Verify StorageSystem and follow the instructions that appear.

4. Review the report that the wizard generates, and if it lists anyproblems, try to resolve them.

For assistance in resolving any problems, see the troubleshootingflowcharts for the storage system on the CLARiiON Tools page ofthe Powerlink website.


Setting storage-system failover values for the server initiators withNavisphere Manager

Use the Navisphere Manager Failover Setup wizard to set thestorage-system failover values for all HBA initiators belonging to theserver:

1. Start Navisphere Manager for the storage system.

2. In the Tools menu, click Failover Setup Wizard.

3. In the Start Wizard dialog box, read the introduction, and thenclick Next.

4. In the Select Host dialog box, select the server you just connected tothe storage system, and click Next.

5. In the Select Storage Systems dialog box, select the storage system,and click Next.

6. In the Specify Settings dialog box, set the following values for thetype of software running on the server.

IMPORTANT

If you enter incorrect values the storage system could becomeunmanageable and unreachable by the server, and the serversfailover software could stop operating correctly.

If you have a Hyper-V or ESX server, set the storage-system failovervalues for the Hyper-V or ESX server.

For a Linux server, set:

Initiator Type to CLARiiON Open Array CommPath to Enabled Failover Mode to 4 if your failover version supports ALUA. Failover Mode to 1 if your failover version does not support

ALUA.


For information on which versions of failover support ALUA forCLARiiON storage systems, refer to the PowerPath release notes or theNative Multipath Failover based on DM-MPIO for v2.6.x Linux Kernel andEMC Storage Arrays Configuration Guide on the Powerlink website orto EMC Knowledgebase solution emc99467.

7. In Configuration Summary, review the configuration and allsettings.

8. 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 tore-enter the correct values.

If you clicked Next, the wizard displays a confirmation dialog box.

9. In the confirmation dialog box, click Yes.

The wizard displays a summary of the success of the operation toset the values for the storage system.

10. If the operation failed, rerun the Failover Setup Wizard again.

11. When the operation is successful, click Finish to close the wizard.

12. Reboot the server for the initiator records to take affect.


Verifying your high-availability Fibre Channel configuration

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





Using the server utility to verify your high-availability configuration

1. From the Unisphere Server Utilitys Welcome screen, select option 3to generate a report of the servers environment.

The utility determines if the server is configured for high availabilityby verifying that the server has at least one connection path toeach storage system SP, and that PowerPath or some other failoversoftware, such as DMP, is running. It does not detect native failoversoftware, such as Linux native multipath (MPIO).

2. Review and resolve any issues reported on the Issues tab of thegenerated report before continuing with the installation process.


Configuring an existing storage system

To configure an existing storage system with Navisphere Manager,use either the Unisphere Service Manager wizards or the Storage treeoptions of Navisphere Manager.

Before you start

You need the completed storage-system disk information worksheetfrom the storage-system configuration planning guide or administrativeworksheets (administrative worksheets) document. You can generatethis guide using the user-customized documentation link from thestorage-system support website (www.emc.com/clariionsupport).

Enabling storage groups or access control with Navisphere Manger

Starting with Navisphere Manager 6.29, the term Access Logix" has beenreplaced with "Storage Groups and the Storage Access tab has been removedfrom the storage-system Properties page.

When you started this installation if the storage system was either anew storage system that will be connected to multiple servers or anexisting storage system that is connected to only one server, you musteither enable storage groups using Navisphere Manager 6.29 or later orto enable access control using Navisphere Manager 6.28 or earlier:

To enable storage groups using Navisphere Manager 6.29 or later

1. In the Navisphere Manager Storage tree, right-click the icon for thestorage system, and click Properties.

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

3. Click OK.

To enable access control using Navisphere Manager 6.28 or earlier

1. In the Navisphere Manager Storage tree, right-click the icon for thestorage system, and click Properties.

2. Click the Storage Access tab, and under Data Access, select AccessControl Enabled.


3. Click OK.

Allocating storage to an existing storage system with the Provision or Allocate wizard

IMPORTANT


Starting with UI version 6.28.10.xx, the Allocate wizard has beenrenamed to Provision wizard. Like the Allocate wizard, use theProvision wizard, found in the Navisphere Manager taskbar, to createstorage system storage and provide server access to this storage.

1. Locate your completed storage-system disk information worksheetso you can refer to it in the steps that follow.

2. In the Navisphere taskbar, click the Storage Management tab.

3. If you need additional LUNs or thin LUNs for the server, use theProvision or Allocate wizard on the Storage Management tab tocreate them.

4. If you want to assign existing LUNs or thin LUNs to the server, usethe Assign wizard on the Storage Management tab to assign them.

For high availability, a host can connect to only one storage group perstorage system at a time. If you connect a host that is already connectedto another storage group, the host will disconnect from the first storagegroup. 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 thefirst storage group.

5. Verify that a server was assigned to the storage group.

If you know the name of the storage group in which the LUNsreside In the Navisphere Manager Storage tree:

Click the icon for the storage system with the storage groupwhose server connection you want to verify.

Click the Storage Groups icon. Click the icon for the storage group.


If the server is assigned to a storage group, an icon for thatserver appears under the storage group icon.

If you know the name of the server to which the storage group isassigned In the Navisphere Manager Hosts tree:

Click the icon for the server to which you assigned the LUNsand whose server connections you want to verify.

Click the LUNs icon and confirm that the new LUNs are listed.

If you do not see any of the LUNs you just created, you may nothave selected the Assign LUNs to a server option in the SelectServers page of the Provision wizard. You can use the Assignwizard to assign the LUNs to a server.

Allocating storage to an existing storage system with the storage tree options

1. Locate your completed storage-system disk information worksheetso you can refer to it in the steps that follow.

2. Create additional traditional LUNs on new or existing RAID groups.

To create traditional LUNs on RAID Groups In the NavisphereManager Storage tree, depending on the UI and FLARE versionthat you identified earlier, right-click the storage-system icon anddo one of the following:

Click Storage Pools Operations > Create LUNs ; create a newRAID group or select an existing one; create new LUNs on theRAID group.

Click Bind LUN; create a new RAID group or select an existingone; bind LUNs on the RAID group

For details on creating traditional LUNs and RAID groups, usethe Navisphere Manager help.

3. Create thin LUNs on thin pools.

You must use Navisphere Manager UI version 6.28.10.xx. The storagesystem must be running FLARE 04.28.000.5.5xx or later and the VirtualProvisioning enabler must be installed on the storage system.


To create thin LUNs on thin pools In the Navisphere ManagerStorage tree, right-click the storage-system icon and click StoragePool Operations > Storage Pools and in the Create Storage Pooldialog box, select Thin Pools. For details on creating thin LUNsand thin pools, use the Navisphere Manager help.

4. Create any additional storage groups that you need for the server.

To create storage groups In the Navisphere Manager tree,right-click the icon for the storage system, and click Create StorageGroups. For details on creating storage groups, use the NavisphereManager help

5. Add the new LUNs you created to new or existing storage groups.

Adding a LUN to a storage group makes the LUN accessible to the serversconnected to the storage group. If a LUN is placed in more than one storagegroup, all servers in those storage groups must be in a cluster configuration.

To add LUNs to storage groups Right-click the icon for thestorage group to which you want to add LUNs, and click SelectLUNs. For details on adding LUNs to storage groups, use theNavisphere Manager help.

6. Assign a server to a new or existing storage group.

To assign servers to storage groups In the Navisphere Managertree, right-click the icon for the storage group to which you wantto assign a server, and then click Connect Hosts. For details onassigning servers to storage groups, use the Navisphere Managerhelp.

For high availability, a host can connect to only one storage group perstorage system at a time. If you connect a host that is already connectedto another storage group, the host will disconnect from the first storagegroup. 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 thefirst storage group.

7. Verify that the server was assigned to the storage group.


To verify that a server is assigned to a storage group In theNavisphere Manager tree:

Click the icon for the storage system with the storage groupwhose server connection you want to verify.

Click the Storage Groups icon. Click the icon for the storage group.

If the server is assigned to a storage group, an icon for thatserver appears under the storage group icon.

Verifying that each LUN is fully initialized using Navisphere Manager

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

To determine the state of a LUN:

1. From the Navisphere Manager Storage tree, navigate to the LUNyou want to verify.

2. Right-click the LUN and click Properties.

Making LUNs visible to a Linux server

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

For a server with HBA connections to the storage system:rmmod driver_modulemodprobe driver_module (or insmoddriver_module)


where driver_module is the driver module name.

Verifying that PowerPath for Linux sees all the paths to the LUNs

IMPORTANT


1. Rescan for disks (LUNs).

2. On the server, configure PowerPath:

powermt config

3. View the LUNs available to the server with the PowerPathcommand:

powermt display dev=all class=clariion

4. Using the output from the command above, verify that none of thepaths to the storage system are dead.


Preparing LUNs to receive data

If you do not want to use a LUN as a raw disk or raw volume, thenbefore Linux can send data to a LUN, Linux must recognize the disk,and you must partition the disk and then create and mount a filesystem on it. For information on how to perform these tasks, refer toyour operating system documentation.

Before a virtual machine can send data to a virtual disk that is a VMFSvolume, you must do the following:

For a Linux virtual machine:

Partition the VMware virtual disk. Create and mount a file system on the partition.


Sending Linux disk information to the storage system

If the Unisphere Host Agent is installed on the server, stop and thenrestart it to send the storage system the operating systems devicename and volume or file system information for each LUN that theserver sees. Navisphere Manager displays this information in the LUNProperties Host page for each LUN. The Unisphere Server Utilitydoes not send operating system LUN mapping information to thestorage system, so this procedure is not required.

IMPORTANT

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

Stopping the host agent


/etc/init.d/naviagent stop




Verifying that the storage system received the LUN information using NavisphereManager

1. Start Navisphere Manager on the storage system with the LUNs.

2. For each LUN in the storage system that is connected to the server,display its Navisphere Manager LUN Properties Hosts page:

a. In the Navisphere Manager Storage tree, navigate to the LUNyou want to verify.

b. Right-click the icon for the LUN, and click Properties.

3. Verify that the Properties page displays a physical device andlogical device name for the LUN.


Verifying your failover configuration with PowerPath

Perform the following steps to verify that the server can send datato and receive data from the storage system and PowerPath showsthe paths from the server to the LUNs that you expect for yourconfiguration.

You can download an I/O simulator (Iometer) for writing data to the storagesystem from the following website: http://www.iometer.org/

Verifying your failover configuration with PowerPath for a Linux server

1. If you are connected to an existing storage system, stop allapplications that are accessing the storage system and disable userlogins to the server.

2. For each HBA connected to the storage 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 theoutput of the powermt display dev= x every=2 command, anddisconnect the cable to that HBA.

f. View the output of the powermt display dev= x every=2command, 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 andthat 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 originalSP:

powermt restore

3. Restart any applications that you stopped and re-enable any userlogins to the server that you disabled.


Copyright 2009-2010 EMC Corporation. All Rights Reserved.

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 OR WARRANTIES OF ANY KIND WITH 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 mentioned herein are the property of their respective owners.


tocThis document explains how to attach a Linux server with EMC PoBefore you startDetermining if your server has a supported configurationStarting the Unisphere Server Utility on a Linux serverGenerating a high-availability report for a serverVerifying a servers configuration with E-Lab Interoperability N

Installing HBAs in the serverBefore you startInstalling HBAs

Installing or updating the HBA driverBefore you startFor an Emulex driverFor a Qlogic driverFor a Brocade driver

Installing the HBA driver

Installing PowerPath software Before you install PowerPathChanging the kernel on a Linux serverRed Hat Linux Location

Modifying configuration files on a Red Hat serverFor Brocade HBAsFor QLogic HBAsFor Emulex HBAs

Saving kernel changes on a Red Hat server

Installing Unisphere server softwareBefore you begin Installing Unisphere server softwareRequirements for Unisphere server softwareDetermining whether to install the Unisphere Host Agent Installing the Unisphere Host AgentInstalling the Unisphere Host Agent on a Linux serverModifying user login scripts

Configuring the Unisphere Host Agent Adding privileged usersSaving the host agent configuration fileUsing the event monitor configuration file

Running the Unisphere Host Agent Starting and stopping the Unisphere Host AgentStarting the host agent Stopping the host agent

Testing the host agent connectionsHost agent status and error logging

Installing the Unisphere Server Utility Installing the Unisphere Server Utility on a Linux server

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

Installing the Admsnap Utility Installation prerequisitesInstalling the Admsnap Utility on a Linux server or a Linux virtRunning the Admsnap Utility

Connecting the storage system to the server in a Fibre Channel sBefore you startIdentifying storage-system Fibre Channel front-end portsStandard Fibre Channel I/O modules with Fibre FE portsOptional Fibre Channel I/O modules with Fibre FE portsModule labels and FE port connectorsFE port connectivity

Cabling the Fibre Channel front-end data ports to the switch porCabling the switch ports to the server HBA ports Zoning the switches

Registering the server with the storage systemRunning the Unisphere Server Utility on a Linux serverStarting the Unisphere Server Utility on a Linux serverRegistering the Linux server using the Unisphere Server Utility

Starting the Unisphere Host AgentStarting the host agent

Verifying HBA registration with Navisphere Manager

Verifying storage-system healthSetting storage-system failover values for the server initiatorsVerifying your high-availability Fibre Channel configurationStarting the Unisphere Server Utility on a Linux serverUsing the server utility to verify your high-availability config

Configuring an existing storage systemBefore you startEnabling storage groups or access control with Navisphere MangerAllocating storage to an existing storage system with the ProvisAllocating storage to an existing storage system with the storagVerifying that each LUN is fully initialized using Navisphere MaMaking LUNs visible to a Linux serverVerifying that PowerPath for Linux sees all the paths to the LUN

Preparing LUNs to receive dataSending Linux disk information to the storage systemStopping the host agent Starting the host agent Verifying that the storage system received the LUN information u

Verifying your failover configuration with PowerPathVerifying your failover configuration with PowerPath for a Linux

Copyright 2009- 2010 EMC Corporation. All Rights Reserved.

tablesTable 1 Host registration differences between the host agent andTable 2 TCP/IP ports

Attaching Server to Storage System- Master

Documents

Transcript of Attaching Server to Storage System- Master