Provisioning a New Windows 2000 Host

 

Topic

Setting up a host environment

Selections

Select a host: Windows 2000

Select a Windows 2000 task: Provisioning a new host

Select a HBA type: Emulex

Select a switch type: McData

 

 

Contents

·             Installing Emulex HBA(s) on a Windows host 4

·             Updating Emulex HBA firmware on a Windows host 6

·             Download the latest Emulex tools and firmware for Windows. 8

·             Installing Emulex HBA driver on Windows host 9

·             Updating Emulex HBA driver forWindows 2000. 12

·             Creating switch zones. 16

·             Adding Symmetrix Devices. 17

·             Mapping Devices within Symmetrix. 22

·             Masking Devices. 27

·             Creating a Device Group.. 31

·             Making LUNs or Devices available to Windows. 33

·             Installing PowerPath software on a Windows 2000 host 34

 


 

Provisioning a new Windows host

This section describes how to setup a new Windows host for the Symmetrix storage management environment. A series of procedures take you from installing HBAs, HBA firmware and drivers, zoning, mapping/masking devices, PowerPath installs, and creating device groups to making LUNs available.

 

 

7Table of Contents

Install/Setup Emulex HBA/Driver Environment on Windows 2000

Using various procedures, this document for Windows, featuring a Emulex HBA environment describes how to install and setup host bus adapters and other aspects of a host environment that deal with managing devices of a Symmetrix storage system. A series of procedures take you from installing HBAs, installing HBA firmware and drivers to updating them for Windows 2000 platforms.

 

 

·        Installing Emulex HBA(s) on a Windows host

 

Overview

These procedures describe how to install a Emulex host bus adapter on a Windows 2000 platform that will interface to Symmetrix storage devices.

 

These procedures are based on content from the following EMC manuals:

  • EMC Host Connectivity Guide for Windows
  • EMC Support Matrix Microsoft Windows 2000

 

You can download these guides from EMC Online Support (registration required): https://support.EMC.com

 

 

1.  

Set jumpers on old models only:

For older HBA models only, jumpers may need to be set: 

 

Set the HBA jumpers as shown in the diagram below to program it for use with the Windows host.  This step does not need to be performed on newer HBAs. 

 

Note:  The LP850-EMC has no user-configurable jumpers.



 

2.  

Install Adapter in card slot

With host system power removed, install the HBA(s) by following the instructions included with your adapter. The adapter installs into a single slot and has no user-configurable jumpers or switches.

 

When choosing an HBA for your host computer, it is important to know which HBA is compatible with its PCI/PCI-X/PCI Express slots.  Certain HBA models have specific voltage requirements or physical limitations that allow them to only work in specific slots. Computers today have several different bus slot types for accepting HBAs.  PCI, PCI-X, PCI-X 2.0, and PCI-Express. PCI slots can be 32-bit and 64-bit (denoted by their 124-pin or 188-pin connectors.)  These slots have plastic “keys” that prevent certain HBAs from fitting into them.  These keys work with the cut-out notches in the HBA edge connecter so that only compatible HBAs will fit into them.  This is done because of the voltage characteristics of the HBA. Inserting a 3.3v HBA into a 5v slot would cause severe damage to both the HBA and the server.  Therefore, the slot keys denote the type of voltage provided by the slot and effectively prevent a voltage incompatible HBA from being inserted.  The following figure shows how PCI slots will appear with their keys and what type of voltage is provided for each slot type.

 

The figure below shows the HBA edge connecters compatible with the PCI slots shown in the figure above.  Note HBA #5 which shows a universal HBA edge connecter.  Universal HBAs are compatible with both 3.3v and 5v PCI slots.

 

Emulex offers HBAs for each bus/slot type available. The following table shows each of the EMC-supported Emulex HBAs, and their respective slot requirements. Be sure to consult both your server user guide and Emulex to ensure that the HBA you want to use is compatible with your server's bus.

 

HBA

PCI spec

BUS length

Power

Slot key

LP7000

PCI 2.2

32-bit

5V

Universal

LP8000

PCI 2.2 (2.1 listed?)

64-bit

5V

Universal

LP850

PCI 2.2

64-bit

5V

Universal

LP9002L

PCI 2.2 

64-bit

3.3V

Universal

LP9002DC

PCI 2.2

64-bit

3.3V

Universal

LP982

PCI-X 1.0a & PCI 2.2

64-bit

3.3V

Universal

LP9802

PCI-X 1.0a & PCI 2.2

64-bit

3.3V

Universal

LP9802DC

PCI-X 1.0a & PCI 2.2

64-bit

3.3V, 5V

3.3V

LP1050/LP1050DC

PCI-X 1.0a & PCI 2.3

64-bit

3.3V, 5V

Universal

LP10000/LP10000DC

PCI-X 1.0a & PCI 2.3

64-bit

3.3V, 5V

Universal

LP1050Ex/LP10000ExDC

PCI Express

x4 lane

3.3v

n/a

LP1150/LP11002

PCI-X 2.0 & PCI 3.0

64-bit

3.3v

3.3v

LPe1150/LPe11002

PCI Express

x4 lane

3.3v

n/a

 

Note that a few HBAs are keyed universally, but require 5 V power (LP7000, LP8000, LP850.) They will fit into a 3.3 V PCI/PCI-X slot, but will not work unless the slot is capable of universal (3.3 V and 5 V) signaling.  Consult your server user guide or manufacturer.  Also, the LP9802DC, while capable of 3.3 V or 5 V signaling operation, fits only into a 3.3 V PCI/PCI-X slot. Remember, some of the older HBAs are tall (also referred to as full-height) and may not fit into a server with a low-profile chassis.  These factors must be considered before implementing your configuration to avoid unnecessary delays and possible equipment swaps or returns.

 

 

3.  

Apply power and boot

Reapply power and allow the system to boot normally.

 

 

 

 

·        Updating Emulex HBA firmware on a Windows host

 

Overview

Refer to release notes provided with the driver for information that might be unique to new driver revisions.

These procedures are based on content from the following EMC manuals:

  • EMC Host Connectivity Guide for Windows
  • EMC Support Matrix Microsoft Windows 2000

 

You can download these guides from EMC Online Support (registration required): https://support.EMC.com

 

 

1.  

Download the firmware

To download the latest firmware:

 

a.     Create a directory that will be used to save the downloaded files.

b.    Open a web browser and access the Emulex Website at http://www.emulex.com.

c.     Click Downloads on the navigation bar on the top of the homepage.

d.    On the next page under Storage and System Supplier Qualified and Supported HBAs, select the EMC link.

e.     On the Support Resources for EMC page, select the link for the correct Emulex HBA model.

f.     On the next page, locate the HBA firmware listing and select the associated Download link.  Download and unzip the file to the directory you created earlier.

 

 

2.  

Close any open applications:

Close all applications prior to this upgrade.  It is not recommended to open any other applications during this upgrade.

 

 

3.  

Boot disk ready:

Ensure that critical files on your local boot disk are backed up as a measure of protection.

 

 

4.  

Select HBAnyware utility:

From the Windows desktop, select Start > Programs > Emulex > HBAnyware.

 

 

5.  

On the screen that appears, select the HBA on the left pane as shown in the example below.

 

 

 

6.  

Select Firmware:

Select the Firmware tab and use the Browse button to locate and select the firmware file downloaded previously.

 

7.  

Download firmware:

On the Firmware tab, click Download to start the firmware upgrade. 

 

When the upgrade is complete, a Download complete message will appear. If there is a dual-channel HBA, or multiple HBAs in the system, select the next HBA and repeat these steps for each HBA.

 

 

 

 

 

·         Download the latest Emulex tools and firmware for Windows

 

Overview

This procedure describes how to download tools and firmware from the Emulex website for the Windows platform.

 

 

1.   

Create save directory:

Create a directory that will be used to save the downloaded files.

 

 

2.   

Access Emulex site:

Open a web browser and access the Emulex Website at http://www.emulex.com.

 

3.   

Select Downloads and EMC:

Click Downloads on the navigation bar on the top of the homepage and on the next page under Storage and System Supplier Qualified and Supported HBAs, select the EMC link.

 

 

4.   

Find HBA link:

On the Support Resources for EMC page, select the link for the correct Emulex HBA model.

 

 

5.   

Locate firmware:

On the next page:

 

a.     Locate the HBA firmware listing and select the associated Download link.  Download and unzip the file to the directory you created earlier.

b.    Locate the Resources panel on the right-hand side of the webpage and select Windows under the Current Drivers heading.
 
On the next page, select the operating system version link under the appropriate driver type column.

 

 

6.   

Select AutoPilot kit and grab:

Select the Download link for the AutoPilot Install Kit and save the file to the directory you created earlier.

 

 

 

·        Installing Emulex HBA driver on Windows host

 

Overview

This procedure describes how to install the latest Emulex driver software on Windows 2000 platforms. When installing or upgrading drivers, be sure to use the latest versions specified by EMC. Review the E-Lab Interoperability Navigator (ESM) for the latest information on approved HBAs and their drivers.

 

The Fibre Channel host adapter driver and related utilities must be installed and configured before Windows can access the EMC disks. This procedure describes how to install the driver using the Emulex AutoPilot Installer.

 

Windows 2000 uses only the SCSIPort driver class.

 

These procedures are based on content from the following EMC manuals:

  • EMC Host Connectivity Guide for Windows
  • EMC Support Matrix Microsoft Windows 2000

 

You can download these guides from EMC Online Support (registration required): https://support.EMC.com

 

 

1.   

Select AutoPilot and install driver:

To install the Emulex HBA driver, use the Emulex AutoPilot Installer as follows:

 

  1. Navigate to the directory containing either the emcfcportkit_<version> and double-click the .exe file. 

  2. Follow the screen prompts to guide you through the installation, accepting all defaults.

    Note: 
    If a previous version of the utility is detected, the screen will display a confirmation prompt to uninstall the current version before continuing.

  3. When the installation is complete, select the Start AutoPilot Installer checkbox (if not already checked) and click Finish.  The AutoPilot Installer program will open displaying a screen similar to the following:


    The AutoPilot Installer program automatically discovers the HBAs in the system.

    Note:  If no HBAs are discovered:

·         Verify the HBA is properly seated into the bus and powered on.  The LEDs should be lit.

·         Verify the HBAs are visible in Computer Management/Device Manager/SCSI and RAID controllers.

  1. Select Next to continue.  A screen similar to the following will appear displaying the available drivers.



  2. For each HBA, use the drop-down menu to select the new driver to be installed and select Next to continue.

  3. On the next screen, select the appropriate answer regarding PowerPath software, and click Next.

    Note:  This question will only appear if you are installing the SCSIPort driver.

  4. On the topology screen that appears, select the topology of the storage network and click Next.

·         Select Arbitrated Loop when directly connected to the array (no Fibre Channel switch).

·         Select Point-to-Point when connected to a SAN (using a Fibre Channel switch).

  1. After installation is complete, a reboot warning will appear as shown below.  Click OK.



  2. Click Next on the AutoPilot Installer window to continue.

  3. On the Summary screen that appears, you can either view or print the driver installation report.  Note that the report is saved in the C:\Program Files\Emulex\AutoPilot Installer\reports.

  4. Click Finish to close the AutoPilot Installer program.

  5. When prompted to restart your computer, click Yes.

    NOTE:  When the AutoPilot Installer installation is complete, there will be new Emulex programs under Start > Programs > Emulex.

 

 

 

 

·        Updating Emulex HBA driver forWindows 2000

 

Overview

This procedure describes how to update Emulex HBA driver software on Windows 2000 platforms. When installing or upgrading firmware and drivers, be sure to use the latest versions specified by EMC. Review the E-Lab Interoperability Navigator (ESM) for the latest information on approved HBAs and their drivers.

 

These procedures are based on content from the following EMC manuals:

  • EMC Host Connectivity Guide for Windows
  • EMC Support Matrix Microsoft Windows 2000

 

You can download these guides from EMC Online Support (registration required): https://support.EMC.com

 

Note: Emulex HBAs must be installed in the server prior to updating the driver.

 

The Fibre Channel host adapter driver and related utilities must be installed and configured before Windows can access the EMC disks. This procedure describes how to update the driver using the Emulex AutoPilot Installer.

 

Windows 2000 uses only the SCSIPort driver class.

 

 

1.   

Grab AutoPilot from  the site:

To update the Emulex HBA driver, use the latest version of the Emulex AutoPilot Installer as follows:

 

a.     Create a directory that will be used to save the downloaded files.

b.    Open a web browser and access the Emulex Website at http://www.emulex.com

c.     Click Downloads on the navigation bar on the top of the homepage.

d.    On the next page under Storage and System Supplier Qualified and Supported HBAs, select the EMC link.

e.     On the Support Resources for EMC page, select the link for the correct Emulex HBA model.

 

f.     Locate the Resources panel on the right-hand side of the webpage and select Windows under the Current Drivers heading.
 
On the next page, select the operating system version link under the appropriate driver type column.

g.    Select the Download link for the AutoPilot Install Kit and save the file to the directory you created earlier.

 

 

2.   

Update the driver:

Update the Emulex HBA driver using the Emulex AutoPilot Installer as follows:

 

a.     Navigate to the directory containing either the emcfcportkit_<version>.exe and double-click the .exe file. 

b.    Follow the screen prompts to guide you through the installation, accepting all defaults.

Note: If a previous version of the utility is detected, the screen will display a confirmation prompt to uninstall the current version before continuing.

 

c.     When the installation is complete, select the Start AutoPilot Installer checkbox (if not already checked) and click Finish. 

The AutoPilot Installer program automatically discovers the HBAs in the system.

Note:  If no HBAs are discovered:

·         Verify the HBA is properly seated into the bus and powered on.  The LEDs should be lit.

·         Verify the HBAs are visible in Computer Management/Device Manager/SCSI and RAID controllers.

d.    Select Next to continue.  A screen similar to the following will appear displaying the available drivers.



e.     For each HBA, use the drop-down menu to select the new driver to be installed and select Next to continue.

f.     On the next screen, select the appropriate answer regarding PowerPath software, and click Next.

Note:  This question will only appear if you are installing the SCSIPort driver.

g.    On the topology screen that appears, select the topology of the storage network and click Next.

·         Select Arbitrated Loop when directly connected to the array (no Fibre Channel switch).

·         Select Point-to-Point when connected to a SAN (using a Fibre Channel switch).

h.     After installation is complete, a reboot warning will appear as shown below.  Click OK.



i.      Click Next on the AutoPilot Installer window to continue.

j.      On the Summary screen that appears, you can either view or print the driver installation report.  Note that the report is saved in the C:\Program Files\Emulex\AutoPilot Installer\reports.

k.     Click Finish to close the AutoPilot Installer program.

l.      When prompted to restart your computer, click Yes.

Note:  When the AutoPilot Installer installation is complete, there will be new Emulex programs under Start > Programs > Emulex.

 

 

 

 

·        Creating switch zones   

 

Overview

For directions specific to McData director and departmental switches, refer to the Connectrix Manager User Guide.

 

You can download these guides from EMC Online Support (registration required): https://support.EMC.com

 

For the Connectrix director class switches using a service processor, refer to the Configuring Zoning section of the Connectrix Manager User Guide.

 

For the departmental switches, not using a service processor, refer to the Labeled Configuring Zoning section of the Connectix Manager Basic User Guide.

 

4.   

Create switch zones

Switch zones define paths between the host HBAs and the Symmetrix array and can be created using the switch management software (refer to the switch documentation).

 

NOTE:  If you are using an HP-UX server with QuickLoop zoning, then you must use port zoning.  Refer to EMC Knowledgebase article emc66355 for more information.

 

Definition -

Zoning is the process by which a single initiator is matched to a single storage array port (FA/SP) to be able to pass info to storage array device.

 

A Zone consists of 2 or more members, with only 1 initiator (HBA) per zone

A Zone is part of a zoneset .

A Zoneset is a collection of zones in a single fabric.

A Zoneset requires activation in order to be updated.

 

 

IMPORTANT:  EMC Recommends single initiator zoning. To reduce the chance of data unavailability in the event that an HBA, switch, or FA Failure,  the host should have at least one primary path and one alternate path to each FA

 

 

5.   

Determine zoning configuration

Follow these steps to determine your zoning configuration:

a.      Determine the FA WWN by entering the following command:

symcfg –sid XXXX list –fa all

b.      Determine the HBA WWN by referencing the OS-specific commands from provisioning a host section.

c.      Determine the number of Paths needed.

d.      Determine the Active Zone name.

The operations above must be performed on both fabrics for all FAs and HBAs.


 

6.   

Verify the HBA is logged in

Solutions Enabler offers a command line utility that will verify what is logged in to a specific Symmetrix FA. Use the following command:

 

symmask –sid SymmID –dir 3c –p 0 list logins

 

Where SymmID is the last four numbers of the Symmetrix serial number, 3c is the FA and 0 is the port on the FA.

 

After verifying that the host is logged in, move on to configuring the host.

 

 

7Table of Contents

 

 

 

 

·        Adding Symmetrix Devices

 

Overview

This procedure explains how to add or create Symmetrix devices from the array’s free physical disk space.

 

This procedure is based on content from the following EMC manual:

  • EMC Solutions Enabler Symmetrix Array Controls CLI Product Guide

 

You can download these guides from EMC Online Support (registration required): https://support.EMC.com.

 

 

1.

Look for free space

To check for available free space before you begin, enter the following command:

 

   symconfigure –sid SymmID list –freespace -units CYLINDERS | MB

 

where:

 

SymmID = The ID of a specific Symmetrix the symconfigure command is to be executed against.

 

For example, to see how much free space is available on a Symmetrix with an ID of  000000012345, execute one of the following commands:

 

symconfigure –sid 12345 list –freespace -units CYLINDERS

 

or

 

symconfigure –sid 12345 list –freespace -units MB

 

2.

Build a command file that will be used to add the device

The create dev command is used to add or create a Symmetrix device. The syntax for this command is:

 

create dev count=n, size=Cylinders,

  emulation=EmulationType,

  config=DeviceConfig,

  [, data_member_count=nn]

  [, remote_config=DeviceConfig, remote_data_member_count=nn, ra_group=n,

    [dynamic_capability=[dyn_rdf | dyn_rdf1_only |dyn_rdf2_only], ]

  [, attribute=ckd_meta | savedev

  [in pool PoolName] [member_state=ENABLE | DISABLE], ]

  [, disk_group_num=nnn, remote_disk_group _num=nnn];

 

where:

count = The number of devices to create.

 

size = The size of the device needed in number of cylinders. In Symmetrix DMX models, a cylinder of an FBA device contains 1920 512-byte blocks, or 0.98 megabytes. In earlier Symmetrix models, a cylinder of an FBA device contains 960 512-byte blocks or, 0.468 megabytes. To calculate the number of cylinders, use one of the following calculations:

 

Blocks ÷ 960

or

(Device size in megabytes) x 10242 ÷ (960 x 512 bytes)

or

(Size in megabytes) x 2.1333

Note: Devices to be used as BCV devices, SRDF devices, or metamembers will need to precisely match corresponding device sizes. Use symdev/sympd show or symdev/sympd list –cyl commands to see relevant device sizes.

 

For additional information about sizing devices in cylinders, refer to Chapter 1 of the Solutions Enabler Symmetrix Array Management CLI Product Guide.

 

emulation = The device emulation type, which currently must be fixed block architecture (FBA), CELERRA FBA, VME512 FBA, or CKD-3380, or CKD-3390 for z/OS environments.

 

config = The desired device configuration type. For possible values, see the Solutions Enabler Symmetrix Array Control CLI Product Guide.

 

data_member_count = The number of data members when creating RAID 5 or RAID 6 devices on a Symmetrix array with Enginuity version 5772 and higher.

The user should set the value to 3 or 7 for RAID 5 (3+1) and RAID 5 (7+1), or  6 or 14 for RAID 6 (6+2) and RAID 6 (14+2).

 

remote_config = The desired remote SRDF configuration (if any). Managing Configuration Changes

remote_data_member_count = The number of remote data members when creating RDF RAID 5 or RAID 6 devices on a Symmetrix array with Enginuity version 5772 and higher. Set the value to 3 or 7 for RAID 5 (3+1) and RAID 5 (7+1) or, 6 or 14 for RAID 6 (6+2) and RAID 6 (14+2).

 

ra_group = The RA group number in the SRDF environment.

 

dynamic_capability = The type of dynamic SRDF device to create. Possible values are:

 

dyn_rdf — Creates a dynamic SRDF device.

dyn_rdf1_only — Creates a dynamic R1 SRDF device.

dyn_rdf2_only — Creates a dynamic R2 SRDF device.

 

The specified dynamic capability will be applied to the local device and the corresponding remote device will be assigned a complementary dynamic capability, according to the following:

 

  Local device     Remote device

  dyn_rdf          dyn_rdf

  dyn_rdf1_only    dyn_rdf2_only

  dyn_rdf2_only    dyn_rdf1_only

 

attribute = The desired device attribute. Possible values are:

 

ckd_meta — When creating a device with an emulation type of CKD-3380 or CKD-3390, this indicates that the device should be a striped metadevice. CKD metadevices must be created in sets of four devices.

 

savedev — When creating a device, this indicates that the device should be a SAVE device. The device will become part of a pool of devices that are used with TimeFinder/Snap for virtual device Snap operations.

 

PoolName = The name of the SAVE device pool. It can be from 1 to 12 alphanumeric characters long and include hyphens ( - ), and underscore ( _ ) characters. The name DEFAULT_POOL is reserved to represent the container of all unpooled devices.

 

member_state = States whether the SAVE device(s) being added should be enabled or disabled in the pool.

Managing Configuration Changes

disk_group_num = When creating a device, this option allows you to specify a disk group. A disk group is a set of physical disks set aside to be used to create devices of the protection level. Disk group usage may improve the performance of some configurations.

 

To see how disk groups are organized in your configuration, use the following commands:

 

symdisk -sid SymmID list -by_diskgroup

 

and

 

symdev -sid SymmID list -diskgroup(nn)

 

remote_disk_group_num = When creating a device, this option allows you to specify a remote disk group.

 

Using a text editor, such as Notepad or the UNIX vi Editor, create a command file that contains one or more create dev commands. (For this procedure, a file named adddevices.cmd is used.)

 

For example, to add four new Symmetrix devices to Symmetrix array 000000012345 as two-way mirrored devices with a size of 1100 cylinders (516 MB) using FBA emulation, and to create the hypers to support the new devices in disk group 1, create a command file that contains the following line:

 

create dev count=4, size=1100, emulation=FBA, config=2-Way-Mir disk_group=1;

 

Note: If the Symmetrix array being used contains an EA, CA, or EF adapter, a value for the mvs_ssid parameter must be provided so any new FBA devices created are not seen as part of an existing subsystem ID group. If that is the case, a command line that looks more like this should be used instead:

 

create dev count=4, size=1100, emulation=FBA, mvs_ssid=1, config=2-Way-Mir disk_group=1;

 

 

3.

Commit the command file used to create the device(s)

Commit the command file created in the previous step (and activate the device creation command) by executing a symconfigure command that looks something like this:

 

symconfigure -sid SymmID -file CmdFile -v -noprompt commit

 

where:

 

SymmID = The ID of a specific Symmetrix the symconfigure command is to be executed against.

 

CmdFile = A file containing one or more create dev commands.

 

For example, to commit the commands in a command file named adddevices.cmd against a Symmetrix with an ID of 000000012345, use the following command:

 

symconfigure -sid 12345 -file adddevices.cmd -v -noprompt commit

 

When this command is executed, you should see output that looks something like this:

 

A Configuration Change operation is in progress. Please wait...

 

    Establishing a configuration change session...............Established.

 

 

    Processing symmetrix 000000012345

    {

      create dev count=4, size=1100 cyl, emulation=FBA, config=2-Way Mir,

        mvs_ssid=0, disk_group=1;

    }

 

    Performing Access checks..................................Allowed.

    Checking Device Reservations..............................Allowed.

    Submitting configuration changes..........................Submitted

    Validating configuration changes..........................Validated.

 

      New symdevs: 0918:091B

    Initiating PREPARE of configuration changes...............Prepared.

    Initiating COMMIT of configuration changes................Queued.

    COMMIT requesting required resources......................Obtained.

    Step 002 of 078 steps.....................................Executing.

    Step 004 of 078 steps.....................................Executing.

    Step 004 of 078 steps.....................................Executing.

 

...

 

    Step 111 of 151 steps.....................................Executing.

    Step 114 of 151 steps.....................................Executing.

    Step 151 of 151 steps.....................................Executing.

    Local:  COMMIT............................................Done.

    Terminating the configuration change session..............Done.

 

The configuration change session has successfully completed.

 

It is important to note that when creating devices there is no impact on I/O activity.

 

 

4.

Verify that the desired devices were created

To verify that the desired devices were created, enter the following command:

 

   symdev –sid SymmID list

 

where:

 

SymmID = The ID of a specific Symmetrix the symdev command is to be executed against.

 

For example, to see if new devices were successfully created on a Symmetrix with an ID of 000000012345, execute the following command:

 

symdev –sid 12345 list

 

The devices that were just created should be displayed at the bottom of the list produced.

 

 

 

7Table of Contents

 

 

 

·        Mapping Devices within Symmetrix

 

Overview

This procedure describes how to map devices within the Symmetrix array. You can map devices to front-end director ports, or a range of devices to consecutive addresses by specifying a starting address.

 

This procedure is based on contents from the following EMC manual:

  • EMC Solutions Enabler Symmetrix Array Controls CLI Product Guide

 

You can download the guide from EMC Online Support (registration required): https://support.EMC.com

 

 

7.  

Identify Symmetrix devices that have not been mapped

Identify Symmetrix devices that have not been mapped to any front-end adapter ports by executing a symdev command that looks like this:

 

symdev –sid SymmID list -noport

 

where:

 

SymmID = The ID of a specific Symmetrix the symdev command is to be executed against.

 

For example, to obtain a list of Symmetrix devices that have not been mapped to a front-end adapter on a Symmetrix with an ID of 000000012345, execute the following command:

 

symdev –sid 12345 list -noport

 

Examine the output produced and identify the Symmetrix devices you want mapped.

 

 

8.  

Identify front-end adapters that are available

Identify the front-end adaptors that are available by executing a symcfg command that looks like this:

 

symcfg –sid SymmID list –dir all

 

where:

 

SymmID = The ID of a specific Symmetrix the symcfg command is to be executed against.

 

For example, to obtain a list of front-end adapters available on a Symmetrix with an ID of  000000012345, execute the following command:

 

symcfg -sid 12345 list -dir all

 

When this command is executed, you should see output that looks something like this:

 

Symmetrix ID: 000000012345

 

           S Y M M E T R I X    D I R E C T O R S

 

    Ident  Symbolic  Numeric  Slot  Type          Status

 

    DF-1A     01A       1       1   DISK          Online

    DF-2A     02A       2       2   DISK          Online

    DF-15A    15A      15      15   DISK          Online

    DF-16A    16A      16      16   DISK          Online

    DF-1B     01B      17       1   DISK          Online

    DF-2B     02B      18       2   DISK          Online

    DF-15B    15B      31      15   DISK          Online

    DF-16B    16B      32      16   DISK          Online

    FA-1C     01C      33       1   FibreChannel  Online

    FA-2C     02C      34       2   FibreChannel  Online

    FA-15C    15C      47      15   FibreChannel  Online

    FA-16C    16C      48      16   FibreChannel  Online

    RF-1D     01D      49       1   RDF-BI-DIR    Online

    RF-2D     02D      50       2   RDF-R1        Online

    RF-15D    15D      63      15   RDF-R1        Online

    RF-16D    16D      64      16   RDF-BI-DIR    Online

 

Examine the output produced and identify the front-end adapter to which you want  Symmetrix devices mapped.

 

 

9.  

Examine the front-end adaptor and port for available LUN Numbers

Identify the LUN numbers that are available for a specific front-end adapter and port by executing a symcfg command that looks like this:

 

symcfg –sid SymmID list –dir Adapter –p Port –address -available

 

where:

 

SymmID = The ID of a specific Symmetrix the symcfg command is to be executed against.

 

Adapter = The ID of the front-end adaptor that device information is to be collected for.

 

Port = The port number that device information is to be collected for.

 

For example, to obtain device information for adapter 16C, port 0 on a Symmetrix with an ID of 000000012345, execute the following command:

 

symcfg -sid 12345 list -dir 16c -p 0 -address -available

 

When this command is executed, you should see output that looks something like this:

 

Symmetrix ID: 000000012345

 

           Director                 Device Name    Attr     Address

    ---------------------- ----------------------- ---- --------------

    Ident   Symbolic  Port Sym   Physical               VBUS  TID  LUN

    ------  --------  ---- ----  -----------------      ----  ---  ---

    FA-16C  16C       0    0100  Not Visible               0   00  000

                           0101  Not Visible               0   00  001

                           0102  Not Visible               0   00  002

                           0103  Not Visible               0   00  003

                           0104  Not Visible               0   00  004

                           0105  Not Visible               0   00  005

...

                           08DC  Not Visible        (M)    0   00  0CC

                           -     AVAILABLE                 0   00  0CD *

                           0520  Not Visible        (M)    0   00  100

...

                           07CD  Not Visible               0   00  143

                           -     AVAILABLE                 0   00  144 *

                           07D1  Not Visible               0   00  200

...

                           0850  Not Visible               0   00  27F

                           -     AVAILABLE                 0   00  280 *

                           068C  Not Visible               0   00  68C

...

                           0697  Not Visible               0   00  697

                           -     AVAILABLE                 0   00  698 *

    Total                  ----

    Mapped Devices:         413

    Including Metamembers:  638

    Available Addresses:   3281 (s)

 

 

Legend for Available address:

 

(*): The VBUS, TID, LUN address values represent a gap in the

     address assignments or are the next available address in

     the run

(s): The Available Addresses for a director are shared among

     its ports (shared)

 

Note: An asterisk (*) in the LUN column represents an available LUN number or the next available range of numbers.

 

 

10.  

Build a command file that will be used to map devices in the Symmetrix array

The map dev command is used to map a Symmetrix device to a front-end director port. The syntax for this command is:

 

map dev SymDevName [:SymDevName] to dir DirectorNum:PortNum

[starting][target=ScsiTarget,] lun=ScsiLun

[, vbus=FibreVbus]

[, device_number=ckd_device_number]

[, awwn=awwn|wwn=wwn|iscsi=iscsi];

[, masking host_lun=lun | dynamic_lun];

 

where:

target = The SCSI target ID (hex value).

 

lun = The SCSI logical unit number (hex value).

 

dynamic_lun = The dynamic LUN addressing scheme. LUN addressing is assigned based on what may already be in use for that host HBA.

 

vbus = The virtual bus address for mapping to an FA port if using volume set addressing.

 

device_number = The CKD device number, when mapping a CKD device to a z/OS host.

 

awwn = The user-given name or alias WWN of a host HBA port, if updating a VCM database.

 

wwn = The unique 64-bit World Wide Name (WWN) identifier for an HBA port, if updating a VCM database.

 

iscsi = The iSCSI name, if updating a VCM database.

 

Note: For HP-UX operating systems, you must specify a target number, a virtual bus number, and LUN number. For Sun, AIX, and Windows, the target number should be 0 in a switched fabric environment.

 

Using a text editor, such as Notepad or the UNIX vi Editor, create a command file that contains one or more map dev commands. (For this procedure, a file named mapdevices.cmd is used.)

 

For example, to map Symmetrix device 000C to port 0 of front-end adapter 16C and assign it the LUN number 0CD, create a command file that contains the following lines:

 

map dev 000C to dir 16C:0 target=0, lun=0CD;

 

11.  

Commit the command file used to map devices

Commit the command file created in the previous step (and activate the map devices command specified) by executing a symconfigure command that looks something like this:

 

symconfigure -sid SymmID -file CmdFile -v -noprompt commit

 

where:

 

SymmID = The ID of a specific Symmetrix the symconfigure command is to be executed against.

 

CmdFile = A file containing one or more map dev commands.

 

For example, to commit the commands in a command file named mapdevices.cmd against a Symmetrix with an ID of 000000012345, use the following command:

 

symconfigure -sid 12345 –file mapdevices.cmd –v –noprompt commit

 

When this command is executed, you should see output that looks something like this:

 

A Configuration Change operation is in progress. Please wait...

 

    Establishing a configuration change session...............Established.

    Processing symmetrix 000000012345

    {

      map dev 000C to dir 16C:0 lun=0CD;

    }

 

    Performing Access checks..................................Allowed.

    Checking Device Reservations..............................Allowed.

    Submitting configuration changes..........................Submitted

    Locking devices...........................................Locked.

    Validating configuration changes..........................Validated.

    Initiating PREPARE of configuration changes...............Prepared.

    Initiating COMMIT of configuration changes................Queued.

    COMMIT requesting required resources......................Obtained.

    Step 003 of 012 steps.....................................Executing.

    Step 003 of 012 steps.....................................Executing.

    Step 009 of 012 steps.....................................Executing.

    Local:  COMMIT............................................Done.

    Terminating the configuration change session..............Done.

 

The configuration change session has successfully completed.

 

 

12.  

Rediscover the SYMAPI database

After performing the proper host procedures to update the host view, you need to complete host addressing by making sure that the host address is recognized in the SYMAPI view. To update the SYMAPI database, execute the following command:

 

symcfg discover

 

This may takes some time; please wait for completion.

 

 

13.  

Verify that the device mapping was successful

To verify that the device specified was successfully mapped to the front-end adapter, port, and LUN specified, execute the following command:

 

symdev –sid SymmID show SymDevName

 

where:

 

SymmID = The ID of a specific Symmetrix the symdev command is to be executed against.

 

SymDevName = The specific Symmetrix device that detailed information is to be displayed for.

 

For example, to display detailed information about Symmetrix device 000C on a Symmetrix with an ID of 000000012345, execute the following command:

 

symdev –sid 12345 show 000C

 

Scan the output produced and examine the section titled “Front Director Paths”. If the Symmetrix device was successfully mapped, you should see something that looks like this:

 

    Front Director Paths (1):

        {

        ------------------------------------------------------------------

                             POWERPATH  DIRECTOR   PORT             LUN

                             --------- ----------  ---- -------- ---------

        PdevName             Type      Type Num    Sts  VBUS TID SYMM Host

        ------------------------------------------------------------------

        Not Visible          N/A       FA   16C:0  RW   000  00  0CD  N/A

        }

 

 

 

 

 

·        Masking Devices

 

Overview

Masking is an operation that is used to present devices to a specific host bus adapter (HBA) and is typically utilized when control is needed over which devices are made available to hosts. In a Symmetrix environment, masking defines a relationship between one or more Symmetrix devices, front-end director ports, and HBAs that reside at a host.

 

To perform masking, you will need access to a host that has the Solutions Enabler base installed along with the device masking portion licensed. This host will need to have a fiber path to the Symmetrix and be able to see the VCM device and a gatekeeper.

 

This procedure is based on contents from the following EMC manual:

  • EMC Solutions Enabler Symmetrix Array Controls CLI Product Guide

 

You can download these guides from EMC Online Support (registration required): https://support.EMC.com

 

 

 

 

 

14.  

Verify that the device(s) to be masked have been mapped

To verify that the device(s) to be masked have been mapped to a front-end director, port, and LUN, execute the following command:

 

symdev –sid SymmID show SymDevName

 

where:

 

SymmID = The ID of a specific Symmetrix the symdev command is to be executed against.

 

SymDevName = The specific Symmetrix device that detailed information is to be displayed for.

 

For example, to display detailed information about Symmetrix device 000C on a Symmetrix with an ID of 000000012345, execute the following command:

 

symdev –sid 12345 show 000C

 

Scan the output produced and examine the section titled “Front Director Paths”. If the Symmetrix device has been mapped, you should see something that looks like this:

 

Front Director Paths (1):

    {

    ----------------------------------------------------------------------

                             POWERPATH  DIRECTOR   PORT             LUN

                             --------- ----------  ---- -------- ---------

    PdevName                 Type      Type Num    Sts  VBUS TID SYMM Host

    ----------------------------------------------------------------------

    \\.\PHYSICALDRIVE7       N/A       FA   16C:0  RW   000  00  016  000

    }

 

Repeat this step for every device to be masked. If a device to be masked has not been mapped, you must map it to a front-end director, port, and LUN before continuing with this procedure.

 

 

15.  

Get the World Wide Name (WWN) for the Host Bus Adapter (HBA) the device(s) are to be masked to

There are several tools that can be used to obtain the WWN of installed HBAs. For example, Emulex provides a utility called HBAnywhere that can be used to obtain this information. If Solutions Enabler has been installed on a host, the syminq hba command can be used as well.

 

 

Using either the appropriate tools on the host or the configuration documentation where this information was recorded earlier, obtain the WWN for the HBA that one or more devices are to be masked to.

 

 

16.  

Mask the appropriate devices in the Symmetrix array

The symmask command is used to mask one or more devices to a specified HBA/director-port channel. The syntax for this command is:

 

symmask -sid SymmID -wwn wwn|-awwn awwn|-iscsi iscsi |-aiscsi aiscsi

add devs StartSymDev:EndSymDev|SymDevName|SymDevName,,,...

-dir DirNumber -p PortNumber [-noprompt]

 

where:

 

SymmID = The ID of a specific Symmetrix the symmask command is to be executed against.

 

wwn= A valid World Wide Name (WWN).

 

awwn = A user-given name in an ASCII WWN format.

 

iscsi = A valid iSCSI name.

 

aiscsi = A user-given name or an alias iSCSI name.

 

StartSymDev = The first Symmetrix device name in a range.

 

EndSymDev = The last Symmetrix device name in a range.

 

SymDevName = One or more specific Symmetrix device names.

 

DirNumber = A specific director number designation.

 

PortNumber = A specific port number designation.

 

Note: When masking metadevices, only the Symmetrix device name that is designated as the metadevice head should be specified (via the SymDevName parameter).

 

For example, to mask Symmetrix devices 000C and 000D, (which have already been mapped to port 0 of front-end adapter 16C on a Symmetrix with an ID of 000000012345), so that they can only be accessed by an HBA that has the World Wide Name 10:00:00:00:c9:6c:c8:12, execute the following command:

 

symmask –sid 12345 –wwn 10000000c96cc812 add devs 000C:000D -dir 16C -p 0

 

If Symmetrix devices 000C and 000D were masked to a different HBA earlier, the following message will be displayed when this command is executed:

 

The following devices are already assigned in at least one entry:

 

000C 000D

 

Would you like to continue (y/[n])?

 

If you indicate that the mask operation is to continue, the devices will be masked for multiple HBAs. (If the -noprompt option is specified, the masking operation will execute automatically without requiring user intervention.)

 

 

17.  

Verify that the device masking was successful

To verify that the device(s) specified were successfully masked, execute the following command:

 

symmaskdb –sid SymmID list database –dir DirNumber –p PortNumber

 

where:

 

SymmID = The ID of a specific Symmetrix the symmask command is to be executed against.

 

DirNumber = The specific director number the Symmetrix device was masked for.

 

PortNumber = The specific port number the Symmetrix device was masked for.

 

For example, to display a list of devices that have been masked for port 0 of front-end adapter 16C on a Symmetrix with an ID of  000000012345, execute the following command:

 

symmaskdb -sid 12345 list database –dir 16C –p 0

 

When this command is executed, you should see output that looks something like this:

 

Symmetrix ID            : 000000012345

 

Database Type           : Type6

Last updated at         : 03:55:26 PM on Tue Mar 31,2009

 

Director Identification : FA-16C

Director Port           : 0

 

                               User-generated

Identifier        Type   Node Name        Port Name         Devices

----------------  -----  ---------------------------------  ---------

10000000c96cc812  Fibre  10000000c96cc812 10000000c96cc812  000C:000D

 

 

18.  

Back up the VCMDB

The symmaskdb backup command is used to create a backup copy of the Device Masking VCMDB. The syntax for this command is:

 

symmaskdb -sid SymmID backup –file BkupFileName -noprompt

 

where:

 

SymmID = The ID of a specific Symmetrix the symmaskdb command is to be executed against.

 

BkupFileName = The name of the file to be used to store the backup copy of the Device Masking VCMDB created. (You cannot reuse backup file names; a new file name must be provided each time this command is executed.) The backup copy will be stored in the file specified and that file will be written to the current directory (i.e., the directory that this command is executed from).

 

For example, to store a backup copy of an existing Device Masking VCMDB for a Symmetrix with an ID of 000000012345 in a file named BackupDevMaskDB_1, execute the following command:

 

symmaskdb –sid 12345 backup –file BackupDevMaskDB_1 –noprompt

 

When this command is executed, you should see a message that looks something like this:

 

Symmetrix SymMask database backed up to file BackupDevMaskDB_1

from Symmetrix 000000012345

 

 

19.  

Refresh the Symmetrix director with VCMDB data

Update the Symmetrix array with the configuration changes by performing a director refresh operation. This causes the Symmetrix director to refresh its WWN/iSCSI-related profile tables in cache with the content data from the device masking VCMDB.

 

The symmaskdb refresh command is used to force a Symmetrix director to refresh its profile tables with the contents of the Device Masking VCMDB. The syntax for this command is:

 

symmask -sid SymmID refresh -noprompt

 

where:

 

SymmID = The ID of a specific Symmetrix the symmaskdb command is to be executed against.

 

For example, to force a Symmetrix director to refresh its profile tables with the contents of the Device Masking VCMDB for a Symmetrix with an ID of  000000012345, execute the following command:

 

symmask –sid 12345 refresh –noprompt

 

When this command is executed, you should see a message that looks something like this:

 

Symmetrix FA directors updated with contents of SymMask Database 000000012345

 

! Caution: Before executing this command, make sure no HBAs are accessing devices in the masked channel (in other words, make sure that no application or user activity is taking place on the HBAs that are about to be refreshed). !

 

 

20.  

Run the appropriate configuration method on all affected hosts or reboot all affected hosts

Many host operating systems provide a utility that can be used to automatically configure devices that have been made available to a system. For example, in Windows you can use the Device Manager to scan for hardware changes; with AIX you can execute the cfgmgr command. Before masked devices will be made visible to a host, this utility must be run on all hosts that have had devices added or removed (via masking changes). If no such utility exists, the affected hosts should be rebooted.

 

Refer to the online help available with each host operating system for information on how to perform online configuration changes or a reboot operation.

 

 

21.  

Rebuild the Symmetrix configuration database on all appropriate hosts/management servers

Any time you reconfigure a Symmetrix array by adding or removing device masking information, the SYMAPI configuration database should be updated on all affected hosts/management servers that are running Solutions Enabler. This is done by executing the following command:

 

symcfg discover

 

When executed, this command interrogates all SCSI devices available; therefore, it can take a significant amount of time to complete.

 

 

 

 

 

 

·        Creating a Device Group

 

Overview

A collection of devices can be assigned to a named group to provide a more manageable single object to query status and impart blanket control operations. Device groups and composite group definitions are created locally through an attached host.

 

This procedure is based on content from the following EMC manual:

  • EMC Solutions Enabler Symmetrix Array Management CLI Product Guide

 

You can download the guide from EMC Online Support (registration required): https://support.EMC.com.

 

 

 

22.  

Examine device groups you already have

Since device group names must be unique, before you attempt to create a new one you should find out what device groups have already been created. To view a list of device groups that have already been created, execute the following command:

 

symdg list

 

 

23.  

Create a new device group

The symdg create command is used to create a new device group. The syntax for this command is:

 

symdg create DgName [-type REGULAR | RDF1 | RDF2 | RDF21]

 

where:

 

DgName = The name to assign to the device group.

 

For example, to create a device group, assign it the name TFgroup, and specify that it is a REGULAR device group, execute a symdg create command that looks like this:

 

symdg create TFgroup –type REGULAR

 

 

24.  

Add Symmetrix devices to the group

The symld command is used to add devices to an existing device group. Individual devices can be added by specifying either the physical device name (add pd) or the Symmetrix device name (add dev), as follows:

 

symld -g TFgroup add pd /dev/rdsk/c4t0d0s2
symld -g TFgroup -sid 12345 add dev 000C

A contiguous set of devices can be added to a device group by executing a symld command that looks more like this:

 

   symld -g TFgroup –sid 12345 addall –RANGE 000C:000E

(In this example, Symmetrix devices on Symmetrix array 000000012345 were used.)

 

On the other hand, BCV devices can be added to a device group by executing a symbcv command that looks like this:

 

symbcv -g TFgroup -sid 12345 associate dev 001C

 

Keep in mind that all devices added to a device group must be part of the same Symmetrix array. (Composite groups are used to group devices that reside on different Symmetrix arrays.)

 

25.  

Verify the device group creation

To verify that the device group was successfully created and that the appropriate devices were added to it, execute the following command:

 

symdg show DgName

 

where:

 

DgName = The name that has been assigned to the device group.

 

For example, to verify that a device group named TFgroup was created and the appropriate devices were assigned to it, execute the following command:

 

symdg show TFgroup

 

When this command is executed, you should see output that looks something like this:

 

Group Name:  TFgroup

 

    Group Type                                   : REGULAR

    Device Group in GNS                          : No

    Valid                                        : Yes

    Symmetrix ID                                 : 000000012345

    Group Creation Time                          : Mon Mar 23 08:50:17 2009

    Vendor ID                                    : EMC Corp

    Application ID                               : SYMCLI

 

    Number of STD Devices in Group               :    3

    Number of Associated GK's                    :    0

    Number of Locally-associated BCV's           :    0

    Number of Locally-associated VDEV's          :    0

    Number of Locally-associated TGT's           :    0

    Number of Remotely-associated VDEV's(STD RDF):    0

    Number of Remotely-associated BCV's (STD RDF):    0

    Number of Remotely-associated TGT's(TGT RDF) :    0

    Number of Remotely-associated BCV's (BCV RDF):    0

    Number of Remotely-assoc'd RBCV's (RBCV RDF) :    0

    Number of Remotely-assoc'd BCV's (Hop-2 BCV) :    0

    Number of Remotely-assoc'd VDEV's(Hop-2 VDEV):    0

    Number of Remotely-assoc'd TGT's (Hop-2 TGT) :    0

 

    Standard (STD) Devices (3):

        {

        --------------------------------------------------------------------

                                                      Sym               Cap

        LdevName              PdevName                Dev  Att. Sts     (MB)

        --------------------------------------------------------------------

        DEV001                N/A                     000C      RW      1031

        DEV002                N/A                     000D      RW      1031

        DEV003                N/A                     000E      RW      1031

        }

 

 

 

 

·        Making LUNs or Devices available to Windows

 

Overview

This procedure describes how to make the devices or LUNs available or visible to a Windows 2000 or Windows Server 2003 host. It describes how to use the format command to label and partition devices.

 

This procedure is based on content from the following EMC manual:

  • EMC Host Connectivity Guide for Windows

 

You can download the guide from EMC Online Support (registration required): https://support.EMC.com

 

Note and Caution: If your host system cannot see the devices, it may necessary to do a disk or device scan of the I/O bus. If you must, at an appropriate low-peak time in your production environment, apply the necessary operating system native commands, to perform a device scan (discover) to make the devices visible to the host workstation. This might take a few minutes or so to execute. Be sure you follow your operating system specific administrators guide and/or known site procedures for this operation, as scanning devices can cause pauses and crashes to other operational processes running on this host. If you can and prefer, a reboot will also accomplish the same thing (device discovery). The following steps are provided only as a general or possible guide and not meant to supersede your site preferences.

 

 

26.  

Scan for new devices:

The host can discover and identify the new connected devices in the storage array using the following actions:

 

a.      Right-click on My Computer on the Windows desktop and click Manage.

b.      Under System Tools, select Device Manager.

c.      Select and right-click Disk drives and click Scan for hardware changes.

 

 

27.  

Verify LUNs/devices visible for PowerPath:

If you have PowerPath installed, use the following PowerPath commands to verify that the new devices are seen by PowerPath:

 

powermt config

powermt display dev=all

 

 

 

7Table of Contents

 

 

·        Installing PowerPath software on a Windows 2000 host

 

Overview

This procedure describes how to install PowerPath on a Windows 2000 host.

 

Note: This procedure is specific to the installation of PowerPath versions 4.5 to 5.0, which is the current shipping version for Windows 2000 hosts.  For instructions on installing older versions of PowerPath, refer to the applicable PowerPath installation manual available on PowerLink.

 

This procedure is based on content from the following EMC manual:

  • PowerPath for Windows Installation and Administration Guide

 

You can download the guide from EMC Online Support (registration required): https://support.EMC.com

 

You must be logged in as the Local System Administrator to proceed.

 

Verify the following prior to the installation of PowerPath:

 

·         Review the patch ReadMe files to determine which patches (if any) you want to install after PowerPath, and whether those patches have any added prerequisites that must be met before you install PowerPath.

·         Determine if the PowerPath software you are installing requires the removal or presence of a previous version of PowerPath.  Some full versions require the previous version to be removed while others do not.  Also, some patches require the full version to be present while others require it to be removed.  Refer to the PowerPath Release Notes and/or PowerPath patch readme files for your specific version to determine what needs to be present/removed and if and when a reboot is necessary in order to install your specific PowerPath software version and/or patch. These documents are available on http://support.EMC.com.

 

Note: A “failed redundancy” state can occur if PowerPath is installed on a host with mirrored disks. This state only happens if disk management applications (that use the dmadmin service) are running when PowerPath is installed. To prevent this, close all disk management applications (including diskmgmt.msc and diskpart.exe) and stop the dmadmin service before installing PowerPath.

 

If applicable, stop all I/O and close all applications that access storage devices.

 

 

28.  

Verify single device paths:

Ensure that there is only one logical connection per logical device. If necessary, disconnect all additional HBAs/NICs other than the primary. 

 

Note: Doing this prevents the host from seeing the same LUN twice before PowerPath is configured.

 

 

29.  

Insert the PowerPath CD-ROM:

Insert the PowerPath installation CD in the CD-ROM drive and begin the installation. If autoplay is enabled, your browser launches and displays the Getting Started page. You can install the software from the Installation section by clicking the appropriate link for your operating system. Then either:

 

  • Select Run this program from its current location and click OK to proceed with the installation.

 

  • Select Run from the Start menu if autoplay is not enabled.

 

 

30.  

Begin Install:

In the Run window, either browse to or enter the name of the PowerPath installation program and click OK.

 

 

31.  

Continue Install:

Complete the information as prompted on the next four screens.

 

 

32.  

Select your options:

Use the Custom Setup screen to configure PowerPath support for EMC Invista devices and/or third party arrays, and to install PowerPath in a directory other than the default directory (if desired).

 

Note: It’s best to install PowerPath in the default directory as no additional action is required to install in the default directory.

 

If you want PowerPath to support Invista devices, do not have third party arrays, and are going to install PowerPath in its default directory (recommended), click Next and skip the remainder of this step to continue with the next step below.

 

a.     PowerPath support for Invista devices is enabled by default.  If this host is not connected to an Invista system, select This feature will not be available from the drop down list.

b.    If you intend to use PowerPath on a third party array, select This feature will be installed on local hard drive. from the drop down list for that array.  You can select multiple array types.

c.     To install PowerPath in a different (non-default) directory, click Change.  The setup wizard prompts you to browse to your destination folder. Select the destination folder, and click OK.

CAUTION:  Do not specify the Windows System directory for your system (specified by the %SYSTEMROOT% environment variable). PowerPath will not function correctly if it is installed in this directory.

d.    Click Next.

 

 

33.  

Continue Install:

In the Ready to Install the Program dialog box, click Install.

 

Note: If you do not already have a license in the registry, the EMC Licensing Tool displays.

 

 

34.  

Register PowerPath

When prompted by the EMC Licensing Tool, enter your PowerPath registration number in the License Key field.  Click Add and then OK.

 

Note: The PowerPath registration number is printed on the License Key Card, which was delivered with the PowerPath media kit.  

 

Caution: Failing to enter a registration number will result in the installation of PowerPath SE, which is the default policy without a valid PowerPath license. If you fail to enter the registration number during installation, it can be entered at a later point.

 

 

35.  

Finish:

Click Finish in the next dialog box and when prompted to reboot the host, click No.

Instead, from the Start menu, select Shut Down and then click OK.

 

 

36.  

Reconnect other I/O interfaces:

Reconnect the additional HBAs/NICs, hubs, switches, etc. that you disconnected earlier.

 

37.  

Power up boot:

Power up the Windows system. After reboot PowerPath is fully configured with multiple paths to logical devices at boot up.

 

38.  

Check for patches

 

If necessary, install any PowerPath patches from the following URL:

 

http://powerlink.emc.com

 

Note: A readme file that explains how to install the patch that accompanies every patch release.  This file will also state whether you need to reboot the host after the installation of the patch.

 

 

39.  

Verify PowerPath sees new paths

The operating system must recognize new paths before PowerPath can do so. Normally, no action is needed; the operating system detects new paths automatically. Depending on the type of HBA installed, you may have to scan for hardware changes in the device manager.  Alternately, reboot.

 

To verify that PowerPath sees all new HBAs and paths to storage devices, use the following command in the PowerPath utility:

 

powermt display dev=all

 

To test and validate any new path(s) with PowerPath functionality, enter:

 

powermt restore