Attachingf Server To Storage System - Master

Here is Your Customized Document
Your Configuration is:

Action to Perform - Attach server
Storage-System Model - CX4-480
Storage-System Status - Existing
Connection Type - Fibre Channel Switch or Boot from SAN
Server Status - New
Server Operating System - Windows Server 2008
Path Management Software - EMC PowerPath
Management Tool - EMC Unisphere
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: 1433065
Content Creation Date 2010/10/12
Attaching a Microsoft Windows

Server 2008 Server with EMC
PowerPath to a CX4-480 Storage
System in a Fibre Channel or a Boot
from SAN Switch Configuration
This document explains how to attach a Microsoft Windows Server 2008

server with EMC PowerPath to a CX4-480 storage system in a Fibre
Channel switch or a boot from storage area network (SAN) 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 .............................................................................

Booting from a SAN ......................................................................
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 ................................
3
6
9
12
14
16
17
31
37
Manually registering the Windows server with the storage system

(boot-from-SAN configurations only).............................................
Verifying storage-system health......................................................
Setting storage-system failover values for the server initiators with
Unisphere ....................................................................................
Verifying your high-availability Fibre Channel configuration ...........
Configuring an existing storage system...........................................
Preparing LUNs to receive data ......................................................
Sending Windows server and Windows virtual machine disk
information to the storage system ..................................................
Verifying your failover configuration with PowerPath .....................
40
43
45
47
49
52
53
55
Attaching a Microsoft Windows Server 2008 Server with EMC PowerPath to a CX4-480 Storage
System in a Fibre Channel or a Boot from SAN Switch Configuration
Before you start

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:
z
As a client in which you launch the Unisphere software. 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 Unisphere release notes in the Technical Documentation and
Advisories section of the Powerlink website.
You must have a supported Windows 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.
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).
For boot-from-SAN configurations:
Be sure your Windows hosts have been qualified for booting

from CLARiiON storage systems over Fibre Channel
connections as described under "Boot Device Support" in
the EMC Support Matrix on the Powerlink website. The
EMC Support Matrix also contains specific boot-from-SAN
restrictions.
Refer to the appropriate Windows HBA guide, available on the

Powerlink website, for information on configuring your HBA
and installing the Windows operating system on an external
storage system:
EMC Host Connectivity with Emulex Fibre Channel Host

Bus Adapters (HBAs) and Converged Network Adapters
(CNAs) in the Windows Environment
EMC Host Connectivity with QLogic Fibre Channel and

iSCSI Host Bus Adapters (HBAs) and Converged Network
Adapters (CNAs) in the Windows Environment
EMC Host Connectivity with Brocade Fibre Channel

and Host Bus Adapters (HBAs) and Converged Network
Adapters (CNAs) in the Windows Environment
At the start of the Windows boot procedure, make sure no

failover software is running. For high availability while booting
from a SAN with a single hardware fault, HBA BIOS must have
a primary path and secondary path(s) properly configured (with
access to both SPs).
Refer to the section on Booting from a SAN, page 6 for additional

information on booting Windows from an external storage.
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/.
Booting from a SAN

Booting from a SAN lets you use your CLARiiON storage system as
the boot disk for your server instead of a directly attached (or internal)
hard disk. By using a properly configured Fibre Channel HBA adapter
connected and zoned to the same switch or fabric as the storage system,
you can configure a server to use a LUN presented from the storage
system as its boot disk.
Benefits of a boot-from-SAN configuration

A boot-from-SAN configuration can simplify management in the
data center. Separating the boot image from each server allows
administrators to leverage their investments in EMC storage systems
to achieve high availability, better data integrity, and more efficient
storage management. Other benefits can include:
Improved disaster tolerance
Reduced total cost through diskless servers
High-availability storage
Rapid server re-purposing
Consolidation of image management
Risks of booting from the storage system

When using the storage system as a boot disk, EMC recommends that
you shut down the host server during any maintenance procedures that
could make the boot disk unavailable to the host.
CAUTION
Microsoft Windows operating systems use virtual memory paging
files that reside on the boot disk. If the paging file is unavailable
to the memory management system when it needs it, the operating
system will crash with a blue screen.
Any of these events could crash an operating system that is booting
from the storage system:
Lost connection to the storage system (pulled or damaged cable

connection)
Storage-system service/upgrade procedures, such as online

microcode upgrades and/or configuration changes
Storage-system failures, including failed lasers on Fibre Channel

ports
Storage-system power failure
Storage area network failures, such as Fibre Channel switches,

switch components, or switch power failures
Storage area network service/upgrade procedures, such as

firmware upgrades or hardware replacements
EMC recommends moving the Windows virtual memory paging file to a local
disk when booting the operating system from the storage system. Consult your
Windows manual for instructions on how to move the paging file.
How to determine I/O latency and load on the boot LUN

The boot-for-SAN configurations listed in the EMC Support
Matrix represent the maximum configurations allowed as typical
configurations. Here are some general measurements you can use to
determine if your environment will support the maximum allowed
boot-from-SAN configurations:
Using the Windows Performance Monitor, capture and analyze

the Physical Disk and Paging File counters for your boot LUN. If
response time (sec/operation), or disk queue depth increase over
time, review any additional loading that may be affecting the boot
LUN performance (HBA/SAN saturation, failovers, ISL usage,
and so forth).
Use available storage system Performance Management tools to

determine that the storage system configuration, LUN configuration
and access are configured optimally for each host.
Possible ways to reduce the load on the boot LUN include:
Move application data away from the boot LUN.
Reduce the number of LUNs bound to the same physical disks.
Select an improved performance RAID type.
Contact your EMC support representative for additional information.
Crash dumps after system failures

If you configure your system to write crash dump files after system
failures and you configure your host to boot from the storage system,
you can successfully save the crash dump file only to the original boot
device path on which the system started. This is a Windows limitation,
and EMC PowerPath does not affect this behavior. At the time a
system crash is to be written to disk, Windows has already saved the
original boot path, and PowerPath cannot redirect the crash dump file
(MEMORY.DMP) to an alternative available device. When you want to
capture a crash dump file for a configuration, you should ensure that
the original primary boot path is always available.
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.
IMPORTANT
If you have a Windows virtual machine, for a complete configuration
report, run the server utility from the Windows Hyper-V server.
If you have this information, go to Verifying a servers configuration

with E-Lab Interoperability Navigator, page 10. 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 Windows server

1. Run the Unisphere Server Utility by selecting Start > Programs
> EMC > Unisphere > Unisphere Server Utility or Start > All
Programs > EMC > Unisphere > Unisphere Server Utility.
2. Select your language, if the software prompts you for it.
A text-based version of the utility is installed automatically when you install
the utility. To start the text-based version, at a command prompt enter cd
C:\Program Files\EMC\Unisphere Server Utility or cd C:\Program Files
(x86)\EMC\Unisphere Server Utility, then enter ServerUtilCLI.exe.
Generating a high-availability report for a server

1. In the Unisphere Server Utility dialog box, select Verify Server
High-Availability to generate a report of the servers environment.
This option detects if PowerPath or some other failover software,
such as DMP, is running. 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.
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.
10
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.
11
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.
12
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.
13
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 service packs 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:
z
14
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 service packs, 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.
15
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.
16
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.
Boot-from-SAN configuration If you are booting from a SAN
configuration, do not install the Unisphere Host Agent or Unisphere
Server Utility to register your server. You will perform a manual
registration later.
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, Admhost, or Admsnap, you
must install them on a virtual machine. For instructions on installing
these software programs on a virtual machine other than Windows
Server 2008, 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 18.
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 19.
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
20.
17
Unisphere Server Utility see Installing the Unisphere Server Utility

, page 25.
Navisphere CLI see Installing Navisphere CLI , page 26
Admhost Utility see Installing the Admhost Utility , page 27.
Admsnap Utility see Installing the Admsnap Utility , page 28.
Requirements for Unisphere server software

To run Unisphere server software, your server must meet the following
requirements:
Run a supported version of the Windows 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
Unisphere 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:
z
any server whose browser you will use to access Unisphere,
a supported Windows server running Unisphere Server software

(replaces the Navisphere Management Server software),
any AIX, HP-UX, Linux, VMware ESX Server, NetWare, Solaris,

or Windows server running Navisphere CLI.
If you want to use Navisphere CLI on the server to manage 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.
18
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:
Table 1
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.
Host registration differences between the host agent and the server
utility
Function
Unisphere Host Agent
Unisphere Server Utility
Pushes LUN mapping

and OS information to the
storage system.
Yes LUN mapping information is

displayed in the Unisphere UI next
to the LUN icon or with the CLI
using the lunmapinfo command.
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 Unisphere UI indicating that the host agent was
not used to register this server.
19
Function
Unisphere Host Agent
Unisphere Server Utility
Runs automatically to
send information to the
storage system.
Yes No user interaction is

required.

Yes You can control whether server information is automatically
sent to the storage system by enabling or disabling the registration
service feature. This feature is automatically enabled during the
installation of the server utility, but you can stop the service at any
time through the services option in the Microsoft user interface. Note
that only the servers name, ID, and IP address are sent to the storage
system; LUN mapping information is not sent.
Requires network
connectivity to the storage
system.
Yes Network connectivity allows

LUN mapping information to be
available to the storage system.

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.
Installing the Unisphere Host Agent

This section describes how to install the Unisphere Host Agent.
Installing the Unisphere Host Agent on a Windows 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. Log in as the administrator or a user who has administrative
privileges.
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 software to your server.
c. Double-click the executable file listed below to start the
installation wizard.
UnisphereHostAgent-Win-32-x86-en_US-version-build.exe
20
where version and build are the version number and the build
number of the software.
4. Follow the instructions on the installation screens to install the
Unisphere Host Agent.
The Unisphere Host Agent software is installed on the Windows
server. If you selected the default destination folder, the software
is installed in the C:\Program Files\EMC\HostAgent (32bit) or
C:\Program Files (x86)\EMC\HostAgent (64bit).
Once the Unisphere Host Agent installation is complete, the
Initialize Privileged User List dialog box is displayed.
5. In the Initialize Privileged User List dialog box, select
Create/Overwrite File and browse to the agent.config file. You will
then need to add users to the Privileged User List (login names for
this server). Only usernames listed in the Privileged User List can
send CLI commands to the storage system.
There must be at least one entry in the Privileged User List or an error
message will appear.
To add a user to the list
Click Add to open the Add Privileged User dialog box.
In the Add Privileged User dialog box, under User Name, enter
the persons account username, for example, Administrator.
Under System Name, enter the name of the host running

Unisphere (for example, Host4) and click OK.
6. Click OK to save the new privileged user list and the new
configuration file.
The program saves the host agent configuration file with the new
privileged user entries and starts the host agent.
7. Click Finish.
A command line window opens indicating that the host agent
service is starting.
21
8. If the system prompts you to reboot the server, click Yes.

9. Click Done to exit the installation wizard.
10. Verify that Unisphere Host Agent is installed using the
Add/Remove Programs dialog box.
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
This section describes how to start and stop the host agent service. This
section also describes how to configure the storage system connected to
the server.
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 on a Windows server

1. Log in as the administrator or the equivalent.
2. Open the Services pane.
From the desktop, right-click My Computer and select

Manage > Services and Applications > Services.
or
Select Start > Administrative Tools > Computer Management

> Services and Applications > Services.
The Services pane opens.

3. In the Services pane, right-click Unisphere Agent and select Start.
4. If you want the host agent to start automatically at system startup:
a. Right-click Unisphere Agent and select Properties.
22
The Unisphere Agent Properties dialog box opens.

b. Select the General tab.
c. In Startup Type, select Automatic.
5. Close the Services pane.
The host agent will now start automatically at system startup.
It may take a few minutes for the host agent to start when:
Applications are using the storage system, or
The SP event log is large and the host agent configuration file is
not set up.
Stopping the host agent on a Windows server

1. At the Windows server or Windows virtual machine, log in as the
administrator or the equivalent.

or


3. In the Services pane, right-click Unisphere Agent and select Stop.
4. If asked to confirm your request to stop the agent service, click Yes,
and close the Services pane.
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 22.
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:
23
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
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
24
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.
Installing the Unisphere Server Utility

This section describes how to install the Unisphere Server Utility.
Installing the Unisphere Server Utility on a Windows server
of the Unisphere Server Utility software from the software downloads
page on the Powerlink website.
1. Log in as the administrator or someone who has administrative
privileges.
Downloads and Licensing > Downloads T-Z > Unisphere
Server Software.
b. Select the Unisphere Server Utility, and then select the option to
save the software to your server.
UnisphereServerUtil-Win-32-x86-language-version-build.exe
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
3. Follow the instructions on the installation screens and accept all
the defaults.
25
If you do not have the host agent installed, do not disable the registration
service feature (it is enabled by default). The registration service feature
automatically registers the servers HBAs with the storage system after the
installation and updates server information to the storage system whenever
the server configuration changes (for example, when you mount new
volumes or create new partitions).
4. When the installation is complete, click Done to exit the wizard.
Installing Navisphere CLI

This section describes how to install Navisphere CLI. You can install
Navisphere CLI on either the server or virtual machine.
Installing Navisphere CLI on a Windows server or a Windows virtual machine
of the Navisphere CLI software from the software downloads page
on the Powerlink website.
1. Log in as the administrator or someone who has administrative
privileges.
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.
Table 2
TCP/IP ports
Software
TCP/IP ports
Classic CLI
6390, 6391, 6392
Secure CLI
443, 2163

Downloads and Licensing > Downloads J-O > Navisphere
Server Software.
b. Select the Navisphere CLI, and then select the option to save the
software to your server.
26
NaviCLI-Win-32-x86-language-version-build.exe
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
Navisphere CLI.
5. When the installation is complete, click Done to exit the wizard.
You have installed the Navisphere CLI software. If you selected the
default destination folder, the software is installed in C:\Program
Files\EMC\Navisphere CLI (32bit) or C:\Program Files
(x86)\EMC\Navisphere CLI (64bit).
6. Verify that Navisphere CLI is installed using the Add/Remove
Programs dialog box.
Installing the Admhost Utility

If you want to access LUNs that participate in SAN Copy sessions,
install the Admhost Utility.
The Admhost Utility is supported on Microsoft Windows platforms only. For
the supported Windows versions, see the Admhost Release Notes.
Installing the Admhost Utility on a Windows server

of the Admhost Utility software from the software downloads page
27
IMPORTANT
Currently, you cannot install admhost on your virtual machine if your
virtual machine is connected to Fibre Channel or FCoE storage; you
must install it on the Hyper-V server. For any updates, refer to the
Admhost Release Notes.
1. Log in as the administrator or as someone who has administrator

privileges.
Downloads and Licensing > Downloads S> SANCopy.
b. Select the Admhost Utility, and then select the option to save the
software to your server.
c. In the folder where you saved the software, double-click the
executable file to start the installation wizard.
Admhost Utility.
4. When the installation is complete, click Finish to exit the wizard.
You have installed the admhost software. If you selected the
default destination folder, admhost is installed in the C:\Program
Files\EMC\Unisphere Admhost (32bit) or C:\Program Files
(x86)\EMC\Unisphere Admhost (64bit).
Running the Admhost Utility
Refer to the EMC SAN Copy Command Line Interface Reference for
information on running admhost commands.
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.
28
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 Windows server
of the Admsnap Utility software from the software downloads page
1. Log in as the administrator or as someone who has administrative
privileges.
Downloads and Licensing > Downloads S > SnapView.
b. Select the Admsnap Utility version you want to download and
select the option to save the software to your server.
c. Double-click the following executable file to start the installation
wizard:
Windows Server 2008
admsnap-Win2K8-32 en_US-version-build.exe
where version and build are the version number and the build
Admsnap Utility.
4. When the installation is complete, click Finish to exit the wizard.
29
If you selected the default destination folder, admsnap is installed

in C:\Program Files\EMC\Unisphere Admsnap (32bit) or
C:\Program Files (x86)\EMC\Unisphere Admsnap (64bit).
Running the Admsnap Utility
Refer to the EMC SnapView Command Line Interface Reference for
information on running admsnap commands.
30
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 A4 for SP A
B0 through B4 for SP B
SP A and SP B must have the same type of I/O module in the same slots.
10/100/1000
B0
Figure 1
B1
B2
B3
B4
A0
10/100/1000
A1
A2
A3
A4
CL4180
I/O module slots (only standard I/O modules shown)
31
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.
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 one optional 4 or 8 Gb Fibre Channel
I/O module per SP each with four Fibre FE ports (0, 1, 2, 3) in any
available slot.
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.
32
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 Unisphere,
refer to the Unisphere online help.
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).
33
CL4021
Connecting an optical cable
Figure 2
10/100/1000
10/100/1000
CL4185
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.
34
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).
10/100/1000
10/100/1000
CL4187
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.
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.
35
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.
36
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.
Booting from a SAN configuration If you are booting from a
SAN, do not register your server using the Unisphere Host Agent or
Unisphere Server Utility. You will perform a manual registration in
the next section.
You must run the Unisphere Server Utility 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 Windows server

Run the Unisphere Server Utility for Windows from the Hyper-V server.
Registering the server using the Unisphere Server Utility on a Windows server
1. If the host agent is running, stop the host agent service.
2. In the Unisphere Server Utility dialog box, select Register this
server to all connected storage systems.
37
The utility automatically scans for all connected storage systems

and lists them under Connected Storage Systems.
3. Locate the WWN of the HBA you just installed. The HBA should
appear once for every SP port to which it is connected.
If the Unisphere Server Utility does not list your storage processors, verify
that your server is properly connected and zoned to the storage system
ports.
4. Click Next to register the server with the storage system.

The utility sends the servers name and WWN of the each HBA to
each storage system. Once the server has storage on the storage
system, the utility also sends the device name and volume or file
system information for each LUN (virtual disk) in the storage
system that the server sees.
5. Click Finish to exit the utility.
6. 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.

or


38

not set up.
Verifying HBA registration with Unisphere

1. From Unisphere, select All Systems > System List.
2. From the Systems page, right-click the entry for the storage
system for which you want to verify HBA registration, and click
Connectivity Status.
3. In the Host Initiators tab, select the initiator name, and then click
Edit.
4. Verify that the server to SP port connection is displayed as Yes
under the Registered columns.
Once all HBAs belonging to a server are registered, you can assign
the server to storage groups.
5. Click Cancel and then OK to close the Connectivity Status dialog
box.
39
Manually registering the Windows server with the storage system

(boot-from-SAN configurations only)
In boot-from-SAN configurations where the operating system is going
to be installed on the CLARiiON LUN, no host agent or server utility is
available to perform the registration. Manual registration of the HBA
WWNs is required in order to present a LUN to the server for booting.
Creating an initiator record

1. Right-click the storage system and then select Connectivity Status
from the drop-down menu.
2. In the Connectivity Status window, click Create.
3. In the Create Initiator Record window, select the following:
Initiator Information
Enter the HBA WWNN (node name) followed by the

WWPN (port name). For our example, the WWNN is
20:00:00:00:00:44:c4:b1 and the WWPN is 20:00:00:00:12:34:56:78.
Select the SP port to which the host will connect.
For Initiator Type select CLARiiON Open
For Failover Mode select:

z
1 for active passive mode
4 for asymmetric active active (ALUA) mode

Asymmetric active active (ALUA) failover is available for CX4
series storage systems .
Booting from SAN configurations EMC strongly recommends
using failover mode 4 (ALUA active/active) when the system
supports it, as ALUA will allow I/O access to the boot LUN
from either SP, regardless of which SP currently owns the boot
LUN. Using other failover modes may cause delays when the
system boots. For information on other failover modes supported
with your Windows failover software and CLARiiON FLARE
software, see EMC Knowledgebase solution emc99467.
40
Host Information
Select New Host.
Enter the servers hostname and IP address.

IMPORTANT
Be sure to note the hostname. If you decide later to install the
host agent on your Windows server, you will need to provide
the same hostname. If the hostname is different, and you install
the host agent, your registration on the CLARiiON storage
system could be lost and your server could lose access to the
boot LUN and crash.
4. Click OK.
5. Repeat steps 2 4 for each HBA that will be connected to the
CLARiiON storage system.
Registering SP and HBA connections with Unisphere

When you have established a connection between the SP and the HBA,
you must register the connection. Use Unispheres Connectivity Status
dialog box to register each HBAconnection with the storage system:
1. In the Connectivity Status dialog box, select the connection for the
WWN of the HBA and click Register.
2. In the Register Initiator Record window, select the following:
CLARiiON Open for the Initiator Type
ArrayCommPath (LUN Z) under Advanced Options
Array for the Unit Serial Number, also under Advanced Options
For Failover Mode select:

z
1 for active passive mode
4 for asymmetric active active (ALUA) mode
41
Asymmetric active active (ALUA) failover is available for CX4

series storage systems.
Booting from SAN configurations EMC strongly recommends
using failover mode 4 (ALUA active/active) when the system
supports it, as ALUA will allow I/O access to the boot LUN
from either SP, regardless of which SP currently owns the boot
LUN. Using other failover modes may cause delays when the
system boots. For information on other failover modes supported
with your Windows failover software and CLARiiON FLARE
software, see EMC Knowledgebase solution emc99467.
3. In the Host Information dialog box, select New Host, enter the
servers IP address, and click OK.
4. Repeat steps 2 and 3 for each HBA that will be connected to the
CLARiiON storage system.
42
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.

43
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.
44
Setting storage-system failover values for the server initiators with

Unisphere
Use the Unisphere Failover Setup wizard to set the storage-system
failover values for all HBA initiators belonging to the server:
2. From the Systems page, select the storage system for whose failover
values you want to set.
3. Select the Hosts tab.
4. Under Host Management, select the Failover Wizard.
5. In the Start Wizard dialog box, read the introduction, and then
click Next.
6. In the Select Host dialog box, select the server you just connected to
the storage system, and click Next.
7. In the Select Storage Systems dialog box, select the storage system,
and click Next.
8. 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 Windows server or Windows virtual machine with PowerPath,

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

ALUA.
45
For information on which versions of PowerPath support ALUA, refer

to the PowerPath release notes on the Powerlink website or to EMC
Knowledgebase solution emc99467.
9. In the Configuration Summary screen, review the configuration

and all settings.
10. 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.
11. In the confirmation dialog box, click Yes.
The wizard displays a summary of the values you set for the storage
system.
12. If the operation failed, rerun the wizard.
13. When the operation is successful, click Finish to close the wizard.
14. Reboot the server for the initiator records to take affect.
46
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.
IMPORTANT
If you have a Windows virtual machine, for a complete configuration
report, run the server utility from the Windows Hyper-V server.

Using the server utility to verify your high-availability configuration

1. From the Unisphere Server Utilitys Welcome screen, select Verify
Server High-Availability.
2. Select Valid Server Configuration only.
3. In the Select Host Type screen, select Local host and click Next.
4. In the Select Report Directory screen, select the location where
you want the system to save the high-availability status report.
Click Next.
5. Read the summary and if it is accurate, click Next to generate the
report. If not, click Back to return to the screen where you need
to correct the data.
47
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 Windows Server 2008 native failover.
6. Review and resolve any issues reported on the Issues tab of the
generated report.
48
Configuring an existing storage system

To configure an existing storage system with Unisphere, use the
Unisphere Service Manager wizards.
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 with Unisphere

If only one server was connected to the storage system when you started
this installation, you must enable storage groups using Unisphere.
2. From the Systems page, right-click the icon for the storage system,
and click Properties.
3. Click the General tab, and select Storage Groups.
4. Click OK.
Allocating storage to an existing storage system with Provision wizard in Unisphere

IMPORTANT
Use the Provision wizard in the Unisphere to create storage-system

storage and provide server access to this storage.
1. Locate your completed storage-system disk information worksheet
so that you can refer to it in the steps that follow.
3. From the Systems page, select a storage system.
4. Select the Storage tab.
49
5. If you need additional LUNs for the server, use the Storage
Provisioning wizard from the LUNs category to create them.
6. If you want to assign existing LUNs to the server, use the Storage
Assignment wizard from the Storage Groups category 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.
7. Verify that the server was assigned to the storage group containing
the LUNs you created.
If you know the name of the storage group in which the LUNs
reside From Unisphere, select Storage > Storage Groups.
If you know the name of the server to which the storage group
is assigned From Unisphere, select Storage > LUNs 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 Storage
Assignment wizard to assign the LUNs to a server.
Verifying that each LUN is fully initialized using Unisphere

Although the storage group with a new LUN is assigned to the
server, the server cannot 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 Unisphere, navigate to the LUN you want to verify (Storage >
LUNs).
2. Right-click the LUN and click Properties.
50
3. Verify that the state of the LUN is Normal.

If the state is Transitioning, wait for the state to change to Normal
before continuing.
Making LUNs visible to a Windows server or Windows virtual machine with NICs
IMPORTANT
To allow the Windows server access to the LUNs that you created, use
Windows Computer Management to perform a rescan.
1. Open the Computer Management window (Start > Computer
Management).
2. Under the Storage tree, select Disk Management.
3. From the tool bar menu, select Action > Rescan Disks.
Verifying that PowerPath for Windows servers or Windows virtual machines sees all
paths to the LUNs
IMPORTANT
1. On the server, configure PowerPath:

powermt config
2. On the Windows taskbar, either double-click the PowerPath
Administrator icon or right-click the icon and select PowerPath
Administrator.
3. In the results pane, verify that the path metric for each LUN is n/n
where n is the total number of paths to the LUN.
51
Preparing LUNs to receive data

If you do not want to use a LUN as a raw disk or raw volume, then
before Windows can send data to a LUN, you must:
Use Unisphere to verify that each new LUN is initialized and to
write a signature to it, as described in the Unisphere online help.
Either create partitions on a basic disk or create the appropriate
volumes on a dynamic disk. 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 Windows virtual machine:
52
Write a signature to the VMware virtual disk.
Either create partitions on a basic disk or create volumes on a

dynamic disk.
Sending Windows server and Windows virtual machine 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. Unisphere displays this information in the LUN Properties
Host dialog box 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 on a Windows server

1. At the Windows server or Windows virtual machine, log in as the
administrator or the equivalent.

or


3. In the Services pane, right-click Unisphere Agent and select Stop.
4. If asked to confirm your request to stop the agent service, click Yes,
and close the Services pane.


or
53


not set up.
Verifying that the storage system received the LUN information using Unisphere
2. From the Systems page, select a storage system that is attached to
the host that you want to verify.
3. Select Hosts > Hosts List.
4. Select a host and then, on the Details page, click the LUNs tab.
5. Verify that the LUNs tab displays a physical drive and logical drive
name for each LUN on the host.
54
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 Windows server or Windows
virtual machine
IMPORTANT
Perform this procedure on your Hyper-V 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. Launch PowerPath Administrator by double-clicking the
PowerPath Monitor icon on the Windows taskbar. This icon may
be under your hidden icons.
3. On the left pane (summary pane), expand the EMC PowerPath
Admin or EMC PowerPath Administrator option.
4. Under the Path Management option, select Disks.
For each disk, the Path Status and the Path Metric columns give
the status of the paths to the disk. When all n paths to a disk are
working, the Path Status for the disk is optimal and the Path Metric
for the disk is n/n, indicating that n of n paths are working. If only
m paths are working, the path metric is m/n.
5. Verify that all n paths to the disks in the storage system are working;
that is, their status is optimal and their path metric is n/n.
If all the paths are not working, refer to the troubleshooting
flowcharts on the CLARiiON Tools page on the Powerlink website.
55
To access the CLARiiON Tools page, use the Navigator drop-down menu
at the top right of the Powerlink home page.
6. For each HBA connected to the storage system:

a. Start writing data to a LUN.
b. Disconnect the cable from oneHBA connected to the storage
system.
c. After several seconds, look at the Details pane and verify that
one or more of the disks in the storage system have red slashes
through them, their status is degraded, and their path metric is
m/n, where n is the number of paths to the disk and m is the
number of working paths, which is less than n. For example, if
the server has 4 paths to a disk in the storage system and 1 path
fails when you disconnect the cable, then n=4 and m=3, so the
path metric is 3/4.
d. Reconnect the cable that you disconnected from the HBA.
e. Right-click the PowerPath Monitor icon on the taskbar, and
select All Tasks and Restore All Devices.
f.
After several seconds, look at the details pane and verify that
none of the disks in the storage system have red slashes through
them, their status is optimal, and their path metric is n/n.
If any disks do not have optimal status and their path metric
is not n/n, refer to the troubleshooting flowcharts 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.
7. Restart any applications that you stopped and re-enable any user
logins to the server that you disabled.
56
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.
57

Attachingf 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

Attachingf Server To Storage System - Master

Uploaded by

Copyright:

Available Formats

Here is Your Customized Document

Your Configuration is:

Content Creation Date 2010/10/12

Content Creation Date 2010/10/12

Content Creation Date 2010/10/12

Attaching a Microsoft Windows

This document explains how to attach a Microsoft Windows Server 2008

The main topics in this document are:

Before you start .............................................................................

Manually registering the Windows server with the storage system

Before you start

As a client in which you launch the Unisphere software. This

To run the Unisphere Service Manager, which runs only on

As an EMC Secure Remote Support (ESRS) IP Client, which

You must have a Unisphere Server with a supported Internet

Be sure your Windows hosts have been qualified for booting

Refer to the appropriate Windows HBA guide, available on the

EMC Host Connectivity with Emulex Fibre Channel Host

EMC Host Connectivity with QLogic Fibre Channel and

EMC Host Connectivity with Brocade Fibre Channel

At the start of the Windows boot procedure, make sure no

Refer to the section on Booting from a SAN, page 6 for additional

Booting from a SAN

Benefits of a boot-from-SAN configuration

Improved disaster tolerance

Reduced total cost through diskless servers

Rapid server re-purposing

Consolidation of image management

Risks of booting from the storage system

Lost connection to the storage system (pulled or damaged cable

Storage-system service/upgrade procedures, such as online

Storage-system failures, including failed lasers on Fibre Channel

Storage-system power failure

Storage area network failures, such as Fibre Channel switches,

Storage area network service/upgrade procedures, such as

How to determine I/O latency and load on the boot LUN

Using the Windows Performance Monitor, capture and analyze

Use available storage system Performance Management tools to

Possible ways to reduce the load on the boot LUN include:

Move application data away from the boot LUN.

Reduce the number of LUNs bound to the same physical disks.

Select an improved performance RAID type.

Contact your EMC support representative for additional information.

Crash dumps after system failures

Determining if your server has a supported configuration

If you have this information, go to Verifying a servers configuration

Starting the Unisphere Server Utility on a Windows server

Generating a high-availability report for a server

2. In the summary report, select the Checklist tab to view the

Verifying a servers configuration with E-Lab Interoperability Navigator

Installing HBAs in the server

Before you start

Store HBAs in antistatic bags.

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

Never plug or unplug HBAs with the power on. Severe

1. If the server is powered up:

3. For each HBA that you are installing:

Installing or updating the HBA driver

Before you start

For an Emulex driver

E-Lab Interoperability Navigator on the Powerlink website

The HBA vendors website

Installing the HBA driver