Attaching Server To Storage System - Master

Here is Your Customized Document
Your Configuration is:

Action to Perform - Attach server Storage-System Model - CX4-960 Storage-System Status - Existing Connection Type - Fibre Channel Switch or Boot from SAN Server Status - New Server Operating System - Linux - Red Hat Path Management Software - EMC PowerPath Management Tool - EMC Navisphere Manager
Reporting Problems
To send comments or report errors regarding this document, please email: UserCustomizedDocs@emc.com. For issues not related to this document, contact your service provider. Refer to Document ID: 1430479
Content Creation Date 2010/10/20
Attaching a Linux Server with EMC PowerPath to a CX4-960 Storage System in a Fibre Channel Switch Configuration
This document explains how to attach a Linux server with EMC PowerPath to a CX4-960 in a Fibre Channel switch configuration. If you are an EMC partner, refer to the EMC Services Partner website to download the Unisphere server software mentioned in this guide. The partner 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 to the virtual machine, or to both the server and the virtual machine. Read each section carefully to determine where to perform the procedure. If you will configure your storage-system connections to your ESX or Hyper-V server, you must attach the ESX or Hyper-V server to your storage system before performing the steps in this document. For information on attaching an ESX or Hyper-V server, generate a new host attach document and select the appropriate ESX or Hyper-V server version.
The main topics in this document are: Before you start ............................................................................. Determining if your server has a supported configuration................ Installing HBAs in the server.......................................................... Installing or updating the HBA driver ............................................ Installing PowerPath software ....................................................... Installing Unisphere server software............................................... Connecting the storage system to the server in a Fibre Channel switch configuration ..................................................................... Registering the server with the storage system ................................ Verifying storage-system health...................................................... Setting storage-system failover values for the server initiators with Navisphere Manager..................................................................... 3 5 7 9 11 14 27 34 36 38

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

This document covers a Fibre Channel switch configuration only. For information on booting from a SAN, refer to the appropriate Host Connectivity Guide or the EMC Support Matrix on the Powerlink website.
Read the release notes for your storage system, which are available in the Technical Documentation and Advisories section on the Powerlink website. If you have not done so already, complete the configuration planning worksheets (administrative worksheets) in the storage-system configuration planning guide or planning worksheets document. You can generate an up-to-date version of the planning guide customized for your installation from the Plan link on the storage-system support website. You must have a supported Windows host on the same network as the storage-system management ports. You can use this host:
As a client in which you launch the Navisphere Manager. This client was formerly referred 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, which must be a Windows host, but cannot be a server (that is, it cannot send I/O to the storage-system data ports).

You must have a Unisphere Server with a supported Internet browser that is on the same network as the storage-system management ports. The Unisphere Server replaces the Navisphere Management Server. This host can also be the server or a Unisphere management station (formerly referred to as the Navisphere off-array management station). For supported Internet browsers, see the Manager release notes in the Technical Documentation and Advisories section of the Powerlink website. You must have a Linux host that is or will be a server with Fibre Channel connections to the storage system. This server must have a supported server configuration; that is, it must have all required updates, such as hot fixes or patches, installed.
3
You must have one or more supported Fibre Channel host bus adapters (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 different vendors in the same server.
Each Fibre Channel front-end port that you will use on the storage system must have an optical cable. These cables may already be connected for a configuration with an existing storage system or server. We strongly recommend you use OM3 50 m cables. For cable specifications, refer to the storage-systems technical specifications. You can generate this user-customized document from the Learn about storage system link on the storage-system support website (www.emc.com/clariionsupport). You must have one or two Fibre Channel switch fabrics, which may already be installed, and an optical cable for connecting each HBA port to a switch port, if not already connected. We strongly recommend you use OM3 50 m cables. For cable specifications, refer to storage-systems Technical Specifications. You can generate this document using the user customized documentation Learn about 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 storage system that will test the paths from the server to the storage system. You can download an I/O simulator (Iometer) from the following website: 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 system on the server.If you have this information, go to Verifying a servers configuration with E-Lab Interoperability Navigator, page 5 . If you do not have this information, you can generate a server configuration report for your server using the Unisphere Server Utility.
Starting the Unisphere Server Utility on 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 utilitys Welcome screen to generate a report of the servers environment. This option detects if PowerPath or some other failover software, such as DMP, is running. The utility will not detect any other native failover software, such as Linux native multipath (MPIO). After the verification, the utility generates a summary report and saves it to the server. 2. In the summary report, select the Checklist tab to view the information about the server that you need to compare with the E-Lab 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 a username and password. 3. Select E-Lab Interoperability Navigator from the Tools menu on the right-side of the home page.
5
4. From the E-Lab Interoperability Navigator page, select Launch E-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 information based on what is installed on 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 and a Results, EMC Support Statements pane appears on the right with information to help you 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 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 with the server utility. 12. If your server software versions and/or patches or hot fixes are not listed in the Host Attach Wizard report, you must upgrade to a supported version or patch before continuing.
The Host Attach Wizard displays only options that supports EMC. If any of the configuration information on the server utilitys high-availability report cannot 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 Channel data ports, it must have one or more supported HBAs installed.
Before you start

To complete this procedure, you will need one or more supported HBAs with the latest supported BIOS and drivers. For information on supported HBAs, BIOS, and drivers, refer to the E-Lab Interoperability Navigator on the Powerlink website.
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 handled accordingly. 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 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 the servers chassis.
7
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. 4. Plug the servers power cord into the power outlet, and power up the 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 the driver. For information on the supported HBA drivers, refer to the E-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 driver You can download the latest supported version and instructions for installing the Emulex HBA driver from the vendors website: http://www.emulex.com/products/fibre-channel-hbas.html. For a Qlogic driver You can download the latest supported version and instructions for installing the QLogic HBA driver from the vendors website: http://support.qlogic.com/support/oem_emc.asp. For a Brocade driver You can download the latest supported version and instructions for installing the Brocade HBA driver driver from the vendors website: http://www.brocade.com/services-support/driversdownloads/HBA/HBA_EMC.page Any updates, such as hot fixes or patches to the servers operating system that are required for the HBA driver version you will install. For information on any required updates, refer to one of the following:
E-Lab Interoperability Navigator on the Powerlink website
The HBA vendors website
Installing the HBA driver

1. Install any updates, such as hot fixes or patches, to the servers operating system that are required for the HBA driver version you are installing. 2. If the hot fix or patch requires it, reboot the server. 3. Install the driver following the instructions on the HBA vendors 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 when the driver installation is complete.
10
Installing PowerPath software

IMPORTANT If you have a Hyper-V or ESX server, install PowerPath on your Hyper-V or ESX server. Do not install PowerPath on the virtual machine.
Install PowerPath by referring to the appropriate PowerPath Installation and Administration Guide for your operating system. This guide is available in the Technical Documentation and Advisories section 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 Modifying configuration 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 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 hba_driver is the name of the HBA driver module uname -r is the string returned to the console by the uname -r command.
11
If you have Red Hat Linux 3.0 or later, you no longer need to build the HBA driver modules and copy them to the above location. The prebuilt kernel 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 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 the ConfigRequired parameters are set to 0:
options qla2xxx q12xfailover=0 ConfigRequired=0
The variable x andxxx vary with the HBA model.
For Emulex HBAs Edit the /etc/modprobe.conf file to set the value 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 determine which 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
12
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 initrd entry of /boot/grub/grub.conf specifies this .img file.
13
Installing Unisphere server software

IMPORTANT If you have a Hyper-V or ESX server, you must install the host agent or server utility on your Hyper-V or ESX server. Do not install these programs on your virtual machine.
This section describes how to install Unisphere server software, which was previously referred to as the CLARiiON server software or Navisphere server software. If you plan to install Navisphere CLI or Admsnap, you must install them on a virtual machine. For instructions on installing these software programs on a virtual machine, generate a new document and select the operating system running on the virtual machine. Before you begin Refer to the sections below to determine which application to install for host registration and the requirements for installing each of these applications. To run CLARiiON server software, your server must meet the requirements outlined in Requirements for Unisphere server software, page 15. To determine whether to install the Unisphere Host Agent or Unisphere Server Utility to register your HBAs with the storage system, refer to Determining whether to install the Unisphere Host Agent , page 16.
Installing Unisphere server software Depending on which Unisphere server software you are installing, refer to the appropriate section below. Unisphere Host Agent see Installing the Unisphere Host Agent, page 17. Unisphere Server Utility see Installing the Unisphere Server Utility , page 22. Navisphere CLI see Installing Navisphere CLI , page 23
14
Admsnap Utility see Installing the Admsnap Utility , page 25.
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 EMC CLARiiON supported HBA hardware and driver installed. Be connected to at least one SP (two SPs for high availability) in each storage 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 storage system. The TCP/IP network connection allows the server to send LUN mapping information to the storage system and it allows Navisphere Manager or Navisphere CLI to communicate with the storage system over the network. Have a configured TCP/IP network connection to any remote hosts that you will use to manage the servers storage systems, including:
any server whose browser you will use to access Navisphere Manager, 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 storage systems on a remote server, the server must be on a TCP/IP network connected to both the remote server and each SP in the remote servers storage system. The remote server can be running AIX, HP-UX, Linux, Solaris, or the Windows operating system.
15
For information about the specific revisions of the server operating system and the storage-system FLARE and Access Logix software that are required for your version of the host agent, see the release notes for the host agent on the EMC 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 information from Symmetrix storage systems. Register the servers HBAs with the storage system. Alternatively, you can use the Unisphere Server Utility to register the servers HBAs with the storage system. Table 1 describes the host registration differences between the host agent and the server utility.
Table 1 Function Pushes LUN mapping and OS information to the storage system.
Host registration differences between the host agent and the server utility Unisphere Server Utility CX4 series, CX3 series, and CX series storage systems No LUN mapping information is not sent to the storage system. Only the servers name, ID, and IP address are sent to the storage system. Note: The text Manually Registered appears next to the hostname icon in the Manager UI indicating that the host agent was not used to register this server.
Unisphere Host Agent Yes LUN mapping information is displayed in the Manager UI next to the LUN icon or with the CLI using the lunmapinfo command.
16
Function Runs automatically to send information to the storage system.
Unisphere Host Agent Yes No user interaction is required.
Unisphere Server Utility CX4 series, CX3 series, and CX series storage systems No You must manually update the information by starting the utility or you can create a script to run the utility. Since you run the server utility on demand, you have more control as to how often or when the utility is executed. CX4 series, CX3 series, and CX series storage systems No LUN mapping information is not sent to the storage system. Note that if you are using the server utility to upload a high-availability report to the storage system, you must have network connectivity.
Requires network connectivity to the storage system.
Yes Network connectivity allows LUN mapping information to be available to the storage system.
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 version of the Unisphere Host Agent software from the software downloads page 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. This port is used by the host agent. If this port is not opened, the host agent will not function properly. 3. Download the software: a. From the Powerlink website, select Support > Software Downloads and Licensing > Downloads T-Z > Unisphere Server Software. b. Select the Unisphere Host Agent, and then select the option to save the zip file to your server. c. At the command line prompt, navigate to the directory where you 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 the following commands to install the software:
17

32-bit server rpm -ivh UnisphereHostAgent-Linux-32noarch-en_US-version-build.noarch.rpm 64-bit server rpm -ivh UnisphereHostAgent-Linux-64x86-en_US-version-build.x86_64.rpm
where version and build are the version number and the build number of the software.
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.
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 login scripts 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 must modify 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
18
3. If you are setting up a new server, go to Running the Unisphere Host Agent , page 20. If you are just upgrading the host agent or CLI on an existing system, you have finished the upgrade.
Configuring the Unisphere Host Agent

Before you can use the Navisphere CLI navicli register command to configure your storage system, you must make sure the host agent configuration file includes a privileged user, as described in Adding privileged users, page 19.
The pathname of the host agent configuration file is /etc/Unisphere/agent.config.
Adding privileged users If you use Navisphere CLI to configure any storage system, the host agent configuration file must include an entry that defines the person who will issue the CLI commands as a privileged user. To define a privileged user, add a local or remote privileged user by adding 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 of the remote server the person will be using. The default host agent configuration file includes a user root entry. Saving the host agent configuration file 1. If you have finished adding information to the host agent configuration file, save the host agent configuration file. 2. Stop and restart the host agent by entering the following commands: /etc/init.d/naviagent stop /etc/init.d/naviagent start
19
Using the event monitor configuration file The Unisphere Host Agent can monitor storage-system events and take such action as sending e-mail or paging you if specified events occur. The event monitor that ships with Navisphere Manager provides an interactive way to define these events and actions. If you do not have event monitor, you can still define such events and actions by editing the event monitor configuration file. /etc/Unisphere/Navimon.cfg The file is self-documenting; that is, text in it describes how to define events and the actions you want taken if the events occur. You can test the file after editing it using the Navisphere CLI command responsetest, as explained in the Navisphere Command Line Interface Reference.
Running the Unisphere Host Agent

This section describes how to start and stop the host agent and how to test the host agent connections. Starting and stopping the Unisphere Host Agent The host agent starts automatically when you bring the server up to init level 3. When you first start the host agent, look at the system log for the servers operating system to make sure the agent started and no device 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 reported to the host agent in a timely manner, resulting in the host agent taking several minutes to execute a storage-system management task. This behavior is most evident when one host agent is managing multiple storage systems. Also, if the SP event log is large and the host agent configuration file is set up to read all events, 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
20
Stopping the host agent 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 Starting and stopping the Unisphere Host Agent, page 20. 2. Look for any errors on the console and in the operating system log to make sure the agent started and no device errors occurred. 3. Verify that the host agent on the server can see the storage system as 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 (only supported with legacy systems). -h hostname is the IP address of the SP. For each HBA in the server, a listing similar to the following will be displayed. For 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:AC Server Name: siux134 Server IP Address: 128.221.208.134 HBA Model Description: HBA Vendor Description: HBA Device Driver Name: Information about each port of this HBA: SP Name: spa HBA Devicename: sp0 Attaching a Linux Server with EMC PowerPath to a CX4-960 Storage System in a Fibre Channel Switch Configuration
21
Trusted: NO Logged In: YES Source ID: 1 Defined: YES Initiator Type: 0 Storage 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 agent events and host agent errors, and places this information in log files on the server. The host agent error log tracks information about the host agents startup, the host agent shutdown, and errors that might occur, such as the host agents inability to access a device in the configuration file. If problems occur, log files are a good place to start your troubleshooting. Host agent events and errors are logged in /var/log/agent.log. System events 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 version of the Unisphere Server Utility software from the software downloads page on the Powerlink website. 1. Log in to the root account. 2. Download the software: a. From the Powerlink website, select Support > Software Downloads and Licensing > Downloads T-Z > Unisphere Server Software. b. Select the Unisphere Server Utility, and then select the option to save the zip file to your server. c. At the command line prompt, navigate to the directory where you saved the zip file and unzip the file. d. Install the software:
22

32-bit server rpm -ivh UnisphereServerUtil-Linux-32-x86en_US-versionbuild.platform.rpm 32-bit Power Linux server rpm -ivh UnisphereServerUtilLinux-32-powerpc-en_US-versionbuild.ppc64.rpm where version and build are the version number and the build number of the software.
64-bit server rpm -ivh UnisphereServerUtil-Linux-64-x86en_US-versionbuild.x86_64.rpm where version and build are the version number and the build number of the software.
The installation process adds a line to the /etc/rc.d/rc.local file that starts the server utility on reboot, provided root has execute permission for the /etc/rc.d/rc.local file.
Installing Navisphere CLI

This section describes how to install Navisphere CLI. You can install Navisphere 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 version of the Navisphere CLI software from the software downloads page on the Powerlink website. 1. Log in to the root account. 2. If your server is behind a firewall, open the TCP/IP ports listed in Table 2. These ports are used by Navisphere CLI. If these ports are not opened, the software will not function properly.
23
Table 2
TCP/IP ports Software Classic CLI Secure CLI TCP/IP ports 6390, 6391, 6392 443, 2163
3. Download the software: a. From the Powerlink website, select Support > Software Downloads and Licensing > Downloads J-O > Navisphere Server Software. b. Select the Navisphere CLI, and then select the option to save the zip file to your server. c. At the command line prompt, navigate to the directory where you saved the zip file and unzip the file. d. Install the software: 32-bit server rpm -ivh NaviSecureCLI-Linux-32-noarchlanguage-version-build.noarch.rpm 32-bit Power Linux server rpm -ivh NaviSecureCLILinux-32-powerpc-language-version-build.ppc64.rpm 64-bit server rpm -ivh NaviSecureCLI-Linux-64-x86language-version-build.x86_64.rpm
where: language is either en_US, when only the English version is available, or loc, when the localized versions are available (including English). version and build are the version number and the build number of the software.
24
The system displays the word navicli or naviseccli and a series of pound (#) signs. When the installation is complete, the system prompt reappears. 4. Verify that Navisphere CLI is installed by using the rpm -qa | more command.
Installing the Admsnap Utility

To access snapshots of LUNs in the storage system, install the Admsnap Utility. You can install admsnap on the server or on the virtual machine. IMPORTANT Currently, you cannot install admsnap on your virtual machine if your virtual machine is connected to Fibre Channel storage; you must install it on the Hyper-V server. For any updates, refer to the Admsnap Release Notes.
Installation prerequisites Before you can install and use the Admsnap Utility, you must install SnapView on a supported CLARiiON storage system. For a list of supported storage 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 Admsnap Utility software from the software downloads page on the Powerlink website. 1. Log in as root or as a member of an administrative group. 2. Download the software: a. From the Powerlink website, select Support > Software Downloads and Licensing > Downloads S > SnapView. b. Select the Admsnap Utility version you want to download and select the option to save the zip file to your server. c. At the command line prompt, navigate to the directory where you saved the zip file and unzip the file.
25
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_USversion-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 the software. 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 entering the following command: /usr/admsnap/admsnap help This command displays a message about the help command, which includes 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. For information on how to use the MAKEDEV utility, refer to the MAKEDEV man pages. Running the Admsnap Utility Refer to the EMC SnapView Command Line Interface Reference for information on running admsnap commands.
26
Connecting the storage system to the server in a Fibre Channel switch configuration
Use optical cables to connect the storage-system Fibre Channel front-end data ports to the Fibre Channel switch ports and to connect the switch ports to the server HBA ports.
Applications such as MirrorView/A, MirrorView/S, or SAN Copy software may restrict or require the use of certain SP ports. Refer to the application documentation for specific cabling information.
Before you start

To complete this procedure, you will need an optical cable for each switch port you will use. We strongly recommend you use OM3 50 m cables for all optical connections. Specifications for the optical cables that connect the switch to the storage system are in the storage systems technical specifications in the documentation section of Powerlink.
Identifying storage-system Fibre Channel front-end ports

The number and location of the SP Fibre Channel front-end ports for the storage system depend on the UltraFlex Fibre Channel I/O modules installed in the I/O module slots (Figure 1): A0 through A5 for SP A B0 through B5 for SP B
SP A and SP B must have the same type of I/O module in the same slots.
27
B0
0 1
B1
2
B2
3
B3
A0
A1
A2
A3
B4
B5
A4
A5
CL4126
Figure 1
I/O module slots (only standard I/O modules shown)
Standard Fibre Channel I/O modules with Fibre FE ports Your storage system has two 4 or 8 Gb Fibre Channel I/O modules per SP each with two Fibre back-end (BE) ports (0, 1) and two Fibre FE ports (2, 3). These modules are either all 4 Gb modules or all 8 Gb modules. One of these modules is always in slots A0 on SP A and in slot B0 in SP B. The other modules can be in any available slot, unless the storage system has the expansion option and is running a FLARE OE version earlier than 04.28.000.5.5xx, in which case, they cannot be in 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 ports Your storage system may have the following optional Fibre Channel I/O modules with Fibre FE ports: For a base system without the expansion option One or two optional 4 or 8 Gb Fibre 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 FLARE OE version 04.28.000.5.5xx or later One or two optional 4 or 8 Gb Fibre 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 a FLARE OE version earlier than 04.28.000.5.5xx One optional 4 Gb Fibre 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.
28
The 8 Gb modules require FLARE OE version 04.28.000.5.7xx or later.
Module labels and FE port connectors Each Fibre Channel I/O module has a 4 GB Fibre or 8 GB Fibre label on its handle and an optical small-form factor pluggable (SFP) transceiver module in each of its Fibre FE ports. FE port connectivity The Fibre FE ports on a 4 Gb/s Fibre Channel I/O module supports 1/2/4 Gb/s connectivity, and the Fibre FE ports on an 8 Gb/s Fibre Channel I/O module supports 2/4/8 Gb/s connectivity. You cannot use the FE ports on an 8 Gb/s Fibre Channel I/O module in a 1 Gb/s Fibre Channel environment. You can use the FE ports on a 4 Gb/s Fibre Channel I/O module in an 8 Gb/s FC environment if the FC switch ports to which the modules FE ports connect auto-adjust their speed to 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-end data ports on SP A to ports on the switch and connect the same number of Fibre Channel front-end data ports on SP B to ports on same switch or on another switch, if two switches are available.
Customer-installable switches are easily configured. Some are preconfigured to use only ports 0 and 4 for SP connections and only ports 1-3 and 5-15 for HBA connections. With switches set up in such hard zones, you can connect the fibre ports only to ports 0 and 4 and HBAs only to ports 13 and 515. For highest availability with one of these hard zoned switches and a multiple-HBA server, connect either fibre port on SP A to switch port 0 and either FE port on SP B to switch port 4.
For each Fibre Channel (FC) front-end data port on the storage system that you will use for I/O with the server: 1. Locate the FC front-end data port to which you will connect the switch port. For information on identifying the front-end ports using Navisphere Manager, refer to the Navisphere Manager online help.
29
Applications such as MirrorView/A, MirrorView/S, or SAN Copy software may restrict or require the use of certain SP ports. Refer to the application documentation for specific cabling information.
2. Remove the protective cover from the FC front-end data port connector on the SP and from one end of the optical cable, and plug the cable into the data port connector (Figure 2 and Figure 3). 3. Remove the protective cover from the optical connector on the switch port that you will use and from the free end of the optical cable, and plug the cable into the switch port (Figure 2 and Figure 3).
CL4021
Figure 2
Connecting an optical cable
30
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 or more HBA ports to ports on the switch and connect the same number of HBA ports to ports on the same switch or on another switch, if two switches are available. For each server HBA port that you will use for I/O with the storage system: 1. Remove the protective cover from the FC switch port connector and from one end of the optical cable, and plug the cable into the connector. 2. Remove the protective cover from the server HBA port connector and from the free end of the optical cable, and plug the cable into the HBA port connector (Figure 4).
31
CL4044
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 not hard zoned. We recommend single-initiator zoning as a best practice. In single-initiator zoning each HBA port has a separate zone that contains it and the SP ports with which it communicates. For information on Fibre Channel topologies, refer to the EMC Networked Storage Topology Guide on Powerlink.
IMPORTANT: For Linux servers, you must use single-initiator and single-target zoning. A single-initiator single-target zone has HBA port and one storage-system SP port. You can share SP ports among HBA ports, provided each HBA port is in its own zone.
32
To zone the switch: 1. Connect the switch management ports to the network from which you will manage the switches. 2. If the switches are not running the most recent supported firmware version, install this software from the switch vendors website.
For information on the supported switch firmware versions, see the E-Lab Interoperability Navigator on Powerlink.
3. Use either the zoning wizard CD that shipped with the switch or the switch management software to set up the appropriate switch zones. a. To use the zoning wizard CD Using the instructions provided with the CD, run the zoning wizard and select the zone configuration that is applicable to the way that you connected the storage-system Fibre ports and the server HBA ports to the switch. b. To use the switch management software Download the latest version of the switch management software from the switch vendors website, and follow the instructions provided for the software to setup the zones that are applicable to the way that you connected the storage-system Fibre ports and the server HBA ports to the switch.
33
Registering the server with the storage system

IMPORTANT If you have a Hyper-V or ESX server, perform this procedure on your Hyper-V or ESX server.
You must run the Unisphere Server Utility or Unisphere Host Agent on each server connected to the storage system to register the servers HBAs 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 your Hyper-V or ESX server. For updates on SCSI pass through support for virtual machines with FC devices, refer to the E-Lab Interoperability Navigator on Powerlink.
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 storage systems, and displays a list of the ones it finds. 3. In the server utility, enter u to register the server with each storage system the utility found.
34
The utility sends the servers name and IP address to each storage system. Once the server has storage on the storage system, the utility also sends the Linux device name and volume or file system information for each LUN (virtual disk) in the storage 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 servers HBAs with the storage system. Starting the host agent Log in as root and enter the following command: /etc/init.d/hostagent start
Verifying HBA registration with Navisphere Manager

1. From the Navisphere Manager Storage tree, right-click the icon for the 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 Yes under the Registered columns. If not, refer to the Troubleshooting Flowcharts section on the CLARiiON Tools page on the Powerlink website.
To access the CLARiiON Tools page, use the Navigator drop-down menu at the top right of the Powerlink home page.
Once all HBAs belonging to a server are registered, you can assign the server to storage groups.
35
Verifying storage-system health

Use the storage-system verification wizard that is part of the Unisphere Service Manager (USM), which replaces the Navisphere Service Taskbar, to: Validate the connectivity of the storage-system hardware components 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 the Powerlink website to a Windows management station that is connected to the storage-systems management ports. If you do not have a Windows management station, your service provider can run this wizard. To access the CLARiiON Tools page, use the Navigator drop-down menu at the 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 the CLARiiON Tools page on the Powerlink website to a Windows Unisphere server that is connected to the storage-systems management ports.
To access the CLARiiON Tools page, use the Navigator drop-down menu at the top right of the Powerlink home page.
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.

36
3. From the System screen, select Diagnostics > Verify Storage System and follow the instructions that appear. 4. Review the report that the wizard generates, and if it lists any problems, try to resolve them. For assistance in resolving any problems, see the troubleshooting flowcharts for the storage system on the CLARiiON Tools page of the Powerlink website.
37
Setting storage-system failover values for the server initiators with Navisphere Manager
Use the Navisphere Manager Failover Setup wizard to set the storage-system failover values for all HBA initiators belonging to the server: 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 then click Next. 4. In the Select Host dialog box, select the server you just connected to the 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 the type of software running on the server. IMPORTANT If you enter incorrect values the storage system could become unmanageable and unreachable by the server, and the servers failover software could stop operating correctly. If you have a Hyper-V or ESX server, set the storage-system failover values 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.
38
For information on which versions of failover support ALUA for CLARiiON storage systems, refer to the PowerPath release notes or the Native Multipath Failover based on DM-MPIO for v2.6.x Linux Kernel and EMC Storage Arrays Configuration Guide on the Powerlink website or to EMC Knowledgebase solution emc99467.
7. In Configuration Summary, review the configuration and all settings. 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 to re-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 to set 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.
39
Verifying your high-availability Fibre Channel configuration

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

1. Open a console window. 2. Navigate to the Unisphere bin directory and run the server utility: /opt/Unisphere/bin/serverutilcli
Using the server utility to verify your high-availability configuration

1. From the Unisphere Server Utilitys Welcome screen, select option 3 to generate a report of the servers environment. The utility determines if the server is configured for high availability by verifying that the server has at least one connection path to each storage system SP, and that PowerPath or some other failover software, such as DMP, is running. It does not detect native failover software, such as Linux native multipath (MPIO). 2. Review and resolve any issues reported on the Issues tab of the generated report before continuing with the installation process.
40
Configuring an existing storage system

To configure an existing storage system with Navisphere Manager, use either the Unisphere Service Manager wizards or the Storage tree options of Navisphere Manager.
Before you start

You need the completed storage-system disk information worksheet from the storage-system configuration planning guide or administrative worksheets (administrative worksheets) document. You can generate this guide using the user-customized documentation link from the storage-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 been replaced with "Storage Groups and the Storage Access tab has been removed from the storage-system Properties page.
When you started this installation if the storage system was either a new storage system that will be connected to multiple servers or an existing storage system that is connected to only one server, you must either enable storage groups using Navisphere Manager 6.29 or later or to 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 the storage 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 the storage system, and click Properties. 2. Click the Storage Access tab, and under Data Access, select Access Control Enabled.
41
3. Click OK.
Allocating storage to an existing storage system with the Provision or Allocate wizard
Starting with UI version 6.28.10.xx, the Allocate wizard has been renamed to Provision wizard. Like the Allocate wizard, use the Provision wizard, found in the Navisphere Manager taskbar, to create storage system storage and provide server access to this storage. 1. Locate your completed storage-system disk information worksheet so 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 the Provision or Allocate wizard on the Storage Management tab to create them. 4. If you want to assign existing LUNs or thin LUNs to the server, use the Assign wizard on the Storage Management tab to assign them.
For high availability, a host can connect to only one storage group per storage system at a time. If you connect a host that is already connected to another storage group, the host will disconnect from the first storage group. When you disconnect a host from a storage group, and then connect it to a different storage group, the host can no longer perform I/O to the first 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 LUNs reside In the Navisphere Manager Storage tree:
42
Click the icon for the storage system with the storage group whose 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 that server appears under the storage group icon. If you know the name of the server to which the storage group is assigned In the Navisphere Manager Hosts tree: Click the icon for the server to which you assigned the LUNs and 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 not have selected the Assign LUNs to a server option in the Select Servers page of the Provision wizard. You can use the Assign wizard 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 worksheet so 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 Navisphere Manager Storage tree, depending on the UI and FLARE version that you identified earlier, right-click the storage-system icon and do one of the following: Click Storage Pools Operations > Create LUNs ; create a new RAID group or select an existing one; create new LUNs on the RAID group. Click Bind LUN; create a new RAID group or select an existing one; bind LUNs on the RAID group
For details on creating traditional LUNs and RAID groups, use the Navisphere Manager help. 3. Create thin LUNs on thin pools.
You must use Navisphere Manager UI version 6.28.10.xx. The storage system must be running FLARE 04.28.000.5.5xx or later and the Virtual Provisioning enabler must be installed on the storage system.
43
To create thin LUNs on thin pools In the Navisphere Manager Storage tree, right-click the storage-system icon and click Storage Pool Operations > Storage Pools and in the Create Storage Pool dialog box, select Thin Pools. For details on creating thin LUNs and 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 Storage Groups. For details on creating storage groups, use the Navisphere Manager 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 servers connected to the storage group. If a LUN is placed in more than one storage group, all servers in those storage groups must be in a cluster configuration.
To add LUNs to storage groups Right-click the icon for the storage group to which you want to add LUNs, and click Select LUNs. For details on adding LUNs to storage groups, use the Navisphere Manager help. 6. Assign a server to a new or existing storage group. To assign servers to storage groups In the Navisphere Manager tree, right-click the icon for the storage group to which you want to assign a server, and then click Connect Hosts. For details on assigning servers to storage groups, use the Navisphere Manager help.
For high availability, a host can connect to only one storage group per storage system at a time. If you connect a host that is already connected to another storage group, the host will disconnect from the first storage group. When you disconnect a host from a storage group, and then connect it to a different storage group, the host can no longer perform I/O to the first storage group.
7. Verify that the server was assigned to the storage group.

44
To verify that a server is assigned to a storage group In the Navisphere Manager tree: Click the icon for the storage system with the storage group whose 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 that server 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 the server, the server cannot see the new LUN until it is fully initialized (completely bound). The time the initialization process takes to complete varies with the size of the LUN and other parameters. While a LUN is initializing, it is in a transitioning state, and when the initialization is complete, its state becomes normal. To determine the state of a LUN: 1. From the Navisphere Manager Storage tree, navigate to the LUN you 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, enter the following commands: For a server with HBA connections to the storage system: rmmod driver_module modprobe driver_module (or insmod driver_module)
45
where driver_module is the driver module name.
Verifying that PowerPath for Linux sees all the paths to the LUNs
1. Rescan for disks (LUNs). 2. On the server, configure PowerPath: powermt config 3. View the LUNs available to the server with the PowerPath command: powermt display dev=all class=clariion 4. Using the output from the command above, verify that none of the paths to the storage system are dead.
46
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 send data to a LUN, Linux must recognize the disk, and you must partition the disk and then create and mount a file system on it. For information on how to perform these tasks, refer to your operating system documentation. Before a virtual machine can send data to a virtual disk that is a VMFS volume, you must do the following: For a Linux virtual machine: Partition the VMware virtual disk. Create and mount a file system on the partition.
47
Sending Linux disk information to the storage system

If the Unisphere Host Agent is installed on the server, stop and then restart it to send the storage system the operating systems device name and volume or file system information for each LUN that the server sees. Navisphere Manager displays this information in the LUN Properties Host page for each LUN. The Unisphere Server Utility does not send operating system LUN mapping information to the storage system, so this procedure is not required. IMPORTANT Perform this procedure on your Hyper-V or ESX server.
Stopping the host agent

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/hostagent start
Verifying that the storage system received the LUN information using Navisphere Manager
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 LUN you want to verify. b. Right-click the icon for the LUN, and click Properties. 3. Verify that the Properties page displays a physical device and logical device name for the LUN.
48
Verifying your failover configuration with PowerPath

Perform the following steps to verify that the server can send data to and receive data from the storage system and PowerPath shows the paths from the server to the LUNs that you expect for your configuration.
You can download an I/O simulator (Iometer) for writing data to the storage system 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 all applications that are accessing the storage system and disable user logins 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 the output of the powermt display dev= x every=2 command, and disconnect the cable to that HBA. 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.
49
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. Restart any applications that you stopped and re-enable any user logins to the server that you disabled.
50
Copyright 2009-2010 EMC Corporation. All Rights Reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks mentioned herein are the property of their respective owners.
51

Attaching Server To Storage System - Master

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Attaching Server To Storage System - Master

Uploaded by

Copyright:

Available Formats

Here is Your Customized Document

Your Configuration is:

Content Creation Date 2010/10/20

Content Creation Date 2010/10/20

Content Creation Date 2010/10/20

Before you start

Determining if your server has a supported configuration

Starting the Unisphere Server Utility on a Linux server

Generating a high-availability report for a server

Verifying a servers configuration with E-Lab Interoperability Navigator

Installing HBAs in the server

Before you start

Installing or updating the HBA driver

Before you start

E-Lab Interoperability Navigator on the Powerlink website

The HBA vendors website

Installing the HBA driver

Installing PowerPath software

Before you install PowerPath

The variable x andxxx vary with the HBA model.

Installing Unisphere server software

Admsnap Utility see Installing the Admsnap Utility , page 25.

Requirements for Unisphere server software

Determining whether to install the Unisphere Host Agent

Function Runs automatically to send information to the storage system.

Unisphere Host Agent Yes No user interaction is required.

Requires network connectivity to the storage system.

Installing the Unisphere Host Agent

Configuring the Unisphere Host Agent

Running the Unisphere Host Agent

Installing the Unisphere Server Utility

Installing Navisphere CLI

Installing the Admsnap Utility

Before you start

Identifying storage-system Fibre Channel front-end ports

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

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

Connecting an optical cable

Sample cabling between a storage system and two switches

Cabling the switch ports to the server HBA ports

Sample cabling for a Fibre Channel switch configuration

Zoning the switches

Registering the server with the storage system

Running the Unisphere Server Utility on a Linux server

Starting the Unisphere Host Agent

Verifying HBA registration with Navisphere Manager

Verifying storage-system health

2. Log in to your system.

Verifying your high-availability Fibre Channel configuration

Starting the Unisphere Server Utility on a Linux server

Using the server utility to verify your high-availability configuration

Configuring an existing storage system

Before you start

Enabling storage groups or access control with Navisphere Manger

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

Verifying that each LUN is fully initialized using Navisphere Manager

Making LUNs visible to a Linux server

where driver_module is the driver module name.

Preparing LUNs to receive data

Sending Linux disk information to the storage system

Stopping the host agent

Starting the host agent

Verifying your failover configuration with PowerPath