Attaching Server to Storage System- Master 1073670

Here is Your Customized DocumentYour Configuration is:

Action to Perform - Attach serverStorage-System Model - CX4-960Storage-System Status - NewConnection Type - Fibre Channel SwitchServer Status - NewServer Operating System - SolarisPath Management Software - EMC PowerPathHBAs to Install - QLogic HBA

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: 1073670

Content Creation Date 2010/3/8



CX4 SeriesAttaching a Solaris Server withEMC PowerPath to a CX4-960

Storage System in a Fibre ChannelSwitch Configuration

This document explains how to attach a Solaris server with EMC®PowerPath® to a CX4-960 storage system in a Fibre Channel switchconfiguration.

The main topics are:

Before you start ............................................................................. 2Determining if your server has a supported configuration................ 4Installing HBAs in the server.......................................................... 7Installing or updating the HBA driver ............................................ 9Modifying Solaris system settings .................................................. 11Installing PowerPath software........................................................ 13About EMC CLARiiON server software.......................................... 15Installing CLARiiON server software.............................................. 18Disabling Sun StorEdge Traffic Manager to use PowerPath .............. 39Connecting the storage system to the server in a Fibre Channelswitch configuration ..................................................................... 40Registering server with the storage system...................................... 47Verifying storage-system health...................................................... 50Setting storage-system failover values for the server initiators........... 52Verifying your high-availability Fibre Channel configuration ........... 54Installing CLARalert software ........................................................ 56Configuring a new storage system .................................................. 59Preparing LUNs to receive data ...................................................... 70Sending Solaris disk information to the storage system .................... 71Verifying your failover configuration with PowerPath ..................... 72

1

Before you start

❑ 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 in the storage-system configuration planningguide or planning worksheets document. You can generate anup-to-date version of the planning guide customized for yourinstallation from the Plan link on the storage-system supportwebsite.

❑ A supported Windows host on the same network as thestorage-system management ports. You can use this host:

As a Navisphere® management station

To run the Navisphere Service Taskbar, which runs only ona Windows host.

As a CLARalert® monitor station, which must be a Windowshost, but cannot be a server (that is, it cannot send I/O to thestorage-system data ports).

❑ A Navisphere® management station with a supported Internetbrowser that is on the same network as the storage-systemmanagement ports. This host can also be the server or a Navisphereoff-array management station. For supported Internet browsers,see the Navisphere Manager release notes in the TechnicalDocumentation and Advisories section of the Powerlink website.

❑ A Solaris host that is or will be a server with Fibre Channelconnections to the storage system. This server must have asupported server configuration; that is, it must have all requiredupdates, such as hot fixes or patches, installed.

❑ One or more supported QLogic Fibre Channel host bus adapters(HBAs), which may already be installed in the server. Theseadapters must have the latest supported BIOS and driver.

Never mix Fibre Channel HBAs from different vendors in the same server.

❑ An optical cable for each storage-processor (SP) Fibre Channel portyou will use on the storage system. (Each storage processor has two

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

http://Powerlink.EMC.com


ports.) These cables may already be connected for a configurationwith an existing storage system or server. We strongly recommendyou use OM3 50 µm cables. For cable specifications, refer tostorage-system’s Technical Specifications. You can generate thisdocument using the user customized documentation Learn aboutstorage system link on the storage-system support website.

❑ One or two Fibre Channel switches, 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 OM350 µm cables. For cable specifications, refer to storage-system’sTechnical Specifications. You can generate this document using theuser customized documentation Learn about storage system linkon the storage-system support website.

❑ A method for writing data to a LUN on the storage system thatwill test the paths from the server to the storage system. You candownload an I/O simulator (Iometer) from the following website:http://www.iometer.org/.

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

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 server’sconfiguration with E-Lab Interoperability Navigator, page 5 . If you do nothave this information, you can generate a server configuration reportfor your server using the Navisphere Server Utility.

Starting the Navisphere Server Utility on a Solaris server

1. Open a shell window.

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

/opt/Navisphere/bin/naviserverutil

Starting the Navisphere Server Utility on a Solaris server from the CD

If you have version 6.28 or earlier of the server utility, you can start itfrom the CD as described below.

1. In the server’s drive, insert the server support CD, which shippedwith the storage system.

2. Navigate to the Solaris directory:

/cdrom /cdrom0/solaris

3. Run the server utility:

./naviserverutilcli

Generating a high-availability report for a server

1. In the Navisphere Server Utility select option 3 from the serverutility’s Welcome screen to generate a report of the server’senvironment.

This option detects if PowerPath or some other failover software,such as DMPor Sun StorEdge Traffic Manager, is running. After the


verification, 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 against theE-Lab™ Interoperability Navigator information.

Verifying a server’s 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 already installed on the server or what you intendto install 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. When the Results link appears, click it 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 aboutyour server software or the checklist report you generated usingthe server utility.



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

The Host Attach Wizard only displays options that are supported byEMC. If any of the configuration information on the server utility’s highavailability report cannot be found in the wizard, then it is not supported.


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.

Before you start

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

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

Installing HBAs

! CAUTION

HBAs 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. Severecomponent damage can result.

1. If the server is powered up:

a. Shut down the server’s operating system.

b. Power down the server.

c. Unplug the server’s power cord from the power outlet.

2. Put on an ESD wristband, and clip its lead to bare metal on theserver’s 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 server’s 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 version of the supported HBA driver.

You can download the latest supported version and instructionsfor installing the QLogic HBA driver from the vendor’s website:http://support.qlogic.com/support/oem_emc.asp.

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

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

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

E-Lab™ Interoperability Navigator on the Powerlink website

The HBA vendor’s website

Installing the HBA driver

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

2. If required by hot fix or patch, reboot the server.

3. Install the driver following the instructions on the HBA vendor’swebsite.

4. If you installed the QLogic HBA driver, set the parameters inthe /kernel/drv/qla2xxx.conf, except for the persistent bindingparameter, to the values required for PowerPath as described in the



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


HBA driver instructions. You will set the persistent bindings afterthe storage system is connected to the server through the switches.

Some driver updates may require you to reboot the server.

5. Reboot the server when the installation program prompts you toreboot.

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


Modifying Solaris system settings

This section lists the recommended Solaris environment setting changeswith a CLARiiON storage system.

Modifying the Solaris system specification file

You must modify the sd_io_time and sd_max_throttle parameters inthe /etc/system file when operating in a Solaris environment.

IMPORTANT

In Solaris, the sd_max_throttle settings are global, so all devicesincluding non-meta devices will also be affected.

1. Set sd_io_time to 60 seconds.set sd:sd_io_time = 0x3C

This setting prevents the host from issuing warning messageswhile non-disruptive operations are performed on the EMC storagesystem.

2. Set sd_max_throttle to 20.set sd:sd_max_throttle = 20

This setting prevents the host from over-sending tag queuingcommands which may cause scsi cmd timeout and scsi bus reset.

A maximum throttle setting of 20 means that each host deviceinstance will have no more than 20 commands outstanding(incomplete I/Os from the standpoint of the operating system) atany given time. This setting is suitable for many environments.However, in some situations this value can be further fine-tuned forconfiguration-specific optimizations. For example, in the case ofmeta devices (which have more physical devices on the back-endand can thus physically process more I/Os in parallel), it may be


beneficial to increase the queue depth to 32. Contact your EMCCustomer Service representative for assistance.

Configuring host warnings

You can configure the host to send warnings to the console instead ofjust to the log file. This step is optional.

1. Add the following line to the /etc/syslog.conf file:

localx.Warn /dev/sysmsg

where x is a value that is not used by any other local setting in/etc/syslog.conf.

For example:local0.Warn /dev/sysmsg

The separator between local x.Warn and /dev/sysmsg must be a tabcharacter.

2. Set the RAD_LOG_FACILITY environment variable toLOG_LOCAL x, where x is the number you used in the local settingof the /etc/syslog.conf file.

For example:

For csh, enter:setenv RAD_LOG_FACILITY LOG_LOCAL0

For sh, enter:RAD_LOG_FACILITY=LOG_LOCAL0;export RAD_LOG_FACILITY


Installing PowerPath software

To install PowerPath, refer to the appropriate PowerPath Installationand Administration Guide for your operating system. This guide isavailable in the Technical Documentation and Advisories section on thePowerlink website.

Before you install PowerPath

In the /etc/system file, make sure the timeout value is setto 60 seconds. This minimizes path failover time withoutcompromising online storage-system microcode or basecode upgrades. The entry must be a hexadecimal number:set ssd: ssd_io_time = 0x3C

Optionally, configure the host to send warnings to the consoleinstead of just to the log file:

1. Add the following line to the /etc/syslog.conf file:

localx.Warn /dev/sysmsg

where x is a value that is not used by any other local setting in/etc/syslog.conf .

For example:local0.Warn /dev/sysmsg.

The separator between local x.Warn and /dev/sysmsg must be a tabcharacter.

2. Set the RAD_LOG_FACILITY environment variable toLOG_LOCAL x, where x is the number you used in the localsetting of the /etc/syslog.conf file.

For example:

For csh, enter:setenv RAD_LOG_FACILITY LOG_LOCAL0



For sh, enter:RAD_LOG_FACILITY=LOG_LOCAL0; exportRAD_LOG_FACILITY

Share the root file system of the target system in a way that allowsroot access over NFS to the installing system, if you want to installPowerPath offline over NFS. You can use a command such as thefollowing on target_sys to share the root file system on target_sys sothat installer_sys has root access:

share -F nfs -d “root on target_sys“ -o ro,rw= installer_sys,root=installer_sys /

If the base directory of the package (the default is /opt ) is not partof the root file system, it also needs to be shared with root access.

If the Navisphere host agent is running on the server, stop it:/etc/init.d/agent stop

Stop all applications that use PowerPath if you are upgrading fromPowerPath 4.0.4 or later. For example, unmount all file systemsmounted on PowerPath pseudo devices. If you do not stop theseapplications, uninstalling PowerPath 4.0.2 or later in preparation forthe upgrade will abort with a message indicating that PowerPathpseudo devices are still in use. If this happens, you must either stopapplications using PowerPath and try pkgrm again, or reboot theserver and postpone the upgrade.

Prepare for the cluster, if you are installing PowerPath for a clusterenvironment, as described in PowerPath for Solaris Installation andAdministration Guide in PowerPath section of the Powerlink website.

TIP To find this document on the Powerlink website, enter PowerPath forSolaris in the Powerlink search field.




About EMC CLARiiON server software

This section describes all the available CLARiiON server software.Your operating system or configuration may not support all thesoftware mentioned.

As of release 6.29, the server support CD no longer ships with your storagesystem.

Navisphere Storage System Initialization Utility

Navisphere Command Line Interface (CLI)

Navisphere Host Agent

Navisphere Server Utility

Admsnap Utility

About the Navisphere Storage System Initialization Utility

For Fibre Channel storage systems, use the Navisphere® initializationutility to discover storage systems and set network parameters (IPaddress, subnet mask, and default gateway). In addition, for iSCSIstorage systems with iSCSI data ports attached to Windows servers, usethe utility to set network parameters for these ports.

You can install it on a server or other host such as a Navisphereoff-array management station. The only requirement is that the hostbe connected to the same network subnet as the storage-systemmanagement ports.

About the Navisphere CLI

The CLI complements or is an alternative to Manager. It provides acommand line interface for storage-system management, includingstorage provisioning, status and configuration information retrieval,and control. You can use the CLI to automate management functions


through shell scripts and batch files. For more information, refer to theEMC Navisphere Command Line Interface (CLI) Reference Guide.

About the Navisphere Host Agent

The host agent registers the server’s host bus adapter (HBA) with theattached storage system when the host agent service starts. This actionsends the initiator records for each HBA to the storage system. Initiatorrecords are used to control access to storage-system data.

The agent can then retrieve information from the storage systemautomatically at startup or when requested by Navisphere Manageror the CLI.

The host agent can also:

Send operating system drive mapping information to the attachedCLARiiON® storage systems.

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

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

About the Navisphere Server Utility

The server utility allows you to perform the following functions:

Update server information to the storage system — Lets you sendthe server name and IP address to the storage system and, if neededlater on, allows you to update or view this data.

Verify server high availability (HA) — Lets you determine if theserver is configured for high availability (HA) by verifying thatthe server has at least one connection path to each storage-systemSP, and that PowerPath® or some other failover software, such asVMware native, DMP, PV Links, or HP native failover for 11iV3is running. The utility does not detect any other native failoversoftware, such as Sun StorEdge Traffic Manager or Linux nativemultipath (MPIO).

This feature is not available on iSCSI servers.


Use the snapshot feature (Navisphere Express only) — On storagesystems with Navisphere Express, you can start and stop a snapshoton the source server (server assigned to the source virtual disk orsource LUN), or you can allow or remove access to the snapshot bythe secondary server (server assigned to the snapshot).

You can run the Navisphere Server Utility from the CD or you caninstall it on the servers that are connected to the storage system. Westrongly recommend that you install the utility on each server that isconnected to the storage system.

About the Admsnap Utility

The Admsnap Utility is an executable program that you can runinteractively or with a script to manage SnapView® clones andsnapshots. The Admsnap Utility resides on the servers connected tothe storage system with the SnapView driver installed.

Use admsnap commands to:

Scan for new storage devices

Make storage devices inaccessible to the server operating system

Flush cached data to disk

List current snapshot devices

Map and unmap to a SnapView session

Start and stop a SnapView session

If you upgraded your storage system to Navisphere Manager and want tomanage snapshots, you must use the SnapView software and the AdmsnapUtility. For more information on SnapView and admsnap, refer to theNavisphere Manager help and the EMC SnapView Command Line InterfacesReference.


Installing CLARiiON server software

This section describes how to install CLARiiON server software.

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

To determine whether to install the Navisphere Host Agent orNavisphere Server Utility to register your HBAs with the storagesystem, refer to Determining whether to install the host agent or serverutility , page 18.

To run CLARiiON server software, your server must meet therequirements outlined in Requirements for CLARiiON serversoftware, page 20.

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

Navisphere Host Agent and/or Navisphere CLI – see Installing theNavisphere Host Agent and/or CLI , page 21.

Navisphere Server Utility – see Installing the Navisphere ServerUtility , page 34.

Admsnap Utility – see Installing the Admsnap Utility , page 35.

Determining whether to install the host agent or server utility

Depending on your application needs, you can install the host agent,server utility, or both on an attached server.

To register the server’s HBAs with the storage system, you must use theNavisphere Server Utility or Navisphere Host Agent on each serverthat is connected to the storage system.


IMPORTANT

If you want to install both applications, you must install version 6.22.20or later of the server utility either before or after you install the hostagent. The registration feature of the server utility will be disabledand the host agent will be used to register the server’s HBAs to thestorage system.

Prior to version 6.22.20 of the server utility, you could not install thehost agent and server utility on the same server. However, you couldinstall them on different servers that are connected to the same storagesystem.

Table 1 describes the differences between the host agent and the serverutility on a server attached to a storage system.

Depending on the version of the server utility, some of the features listed inTable 1 may not be available.

Table 1 Differences between the host agent and the server utility

Function Host agent 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 server’s 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.

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.

Provides high-availability(HA) validation.

No – You can run the server utility’sHA validation feature from the CDwithout having to install the serverutility.

CX4 series, CX3 series, and CX series storage systemsYes – The HA validation feature verifies that failover software isinstalled on the server and that working paths exist between theserver and each SP in the storage system.


Function Host agent Server utility

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.

Requires installation. Yes – You must install the hostagent on the server.

CX4 series, CX3 series, and CX series storage systemsNo – You can run the server utility from the CD. However, werecommend that you install it on the server.

Note: If you install the host agent and then version 6.22.20 or later of the server utility, the server utility’s registration service feature willnot be installed. Prior to version 6.22.20 of the server utility, you could not install the host agent and server utility on the same server.

Requirements for CLARiiON server software

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

Run a supported version of the Solaris operating system.

Be a Sun SPARCserver, SPARCstation, or Enterprise server runninga supported version of a Solaris operating system. For the latestrequirements see the software product release notes.

For Fibre Channel connections, have the EMC CLARiiONsupported 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 the CLI to communicate with the storagesystem over the network.

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

any server whose browser you will use to access Manager 6.X,

a supported Windows server running Storage ManagementServer software,

any AIX, HP-UX, Linux, VMware ESX Server, NetWare, Solaris,or Windows server running the CLI.


If you want to use the CLI on the server to manage storage systems ona remote server, the server must be on a TCP/IP network connectedto both the remote server and each SP in the remote server’s storagesystem. 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.

Power-cycling the storage system

Do not issue verify_disk_array while the SP is powering up. You must waituntil the SP has completed the powerup cycle.

Solaris does not generally support the powering down of a storagedevice while the Solaris server is running. There are, however,occasions when we recommend power-cycling a storage system as partof service. When power-cycling a storage system, it is important toobserve the following guidelines:

If the system is booted from the storage system, the server must beshut down before the storage system is powered down.

If the system does not boot from the storage system, it is stillimportant to unmount any file systems on the storage system beforepower-cycling the storage system.

We recommend that you stop all I/O, including raw I/O, beforepower-cycling the storage system. However, the system will notpanic if raw I/O occurs when the storage system is powered down.If there is any attempt at I/O while the storage system is off orwhile it is going through its boot sequence, the failover softwarewill attempt to fail over.

Installing the Navisphere Host Agent and/or CLI

You can install both the host agent and CLI, or you can install themseparately. If you will install both, install the host agent first.



If you want to install the host agent and use some of the features in the serverutility, see Determining whether to install the host agent or server utility , page 18.

Installing the host agent on a Solaris server

This section applies to version 6.26 or later of the Navisphere HostAgent software package.

Download the most recent version of the host agent from the softwaredownloads page on the Powerlink website. If you are installing version6.28 or earlier, you can install the software from the server support CD;however, the CD may not contain the most recent version for yourconfiguration.

1. If you are installing the host agent, make sure that each storagesystem is connected to the Solaris server where you are installingthe host agent.

2. At the Solaris server, log in as superuser (root).

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

4. To download the software, do the following:

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

b. Select the host agent version you want to download and selectthe option to save 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 Sun-NAVIAGNT-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:

Version 6.29 or later:




Sun Solaris – pkgadd -d NaviHostAgent-Solaris-32-sparc-en_US-version-build.pkg

Sun Opteron – pkgadd -d NaviHostAgent-Solaris-32-x64-en_US-version-build.pkg

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

Version 6.28 or earlier:pkgadd -d NAVIAGNT.pkg

5. If you are installing version 6.28 or earlier, you can install thesoftware from the server support CD; however, the CD may notcontain the most recent version for your configuration. To installthe software from the server support CD, do the following:

a. In the server’s drive, insert the server support CD that shippedwith your storage system.

b. In a shell, enter the following command to install the software:

cd /cdrom/cdrom0/solaris pkgadd -d /solaris/NAVIAGNT.pkg

6. Press Enter and y to begin the installation.

The installation program looks for any agent configuration filesyou may already have on your system. If the program finds anexisting configuration files, it displays a message like the following:

At Least 1 saved config file exists for NavisphereAgent.Please select 1 of the following:[1]Restore/etc/Navisphere/.Naviagent-config.000120:1059[2]Restore/etc/Navisphere/.Naviagent-config.000121:1408[3] QuitSelect number 1 - 3.

7. If the program finds any existing configuration file, select theexisting file you want to serve as the agent configuration file. Thesoftware will retain that file and rename it with the required agentfilename, agent.config. Generally, you will want to use the most


recent file, as shown by the numeric date suffix. To use the defaultconfiguration file, specify the number for the Quit option.

When the installation of the host agent is complete, a successfulmessage is displayed.

8. If you installed the host agent from the server support CD, wheninstallation is complete, exit the /cdrom directory (for example,execute cd /), and then remove the CD from the server’s CD drive.

Any user who can access the management station can change or delete theNavisphere files you just installed. You may want to change permissionson these files to restrict access to them.

9. Verify the installation by entering the command pkginfo -l | grepNAVI*.

A message similar to the following may be displayed:NAVIAGENT: Navisphere Disk Array Management Tool (Agent)

Installing the Navisphere CLI on a Solaris server

This section applies to version 6.26 or later of the Navisphere CLIsoftware package.

Download the most recent version of the Navisphere CLI from thesoftware downloads page on the Powerlink website. If you areinstalling version 6.28 or earlier, you can install the software from theserver support CD; however, the CD may not contain the most recentversion for your configuration.

1. Log in as superuser (root).

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

Navisphere Software TCP/IP ports

Classic CLI 6390, 6391, 6392

Secure CLI 443, 2163





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


unzip Sun-NAVICLI-version.zip




Sun Solaris – pkgadd -d NaviCLI-Solaris-32-sparc-en_US-version-build.pkg

Sun Opteron – pkgadd -d NaviCLI-Solaris-32-x64-en_US-version-build.pkg


Version 6.28 or earlier:

pkgadd -d NAVICLI.pkg



b. In a shell, enter the following command:

cd /cdrom/cdrom0/solaris pkgadd -d /solaris/NAVICLI.pkg



5. Select the packages that you want to install by doing one of thefollowing:

Enter 1 (to install classic CLI)

Enter 2 (to install secure CLI)

Enter All (to install both)

6. When the installation of the CLI is complete, a successful messageis displayed.

7. If you installed the CLI from the server support CD, wheninstallation is complete, exit the /cdrom directory by entering cd /,and then remove the CD from the server’s CD drive.



Depending on what you installed, one of the following may bedisplayed:

NAVICLI: Navisphere Disk Array Management Tool (CLI)

NAVISCLI: Navisphere Disk Array Management Tool

(CLI)

Installing the host agent and/or Navisphere CLI on a Solaris server

This section applies to version 6.24 or earlier of the Navisphere HostAgent/ CLI software package.

Download the most recent version of the host agent/CLI from thesoftware downloads page on the Powerlink website. If you areinstalling version 6.28 or earlier, you can install the software from theserver support CD; however, the CD may not contain the most recentversion for your configuration.

1. If you are installing the host agent, make sure that each storagesystem is connected to the Solaris server where you are installingthe host agent.

2. At the Solaris server, log in as superuser (root).



3. If your server is behind a firewall, open the TCP/IP ports listed inTable 3. These ports are used by the host agent and CLI. If theseports are not opened, the software will not function properly.

Table 3 TCP/IP ports

Navisphere Software TCP/IP ports

Host Agent 6389

Classic CLI 6390, 6391, 6392

Secure CLI 443, 2163

4. To download software for your storage system, do the following:


b. Select the host agent/CLI version you want to download andselect the option to save the zip file to your server.


unzip Sun-NAVIAGNT-version.zip


d. Enter the following command to install the host agent and/orCLI package:

pkgadd -d NAVIAGNT.pkg



b. In a shell, enter the following command:

cd /cdrom/cdrom0/solaris pkgadd -d /solaris/NAVIAGNT.pkg



6. Select the packages that you want to install by doing one of thefollowing:

Enter 1 (to install the host agent)

Enter 2 (to install CLI)

Enter All (to install both the host agent and CLI)

7. Enter y and y to begin the installation.

The installation program looks for any agent configuration filesyou may already have on your system. If the program doesnot find any agent configuration files, then you have finishedinstalling the agent; go to step 10. If the program does find anyexisting configuration files, it displays a message like the following:

At Least 1 saved config file exists for NavisphereAgent.Please select 1 of the following:[1]Restore/etc/Navisphere/.Naviagent-config.000120:1059[2]Restore/etc/Navisphere/.Naviagent-config.000121:1408[3] QuitSelect number 1 - 3.

8. Select the existing file you want to serve as the agent configurationfile. The software will retain that file and rename it with the requiredagent filename, agent.config. Generally, you will want to use themost recent file, as shown by the numeric date suffix. To use thedefault configuration file, specify the number for the Quit option.

9. When the installation of the host agent is complete, a successfulmessage is displayed. If you are also installing the CLI, enter y atthe CLI installation prompt as you did for the agent.

10. If you installed the host agent/CLI from the server support CD,when installation is complete, exit the /cdrom directory by enteringcd /, and then remove the CD from the server’s CD drive.




Depending on what you installed, some of the following may bedisplayed:

NAVIAGENT: Navisphere Disk Array Management Tool(Agent)

NAVICLI: Navisphere Disk Array Management Tool (CLI)

NAVISCLI: Navisphere Disk Array Management Tool (CLI)

What next?

Before you can use the host agent or CLI, you must modify the userlogin scripts.

Modifying user login scripts

Use a text editor to modify login scripts as described below:

1. Use a text editor, such as vi, to make the following additions to thespecified paths in $HOME/.profile or $HOME/.cshrc:

add the text /opt/Navisphere/bin to PATH

add the text /opt/Navisphere/man to MANPATH

add the text /opt/Navisphere/lib to LD_LIBRARY_PATH

2. Run the $HOME/.profile or $HOME/.cshrc file and export eachpath you modified.

3. View the paths using the echo command as follows:

# echo $PATH

# echo $MANPATH

# echo $LD_LIBRARY_PATH


What next?

If you are setting up a new server, go to Running the Navisphere HostAgent , page 31. If you are just upgrading the host agent or CLI on anexisting system, you have finished the upgrade.

Configuring the Navisphere 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 30.

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

If you are configuring a legacy storage system, refer to revision A09 ofthis guide.

A legacy system is an FC series storage system that is not running storagemanagement server software.

Adding privileged users

If you will use Navisphere CLI to configure any storage system, thehost agent configuration file must include an entry that defines theperson who 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 person’s 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. Save the host agent configuration file.

2. If you have finished adding information to the host agentconfiguration file, stop and restart the host agent by entering thefollowing commands:

#/etc/init.d/agent stop#/etc/init.d/agent start

Using the event monitor configuration file

The Navisphere Host Agent can monitor storage-system events andtake such action as sending email or paging you if specified eventsoccur. The event monitor that ships with Navisphere Manager providesan interactive way to define these events and actions. If you do nothave event monitor, you can still define such events and actions byediting the event monitor configuration file.

/etc/Navisphere/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 Navisphere Host Agent

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

Starting and stopping the Navisphere 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 server’s 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 this command:

/etc/init.d/agent start

Stopping the host agent


/etc/init.d/agent 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 theNavisphere Host Agent, page 31.

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: sp0Trusted: NOLogged In: YESSource ID: 1Defined: YESInitiator Type: 0Storage Group Name:Storage Group 134

b. In the listing, examine the information for each HBA installed inthe host to verify the path from the HBA to 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 agent’sstartup, the host agent shutdown, and errors that might occur, such asthe host agent’s 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/adm/messages.


Informational messages about host agent events are recorded in/var/adm/log/agent.log.

Installing the Navisphere Server Utility

This section describes how to install the Navisphere Server Utility.

Installing the Navisphere Server Utility on a Solaris server

Download the most recent version of the server utility from thesoftware downloads page on the Powerlink website. If you areinstalling version 6.28 or earlier, you can install the software from theserver support CD; however, the CD may not contain the most recentversion for your configuration.

1. Log in to the server as superuser (root).



b. Select the Navisphere Server Utility version you want todownload and select the option to save the zip file to your server.


unzip Sun_HOSTUTIL-version.zip




Sun Solaris – pkgadd -d NaviServerUtil-Solaris-32-sparc-en_US-version-build.pkg

Sun Opteron – pkgadd -d NaviServerUtil-Solaris-32-x64-en_US-version-build.pkg






pkgadd -d HOSTUTIL.pkg


a. In the server’s drive, insert the server support CD, whichshipped with the storage system.

b. From a console window, mount the CD:

mount /mnt/cdrom

c. Start the installation program:

cd /cdrom/cdrom0pkgadd -d HOSTUTIL.pkg

4. At the prompt to select the packages to process, enter 1 to selectHOSTUTIL.

5. At the prompt about scripts that execute with superuser permissionduring the installation, enter y.

The screen displays information about the installation.

6. When installation is complete, exit the /cdrom directory by enteringcd /.

7. If you installed the server utility from the CD, remove the CD fromthe server’s CD drive.

Installing the Admsnap Utility

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


Installation prerequisites

Before you can install and use the Admsnap Utility, you must:

Install SnapView on a supported CLARiiON storage system. Fora list of supported storage systems, refer to the release notes forSnapView and admsnap.

Enable data access control on the same CLARiiON storage system.

Installing the Admsnap Utility on a Solaris server

Download the most recent version of the admsnap utility from thesoftware downloads page on the Powerlink website. If you areinstalling version 6.28 or earlier, you can install the software from theserver support CD; however, the CD may not contain the most recentversion for your configuration.

1. Log in as a superuser, such as root.


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


d. Depending on which version you are installing, load theappropriate admsnap package:


Sun Solaris – ADMSNAP-Solaris-32-sparc-en_US-version-build.pkg

Sun Opteron – ADMSNAP-Solaris-32-i386-en_US-version-build.pkg






/usr/sbin/pkgadd -d ADMSNAP.pkg

3. If you are installing admsnap version 6.28 or earlier, you can installit from the server support CD; however, the CD may not contain themost recent version for your configuration. To install the softwarefrom the server support CD, do the following:


The CD is mounted automatically on /cdrom/admsnap, whichis linked to /cdrom/cdrom0.

If the CD does not mount automatically, then mount the CDusing the mount/dev/cdrom command.

The File Manager Admsnap window appears withADMSNAP.pkg displayed.

b. Load admsnap from the CD:

/usr/sbin/pkgadd —/cdrom/cdrom0/solaris/ADMSNAP.pkg

The following messages appear:The following packages are available:1 ADMSNAP Navisphere Admsnap

(sparc) X.X.X.X.XSelect package(s)...to process (or "all" to process allpackages). (default: all) [?, ??, q]:

4. When prompted, enter y to install the admsnap package and yagain to continue the installation.

The installation script runs, listing the files installed, and oncompletion, displays the message: Installation of <ADMSNAP>

was successful.

5. Use the pkginfo command to verify the installation. Enter/usr/sbin/pkginfo-1 ADMSNAP.

Messages similar to the following appear:


PKGINST: ADMSNAPNAME ...CATEGORY: applicationVERSION X.X.X.X.XPSTAMP: Navisphere: 2000:10:28:13:03:01INSTDATE: November 20 2000 13:03STATUS: Completely installedFILES: xxxxxxx

xxxxxxxx xxxxxx

When you see the error-free pkginfo message, admsnap softwareinstallation is complete. The software is installed in the directory/usr/admsnap.

6. Unmount the CD by entering the unmount/dev/cdrom command.

7. Remove the CD from its drive.

Running the Admsnap Utility

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


Disabling Sun StorEdge Traffic Manager to use PowerPath

If you are using PowerPath failover software, you must disable SunStorEdge Traffic Manager (MPxIO) as follows for your Solaris version.

Uncomment the following line in the /kernel/drv/iscsi.conf file:

mpxio-disable="yes"

In addition, if the following line appears in the iscsi.conf file:

mpxio-disable="no"

you must add the comment (#) as shown here:matrix 5.10 (64 bit): more /kernel/drv/iscsi.conf## CDDL HEADER START...# Global mpxio-disable property:## To globally enable MPxIO on all iscsi ports set:# mpxio-disable="no";## To globally disable MPxIO on all iscsi ports set:mpxio-disable="yes";#matrix 5.10 (64 bit):


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

Use optical cables to connect switch ports to the storage-system FibreChannel front-end data ports and to Fibre Channel switch ports and toconnect 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 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 system’s 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 B

SP 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 module’s FE ports connect auto-adjust their speedto 4 Gb/s.

Cabling the Fibre Channel front-end data ports to the switch ports

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-15for HBA connections. With switches set up in such “hard zones,” you canconnect the fibre ports only to ports 0 and 4 and HBAs only to ports 1–3 and5–15. For highest availability with one of these “hard zoned” switches and amultiple-HBA server, connect either fibre port on SP A to switch port 0 andeither FE port on SP 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 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

You must use switch management software to update switch softwareand zone switches that are not hard zoned.

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 vendor’s website.

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

3. Locate the zoning wizard CD that shipped with the switch.



4. Using the instructions provided with the CD, run the zoning wizardand select the zone configuration that is applicable to the way thatyou connected the storage-system Fibre ports and the server HBAports to the switch.


Registering server with the storage system

You must run the Navisphere Server Utility or Navisphere Host Agenton each server connected to the storage system to register the server’sHBAs with the storage system.

Running the Navisphere Server Utility on a Solaris server

You can run the Navisphere Server Utility for Solaris from the server, ifyou installed the utility on the server, or from the server support CD,which shipped with the storage system.











./naviserverutilcli

Registering the server using the Navisphere 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 server’s name and IP address to each storagesystem. Once the server has storage on the storage system, theutility also sends the Solairs 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.

Setting the Navisphere Server Utility to restart on Solaris reboot

Set the utility to restart automatically each time the Solaris serverreboots by using a text editor to modify login scripts as follows:

1. If you are running Common Desktop Environment, remove thecomment from the last line in $HOME/.dtprofile.

The line should readDTSOURCEPROFILE=true.

2. Make the following addition to PATH in $HOME/.profile or$HOME/.cshrc, and export the path:

/opt/Navisphere/bin

Starting the Navisphere Host Agent

Starting the host agent on a server automatically registers the server’sHBAs 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 NavisphereService Taskbar to:

Validate the connectivity of the storage-system hardwarecomponents

Check back-end functionality

Check the status of all field-replaceable units

Analyze storage-system logs

Download the NST from a link on the CLARiiON Tools page of thePowerlink website to a Windows management station that is connected to thestorage-system’s 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 Navisphere Service Taskbar running:

a. Download and install the Navisphere Service Taskbar from theCLARiiON Tools page on the Powerlink website to a Windowsmanagement station that is connected to the storage-system’smanagement ports.

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

b. Start the Navisphere Service Taskbar by doing one of thefollowing:

Click the Navisphere Service Taskbar icon on your desktop,or

Select Start > Programs > EMC > Navisphere > NavisphereService Taskbar version > Navisphere Service Taskbarversion

2. In the taskbar’s navigation pane, select the Hardware Maintenancetab.






3. In the tab’s navigation pane, select Verify Storage System.

4. If the Navisphere Connection screen opens:

a. Enter the IP address for an SP in the storage system.

b. Click Connect.

c. Enter your Navisphere login username, password, and scope(global, local, or LDAP) and click OK.

Once you connect to a storage system, you do not need to reconnect to itagain during the NST session. To connect to a different storage system, youmust disconnect the current storage system by selecting File > Disconnect.

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

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.

IMPORTANTIf you enter incorrect values the storage system could becomeunmanageable and unreachable by the server, and the server’sfailover software could stop operating correctly.

Solaris 9 or 10For a Solaris 9 or 10 server, set:

Unit Serial Number to Array

Failover Mode to 4 if your failover version supports ALUA.

Failover Mode to 1 if your failover version does not supportALUA.

For information on which versions of failover support ALUA forCLARiiON storage systems, refer to the PowerPath release notes on thePowerlink website.

Solaris 8, 7, or 2.6For a Solaris 8, 7, or 2.6 server, set:



Failover Mode to 4 if your failover version supports ALUA.

Failover Mode to 1 if your failover version does not supportALUA.

For information on which versions of failover support ALUA forCLARiiON storage systems, refer to the PowerPath release notes on thePowerlink website.

For a Solaris 8, 7, or 2.6 server with any of the following packages:

Solstice DiskSuite

Sun Cluster 3.x

VERITAS DBE/AC

SFRAC

VRTSvcs with I/O fencing

set:

Unit Serial Number to LUN

For a Solaris 8, 7, or 2.6 server without any of the above packagesor with VRTSvcs without I/O fencing, set:

Unit Serial Number to Array

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.



Verifying your high-availability Fibre Channel configuration

Use the server high-availability feature in the Navisphere ServerUtility to verify the following for each server in a high-availabilityconfiguration with the storage system:

Your Fibre Channel configuration is highly available (that is, eachFibre Channel HBA has at least one active path to each storageprocessor).

Path management software is installed and running on the server.











./naviserverutilcli

Using the server utility to verify your high-availability configuration

1. In the Navisphere Server Utility select option 3 from the serverutility’s Welcome screen to generate a report of the server’senvironment.


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, Sun StorEdge Traffic Manager.

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


Installing CLARalert software

CLARalert® software monitors your storage system’s operation forerror events and automatically notifies your service provider of anyerror events. CLARalert is available from the CLARiiON Tools page onthe Powerlink website. If the CLARiiON Tools page does not containa CLARalert link, it is not supported for your system or your serviceprovider can install the CLARalert software.


CLARalert uses a centralized monitoring environment. In a centralizedmonitoring environment you designate a monitor station to monitorthe events of storage systems you specify. The centralized monitoringenvironment is a monitoring environment option for Navisphere EventMonitor, which is a feature of the Navisphere Manager application.

During the CLARalert installation, you designate the monitor stationand portal system where you want to configure your centralizedmonitoring environment. The storage system that you designate as aportal system during CLARalert installation is automatically addedto the list of monitored storage systems. You can later add storagesystems to your centralized monitoring environment using NavisphereManager. For more information, see the Navisphere Manager help,which is in the Navisphere Manager UI or the Powerlink website. Theversion on Powerlink is the most up to date.





For a new CLARalert installation, the wizard automatically installs the emailnotification service, which sends event notification to your service providerwith email (SMTP). CLARalert integrates with WebEx, allowing you to initiatereal-time customer support sessions over the web. See the WebEx EMC SupportCenter at https://emcsupport.webex.com for more information on WebEx.

CLARalert requirements

CLARalert installation and operation requires that TCP ports 80, 443, 25 (SMTPserver) are open. Refer to the EMC CLARalert Release Notes for the most currentCLARalert environment and system requirements.

The CLARalert version must be at or later than the version of FLARE®Operating Environment (OE) running on each storage system beingmonitored. CLARalert installation requires:

❑ A monitor station, which is a host running a supported Windowsoperating system. For supported versions, refer to the EMCCLARalert Release Notes. The monitor station cannot be a server(host connected to storage-system data ports), and it must be on thesame network as your storage-system management ports.

CLARalert is installed on and runs on the monitor station. Themonitor station must have a static or DHCP reserved IP address.The wizard automatically detects and supplies the IP address forthe monitor station, which is required for CLARalert installation.You can verify the IP address in the wizard and, if required, enteror select a different one.

❑ A portal system, which is a storage system running the requiredFLARE Operating Environment (OE ) version. For requiredversions, refer to the EMC CLARalert Release Notes.

You must provide the IP address for either SP of the portal systemduring CLARalert installation. You must also supply globaladministrator login credentials for the portal system duringinstallation.


https://emcsupport.webex.com

If your CLARalert installation will use email notification, for example, for anew installation, you will need connectivity to an outgoing SMTP server. Youmust provide the IP address for the SMTP server during CLARalert installation.You must also provide your service provider email address (to) and your localemail address (from) for email notification.

If you do not have an existing monitor station — You can create amonitor station by installing CLARalert on a Windows host.

If you have an existing monitor station running CLARalert — Youcan upgrade CLARalert on the monitor station. When you perform anupgrade, the wizard asks if you want to preserve your existing emailconfiguration or if you want to reconfigure it.

If you have an existing monitor station running event monitor — Youcan install CLARalert on the monitor station.

Downloading and installing CLARalert software

From the monitor station:

1. On the Powerlink website, select the Search Powerlink tab.

2. Replace the “Search Powerlink” text with “claralert” and in Filterby content type, select Support: Downloads and click Search.

3. In the results page, select Download CLARalert and save thesoftware to your monitor station.

4. In the folder where you saved CLARalert, double-click theNaviClarAlert executable (.exe) file or if necessary, right-click thefile and select Run as to run the installation wizard using a differentuser’s credentials.

5. Follow the steps in the wizard, using the information from thecompleted CLARalert Worksheet in the planning guide for yourstorage system.

You can generate the latest version of the storage-system planningguide from the CLARiiON Tools page on the Powerlink website.




Configuring a new storage system

A new storage system is one that was not already connected to a serverwhen you started the installation procedure.

To configure a storage system, use either the Navisphere taskbarwizards or the Storage tree options of Navisphere Manager.

Before you start

You will need the completed LUN worksheets from the storage-systemconfiguration planning guide or the planning worksheets document.You can generate an up-to-date version of this planning guide usingthe user-customized documentation link from the CLARiiON Toolspage on the Powerlink website or view it on the documentation andresources CD, which shipped with the storage system.


Starting Navisphere Manager

To manage a CX4 storage system running FLARE OE version 04.28.000.5.5xx orlater, you must use Navisphere Manager UI version 6.28.10 or later.

1. Log in to a host (which can be a server) that is connected through anetwork to the storage system’s management ports and that has anInternet browser: Microsoft Internet Explorer, Netscape, or Mozilla.

2. Start the browser.

3. In the browser window, enter the IP address of one of the followingthat is in the same domain as the storage systems that you wantto manage:

A storage-system SP with the most recent version of the FLAREOperating Environment (OE) installed




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

A Navisphere off-array management station with the mostrecent Navisphere management server and UIs installed

A dialog box opens that requests your username and password.

If you do not have a supported version of the JRE installed, you will bedirected to the Sun website where you can select a supported version todownload. For information on the supported JRE versions for your versionof Navisphere Manager, refer to “Environment and System Requirements”in the Navisphere Manager release notes on the Powerlink website.

4. Enter the username and password for the account you want to use,and leave the scope unchanged (set to global).

5. If you are prompted to add the storage system to a domain, addit now.

The first time that you log in to a storage system, you are promptedto add the storage system to a Navisphere domain. If the storagesystem is the first one, create a domain for it. If you alreadyhave storage systems in a domain, you can either add the newstorage system to the existing domain or create a new domain forit. For details on adding the storage system to a domain, use theNavisphere Manager help.

The Navisphere Manager main window opens with a navigation paneon the left that contains the Navisphere taskbar and an EnterpriseStorage window on the right. The Navisphere taskbar consists ofthe following tabs: Storage Management, Monitoring, Replication,Reporting, Service. When you select a tab, it displays one or more iconsfor starting the wizards. The Enterprise Storage window contains tabsfor the following trees:

Storage tree – Displays a storage-system icon for every storagesystem in this domain.

Hosts tree – Displays a host icon for each server connected to anystorage system in this domain.

Monitors tree – Displays a monitor icon for:



Every monitored storage system in the domain.

Storage systems that do not belong to the domain, but arephysically connected to a storage system that does belong. Anexample is a SAN Copy destination storage system.

The Navisphere Manager user interface (UI) version 6.28.10 introducesthe following new storage concepts – storage pool, traditional LUN,thin pool, and thin LUN – to support the Virtual Provisioning feature.For more information on these concepts, refer to the NavisphereManager Help.

Thin pools and thin LUNs are part of the Virtual Provisioning feature, whichis available only on storage systems with FLARE OE version 04.28.5.00.5xx orlater and the Virtual Provisioning enabler installed.

Configuring the storage-system cache

1. In the Navisphere Manager storage tree, right-click the storagesystem and select Properties.

2. Click the Memory tab.

3. Set the write cache memory size.

Generally, for a storage system with the maximum cache memory,we recommend that the write cache should be 10764 MB per SP,which is the maximum allowed size.

4. Set the read cache memory size.

5. Click Apply.

6. Click the Cache tab, and select SP A Read Cache, SP B Read Cache,Write Cache, and Enable Watermarks.

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


8. Click Apply.

Enabling storage groups or access control

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.

If you want to connect multiple servers to the storage system, you musteither enable storage groups using Navisphere Manager 6.29 or later orenable 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.

To enable access control using Navisphere Manager 6.48 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.

Allocating storage on a new storage system with the Provision or Allocate wizard

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.

To provision storage:

1. In the Navisphere taskbar, click the Storage Management tab andthen open the Provision or Allocate wizard.

2. Select the server that will have access to the new LUNs.

3. Select the storage system in which the new LUNs will reside.

4. Create hot spares on a RAID group.

Thin pools do not support the Hot Spare RAID type.


A hot spare is a single global spare disk that serves as a temporaryreplacement for any failed disk in the storage system. The storagesystem automatically reconstructs data from the failed disk ontothe hot spare, so the data is always available. Do not use an FSSDdisk as a hot spare, and do not use a SATA disk as a spare for aFibre-Channel-based LUN, nor a Fibre Channel disk as a spare foran SATA-based LUN.

a. From the Provision wizard, select the Traditional option in theSelect LUN Type page or, if you are running an older version ofthe Provision wizard (Allocate wizard), click New RAID Groupin the Select RAID Group page.

b. Create a new RAID group with the Hot Spare RAID type.

c. Let the software select the disk for the RAID group (Automatic),or select Manual to choose the disk yourself.

The software creates the Hot Spare RAID type with one LUN.

Click Help in the dialog box for more details.

5. Create traditional LUNs on a RAID group:

a. Create a new RAID group with the appropriate RAID type(individual disk, RAID 0, RAID 1, RAID 1/0, RAID 3, RAID 5,or RAID 6) for each type of LUN you want to create.

b. Let the software select the disks for the RAID group (Automatic)or select Manual to choose the disks yourself.

The software creates the specified RAID group.

c. Select the number of LUNs and set the properties for the LUNsthat will reside in the new RAID group.

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


6. Create thin LUNs on a thin pool storage pool.


To create thin pools and thin LUNs, the storage system must be runningFLARE version 04.28.000.5.5xx or later and the Virtual Provisioning enablermust be installed on the storage system. You must use version 6.28.10.xxor later of the Navisphere Manager UI to create thin pools and thin LUNs.For more information about Virtual (Thin) Provisioning, refer to theNavisphere Manager online help and the Provision wizard help.

To create thin LUNs:

a. Select the Thin option in the Select LUN Type page of thewizard.

b. Create a new thin pool storage pool with the appropriate RAIDtype (RAID 5 or RAID 6) for each type of thin LUN you need tocreate.

c. Let the software select the disks for the thin pool (Automatic) orselect Manual to choose the disks yourself.

The software creates the specified thin pool.

d. Select the number of thin LUNs and set the properties for theLUNs that will reside in the new thin pool.

e. Either add the thin LUNs to a user-defined folder or do notplace them in a folder.


7. Verify that the server was assigned to the storage group containingthe LUNs you created.

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 storagegroup 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 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 on a new storage system with the Navisphere storage tree options

1. Locate your completed LUN worksheets so you can refer to themin the steps that follow.

2. Create one or more hot spares on a RAID group.

A hot spare is a single global spare disk that serves as a temporaryreplacement for any failed disk in the storage system. The storagesystem automatically reconstructs data from the failed disk ontothe hot spare, so the data is always available. Do not use an SSDdisk as a hot spare, and do not use a SATA disk as a spare for aFibre-Channel based LUN, nor a Fibre Channel disk as a spare foran SATA-based LUN.

From the Navisphere Manager Storage tree, depending on the UIthat you are using, right-click the storage-system icon and do one ofthe following:

Click Storage Pools Operations > Storage Pools and, if visiblein the Create Storage Pool dialog box, select Raid Groups.Create a hot spare RAID group with one LUN.

Click Bind LUN; create a Hot Spare RAID group and bind oneLUN on the RAID group.

For details on creating Hot Spares, use the Navisphere Managerhelp.

3. Create traditional LUNs on RAID groups:


From the Navisphere Manager Storage tree, depending on the UIthat you are using, right-click the storage-system icon and do one ofthe 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.

4. Create thin LUNs on thin pools:

From the Navisphere Manager Storage tree, right-click thestorage-system icon and click Storage Pool Operations > StoragePools and in theCreate Storage Pool dialog box, select Thin Pools.

For details on creating thin LUNs and thin pools, use theNavisphere Manager help.

5. Create one or more storage groups:

From the Navisphere Manager Storage tree, right-click the icon forthe storage system, and click Create Storage Groups. For details oncreating storage groups, use the Navisphere Manager help.

6. Add LUNs (traditional LUNs and thin LUNs) to the storage group.

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.

From the Navisphere Manager Storage tree, right-click the iconfor the storage group to which you want to add LUNs, and clickSelect LUNs. For details on adding LUNs to storage groups, usethe Navisphere Manager help.

7. Assign a server to a storage group:


To send data to or receive data from the LUNs, you must assign serversto the storage groups.

From the Navisphere Manager Storage tree, right-click the icon forthe storage group to which you want to connect a server, and thenclick Connect Hosts. For details on connecting servers to storagegroups, use the Navisphere Manager help.

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.

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

From 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 the storage group, an icon for thatserver appears under the storage group icon.

Configuring event notification on a new storage system using Navisphere Manager

Event monitor supports monitoring of storage-system events in aheterogeneous environment. Once configured, event monitor runscontinuously as a service or daemon, observing the state of all specifiedstorage systems and notifying you when selected events have occurred.The event monitor user interface (UI) is part of Navisphere Managerand runs on a web browser.

Event monitor supports centralized or distributed monitoring ofstorage systems. With centralized monitoring, a monitoring host agentmonitors storage systems from a central location. With distributed


monitoring, SP agents monitor only the storage system in which theyreside, or host agents monitor all attached storage systems. All AX4-5series, AX series, CX4 series, CX3 series, and CX series storage systemshave resident SP agents.

FLARE OE includes the SP agent.

For both configurations, the monitoring agent notifies the client ofevents that occur on the monitored storage systems.

To use centralized monitoring, you must use either the Navispheretaskbar Monitor wizard or the Monitor tree options of NavisphereManager to:

Have a host that is not managing any storage system and thathas the host agent installed on it. This host agent becomes thecentralized monitoring agent.

Define a portal.

Add monitored agents to the centralized monitoring configuration.

Create and apply templates to the monitoring agent.

To configure event monitor for the storage system using theMonitor wizardIn the Navisphere taskbar, click the Monitoring tab, and use theConfigure Monitoring wizard under this tab to configure centralizedor distributed monitoring. For details on how to configure monitoringand how to configure the storage system to send event notification,use the Navisphere Manager help.

To configure event monitor for the storage system with theNavisphere Monitor treeIn the Navisphere Manager Enterprise Storage window, click theMonitors tab and configure centralized or distributed monitoring. Fordetails on configuring monitoring and configuring the storage systemto send event notification, use the Navisphere Manager help.

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 to complete the initialization processvaries with the size of the LUN and other parameters. While a LUN is


initializing, it is in a transitioning state, and when the initialization iscomplete, 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 Solaris server

To allow the Solaris server access to the LUNs that you created:

1. From the server, scan for the LUNs:devfsadm -C.

2. Use the format command to verify that Solaris recognizes the LUNs.

If Solaris does not recognize the LUNs, reboot the server:reboot – -r

Verifying that PowerPath for Solaris 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 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 Solaris can send data to a LUN, you must partition the LUN andthen create and mount a file system on it. For information on how toperform these tasks, refer to your operating system documentation.

For information on how to perform these tasks, refer to your operatingsystem documentation.


Sending Solaris disk information to the storage system

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

Stopping the host agent


/etc/init.d/agent 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

Before you store data on LUNs, use the procedure in this section toverify that:

The server can send data to and receive data from the storagesystem.

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

PowerPath shows the paths from the server to the LUNs that youexpect for your configuration.

Verifying your failover configuration

1. 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 theLUN, indicating that the failover path was successful andthat PowerPath is working properly.


http://www.iometer.org/

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

h. If you caused any LUNs to fail over, restore them to theiroriginal SP:

powermt restore


Copyright© 2009 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.


Date post:	08-Apr-2015
Category:	Documents
Upload:	alsipd
View:	281 times
Download:	1 times

Attaching Server to Storage System- Master 1073670

Documents