Reporting Problems
To send comments or report errors regarding this document,
please email: mydocs@emc.com.
For Issues not related to this document, contact your service provider.
Refer to Document ID:
1416899054917
Content Creation Date November 25, 2014
u
u
u
u
u
u
u
u
u
If you will configure your system connections to your ESX or Hyper-V server, you must
attach the ESX or Hyper-V server to your system prior to performing the steps in this
document. For information on attaching an ESX or Hyper-V server to your system,
generate a new document and select the appropriate ESX or Hyper-V server version.
u
Read the release notes for your system, which are available on the EMC Online
Support website.
The following network information from the person responsible for your network:
System iSCSI network information, including static IP address, subnet mask, and
default gateway for each system iSCSI port that you will use.
You must have a supported Windows host on the same network as the system
management ports. You can use this host:
l
To run the Unisphere Service Manager, which runs only on a Windows host.
You must have a Unisphere Server with a supported Internet browser that is on the
same network as the system management ports. This host can also be the server or a
Unisphere management station. For supported Internet browsers, see the Unisphere
release notes on the EMC Online Support website.
You must have, a Windows 2000, Windows Server 2003, Windows Server 2008, or
Windows 2012 host that is or will be a server with iSCSI connections to the system.
This server must have a supported server configuration; that is, it must have all
required updates, such as hot fixes or patches, installed.
Each Fibre Channel front-end port that you will use on the system must have an
optical cable. These cables may already be connected for a configuration with an
existing system or server. We strongly recommend you use OM3 50 m cables. For
cable specifications, refer to the system's technical specifications.
You must have a Cat5, Cat5e, or Cat6 Ethernet network cable (100 meters maximum)
for each system iSCSI port that will connect 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 system or
existing server. For cable specifications, refer to system's Technical Specifications.
The following cables, which may already be connected for a configuration with an
existing system or existing server:
A Cat 5e or higher, Ethernet LAN cable (100 meters maximum) for each system 1
GbE iSCSI port that will connect through network routers or switches to the NICs or
iSCSI HBAs in the server. We recommend Cat 6 cables for best performance.
A fibre optical cable for Ethernet transmisssion or an active twinaxial cable for
each system 10 GbE iSCSI port that will connect directly though network routers or
switches to the NICs or iSCSI HBAs in the server. We strongly recommend you use
OM3 50 m cables.
Note
You must have a method for writing data to a LUN on the system that will test the
paths from the server to the system. You can download an I/O simulator (Iometer)
from the following website: http://www.iometer.org.
We recommend that you never mix NICs or iSCSI HBAs from different vendors in the same
server.
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:
u
Use a ground (ESD) strap whenever you handle NICs or iSCSI HBAs.
Never plug or unplug NICs or iSCSI HBAs with the power on. Severe component
damage can result.
Procedure
1. If the server is powered up:
a. Shut down the server's operating system.
Installing NICs or iSCSI HBAs in the server
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.
If you have a QLogic driver, download the latest supported version and instructions
for installing the driver from the vendors website:
http://support.qlogic.com/support/oem_emc.asp
u
Any updates, such as hot fixes to the servers 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
4. Reboot the server when the installation program prompts you to do so. If the
installation program did not prompt you to reboot, then reboot the server when the
driver installation is complete.
If you configured your system iSCSI connections to your Windows virtual machine with
NICs, start the iSCSI service on the virtual machine. If you configured your system
connections to your Hyper-V server, start the iSCSI service on the NIC or iSCSI HBA in the
Hyper-V server. If you have a non-Windows virtual machine or a Windows virtual machine
with iSCSI HBA, start the iSCSI service on the NIC or iSCSI HBA in the Hyper-V server.
For Windows Server 2012 servers and virtual machines, you do not need to download and
install the iSCSI initiator software. The operating system includes the iSCSI initiator
software. You do need to start the iSCSI service before running the Unisphere Server
Utility.
Procedure
1. From the server, click Start > All Programs > Administrative Tools > iSCSI Initiator.
2. In the Microsoft iSCSI dialog box, click Yes to start the iSCSI service.
Note
If the server is behind a Windows firewall, Microsoft asks if you want to communicate
through the firewall. We suggest that you consult with your network support person
before proceeding.
If you configured your system iSCSI connections to your Windows 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.
3. Identify the NIC for which you want to set the IP address, right-click the NIC and select
Properties.
4. In the Networking tab, verify that IPV6 is not selected.
5. Highlight the IPV4 option and click Properties.
6. In the General tab, select Use the following IP address.
7. Enter an IP address for each NIC that you want to use.
8. Click OK and close all open dialog boxes.
If you configured your system iSCSI connections to your Windows virtual machine with
NICs, install PowerPath software on the virtual machine. If you configured your system
connections to your Hyper-V or ESX server, install PowerPath software on the Hyper-V or
ESX server. You cannot configure your system connections to both your virtual machine
and Hyper-V or ESX server. If the system connections 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 non-Windows virtual machine or a Windows virtual machine with iSCSI
HBAs, install PowerPath software on the Hyper-V or ESX server.
Install PowerPath by referring to the appropriate PowerPath Installation and
Administration Guide for your operating system. This guide is available on the EMC
Online Support website.
Check the download section on the EMC Online Support website for a more recent version
of PowerPath or a patch to the version of PowerPath installed on the server. If a more
recent version exists, install it, as described in the appropriate PowerPath Installation
and Administration Guide for your operating system. This guide is available on the EMC
Online Support website. If the server is running the most recent version and a patch
exists for this version, install it, as described in the readme file that accompanies the
patch.
You must install the host agent or server utility on your Hyper-V or ESX server if you:
u
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.
If you plan to install Navisphere CLI, Admhost, or Admsnap, you must install them on a
virtual machine. For instructions on installing these software programs on a virtual
machine other than Windows Server 2008, generate a new document and select the
operating system running on the virtual machine.
Before you begin
Refer to the sections below to determine which application to install for host registration
and the requirements for installing each of these applications.
u
To run Unisphere server software, your server must meet the requirements outlined in
Requirements for Unisphere server software on page 7.
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 Determining whether to
install the Unisphere Host Agent on page 8.
Unisphere Host Agent see Installing the Unisphere Host Agent on page 9.
Navisphere CLI see Installing VNX for Block Secure CLI on page 15.
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 Navisphere CLI to communicate with the system over the
network.
Installing Unisphere server software
Have a configured TCP/IP network connection to any remote hosts that you will use to
manage the systems, including:
l
any AIX, HP-UX, Linux, VMware ESX Server, Solaris, or Windows server running
VNX for Block CLI.
If you want to use VNX for Block 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.
Note
For information about the specific revisions of the server operating system, the system
VNX for Block OE, 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 Online Support website.
Monitor system events and notify personnel by e-mail, page, or modem when any
designated event occurs.
Retrieve LUN world wide name (WWN) and capacity information from VNX systems.
Table 1 Host registration differences between the host agent and the server utility
Function
Runs automatically to
send information to the
system.
Table 1 Host registration differences between the host agent and the server utility (continued)
Function
Requires network
connectivity to the
system.
Installing the Unisphere Host Agent 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
Host Agent software from the EMC Online Support website.
Procedure
1. Log in as the administrator or a user who has administrative privileges.
2. If your server is behind a firewall, open TCP/IP port 6389.
This port is used by the host agent. If this port is not opened, the host agent will not
function properly.
3. If you are running a version prior to 6.26 of the host agent, you must remove it before
continuing with the installation.
4. Download the software:
a. From the EMC Online Support website, select the appropriate VNX Series Support
by Product page and select Downloads.
b. Select the Unisphere Host Agent, and then select the option to save the software
to your server.
c. Double-click the executable file listed below to start the installation wizard.
UnisphereHostAgent-Win-32-x86-en_US-version-build.exe
where version and build are the version number and the build number of the
software.
5. Follow the instructions on the installation screens to install the Unisphere Host Agent.
The Unisphere Host Agent software is installed on the Windows server. If you selected
the default destination folder, the software is installed in the C:\Program Files
\EMC\HostAgent.
Once the Unisphere Host Agent installation is complete, the Initialize Privileged User
List dialog box is displayed.
6. In the Initialize Privileged User List dialog box, perform one of the following:
l
If the Config File field contains a file entry, then a host agent configuration file
already exists on the server from a previous agent installation. Select Use Existing
File to use this configuration file or select Browse to use a different file.
Installing the Unisphere Host Agent
The host agent configuration file contains a list of login names for this server. Only
users whose usernames are listed in the Privileged User List can send CLI
commands to the system.
l
If the Config File field does not contain a file entry, then a host agent configuration
file does not exist on the server. Select Create/Overwrite File and browse to the
agent.config file.
You will then need to add users to the Privileged User List (login names for this
server). Only users whose usernames are listed in the Privileged User List can send
CLI commands to the system.
Note
There must be at least one entry in the Privileged User List or an error message will
appear.
7. To add a user to the list:
a. Click Add to open the Add Privileged User dialog box.
b. In the Add Privileged User dialog box, under User Name, enter the persons
account username, for example, Administrator.
c. Under System Name, enter the name of the host running Unisphere> (for example,
Host4) and click OK.
8. To remove a privileged user from the list:
a. Select the privileged username, and click Remove.
9. Click OK to save the new privileged user list and /or >the new configuration file.
The program saves the host agent configuration file with the new privileged user
entries and starts the host agent.
10.Click Finish.
A command line window opens indicating that the host agent service is starting.
11.If the system prompts you to reboot the server, click Yes.
Servers with NIC initiators If you do not reboot before you run the
Microsoft iSCSI software initiator, the NIC initiators cannot log in to the system.
12.If you updated the host agent and were using event monitor, restore the event monitor
configuration from a previously copied Navimon.cfg file:
a. Stop the agent:
a. At the Windows server, log in as the administrator or the equivalent.
b. Open the Services pane.
For Windows 2008 and earlier versions, from the desktop, right-click My
Computer and select Manage > Services and Applications > Services; or for
Windows 2012, from the desktop, mouse over to the left bottom corner of
the taskbar and select Start, then right-click Computer > Manager > Tools >
Services.
The Services pane opens.
c. In the Services pane, right-click Navisphere Agent and select Stop.
d. If asked to confirm your request to stop the agent service, click Yes, and close
the Services pane or dialog box.
b. Move or copy the saved Navimon.cfg to the real Navimon.cfg file.
10
11
If EV_AGENTID_DIRECTORY or HKEY_LOCAL_MACHINE\SOFTWARE\EMC
\Agent\1.0\ConfigPath does not exist, create the agentID.txt file in
the C:\ directory.
b. Add the following two separate lines to the agentID.txt file, with no special
formatting:
First line: Fullyqualified hostname of the host
Second line: IP address of the NIC port that you want host agent to use
For example, if your host is named host28 on the domain mydomain.com and
your host contains two NICs, NIC1 with IP address 192.111.222.2 and NIC2 with IP
address 192.111.222.3, and you want the host agent to use NIC 2, you would
configure agentID.txt as follows:
host28.mydomain.com 192.111.222.3
Note
The agentID.txt file should contain only these two lines, without any
formatting. The first line should contain the hostname and the second line should
contain the IP address of the NIC port as described above. Both lines should end
with a carriage return. As a result, the cursor will be on a third line but this line
should not contain any text.
c. Save the agentID.txt file.
d. Restart the host agent.
e. Once the host agent has restarted, verify that the host agent is using the correct IP
address that is entered in the agentID.txt file by doing one of the following:
From Unisphere>, verify that the host IP address is the same as the IP address
that you entered in the agentID.txt file.
If the address is the same, the agentID.txt file is configured correctly.
View the new HostIdFile.txt file.
You should see the IP address that is entered in the agentID.txt file.
15.Verify that Unisphere Host Agent is installed using the Add/Remove Programs dialog
box.
12
Note
When a system experiences heavy input/output traffic (that is, applications are using the
system), information may not be reported to the host agent in a timely manner, resulting
in the host agent taking several minutes to execute a system management task. This
behavior is most evident when one host agent is managing multiple systems. Also, if the
SP event log is large and the host agent configuration file is set up to read all events, it
may take a few minutes for the host agent to start.
Procedure
1. Log in as the administrator or the equivalent.
2. Open the Services pane.
a. For Windows 2008 and earlier versions, from the desktop, right-click My Computer
and select Manage > Services and Applications > Services; or for Windows 2012,
from the desktop, mouse over to the left bottom corner of the taskbar and select
Start, then right-click Computer > Manager > Tools > Services.
This section describes how to start and stop the host agent service. This section
also describes how to configure the system connected to the server.
Note
When a system experiences heavy input/output traffic (that is, applications are
using the system), information may not be reported to the host agent in a timely
manner, resulting in the host agent taking several minutes to execute a system
management task. This behavior is most evident when one host agent is managing
multiple systems. Also, if the SP event log is large and the host agent configuration
file is set up to read all events, it may take a few minutes for the host agent to
start.
The Services pane opens.
3. In the Services pane, right-click Navisphere Agent and select Start.
4. If you want the host agent to start automatically at system startup:
a. Right-click Navisphere Agent and select Properties.
The Navisphere Agent Properties dialog box opens.
b. Select the General tab.
c. In Startup Type, select Automatic.
5. Close the Services pane.
Results
The host agent now start automatically at system startup.
It may take a few minutes for the host agent to start when:
u
The SP event log is large and the host agent configuration file is not set up.
The SP event log is large and the host agent configuration file is not set up.
13
For Windows 2008 and earlier versions, from the desktop, right-click My Computer
and select Manage > Services and Applications > Services; or for Windows 2012,
from the desktop, mouse over to the left bottom corner of the taskbar and select
Start, then right-click Computer > Manager > Tools > Services.
14
b. In the listing, verify the path for each HBA installed in the host to the SP.
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 applicable support by product page on the EMC Online
Support website.
Procedure
1. Log in as the administrator or someone who has administrative privileges.
2. Download the software:
a. From the EMC Online Support website, select the VNX Series Support by Product
page and select Downloads.
b. Select the Unisphere Server Utility, and then select the option to save the software
to your server.
c. Double-click the executable 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.
Note
If you do not have the host agent installed, do not disable the registration service
feature (it is enabled by default). The registration service feature automatically
registers the servers 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.
5. When the installation is complete, click Done to exit the wizard.
15
Installing VNX for Block Secure CLI on a Windows server or a Windows virtual machine
We recommend that you download and install the most recent version of the VNX for
Block Secure CLI software from the applicable support by product page on the EMC
Online Support website.
Procedure
1. Log in as the administrator or someone who has administrative privileges.
2. If an earlier version of the CLI is already installed, you must remove it before
continuing with the installation.
The installation program does not let you overwrite an existing version.
3. If your server is behind a firewall, open the TCP/IP ports listed in TCP/IP ports on page
16.
These ports are used by VNX for Block CLI. If these ports are not opened, the software
will not function properly.
Table 2 TCP/IP ports
5. Follow the instructions on the installation screens to install the Navisphere Secure
CLI.
6. When the installation is complete, click Done to exit the wizard.
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).
You have installed the VNX for Block CLI software.
7. Verify that VNX for Block Secure CLI is installed using the Add/Remove Programs
dialog box.
8. If you have a multihomed host (multiple NIC cards installed on the host), ensure a
route is created for each individual IP address.
16
Note
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 NICs, NIC1 with IP address 192.111.222.1 and NIC2 with IP
address 192.111.223.1 with a subnet mask of 255.255.255.0 you would create
the following routes:
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!
Note
The Admhost Utility is supported on Microsoft Windows platforms only. For the supported
Windows versions, see the Admhost Release Notes.
Installing the Admhost Utility on a Windows server or a Windows virtual machine with NICs
We recommend that you download and install the most recent version of the Admhost
Utility software from the applicable support by product page on the EMC Online Support
website.
NOTICE
If you configured your system connections to your Windows virtual machine with NICs,
install admhost on the virtual machine. If you configured your system connections to your
Hyper-V server, install admhost on the Hyper-V server. You cannot configure your system
connection to both your virtual machine and Hyper-V server.
Installing the Admhost Utility
17
Procedure
1. Log in as the administrator or as someone who has administrator privileges.
2. If admhost is already installed, remove it.
3. Download the software:
a. From the EMC Online Support website, select the VNX Series Support by Product
page and select Downloads.
b. Select the Admhost Utility, and then select the option to save the software to your
server.
c. In the folder where you saved the software, double-click the executable file to start
the installation wizard.
4. Follow the instructions on the installation screens to install the Admhost Utility.
5. When the installation is complete, click Finish to exit the wizard.
You have installed the admhost software.
If you selected the default destination folder, admhost is installed in the C:
\Program Files\EMC\Unisphere Admhost (32bit) or C:\Program Files
(x86)\EMC\Unisphere Admhost (64bit).
Installing the Admsnap Utility on a Windows server or Windows virtual machine with NICs
We recommend that you download and install the most recent version of the Admsnap
Utility software from the Downloads section of the VNX Series support by product page on
the EMC Online Support website.
Procedure
1. Log in as the administrator or as someone who has administrative privileges.
2. If admsnap is already installed, remove it.
The installation program will not let you install admsnap over an existing revision.
3. Download the software:
a. From the EMC Online Support website, select the VNX Series Support by Product
page and select Downloads.
b. Select the Admsnap Utility version you want to download and select the option to
save the zip file to your server.
c. Double-click the following executable file to start the installation wizard:
Windows Server 2012 - admsnap-Win2012-32-en_US-versionbuild.exe
where version and build are the version number and the build number of the
software.
4. Follow the instructions on the installation screens to install the Admsnap Utility.
5. When the installation is complete, click Finish to exit the wizard.
18
If you have a Windows virtual machine, for a complete configuration report, run the server
utility from the Windows Hyper-V server.
If you have this information, go to Verifying a server's configuration with E-Lab Navigator.
If you do not have this information, you can generate a server configuration report for
your server using the Unisphere Server Utility.
Start > Programs > EMC > Unisphere > Unisphere Server Utility or Start > All Programs
> EMC > Unisphere > Unisphere Server Utility
For Windows Server 2012, mouse over to the bottom corner of the taskbar and
click Start, then right-click the Desktop > All Apps > EMC > Unisphere > Unisphere
Server Utility
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.
This option detects if PowerPath or some other failover software, such as DMP, is
running. After the verification, the utility generates a summary report and saves it to
the server.
2. In the summary report, select the Checklist tab to view the information about the
server that you need to compare with the E-Lab Navigator information.
19
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.
Note
If you added virtual ports for a system iSCSI data port, when you set up your host
initiators to access the iSCSI data port, the system target is the virtual port and not the
physical port. In other words, the target is either the physical iSCSI data port or a virtual
port on the physical iSCSI data port.
Note
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.
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. 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
20
are in standby mode. If you leave the Server Network Adapter IP option set to
Default and a NIC fails, the server uses 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.
Note
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.
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.
Note
Network Interfaces (NICs) window This window displays if all of the following
statements are true:
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.
Server registration window This window displays and lists all connected
systems if the above conditions are not true.
Configuring NIC initiators on a Windows server or Windows iSCSI virtual machine to connect to the iSCSI targets without iSNS
21
Note
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 utilitys 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.
10.In the server registration window, click Next to send the updated information to the
system.
Note
If you have the host agent installed on the server, you get an error message indicating
that the host agent is running and you cannot use the server utility to update
information to the system; the host agent does this automatically.
A success message is displayed.
11.Click Finish to close the wizard.
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.
Procedure
1. Open QLogic SANsurfer as described in the QLogic documentation.
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.
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.
Note
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:
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.
h. Select Config Parameters.
i. 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.
23
Procedure
1. From Unisphere, select All Systems > System List.
2. From the Systems page, right-click the entry for the system for which you want to
establish an iSNS connection.
3. Select iSCSI > iSNS.
4. In iSNS Servers dialog box, enter the IP address of an iSNS server on the IP network
that you want the system to communicate with, and click Add.
Unisphere displays a confirmation dialog asking if you want to continue with the add
operation.
5. In the confirmation dialog box, click Yes to continue with the add operation.
Unisphere establishes and tests the validity of the connection, registers the system's
iSCSI port information with the iSNS server, and displays a success or error
confirmation dialog box when the operation completes. The error message includes a
brief reason for the connection failure.
Note
If the software is unable to establish and validate the connection, you can still add the
server to the configuration, and then test the connection after you repair the error.
6. Click OK to close the confirmation dialog box.
7. Select the server that you want to be the primary server and click Set Primary for a
primary server.
Note
If there is only one iSNS server, that server is the primary server by default. In this
case, there are no backup servers.
8. To test the connection from the system to the iSNS server, select the server and click
Test Connection.
Note
If you added virtual ports for a system iSCSI data port, when you set up your host
initiators to access the iSCSI data port, the system target is the virtual port and not the
physical port. In other words, the target is either the physical iSCSI data port or a virtual
port on the physical iSCSI data port.
24
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.
If you configure your system iSCSI connections to your Windows virtual machine with
NICs, start the server utility or host agent on the virtual machine. If you configure your
system connection to your Hyper-V or ESX 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 Server Utility on each server connected to the system to register the
server's NICs or iSCSI HBAs with the system.
Configuring iSCSI HBA initiators on a Windows server to connect to the system iSCSI targets with iSNS
25
Start > Programs > EMC > Unisphere > Unisphere Server Utility or Start > All Programs
> EMC > Unisphere > Unisphere Server Utility
For Windows Server 2012, mouse over to the bottom corner of the taskbar and
click Start, then right-click the Desktop > All Apps > EMC > Unisphere > Unisphere
Server Utility
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
Procedure
1. If the host agent is running, stop the host agent service.
2. In the Unisphere Server Utility dialog box, select Register this server to all connected
systems.
The utility automatically scans for all connected systems and lists them under
connected systems.
3. 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.
Note
If the Unisphere Server Utility does not list your storage processors, verify that your
server is properly connected and zoned to the system ports.
4. 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.
5. Click Finish to exit the utility.
6. If you stopped the host agent, restart it.
26
When a system experiences heavy input/output traffic (that is, applications are using the
system), information may not be reported to the host agent in a timely manner, resulting
in the host agent taking several minutes to execute a system management task. This
behavior is most evident when one host agent is managing multiple systems. Also, if the
SP event log is large and the host agent configuration file is set up to read all events, it
may take a few minutes for the host agent to start.
Procedure
1. Log in as the administrator or the equivalent.
2. Open the Services pane.
a. For Windows 2008 and earlier versions, from the desktop, right-click My Computer
and select Manage > Services and Applications > Services; or for Windows 2012,
from the desktop, mouse over to the left bottom corner of the taskbar and select
Start, then right-click Computer > Manager > Tools > Services.
This section describes how to start and stop the host agent service. This section
also describes how to configure the system connected to the server.
Note
When a system experiences heavy input/output traffic (that is, applications are
using the system), information may not be reported to the host agent in a timely
manner, resulting in the host agent taking several minutes to execute a system
management task. This behavior is most evident when one host agent is managing
multiple systems. Also, if the SP event log is large and the host agent configuration
file is set up to read all events, it may take a few minutes for the host agent to
start.
The Services pane opens.
3. In the Services pane, right-click Navisphere Agent and select Start.
4. If you want the host agent to start automatically at system startup:
a. Right-click Navisphere Agent and select Properties.
The Navisphere Agent Properties dialog box opens.
b. Select the General tab.
c. In Startup Type, select Automatic.
5. Close the Services pane.
Results
The host agent now start automatically at system startup.
It may take a few minutes for the host agent to start when:
Starting the Unisphere Host Agent
27
The SP event log is large and the host agent configuration file is not set up.
The SP event log is large and the host agent configuration file is not set up.
Procedure
1. If you do not have the Unisphere Service Manager running:
a. Download and install the Unisphere Service Manager from the EMC Online Support
website to a Windows management station that is connected to the system's
management ports. If you do not have a Windows management station, your
service provider can run this wizard.
b. Start the Unisphere Service Manager by doing one of the following:
Click the Unisphere Service Manager icon on your desktop,
or
Select Start > All Programs or Start > Programs, then select EMC > Unisphere >
Unisphere Service Manager > Unisphere Service Manager
2. Log in to your system.
3. From the System screen, select Diagnostics > Verify Storage System and follow the
instructions that appear.
4. Review the report that the wizard generates, and if it lists any problems, try to resolve
them.
Procedure
1. From Unisphere, select your system from the drop-down list.
2. Select the Hosts tab.
3. Under Wizards, select Failover Wizard.
4. In the Start Wizard dialog box, read the introduction, and then click Next.
5. In the Select Host dialog box, select the server you just connected to the system, and
click Next.
6. In the Select Storage Systems dialog box, select the system, and click Next.
7. In the Specify Settings dialog box, set the following values for the type of software
running on the server.
NOTICE
If you enter incorrect values the system could become unmanageable and
unreachable by the server, and the server's failover software could stop operating
correctly.
If you configured your system iSCSI connections to your Windows virtual machine with
NICs, set the system failover values for the virtual machine. If you configured your
system iSCSI connections to your Hyper-V or ESX server, set the system failover values
for the Hyper-V or ESX server. If you have a non-Windows virtual machine or a
Windows virtual machine with iSCSI HBAs, set the system failover values for the
Hyper-V or ESX server.
If you have a Hyper-V or ESX server, set the system failover values for the Hyper-V or
ESX server.
For a Windows server or Windows virtual machine with PowerPath, set:
l
Setting system failover values for the server initiators using Unisphere
29
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.
Start > Programs > EMC > Unisphere > Unisphere Server Utility or Start > All Programs
> EMC > Unisphere > Unisphere Server Utility
For Windows Server 2012, mouse over to the bottom corner of the taskbar and
click Start, then right-click the Desktop > All Apps > EMC > Unisphere > Unisphere
Server Utility
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.
some other failover software, such as DMP, is running. It does not detect native
failover software, such as Windows Server 2008 native failover.
6. Review and resolve any issues reported on the Issues tab of the generated report.
Starting Unisphere
Procedure
1. Log in to a host (which can be a server) that is connected through a network to the
systems management ports and that has an Internet browser: Microsoft Internet
Explorer, Netscape, or Mozilla.
2. Start the browser.
3. In the browser window, enter the IP address of one of the following that is in the same
domain as the systems that you want to manage:
l
A system SP with the most recent version of the VNX Operating Environment (OE)
installed
Note
A Unisphere management station with the most recent Unisphere Server and UIs
installed
Note
If you do not have a supported version of the JRE installed, you will be directed to the
Sun website where you can select a supported version to download. For information
on the supported JRE versions for your version of Unisphere, refer to Environment and
System Requirements in the Unisphere release notes on the EMC Online Support
website.
4. Enter your user name and password.
5. Select Use LDAP if you are using an LDAP-based directory server to authenticate user
credentials.
If you select the Use LDAP option, do not include the domain name.
When you select the LDAP option, the username / password entries are mapped to an
external LDAP or Active Directory server for authentication. Username / password
pairs whose roles are not mapped to the external directory will be denied access. If
the user credentials are valid, Unisphere stores them as the default credentials.
6. Select Options to specify the scope of the systems to be managed.
Global (default) indicates that all systems in the domain and any remote domains can
be managed. Local indicates that only the targeted system can be managed.
7. Click Login.
When the user credentials are successfully authenticated, Unisphere stores them as
the default credentials and the specified system is added to the list of managed
systems in the Local domain.
Configuring your VNX system
31
Committing VNX for Block Operating Environment (OE) software with Unisphere
If you did not install a VNX for Block OE update on the system, you need to commit the
VNX for Block OE software now.
Procedure
1. From Unisphere, select All Systems > System List.
2. From the Systems page, right-click the entry for the system for which you want commit
the VNX for Block OE and select Properties.
3. Click the Software tab, select VNX-Block-Operating-Environment, and click Commit.
4. Click Apply.
Click OK to create the new Storage Group and close the dialog box, or
Click Apply to create the new Storage Group without closing the dialog box. This
allows you to create additional Storage Groups.
6. Select the storage group you just created and click the Connect hosts.
32
7. Move the host from Available host to Host to be connected and click OK.
Making LUNs visible to a Windows server or Windows virtual machine with NICs
Note
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 LUNs that you created, use Windows Computer
Management to perform a rescan:
Procedure
1. Open the Computer Management window).
2. Under the Storage tree, select Disk Management.
3. From the tool bar menu, select Action > Rescan Disks.
Verifying that PowerPath for Windows servers or Windows virtual machines sees all
paths to the LUNs
Procedure
1. On the server, configure PowerPath:
powermt config
2. On the Windows taskbar, either double-click the PowerPath Administrator icon or
right-click the icon and select PowerPath Administrator.
3. In the results pane, verify that the path metric for each LUN isn/n where n is the total
number of paths to the LUN.
If you configured your system connections to your Windows virtual 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.
Making LUNs visible to a Windows server or Windows virtual machine with NICs
33
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 LUNs to receive data. If you prepare disks to receive data before
you set up and enable CHAP security, you lose access to the LUNs. While you are setting
up and enabling CHAP, you may temporarily lose connectivity between the server and
the system.
CHAP has the following variants:
u
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.
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.
34
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.
On each server using NICs that will connect to 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 using 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.
Note
When you remove an iSCSI target, the specified target and all other targets on the system
are removed. If you want to remove a specific target on the system, you must use the
Microsoft Software Initiator.
Procedure
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.
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 you are setting up and enabling CHAP, you may
temporarily lose connectivity between the server and the system.
Configure CHAP security on the system with Unisphere.
35
2. From the Systems page, select the system for which you want to configure CHAP.
3. Under iSCSI Management, select CHAP Management.
4. In the CHAP Management dialog box, click Add.
The Add CHAP Credentials dialog box opens.
5. In Defined For, select Target.
6. Enter the CHAP username for the system.
To avoid potential confusion, we recommend that you use the default username
supplied by the system.
7. Enter the CHAP secret for the system.
Note
If you enter the secret in hexadecimal, you must select CHAP Secret Specified in HEX.
8. Click Apply to save the CHAP credentials.
9. Click Yes, and then OK and click OK again.
Note
If you click Cancel to close the iSCSI CHAP Management dialog box and you did not
click Apply after entering new information, the new information is not saved.
10.Click Cancel to close the dialog box and return to the iSCSI Management dialog box.
If you enter the secret in hexadecimal, you must select CHAP Secret Specified in HEX.
36
If you click Cancel to close the iSCSI CHAP Management dialog box and you did not
click Apply after entering new information, the new information is not saved.
10.Click Cancel to close the dialog box and return to the iSCSI Management dialog box.
Windows server with NICs You must enable CHAP security on the system before you
can configure CHAP for the NICs. While you are setting up and enabling CHAP, you may
temporarily lose connectivity between the server and the system.
After entering CHAP data on the target, you must enter the same data on each NIC
initiator. 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.
To configure initiator CHAP for NIC initiators:
Procedure
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:
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.
Note
If CHAP authentication is enabled on all target ports on a system, you 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.
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. In this window:
a. Enter the CHAP security information (username and secret).
Configuring initiator CHAP on a Windows server or Windows virtual machine with NIC initiators
37
b. If you have mutual CHAP configured on the system and on this server, check
Mutual CHAP.
c. Click OK.
The utility scans for iSCSI target ports and displays the IP address for each target it
discovers.
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 continues 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 uses 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.
Note
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.
9. Click Logon to connect to the selected target.
If CHAP authentication is enabled on the target, a CHAP login dialog box is displayed.
In this window:
a. Enter the CHAP security information (username and secret).
b. If you have mutual CHAP configured on both the system and the server, check
Mutual CHAP if you want the initiator to authenticate the target.
c. Click OK.
Note
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 6 on page 38 9 on page 38 for each target to which you want to log in.
11.Click Next.
The server registration window opens and lists all connected systems.
12.In the server registration window, click Next to send the updated nformation to the
system.
A success message will be displayed.
38
Note
If you have the host agent installed on the server, you get an error message indicating
that the host agent is running and you cannot use the server utility to update
information to the system; the host agent does this automatically.
13.Click Finish to close the wizard.
Results
You have set and enabled initiator security on the server and system.
Windows server with NICs You must enable CHAP security on the system before you
can configure CHAP for the NICs. While you are setting up and enabling CHAP, you may
temporarily lose connectivity between the server and the system.
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.
Procedure
1. On the server, open the Unisphere Server Utility
2. Select Configure iSCSI Connections on this server and click Next.
3. If you are setting up mutual CHAP, follow the steps below, and If you are not setting up
mutual CHAP, go to step 4 on page 39.
a. Select Configure Mutual CHAP and click Next.
b. In the Mutual CHAP Authentication window, enter the mutual CHAP secret
(password).
NOTICE
If you have already configured mutual CHAP on the system, enter the same secret.
You entered this mutual CHAP secret in the Add Initiator CHAP Credentials Advanced page.
c. Click Next.
d. Click Finish in the success window.
4. Select Configure iSCSI Connections and click Next.
5. In the iSCSI Targets and Connections window, select one of the following options to
discover the iSCSI target ports on the connected systems:
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.
Configuring mutual (target) CHAP on a Windows server or Windows virtual machine with NIC initiators
39
Note
If CHAP authentication is enabled on all target ports on a system, you 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.
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. In this window:
a. Enter the CHAP security information (username and secret).
b. If you have mutual CHAP configured on the system and the server and you want the
initiator to authenticate the target, check Mutual CHAP.
c. 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.
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.
Note
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.
10.Click Logon to connect to the selected target.
If CHAP authentication is enabled on the target, a CHAP login popup dialog box is
displayed. In this dialog box:
a. Enter the CHAP security information (username and secret).
40
b. If you have mutual CHAP configured on the system and the server, check Mutual
CHAP if you want the initiator to authenticate the target.
c. Click OK.
Note
If you are running PowerPath 4.6 or later, the Unisphere Server Utility automatically
enables multipath when logging in to the target.
11.Repeat 7 on page 40 10 on page 40 for each target you want to log in to.
12.Click Next.
The server registration window opens and lists all connected systems.
13.In the server registration window, click Next to send the updated nformation to the
system.
A success message is displayed.
Note
If you have the host agent installed on the server, you get an error message indicating
that the host agent is running and you cannot use the server utility to update
information to the system; the host agent does this automatically.
14.Click Finish to close the wizard.
Results
You have completed the setup and enabling of mutual (target) security on the server and
system.
41
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 LUNs to receive data. If you prepare disks to receive data before
you set up and enable CHAP security, you lose access to the LUNs. While you are setting
up and enabling CHAP, you may temporarily lose connectivity between the server and
the system.
CHAP has the following variants:
u
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.
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.
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 send this data
to the target and the target uses this data to authenticated 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.
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.
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.
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.
42
Note
The SANsurfer diagnostic read / write buffer test is not supported on EMC systems.
Configure initiator CHAP on each iSCSI HBA that communicates with the server:
Procedure
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.
4. Select the Target Settings tab.
5. Click Config Authentication on the bottom of the pane.
Note
Configuring mutual (target) CHAP on a Windows server with iSCSI HBA initiators
Before you begin
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.
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.
Configuring mutual (target) CHAP on a Windows server with iSCSI HBA initiators
43
Note
The SANsurfer diagnostic read/write buffer test is not supported on EMC systems.
Procedure
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.
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 target CHAP username
that you entered on the system.
b. In the Target Secret column, enter the target> 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).
Results
You have set up mutual CHAP security on the server.
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 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
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.
CHAP authentication for a system, a server authenticates the system iSCSI data ports
when they log in to the servers initiators.
To configure initiator CHAP:
Procedure
1. From Unisphere, select All Systems > System List.
2. From the Systems page, select the system for which you want to configure CHAP.
3. Under iSCSI Management, select CHAP Management.
4. In the CHAP Management dialog box, click Add.
The Add CHAP Credentials dialog box opens.
5. In Defined For, select Target.
6. Enter the CHAP username for the system.
To avoid potential confusion, we recommend that you use the default username
supplied by the system.
7. Enter the CHAP secret for the system.
Note
If you enter the secret in hexadecimal, you must select CHAP Secret Specified in HEX.
8. Click Apply to save the CHAP credentials.
9. Click Yes, and then OK and click OK again.
Note
If you click Cancel to close the iSCSI CHAP Management dialog box and you did not
click Apply after entering new information, the new information is not saved.
10.Click Cancel to close the dialog box and return to the iSCSI Management dialog box.
45
If you enter the secret in hexadecimal, you must select CHAP Secret Specified in HEX.
8. Click Apply to save the CHAP credentials.
9. Click Yes, and then OK and click OK again.
Note
If you click Cancel to close the iSCSI CHAP Management dialog box and you did not
click Apply after entering new information, the new information is not saved.
10.Click Cancel to close the dialog box and return to the iSCSI Management dialog box.
Use Unisphere to verify that each new LUN is initialized and to write a signature to it,
as described in the Unisphere online help.
Before a virtual machine can send data to a virtual disk that is a VMFS volume, you must
do the following:
Windows virtual machine
1. Write a signature to the VMware virtual disk.
2. Either create partitions on a basic disk or create volumes on a dynamic disk.
46
NOTICE
If you configured your system connections to your Windows virtual 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.
For Windows 2008 and earlier versions, from the desktop, right-click My Computer
and select Manage > Services and Applications > Services; or for Windows 2012,
from the desktop, mouse over to the left bottom corner of the taskbar and select
Start, then right-click Computer > Manager > Tools > Services.
From the desktop, right-click My Computer and select Manage > Services and
Applications > Services
or
Select Start > Administrative Tools > Computer Management > Services and
Applications > Services.
47
The SP event log is large and the host agent configuration file is not set up.
From the desktop, right-click My Computer and select Manage > Services and
Applications > Services.
or
Select Start > Administrative Tools > Computer Management > Services and
Applications > Services.
The SP event log is large and the host agent configuration file is not set up.
Verifying that the system received the LUN information using Unisphere
Procedure
1. From Unisphere, select your system.
2. Select Hosts > Hosts List.
3. Select a host and then, on the Details page, click the LUNs tab.
4. Verify that the LUNs tab displays a physical drive and logical drive name for each LUN
on the host.
48
Note
You can download an I/O simulator (Iometer) for writing data to the system from the
following website: http://www.iometer.org
If you configured your system connections to your Windows virtual 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.
Procedure
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.
This icon may be under your hidden icons.>
3. On the left pane (summary pane), expand the EMC PowerPath Admin or EMC
PowerPath Administrator option.
4. Under the Path Management option, select Disks.
For each disk, the Path Status and the Path Metric columns give the status of the
paths to the disk. When all n paths to a disk are working, the Path Status for the disk
is optimal and the Path Metric for the disk is n/n, indicating that n of n paths are
working. If only m paths are working, the path metric is m/n.
5. Verify that all n paths to the disks in the 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 LUN>.
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.
Verifying your failover configuration with PowerPath for a Windows server or Windows virtual machine
49
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.
50
51