Vnx5500 windows connectivity guide

Here is Your Customized DocumentYour Configuration is:

Attach a server Operating System - Windows Server 2008 Path Management Software - Windows native Model - VNX5500 Connection Type - Fibre Channel Switch or Boot from SAN

Document ID - 1421245133756

Reporting Problems

To send comments or report errors regarding this document,please email: [email protected] Issues not related to this document, contact your service provider.Refer to Document ID:1421245133756Content Creation Date January 14, 2015

EMC VNX Series

Attaching a Server to a ConfigurationNovember, 2014

This document explains how to attach a Microsoft Windows Server 2008 Server with NativeMultipath Failover to a VNX in a Fibre Channel switch or boot from a storage area network(SAN) configuration.The main topics in this document are:u Before you start..........................................................................................................2u Booting from a SAN....................................................................................................3u Installing HBAs in the server.......................................................................................4u Installing or updating the HBA driver.......................................................................... 5u Installing or updating Windows native failover........................................................... 6u Installing Unisphere server software.......................................................................... 7u Connecting the VNX to the server in a Fibre Channel switch configuration................ 17u Determining if your server has a supported configuration.........................................21u Registering the server with the system..................................................................... 23u Manually registering the Windows server with the system (boot-from-SAN

configurations only)................................................................................................. 25u Verifying system health............................................................................................26u Setting system failover values for the server initiators using Unisphere....................27u Setting Windows native failover properties...............................................................28u Verifying your high-availability Fibre Channel configuration......................................28u Configuring your VNX system....................................................................................29u Preparing LUNs to receive data.................................................................................34u Sending Windows server and Windows virtual machine disk information to the system

................................................................................................................................ 34u Verifying your Windows Server 2008 native multipath failover configuration............ 36

Before you startNote

This document uses the term system to refer to your VNX.If you are an EMC partner, refer to the EMC online support website to download thesoftware mentioned in ths guide (support.emc.com).NOTICE

If you will configure your system connections to your ESX or Hyper-V server, you mustattach the ESX or Hyper-V server to your system prior to performing the steps in thisdocument. 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.u You must have a supported Windows host on the same network as the system

management ports. You can use this host:l As a client in which you launch the Unisphere software.l To run the Unisphere Service Manager, which runs only on a Windows host.l 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).u 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 aUnisphere management station. For supported Internet browsers, see the Unisphererelease notes on the EMC Online Support website.

u You must have, a supported Windows host, a Windows 2000, Windows Server 2003,Windows Server 2008, or Windows 2012 host that is or will be a server with FibreChannel connections to the system. This server must have a supported serverconfiguration; that is, it must have all required updates, such as hot fixes or patches,installed.

u You must have one or more supported Fibre Channel host bus adapters (HBAs), whichmay already be installed in the server. These adapters must have the latestsupported BIOS and driver.We recommend that you do not mix Fibre Channel HBAs from different vendors in thesame server.

u Each storage-processor (SP) Fibre Channel port that you will use on the system musthave an optical cable. These cables may already be connected for a configurationwith an existing system or server. We strongly recommend you use OM3 50 mcables. For cable specifications, refer to the system's technical specifications.

u You must have one or two Fibre Channel switch fabrics, which may already beinstalled, and an optical cable for connecting each HBA port to a switch port, if notalready connected. We strongly recommend you use OM3 50 m cables. For cablespecifications, refer to system's Technical Specifications.

u For boot-from-SAN configurations:l Be sure your Windows hosts have been qualified for booting from your EMC

system over Fibre Channel connections as described under "Boot Device Support"in the EMC Support Matrix on the EMC Online Support website. The EMCSupportMatrix also contains specific boot-from-SAN restrictions.

2

l Refer to the appropriate Windows HBA guide, available on the EMC OnlineSupport website, for information on configuring your HBA and installing theWindows operating systemon an external system: EMC Host Connectivity with Emulex Fibre Channel Host Bus Adapters (HBAs)

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

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

(HBAs) and Converged Network Adapters (CNAs) in the Windows Environmentl At the start of the Windows boot procedure, make sure no failover software is

running. For high availability while booting from a SAN with a single hardwarefault, HBA BIOS must have a primary path and secondary path(s) properlyconfigured (with access to both SPs).

l Refer to the section on Booting from a SAN on page 3 for additionalinformation on booting Windows from an external storage.

u You must have a method for writing data to a LUN on the system that will test thepaths from the server to the system. You can download an I/O simulator (Iometer)from the following website: http://www.iometer.org.

Booting from a SANBooting from a SAN lets you use your system as the boot disk for your server instead of adirectly attached (or internal) hard disk. By using a properly configured Fibre ChannelHBA or blade server mezzanine adapter connected and zoned to the same switch orfabric as the system, you can configure a server to use a LUN presented from the systemas its boot disk.Benefits of a boot-from-SAN configurationA boot-from-SAN configuration can simplify management in the data center. Separatingthe boot image from each server allows administrators to leverage their investments inEMC systems to achieve high availability, better data integrity, and more efficient storagemanagement. Other benefits can include:u Improved disaster toleranceu Reduced total cost through diskless serversu High-availability storageu Rapid server re-purposingu Consolidation of image managementRisks of booting from the systemWhen using the system as a boot disk, EMC recommends that you shut down the hostserver during any maintenance procedures that could make the boot disk unavailable tothe host.

CAUTION

Microsoft Windows operating systems use virtual memory paging files that reside on theboot disk. If the paging file is unavailable to the memory management system when itneeds it, the operating system will crash with a blue screen.Any of these events could crash an operating system that is booting from the system:u Lost connection to the system (pulled or damaged cable connection)

Attaching a Server to a Configuration

Booting from a SAN 3

u System service/upgrade procedures, such as online microcode upgrades and/orconfiguration changes

u System failures, including failed lasers on Fibre Channel portsu System power failureu Storage area network failures, such as Fibre Channel, switch components, or switch

power failuresu Storage area network service/upgrade procedures, such as firmware upgrades or

hardware replacements

Note

EMC recommends moving the Windows virtual memory paging file to a local disk whenbooting the operating system from the EMC system. Consult your Windows manual forinstructions on how to move the paging file.How to determine I/O latency and load on the boot LUNThe boot-for-SAN configurations listed in the EMC Support Matrix represent the maximumconfigurations allowed as typical configurations. Here are some general measurementsyou can use to determine if your environment will support the maximum allowed boot-from-SAN configurations:u Using the Windows Performance Monitor, capture and analyze the Physical Disk and

Paging File counters for your boot LUN. If response time (sec/operation), or diskqueue depth increase over time, review any additional loading that may be affectingthe boot LUN performance (HBA/SAN saturation, failovers, ISL usage, and so forth).

u Use available system Performance Management tools to determine that the systemconfiguration, LUN configuration and access are configured optimally for each host.

Possible ways to reduce the load on the boot LUN include:u Move application data away from the boot LUN.u Reduce the number of LUNs bound to the same physical disks.u Select an improved performance RAID type.Contact your EMC support representative for additional information.Crash dumps after system failuresIf you configure your system to write crash dump files after system failures and youconfigure your host to boot from the system, you can successfully save the crash dumpfile only to the original boot device path on which the system started. This is a Windowslimitation, and EMC PowerPath does not affect this behavior. At the time a system crashis to be written to disk, Windows has already saved the original boot path, andPowerPath cannot redirect the crash dump file (MEMORY.DMP) to an alternative availabledevice. When you want to capture a crash dump file for a configuration, you shouldensure that the original primary boot path is always available.

Installing HBAs in the serverFor the server to communicate with the system Fibre Channel data ports, it must have oneor more supported HBAs installed.

Before you startTo complete this procedure, you will need one or more supported HBAs with the latestsupported BIOS and drivers.

4

For information on supported HBAs, BIOS, and drivers, refer to the E-Lab InteroperabilityNavigator on the EMC Online Support website.

Note

We recommend that you never mix HBAs from different vendors in the same server.

Installing HBAsCAUTION

HBAs are very susceptible to damage caused by static discharge and need to be handledaccordingly. Before handling HBAs, observe the following precautions:u Store HBAs in antistatic bags.u Use a ground (ESD) strap whenever you handle HBAs.u Never plug or unplug HBAs with the power on. Severe component damage can result.

Procedure1. 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 HBA that you are installing:

a. Locate an empty PCI bus slot or a slot in the server that is preferred for PCI cards.b. Install the HBA following the instructions provided by the HBA vendor.c. If you installed a replacement HBA, reconnect the cables that you removed in the

exact same way as they were connected to the original HBA.4. Plug the server's power cord into the power outlet, and power up the server.Results

Installing or updating the HBA driverThe server must run a supported operating system and a supported HBA driver. EMCrecommends that you install the latest supported version of the driver.For information on the supported HBA drivers, refer to the E-Lab InteroperabilityNavigator on EMC Online Support website.

Before you startTo complete this procedure, you will need:u The latest supported version of the HBA driver.


Installing HBAs 5

Note

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

If you have an Emulex driver, download the latest supported version and instructionsfor installing the driver from the vendors website:http://www.emulex.com/products/fibre-channel-hbas.htmlIf you have a QLogic driver, download the latest supported version and instructionsfor installing the driver from the vendors website:http://support.qlogic.com/support/oem_emc.aspIf you have a Brocade driver, download the latest supported version and instructionsfor installing the driver from the vendors website:http://www.brocade.com/services-support/driversdownloads/HBA/HBA_EMC.page

u Any updates, such as hot fixes or service packs to the servers operating system thatare required for the HBA driver version you will install.For information on any required updates, refer to one of the following:l E-Lab Interoperability Navigator on the EMC Online Support websitel The HBA vendors website

Installing the HBA driverProcedure1. Install any updates, such as hot fixes or service packs, to the servers operating

system that are required for the HBA driver version you are installing.2. If the hot fix or patch requires it, reboot the server.3. Install the driver following the instructions on the HBA vendors website.4. Reboot the server when the installation program prompts you to do so. If the

installation program did not prompt you to reboot, then reboot the server when thedriver installation is complete.

Installing or updating Windows native failoverWindows native failover is included with the Windows Server 2008 operating system butyou must enable it as described below.

Enabling Windows native failoverProcedure1. Navigate to the server features window:

Server Manager > Features > Add features2. Select the Multipath I/O feature.

If asked about rebooting the server, choose to reboot later.

6

Updating Windows native failoverTo check for any updates or patches to the failover software, refer to the Microsoftwebsite. If an update is available, follow the instructions to install it as described on the Microsoft website.

Installing Unisphere server softwareThis section describes how to install Unisphere server software.NOTICE

You must install the host agent or server utility on your Hyper-V or ESX server if you:u configured your system connections to your Hyper-V or ESX server,u have a non-Windows virtual machine, oru 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 have a Hyper-V or ESX server, you must install the host agent or server utility onyour Hyper-V or ESX server. Do not install these programs on your virtual machine.Boot-from-SAN configuration If you are booting from a SAN configuration, do not installthe Unisphere Host Agent or Unisphere Server Utility to register your server. You willperform a manual registration later.

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 virtualmachine other than Windows Server 2008, generate a new document and select theoperating system running on the virtual machine.Before you beginRefer to the sections below to determine which application to install for host registrationand 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 8.u To determine whether to install the Unisphere Host Agent or Unisphere Server Utility

to register your HBAs with the system, refer to Determining whether to install theUnisphere Host Agent on page 8.

Installing Unisphere server softwareDepending on which Unisphere server software you are installing, refer to the appropriatesection below.u Unisphere Host Agent see Installing the Unisphere Host Agent on page 9.u Unisphere Server Utility see Installing the Unisphere Server Utility on

page 14.u Navisphere CLI see Installing VNX for Block Secure CLI on page 15.u Admhost Utility see Installing the Admhost Utility on page 16 .u Admsnap Utility see Installing the Admsnap Utility on page 16.


Updating Windows native failover 7

Requirements for Unisphere server softwareTo run Unisphere server software, your server must meet the following requirements:u Run a supported version of the Windows operating system.u For Fibre Channel connections, have the EMC VNX supported HBA hardware and

driver installed.u 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.u 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 tothe system and it allows Navisphere CLI to communicate with the system over thenetwork.

u Have a configured TCP/IP network connection to any remote hosts that you will use tomanage the systems, including:l any server whose browser you will use to access Unisphere,l a supported Windows server running Unisphere Server software,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 SPin the system. The remote server can be running AIX, HP-UX, Linux, Solaris, or theWindows operating system.

Note

For information about the specific revisions of the server operating system, the systemVNX for Block OE, and Access Logix software that are required for your version of thehost agent, see the release notes for the host agent on the EMC Online Support website.

Determining whether to install the Unisphere Host AgentDepending on your application needs, you can install the host agent to:u Monitor system events and notify personnel by e-mail, page, or modem when any

designated event occurs.u Retrieve LUN world wide name (WWN) and capacity information from VNX systems.u Register the servers HBAs with the system.

Alternatively, you can use the Unisphere Server Utility to register the servers HBAswith the system. Host registration differences between the host agent and theserver on page 8 describes the host registration differences between the hostagent and the server utility.

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

Function Unisphere Host Agent Unisphere Server UtilityPushes LUN mappingand OS information tothe system.

Yes LUN mappinginformation is displayed inthe Unisphere UI next to the

No LUN mapping information is notsent to the system. Only the serversname, ID, and IP address are sent to the

8

Table 1 Host registration differences between the host agent and the server utility (continued)

Function Unisphere Host Agent Unisphere Server UtilityLUN icon or with the CLIusing the Server -volmap command.

system. The text ManuallyRegistered appears next to thehostname icon in the Unisphere UIindicating that the host agent was notused to register this server.

Runs automatically tosend information to thesystem.

Yes No user interaction isrequired.

Yes You can control whether serverinformation is automatically sent to thesystem by enabling or disabling theregistration service feature. This featureis automatically enabled during theinstallation of the server utility, but youcan stop the service at any time throughthe services option in the Microsoft userinterface. Note that only the serversname, ID, and IP address are sent to thesystem; LUN mapping information is notsent.

Requires networkconnectivity to thesystem.

Yes Network connectivityallows LUN mappinginformation to be available tothe system.

No LUN mapping information is notsent to the system. Note that if you areusing the server utility to upload a high-availability report to the system, youmust have network connectivity.

Installing the Unisphere Host AgentThis 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 serverWe recommend that you download and install the most recent version of the UnisphereHost Agent software from the EMC Online Support website.Procedure1. 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 notfunction properly.

3. If you are running a version prior to 6.26 of the host agent, you must remove it beforecontinuing 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.


Installing the Unisphere Host Agent 9

c. Double-click the executable file listed below to start the installation wizard.UnisphereHostAgent-Win-32-x86-en_US-version-build.exewhere version and build are the version number and the build number of thesoftware.

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 selectedthe 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 UserList 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 ExistingFile to use this configuration file or select Browse to use a different file.The host agent configuration file contains a list of login names for this server. Onlyusers whose usernames are listed in the Privileged User List can send CLIcommands to the system.

l If the Config File field does not contain a file entry, then a host agent configurationfile does not exist on the server. Select Create/Overwrite File and browse to theagent.config file.You will then need to add users to the Privileged User List (login names for thisserver). Only users whose usernames are listed in the Privileged User List can sendCLI commands to the system.

Note

There must be at least one entry in the Privileged User List or an error message willappear.

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 userentries 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.12.If you updated the host agent and were using event monitor, restore the event monitor

configuration from a previously copied Navimon.cfg file:

10

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 MyComputer and select Manage > Services and Applications > Services; or forWindows 2012, from the desktop, mouse over to the left bottom corner ofthe 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.c. Start 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 MyComputer and select Manage > Services and Applications > Services; or forWindows 2012, from the desktop, mouse over to the left bottom corner ofthe 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 Start.d. If you want the host agent to start automatically at system startup:

a. Right-click Unisphere Host Agent and select Properties.The Unisphere Host Agent Properties dialog box opens.

b. Select the General tab.c. In Startup Type, select Automatic.

The host agent will now start automatically at system startup.e. Close Computer Management.

It may take a few minutes for the host agent to start if either applications areusing the system or the SP event log is large and the host agent configurationfile is not set up.

13.Click Done to exit the installation wizard.14.Verify that Unisphere Host Agent is installed using the Add/Remove Programs dialog

box.

Running the Unisphere Host AgentThis section describes how to start and stop the host agent and how to test the hostagent connections.

Starting the host agent on a Windows serverThis section describes how to start the host agent service.


Running the Unisphere Host Agent 11

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, resultingin the host agent taking several minutes to execute a system management task. Thisbehavior is most evident when one host agent is managing multiple systems. Also, if theSP event log is large and the host agent configuration file is set up to read all events, itmay take a few minutes for the host agent to start.Procedure1. 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 Computerand select Manage > Services and Applications > Services; or for Windows 2012,from the desktop, mouse over to the left bottom corner of the taskbar and selectStart, then right-click Computer > Manager > Tools > Services.This section describes how to start and stop the host agent service. This sectionalso describes how to configure the system connected to the server.

Note

When a system experiences heavy input/output traffic (that is, applications areusing the system), information may not be reported to the host agent in a timelymanner, resulting in the host agent taking several minutes to execute a systemmanagement task. This behavior is most evident when one host agent is managingmultiple systems. Also, if the SP event log is large and the host agent configurationfile is set up to read all events, it may take a few minutes for the host agent tostart.

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.


5. Close the Services pane.ResultsThe host agent now start automatically at system startup.It may take a few minutes for the host agent to start when:u Applications are using the system, oru The SP event log is large and the host agent configuration file is not set up.u Applications are using the system, oru The SP event log is large and the host agent configuration file is not set up.

12

Stopping the host agent on a Windows serverProcedure1. Log in as the administrator or the equivalent.2. Open the Services pane.

l For Windows 2008 and earlier versions, from the desktop, right-click My Computerand select Manage > Services and Applications > Services; or for Windows 2012,from the desktop, mouse over to the left bottom corner of the taskbar and selectStart, then right-click Computer > Manager > Tools > Services.

The Services pane opens.3. In the Services pane, right-click Navisphere Agent and select Stop. If asked to confirm

your request to stop the agent service, click Yes, and close the Services pane.

Testing the host agent connectionsBefore continuing, you should test the host agent connections as follows:Procedure1. Start the host agent.2. Look for any errors on the console and in the operating system log to make sure the

agent started and no device errors occurred.3. Verify that the host agent on the server can see the system as follows:

a. Enter the following CLI command: naviseccli |navicli [-d device]| -hhostname port -list -hba

Note

You cannot specify both the d switch and h switch.where[-d device] is the device name for the system (only supported with legacysystems).-h hostname is the IP address of the SP.For each HBA in the server, a listing similar to the following will be displayed. Forsystems in a SAN (shared storage) environment, the listing includes HBAs in allconnected 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


Running the Unisphere Host Agent 13

b. In the listing, verify the path for each HBA installed in the host to the SP.

Host agent status and error loggingWhile the system is running, the operating system tracks information about host agentevents and host agent errors, and places this information in log files on the server.The host agent error log tracks information about the host agents startup, the host agentshutdown, and errors that might occur, such as the host agents inability to access adevice in the configuration file. If problems occur, log files are a good place to start yourtroubleshooting.

Installing the Unisphere Server UtilityThis section describes how to install the Unisphere Server Utility on your server.

Installing the Unisphere Server Utility on a Windows serverWe recommend that you download and install the most recent version of the UnisphereServer Utility software from the applicable support by product page on the EMC OnlineSupport website.Procedure1. 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 Productpage and select Downloads.

b. Select the Unisphere Server Utility, and then select the option to save the softwareto your server.

c. Double-click the executable listed below to start the installation wizard.UnisphereServerUtil-Win-32-x86-language-version-build.exewherelanguage is either en_US, when only the English version is available, or loc, whenthe 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 servicefeature (it is enabled by default). The registration service feature automaticallyregisters the servers HBAs with the system after the installation and updates serverinformation 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 iSCSIinitiator to connect to the system, select Yes when prompted.

5. When the installation is complete, click Done to exit the wizard.

14

Installing VNX for Block Secure CLIThis section describes how to install VNX for Block Secure CLI.You can install VNX for Block CLI on either the server or virtual machine.

Installing VNX for Block Secure CLI on a Windows server or a Windows virtual machineWe recommend that you download and install the most recent version of the VNX forBlock Secure CLI software from the applicable support by product page on the EMCOnline Support website.Procedure1. 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 page15.These ports are used by VNX for Block CLI. If these ports are not opened, the softwarewill not function properly.Table 2 TCP/IP ports

Software TCP/IP portsSecure CLI 443, 2163

4. Download the software:a. From the EMC Online Support website, select the VNX Series Support by Product

page and select Downloads.b. Select the VNX for Block 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..exewhere:language is either en_US, when only the English version is available, or loc, whenthe localized versions are available (including English).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 Navisphere SecureCLI.

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 Programsdialog box.


Installing VNX for Block Secure CLI 15

Installing the Admhost UtilityIf you want to access LUNs that participate in SAN Copy sessions, install the AdmhostUtility.

Note

The Admhost Utility is supported on Microsoft Windows platforms only. For the supportedWindows versions, see the Admhost Release Notes.

Installing the Admhost Utility on a Windows serverWe recommend that you download and install the most recent version of the AdmhostUtility software from the applicable support by product page on the EMC Online Supportwebsite.NOTICE

Currently, you cannot install admhost on your virtual machine if your virtual machine isconnected to Fibre Channel or FCoE storage; you must install it on the Hyper-V server. Forany updates, refer to the Admhost Release Notes.

Procedure1. Log in as the administrator or as someone who has administrator privileges.2. If admhost is already installed, remove it.3. Download the software:


b. Select the Admhost Utility, and then select the option to save the software to yourserver.

c. In the folder where you saved the software, double-click the executable file to startthe 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 UtilityTo access snapshots of LUNs in the system, install the Admsnap Utility.You can install admsnap on the server or on the virtual machine.NOTICE

Currently, you cannot install admsnap on your virtual machine if your virtual machine isconnected to Fibre Channel storage; you must install it on the Hyper-V server. For anyupdates, refer to the EMC SnapView, Admsnap, and ADMhost Release Notes.

16

Installation prerequisitesBefore you can install and use the Admsnap Utility, you must install SnapView on asupported system.For a list of supported systems, refer to the release notes for SnapView and admsnap.

Installing the Admsnap Utility on a Windows serverWe recommend that you download and install the most recent version of the AdmsnapUtility software from the Downloads section of the VNX Series support by product page onthe EMC Online Support website.Procedure1. 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:


b. Select the Admsnap Utility version you want to download and select the option tosave the zip file to your server.

c. Double-click the following executable file to start the installation wizard:Windows Server 2008admsnap-Win2K8-32-en_US-version-build.exewhere version and build are the version number and the build number of thesoftware.

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.

If you selected the default destination folder, admsnap is installed in C:\ProgramFiles\EMC\Unisphere Admsnap (32-bit) or C:\Program Files(x86)\EMC\Unisphere Admsnap (64-bit).

Connecting the VNX to the server in a Fibre Channel switchconfiguration

Use optical cables to connect switch ports to the VNX Fibre Channel host ports and toFibre Channel switch ports and to connect the switch ports to the server HBA ports.For cable specifications, refer to the technical specifications for your VNX available fromthe Learn about system link on the VNX support website or from EMC Online Supportwebsite.

Note

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

Identifying VNX Fibre-Channel host ports for server connectionsYou can connect servers to the VNX onboard Fibre Channel host ports 2 and 3 and to anyports (0, 1, 2, 3) on the UltraFlex Fibre Channel I/O modules in slots A0 and B0 or A1and B1. Onboard Fibre Channel host ports and slots for I/O modules with host ports in a


Connecting the VNX to the server in a Fibre Channel switch configuration 17

VNX5300VNX5500 (FC and iSCSI modules shown) on page 18 shows the location of theonboard ports and of the slots for I/O module with host ports.

Note

In a VNX Unified system or a VNX for File system the onboard Fibre Channel ports 4 and 5are for blade connections. If you add a third blade, you must connect it to port 3. If youhave a host connected to port 3 when you add the third blade, you must move the hostconnection to a port on a Fibre Channel I/O module.Figure 1 Onboard Fibre Channel host ports and slots for I/O modules with host ports in a VNX (FCand iSCSI modules shown)

2 3 4 5 2 3 4 5

12

30

12

30

CL4612

B0 B1 A1 A0

Slots for I/O moduleswith host ports

Onboard FChost ports

Onboard FChost ports

Module labels and FE port connectorsEach Fibre Channel I/O module has a 8 GB Fibre label on its handle and an optical small-form factor pluggable (SFP) transceiver module in each of its Fibre FE ports.FE port connectivityThe Fibre FE ports on an 8 Gb/s Fibre Channel I/O module supports 2/4/8 Gb/sconnectivity. You cannot use the FE ports on an 8 Gb/s Fibre Channel I/O module in a 1Gb/s Fibre Channel environment.

Handling optical cablesOptical cables are susceptible to damage, so take the following precautions whenhandling them:u Keep the covers on all optical cables until you are ready to insert them.u Avoid tight bends. If you need to make a 90 bend, do it over 6 to 12 inches.u Do not use optical cables to support weight (including their own unsupported weight

if they are long).u Do not pull long runs of cable; instead, lay the cable in place or pull only a few feet at

a time.u Place the cables where no one can step on them or roll equipment over them.

Cabling the VNX Fibre Channel host ports to the switch ports (if necessary)For highest availability, connect one or more Fibre Channel host ports on SP A to ports onthe switch and connect the same number of Fibre Channel host ports on SP B to ports onsame switch or on another switch, if two switches are available.

18

For each Fibre Channel (FC) host port on the VNX that you will use for I/O with the server:Procedure1. Locate the FC host port to which you will connect the switch port.

For information on identifying the host ports using Unisphere, refer to the Unisphereonline help.

Note

The MirrorView/A and MirrorView/S applications require onboard port 2. The SANCopy application may restrict or require the use of certain SP ports. Refer to theapplication documentation for specific cabling information.

2. Remove the protective cover from the FC host port connector on the SP and from oneend of the optical cable, and plug the cable into the host port connector (Connectingan optical cable on page 19 and Sample cabling between a VNX and twoswitches on page 19).

3. Remove the protective cover from the optical connector on the switch port that youwill use and from the free end of the optical cable, and plug the cable into the switchport (Connecting an optical cable on page 19 and Sample cabling between a VNXand two switches on page 19).Figure 2 Connecting an optical cable

CL4021

Figure 3 Sample cabling between a VNX and two switches

2 3 4 5 2 3 4 5

12

30

12

30

CL4616


Cabling the VNX Fibre Channel host ports to the switch ports (if necessary) 19

Cabling the switch ports to the server HBA ports (if necessary)For highest availability in a multiple-HBA server, connect one or more HBA ports to portson the switch and connect the same number of HBA ports to ports on same switch or onanother switch, if two switches are available.For each server HBA port that you will use for I/O with the VNX:Procedure1. Remove the protective cover from the FC switch port connector and from one end of

the optical cable, and plug the cable into the connector.2. Remove the protective cover from the server HBA port connector and from the free end

of the optical cable, and plug the cable into the HBA port connector (Sample cablingfor a Fibre Channel switch configuration on page 20).Figure 4 Sample cabling for a Fibre Channel switch configuration

2 3 4 5 2 3 4 5

12

30

12

30

CL4186

CL4620

Zoning the switchesUse switch management software to update switch software and zone switches that arenot hard zoned.We recommend single-initiator zoning as a best practice. In single-initiator zoning eachHBA port has a separate zone that contains it and the SP ports with which itcommunicates. For information on Fibre Channel topologies, refer to the EMC NetworkedStorage Topology Guide on the EMC Online Support website.To zone the switch:Procedure1. Connect the switch management ports to the network from which you will manage the

switches.

20

2. If the switches are not running the most recent supported firmware version, install thissoftware from the switch vendor's website.

Note

For information on the supported switch firmware versions, see the E-LabInteroperability Navigator on the EMC Online Support website.

3. Use either the zoning wizard CD that shipped with the switch or the switchmanagement software to set up the appropriate switch zones.a. To use the zoning wizard CD Using the instructions provided with the CD, run the

zoning wizard and select the zone configuration that is applicable to the way thatyou connected the VNX Fibre ports and the server HBA ports to the switch.

b. To use the switch management software Download the latest version of theswitch management software from the switch vendor's website, and follow theinstructions provided for the software to setup the zones that are applicable to theway that you connected the VNX Fibre ports and the server HBA ports to the switch.

Determining if your server has a supported configurationBefore 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 .NOTICE

If you have a Windows virtual machine, for a complete configuration report, run the serverutility from the Windows Hyper-V server.If you have this information, go to Verifying a server's configuration with E-LabNavigator on page 22. If you do not have this information, you can generate a serverconfiguration report for your server using the Unisphere Server Utility.

Starting the Unisphere Server Utility on a Windows serverProcedure1. Run the Unisphere Server Utility by selecting.

l Start > Programs > EMC > Unisphere > Unisphere Server Utility or Start > All Programs> EMC > Unisphere > Unisphere Server Utility

l For Windows Server 2012, mouse over to the bottom corner of the taskbar andclick Start, then right-click the Desktop > All Apps > EMC > Unisphere > UnisphereServer 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 enter cd C:\Program Files\EMC\Unisphere Server Utility or cd C:\Program Files (x86)\EMC\Unisphere Server Utility, then enter ServerUtilCLI.exe.


Determining if your server has a supported configuration 21

Generating a high-availability report for a serverProcedure1. In the Unisphere Server Utility dialog box, select Verify Server High-Availability to

generate a report of the servers environment.This option detects if PowerPath or some other failover software, such as DMP, isrunning. After the verification, the utility generates a summary report and saves it tothe server.

2. In the summary report, select the Checklist tab to view the information about theserver that you need to compare with the E-Lab Navigator information.

Verifying a server's configuration with E-Lab NavigatorProcedure1. From your web browser, go to the EMC Online Support website and log in.2. If required, register and create a username and password.3. Select E-Lab Navigator on the EMC Online Support website from the Tools menu on

the right-side of the home page.4. From the E-Lab Navigator page, select Launch E-Lab Navigator and then select the

Solutions and Wizards tab.5. From the drop-down menu, select the CLARiiON Host Attach Wizard.6. For each step of the wizard, provide the requested information based on what is

installed on the server or what you intend to install on the server.If the configuration you entered is invalid, an additional step appears in the wizardand a Results, EMC Support Statements pane appears on the right with information tohelp you provide the requested information in the additional step.If the configuration you entered is valid, a Results link appears on the right.

7. Click the Results link appears to view a report that contains information about theconfiguration you entered.

8. Print and/or save a copy of the report.9. Close the E-Lab 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 beforecontinuing.

Note

The Host Attach Wizard displays only options that EMC supports. If any of theconfiguration information on the server utility's high-availability report cannot befound in the wizard, then EMC does not support it.

22

Registering the server with the systemNOTICE

Booting from a SAN configuration - If you are booting from a SAN, do not register youserver using the Unisphere Host Agent or Unisphere Server Utility. You will perform amanual registration in the next section.

You must run the Server Utility on each server connected to the system to register theserver's HBAs with the system.

Running the Unisphere Server Utility on a Windows serverRun the Unisphere Server Utility for Windows from the server.





Note


Registering the server using the Unisphere Server Utility on a Windows serverProcedure1. 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 underconnected systems.

3. Locate the WWN of the HBA you just installed. The HBA should appear once for everySP port to which it is connected.

Note

If the Unisphere Server Utility does not list your storage processors, verify that yourserver 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 WWN of the each HBA to each system. Oncethe server has storage on the system, the utility also sends the device name and


Registering the server with the system 23

volume or file system information for each LUN (virtual disk) in the system that theserver sees.

5. Click Finish to exit the utility.6. If you stopped the host agent, restart it.

Starting the Unisphere Host AgentStarting the host agent on a server automatically registers the servers HBAs with thesystem.

Starting the host agent on a Windows serverThis section describes how to start the host agent service.

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, resultingin the host agent taking several minutes to execute a system management task. Thisbehavior is most evident when one host agent is managing multiple systems. Also, if theSP event log is large and the host agent configuration file is set up to read all events, itmay take a few minutes for the host agent to start.Procedure1. 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 Computerand select Manage > Services and Applications > Services; or for Windows 2012,from the desktop, mouse over to the left bottom corner of the taskbar and selectStart, then right-click Computer > Manager > Tools > Services.This section describes how to start and stop the host agent service. This sectionalso describes how to configure the system connected to the server.

Note

When a system experiences heavy input/output traffic (that is, applications areusing the system), information may not be reported to the host agent in a timelymanner, resulting in the host agent taking several minutes to execute a systemmanagement task. This behavior is most evident when one host agent is managingmultiple systems. Also, if the SP event log is large and the host agent configurationfile is set up to read all events, it may take a few minutes for the host agent tostart.

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.


24

5. Close the Services pane.ResultsThe host agent now start automatically at system startup.It may take a few minutes for the host agent to start when:u Applications are using the system, oru The SP event log is large and the host agent configuration file is not set up.u Applications are using the system, oru The SP event log is large and the host agent configuration file is not set up.

Verifying HBA registration using UnisphereProcedure1. From Unisphere, select your system, then Hosts > Initiators.2. In the Initiators list, select the initiator name, and tverify that the SP port connection

is displayed as Registered.Once all HBAs belonging to the server are registered, you can assign the server tostorage groups.

Manually registering the Windows server with the system (boot-from-SAN configurations only)

In boot-from-SAN configurations where the operating system is going to be installed onthe LUN, no host agent or server utility is available to perform the registration. Manualregistration of the HBA WWNs is required in order to present a LUN to the server forbooting.

Registering SP and HBA connections with UnisphereWhen you have established a connection between the SP and the HBA, you must registereach connection with the system:Procedure1. Select Hosts > Intiators then select the connection for the WWN of the HBA and click

Register.2. For each HBA that will be connected to the system:

a. In the Register Initiator Record window, select the following: CLARiiON Open for the Initiator Type ArrayCommPath (LUN Z) under Advanced Options Array for the Unit Serial Number, also under Advanced Options For Failover Mode select:

4 for asymmetric active active (ALUA) mode


Verifying HBA registration using Unisphere 25

Note

Asymmetric active active (ALUA) failover is available for your system.If you are booting from SAN configurations, EMC strongly recommends usingfailover mode 4 (ALUA active/active) when the system supports it, as ALUAwill allow I/O access to the boot LUN from either SP, regardless of which SPcurrently owns the boot LUN. Using other failover modes may cause delayswhen the system boots. For information on other failover modes supportedwith your Windows failover software and VNX OE Block (SAN) software, seeEMC Knowledgebase solution emc99467.

If you are booting from SAN configurations, EMC strongly recommends usingfailover mode 4 (ALUA active/active) when the system supports it, as ALUAwill allow I/O access to the boot LUN from either SP, regardless of which SPcurrently owns the boot LUN. Using other failover modes may cause delayswhen the system boots. For information on other failover modes supportedwith your Windows failover software and VNX OE Block (SAN) software, seeEMC Knowledgebase solution emc99467.

b. In the Host Information dialog box, select New Host, enter the servers IP address,and click OK.

Verifying system healthUse the system verification wizard that is part of the Unisphere Service Manager (USM)to:u Validate the connectivity of the system hardware componentsu Verify back-end functionalityu Verify the status of all field-replaceable unitsu Analyze system logsProcedure1. If you do not have the Unisphere Service Manager running:

a. Download and install the Unisphere Service Manager from the EMC Online Supportwebsite to a Windows management station that is connected to the system'smanagement ports. If you do not have a Windows management station, yourservice 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 Manager2. 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.

26

Setting system failover values for the server initiators usingUnisphere

Use the Unisphere Failover Setup wizard to set the system failover values for all HBAinitiators belonging to the server:Procedure1. 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 andunreachable by the server, and the server's failover software could stop operatingcorrectly.If you have a Hyper-V or ESX server, set the system failover values for the Hyper-V orESX server.

For a Windows server with native multipath failover, set:l Initiator Type to CLARiiON/VNXl Array CommPath to Enabledl Failover Mode to 4

Note

For information on which versions of failover support ALUA for your system, refer tothe to EMC Knowledgebase solution emc99467.

8. In the Configuration Summary screen, review the configuration and all settings.9. If the settings are correct, click Next, and if the settings are incorrect, click Back until

you return to the dialog box in which you need to re-enter the correct values.If you clicked Next, the wizard displays a confirmation dialog box.

10.In the confirmation dialog box, click Yes.The wizard displays a summary of the values you set for the system.

11.If the operation failed, rerun the wizard.12.When the operation is successful, click Finish to close the wizard.13.Reboot the server for the initiator records to take affect.


Setting system failover values for the server initiators using Unisphere 27

Setting Windows native failover propertiesThis section describes the required native failover properties you need to set afterupdating>installing> the failover software.

Add support for VNX devicesExecute the following commands to allow Windows native failover (MPIO) to control VNXdevices: %systemroot%\system32\mpclaim.exe -n i -d "DGC RAID 5 "

%systemroot%\system32\mpclaim.exe -n -i -d "DGC RAID 3 "




%systemroot%\system32\mpclaim.exe -n -i -d "DGC VRAID "

%systemroot%\system32\mpclaim.exe -n -i -d "DGC DISK "

NOTICE

The spacing in the command must be exact. Make sure that you have exactly:u 5 spaces after DGCu 10 spaces between RAID 5, RAID 3, RAID 1, RAID 0 and the "u 9 spaces between RAID 10 and the "u 11 spaces between VRAID and the "

The VRAID command is for RAID 6 LUNs and thin LUNs.u 12 spaces between DISK and the "

Verifying your high-availability Fibre Channel configurationUse the server high-availability feature in the Unisphere Server Utility to verify your FibreChannel configuration is highly available (that is, each Fibre Channel HBA has at leastone active path to each storage processor) and path management software is installedand running on the server.NOTICE

If you have a Windows virtual machine, for a complete configuration report, run the serverutility from the Windows Hyper-V server.

28





Note


Using the server utility to verify your high-availability configurationProcedure1. From the Unisphere Server Utility's Welcome screen, select Verify Server High-

Availability.2. Select Valid Server Configuration only.3. In the Select Host Type screen, select Local host and click Next.4. In the Select Report Directory screen, select the location where you want the system

to save the high-availability status report. Click Next.5. Read the summary and if it is accurate, click Next to generate the report. If not, click

Back to return to the screen where you need to correct the data.The utility determines if the server is configured for high availability by verifying thatthe server has at least one connection path to each system SP, and that PowerPath orsome other failover software, such as DMP, is running. It does not detect nativefailover software, such as Windows Server 2008 native failover.

6. Review and resolve any issues reported on the Issues tab of the generated report.

Configuring your VNX systemTo configure your VNX system, use either the Unisphere Service Manager wizards orUnisphere.

Starting UnisphereProcedure1. 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 InternetExplorer, Netscape, or Mozilla.

2. Start the browser.


Starting the Unisphere Server Utility on a Windows server 29

3. In the browser window, enter the IP address of one of the following that is in the samedomain 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

This SP can be in one of the systems that you want to manage.l 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 theSun website where you can select a supported version to download. For informationon the supported JRE versions for your version of Unisphere, refer to Environment andSystem Requirements in the Unisphere release notes on the EMC Online Supportwebsite.

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 anexternal LDAP or Active Directory server for authentication. Username / passwordpairs whose roles are not mapped to the external directory will be denied access. Ifthe 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 canbe managed. Local indicates that only the targeted system can be managed.

7. Click Login.When the user credentials are successfully authenticated, Unisphere stores them asthe default credentials and the specified system is added to the list of managedsystems in the Local domain.

8. If you are prompted to add the system to a domain, add it now.The first time that you log in to a system, you are prompted to add the system to aUnisphere domain. If the system is the first one, create a domain for it. If you alreadyhave systems in a domain, you can either add the new system to the existing domainor create a new domain for it. For details on adding the system to a domain, use theUnisphere help.

Committing VNX for Block Operating Environment (OE) software with UnisphereIf you did not install a VNX for Block OE update on the system, you need to commit theVNX for Block OE software now.Procedure1. 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.

30

3. Click the Software tab, select VNX-Block-Operating-Environment, and click Commit.4. Click Apply.

Configuring cache with UnisphereProcedure1. From Unisphere, select All Systems > System List.2. From the Systems page, right-click the entry for the system for which you want to

verify cache properties and select Properties.3. Enable or configure the cache as described in the Unisphere online help.

Note

The latest version of Unisphere automatically sets the read and write cache sizes. Ifyour system is running an older version of Unisphere, refer to the system's version ofthe online help for advice on setting read/write cache values and setting watermarks.

Enabling storage groups with UnisphereYou must enable storage groups using Unisphere if only one server is connected to thesystem and you want to connect additional servers to the system.Procedure1. From Unisphere, select All Systems > System List.2. From the Systems page, right-click the icon for the system, and click Properties.3. Click the General tab, and select Storage Groups.4. Click OK.

Allocating storage on a new system with the Unisphere LUN Provisioning WizardNOTICE

If you have a Hyper-V or ESX server, perform this procedure on your Hyper-V or ESX server.

Procedure1. Select the system for which you want to allocate storage.2. Select Storage > LUNS > LUNS.3. Under the Wizards list, select the LUN Provisioning Wizard.4. On the Select Servers page, select Assign LUNs to the Servers, and select the servers

that will have access to the new LUNs.5. Select the system in which the new LUNs will reside.6. Create a LUN:

a. Select a pool or RAID group in which to create a LUN, or create a new pool for theLUN.We recommend you use an existing pool or create a pool instead of a RAID groupbecause a pool supports options, such as Fully Automated Storage Tiering (FAST)and Thin Provisioning, which a RAID group does not support.

b. If you are creating a pool LUN and you want the LUN to be a thin LUN, select ThinLUN.


Configuring cache with Unisphere 31

The Thin LUN option is available and will be selected by default if the ThinProvisioning enabler is installed. To learn about pools and thin LUNs, click the ?icon next to Thin LUN.

c. Select the properties for the LUN.d. Add the LUNs to a user-defined folder or do not place them in a folder.e. Click Finish to create the LUN.

7. Verify that the server was assigned to the storage group containing the LUNs youcreated:l If you know the name of the storage group in which the LUNs reside, from

Unisphere, select Storage > Storage Pools.l If you know the name of the server to which the storage group is assigned, from

Unisphere, select Storage > LUNs and confirm that the new LUNs are listed.If you do not see any of the LUNs you just created, you may not have selected theAssign LUNs to a server option in the Select Servers page of the LUN Provisioningwizard. You can use the Storage Assignment Wizard for Block to assign the LUNs to aserver.

8. Create a hot spare policy (a RAID group with a hot spare RAID Type) as described inthe Unisphere online help. To do this, select System > Hardware > Hot Spare Policy.A hot spare is a single disk that serves as a temporary replacement for a failed disk ina 6, 5, 3, 1, or 1/0 RAID group. Data from the failed disk is reconstructedautomatically on the hot spare from the parity or mirrored data on the working disks inthe LUN, so the data on the LUN is always accessible.

Note

Only RAID group LUNs can be hot spares.

Note

Vault drives (the first 4 drives) cannot be qualified as hot spares.

Allocating storage to an existing system with the Storage Assignment wizard inUnisphere

NOTICE


Use the Provision wizard in the Unisphere to create system storage and provide serveraccess to this storage:Procedure1. From Unisphere, select the system for which you want to allocate storage.2. Select the Storage > LUNS > LUNS.3. If you need additional LUNs for the server, use the LUN Provisioning wizard listed in

the LUNs category to create them.4. If you want to assign existing LUNs to the server, use the Storage Assignment wizard

for block.

32

Note

For high availability, a host can connect to only one storage group per system at atime. If you connect a host that is already connected to another storage group, thehost will disconnect from the first storage group. When you disconnect a host from astorage group, and then connect it to a different storage group, the host can no longerperform I/O to the first storage group.

5. Verify that the server was assigned to the storage group containing the LUNs youcreated.l If you know the name of the storage group in which the LUNs reside From

Unisphere, select Storage > Storage Pools.l If you know the name of the server to which the storage group is assigned From

Unisphere, select Storage > LUNs and confirm that the new LUNs are listed.If you do not see any of the LUNs you just created, you may not have selected theAssign LUNs to a server option in the Select Servers page of the Provision wizard. Youcan use the Storage Assignment wizard for block to assign the LUNs to a server.

Verifying that each LUN is fully initialized using UnisphereAlthough the storage group with a new LUN is assigned to the server, the server cannotsee the new LUN until it is fully initialized (completely bound). The time the initializationprocess takes to complete varies with the size of the LUN and other parameters. While aLUN is initializing, it is in a transitioning state, and when the initialization is complete, itsstate becomes ready.To determine the state of a LUN:Procedure1. From Unisphere, navigate to the LUN you want to verify (Storage > LUNs).2. Right-click the LUN and click Properties.3. Verify that the state of the LUN is Normal.

If the state is Transitioning, wait for the state to change to Ready before continuing.

Creating storage groups with UnisphereIf you do not have any storage groups created, create them now.Procedure1. In the systems drop-down list on the menu bar, select a system.2. Hosts > Storage Groups.3. Under Storage Groups, select Create.4. In Storage Group Name, enter a name for the Storage Group to replace the default

name.5. Choose from the following:

l Click OK to create the new Storage Group and close the dialog box, orl 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.7. Move the host from Available host to Host to be connected and click OK.


Verifying that each LUN is fully initialized using Unisphere 33

Making LUNs visible to a Windows server or Windows virtual machine with NICsNote


To allow the Windows server access to the LUNs that you created, use Windows ComputerManagement to perform a rescan:Procedure1. Open the Computer Management window (Start > Computer Management).2. Under the Storage tree, select Disk Management.3. From the tool bar menu, select Action > Rescan Disks.

Verifying that Windows Server 2008 native multipath failover (MPIO) sees all pathsto the LUNs

Note

If you have multiple systems connected to the server, you will not be able to tell fromMPIO which paths connect to which system.Procedure1. Select Server Manager > Diagnostics > Device Manager > Disk Drives.2. Right-click any DGC RAID disk device and select Disk Properties.3. In the Multi-Path Disk Device Properties window, verify that all paths to the SPs have

a TPG state of Active/Optimized.

Preparing LUNs to receive dataIf you do not want to use a LUN as a raw disk or raw volume, then before Windows cansend data to a LUN, you must:u Use Unisphere to verify that each new LUN is initialized and to write a signature to it,

as described in the Unisphere online help.u Either create partitions on a basic disk or create the appropriate volumes on a

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

Before a virtual machine can send data to a virtual disk that is a VMFS volume, you mustdo the following:Windows virtual machine1. Write a signature to the VMware virtual disk.2. Either create partitions on a basic disk or create volumes on a dynamic disk.

Sending Windows server and Windows virtual machine diskinformation to the system

If the Unisphere Host Agent is installed on the server, stop and then restart it to send thesystem the operating systems device name and volume or file system information for

34

each LUN that the server sees. Unisphere displays this information in the LUN Properties Host dialog box for each LUN.The Unisphere Server Utility does not send operating system LUN mapping information tothe system, so this procedure is not required.NOTICE

Perform this procedure on your Hyper-V or ESX server.

Stopping the host agent on a Windows serverProcedure1. Log in as the administrator or the equivalent.2. Open the Services pane.

l For Windows 2008 and earlier versions, from the desktop, right-click My Computerand select Manage > Services and Applications > Services; or for Windows 2012,from the desktop, mouse over to the left bottom corner of the taskbar and selectStart, then right-click Computer > Manager > Tools > Services.

The Services pane opens.3. In the Services pane, right-click Navisphere Agent and select Stop. If asked to confirm

your request to stop the agent service, click Yes, and close the Services pane.

Starting the host agent on a Windows serverProcedure1. Log in as the administrator or the equivalent.2. Open the Services pane:

l From the desktop, right-click My Computer and select Manage > Services andApplications > Servicesor

l Select Start > Administrative Tools > Computer Management > Services andApplications > Services.

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

a. Right-click Unisphere Agent and select Properties.The Unisphere Agent Properties dialog box opens.


5. Close the Services pane.ResultsThe host agent will now start automatically at system startup.It may take a few minutes for the host agent to start when:u Applications are using the system

or


Stopping the host agent on a Windows server 35

u 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 UnisphereProcedure1. 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.

Verifying your Windows Server 2008 native multipath failoverconfiguration

If your server has a high-availability configuration, that is, at least one HBA HBA path toeach SP on the system, your environment is enabled for failover and you can proceed toverify your failover configuration for a dual-SP system.If you do not have a high-availability configuration, you have a single SP, and an SPfailure leaves the server without access to the data. If you have a single SP with only oneHBA, your environment is not enabled for failover. An HBA failure leaves the serverwithout access to the data.

Note

Disconnecting a path from the HBA side of a switch causes an HBA failover, whiledisconnecting all paths to an active SP causes the paths to fail over to the other SP.Before you startBefore you store data on LUNs, use the procedure in this section to verify that:u The server can send data to and receive data from the system.

Note

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

u Windows native multipath failover shows the paths from the server to the LUNs thatyou expect for your configuration.

Verifying your Windows Server 2008 native multipath failover configuration (dual-SP)

NOTICE

If you have multiple systems connected to the server, you will not be able to tell fromMPIO which paths connect to which system.This test applies to a server with two single-port HBAs connected through a switch to thesystem SPs.Procedure1. Find an SP in the system with Active/Optimized paths between it and the server:

36

a. Select Computer Management > Device Management > Disk Drives.b. Right-click any DGC RAID disk device and select Disk Properties.c. In the Multi-Path Disk Device Properties window, find a path with a TPG state of

Active/Optimized and determine the system SP for the path from the TPG ID:TPG ID of 1 = SP ATPG ID 2 = SP B

2. Use Unisphere> to determine which LUNs are owned by the SP and record them.After the test, you need to return these LUNs to this SP, which is their original SPowner.

3. Disconnect the cables from all the ports on this SP.4. View the properties window for the disk device, and verify the following path

information:l The paths to the SP from which you disconnected the cables no longer appear in

the paths list.l The TPG state of the paths to the other SP is Active/Optimized, indicating that I/O

continues through the remaining paths and that native failover is working properly.5. Reconnect the cables that you disconnected from the SP.6. For each LUN that was owned by the SP before you disconnected cables from the SP,

use the Unisphere> LUN Properties dialog box to return the LUN to this SP (the LUNsoriginal SP owner).

7. Verify the paths to the SP for which you tested failover:a. Select Computer Management > Device Management > Disk Drives.b. Right-click any DGC RAID disk device and select Disk Properties.c. In the Multi-Path Disk Device Properties window, verify that all paths to the SP

have a TPG state of Active/Optimized.


Verifying your Windows Server 2008 native multipath failover configuration (dual-SP) 37

Copyright 2010-2014 EMC Corporation. All rights reserved. Published in USA.Published November, 2014EMC believes the information in this publication is accurate as of its publication date. The information is subject to change withoutnotice.The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind withrespect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for aparticular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable softwarelicense.EMC, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries.All other trademarks used herein are the property of their respective owners.For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).

38

Documents

Vnx5500 windows connectivity guide