AX4 Installing An ISCSI Storage System - Master 1692635

Here is Your Customized Document
Your Configuration is:

Action to Perform - Install
Storage-System Model - AX4-5i (AX4-5I)
Connection Type - iSCSI Network
Server Operating System - Windows Server 2003
Storage-System Status - Existing
Server Status - New
Management Tool - Navisphere Express
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: 1692635
Content Creation Date 2012/4/4
AX4-5 Series
Installing an AX4-5i Storage System

in an iSCSI Network Configuration
with a Microsoft Windows Server
with EMC PowerPath
If you want to install an AX4-5i storage system in a network configuration

with a Microsoft Windows server, this document is for you. You can use the
procedures in this document to set up configurations with a new or existing
storage system that you want to connect to a new or existing server.
This document describes how to install Unisphere server software, which was
previously referred to as the CLARiiON server software or Navisphere server
software.
The main topics are:

w
w
w
w
w
w
w
w
w
w
w
w
w
w
w
w
w
w
Terminology..................................................................................
Before you start .............................................................................
Resetting the storage-system security settings .................................
Upgrading storage-system software................................................
Registering the storage-system configuration with your service
provider.......................................................................................
Installing NICs or iSCSI HBAs in the server ....................................
Installing or updating the NIC or iSCSI HBA driver.........................
Installing NIC or HBA iSCSI initiator software (Windows Server
2003 virtual machines only) ...........................................................
Assigning an IP address to a NIC or iSCSI HBA ..............................
Installing PowerPath on a server ....................................................
Installing Unisphere server software...............................................
Modifying TCP/IP registry settings ...............................................
Connecting iSCSI ports in a network configuration ..........................
Configuring iSCSI initiators for a configuration without iSNS...........
Configuring the iSNS client on the system.......................................
Configuring iSCSI initiators for a configuration with iSNS ...............
Registering the server with the system ............................................
Configuring an existing storage system...........................................
3
5
7
9
19
21
23
25
27
29
33
42
44
46
52
54
58
60
1
w
w
w
w
w
w
Verifying your high-availability iSCSI configuration .......................

Configuring optional CHAP security for Windows servers or
Windows virtual machines with NICs ............................................
Configuring optional CHAP security for iSCSI HBA initiators
....................................................................................................
Preparing virtual disks to receive data ............................................
Sending Windows server and Windows virtual machine disk
information to the system..............................................................
Verifying your failover configuration with PowerPath .....................
64
66
78
86
87
91
Installing an AX4-5i Storage System in an iSCSI Network Configuration with a Microsoft Windows
Server with EMC PowerPath
Terminology
This document uses the following terms:
host
A computer that is or will be connected to a CLARiiON storage

system. This computer is called either a management station or a
server, depending on how it is or will be connected to the storage
system.
management station
A host from which you manage CLARiiON storage systems. It

must be on the same network as the storage-system management
ports. A management host may also be a server.
server
A host that is already or will be connected over a network to the

iSCSI ports on a CLARiiON storage system. A management host
may also be a server.
new server
A server that is not already connected to or set up for a CLARiiON

storage system.
existing NIC or iSCSI

HBA
The network interface card (NIC) or iSCSI host bus adapter (HBA)
that is already installed in a server.
new NIC or iSCSI HBA
The NIC or iSCSI HBA that was not already installed in the server.
base dual-SP system
An AX4-5 series system with two storage processors (SPs) an

AX4-5i storage system.
expansion dual-SP
system
An AX4-5 series system with two storage processors (SPs)

an AX4-5 or AX4-5i storage system with the expansion pack
enabler installed.
existing storage system
A storage system that is already connected to a server and

configured for storage.
field-replaceable unit
(FRU)
A storage-system component that you can add to your storage

system or replace in your storage system at your site. Examples
of FRUs are disks andpower/cooling modules.
DPE-AX
A disk processor enclosure that contains 1 or 2 storage processors

(SPs) and 4 to 12 disks.
DAE-AX
A disk-array enclosure that provides additional storage for a

DPE-AX with 2 storage processors and an expansion pack
installed. Each DAE-AX supports a maximum of 12 disks.
Installing an AX4-5i Storage System in an iSCSI Network Configuration with a

Microsoft Windows Server with EMC PowerPath
storage processor (SP)
A printed-circuit board with processors, memory modules, and

control logic that manages the I/O between the server and the
disk modules.
disk pool
A set of disks with the same capacity and RAID type on which you
create one or more virtual disks.
virtual disk
A grouping of physical disk partitions into one span of disk storage

space. Each virtual disk you create is distributed equally across
the disks in the disk pool. A virtual disk looks like an individual
disk to the server's operating system. A virtual disk is created with
Navisphere Express.
initiator
A NIC or iSCSI HBA port that issues requests to send data to or

receive data from a target in the storage system.
target
A storage-system SP port that accepts and responds to requests

from an initiator. Such a port is called an iSCSI data port.
CHAP
Challenge Handshake Authentication Protocol. An optional

security mechanism to control access to an iSCSI storage system
over the iSCSI data ports.
iSNS
Microsoft Internet Storage Naming Service (iSNS) provides

automated discovery, management and configuration of iSCSI
devices.
An AX4-5i storage system has two SPs, so it is called a dual-SP system.
Before you start

Review the support matrix on the Service & Support page of the
storage-system support website to confirm that the following are
supported:
l
The server hardware that will access the storage system.
The operating system version running on the server hardware.
Read the release notes for your storage system, which are available
on the Service & Support page of the storage-system support
website.
The url for the storage-system support website is in the Documentation and
Support document that shipped with your storage system.
For any installation, you will need:

A Navisphere management station with a supported Internet
browser for running Navisphere Express and on the same network
as the storage-system management ports. This host can also be
a server. For supported host and browsers, refer to the E-Lab
Interoperability Navigator on the Powerlink website.
A supported Windows host on the same subnet as the
storage-system management ports. You can use this host:
l
As a Navisphere management station
To run the Navisphere Service Taskbar, which runs only on

a Windows host.
As a CLARalert monitor station, which must be a Windows

host, but cannot be a server (that is, it cannot send I/O to the
storage-system data ports).
A Windows 2000, Windows Server 2003 or Windows Server 2008

host that is or will be a server with iSCSI 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.
A Navisphere management station with a supported Internet
browser that is on the same network as the storage-system
management ports. This host can also be the server. For supported
Internet browsers, see the AX4-5 release notes on the Service &
Support page of the storage-system support website.
A Cat5, Cat5e, or Cat6 Ethernet network cable (100 meters
maximum) for each iSCSI port that will connect the storage system
though network routers or switches to the NICs or iSCSI HBAs
in the server. We recommend Cat6 cables for best performance.
These cables may already be connected for a configuration with an
existing storage system or existing server.
For cable specifications, refer to Technical Specifications on the Learn
page of the storage-system support website.
For a network configuration, Ethernet network cables as needed
for the hosts. These cables may already be connected for a
configuration with an existing storage system or existing server.
We recommend discrete networks dedicated to iSCSI traffic. In a server
with multiple NICs or iSCSI HBAs that are connected through network
routers or switches to the storage system, each NIC or iSCSI HBA initiator
port must be on a separate subnet.
For cable specifications, refer to Technical Specifications on the Learn

page of the storage-system support website.
A method for writing data to a virtual disk 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/.
Resetting the storage-system security settings

If you forget the storage-system security settings (use account
information) or want to change these settings, you must put the storage
system in a special state that will let you change the settings with
Navisphere Express.
1. On an SP, press the white security button to the far right of the
power button to put the SP in a special reset state (Figure 1).
The amber SP fault light turns on.
The special reset state gives you 15 minutes to reset the storage
system's security settings. This 15-minute window stays active until
one of the following occurs:
FRU Label
You log in to the storage system with a valid username and

password.
You create a new user account.
You modify an existing user account.
The 15 minutes is up.
FRULabel
CL3872
Figure 1
Security button on each SP (dual-SP system shown)
2. After 2 minutes, start Navisphere Express on the storage system:

a. Open an Internet browser, such as Internet Explorer, Netscape,
or Mozilla, on the management host.
b. Enter the IP address of an SP in the storage system.
This address is the one you assigned when you initialized the storage
system.

c. Either log in to Navisphere Express as you normally would or

without a username and password.
3. In the navigation pane, under System, select Settings.
4. In the System Settings pane, select User Management.
5. Modify or create user accounts; then exit Navisphere Express.
For information on modifying or creating user accounts, use the
Navisphere Express help system.
6. Test the new credentials by restarting Navisphere Express and
logging in to it with the new username/password credentials.
Upgrading storage-system software

For optimal performance, the storage system should be running the
latest release of the FLARE Operating Environment (OE). The version
number of this release is displayed on the storage-system support
website. If the storage system is not running this version, install it now.
To display the FLARE OE version with Navisphere Express, in the navigation
pane, select System and then Software.
Install the storage-system software with the software upgrade feature

of Navisphere Express or the Software Assistant, which is part of the
Navisphere Service Taskbar (NST). With Navisphere Express you can
install only one software package (FLARE OE version, enabler, or
language pack) at a time. With the Software Assistant, you can install
multiple software packages (FLARE OE version, enabler, language
pack) at the same time; however, it requires a Windows host or server
on the same network as the storage-system management ports.
When to install a Navisphere language pack
A Navisphere language pack is updated only if the Navisphere user
interface (UI) changes in the FLARE OE. Typically the language pack is
available after the English FLARE OE version is available. If you install
FLARE OE with an updated Navisphere UI, then until you install the
new version of the language pack, text changes in the Navisphere UI
are displayed in English and unchanged text continues to be displayed
in the language, including the Navisphere Express help text. To
ensure that all text changes and help changes in the Navisphere UI are
displayed in the language, you should update the language pack as
soon as the new version is available. To determine if the Navisphere
UI changed in a new FLARE OE version, refer to the AX4-5 Integrated
Management Software release notes (which includes Navisphere
Express information) on the storage-system support website.
Preparing to install software on an existing storage system

If you will use Navisphere Express to install the software on a dual-SP
system, you must verify the high-availability (HA) configuration of the
servers connected to the storage system.

The procedure for using the Software Assistant includes verifying the
high-availability (HA) configuration of the servers connected to the storage
system.
Verifying that connected servers are configured for high availability

To verify that connected servers are configured for high availability,
you need to determine which have active registered connections to the
storage system, and then use the server high-availability feature of
the Navisphere Server Utility to determine if each of these servers is
configured for high availability. The server high-availability feature is
supported for all servers in an iSCSI configuration, except for AIX,
HP-UX, and Solaris servers.
Determining which servers are connected to the storage system
1. Start Navisphere Express for the storage system.
2. In the navigation pane, under Manage, click Servers.
3. Record all the servers listed in the Manage Servers screen.
These are the servers with active registered connections to the
storage system, which means that they can send data to and receive
data from the storage system.
Using the HA option on the server utility
1. Locate the following:
w
The server support CD that ships with the storage system and
the AX4-5 series Navisphere Manager upgrade kit.
The server products installation guide for the operating system

running on the server. This document is on the Install page of
the storage-system support website under Related Documents
Attach a host or on the documentation CD, which ships with
the storage system and the AX4-5 series Navisphere Manager
upgrade kit.
2. Using the instructions in the appropriate server support products

installation guide:
a. Either install the server utility on the server, and then start it
from the server or start the server utility on the CD.
10
If the AX version of the Navisphere Server Utility is installed on the

server, you must remove it before installing the AX4-5 version.
b. Generate a high-availability report.

c. The software upgrade feature of Navisphere Express and the
Software Assistant use this report.
Upgrading storage-system software with Navisphere Express

You can install only one software package (FLARE OE version, enabler,
or language pack) at a time with the Navisphere Express upgrade
feature.
Installing updated FLARE OE or an enabler using Navisphere Express
CAUTION
During the software installation procedure:
w The storage system must not have any faulted or transitioning
components.
You can view the current state of storage-system components on
the Navipshere Express View Components page.
w You must not power down or reboot the storage system, power
down an SP, or remove any components. Doing so may put the
storage system in a state from which it cannot be restarted.
For a dual-SP system:
w The software installation procedure reboots SP A, and then after
the reboot of SP A completes, it reboots SP B. This causes any
connected servers that are not configured for high availability
(not connected to each SP) to lose access to the storage system
until the operation is completed.
1. If you are updating FLARE OE software, download the latest

FLARE OE version from the CLARiiON AX4-5 part of the
Downloads and Licensing section of the Powerlink website
11
(http://Powerlink.EMC.com) onto the host or server from which

you will install the software.
This host or server must be on the same network as the storage-system
management ports.
The FLARE OE software is in a .pbu file.

2. If you are installing an enabler:
a. Locate the enabler CD that shipped in the AX4-5 software or
upgrade kit, and insert it into the CD drive on the host or server
from which you will install the software.
This host or server must be on the same network as the storage-system
management ports.
b. Copy the enabler (.ena file) from the CD onto the host or server.
c. Remove the CD from the CD drive.
3. On the server or host with the FLARE version or enabler that you
want to install, start Navisphere Express for the storage system.
4. Wait until no storage-system components are in a transitioning state
before continuing.
You can view the current state of storage-system components on the
Navisphere Express View Components page.
5. In the navigation pane under System, click Software.
6. On the System Software page, click Upgrade Software.
Prior to installing the software on the storage system, Navisphere
Express performs a series of pre-installation checks to ensure that
the storage system is in a ready state. If problems exist, the software
will ask you to fix them so it can continue the installation.
7. Either enter the path for the software .pbu or .ena file you just
downloaded or browse for it, and click Upgrade.
8. Monitor the status of the installation in the Software Upgrade
Status window.
12
After the installation is complete, the storage system reboots

automatically. On a dual-SP system, one SP reboots, and when it
has finished, the other SP reboots. You cannot restart Navisphere
Express for the storage system, until the reboot is complete, which
could take a couple minutes. When the reboot is complete, the
power button on each SP remains solid/steady green. When the
storage system reboots, you may see an error message, such as
Action Cancelled, in the browser. If you see an error message,
close the browser, wait for the storage system to complete the
reboot, and then reopen the browser and restart Navisphere Express
for the storage system. If you do not see an error message, wait
until the reboot is complete before continuing.
Upgrading storage-system software with the Software Assistant

If you have enablers and/or Navisphere Express language packs to
install, copy them to the Windows host and/or server from which you
will install the software.
CAUTION
During the software installation procedure:
w The system must not have any faulted or transitioning
components.
Using Navisphere Express, you can view the current state of
system components on the View Components page.
w You must not power down or reboot the system, power down an
SP, or remove any components. Doing so you may put the system
in a state from which you cannot restart it.
For a dual-SP system:
w After the software installation is complete, the storage system
reboots automatically. One SP reboots, and when it has finished,
the other SP reboots. This causes any connected servers that are
not configured for high availability to lose access to the storage
system until the operation is completed.

13
Copying enablers and/or Navisphere language packs into the system software repository
Read this section if you have enablers or Navisphere language packs to
install on the system.
To copy enablers or language packs into the software repository:
1. For each enabler that you want to install on the system:
a. Locate the enabler CD that shipped with your order, and
insert the CD into the CD drive on the Windows server or host
running the USM.
This Windows server or host must be on the same network as the
system management ports.
b. Copy the enabler (.ena) file from each CD into the

C:\emc\repository\Downloads folder on the Windows server
or host on which you installed the USM.
The USM installation process creates a C:\emc\repository\Downloads
folder as the default repository for the USM's system software to use. If
this folder does not exist, you must create it.

2. For each Navisphere language pack that you want to install,
download the language pack from the CLARiiON AX4-5 part of
the Software Downloads and Licensing section of the Powerlink
website into the c:\emc\repository\Downloads folder.
Installing system software
To install system software (a new operating environment version,
software enablers, or language packs) using the USM's software
wizards, follow the instructions on this section:
w
Validate the environment of any servers connected to the system.
Install the USM.
Copy any enablers or language packs that you are installing to the
software repository.
Run the software wizards:

l
14
Prepare for Installation wizard
Install Software wizard
Validating the server environment and installing the USM

You must install the USM on a Windows host that is connected to the
Internet and on the same network as the management ports on the
system.
1. On the Powerlink website, navigate to the CLARiiON Tools page
and select your CLARiiON system.
To access the CLARiiON Tools page, use the Navigator drop-down menu
at the top right of the Powerlink home page.
2. In the navigation pane, click CLARiiON Software Update tools

and then CLARiiON Software Update (Standard).
3. On the CLARiiON Software Update (Standard) page.
a. Complete step 1 to determine if you can use the update process.
b. If the system is a dual-SP system with one or more servers
connected to its data ports, complete step 2 to validate the server
environment; otherwise, skip this step.
c. Complete step 3 to install the USM on the Windows server or
host you will use to install the system software.
d. Accept the USM license agreement.
The installation wizard verifies that the server is running the
supported Java Runtime Environment (JRE) version.
w
If the server is running an earlier version of the JRE, select

Yes when asked if you want to continue with the installation.
The installation wizard prompts you to download and install
the most recent version of the JRE from the Sun website.
If the server is running a later version of the JRE, select Yes

to continue or No to cancel the installation.

15
Important: If you select Yes, the USM may not work properly with
a later JRE version. If you select No, and manually remove the
later version of the JRE, other applications that require this version
may not work properly.
Copying enablers and/or Navisphere language packs into the system software repository
Read this section if you have enablers or Navisphere language packs to
install on the system.
To copy enablers or language packs into the software repository:
1. For each enabler that you want to install on the system:
a. Locate the enabler CD that shipped with your order, and
insert the CD into the CD drive on the Windows server or host
running the USM.
This Windows server or host must be on the same network as the
system management ports.
b. Copy the enabler (.ena) file from each CD into the

C:\emc\repository\Downloads folder on the Windows server
or host on which you installed the USM.
The USM installation process creates a C:\emc\repository\Downloads
folder as the default repository for the USM's system software to use. If
this folder does not exist, you must create it.

2. For each Navisphere language pack that you want to install,
download the language pack from the CLARiiON AX4-5 part of
the Software Downloads and Licensing section of the Powerlink
website into the c:\emc\repository\Downloads folder.
Running the System Software wizards
1. Start the USM by doing either of the following:
w
16
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.

You must first download the software packages using the USM Downloads
wizard. Then, use the Prepare for Installation and Install Software wizards
to complete the installation of the software packages.
3. From the System screen, select Software > System Software >
Prepare for Installation.
4. Follow the recommended steps in the Prepare for Installation
wizard, being sure to do the following:
5. When the Prepare for Installation wizard is complete, start the
Install Software wizard.
6. Follow the instructions to install the desired software packages.
After the installation is complete, the storage system reboots
automatically. On a dual-SP system, one SP reboots, and when it
has finished, the other SP reboots. You cannot start Navisphere
Express on the storage system until the reboot is complete, which
could take 40 minutes or more, depending on how many software
packages you installed. The reboot is complete when the power
button on the SP on a single-SP system or on each SP on a dual-SP
system remains solid/steady green. Wait until the reboot is
complete before continuing.
A health check is performed after the software is upgraded. The
number and content of the post-upgrade health checks may differ
from those performed before the upgrade. Be sure to review the
results of the health check, and if any problems are detected, resolve
them before using your system.
7. When the installation is complete, select Notify your service
provider with updated storage system configuration information,
and click Finish.

17
If the newly-installed software requires a commit, the last step in the

wizard provides the option to make the commit.
8. Close the USM.
Verifying the system software has been successfully installed

Use Navisphere Express to verify that the software was successfully
installed.
Verifying the software installation with Navisphere Express
1. Start Navisphere Express for the storage system, if it is not already
running.
2. From the navigation pane, under System, select Software.
3. From the System Software page, click Last Installation Status.
4. Verify that the list of software contains an entry for each software
package that you installed and that the status of the installation
was successful.
The entry for the expansion pack enabler is named ExpansionTier.
18
Registering the storage-system configuration with your service

provider
Read this section if you are installing a new storage system and you have
a Windows client connection to the storage-system management ports.
We strongly recommend that you use the Storage System Registration
wizard to send site and storage-system configuration information to
your provider. Your provider uses this information to supply proactive
and timely support. The registration wizard is part of the Unisphere
Service Manager (USM), which runs on a Windows client that is
connected to the storage-system management ports.
The Storage System Registration wizard asks you several questions
about the site where the storage system is installed and your support
provider contact. It sends this information and basic storage-system
configuration details to your service provider either directly over the
Internet or using email. If you do not have an Internet connection, the
wizard lets you save the registration information to a file, which you
can send to your service provider.
If you decide not to register your storage system at this time or you
do not have Internet access and email, you can still run the wizard to
collect the data and send it to your service provider at a later time.
If you do not register now, you may spend significantly more time
registering it later.
Downloading and installing the Unisphere Service Manager

1. From the EMC Online Support website, select your product, then
search for the link to download the Unisphere Service Manager.
2. Select the Unisphere Service Manager link and save the software
to your host or management station.
3. In the folder where you saved the USM, double-click the executable
(.exe) file, and if necessary, click Run to start the installation wizard.
4. Follow the instructions that appear.
After you accept the license agreement, the wizard verifies that
the server is running the supported Java Runtime Environment
(JRE) version.
19
If the server is running an earlier version of the JRE, select Yes

when asked if you want to continue with the installation.
The installation wizard prompts you to download and install
the later version of the JRE from the Sun website.
If the server is running a later version of the JRE, the installation

wizard asks if you want to continue with the installation.
Select Yes to continue or No to quit the installation.
Important: If you select Yes, the USM may not work properly with
a later JRE version. If you select No, and manually remove the later
version of the JRE, other applications that require this version may
not work properly.
5. When the installation is complete, click Done.
Running the storage system registration wizard

1. Start the Unisphere Service Manager (USM) by doing either one of
the following:
w
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. In the taskbar's navigation pane, select the Hardware Registration

tab.
3. In the tab's navigation pane, select the Register Storage System to
start the Storage System Registration wizard.
4. Follow the steps in the wizard to provide contact and storage-system
information to your service provider.
20
Installing NICs or iSCSI HBAs in the server

For the server to communicate with the system iSCSI data ports, it must
have one or more supported NICs or iSCSI HBAs installed.
Before you start

To complete this procedure, you will need one or more supported NICs
or iSCSI HBAs with the latest supported BIOS and drivers.
For information on supported NICs or iSCSI HBAs, BIOS, and drivers,
refer to the support matrix on the Service & Support page of the
system support website.
We recommend that you never mix NICs or iSCSI HBAs from different vendors
in the same server.
Installing NICs or iSCSI HBAs
CAUTION
NICs or iSCSI HBAs are very susceptible to damage caused by static
discharge and need to be handled accordingly. Before handling NICs
or iSCSI HBAs, observe the following precautions:
w Store NICs or iSCSI HBAs in antistatic bags.
w Use a ground (ESD) strap whenever you handle NICs or iSCSI
HBAs.
w Never plug or unplug NICs or iSCSI HBAs with the power on.
Severe component damage can result.
1. If the server is powered up:

a. Shut down the server's operating system.
b. Power down the server.
c. Unplug the server's power cord from the power outlet.
21
2. Put on an ESD wristband, and clip its lead to bare metal on the
server's chassis.
3. For each NIC or iSCSI 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 NIC or iSCSI HBA following the instructions
provided by the NIC or iSCSI HBA vendor.
4. Plug the server's power cord into the power outlet, and power up
the server.
22
Installing or updating the NIC or iSCSI HBA driver

The server must run a supported operating system and NIC or iSCSI
HBA driver. EMC recommends that you install the latest supported
version of the driver. For information on the supported NIC or iSCSI
HBA drivers, refer to the support matrix on the Service & Support
page of the system support website.
Before you start

To complete this procedure, you will need:
The latest supported version of the NIC or iSCSI HBA driver.
The NIC or iSCSI HBA driver is also on the installation CD that ships
with the NIC or iSCSI HBA. However, this version may not be the latest
supported version.
For a Qlogic driver

You can download the latest supported version and instructions
for installing the QLogic HBA driver from the vendor's website:
http://support.qlogic.com/support/oem_emc.asp.
Any updates, such as hot fixes or service packs to the server's
operating system that are required for the NIC or iSCSI HBA driver
version you will install.
For information on any required updates, refer to one of the
following:
l
Support matrix on the Service & Support page on the system

support website
The NIC or iSCSI HBA vendor's website
Installing the NIC or iSCSI HBA driver

1. Install any updates, such as hot fixes or service packs, to the server's
operating system that are required for the NIC or iSCSI HBA driver
version you are installing.
2. If the hot fix or patch requires it, reboot the server.
23
3. Install the driver following the instructions on the NIC or iSCSI

HBA vendor's website.
4. Reboot the server when the installation program prompts you to
do so.
5. If the installation program did not prompt you to reboot, then
reboot the server when the driver installation is complete.
24
Installing NIC or HBA iSCSI initiator software (Windows Server 2003

virtual machines only)
IMPORTANT
If you configured your system iSCSI connections to your Windows
virtual machine with NICs, install the initiator software on the virtual
machine. If you configured your system iSCSI connections to your
Hyper-V server, install the initiator software on the Hyper-V server.
If you have a non-Windows virtual machine or a Windows virtual
machine with iSCSI HBAs, install the initiator software on the Hyper-V
server.
Install NIC or HBA iSCSI initiator software on each server with NICs
or iSCSI HBAs that you will connect to the system.
For Windows NICs, install the Microsoft iSCSI software initiator as
described in Downloading and installing the Microsoft iSCSI software
initiator (Windows 2000 or Windows Server 2003 hosts only), page 25.
You must install the Microsoft iSCSI software initiator because the Unisphere
Server Utility uses it to configure iSCSI connections.
For QLogic HBAs, you must install the Initiator Service option of the Microsoft
iSCSI Software Initiator because the QLogic driver requires it.
Downloading and installing the Microsoft iSCSI software initiator (Windows 2000 or
Windows Server 2003 hosts only)
1. From http://www.microsoft.com, navigate to the Download Center.
2. Search for and download to your host the revision of the iSCSI
initiator listed in E-Lab Navigator on the EMC Powerlink website
or the EMC Online Support website.
3. Double-click the executable to open the installation wizard and
click Next at the welcome screen.
4. Select the following at the Installation Options screen:
25
For NICs select Initiator Service, Software Initiator, and

Microsoft MPIO Multipathing Support for iSCSI (required for
Windows Server 2003 servers only), then click Next.
For iSCSI HBAs select Initiator Service and MPIO Multipathing
Support for iSCSI, then click Next.
Do not select Software Initiator for iSCSI HBAs.
5. Read and accept the license agreement and click Next to install
the software.
6. At the completion screen, click Finish if this is a new installation.
If this is an upgrade, you must reboot the system to apply the
updates. If you have a NIC and will be modifying the TCP/IP
registry settings in the next section, you do not need to reboot now.
If you have an iSCSI HBA, download and install the QLogic
SANsurfer software.
IMPORTANT
If an iSCSI initiator icon appears on the desktop, do not use this icon
to configure iSCSI HBAs; use the QLogic SANsurfer utility.
Downloading and installing the QLogic SANsurfer software for iSCSI HBAs
1. Download the QLogic SANsurfer software on the server:
a. Open a web browser and connect to the QLogic website:
http://support.qlogic.com/support/oem_emc.asp
b. Go to the Downloads page.
c. Select the HBA.
For information on supported software, refer to Supported
Configurations in Technical descriptions on the system support
website.
d. Select and download the software and related documentation.
2. Install the software as described in the QLogic documentation.
26
Assigning an IP address to a NIC or iSCSI HBA

Assign an IP address to each NIC or iSCSI HBA in the server that will
be connected to the system.
IMPORTANT
virtual machine with NICs, assign an IP address to the NIC in the
Windows virtual machine. If you configured your system connections
to your Hyper-V or ESX server, assign an IP address to the NIC in the
Hyper-V or ESX server. If you have a non-Windows virtual machine or
a Windows virtual machine with iSCSI HBAs, perform this procedure
on the Hyper-V or ESX server. For instructions on assigning an IP
address on a Windows 2003 virtual machine, generate a new document
and select the appropriate Windows operating system.
For the NIC or iSCSI HBA IP addresses, refer to the iSCSI target and
initiator port network information worksheet, which you should
have completed when you planned your configuration using the
Administration Worksheet and the configuration and planning guide.
Assigning an IP address to a NIC in a Windows Server 2003 or a Windows Server 2000

and 2003 virtual machine server
Open the appropriate Microsoft networking tool provided with the
operating system, such as NetWork Connections, and select the NIC
and set its IP address, as described in Microsoft documentation.
For example:
1. Select Start > Settings > Network Connections.
2. Select the NIC.
3. Select Properties > Internet Protocol (TCP/IP) > Properties and
specify the IP address for the NIC.
If the NIC is a replacement for a previously installed NIC, assign it
the same IP address as the NIC it replaced, so that it automatically

27
has the same iSCSI initiator settings and optional CHAP security
settings as the NIC it replaced.
Assigning an IP address to a QLogic iSCSI HBA in a Windows server

1. Open QLogic SANsurfer as described in the QLogic documentation.
2. Use QLogic SANsurfer to set the IP address for the HBA as
described in the documentation provided with the HBA.
If the HBA is a replacement for a previously installed HBA, assign
it the same IP address and iqn name as the HBA it replaced, so that
it automatically has the same iSCSI initiator settings and optional
CHAP security settings as the HBA it replaced.
28
Installing PowerPath on a server

PowerPath provides full failover for any storage-system configuration.
Full failover manages the I/O paths between the server and the storage
system. It protects against back-end storage-system failures, HBA
failovers, and switch fabric failovers, and supports non-disruptive
(online) upgrades of storage-system software. PowerPath also provides
I/O load balancing.
Before you start

To complete this procedure, you will need to:
Locate the PowerPath CD for your operating system in the
PowerPath kit.
Installing PowerPath on a Windows server or Windows virtual machine

IMPORTANT
If you configured your storage-system connection to your Windows
virtual machine with NICs, install PowerPath on this Windows virtual
machine. If you configured your storage-system connection to your
Hyper-V or ESX server, install PowerPath on the Hyper-V or ESX
server. You cannot configure your storage-system connection to both
your virtual machine and Hyper-V or ESX server. If the storage-system
connection is to the virtual machine, the parent Hyper-V or ESX server
will not see any LUNs on the virtual machine.
CAUTION
Close all host applications before installing or upgrading to
PowerPath 5.0. This is necessary to maintain the integrity of the
system and user data while low level disk drivers are installed or
upgraded. Failure to do so could result in data loss or corruption
of data.

29
For information on integrating PowerPath into an existing MSCS cluster, refer

to the PowerPath for Windows Installation and Administrator's Guide, which is
available
1. To install from a CD if autoplay is enabled on the server:

a. Insert the PowerPath installation CD in the server's CD drive.
b. When the Getting Started page appears, click the appropriate
link in the Installation section for the server's operating system.
c. Select Run this program from its current location (or similar
message depending on your browser) and click OK.
2. To install from a CD if autoplay is not enabled on the server, Insert
the PowerPath installation CD in the server's CD drive.
a. Insert the PowerPath installation CD in the server's CD drive.
b. On the Windows taskbar, select Start > Run.
c. In the Run window, either browse to or enter the name of the
appropriate PowerPath installation program below and click
OK.
For 32-bit Windows Server 2003, enter
d:\2003\EMCPP.W2003_32.x.y.z.GA.exe
d:\2003\EMCPP.W2003.64.x.y.z.GA.exe
where:
d is the CD drive letter
x.y.z is the revision of PowerPath on the CD.
If you do not know whether your Windows server is 32-bit or
64-bit, right-click My Computer and select Manage. Select System
Information > System Summary or select Start > Administrative Tools
> Computer Management > System Tools > Device Manager. View
the System Type or Computer option. If x86 is displayed, you have a
32-bit system. If IA64 or AMD64 is displayed, you have a 64-bit system.
30
Alternatively, double-click the platform-specific .exe icon in the

appropriate directory on the CD.
3. To install from a compressed archive file:
a. From the downloads section of the EMC Powerlink website
or from the EMC Online Support website, download the
appropriate PowerPath archive for the Windows platform
running on the server.
b. Save the file to your local directory.
c. On the Windows taskbar, select Start > Run.
d. In the Run window, either browse to or enter the name of the
appropriate PowerPath installation program below and click
OK.
d:\2003\EMCPP.W2003_32.x.y.z.GA.exe
d:\2003\EMCPP.W2003.64.x.y.z.GA.exe
where:
d is the CD drive letter
x.y.z is the revision of PowerPath on the CD.
If you do not know whether your Windows server is 32-bit or
64-bit, right-click My Computer and select Manage. Select System
Information > System Summary or select Start > Administrative Tools
> Computer Management > System Tools > Device Manager. View
the System Type or Computer option. If x86 is displayed, you have a
32-bit system. If IA64 or AMD64 is displayed, you have a 64-bit system.
Alternatively, double-click the platform-specific .exe icon in the

appropriate directory on the CD.
4. In the Choose Language Setup window, select the language you
want for this installation and click OK.
5. In the setup wizard Welcome window, click Next.
31
6. In the CLARiiON AXseries window, select Yes and click Next.

7. In the Customer Information dialog box, enter your name and
organization and click Next.
8. If the Destination Folder dialog box opens, click Next to install
PowerPath in the default directory.
We recommend that you install PowerPath in the default directory.
9. If the Setup Type dialog box opens, select Complete Install and
then Next to install PowerPath with the default features selected.
10. In the Ready to Install the Program dialog box, click Install.
If there is no license in the registry, the EMC Licensing Tool dialog
box opens.
11. In the InstallShield Wizard Completed dialog box, click Finish.
12. If the setup wizard opens and asks whether you want to reboot
the host, click Yes.
When PowerPath is installed, the following PowerPath Administrator
icon appears on the Windows taskbar:
Installing a PowerPath patch

Check the CLARiiON AX4-5 section of the storage-system support
website for a patch to the version of PowerPath that you just installed.
If such a patch is available, install it, as described in the readme file
that accompanies the patch.
32
Installing Unisphere server software

IMPORTANT
You must install the host agent or server utility on your Hyper-V or
ESX server if you:
w
configured your system connections to your Hyper-V or ESX server,
have a non-Windows virtual machine, or
have a Windows virtual machine with iSCSI HBAs.
If you configured your system connections to your Windows virtual

machine with NICs, install the host agent or server utility on the
Windows virtual machine.
This section describes how to install Unisphere 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, 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.
w
To run Unisphere server software, your server must meet the

requirements outlined in Requirements for Unisphere server software,
page 34.
To determine whether to install the Unisphere Host Agent or

Unisphere Server Utility to register your NICs or iSCSI HBAs with
the system, refer to .
Installing Unisphere server software

Depending on which Unisphere server software you are installing,
refer to the appropriate section below.
w
Unisphere Server Utility see Installing the Unisphere Server Utility

, page 36.
Navisphere CLI see Installing Navisphere CLI , page 39
Admhost Utility see .

33
Admsnap Utility see .
Requirements for Unisphere server software

To run Unisphere server software, your server must meet the following
requirements:
w
Run a supported version of the Windows operating system.
Be connected to at least one SP (two SPs for high availability) in

each system either directly or through a switch or hub. Each SP
must have an IP connection.
For the host agent and CLI only - Be on a TCP/IP network connected
to at least one SP (two SPs for high availability) in the system.
The TCP/IP network connection allows the server to send LUN
mapping information to the system and it allows or Navisphere CLI
to communicate with the system over the network.
Have a configured TCP/IP network connection to any remote hosts

that you will use to manage the systems, including:
l
any server whose browser you will use to access ,
a supported Windows server running Unisphere Server software

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

or Windows server running Navisphere CLI.
If you want to use Navisphere CLI on the server to manage systems on

a remote server, the server must be on a TCP/IP network connected to
both the remote server and each SP in the system. The remote server
can be running AIX, HP-UX, Linux, Solaris, or the Windows operating
system.
34
For information about the specific revisions of the server operating system and
the 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
EMC Online Support website.
Installing the Unisphere Host Agent

This section describes how to install the Unisphere Host Agent.
Running the Unisphere Host Agent

This section describes how to start and stop the host agent and how to
test the host agent connections.
Testing the host agent connections
Before continuing, you should test the host agent connections as
follows:
1. Start the host agent as described in.
2. Look for any errors on the console and in the operating system log
to make sure the agent started and no device errors occurred.
3. Verify that the host agent on the server can see the system as follows:
a. Enter the following CLI command:
naviseccli |navicli [-d device]| -h hostname port -list -hba
You cannot specify both the d switch and h switch.
where:
[-d device] is the device name for the system (only supported
with legacy systems).
-h hostname is the IP address of the SP.

35
For each HBA in the server, a listing similar to the following

will be displayed. For 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
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.
Downloading and installing the Microsoft iSCSI software initiator (Windows 2000 or Windows
Server 2003 hosts only)
1. From http://www.microsoft.com, navigate to the Download Center.
2. Search for and download to your host the revision of the iSCSI
initiator listed in E-Lab Navigator on the EMC Powerlink website
or the EMC Online Support website.
3. Double-click the executable to open the installation wizard and
click Next at the welcome screen.
36
4. Select the following at the Installation Options screen:

For NICs select Initiator Service, Software Initiator, and
Microsoft MPIO Multipathing Support for iSCSI (required for
Windows Server 2003 servers only), then click Next.
For iSCSI HBAs select Initiator Service and MPIO Multipathing
Support for iSCSI, then click Next.
Do not select Software Initiator for iSCSI HBAs.
5. Read and accept the license agreement and click Next to install
the software.
6. At the completion screen, click Finish if this is a new installation.
If this is an upgrade, you must reboot the system to apply the
updates. If you have a NIC and will be modifying the TCP/IP
registry settings in the next section, you do not need to reboot now.
If you have an iSCSI HBA, download and install the QLogic
SANsurfer software.
IMPORTANT
If an iSCSI initiator icon appears on the desktop, do not use this icon
to configure iSCSI HBAs; use the QLogic SANsurfer utility.
Installing the Unisphere Server Utility on a Windows server or a Windows virtual machine
with NICs
We recommend that you download and install the most recent version
of the Unisphere Server Utility software from the EMC Powerlink
website or the EMC Online Support website.
The Navisphere Server Utility is now referred to as the Unisphere Server Utility.
1. Log in as the administrator or someone who has administrative

privileges.
2. Download the software:
37
a. From the Powerlink website, select Support > Software

Downloads and Licensing > Downloads T-Z > Unisphere
Server Software and search for the link to download the
software.
or
From the EMC Online Support website, select the AX4 Support
by Product page and locate the software tools downloads.
b. Select the Unisphere Server Utility, 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.
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 number
of the software.
3. Follow the instructions on the installation screens and accept all
the defaults.
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 server's NICs or iSCSI HBAs with the system
after the installation and updates server information to the system
whenever the server configuration changes (for example, when you mount
new volumes or create new partitions).
4. If you are installing the server utility on a server that is using the
Microsoft iSCSI initiator to connect to the system, select Yes when
prompted.
38
5. 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
We recommend that you download and install the most recent version
of the Navisphere CLI software from the EMC Powerlink website or
the EMC Online Support 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 1. These ports are used by Navisphere CLI. If these ports are
not opened, the software will not function properly.
Table 1
TCP/IP ports
Software
TCP/IP ports
Classic CLI
6390, 6391, 6392
Secure CLI
443, 2163
3. Download the software:

a. From the Powerlink website, select Support > Software
Downloads and Licensing > Downloads T-Z > Unisphere
Server Software and search for the link to download the
software.
or
From the EMC Online Support website, select the AX4 Support
by Product page and locate the software tools downloads.
b. Select the Navisphere CLI, 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.
NaviCLI-Win-32-x86-language-version-build.exe
39
where:
language is either en_US, when only the English version is
available, or loc, when the localized versions are available
(including English).
version and build are the version number and the build number
of the software.
4. Follow the instructions on the installation screens to install the
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.
7. If you have a multihomed host (multiple NIC cards installed on the
host), ensure a route is created for each individual IP address.
A multihomed host machine has multiple IP addresses connected to
networks; it is physically connected to multiple data links that can be on
the same or different networks. When you install Navisphere CLI on a
multihomed host, by default, Navisphere CLI binds to the first NIC in
the host. If your host is multihomed, you should ensure each IP subnet
contains correct entries in the routing table.
a. From a console window, enter the following command to

specify a specific IP subnet route:
C:\Users\Administrator>route add [destination] MASK [subnet
mask] [gateway for NIC 1]
OK!
C:\Users\Administrator>route add [destination] MASK [subnet
mask] [gateway for NIC 2]
OK!
40
where:
destination is the subnet of the NIC being configured.
subnet mask is the same subnet mask as the NIC being
configured.
gateway is the gateway for the NIC being configured.
For example, if your host is named host28 on the domain
mydomain.com and your host contains two iSCSI HBAs/NICs,
iSCSI HBA1/NIC1 with IP address 192.111.222.1 and iSCSI
HBA2/NIC2 with IP address 192.111.223.1 with a subnet mask
of 255.255.255.0 you would create the following routes:
Each route should appear on a single line.
C:\Users\Administrator>route add 192.111.222.0
MASK 255.255.255.0 192.111.222.1
OK!
C:\Users\Administrator>route add 192.111.223.0
MASK 255.255.255.0 192.111.223.1
OK!
b. Close the console window.

41
Modifying TCP/IP registry settings

IMPORTANT
This section is recommended if you have a Microsoft iSCSI configuration.
You can improve the performance of any NICs that will be used
primarily for iSCSI traffic rather than general network traffic by
changing the network settings so that NICs immediately acknowledge
incoming TCP segments. You can use the Optimize Network Interfaces
(NICs) for iSCSI option in the server utility or you can manually
modify the TCP/IP registry settings, as described below, to improve
performance. For more information on using the server utility option,
refer to the server utility's online help.
CAUTION
The following section contains information about modifying TCP/IP
registry settings. Before you modify the registry, make sure you
back it up and understand how to restore the registry if a problem
occurs. For information about how to back up, restore, and edit the
registry, click the following link to the Microsoft Knowledge Base:
http://support.microsoft.com/kb/256986/.
Depending on your operating system type, follow the appropriate
procedure below to modify the TCP/IP settings for network interfaces
carrying iSCSI traffic so that they immediately acknowledge incoming
TCP segments.
Windows Server 2003 SP1 or later
1. Determine which IP addresses or DHCP IP addresses are used for
iSCSI traffic.
2. Start the Registry Editor.
a. Select Start >Run.
b. Enter Regedit and click OK.
3. Locate and then click the following registry subkey:
42
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet >

Services > Tcpip > Parameters > Interfaces
The interfaces will be listed below the Interfaces
folder by automatically generated GUIDs, for example,
064A622F-850B-4C97-96B3-0F0E99162E56.
4. Click each of the interface GUIDs and perform the following steps:
a. Select the IPAddress or DhcpIPAddress parameters that are used
for iSCSI traffic.
b. Select Edit > New > DWORD value.
c. Name the new value TcpAckFrequency and assign it a value
of 1.
5. Exit the Registry Editor.
6. Restart Windows for this change to take effect.

43
Connecting iSCSI ports in a network configuration

Use CAT5, CAT5e, or CAT 6 Ethernet network cables to connect the
storage-system iSCSI data ports to an Ethernet LAN and to connect the
server iSCSI data ports to either a 10/100 or 1-gigabit Ethernet LAN.
Before you start

To complete this procedure, you need:
One Ethernet network cable per storage-system iSCSI port that you
will connect to the network. You need CAT 5 Ethernet network
cables for iSCSI connections to 10/100 LANs or CAT 6 cables for
iSCSI connections to 1-gigabit LANs. These cables can be up to
100 meters long.
One Ethernet network cable per server iSCSI port that you will
connect to the network. You need CAT 5 Ethernet network cables
for iSCSI connections to 10/100 LANs or CAT 6 cables for iSCSI
connections to 1-gigabit LANs. These cables can be up to 100
meters long.
Connecting storage-system and server iSCSI ports to the LAN

1. For each iSCSI port on the storage system, connect one end of an
Ethernet network cable to the 0 iSCSI or 1 iSCSI port on the SP and
the other end to a router or switch (Figure 2).
44
FRU Label
FRU Label
CL3851
Figure 2
Connecting storage-system iSCSI ports to a LAN
2. For each NIC or iSCSI HBA port on the server, connect one end of
an Ethernet network cable (CAT 6 for 1-gigabit Ethernet network,
CAT 5 for 10/100 LAN) to the iSCSI port on the NIC or iSCSI HBA
and the other end to the network.

45
Configuring iSCSI initiators for a configuration without iSNS

If you are using iSNS, this section is not for you. Instead, go to section
on configuring the iSNS client on the system.
Before an iSCSI initiator can send data to or receive data from the
system, you must configure the network parameters for the NIC or
HBA iSCSI initiators to connect with the system SP iSCSI targets.
Configuring NIC initiators on a Windows server or Windows iSCSI virtual machine to

connect to the iSCSI targets without iSNS
Use the Unisphere Server Utility to configure the network parameters
for each NIC initiator that needs access to the system.
1. On the server, open the Unisphere Server Utility.
2. Select Configure iSCSI Connections on this server and click Next.
3. Select Configure iSCSI Connections and click Next.
4. In the iSCSI Targets and Connections window, select one of
the following options to discover the iSCSI target ports on the
connected systems:
w
Discover iSCSI targets on this subnet - Scans the current

subnet for all connected iSCSI system targets. The utility scans
the subnet in the range from 1 to 255. For example, if the current
subnet is 10.12.77, the utility will scan the IP addresses from
10.12.77.1 to 10.12.77.255.
If CHAP authentication is enabled on all target ports on a system, you
cannot discover the iSCSI target ports using a subnet scan. You must
discover the targets using the target portal.
Discover iSCSI targets for this target portal - Discovers targets

known to the specified iSCSI SP data port.
5. Click Next.
If you entered the IP address of the iSCSI target and you have
CHAP authentication enabled on that target, the CHAP login
window is displayed.
46
6. If the CHAP login window is displayed, enter the CHAP security

information (username and secret) and, if you have mutual CHAP
configured on the system and the server and you want the initiator
to authenticate the target, check Mutual CHAP, and click Next.
7. For each target you want to log in to:
a. In the iSCSI Targets window, select the IP address of the
Inactive target.
b. Under Login Options, select Also login to peer iSCSI target for
High Availability (recommended) if the peer iSCSI target is
listed.
This option allows the utility to create a login connection to
the peer target so if the target you selected above becomes
unavailable, data will continue to the peer target.
CAUTION
If multiple NICs are on the same subnet and you leave the
Server Network Adapter IP option set to Default, only one
NIC is actually used at a time. Other NICs are in standby
mode. If you leave the Server Network Adapter IP option set
to Default and a NIC fails, the server will use one of the other
NICs, even if they are on the same subnet, as long as there is a
network path from the system to the NIC that is in standby
mode.
c. If you selected Also login to peer iSCSI target for High
Availability (recommended) in the previous step, leave the
Server Network Adapter IP set to Default to allow the iSCSI
initiator to automatically fail over to an available NIC in the
event of a failure.
If you are an advanced user and you want to control which network
or subnet is used, you can select a Server Network Adapter IP address
from the drop-down list but failover may not occur if you do not have
the appropriate failover software.
d. Click Logon to connect to the selected target.

47
If CHAP authentication is enabled on the target, a CHAP login

popup dialog box is displayed.
e. If a CHAP login popup dialog box is displayed, enter the CHAP
security information (username and secret) and, if you have
mutual CHAP configured on the system and the server and
you want the initiator to authenticate the target, check Mutual
CHAP, and click OK.
The CHAP login window will not be displayed if:
you are already logged in to this target.
you already entered the CHAP credentials to this target in a previous
login and you did not close the utility.
8. Click Next.
One of the following windows is displayed:
w
Network Interfaces (NICs) window This window is displayed

if all of the following statements are true:
l
the NICs are on the same subnet as an iSCSI target connected

to this server.
the NICs appear to be used primarily for iSCSI traffic rather

than general network traffic.
the NICs do not already have the recommended TCP

settings enabled.
This window allows you to update network settings on the

selected NICs so that the NICs immediately acknowledge
incoming TCP segments.
w
Server registration window This window is displayed and

lists all connected systems if the above conditions are not true.
9. If the Network Interfaces (NICs) window is displayed:

a. Uncheck any NICs that will be used for general network traffic
and click Apply.
48
If a NIC is not listed and it is used primarily for iSCSI traffic, complete
the remaining steps in this section and refer to the server utility's online
help for information on using the Optimize Network Interface (NICs)
for iSCSI option. This option lists all the NICs on your server and
allows you to manually select which NICs you want to immediately
acknowledge incoming TCP segments for.
A confirmation dialog is displayed stating that the network

settings for your NICs have been updated but that you must
restart your system to apply them.
b. Click OK and then Next.
10. In the server registration window, click Next to send the updated
information to the system.
A success message is displayed.
11. Click Finish to close the wizard.
Configuring iSCSI HBA initiators on a Windows server or Windows virtual machine to

connect to the system iSCSI targets without iSNS
Use the QLogic SANsurfer software to configure the network
parameters for each QLogic iSCSI HBA that needs to access the system.
CAUTION
Although the Microsoft iSCSI Software Initiator Service option is
required by the QLogic driver, you must use the QLogic SANsurfer
software to control iSCSI HBAs.
2. For each iSCSI connection to the system:
a. If multiple HBAs are listed in the first column under the servers
name, select the HBA to be configured.
b. Click the Target Settings tab.

49
c. On the Target Settings page, click the green plus (+) sign and
enter the IP address for the iSCSI port on your system, and
click OK.
For the iSCSI data port IP addresses, refer to the iSCSI target and
initiator port network information worksheet, which should
have been completed when you planned your configuration.
The state for the port is No Connection Active.
d. Select Auto Discover Targets.

e. Click Save and Yes to save the changes and discover all targets.
If the network is routed, the discovery finds all targets (ports)
for the IP address you entered earlier. The state of routed ports
is Session Active; for unrouted ports, it is Unknown.
f.
In the Security Check window, enter your password and click

OK.
The default password is config.
For an existing system with CHAP already configured, the state
will be Session Failed.
g. For an existing system with CHAP already configured:

w
Configure CHAP for the iSCSI HBA initiator as described in

the section on setting up optional CHAP security.
After you enable CHAP security for the iSCSI HBA initiator,
click Save.
At the prompt to refresh the information for the server,

click Yes.
h. Select Config Parameters.

i.
50
Select and enable all the targets that you want to connect to the
server.
If you do not want the server to connect to a port or you want to

remove unknown ports, select the entry for the port and click
the red minus (-) sign.
j.
Enable timestamps, set the execution throttle to 256, and

uncheck immediate data.
k. Click Save and Yes.

l.
In the Security Check window, enter your password and click

OK.
The HBA performs an iSCSI discovery. Once finished,
SANsurfer displays all targets on the system.

51
Configuring the iSNS client on the system

Read this section if are configuring the system in an iSNS configuration.
If you configured the iSNS client on the system for a previous
installation, you do not need to reconfigure it again.
Use Navisphere Express to configure the iSNS client on the system.
iSNS (Internet Storage Naming Service) is supported only for Windows
iSCSI environments. iSNS provides the same function as the Simple
Name Server (SNS) service in a Fibre Channel fabric - automated
discovery, management, and configuration of iSCSI devices. It
eliminates the need to manually configure each individual system with
its own list of initiators and targets.
iSNS includes an iSNS server component and iSNS client component.
The iSNS server must reside somewhere within the IP storage network,
for example, on a host or in the switch firmware. An iSNS client
resides on both the iSCSI system and any iSCSI servers connected to
the system. When you start the system, the iSNS client on the system
gathers all the system iSCSI port information and stores it locally on
the system. When you add a server to the systems iSNS configuration,
Navisphere Express establishes a connection from the system to the
iSNS server, and then registers the information stored on the system
with the iSNS server.
You configure the iSNS client on the system with Navisphere Express.
Configuring the iSNS client with Navisphere Express

For each iSNS server to which you want the system to connect:
1. In the Navisphere Express Manage iSCSI page, click iSNS to open
the iSNS Servers page.
2. Click Add to open the Add iSNS Servers dialog box.
3. In the Add iSNS Servers dialog box, enter the IP address of the
server you are adding.
4. Click Apply to send the SP iSCSI port information to the server.
Before the IP address is applied, it is tested to ensure it is valid.
52
5. In the iSNS Servers dialog box, select the server to be the primary
server and click Set Primary.

53
Configuring iSCSI initiators for a configuration with iSNS

Before a NIC or HBA iSCSI initiator in a server can send data to
or receive data from the system, you must configure the network
parameters for the initiators for iSNS.
Configuring NIC initiators on a Windows server or Windows virtual machine to connect

to the system iSCSI targets with iSNS
Use the Unisphere Server Utility to configure the network parameters
for each NIC iSCSI initiator.
4. In the iSCSI Targets and Connections window, select Discover
iSCSI targets using this iSNS server to send a request to the iSNS
server for all connected iSCSI system targets and click Next.
5. For each target you want to log in to:
a. In the iSCSI Targets window, select the IP address of the
Inactive target.
b. Under Login Options, select Also login to peer iSCSI target for
High Availability (recommended) if the peer iSCSI target is
listed.
This option allows the utility to create a login connection to the
peer target so that data will continue to the peer target if the
target you selected above becomes unavailable.
54
CAUTION
If multiple NICs are on the same subnet and you leave the
Server Network Adapter IP option set to Default, only one
NIC is actually used at a time. Other NICs are in standby
mode. If you leave the Server Network Adapter IP option set
to Default and a NIC fails, the server will use one of the other
NICs, even if they are on the same subnet, as long as there is a
network path from the system to the NIC that is in standby
mode.
c. If you selected Also login to peer iSCSI target for High
Availability (recommended) in the previous step, leave the
Server Network Adapter IP set to Default. This allows the
iSCSI initiator to automatically fail over to an available NIC
in the event of a failure.
d. Click Logon to connect to the selected target.

If CHAP authentication is enabled on the target, a CHAP login
pop-up dialog box is displayed.
e. If a CHAP login pop-up dialog box is displayed, enter the
CHAP security information (username and secret) and, if you
have mutual CHAP configured on the system and the server
and you want the initiator to authenticate the target, check
Mutual CHAP, and click OK.
The CHAP login window will not be displayed if:
you are already logged in to this target.
you already entered the CHAP credentials to this target in a previous
login and you did not close the utility.

55
6. Click Next.
One of the following windows is displayed:
w
Network Interfaces (NICs) window This window is displayed

if all of the following statements are true:
l
The NICs are on the same subnet as an iSCSI target

connected to this server.
The NICs appear to be used primarily for iSCSI traffic rather

than general network traffic.
The NICs do not already have the recommended TCP

settings enabled.
This window allows you to update network settings on the

selected NICs so that the NICs immediately acknowledge
incoming TCP segments.
w
Server registration window This window is displayed and

lists all connected systems if the above conditions are not true.
7. If the Network Interfaces (NICs) window is displayed:

a. Uncheck any NICs that will be used for general network traffic
and click Apply.
If a NIC is not listed and it is used primarily for iSCSI traffic, complete
the remaining steps in this section and refer to the server utility's
online help for information on using the Optimize Network Interface
(NICs) for iSCSI option. This option lists all the NICs on your server
and allows you to manually select the NICs for which you want to
immediately acknowledge incoming TCP segments.
A confirmation dialog box is displayed stating that the network

settings for your NICs have been updated but that you must
restart your system to apply them.
b. Click OK and then Next.
information to the system.
A success message will be displayed.
56
Configuring iSCSI HBA initiators on a Windows server to connect to the system iSCSI
targets with iSNS
Use the QLogic SANsurfer package to configure the network
parameters for each HBA iSCSI initiator:
2. In the HBA tree, select the HBA and click the HBA Options tab.
The iSCSI name defaults to the iSCSI standard (iqn.xxxx).
3. Select Enable iSNS.
4. For each iSNS server, set the iSNS server address automatically or
manually:
w
For an automatic setting - Select Obtain iSNS server address

automatically (via DCHP).
For a manual setting - Select Use the following iSNS server

address and enter the IP address of the server.
5. Click Save to save the new settings.

6. On the Target Settings tab, verify that the targets were discovered.
If any target was not discovered in a system without CHAP
configured, verify that the IP address for each iSNS server is correct
and that iSNS is set up correctly on the server.
For an existing system with CHAP already configured, the state
of its targets will be Session Failed. If any other target was not
discovered, verify that the IP address for each iSNS server is correct
and that iSNS is set up correctly on the server.
7. For an existing system with CHAP already configured:
a. Configure CHAP for the iSCSI HBA initiator as described in the
section on setting up optional CHAP security.
b. After you enable CHAP security for the iSCSI HBA initiator,
click Save.
c.
At the prompt to refresh the information for the server, click

Yes.

57
Registering the server with the system

IMPORTANT
virtual machine with NICs, start the server utility or host agent on the
virtual machine. If you configured your system connection to your
Hyper-V or ESX server, start the server utility or host agent on the
Hyper-V or ESX server. If you have a non-Windows virtual machine or
a Windows virtual machine with iSCSI HBAs, perform this procedure
on the Hyper-V or ESX server.
You must run the Unisphere Server Utility on each server connected to
the system to register the servers NICs or iSCSI HBAs with the system.
Running the Unisphere Server Utility on a Windows server or a Windows virtual machine
Starting the Unisphere Server Utility on a Windows server or a Windows virtual machine
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.
Registering the server using the Unisphere Server Utility on a Windows server or a Windows
virtual machine
1. In the Unisphere Server Utility dialog box, select Register this
server to all connected systems.
The utility automatically scans for all connected systems and lists
them under connected systems.
58
2. Locate the WWN of the NIC or iSCSI HBA you just installed. The
NIC or iSCSI 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 system ports.
3. Click Next to register the server with the system.

The utility sends the servers name and IP address of the each NIC
or iSCSI HBA to each system. Once the server has storage on the
system, the utility also sends the device name and volume or file
system information for each LUN (virtual disk) in the system that
the server sees.
4. Click Finish to exit the utility.
Verifying NIC or iSCSI HBA registration with Navisphere Express

1. In the navigation pane, under Manage, click Connections to
display the Manage Connections page.
2. Verify that the SP/Port status is Active for each NIC or iSCSI HBA
connected to the system.
w
If the status is Active (unregistered), register the NIC or

iSCSI HBA with the system by running the server utility.
If the status is Inactive, either the physical connection between

the NIC or iSCSI HBA and the system is faulty or the server is
not powered up.

59
Configuring an existing storage system

Before you start
You need the completed storage-system disk information worksheet
from the storage-system configuration planning guide or the planning
worksheets document. You can generate this guide using the Plan link
on the Install page of the storage-system support website.
Configuring storage on an existing storage system with Navisphere Express

1. Locate your completed storage-system disk information worksheet
so you can refer to it in the steps that follow.
2. If you need additional disk pools for virtual disks for the server,
create one or more disk pools.
A disk pool is a set of disks, all with the same capacity and redundancy, on
which you create one or more virtual disks. A RAID 6 disk pool usually
has 6 or 12 disks, but can have 4, 8, 10, 14, or 16 disks. RAID 6 disk pools
are supported only for AX4-5 series storage systems running FLARE OE
version 02.23.050.5.7xx or later. A RAID 5 disk pool must include at least
three disks, a RAID 3 disk pool must include five or nine disks, and a RAID
1/0 disk must include at least two disks. The storage system supports a
maximum of thirty disk pools.
To create a disk pool In the navigation pane, under Manage,

click Disk Pools. For details on creating a disk pool, use the
Navisphere Express Help Center.
60
The disk modules marked 0 through 3 contain storage-system software or

reserved space according to their slot assignment. Do not move any disk
marked 0 through 3 from its assigned slot. Remove it only to replace the
disk module. Part of the space on these disks is reserved or preloaded
with system data, and as a result, is not available for your data. If you
combine operating system disks in a disk pool with other disks, each of the
other disks loses space for your data equal to the system data space on
an operating system disk.
3. If you need additional virtual disks for the server, create one or
more virtual disks on the disk pools.
Each disk pool can have 128 virtual disks.
To create a virtual disk In the navigation pane, under Manage,

click Virtual Disks.
For details on creating a virtual disk, use the Navisphere Express
Help Center.
4. Assign one or more virtual disks to the server.
To send data to or receive data from the virtual disks, you must assign
the virtual disks to a server.
To assign a virtual disk to a server In the navigation pane, under

Manage, click Virtual Disks.
For details on assigning a virtual disk to a server, use the Navisphere
Express Help Center.
5. Verify that the virtual disks were assigned to the server by looking
at the Manage Servers page.
To display the Manage Servers page In the navigation pane,
under Manage, click Servers.
61
You should see the virtual disks you assigned to the server listed in
the Virtual Disks column of the servers row.
Verifying that each virtual disk is fully initialized using Navisphere Express
Although a new virtual disk is assigned to the server, the server cannot
see the new disk until it is fully initialized. The time to complete the
initialization process varies with the size of the virtual disk and other
parameters. For example, a 1 TB virtual disk in a RAID 5 disk pool of
11 disks can take about 70 minutes to initialize with no host I/O to
other virtual disks in the disk pool.
To determine if any virtual disks are initializing:
1. Start Navisphere Express on the storage system with the virtual
disks.
2. In the navigation pane under Manage, click Virtual Disk.
3. In the Manage Virtual Disks screen, if the status of any virtual disk
is Initializing, wait until the initialization is complete before
continuing.
4. If the virtual disk is connected to a server running Windows Server
2003, reboot the server.
Making virtual disks visible to a Windows server or Windows virtual machine with NICs
IMPORTANT
If you have a Windows virtual machine with NICs, in order for a
virtual machine to see LUNs, your Windows virtual machine with
NICs must be connected to the system (either directly or through a
network) or the Hyper-V or ESX server has to assign the LUNs to the
virtual machine. A virtual machine cannot see LUNs using both of
these methods at the same time.
If you have an non-Windows virtual machine or Windows virtual
machine with iSCSI HBAs, perform this procedure on your Hyper-V
or ESX server.
To allow the Windows server access to the virtual disks that you
created, use Windows Computer Management to perform a rescan.
1. Open the Computer Management window (Start > Administrative
Tools > Computer Management.
62
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 virtual disks
IMPORTANT
or ESX server.
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 virtual disk
is n/n where n is the total number of paths to the virtual disk.

63
Verifying your high-availability iSCSI configuration

IMPORTANT
or ESX server.
Use the server high-availability feature in the Unisphere Server Utility
to verify your iSCSI configuration is highly available (for example, each
NIC has at least one active path to each storage processor) and path
management software is installed and running on the server.
Starting the Unisphere Server Utility on a Windows server or a Windows virtual machine
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.
Using the server utility to verify your high-availability configuration

1. From the Unisphere Server Utility's 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.
64
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.
The utility determines if the server is configured for high availability
by verifying that the server has at least one connection path to each
system SP, and that PowerPath or some other failover software,
such as DMP, is running. It does not detect native failover software.
6. Review and resolve any issues reported on the Issues tab of the
generated report.

65
Configuring optional CHAP security for Windows servers or Windows

virtual machines with NICs
You must configure CHAP on the system before you configure CHAP
for NIC initiators on the Windows server or Windows iSCSI virtual
machine.
IMPORTANT
machine with NICs, configure CHAP on the virtual machine. If you
configured your system connections to your Hyper-V server, configure
CHAP on the Hyper-V server. You cannot configure your system
connection to both your virtual machine and Hyper-V server. If the
system connection is to the virtual machine, the parent Hyper-V server
will not see any LUNs on the virtual machine.
Before you start

Before you configure CHAP, make sure that you complete the CHAP
worksheets in the customized planning document you created on the
system support website or on the EMC Online Support website, and
that you have the worksheets available.
CHAP security overview

Challenge Handshake Authentication Protocol (CHAP) is a method
of authenticating iSCSI users. The iSCSI system can use CHAP to
authenticate initiators and initiators can likewise authenticate targets
such as the system.
66
CAUTION
If you do not configure CHAP security for the system, any host
connected to the same IP network as the system iSCSI ports can read
from and write to the system. If the system is on a private network,
you can choose not to use CHAP security. If the system is on a public
network, we strongly recommend that you use CHAP security.
If you want to use CHAP security, you must set up and enable it on
both the server and system before preparing virtual disks to receive
data. If you prepare disks to receive data before you set up and
enable CHAP security, you lose access to the virtual disks. While
you are setting up and enabling CHAP, you may temporarily lose
connectivity between the server and the system.
CHAP has the following variant(s):
w
Initiator CHAP - Sets up accounts that iSCSI initiators use to

connect to targets. The target authenticates the initiator. Initiator
CHAP is the primary CHAP authentication method.
Navisphere Express provides Basic and Advanced initiator CHAP
options. Basic CHAP specifies one secret (password) for all initiators
that log in to a given target. The Advanced option allows you to
specify a different secret for each initiator, and also allows you to
set up mutual CHAP.
Mutual CHAP - Applied in addition to initiator CHAP, mutual

CHAP sets up an account that a target uses to connect to an initiator.
The initiator authenticates the target.
CHAP setup process for Windows server with NICs

Setting up and enabling initiator CHAP is necessary for iSCSI security
to work. Mutual CHAP is an optional additional level of security. Only
one mutual CHAP credential is supported for each system.
The setup process is as follows:
w
On a server that uses NICs, log off and remove target portals.
On the system, configure and enable initiator CHAP (basic or

advanced) by entering the initiator user data for all initiators that
are allowed access to the system.

67
If you are setting up optional mutual CHAP with Navisphere

Express, use the Advanced option to enter the mutual CHAP user
data. This is the target user account data that the system sends to
initiators.
w
On each server that uses NICs that will use the system, configure
initiator CHAP by entering the user data for each initiator that will
connect to the target. The initiator sends this data to the target and
the target uses this data to authenticate the initiator.
If you are setting up mutual CHAP, you must enter the mutual
CHAP user data on each server that uses NICs, that is, the target
user account data that the system sends to initiators. The
initiators compare this data with their stored user data when they
authenticate the system.
Logging off and removing targets on a Windows server or Windows virtual machine
with NICs
On a Windows server or Windows virtual machine that uses NICs, clear
any existing sessions or target portals to the system as described below.
When you remove an iSCSI target, the specified target and all other targets on
the system will be removed. If you want to remove a specific target on the
system, you must use the Microsoft Software Initiator.
1. On the Windows server or Windows virtual machine that includes your

iSCSI initiators, open the Unisphere Server Utility.
2. Log off and remove any targets on the system you are setting up
for CHAP:
a. Select Configure iSCSI Connections on this server and then
Configure iSCSI Connections.
b. In the iSCSI Targets and Connections window, under View
iSCSI Connections, select View currently available targets.
c. Click Next. The utility displays the IP address for each target it
discovers.
d. In the iSCSI Targets window, select the IP address of the
Connected target and click Logoff. The target status changes
to Inactive.
68
e. Select the IP address of the Inactive target and click Remove.

All targets for the system are removed.
f.
Click Cancel to close the wizard.
Configuring CHAP security on the system connected to a Windows sever with NICs
CAUTION
Windows server with NICs You must enable CHAP security on
the system before you can configure CHAP for the NICs. While
Configure CHAP security on the system with Navisphere Express.
Configuring basic initiator CHAP on a storage system with Navisphere Express

1. On your storage system management station, start Navisphere Express.
2. In the navigation pane, under Manage, click iSCSI to open the
Manage iSCSI screen.
3. To set basic security, click Basic.
4. In the iSCSI Security - Basic screen, select Enable, and then click
Initiator CHAP Configuration.
5. In the Initiator CHAP Configuration - Basic screen, click Add.
The Add Initiator CHAP Credentials - Basic screen opens.
6. In Step 1 on the screen, enter a CHAP username. This name must
match the username for the server's iSCSI initiators.
7. In Step 2 on the screen, enter and confirm a CHAP secret.
You will enter this secret on the server later.
You can specify the secret in ASCII or hexadecimal characters.

ASCII secrets must consist of at least 12 and no more than 16
characters. Hexadecimal secrets must consist of at least 12 and no
more than 16 pairs of data (24 to 32 characters). If you specify the
69
CHAP secret using hexadecimal characters, you must select CHAP

Secret Specified In Hex.
8. In Step 3 on the screen, click Apply to add the CHAP credential and
return to the Add Initiator CHAP Credentials - Basic screen.
9. Click View all initiator CHAP credentials and confirm that the
new CHAP entry exists.
Configuring advanced initiator CHAP on a storage system with Navisphere Express
3. To set advanced security, click Advanced.
4. In the iSCSI Security - Advanced screen, select Enable and then
5. In the Initiator CHAP Configuration - Advanced screen, click Add.
The Add Initiator CHAP Credentials - Advanced screen opens.
6. In Step 1 on the screen, select the initiator or initiators that will use
the new CHAP credentials.
You can allow any initiator to log in with the credentials you specify
(the equivalent of basic CHAP), or you can restrict access to a
specific initiator. To restrict access, you must create a CHAP user
for each server initiator.
match whatever is entered as a username for the server.
You can do one of the following:
w
You can manually enter a username

or
If you specified in Step 1 on the screen to restrict logins to

specific initiators, you can choose to use the initiator name
(IQN) as the CHAP user.
70
You will also enter this secret for the server initiators later.

9. In Step 4 on the screen, either click Apply to set the advanced
initiator CHAP credentials or click Cancel to return to the Initiator
CHAP Configuration - Advanced screen.
Configuring initiator CHAP on a Windows server or Windows virtual machine with NIC
initiators
CAUTION
After entering CHAP data on the target, you must enter the same data
on each NIC initiator you log in to. On each initiator, enter the initiator
CHAP user account data (username and secret) that the initiator sends
to the target for authentication. For initiator CHAP, this data is the
initiator username and secret that you entered on the target. When
the initiator sends this data, the target compares it with an account
database and authenticates the initiator.

71

connected systems:
w

10.12.77.1 to 10.12.77.255.
cannot discover a target port using a subnet scan. You must discover
the targets using the target portal.
Discover iSCSI targets for this target portal - Discovers the

specified IP address of the iSCSI SP port.
Discover iSCSI targets using this iSNS server - Sends a request

to the iSNS server for all connected iSCSI system targets.
5. Click Next.
The utility scans for iSCSI target ports and displays the IP address
for each target it discovers.
If you entered the IP address of the iSCSI target and you have CHAP
authentication enabled on that target, the CHAP login window is
displayed. Enter the CHAP security information (username and secret). If
you have mutual CHAP configured on the system and on this server, check
Mutual CHAP. Click OK.
6. In the iSCSI Targets window, select the IP address of the Inactive

target.
7. Under Login Options, select Also login to peer iSCSI target for
High Availability (recommended) if the peer iSCSI target is listed.
This allows the utility to create a login connection to the peer target
so if the target you selected above becomes unavailable, data would
continue to the peer target.
72
CAUTION
If multiple NICs are on the same subnet and you leave the Server
Network Adapter IP option set to Default, only one NIC is
actually used at a time. Other NICs are in standby mode. If you
leave the Server Network Adapter IP option set to Default and a
NIC fails, the server will use one of the other NICs, even if they
are on the same subnet, as long as there is a network path from
the system to the NIC that is in standby mode.
8. If you selected Also login to peer iSCSI target for High Availability
(recommended) in the previous step, leave the Server Network
Adapter IP set to Default. This allows the iSCSI initiator to
automatically fail over to an available NIC in the event of a failure.
9. Click Logon to connect to the selected target. If CHAP

authentication is enabled on the target, a CHAP login popup dialog
box is displayed. Enter the CHAP security information (username
and secret) and, if you have mutual CHAP configured on the system
and the server, check Mutual CHAP if you want the initiator to
authenticate the target. Click OK.
If you are running PowerPath 4.6 or later, the Unisphere Server Utility will
automatically enable multipath when logging in to the target.
10. Repeat steps 6 9 for each target you want to log in to.
11. Click Next. The server registration window opens and lists all
connected systems.
information to the system. A success message will be displayed.
73
You have set and enabled initiator security on the server and system.
Configuring mutual (target) CHAP on a Windows server or Windows virtual machine

with NIC initiators
CAUTION
After entering CHAP data on the target, you must enter the same
CHAP user account data (username and secret) on each NIC initiator
that will connect to the target. The initiator sends the user account
credentials to the target for authentication. When the initiator sends this
data, the target compares it with an account database and authenticates
the initiator.
3. If you are setting up mutual CHAP, follow the steps below.
If you are not setting up mutual CHAP, go to step 4.
a. Select Configure Mutual CHAP and click Next.
b. In the Mutual CHAP Authentication window, enter the mutual
CHAP secret (password). If you have already configured
mutual CHAP on the system, enter the same secret. Click Next.
You entered the mutual CHAP secret in the Add Initiator CHAP
Credentials - Advanced page.
c. Click Finish in the success window.

connected systems:
74

10.12.77.1 to 10.12.77.255.
cannot discover a target port using a subnet scan. You must discover
the targets using the target portal.
Discover iSCSI targets for this target portal - Discovers targets

known to the specified iSCSI SP data port.
Discover iSCSI targets using this iSNS server - Sends a request

to the iSNS server for all connected iSCSI system targets.
6. Click Next. If you entered the IP address of the iSCSI target and
you have CHAP authentication enabled on that target, the CHAP
login window is displayed. Enter the CHAP security information
(username and secret) and if you have mutual CHAP configured on
the system and the server and you want the initiator to authenticate
the target, check Mutual CHAP. Click Next.
The utility scans for iSCSI target ports and displays the IP address
for each target it discovers.
7. In the iSCSI Targets window, select the IP address of the Inactive
target.
8. Under Login Options, select Also login to peer iSCSI target for
High Availability (recommended) if the peer iSCSI target is listed.
This allows the utility to create a login connection to the peer target
so if the target you selected above becomes unavailable, data would
continue to the peer target.

75
CAUTION
If multiple NICs are on the same subnet and you leave the Server
Network Adapter IP option set to Default, only one NIC is
actually used at a time. Other NICs are in standby mode. If you
leave the Server Network Adapter IP option set to Default and a
NIC fails, the server will use one of the other NICs, even if they
are on the same subnet, as long as there is a network path from
the system to the NIC that is in standby mode.
9. If you selected Also login to peer iSCSI target for High Availability
(recommended) in the previous step, leave the Server Network
Adapter IP set to Default. This allows the iSCSI initiator to
automatically fail over to an available NIC in the event of a failure.
10. Click Logon to connect to the selected target. If CHAP

authentication is enabled on the target, a CHAP login pop-up
dialog box is displayed. Enter the CHAP security information
(username and secret) and, if you have mutual CHAP configured
on the system and the server and you want mutual CHAP enabled
on the initiator, check Mutual CHAP. Click OK.
If you are running PowerPath 4.6 or later, the server utility will
automatically enable multipath when you log in to the target.
11. Repeat steps 7 10 for each target you want to log in to.
12. Click Next. The server registration window opens and lists all
connected systems.
information to the system. A success message is displayed.
76
If you have the host agent installed on the server, you will get an error
message indicating that the host agent is running and you cannot use the
server utility to update information to the ; the host agent will do this
automatically.

You have completed the setup and enabling of advancedtarget security
on the server and system.

77
Configuring optional CHAP security for iSCSI HBA initiators

You must configure CHAP for iSCSI HBA initiators on the Windows
server before you configure CHAP on the system.
Before you start

Before you configure CHAP, make sure that you complete the CHAP
worksheets in the customized planning document you created on the
system support website or on the EMC Online Support website, and
that you have the worksheets available.
For more information on the QLogic SANsurfer software, refer to the
QLogic documentation supplied with the QLogic iSCSI HBA. Note that
the QLogic documentation uses the term Initiator Name to describe
CHAP Username, Initiator Secret to describe CHAP Secret, and CHAP
to describe Initiator (Basic) CHAP.
CHAP security overview

Challenge Handshake Authentication Protocol (CHAP) is a method
of authenticating iSCSI users. The iSCSI system can use CHAP to
authenticate initiators and initiators can likewise authenticate targets
such as the system.
CAUTION
If you do not configure CHAP security for the system, any host
connected to the same IP network as the system iSCSI ports can read
from and write to the system. If the system is on a private network,
you can choose not to use CHAP security. If the system is on a public
network, we strongly recommend that you use CHAP security.
If you want to use CHAP security, you must set up and enable it on
both the server and system before preparing virtual disks to receive
data. If you prepare disks to receive data before you set up and
enable CHAP security, you lose access to the virtual disks. While
78
CHAP has the following variant(s):

w
Initiator CHAP - Sets up accounts that iSCSI initiators use to

connect to targets. The target authenticates the initiator. Initiator
CHAP is the primary CHAP authentication method.
Navisphere Express provides Basic and Advanced initiator CHAP
options. Basic CHAP specifies one secret (password) for all initiators
that log in to a given target. The Advanced option allows you to
specify a different secret for each initiator, and also allows you to
set up mutual CHAP.
Mutual CHAP - Applied in addition to initiator CHAP, mutual

CHAP sets up an account that a target uses to connect to an initiator.
The initiator authenticates the target.
CHAP setup process for iSCSI HBAs

Setting up and enabling initiator CHAP is necessary for iSCSI security
to work. Mutual CHAP is an optional additional level of security. Only
one mutual CHAP credential is supported for each system.
The setup process is as follows:
w
On each server that will use the system, configure initiator CHAP
by entering the user data for each initiator that will connect to the
target. The initiator sends this data to the target and the target uses
this data to authenticate the initiator.
If you are setting up mutual CHAP, you must enter the mutual
CHAP user data on each server, that is, the target user account data
that the system sends to initiators. The initiators compare this data
with their stored user data when they authenticate the system.

79
On the system, configure and enable initiator CHAP (basic or

advanced) by entering the initiator user data for all initiators that
are allowed to access the system.
Configuring initiator CHAP on a Windows server with iSCSI HBA initiators
CAUTION
You must enable CHAP security for the NIC or iSCSI HBA before
you can configure CHAP on the system. While you are setting up
and enabling CHAP, you may temporarily lose connectivity between
the server and the system.
Configure initiator CHAP on each iSCSI HBA that communicates with
the server.
The steps below apply to version 4.01.00 or later of the QLogic
SANsurfer software. If you are running an earlier version, refer to the
SANsurfer documentation.
The SANsurfer diagnostic read/write buffer test is not supported on EMC
systems..
1. Open the SANsurfer software.

2. Click Connect and enter the hostname or IP address. Click Connect.
3. Under the iSCSI HBA tab, double-click the HBA and select the
HBA port.
4. Click the Target Settings tab.
5. Click Config Authentication on the bottom of the pane.
The default password is config.
6. Select the CHAP tab.

7. Click the green plus sign (+) on the right of the CHAP Entries
portion of the CHAP screen.
80
a. Type in the initiator name for your HBA initiator. This name
must match the CHAP username you entered on the system.
b. Type in the secret for that initiator. The CHAP username secret
must match the secret you entered on the system.
8. Under the Targets portion of the CHAP screen, select the Chap
Name/Secret row; then from the drop-down menu, select the
initiator name and secret you just entered in the CHAP Entries
table.
9. Click OK.
10. Save your changes on the Target Settings window (the default
password remains config).
You have set up initiator CHAP security on the server.
Configuring mutual (target) CHAP on a Windows server with iSCSI HBA initiators
CAUTION
Mutual CHAP is applied in addition to initiator CHAP, so you must set
up initiator CHAP before setting up mutual CHAP.
The steps below apply to version 4.01.00 or later of the QLogic
SANsurfer software. If you are running an earlier version, refer to the
SANsurfer documentation.
The SANsurfer diagnostic read/write buffer test is not supported on EMC
systems.
1. Open the SANsurfer software.

2. Click Connect and enter the hostname or IP address, and click
Connect.
3. Under the iSCSI HBA tab, double-click the HBA and select the
HBA port.
81
4. Select the Target Settings tab.

5. Select Config Authentication from the bottom of the pane, and in
the password prompt, use the password config.
6. Select the CHAP tab.
7. Click the green plus sign (+) on the right of the Target Table portion
of the CHAP screen.
a. In the blank row under the Target Name column, enter the
CHAP username that you entered on the system.
b. In the Target Secret column, enter the CHAP secret that you
entered on the system.
8. Under the Targets portion of the CHAP screen, select Bidi
(bi-directional) for the target you want the initiator to authenticate.
9. Click OK.
10. Save your changes on the Target Settings screen (the default
password remains config).
You have set up mutual CHAP security on the server.
Configuring CHAP security on a system

If you are configuring optional CHAP security, read this section in
either for the following situations:
82
The system was not connected to another system when you started
attaching it to this server
The system was connected to another server when you started

attaching this server to it and either
l
You installed a new NIC in this server, or
You installed a new iSCSI HBA in this server and you did
not already add the HBA to the existing system CHAP
configuration. The CHAP configuration procedure registers
the iSCSI HBA.
CAUTION
Configuring basic initiator CHAP on a storage system with Navisphere Express

3. To set basic security, click Basic.
4. In the iSCSI Security - Basic screen, select Enable, and then click
5. In the Initiator CHAP Configuration - Basic screen, click Add.
The Add Initiator CHAP Credentials - Basic screen opens.
match the username for the server's iSCSI initiators.
You will enter this secret on the server later.

8. In Step 3 on the screen, click Apply to add the CHAP credential and
return to the Add Initiator CHAP Credentials - Basic screen.
83
Configuring advanced initiator CHAP on a storage system with Navisphere Express

3. To set advanced security, click Advanced.
4. In the iSCSI Security - Advanced screen, select Enable and then
5. In the Initiator CHAP Configuration - Advanced screen, click Add.
The Add Initiator CHAP Credentials - Advanced screen opens.
6. In Step 1 on the screen, select the initiator or initiators that will use
the new CHAP credentials.
You can allow any initiator to log in with the credentials you specify
(the equivalent of basic CHAP), or you can restrict access to a
specific initiator. To restrict access, you must create a CHAP user
for each server initiator.
match whatever is entered as a username for the server.
You can do one of the following:
w
You can manually enter a username

or
If you specified in Step 1 on the screen to restrict logins to

specific initiators, you can choose to use the initiator name
(IQN) as the CHAP user.

You will also enter this secret for the server initiators later.

84

9. In Step 4 on the screen, either click Apply to set the advanced
initiator CHAP credentials or click Cancel to return to the Initiator
CHAP Configuration - Advanced screen.

85
Preparing virtual disks to receive data

If you do not want to use a virtual disk as a raw disk or raw volume,
then before Windows can send data to a virtual disk, you must:
Use Navisphere Express to verify that each new virtual disk is
initialized and to write a signature to it, as described in the 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:
86
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 system
If the Unisphere Host Agent is installed on the server, stop and then
restart it to send the system the operating system's device name and
volume or file system information for each LUN that the server sees.
The Unisphere Server Utility does not send operating system LUN
mapping information to the system, so this procedure is not required.
IMPORTANT
machine with NICs, perform this procedure on the virtual machine.
If you configured your system connections to your Hyper-V or ESX
server, perform this procedure on the Hyper-V or ESX server. You
cannot configure your system connection to both your virtual machine
and Hyper-V or ESX server. If the system connection is to the virtual
machine, the parent Hyper-V or ESX server will not see any LUNs on
the virtual machine.
If you have a server with iSCSI HBAs or a non-Windows virtual
machine with NICs, perform this procedure on your Hyper-V or ESX
server.
Stopping the host agent on a Windows server or Windows virtual machine

1. At the Windows server or Windows virtual machine, log in as the
administrator or the equivalent.
2. Open the Services pane.
w
From the desktop, right-click My Computer and select Manage

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

The Services pane opens.

3. In the Services pane, right-click Unisphere Agent and select Stop.

87
4. If asked to confirm your request to stop the agent service, click Yes,
and close the Services pane.
Starting the host agent on a Windows server or Windows virtual machine

1. Log in as the administrator or the equivalent.
w

or


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.
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:
w
Applications are using the 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 virtual machine with NICs

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

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 dialog box.
Starting the host agent on a Windows virtual machine with NICs

1. Log in as the administrator or the equivalent.
w

or


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.
The Unisphere Agent Properties dialog box opens.
b. Select the General tab.
c. In Startup Type, select Automatic.
5. Close Computer Management.
The host agent will now start automatically at system startup.
It may take a few minutes for the host agent to start when:
w
Applications are using the system, or
The SP event log is large and the host agent configuration file is
not set up.
Verifying that the system received the disk information using Navisphere Express
1. Start Navisphere Express on the storage system with the virtual
disks.
89
2. For each virtual disk in the storage system that is connected to the
server, display its Navisphere Express Details page:
a. In the navigation pane, under Manage, click Virtual Disks.
b. On the Manage Virtual Disk page, click the virtual disk to
display its Details page.
3. Verify that the Details page displays the volume or file system and
device name for the virtual disk.
90
Verifying your failover configuration with PowerPath

Perform the following steps to verify that the server can send data to
and receive data from the 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 system
from the following website: http://www.iometer.org/
Verifying your failover configuration with PowerPath for a Windows server or Windows
virtual machine
IMPORTANT
machine with NICs, perform this procedure on the virtual machine.
If you configured your system connections to your Hyper-V server,
perform this procedure on the Hyper-V server. You cannot configure
your system connection to both your virtual machine and Hyper-V
server. If the system connection is to the virtual machine, the parent
Hyper-V server will not see any LUNs on the virtual machine.
If you have a server with iSCSI HBAs or a non-Windows virtual
machine with NICs, perform this procedure on your Hyper-V server.
1. If you are connected to an existing system, stop all applications that
are accessing the system and disable user logins to the server.
2. Launch PowerPath Administrator by double-clicking the
PowerPath Monitor icon on the Windows taskbar.
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.
91
5. Verify that all n paths to the disks in the system are working; that is,
their status is optimal and their path metric is n/n.
6. For each NIC or iSCSI HBA connected to the system:
a. Start writing data to a virtual disk.
b. Disconnect the cable from one NIC or iSCSI HBA connected
to the system.
c. After several seconds, look at the Details pane and verify that
one or more of the disks in the 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 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 NIC or
iSCSI 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 system have red slashes through them,
their status is optimal, and their path metric is n/n.
7. If you are connected to an existing system, restart any applications

that you stopped and re-enable any user logins to the server that
you disabled.
92
Copyright 2007-2011EMC 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.
93

AX4 Installing An ISCSI Storage System - Master 1692635

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

AX4 Installing An ISCSI Storage System - Master 1692635

Загружено:

Авторское право:

Доступные форматы

Here is Your Customized Document

Your Configuration is:

Content Creation Date 2012/4/4

Installing an AX4-5i Storage System

If you want to install an AX4-5i storage system in a network configuration

The main topics are:

Verifying your high-availability iSCSI configuration .......................

A computer that is or will be connected to a CLARiiON storage

A host from which you manage CLARiiON storage systems. It

A host that is already or will be connected over a network to the

A server that is not already connected to or set up for a CLARiiON

existing NIC or iSCSI

new NIC or iSCSI HBA

base dual-SP system

An AX4-5 series system with two storage processors (SPs) an

An AX4-5 series system with two storage processors (SPs)

existing storage system

A storage system that is already connected to a server and

A storage-system component that you can add to your storage

A disk processor enclosure that contains 1 or 2 storage processors

A disk-array enclosure that provides additional storage for a

Installing an AX4-5i Storage System in an iSCSI Network Configuration with a

storage processor (SP)

A printed-circuit board with processors, memory modules, and

A grouping of physical disk partitions into one span of disk storage

A NIC or iSCSI HBA port that issues requests to send data to or

A storage-system SP port that accepts and responds to requests

Challenge Handshake Authentication Protocol. An optional

Microsoft Internet Storage Naming Service (iSNS) provides

An AX4-5i storage system has two SPs, so it is called a dual-SP system.

Before you start

The server hardware that will access the storage system.

The operating system version running on the server hardware.

For any installation, you will need:

As a Navisphere management station

To run the Navisphere Service Taskbar, which runs only on

As a CLARalert monitor station, which must be a Windows

A Windows 2000, Windows Server 2003 or Windows Server 2008

For cable specifications, refer to Technical Specifications on the Learn

Resetting the storage-system security settings

You log in to the storage system with a valid username and

You create a new user account.

You modify an existing user account.

The 15 minutes is up.

Security button on each SP (dual-SP system shown)

2. After 2 minutes, start Navisphere Express on the storage system:

Installing an AX4-5i Storage System in an iSCSI Network Configuration with a

c. Either log in to Navisphere Express as you normally would or

Upgrading storage-system software

Install the storage-system software with the software upgrade feature

Preparing to install software on an existing storage system

Installing an AX4-5i Storage System in an iSCSI Network Configuration with a

Verifying that connected servers are configured for high availability

The server products installation guide for the operating system

2. Using the instructions in the appropriate server support products

If the AX version of the Navisphere Server Utility is installed on the

b. Generate a high-availability report.

Upgrading storage-system software with Navisphere Express

1. If you are updating FLARE OE software, download the latest

(http://Powerlink.EMC.com) onto the host or server from which

The FLARE OE software is in a .pbu file.

After the installation is complete, the storage system reboots

Upgrading storage-system software with the Software Assistant