iSCSI Network W2k8

download iSCSI Network W2k8

of 86

Transcript of iSCSI Network W2k8

  • 8/13/2019 iSCSI Network W2k8

    1/86

    Here is Your Customized Document

    Your Configuration is:

    Attaching a server in a Block configuration

    Model - VNX5300

    Storage Type - VNX for Block (SAN)

    Connection Type - iSCSI Network

    Server Operating System - Windows Server 2008

    Path Management Software - PowerPath

    Document ID - 1342619800062

    Reporting Problems

    To send comments or report errors regarding this document,

    please email: [email protected].

    For Issues not related to this document, contact your service provider.

    Refer to Document ID:

    1342619800062

    Content Creation Date July 18, 2012

  • 8/13/2019 iSCSI Network W2k8

    2/86

    This document explains how to attach a Microsoft Windows Server 2008 Server with EMC

    PowerPath to a VNX5300 in an iSCSI network configuration.

    Important: This document uses the termsystemto refer to your VNX.

    If you are an EMC partner, refer to the EMC Services Partner website to download the Unisphere

    server software mentioned in this guide. The partner site is available from the Navigator drop-down

    menu onPowerlink.

    Important: 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.

    The main topics in this document are:

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

    Installing NICs or iSCSI HBAs in the server.............................................................................................6

    Installing or updating the NIC or iSCSI HBA driver...................................................................................8

    Starting the iSCSI service.........................................................................................................................9

    Assigning an IP address to a NIC or iSCSI HBA....................................................................................10Installing or Updating PowerPath software.............................................................................................12

    Installing Unisphere server software.......................................................................................................13

    Connecting the VNX to a server in an iSCSI network configuration.......................................................28

    Determining if your server has a supported configuration......................................................................33

    Configuring iSCSI initiators for a configuration without iSNS.................................................................35

    Configuring the iSNS client on the system..............................................................................................40

    Configuring iSCSI initiators for a configuration with iSNS......................................................................42

    Configuring NIC initiators on a Windows server or Windows virtual machine to connect to the system

    iSCSI targets with iSNS..........................................................................................................................43

    EMC

    Attaching a Microsoft Windows Server 2008

    Server with EMC PowerPath to a VNX5300 in

    an iSCSI Network Configuration

    http://powerlink.emc.com/http://powerlink.emc.com/
  • 8/13/2019 iSCSI Network W2k8

    3/86

    Configuring iSCSI HBA initiators on a Windows server to connect to the system iSCSI targets with

    iSNS........................................................................................................................................................46

    Registering the server with the system...................................................................................................47

    Verifying system health...........................................................................................................................51

    Setting system failover values for the server initiators using Unisphere.................................................52

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

    Configuring your VNX system.................................................................................................................56

    Configuring optional CHAP security for Windows servers or Windows virtual machines with NICs.......63

    Configuring optional CHAP security for iSCSI HBA initiators ................................................................73Preparing LUNs to receive data..............................................................................................................79

    Sending Windows server and Windows virtual machine disk information to the system........................80

    Verifying your failover configuration with PowerPath..............................................................................84

  • 8/13/2019 iSCSI Network W2k8

    4/86

    Before you start

    Read the release notes for your system, which are available on theEMC 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.

    The network configuration information, including the IP address and network mask,

    for any NICs or iSCSI HBAs that you are installing.

    Optional iSNS server information.

    You must have a supported Windows host on the same network as the system

    management ports. You can use this host:

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

    referred to as the Navisphere management station.

    To run the Unisphere Service Manager, which runs only on a Windows host.

    As an EMC Secure Remote Support (ESRS) IP Client, which must be a Windows

    host, but cannot be a server (that is, it cannot send I/O to the system data ports).

    You must have a Unisphere Server with a supported Internet browser that is on the same

    network as the system management ports. The Unisphere Server replaces the Navisphere

    Management Server. This host can also be the server or a Unisphere management

    station (formerly referred to as the Navisphere off-array management station). For

    supported Internet browsers, see the Unisphere release notes on the EMC Online Support

    website.

    You must have an , a supported Windows 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.

    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 switchesto the NICs or iSCSI HBAs in the server. We strongly recommend you use OM3 50

    m cables.

    4 Attaching a server

    Before you start

    http://support.emc.com/http://support.emc.com/http://support.emc.com/http://support.emc.com/http://support.emc.com/http://support.emc.com/http://support.emc.com/http://support.emc.com/
  • 8/13/2019 iSCSI Network W2k8

    5/86

    Note: 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 system, each NIC

    or iSCSI HBA initiator port can be on a separate subnet or on the same subnet.

    For cable specifications, refer to the system's Technical Specifications. You can generate

    this user customized document from the learn link on the system support website

    (http://www.emc.com/vnxsupport).

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

    Before you start 5

    Before you start

    http://www.emc.com/vnxsupporthttp://www.iometer.org/http://www.iometer.org/http://www.emc.com/vnxsupport
  • 8/13/2019 iSCSI Network W2k8

    6/86

    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 E-Lab

    Interoperability Navigator on theEMC Online Support website.

    Note: We recommend that you never mix NICs or iSCSI HBAs from different vendors in the sameserver.

    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:

    Store NICs or iSCSI HBAs in antistatic bags.

    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.

    1. If the server is powered up:

    a. Shut down the server's operating system.

    b. Power down the server.

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

    2. Put on an ESD wristband, and clip its lead to bare metal on 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.

    6 Attaching a server

    Installing NICs or iSCSI HBAs in the server

    http://support.emc.com/http://support.emc.com/
  • 8/13/2019 iSCSI Network W2k8

    7/86

    b. Install the NIC or iSCSI HBA following the instructions provided by the NIC or iSCSI

    HBA vendor.

    c. If you installed a replacement NIC or iSCSI HBA, reconnect the cables that you

    removed in the exact same way as they were connected to the original NIC or iSCSI

    HBA.

    4. Plug the server's power cord into the power outlet, and power up the server.

    Installing NICs or iSCSI HBAs in the server 7

    Installing NICs or iSCSI HBAs in the server

  • 8/13/2019 iSCSI Network W2k8

    8/86

  • 8/13/2019 iSCSI Network W2k8

    9/86

    Starting the iSCSI service

    Important: 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 2008 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.

    1. From the server, clickStart All Programs Administrative Tools iSCSI Initiator.

    2. In theMicrosoft iSCSIdialog box, clickYes 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.

    Starting the iSCSI service 9

    Starting the iSCSI service

  • 8/13/2019 iSCSI Network W2k8

    10/86

    Assigning an IP address to a NIC or iSCSI HBA

    Assign an IP address to each NIC or iSCSI HBA in the server or virtual machine that will be

    connected to the system.

    Important: 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.

    Assigning an IP address to a NIC in a Windows Server 2008 host or virtualmachine

    If the IP addresses for the NICs within the server or virtual machine are not assigned

    dynamically (DHCP), you must manually assign them using the following procedure. Open

    the appropriate Microsoft networking tool provided with the operating system.

    1. SelectStart Server Manager.

    2. In theServer Managerscreen, select theView Network Connectionstab.

    3. Identify the NIC for which you want to set the IP address, right-click the NIC and select

    Properties.

    4. In theNetworkingtab, verify that IPV6 is not selected.

    5. Highlight theIPV4option and click Properties.

    6. In theGeneraltab, selectUse the following IP address.

    7. Enter an IP address for each NIC that you want to use.

    8. ClickOK and close all open dialog boxes.

    Assigning an IP address to a QLogic iSCSI HBA in a Windows server

    1. Open QLogic SANsurfer as described in the QLogic documentation.

    10 Attaching a server

    Assigning an IP address to a NIC or iSCSI HBA

  • 8/13/2019 iSCSI Network W2k8

    11/86

    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 initiatorsettings and optional CHAP security settings as the HBA it replaced.

    Assigning an IP address to a NIC or iSCSI HBA 11

    Assigning an IP address to a NIC or iSCSI HBA

  • 8/13/2019 iSCSI Network W2k8

    12/86

    Installing or Updating PowerPath software

    Important:

    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

    Guidefor your operating system. This guide is available on the EMC Online Support website.

    Check the PowerPath software download section on the EMC Online Support websitefor

    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 Guidefor your operating system. This guide is available on

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

    12 Attaching a server

    Installing or Updating PowerPath software

    http://support.emc.com/http://support.emc.com/http://support.emc.com/http://support.emc.com/http://support.emc.com/http://support.emc.com/
  • 8/13/2019 iSCSI Network W2k8

    13/86

    Installing Unisphere server software

    This section describes how to install Unisphere server software.

    Important: You must install the host agent or server utility on your Hyper-V or ESX server if you:

    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.

    If you plan to install Navisphere CLI, Admhost, or Admsnap, you must install them on avirtual machine. For instructions on installing these software programs on a virtual machine

    other than Windows Server 2008, generate a new document and select the operating system

    running on the virtual machine.

    Before you begin

    Refer to the sections below to determine which application to install for host registration

    and the requirements for installing each of these applications.

    To run Unisphere server software, your server must meet the requirements outlined

    inRequirements for Unisphere server software on page 14.

    To determine whether to install the Unisphere Host Agent or Unisphere Server Utilityto register your NICs or iSCSI HBAs with the system, refer to Determining whether

    to install the Unisphere Host Agent on page 14.

    Installing Unisphere server software

    Depending on which Unisphere server software you are installing, refer to the appropriate

    section below.

    Unisphere Host Agent seeInstalling the Unisphere Host Agent on page 15.

    Unisphere Server Utility seeInstalling the Unisphere Server Utility on page 23.

    Navisphere CLI seeInstalling Navisphere Secure CLI on page 24.

    Admhost Utility seeInstalling the Admhost Utility on page 26.

    Admsnap Utility seeInstalling the Admsnap Utility on page 27.

    Installing Unisphere server software 13

    Installing Unisphere server software

  • 8/13/2019 iSCSI Network W2k8

    14/86

    Requirements for Unisphere server software

    To run Unisphere server software, your server must meet the following requirements:

    Run a supported version of the Windows operating system.

    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.

    Have a configured TCP/IP network connection to any remote hosts that you will use to

    manage the systems, including: any server whose browser you will use to access Unisphere,

    a supported Windows server running Unisphere Server software (replaces the

    Navisphere Management Server software),

    any AIX, HP-UX, Linux, VMware ESX Server, 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.

    Note: 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 theEMC Online Support website.

    Determining whether to install the Unisphere Host Agent

    Depending on your application needs, you can install the host agent to:

    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 Symmetrix

    systems.

    Register the servers NICs or iSCSI HBAs with the system.

    14 Attaching a server

    Installing Unisphere server software

    http://support.emc.com/http://support.emc.com/
  • 8/13/2019 iSCSI Network W2k8

    15/86

    Alternatively, you can use the Unisphere Server Utility to register the servers NICs or

    iSCSI HBAs with the system.Table 1 on page 15describes the host registration

    differences between the host agent and the server utility.

    Table 1. Host registration differences between the host agent and the server utility

    Unisphere Server UtilityUnisphere Host AgentFunction

    No LUN mapping information is not sent

    to the system. Only the servers name, ID,

    and IP address are sent to the system.

    Yes LUN mapping informa-

    tion is displayed in the Uni-

    sphere UI next to the LUN icon

    Pushes LUN mapping

    and OS information to

    the system.

    or with the CLI using the lun-

    mapinfo command.Note: The text Manually Registered ap-

    pears next to the hostname icon in the

    Unisphere UI indicating that the host agent

    was not used to register this server.

    Yes You can control whether server in-

    formation is automatically sent to the sys-

    tem by enabling or disabling the registra-

    tion service feature. This feature is auto-

    matically enabled during the installation

    of the server utility, but you can stop the

    service at any time through the services

    option in the Microsoft user interface. Note

    that only the servers name, ID, and IP

    address are sent to the system; LUN

    mapping information is not sent.

    Yes No user interaction is

    required.

    Runs automatically to

    send information to the

    system.

    No LUN mapping information is not sent

    to the system. Note that if you are usingthe server utility to upload a high-availabil-

    ity report to the system, you must have

    network connectivity.

    Yes Network connectivity al-

    lows LUN mapping informationto be available to the system.

    Requires network connec-

    tivity to the system.

    Installing the Unisphere Host Agent

    This section describes how to install the Unisphere Host Agent.

    To modify an existing host agent configuration, refer to the next section.

    Installing the Unisphere Host Agent on a Windows server or a Windows virtual machine withNICs

    We recommend that you download and install the most recent version of the Unisphere Host

    Agent software from theEMC Online Support website.

    1. Log in as the administrator or a user who has administrative privileges.

    Installing the Unisphere Host Agent 15

    Installing Unisphere server software

    http://support.emc.com/http://support.emc.com/
  • 8/13/2019 iSCSI Network W2k8

    16/86

    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 theEMC Online Support website, select theVNX 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

    whereversionand buildare 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 (32bit) or C:\Program Files (x86)\EMC\HostAgent (64bit).

    Once the Unisphere Host Agent installation is complete, the Initialize Privileged User List

    dialog box is displayed.

    6. In theInitialize Privileged User Listdialog box, select Create/Overwrite Fileand browse to the

    agent.config file.perform one of the following:

    You will then need to add users to the Privileged User List (login names for this server).

    Only usernames listed in the Privileged User List can send CLI commands to the system.

    If theConfig Filefield 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 Browseto use a different file.

    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.

    If theConfig Filefield 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.

    16 Attaching a server

    Installing Unisphere server software

    http://support.emc.com/http://support.emc.com/
  • 8/13/2019 iSCSI Network W2k8

    17/86

    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. ClickAdd to open the Add Privileged Userdialog box.

    b. In theAdd Privileged Userdialog box, underUser Name, enter the persons account

    username, for example, Administrator.

    c. UnderSystem 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 clickRemove.

    9. ClickOK 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. ClickFinish.

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

    From the desktop, right-click My Computerand select Manage Services and

    Applications Services.

    or

    Installing Unisphere server software 17

    Installing Unisphere server software

  • 8/13/2019 iSCSI Network W2k8

    18/86

    SelectStart Administrative Tools Computer Management Services and

    Applications Services.

    TheServicespane opens.

    c. In theServicespane, right-click Unisphere Host Agentand select Stop.

    d. If asked to confirm your request to stop the agent service, clickYes, and close the

    Servicespane or dialog box.

    b. Move or copy the saved Navimon.cfg to the real Navimon.cfg file.

    c. Start the agent:

    a. At the Windows server, log in as the administrator or the equivalent.

    b. Open theServicespane.

    From the desktop, right-click My Computerand select Manage Services and

    Applications Services.

    or

    SelectStart Administrative Tools Computer Management Services and

    Applications Services.

    TheServicespane opens.

    c. In theServicespane, right-click Unisphere Host Agentand select Start.

    d. If you want the host agent to start automatically at system startup:

    i. Right-clickUnisphere Host Agentand select Properties.

    TheUnisphere Host Agent Propertiesdialog box opens.

    ii. Select theGeneraltab.

    iii. InStartup Type, selectAutomatic.

    The host agent will now start automatically at system startup.

    e. CloseComputer Management.

    It may take a few minutes for the host agent to start if either applications are using

    the system or the SP event log is large and the host agent configuration file is not

    set up.

    13. ClickDoneto exit the installation wizard.

    14. If you have a multihomed host (multiple NIC cards installed on the host), create an

    agentID.txt file, as described below, to ensure that the agent finds the correct NIC card.

    18 Attaching a server

    Installing Unisphere server software

  • 8/13/2019 iSCSI Network W2k8

    19/86

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

    Unisphere Host Agent on a multihomed host, the host agent, by default, binds to the first NIC in

    the host. If your host is multihomed, for the host agent to successfully register with the desiredEMC system, you need to configure the host agent to bind to a specific NIC. You do this by setting

    up anagentID.txtfile.

    a. Using a text editor that does not add special formatting, create a file named agentID.txt

    (case sensitive).

    Save this file by doing one of the following:

    Set theEV_AGENTID_DIRECTORYenvironmental variable to the location where

    you want to save the agentID.txt file.

    The Unisphere Host Agent will then look for the agentID.txt file in the location you

    specified.

    If you do not specify a location in the EV_AGENTID_DIRECTORYenvironmental

    variable, Unisphere Host Agent will look for the agentID.txt file in the location

    specified by the registry entry

    HKEY_LOCAL_MACHINE\SOFTWARE\EMC\Agent\1.0\ConfigPath. This location

    is usually C:\Program Files\emc\HostAgent.

    IfEV_AGENTID_DIRECTORYor

    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: TheagentID.txtfile should contain only these two lines, without any formatting. Thefirst 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, thecursor 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.

    Installing Unisphere server software 19

    Installing Unisphere server software

  • 8/13/2019 iSCSI Network W2k8

    20/86

    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 theAdd/Remove Programsdialog box.

    Running the Unisphere Host Agent

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

    connections.

    Starting the host agent on a Windows server or Windows virtual machine

    This section describes how to start the host agent service.

    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.

    1. Log in as the administrator or the equivalent.

    2. Open theServicespane.

    a. From the desktop, right-click My Computerand select Manage Services and Applications

    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 thesystem), 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.

    20 Attaching a server

    Installing Unisphere server software

  • 8/13/2019 iSCSI Network W2k8

    21/86

    or

    b. SelectStart Administrative Tools Computer Management Services and Applications

    Services.

    TheServicespane opens.

    3. In theServicespane, right-click Unisphere Agentand select Start.

    4. If you want the host agent to start automatically at system startup:

    a. Right-clickUnisphere Agentand select Properties.

    TheUnisphere Agent Propertiesdialog box opens.

    b. Select theGeneraltab.

    c. InStartup Type, selectAutomatic.

    5. Close theServicespane.

    The host agent nows start automatically at system startup.

    It may take a few minutes for the host agent to start when:

    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 server or Windows virtual machine

    1. Log in as the administrator or the equivalent.

    2. Open theServicespane.

    From the desktop, right-click My Computerand select Manage Services and Applications

    Services.

    or

    SelectStart Administrative Tools Computer Management Services and Applications

    Services.

    TheServicespane opens.

    3. In theServicespane, right-click Unisphere Agentand select Stop. If asked to confirm your

    request to stop the agent service, clickYes, and close theServicespane.

    Running the Unisphere Host Agent 21

    Installing Unisphere server software

  • 8/13/2019 iSCSI Network W2k8

    22/86

    Testing the host agent connections

    Before continuing, you should test the host agent connections as follows:

    1. Start the host agent as described inStarting the host agent on a Windows server or

    Windows virtual machine on page 48.

    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 [-ddevice]| -hhostnameport -list -hba

    Note: You cannot specify both the d switch and h switch.

    where

    [-ddevice] is the device name for the system (only supported with legacy systems).

    -hhostnameis the IP address of the SP.

    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:ACServer Name: siux134Server IP Address: 128.221.208.134HBA Model Description:

    HBA Vendor Description:HBA Device Driver Name:Information about each port of this HBA:SP Name: spaHBA Devicename: sp0Trusted: NOLogged In: YESSource ID: 1Defined: YESInitiator Type: 0Storage Group Name:Storage Group 134

    b. In the listing, 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.

    22 Attaching a server

    Installing Unisphere server software

  • 8/13/2019 iSCSI Network W2k8

    23/86

    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 on your server.

    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.

    1. Log in as the administrator or someone who has administrative privileges.

    2. Download the software:

    a. From theEMC Online Support website, select theVNX 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

    languageis either en_US, when only the English version is available, or loc, when the

    localized versions are available (including English).

    versionand buildare 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 createnew 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.

    Installing the Unisphere Server Utility 23

    Installing Unisphere server software

    http://support.emc.com/http://support.emc.com/http://support.emc.com/http://support.emc.com/http://support.emc.com/http://support.emc.com/
  • 8/13/2019 iSCSI Network W2k8

    24/86

    5. When the installation is complete, clickDoneto exit the wizard.

    Installing Navisphere Secure CLI

    This section describes how to install Navisphere Secure CLI.

    You can install Navisphere CLI on either the server or virtual machine.

    Installing Navisphere Secure CLI on a Windows server or a Windows virtual machine

    We recommend that you download and install the most recent version of the Navisphere

    Secure CLI software from the applicable support by product page on the EMC Online Support

    website.

    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 inTable 2 on page 24.

    These ports are used by Navisphere CLI. If these ports are not opened, the software will

    not function properly.

    Table 2. TCP/IP ports

    TCP/IP portsSoftware

    443, 2163Secure CLI

    4. Download the software:

    a. From theEMC Online Support website, select theVNX Series Support by Product page

    and select Downloads.

    b. Select the Navisphere Secure 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

    where:

    languageis eitheren_US, when only the English version is available, orloc, when the

    localized versions are available (including English).

    versionand buildare the version number and the build number of the software.

    24 Attaching a server

    Installing Unisphere server software

    http://support.emc.com/http://support.emc.com/http://support.emc.com/http://support.emc.com/
  • 8/13/2019 iSCSI Network W2k8

    25/86

    5. Follow the instructions on the installation screens to install the Navisphere Secure CLI.

    6. When the installation is complete, clickDoneto exit the wizard.

    If you selected the default destination folder, the software is installed in C:\ProgramFiles\EMC\Navisphere CLI(32bit) or C:\Program Files (x86)\EMC\Navisphere CLI (64bit).

    You have installed the Navisphere CLI software.

    7. Verify that Navisphere Secure CLI is installed using theAdd/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.

    Note: 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 Secure CLI on a multihomed host, by default, Navisphere Secure CLI binds to the firstNIC 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!

    where:

    destination is the subnet of the NIC being configured.

    subnet mask is the same subnet mask as the NIC being configured.

    gatewayis 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: Each route should appear on a single line.

    b. Close the console window.

    Installing Unisphere server software 25

    Installing Unisphere server software

  • 8/13/2019 iSCSI Network W2k8

    26/86

    Installing the Admhost Utility

    If you want to access LUNs that participate in SAN Copy sessions, install the Admhost Utility.

    Note: The Admhost Utility is supported on Microsoft Windows platforms only. For the supported

    Windows versions, see theAdmhost 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 theEMC Online Support website.

    Important:

    If you configured your system connections to your Windows virtual machine with NICs, install admhoston 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. If you have a Windows virtual machine with iSCSI HBAs, install admhost

    on the Hyper-V server.

    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 theEMC Online Support website, select theVNX Series Support by Product pageand 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, clickFinishto 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).

    26 Attaching a server

    Installing Unisphere server software

    http://support.emc.com/http://support.emc.com/http://support.emc.com/http://support.emc.com/
  • 8/13/2019 iSCSI Network W2k8

    27/86

    Installing the Admsnap Utility

    To access snapshots of LUNs in the system, install the Admsnap Utility.

    You can install admsnap on the server or on the virtual machine.

    Installation prerequisites

    Before you can install and use the Admsnap Utility, you must install SnapView on a

    supported system.

    For a list of supported systems, refer to the release notes for SnapView and admsnap.

    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 EMCOnline Support website.

    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 theEMC Online Support website, select theVNX 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 2008 -

    admsnap-Win2K8-32-en_US-version-build.exe

    whereversionand buildare 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, clickFinishto exit the wizard.

    If you selected the default destination folder, admsnap is installed in C:\Program

    Files\EMC\Unisphere Admsnap (32-bit) or C:\Program Files (x86)\EMC\Unisphere

    Admsnap (64-bit).

    Installing the Admsnap Utility 27

    Installing Unisphere server software

    http://support.emc.com/http://support.emc.com/http://support.emc.com/http://support.emc.com/http://support.emc.com/http://support.emc.com/
  • 8/13/2019 iSCSI Network W2k8

    28/86

    Connecting the VNX to a server in an iSCSI network configuration

    To connect your VNX to a server in an iSCSI network configuration, you need one Ethernet

    LAN cable or fibre optical cable for Ethernet transmission for each VNX iSCSI host port that

    you will connect to the network.

    Note: A VNX host port is also called a VNX front-end data port.

    For 1 gigabit transmission, you need CAT 5 Ethernet LAN cables for 10/100 transmission

    or CAT 6 cables. These cables can be up to 100 meters long.

    For 10 gigabit Ethernet transmission, you need fibre optical cables. We strongly recommend

    you use OM3 50 m cables for all optical connections.

    For cable specifications, refer to the Technical Specificationsfor your system. You can

    generate an up-to-date version of the these specification using the Learn about VNX link ontheVNX support websiteor theVNX Series Support by Product page on theEMC Online

    Support website.

    28 Attaching a server

    Connecting the VNX to a server in an iSCSI network configuration

    http://www.emc.com/vnxsupporthttp://support.emc.com/http://support.emc.com/http://support.emc.com/http://support.emc.com/http://www.emc.com/vnxsupport
  • 8/13/2019 iSCSI Network W2k8

    29/86

    Identifying VNX iSCSI host ports for server connections

    You can connect servers to any ports (0, 1, 2, 3) on the UltraFlex 1 GbE I/O modules or anyports (0, 1) on the UltraFlex 10 GbE iSCSI I/O modules in slots A0 and B0 or A1 and B1.

    Figure 1 on page 29shows the location of the I/O module slots.

    Figure 1. Slots for I/O modules with host ports in a VNX5300 (FC and iSCSI modules shown)

    iSCSI module labels

    Each 1 GbE I/O module has a 1 GbE iSCSI/TOE label on its handle. Each 10 GbE I/O

    module has a 10 GbE iSCSI label on its handle.

    iSCSI FE port connectivityBecause the 1 GbE iSCSI and 10 GbE iSCSI connection topologies are not interoperable,

    these modules cannot operate on the same physical network. The 1 Gb Ethernet iSCSI

    I/O module can auto-negotiate a 10 Mb/s or 100 Mb/s Ethernet. The 10 GbE iSCSI I/O

    module runs at a fixed 10 Gb/s rate.

    Handling optical cables

    Optical cables are susceptible to damage, so take the following precautions when handling

    them:

    Keep the covers on all optical cables until you are ready to insert them. Avoid tight bends. If you need to make a 90 bend, do it over 6 to 12 inches.

    Do not use optical cables to support weight (including their own unsupported weight if

    they are long).

    Identifying VNX iSCSI host ports for server connections 29

    Connecting the VNX to a server in an iSCSI network configuration

  • 8/13/2019 iSCSI Network W2k8

    30/86

  • 8/13/2019 iSCSI Network W2k8

    31/86

    Figure 4 on page 31orFigure 5 on page 32andFigure 6 on page 32for fibre optical or

    active twinaxial cables).

    Figure 2. Connecting an Ethernet cable

    Figure 3. Sample cabling for an iSCSI network configuration (1 GbE iSCSI and FC modules shown)

    Connecting the VNX to a server in an iSCSI network configuration 31

    Connecting the VNX to a server in an iSCSI network configuration

  • 8/13/2019 iSCSI Network W2k8

    32/86

    Figure 4. Connecting a fibre optical cable for Ethernet transmission

    Figure 5. Connecting an active twinaxial cable

    Figure 6. Sample cabling for an iSCSI network configuration (10 GbE iSCSI and FC modules

    shown)

    32 Attaching a server

    Connecting the VNX to a server in an iSCSI network configuration

  • 8/13/2019 iSCSI Network W2k8

    33/86

    Determining if your server has a supported configuration

    Before you can determine if your server has a supported configuration, you need to knowthe revision and patch level of the operating system on the server and the TCP/IP (TOE),

    firmware, and BIOS revisions for the servers NICs or iSCSI HBAs.

    Important: If you have a Windows virtual machine, for a complete configuration report, run the server

    utility from the Windows Hyper-V server.

    If you have this information, go to Verifying a server's configuration with E-Lab Interoperability

    Navigator on page 34. If you do not have this information, you can generate a server

    configuration report for your server using the Unisphere Server Utility.

    Starting the Unisphere Server Utility on a Windows server or a Windows virtual

    machine

    1. Run the Unisphere Server Utility by selectingStart Programs EMC Unisphere

    Unisphere Server UtilityorStart All Programs EMC Unisphere Unisphere Server Utility .

    2. Select your language, if the software prompts you for it.

    Note: 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 entercd C:\Program Files\EMC\Unisphere Server

    Utilityorcd C:\Program Files (x86)\EMC\Unisphere Server Utility, then enterServerUtilCLI.exe.

    Generating a high-availability report for a server

    1. In theUnisphere Server Utility dialog box, selectVerify Server High-Availabilityto generate a

    report of the servers environment.

    This option detects if PowerPath or some other failover software, such as DMP, is

    running. After the verification, the utility generates a summary report and saves it to the

    server.

    2. In the summary report, select theChecklisttab to view the information about the server

    that you need to compare with the E-Lab Interoperability Navigator information.

    Determining if your server has a supported configuration 33

    Determining if your server has a supported configuration

  • 8/13/2019 iSCSI Network W2k8

    34/86

    Verifying a server's configuration with E-Lab Interoperability Navigator

    1. From your web browser, go to theEMC Online Support websiteand log in.

    2. If required, register and create a username and password.

    3. SelectE-Lab Interoperability Navigatoron the EMC Online Support website from the Tools

    menu on the right-side of the home page.

    4. From theE-Lab Interoperability Navigatorpage, selectLaunch E-Lab Interoperability Navigator

    and then select the Solutions and Wizardstab.

    5. From the drop-down menu, select theCLARiiON Host Attach Wizard.

    6. For each step of the wizard, provide the requested information based on what is installedon the server or what you intend to install on the server.

    If the configuration you entered is invalid, an additional step appears in the wizard and

    aResults, EMC Support Statementspane appears on the right with information to help you

    provide the requested information in the additional step.

    If the configuration you entered is valid, aResultslink appears on the right.

    7. Click theResultslink appears to view a report that contains information about the

    configuration you entered.

    8. Print and/or save a copy of the report.

    9. Close the E-Lab Interoperability Navigator.

    10. Compare this report to either the information that you know about your server software

    or the checklist report you generated with the server utility.

    11. If your server software versions and/or patches or hot fixes are not listed in the Host

    Attach Wizard report, you must upgrade to a supported version or patch before continuing.

    Note: The Host Attach Wizard displays only options that EMC supports. If any of the configuration

    information on the server utility's high-availability report cannot be found in the wizard, then EMC

    does not support it.

    34 Attaching a server

    Determining if your server has a supported configuration

    http://support.emc.com/http://support.emc.com/
  • 8/13/2019 iSCSI Network W2k8

    35/86

    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.

    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.

    Configuring NIC initiators on a Windows server or Windows iSCSI virtual machineto 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. SelectConfigure iSCSI Connections on this serverand clickNext.

    3. SelectConfigure iSCSI Connections and clickNext.

    4. In the iSCSI Targets and Connections window, select one of the following options to discover

    the iSCSI target ports n 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 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. ClickNext.

    Configuring iSCSI initiators for a configuration without iSNS 35

    Configuring iSCSI initiators for a configuration without iSNS

  • 8/13/2019 iSCSI Network W2k8

    36/86

    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 (usernameand 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 clickNext.

    7. For each target you want to log in to:

    a. In theiSCSI Targetswindow, select the IP address of the Inactive target.

    b. UnderLogin Options, selectAlso 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.

    Note: If multiple NICs are on the same subnet and you leave the Server Network Adapter IPoption set to Default, only one NIC is actually used at a time. Other NICs are in standby mode.

    If you leave theServer 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 selectedAlso login to peer iSCSI target for High Availability (recommended) in the

    previous step, leave theServer 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. ClickLogonto 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 clickOK.

    36 Attaching a server

    Configuring iSCSI initiators for a configuration without iSNS

  • 8/13/2019 iSCSI Network W2k8

    37/86

    Note: 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 notclose the utility.

    8. ClickNext.

    One of the following windows displays:

    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 registrationwindow This window displays and lists all connected systems if

    the above conditions are not true.

    9. If theNetwork Interfaces (NICs)window displays:

    a. Uncheck any NICs that will be used for general network traffic and clickApply.

    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 immediatelyacknowledge 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. ClickOK and then Next.

    10. In the server registration window, click Next to send the updated information to the system.

    Configuring iSCSI initiators for a configuration without iSNS 37

    Configuring iSCSI initiators for a configuration without iSNS

  • 8/13/2019 iSCSI Network W2k8

    38/86

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

    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 theTarget Settings tab.

    c. On theTarget Settingspage, click the green plus (+) sign and enter the IP address forthe iSCSI port on your system, and clickOK.

    Note: The state for the port is No Connection Active.

    d. SelectAuto Discover Targets.

    e. ClickSaveand 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 theSecurity Checkwindow, 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.

    38 Attaching a server

    Configuring iSCSI initiators for a configuration without iSNS

  • 8/13/2019 iSCSI Network W2k8

    39/86

    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, clickSave.

    c. At the prompt to refresh the information for the server, clickYes.

    h. SelectConfig 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. ClickSaveand Yes.

    l. In theSecurity Checkwindow, enter your password and click OK.

    The HBA performs an iSCSI discovery. Once finished, SANsurfer displays all targets

    on the system.

    Configuring iSCSI initiators for a configuration without iSNS 39

    Configuring iSCSI initiators for a configuration without iSNS

  • 8/13/2019 iSCSI Network W2k8

    40/86

    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.

    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 system's iSNS configuration, Unisphere establishes a connection from the system to

    the iSNS server, and then registers the information stored on the system with the iSNS

    server.

    Use Unisphere to configure the iSNS client on the system.

    Configuring the iSNS client with Unisphere

    For each iSNS server to which you want the system to connect:

    Note: Only one connection can be active at a time.

    1. From Unisphere, selectAll 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. SelectiSCSI iSNS.

    4. IniSNS Serversdialog 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 addoperation.

    5. In the confirmation dialog box, clickYes 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

    40 Attaching a server

    Configuring the iSNS client on the system

  • 8/13/2019 iSCSI Network W2k8

    41/86

    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. ClickOK 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: You can test only one server connection at a time.

    Unisphere displays an error or a success confirmation dialog box.

    9. ClickOK to close the confirmation dialog box and begin the test operation.

    Configuring the iSNS client on the system 41

    Configuring the iSNS client on the system

  • 8/13/2019 iSCSI Network W2k8

    42/86

    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.

    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.

    42 Attaching a server

    Configuring iSCSI initiators for a configuration with iSNS

  • 8/13/2019 iSCSI Network W2k8

    43/86

    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.

    1. On the server, open the Unisphere Server Utility.

    2. SelectConfigure iSCSI Connections on this serverand clickNext.

    3. SelectConfigure iSCSI Connections and clickNext.

    4. In theiSCSI Targets and Connections window, select Discover iSCSI targets using this iSNS

    serverto send a request to the iSNS server for all connected iSCSI system targets and

    clickNext.

    5. For each target you want to log in to:

    a. In theiSCSI Targetswindow, select the IP address of the Inactive target.

    b. UnderLogin Options, selectAlso 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 continues to the peer target if the target you selected above becomes unavailable.

    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 toDefaultand a NIC

    fails, the server uses one of the other NICs, even if they are on the same subnet, aslong as there is a network path from the system to the NIC that is in standby mode.

    c. If you selectedAlso login to peer iSCSI target for High Availability (recommended) in the

    previous step, leave theServer Network Adapter IP set toDefault.

    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.

    d. ClickLogonto connect to the selected target.

    If CHAP authentication is enabled on the target, a CHAP login pop-up dialog box is

    displayed.

    Configuring NICinitiators on a Windows serveror Windows virtual machine to connect to the 43

    system iSCSI targets with iSNS

    Configuring NIC initiators on a Windows server or Windows virtual machine to

    connect to the system iSCSI targets with iSNS

  • 8/13/2019 iSCSI Network W2k8

    44/86

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

    Note: 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.

    6. ClickNext.

    One of the following windows is displayed:

    Network Interfaces (NICs) window This window is displayed 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 registrationwindow This window is displayed and lists all connected systemsif the above conditions are not true.

    7. If theNetwork Interfaces (NICs)window is displayed:

    a. Uncheck any NICs that will be used for general network traffic and clickApply.

    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 theOptimize 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 immediatelyacknowledge 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. ClickOK and then Next.

    44 Attaching a server

    Configuring NIC initiators on a Windows server or Windows virtual machine to

    connect to the system iSCSI targets with iSNS

  • 8/13/2019 iSCSI Network W2k8

    45/86

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

    9. ClickFinishto close the wizard.

    Configuring NICinitiators on a Windows serveror Windows virtual machine to connect to the 45

    system iSCSI targets with iSNS

    Configuring NIC initiators on a Windows server or Windows virtual machine to

    connect to the system iSCSI targets with iSNS

  • 8/13/2019 iSCSI Network W2k8

    46/86

    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:

    1. Open QLogic SANsurfer as described in the QLogic documentation.

    2. In the HBA tree, select the HBA and click theHBA Optionstab.

    The iSCSI name defaults to the iSCSI standard (iqn.xxxx).

    3. SelectEnable iSNS.

    4. For each iSNS server, set the iSNS server address automatically or manually:

    For an automatic setting - Select Obtain iSNS server address automatically (via DCHP).

    For a manual setting - SelectUse the following iSNS server address and enter the IP

    address of the server.

    5. ClickSaveto save the new settings.

    6. On theTarget Settingstab, 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 eachiSNS 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, clickSave.

    c. At the prompt to refresh the information for the server, clickYes.

    46 Attaching a server

    Configuring iSCSI HBAinitiators on a Windows serverto connect to thesystem

    iSCSI targets with iSNS

  • 8/13/2019 iSCSI Network W2k8

    47/86

    Registering the server with the system

    Important:

    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.

    Running the Unisphere Server Utility on a Windows server or a Windows virtualmachine

    Starting the Unisphere Server Utility on a Windows server or a Windows virtual machine

    1. Run the Unisphere Server Utility by selectingStart Programs EMC Unisphere

    Unisphere Server UtilityorStart All Programs EMC Unisphere Unisphere Server Utility .

    2. Select your language, if the software prompts you for it.

    Note: 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 entercd C:\Program Files\EMC\Unisphere ServerUtilityorcd C:\Program Files (x86)\EMC\Unisphere Server Utility, then enterServerUtilCLI.exe.

    Registering the server using the Unisphere Server Utility on a Windows server or a Windows

    virtual machine

    1. If the host agent is running, stop the host agent service.

    2. In theUnisphere Server Utilitydialog 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.

    Registering the server with the system 47

    Registering the server with the system

  • 8/13/2019 iSCSI Network W2k8

    48/86

    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. ClickNextto 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. ClickFinishto exit the utility.

    6. If you stopped the host agent, restart it.

    Starting the Unisphere Host Agent

    Starting the host agent on a server automatically registers the servers NICs or iSCSI HBAs

    with the system.

    Starting the host agent on a Windows server or Windows virtual machine

    This section describes how to start the host agent service.

    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.

    1. Log in as the administrator or the equivalent.

    2. Open theServicespane.

    a. From the desktop, right-click My Computerand select Manage Services and Applications

    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.

    48 Attaching a server

    Registering the server with the system

  • 8/13/2019 iSCSI Network W2k8

    49/86

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

    or

    b. SelectStart Administrative Tools Computer Management Services and Applications

    Services.

    TheServicespane opens.

    3. In theServicespane, right-click Unisphere Agentand select Start.

    4. If you want the host agent to start automatically at system startup:a. Right-clickUnisphere Agentand select Properties.

    TheUnisphere Agent Propertiesdialog box opens.

    b. Select theGeneraltab.

    c. InStartup Type, selectAutomatic.

    5. Close theServicespane.

    The host agent nows start automatically at system startup.

    It may take a few minutes for the host agent to start when:

    Applications are using the system, or

    The SP event log is large and the host agent configuration file is not set up.

    Verifying NIC or iSCSI HBA registration using Unisphere

    1. From Unisphere, selectAll Systems System List.

    2. From the Systemspage, right-click the entry for the system for which you want to verify

    NIC or iSCSI HBA registration, and click Connectivity Status.

    3. In theHost Initiators tab, select the initiator name, and then click Edit.

    4. Verify that the server to SP port connection is displayed as Yes under the Registered

    columns.

    Verifying NIC or iSCSI HBA registration using Unisphere 49

    Registering the server with the system

  • 8/13/2019 iSCSI Network W2k8

    50/86

    Once all NICs or iSCSI HBAs belonging to the server are registered, you can assign the

    server to storage groups.

    5. ClickCanceland then OK to close the Connectivity Statusdialog box.

    50 Attaching a server

    Registering the server with the system

  • 8/13/2019 iSCSI Network W2k8

    51/86

    Verifying system health

    Use the system verification wizard that is part of the Unisphere Service Manager (USM),

    which replaces the Navisphere Service Taskbar, to:

    Validate the connectivity of the system hardware components

    Verify back-end functionality

    Verify the status of all field-replaceable units

    Analyze system logs

    1. If you do not have the Unisphere Service Manager running:

    a. Download and install the Unisphere Service Manager from theEMC 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

    SelectStart All Programs orStart Programs, then selectEMC Unisphere

    Unisphere Service Manager Unisphere Service Manager

    2. Log in to your system.

    3. From the Systemscreen, 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.

    Verifying system health 51

    Verifying system health

    http://support.emc.com/http://support.emc.com/
  • 8/13/2019 iSCSI Network W2k8

    52/86

    Setting system failover values for the server initiators using Unisphere

    Use the Unisphere Failover Setup wizard to set the system failover values for all NIC or

    iSCSI HBA initiators belonging to the server:

    1. From Unisphere, selectAll Systems System List.

    2. From the Systemspage, select the system for whose failover values you want to set.

    3. Select theHoststab.

    4. UnderHost Management, select theFailover Wizard.

    5. In theStart Wizarddialog box, read the introduction, and then click Next.

    6. In the Select Host dialog box, select the server you just connected to the system, and clickNext.

    7. In theSelect Storage Systems dialog box, select the system, and click Next.

    8. In theSpecify Settingsdialog box, set the following values for the type of software running

    on the server.

    Important:

    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:

    Initiator Typeto CLARiiON Open

    Array CommPathto Enabled

    Failover Modeto 4 if your PowerPath version supports ALUA.

    Failover Modeto 1 if your PowerPath version does not support ALUA.

    Note: For information on which versions of PowerPath support ALUA, refer to the PowerPath

    release notes on theEMC Online Support websiteor to EMC Knowledgebase solution

    emc99467.

    52 Attaching a server

    Setting system failover values for the server initiators using Unisphere

    http://support.emc.com/http://support.emc.com/
  • 8/13/2019 iSCSI Network W2k8

    53/86

  • 8/13/2019 iSCSI Network W2k8

    54/86

    Verifying your high-availability iSCSI configuration

    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