Provisioning a New Linux Host

 

Topic

Setting up a host environment

Selections

Select a host: Linux

Select a Linux task: Provisioning a new host

Select a HBA type: Emulex

Select a switch type: Brocade

 

 

Contents

·             Installing Emulex HBA(s) on a Linux Host 4

·             Updating Emulex HBA firmware for Linux. 5

·             Installing an Emulex HBA driver on a Linux v2.6.x kernel 11

·             Installing an Emulex driver on a Linux v2.4.x kernel 18

·             Determine WWN of new HBA for Linux. 27

·             Creating switch zones. 27

·             Adding Symmetrix Devices. 29

·             Mapping Devices within Symmetrix. 33

·             Masking Devices. 38

·             Creating a Device Group.. 42

·             Making LUNs or Devices available to Linux. 44

·             Installing PowerPath software on a Linux host 47

 


 

Provisioning a new Linux host

This document for Linux describes how to setup a new host for the Symmetrix storage management environment. A series of procedures take you from installing HBAs, HBA firmware and drivers, zoning, mapping/masking devices, to configuring kernel files and LUNs.

 

Install/Setup Emulex HBA/Driver Environment on Linux

Using various procedures, this section for Linux, 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 storage system. A series of procedures take you through installing HBAs, HBA firmware and drivers.

 

·              Installing Emulex HBA(s) on a Linux Host

 

Overview

This procedure describes how to install Emulex HBAs on a Linux host.

 

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

  • EMC Host Connectivity Guide for Linux
  • EMC Support Matrix Linux

 

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

 

 

1.   

Set Jumpers on adapter board

Review your host computer documentation for slot recommendations that meet or exceed the HBA capabilities.

 

Set the HBA jumpers as shown in the figure below to enable it for use with the Intel-based Linux host.

 

 

 

2.   

Install Adapter in card slot

With host system power off, install the HBA(s) by following the instructions included with your adapter. The adapter installs into a single slot PCI bus.

 

Repeat the installation steps for each server in which you are installing Fibre Channel HBAs.

 

 

3.   

Apply power and boot

Reapply power and allow the system to boot normally.

 

 

 

 

 

 

 

7Table of Contents

 

·        Updating Emulex HBA firmware for Linux

 

Overview

This procedure describes how to intall the appropriate firmware for an Emulex HBA on the Linux platform. 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 Linux
  • EMC Support Matrix Linux

 

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

 

Each Emulex Fibre Channel controller has a flash upgradeable firmware and boot BIOS. In most instances, it is necessary to keep only the firmware up to date, since the BIOS is applied only when using connected storage as a boot device.

 

Note: If you are upgrading the firmware and BIOS, you must update the firmware first as it may contain an older BIOS version, which can be updated separately later.

 

Depending on the Linux platform, that you are running, you may already have the appropriate driver included in the Linux Distribution. Prior to updating to the latest driver that is distributed on the Emulex Website, please review the E-Lab Interoperability Navigator (ESM) for specific qualified kernel versions and distributions.  The support stated in the E-Lab Interoperability Navigator (ESM) supersedes versions listed in this document.

 

 

1.   

Download the firmware:

Obtain the latest firmware from the Emulex website at http://www.emulex.com/ts/docoem/framemc.htm.

 

Include the kernel source/development package and the gcc complier tools during the installation. If these tools are not installed, then the RPM installation will fail and the driver will not be installed.

 

Each Emulex Fibre Channel controller has a flash upgradeable firmware and BIOS. In most instances, it is necessary to keep only the firmware up to date, since the BIOS is applied only when using connected storage as a boot device.

 

From this site, select the appropriate file for your adapter.  The files are typically in a .zip file that contains different combinations of firmware and BIOS images. Extract the downloaded file to a diskette, and refer to the included readme.txt to determine which filename image to use.    If you are planning to boot from an EMC storage array, you need to use the file that includes the boot BIOS. Select the boot BIOS under the BootBIOS/FCode link for your HBA.

Either of two methods can be used to update the firmware and boot BIOS:

 

  • METHOD ONE – Using lputil at the command line.  Updating the HBA Firmware and HBA boot BIOS with lputil.

  • METHOD TWO – Booting from a DOS bootable diskette and using the lp6dutil utility.

 

 

METHOD ONE - Using lputil at the command line:

 

Update the HBA Firmware with lputil as follows:

 

The lputil utility is dependent upon the existence of the Emulex driver; therefore, the operating system and the Emulex driver must be installed prior to using lputil.  The lputil utility is included in the Emulex Application Kit along with the HBA API and HBAnyware.

 

a.     Download the Emulex Application Kit from the EMC-approved section of the Emulex website (refer to link above).

b.    Copy the appropriate firmware file from the EMC-approved section of the Emulex website to the appropriate directory, /usr/sbin/lpfc.

The following table lists the HBA models and the name of the corresponding firmware files:

HBA Model

Firmware File

LP982-E

 

lfbXXX.all (where XXX is the version)

Example: lfb191a1.all

LP9002-E

 

cdcXXX.all (where XXX is the version)

Example: cdc392a2.all

LP9802-E

hdXXX.all (where XXX is the version)

Example: hd191a1.all

LP9802DC-E

 

hfXXX.all (where XXX is the version)

Example: hf191a1.all

LP1050-E

 

mfXXX.all (where XXX is the version)

Example: mf191a1.all

LP1050DC-E

 

mfXXX.all (where XXX is the version)

Example: mf191a1.all

LP1050EX-E

 

mfXXX.all (where XXX is the version)

Example: mf191a1.all

LP10000-E

tdXXX.all (where XXX is the version)

Example: td191a1.all

LP10000DC-E

 

tdXXX.all (where XXX is the version)

Example: td191a1.all

LP10000EXDC-E

 

tdXXX.all (where XXX is the version)

Example: td191a1.all

LP101-E

 

embXXX.all (where XXX is the version)

Example: emb191a1.all

LPe111-E

 

ymXXX.all (where XXX is the version)

Example: ym250a8.all

LPe1150-E

 

wfXXX.all (where XXX is the version)

Example: wf250a4.all

LPe11002-E

 

zfXXX.all (where XXX is the version)

Example: zf210a7.all

LP1150-E

 

jfXXX.all (where XXX is the version)

Example: jf250a4.all

LP11002-E

 

bfXXX.all (where XXX is the version)

Example: bf250a4.all

LP1005DC Mezzanine for

HPQ Blade Servers

mfXXX.all (where XXX is the version)

Example: mf191a2.all

LP1005-HP Mezzanine for HPQ Blade Servers

zfXXX.all (where XXX is the version)

Example: zf250a8.all

LP1005DC Mezzanine for

IBM Blade Servers

mfXXX.all (where XXX is the version)

Example: mf190a5.all

LP1005BC Mezzanine

for IBM Blade Servers

bfXXX.all (where XXX is the version)

Example: bf210a10.all

 

Each firmware file contains four files. The naming scheme of the files follows the format as shown in the example below for the LP9002 v3.92a2 firmware.


cdc392a2.dwc = contains the firmware with combination boot

cdc392a2.awc = contains the firmware with loader and combination boot

cd392a2.dwc = contains the firmware with no boot code

cd392a2.awc = contains the firmware with loader, no boot code

c.     Start the firmware update utility:

 

cd /usr/sbin/lpfc
./lputi
l

 

d.    Select Option 3 – Firmware Maintenance.

e.     Select the number of the adapter to update.

f.     Select Option 1 – Load Firmware Update.

g.    Enter the full name of the image file (as shown in the table above; for example, td190a4.all) and press Enter.

h.     Select Option 0 – Return to Main Menu.

i.      Repeat steps d through h for each additional adapter in the system.

j.      If you plan to update the firmware on the system that will allow the system to boot from the EMC storage array, then update the boot BIOS.

k.     If you do not plan to update the boot BIOS, then reboot the system.

Note: If you are using the HBA to boot from the SAN, update the boot BIOS immediately after updating the firmware as the firmware overwrites part of the boot BIOS.

 

Updating the HBA boot BIOS with lputil as follows:

 

a.     Ensure that the firmware has been updated prior to updating the boot BIOS.

b.    Download the appropriate boot BIOS file from the EMC-approved section of the Emulex website and copy it to the appropriate directory, /usr/sbin/lpfc:


HBA Model

Boot BIOS File

LP982-E

 

lbXXX.prg (where XXX is the version)

Example: lb170a3.prg

LP9002-E

 

cbXXX.prg (where XXX is the version)

Example: cb170a3.prg

LP9802-E

 

hbXXX.prg (where XXX is the version)

Example: hb170a3.prg

LP9802DC-E

 

hbXXX.prg (where XXX is the version)

Example: hb170a3.prg

LP1050-E

 

mbXXX.prg (where XXX is the version)

Example: mb170a3.prg

LP1050DC-E

 

mbXXX.prg (where XXX is the version)

Example: mb170a3.prg

LP1050EX-E

 

mbXXX.prg (where XXX is the version)

Example: mb170a3.prg

LP10000-E

 

tbvXXX.prg (where XXX is the version)

Example: tb170a3.prg

LP10000DC-E

 

tbXXX.prg (where XXX is the version)

Example: tb170a3.prg

LP10000EXDC-E

 

tbXXX.prg (where XXX is the version)

Example: tb170a3.prg

LP101-E

 

ebXXX.prg (where XXX is the version)

Example: eb170a3.prg

LPe111-E

 

ybXXX.all (where XXX is the version)

Example: yb170a3.prg

LPe1150-E

 

wbXXX.prg (where XXX is the version)

Example: wb170a3.prg

LPe11002-E

 

zbXXX.prg (where XXX is the version)

Example: zb170a3.prg

LP1150-E

 

jbXXX.prg (where XXX is the version)

Example: jb170a3.prg

LP11002-E

 

bbXXX.prg (where XXX is the version)

Example: bb170a3.prg

LP1005DC Mezzanine for

HPQ Blade Servers

 

mpXXX.prg (where XXX is the version)

Example: mp501a5.prg

LPe1105-HP Mezzanine for HPQ Blade Servers

zbXXX.prg (where XXX is the version)

Example: zb600a1.prg

LP1005DC Mezzanine for

IBM Blade Servers

mc XXX.prg (where XXX is the version)

Example: mc501a3.prg

LP1005BC Mezzanine for

IBM Blade Servers

buXXX.prg (where XXX is the version)

Example: bu502a1.prg

 

c.     Copy the file for Open Boot support from the EMC-approved section of the Emulex website to the appropriate directory, /usr/sbin/lpfc.

d.    Start the boot BIOS update utility:

 

cd /usr/sbin/lpfc
./lputil

 

e.     Select Option 3 – Firmware Maintenance.

f.     Select the adapter number to update.

g.    Select Option 1 – Load Firmware Update.

h.     Enter the full name of the image file (as shown in the table in item 1; for example, cd190a4.awc) and press Enter.

i.      Select Option 0 – Return to Main Menu.

j.      If desired, repeat steps d through h for each additional adapter in the system.

k.     Using lputil, choose the HBA that is to be used for booting from the fabric. Select Option 3 to enable the boot BIOS on the intended HBA.

l.      Reboot the system.


METHOD TWO - Booting from a DOS bootable diskette:

 

a.     Boot the computer using a DOS/WIN95/WIN98 bootable diskette.

b.    Insert the diskette containing the flash utility (LP6DUTIL.EXE).

c.     At the A:\> prompt, type lp6dutil and press Enter to start the utility.

The utility performs diagnostic tests on the installed adapter(s).  You may be required to press Enter after each test so the program can move on to the next test.  After the diagnostics are complete, the main menu appears.

d.    Type 5 and press Enter, to select Maintenance.

e.     Type 1 and press Enter, to select Upgrade Firmware.

f.     Enter the range of adapters to flash; for example: 1–4 (for four adapters).

g.    Enter the Firmware Image filename, including the path.  The firmware image file should be on the same disk as the LP6DUTIL.EXE program file.

h.     When prompted, type 1 and press Enter to proceed with the upgrade for the first controller.

i.      When prompted, type 1 and press Enter to reset the adapter after loading is complete.

j.      Repeat steps i and j for each adapter in the range entered earlier.

k.     When all adapters have been loaded, type 0 and press Enter at the Maintenance menu to return to the main menu.

l.      Type 7 and press Enter at the main menu to exit the flash utility.

 

 

2.   

Install the firmware

Follow these steps to install the firmware:

 

a.      Start the firmware update utility:

 

./lputil

 

a.      Select option 3 – Firmware Maintenance.

b.      Select the adapter number to update.

c.      Select option 1 – Load Firmware Image.

d.      Type the full file name of the image file (as shown in the table above; cd390a7.awc, for example) and press Enter.

 

Note: Select the proper release for the HBA you are configuring.

 

e.      Select option 0 – Return to Main Menu.

f.       For any other adapters, repeat these steps beginning with the step above where you select option 3 - Firmware Maintenance.

 

If the HBA driver is version 5.x or older, the host must reboot for the upgrade firmware to take effect.

 

 

7Table of Contents

 

·        Installing an Emulex HBA driver on a Linux v2.6.x kernel

 

Overview

This procedure describes how to install an Emulex HBA driver on a Linux v2.6.x kernel. For Linux v2.4.x driver procedures, go to the next procedure table in the sequence.

 

Refer to release notes provided with the driver for information that might be unique to new driver revisions. Verify that all HBA firmware upgrades are complete before installing HBA drivers.  Failure to maintain minimum required HBA firmware revisions can cause errors when installing drivers. Refer to the E-Lab Interoperability Navigator (ESM) for specific qualified kernel versions and distributions. 

 

The support stated in the E-Lab Interoperability Navigator (ESM) and the EMC Host Connectivity Guide for Linux supersedes versions listed in this document.

 

When downloading driver software, Include the kernel source/development package and the gcc complier tools during the installation. If these tools are not installed, then the RPM installation will fail and the driver will not be installed.

 

 

1.   

Download Driver software:

Download the Emulex v8.x-Series driver for the v2.6.x kernel from the Emulex web site as follows:

 

a.     Create a directory to which you will save the tar archive:

mkdir /home/Emulex
cd /home/Emulex

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

c.     Click drivers, downloads, and documentation on the left side of the screen.

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 version and select Linux on the next page.

f.  Find and select the listing for the Linux v8.x-Series driver listed:

lpfc_2.6_driver_kit-8.0.16.6_x2-1.tar.gz

 

g.    Create a directory to which the Emulex Application Kit will be saved:

mkdir /home/emulex_apps

h.  Find and select the listing for the Emulex Application Kit tar archive:

ElxLinuxApps-2.1a8-8.0.16.4-1.tar

 

 

2.   

Install the driver:

Depending on the Linux platform, perform the applicable set of instructions:

 

·         Installing the Emulex 8.x-Series driver on SLES 9 SP1 hosts

·         Installing the Emulex 8.x-Series driver on RHEL 4.0 hosts

·         Included Emulex driver on RHEL4 U1, RHEL4 U2, SLES9 SP2 and Asianux 2.0

 

 

Installing the Emulex 8.x-Series driver on SLES 9 SP1 hosts:

 

The Emulex v2.10f driver (included by default in the SLES 9 SP1 distribution) is not supported by EMC.  EMC requires the use of the v8.0.16.6_x2 driver when connecting to EMC storage.

Before installing the v8.0.16.6_x2 driver, the existing v2.x series driver must be uninstalled. The Emulex v8.0.16.6_x2 driver may then be compiled as a module and configured to load automatically at boot time.  When the installer script is used, it creates a new RAM disk which includes the new driver.

 

This section describes the above mentioned process using the installer script included in the package.

 

a.     Boot into the qualified and supported kernel onto which the driver will be installed.

b.    Verify you have obtained the lpfc_2.6_driver_kit-8.0.16.6_x2-1.tar.gz file from the Emulex website as instructed earlier.

c.     Uncompress and extract the source files from the tar archive:

cd /home/Emulex
tar xzvf lpfc_2.6_driver_kit-8.0.16.6_x2-1.tar.gz


The initial uncompression will create a new directory and will provide you with the following files within the new directory:

lpfc_2.6_driver_kit-8.0.16.6_x2-1/
lpfc_2.6_driver_kit-8.0.16.6_x2-1/lpfc_2.6_ioctl_module-2.0.2-1.noarch.rpm
lpfc_2.6_driver_kit-8.0.16.6_x2-1/lpfcdriver_2.6-8.0.16.6_x2-1.noarch.rpm
lpfc_2.6_driver_kit-8.0.16.6_x2-1/lpfc-install
lpfc_2.6_driver_kit-8.0.16.6_x2-1/README
lpfc_2.6_driver_kit-8.0.16.6_x2-1/elxlpfc


Contained within the newly created directory is the lpfc-install script.  This script may be used to uninstall the existing v2.10f driver and will install both the lpfc and the lpfcdfc drivers

d.    Stop all applications using the Emulex driver and unload the currently running Emulex v2.10f driver in the system as follows:

modprobe –r lpfcdd


e.  Uninstall the Emulex v2.10f driver by executing the lpfc-install script with the –u flag:

cd lpfc_2.6_driver_kit-8.0.16.6_x2-1/
./lpfc-install –u


The output from running the script is as follows:

Emulex LPFC Driver Installer Version 1.30.1.2
Determining distribution type and kernel version ...
Checking for Emulex driver packages ...
Restoring old Emulex drivers...
Configuring /etc/modprobe.conf ...
Configuring /etc/sysconfig/kernel ...
Uninstallation complete.


f.     The installer script will install both the lpfc and the lpfcdfc drivers.  No options are needed when executing this script.  The installer script unpacks the source RPMs included in the package in the /usr/src/lpfc directory and builds the driver using the sources for the currently running kernel.  The script then modifies /etc/modprobe.conf and /etc/sysconfig/kernel to include changes for the v8.x driver.  The elxlpfc is an initialization script for the lpfcdfc driver. The elxlpfc script is also installed so that the lpfcdfc driver is configured to start and stop during system boot up and shutdown.  Finally, the installer script creates a backup of the existing RAM disk and creates a new RAM disk. 

The output from the installer script will appear beginning as follows:

./lpfc-install
Emulex LPFC Driver Installer Version 1.30.1.2
Determining distribution type and kernel version ...
Checking for old Emulex driver ...
Looking for kernel source package ...
Looking for compilers ...
Searching for LPFC Driver source RPM from
    /home/emulex/lpfc_2.6_driver_kit-8.0.16.6_x2-1/. ...
Installing package ...


NOTE:  The system must be rebooted so that the lpfc driver is loaded through the newly created ramdisk.

 

 

Installing the Emulex 8.x-Series driver on RHEL 4.0 hosts:

 

By default, the Emulex v8.0.16 driver is integrated into the RHEL 4.0 kernel.  EMC requires the use of the v8.0.16.6_x2 driver when connecting to EMC storage. 

 

Before installing the v8.0.16.6_x2 driver, the existing v8.0.16 driver must be uninstalled. The Emulex v8.0.16.6_x2 driver will then be compiled as a module and configured to load automatically on boot up. Also, a new RAM disk will be created for the system that includes the new driver in it.

 

This section describes the previously mentioned process using the installer script included in the package.

Important:  If the lpfcdfc driver is loaded, then it must be unloaded prior to the lpfc driver.  Use the following commands to unload the Emulex drivers:


modprobe –r lpfcdfc

modprobe –r lpfc

 

a.     Boot into the qualified and supported kernel onto which the driver will be installed.

b.    Verify you have obtained the lpfc_2.6_driver_kit-8.0.16.6_x2-1.tar.gz file from the Emulex website as instructed earlier.

c.     Uncompress and extract the source files from the tar archive:

cd /home/Emulex
tar xzvf lpfc_2.6_driver_kit-8.0.16.6_x2-1.tar.gz


The initial uncompression will create a new directory and will provide you with the following files within the new directory:

lpfc_2.6_driver_kit-8.0.16.6_x2-1/
lpfc_2.6_driver_kit-8.0.16.6_x2-1/lpfc_2.6_ioctl_module-2.0.2-1.noarch.rpm
lpfc_2.6_driver_kit-8.0.16.6_x2-1/lpfcdriver_2.6-8.0.16.6_x2-1.noarch.rpm
lpfc_2.6_driver_kit-8.0.16.6_x2-1/lpfc-install
lpfc_2.6_driver_kit-8.0.16.6_x2-1/README
lpfc_2.6_driver_kit-8.0.16.6_x2-1/elxlpfc


Contained within the newly created directory is the lpfc-install script.  This script may be used to uninstall the existing v8.0.16 driver and will install both the lpfc and the lpfcdfc drivers.

d.    Stop all applications using the Emulex driver and then unload the currently running Emulex v8.0.16 driver in the system as follows:

modprobe –r lpfc


e.  Uninstall the Emulex v8.0.16 driver by executing the lpfc-install script with the –u flag as follows:

cd lpfc_2.6_driver_kit-8.0.16.6_x2-1/
./lpfc-install –u


The output from running the script is as follows:

Emulex LPFC Driver Installer Version 1.30.1.2
Determining distribution type and kernel version ...
Checking for Emulex driver packages ...
Restoring old Emulex drivers...
Configuring /etc/modprobe.conf ...
Uninstallation complete.


f.     The installer script will install both the lpfc and the lpfcdfc drivers.  No options are needed when executing this script.  The installer script unpacks the source RPMs included in the package in the /usr/src/lpfc directory and builds the driver using the sources for the currently running kernel.  The script then modifies /etc/modprobe.conf to include scsi_host_adapter lines.  The elxlpfc is an initialization script for the lpfcdfc driver.  The elxlpfc script is also installed so that the lpfcdfc driver is configured to start and stop during system boot up and shutdown.  Finally, the installer script creates a backup of the existing RAM disk and creates a new RAM disk.

The output from the installer script will appear beginning as follows:

./lpfc-install
Emulex LPFC Driver Installer Version 1.30.1.2
Determining distribution type and kernel version ...
Checking for old Emulex driver ...
Looking for kernel development package ...
Looking for compilers ...
Searching for LPFC Driver source RPM from
    /home/emulex/lpfc_2.6_driver_kit-8.0.16.6_x2-1/.
    ...
Installing package ...


Note:  The system must be rebooted so that the lpfc driver is loaded through the newly created ramdisk.

 

 

Included Emulex driver on RHEL4 U1, RHEL4 U2, SLES9 SP2 and Asianux 2.0:

 

The following table lists the Emulex driver versions supported with the corresponding OS updates.  These driver versions are included by default in the kernel, and do not require any installation.

 

OS

Driver Version

RedHat RHEL 4 U1

Asianux 2.0

Miracle Linux SE 4.0

RedFlag DC Server 5.0

Haansoft Linux 2006 Server

 

8.0.16.6_x2

 

Note: Does not support the 4Gb HBAs.

Red Hat RHEL 4.0 U2

SuSe SLES 9 SP3

 

8.0.16.17

 

SuSe SLES 9 SP2

 

8.0.16.6_p3

RedHat RHEL 4.0 U3

 

8.0.16.18

RedHat RHEL 4.0 U4

 

8.0.16..27

SuSe SLES 10 GA

 

8.1.6

 

 

 

3.   

Grab the Emulex Application kit and install it:

To install the Emulex Applications Kit, proceed as follows:

 

The lpfc driver must be installed first, because HBAnyware is dependent upon the existence of the lpfc driver.

 

a.     Verify you have obtained the Applications Kit from the Emulex website as instructed earlier and saved it to the newly created directory.

Note:  There is a one-to-one relationship between versions of the lpfc driver and the versions of the applications kit.  For example, for the 8.0.16.6_x2 lpfc driver the application kit is ElxLinuxApps-2.1a8-8.0.16.4-1.tar.  You will find the appropriate application kit located on the same page as the driver on the EMC-approved webpage at the Emulex website.

b.    Change to the newly created directory and uncompress and extract the source files from the tar archive:

cd /home/emulex_apps
tar xvf ElxLinuxApps-2.1a8-8.0.16.4-1.tar


The initial uncompression will create a new directory and will provide you with the following files within the new directory:

enterprise_kitfiles/
enterprise_kitfiles/hbaapi_2.1.a.tgz
enterprise_kitfiles/lputil_20a3.tgz
enterprise_kitfiles/EmlxApps300a28.tgz
enterprise_kitfiles/lpfcutil_2.6_lib_kit-80.161-2.tgz
install
uninstall
README.txt
README_SSC.txt


Contained within the existing directory is the install script.

Note:  When the installation script is run, it will automatically install HBAnyware, the lputil utility, and the HBA API libraries.

c.     To install the Application Kit, change to the newly created directory and run the installation script.

./install

The output from running the installer script is as follows:

Untarring EmlxApps tgz file...
Untarring lpfcutil tgz file...
Untarring hbaapi libs tgz file...
Untarring lputil tgz file...
Stopping HBAnyware Remote Management Server
Stopping HBAnyware Discovery Server
Starting HBAnyware Remote Management Server
Untarring HBAnyware local jre...
HBAnyware installation complete.
Cleaning up...


d.    HBAnyware is a GUI-based application that is used to manage Emulex adapters on the host.  To start up the HBAnyware application, run the following commands:

cd /usr/sbin/hbanyware
./hbanyware


Note:  hbacmd is a command-line program that can be used to modify and query Emulex adapter parameters.  A sample session using hbacmd is described in EMC Fibre Channel with Emulex Host Bus Adapters for the Linux v2.6.x Kernel Environment and the v8.x-Series Driver (P/N 300-002-583), which is available on the Emulex website.

 

 

4.   

Edit the driver parameters:

If necessary, edit the driver parameters.

 

Note:  Default settings and descriptions of the driver parameters can be located in EMC Fibre Channel with Emulex Host Bus Adapters for the Linux v2.6.x Kernel Environment and the v8.x-Series Driver (P/N 300-002-583), which is available on the Emulex website.

 

 

 

7Table of Contents

 

·        Installing an Emulex driver on a Linux v2.4.x kernel

 

Overview

This procedure describes how to install an Emulex HBA driver on a Linux v2.4.x kernel. Refer to release notes provided with the driver for information that might be unique to new driver revisions. Verify that all HBA firmware upgrades are complete before installing HBA drivers.  Failure to maintain minimum required HBA firmware revisions can cause errors when installing drivers. Refer to the E-Lab Interoperability Navigator (ESM) for specific qualified kernel versions and distributions. 

 

The support stated in the E-Lab Interoperability Navigator (ESM) and the EMC Host Connectivity Guide for Linux supersedes versions listed in this document.

 

When downloading driver software, Include the kernel source/development package and the gcc complier tools during the installation. If these tools are not installed, then the RPM installation will fail and the driver will not be installed.

 

 

1.   

Install Helper module for RHEL 3.0:

For Linux RHEL 3.0 U4 only – Install the IOCTL Application Helper Module on RHEL 3.0 U4:

 

Note:  By default, RHEL 3.0 U5, RHEL 3.0 U6, and Asianux 1.0 U1 include the lpfcdfc IOCTL Application Helper Module so no steps need to be taken in order to enable it.  The IOCTL Application Helper Module is not included in the RHEL 3.0 U4 kernel; therefore, if Emulex applications are to be used on the host, the IOCTL Application Helper Module must be downloaded and installed separately.

a.     Verify that the correct version of the Emulex driver is loaded in the kernel.  Run the lsmod command to ensure that the Emulex driver is loaded on the system.

b.    Review the files in /proc/scsi/lpfc/ to verify the Emulex driver version.

c.     Change to the directory to which you will save the IOCTL Application Helper Module kit.

Example:
[root@l82bi250 /]# mkdir /home/Emulex
[root@l82bi250 /]# cd /home/emulex/

d.    Download the IOCTL Application Helper Module from the Emulex website to a directory on the server.  Open a browser and access the Emulex website at http://www.emulex.com.

Click drivers, downloads, and documentation on the left side of the screen.  On the next page under Storage and System Supplier Qualified and Supported HBAs, select the EMC link.  On the Support Resources for EMC page, select the link for the correct Emulex HBA version and select Linux on the next page.

Select the appropriate link to download the IOCTL Application Helper Module.

e.  Uncompress and extract the source files from the tar archive:

[root@l82bi250 /]# cd /home/emulex/
[root@l82bi250 /]# tar zxvf lpfc_2.4_ioctl_module_kit-1.0.13-1.tar.gz


The uncompressing will create a new directory and will provide you with the following files within the new directory:

lpfc_2.4_ioctl_module_kit-1.0.13-1/
lpfc_2.4_ioctl_module_kit-1.0.13-1/elxlpfc
lpfc_2.4_ioctl_module_kit-1.0.13-1/ioctl-install
lpfc_2.4_ioctl_module_kit-1.0.13-1/lpfc_2.4_ioctl_module-1.0.13-1.noarch.rpm
lpfc_2.4_ioctl_module_kit-1.0.13-1/README


f.     Change to the directory and install the IOCTL Application Helper Module using the installer script:

[root@l82bi250 /]# cd lpfc_2.4_ioctl_module_kit-1.0.13-1/
[root@l82bi250 /]# ./ioctl-install


Note:  For additional information on installing the Applications Kit, refer to Installing the Emulex Applications Kit later in this procedure.

 

 

2.   

Enable the v7 driver:

Depending on the Linux platform, perform the applicable set of instructions:

 

·         Enabling the Emulex v7.x-Series driver in RHEL 3.0 U4 and U5

·         Enabling the Emulex v7.x-Series driver in Asianux 1.0 U1

·         Enabling the Emulex v7.3.2 driver in RHEL 3.0 U6

·         Installing older Emulex v7.x-Series drivers

 

 

 

Enabling the Emulex v7.x-Series driver in RHEL 3.0 U4 and U5:

 

EMC supports the Emulex v7.1.14 driver included in RHEL 3.0 U4 and U5 distributions.  In RHEL 3.0 kernel v2.4.21-27.EL and later, the Emulex v7.1.14 driver is the default driver integrated into the kernel.

 

To enable the integrated v7.1.14 driver:

a.  Ensure that the /etc/modules.conf file references an entry for each installed Emulex HBA.  For each installed Emulex HBA, add an entry:

alias scsi_hostadapterN lpfc

where N is the sequential value of each Emulex HBA installed in the system, beginning with the number after the last host adapter number entry in the file. (The first host adapter entry begins with zero.)

Example:
alias parport_lowlevel partport_pc
alias scsi_hostadapter mptbase
alias scsi_hostadapter1 mptscsi
alias scsi_hostadapter2 lpfc
alias scsi_hostadapter3 lpfc
alias eth0 tg3
options scsi_mod max_scsi_luns=255 scsi_allow_ghost_devices=1


b.  If any modifications are made to the /etc/modules.conf file to include references to the Emulex HBAs, create a new ramdisk to reflect the changes made:

cd /boot
mkinitrd –v initrd-
$1.img $1

where $1 is the currently running v2.4.x kernel version.

Example:
cd /boot
cp initrd-2.4.21-27.ELsmp.img
initrd-2.4.21-27.ELsmp.img.orig
mkinitrd –v initrd-2.4.21-27.ELsmp.img 2.4.21-27.ELsmp


c.     Reboot the host.

Note:  When using RHEL 3.0 U4 and U5, it is required that parameter value modifications be made via an edit to /etc/modules.conf, not lpfc.conf.

 

 

Enabling the Emulex v7.x-Series driver in Asianux 1.0 U1:

EMC supports the Emulex v7.1.14 driver integrated into the Asianux 1.0 U1 distribution. The Asianux 1.0 U1 kernel v2.4.21-20.19AX includes the Emulex v7.1.14 lpfc driver and the lpfcdfc IOCTL application helper driver by default in the kernel.

Follow the procedure used to enable the integrated v7.1.14 driver for RHEL 3.0 U4 for Asianux 1.0 U1 hosts. Refer to the previous set of instructions for Enabling the Emulex v7.x-Series Driver in RHEL 3.0 U4 and U5.

Note:  Asianux 1.0 U1 includes the lpfcdfc IOCTL Application Helper Module by default, so no steps need to be taken in order to enable it.


 

Enabling the Emulex v7.3.2 driver in RHEL 3.0 U6:

 

EMC supports the Emulex v7.3.2 driver included in RHEL 3.0 U6 distribution.  In the RHEL 3.0 kernel v2.4.21-37.EL, the Emulex v7.3.2 driver is the default driver integrated into the kernel. 

 

Note:  RHEL 3.0 U6 includes the lpfcdfc IOCTL Application Helper Module by default, so no steps need be taken to enable it.

 

To enable the integrated v7.3.2 driver:

 

a.     Ensure that the /etc/modules.conf file references an entry for each installed Emulex HBA.

For each installed Emulex HBA, add an entry:

alias scsi_hostadapterN lpfc

where N is the sequential value of each Emulex HBA installed in
the system, beginning with the number after the last host adapter number entry in the file.  (The first host adapter entry begins with zero.)

Example:
alias parport_lowlevel partport_pc
alias scsi_hostadapter mptbase
alias scsi_hostadapter1 mptscsi
alias scsi_hostadapter2 lpfc
alias scsi_hostadapter3 lpfc
alias eth0 tg3
options scsi_mod max_scsi_luns=255 scsi_allow_ghost_devices=1

b.    If any modifications are made to the /etc/modules.conf file to include references to the Emulex HBAs, create a new ramdisk to reflect the changes made:

cd /boot
mkinitrd -v initrd-
$1.img $1

where $1 is the v2.4.x kernel version that is currently running.

Example:
cd /boot
mv initrd-2.4.21-37.ELsmp.img initrd-2.4.21-37.ELsmp.img.orig
mkinitrd -v initrd-2.4.21-37.ELsmp.img 2.4.21-37.ELsmp


c.     Reboot the host.

Note:  When using RHEL 3.0 U6, parameter value modifications must be made by editing /etc/modules.conf, not lpfc.conf.

 

 

 

Installing older Emulex v7.x-Series drivers:

 

The Emulex v7.x-series lpfc and lpfcdfc drivers may be installed onto a Linux host using one of two methods:

 

·         METHOD ONE – Run the installer script provided in the driver tar archive to compile and install the modular lpfc and lpfcdfc drivers on RHEL 2.1, RHEL 3.0, and SLES 8 systems.

·         METHOD TWO – Use the DKMS RPM to compile and install the modular lpfc and lpfcdfc drivers on RHEL 2.1 and RHEL 3.0 systems.  By using the DKMS RPM, the necessary files will be edited and the drivers will be compiled and installed automatically.

 

METHOD ONE:

This section guides you through the process of installing and utilizing the Emulex tar archive. The installer script contained within the tar archive will create the Emulex v7.x-series driver for RHEL 2.1, RHEL 3.0, and SLES 8 distributions.

 

a.     Boot into the qualified and supported kernel onto which the driver will be installed.

b.    Create a directory to which you will save the tar archive:

mkdir /home/Emulex
cd /home/emulex


c.     Download the correct HBA driver version.  Open a browser and access the Emulex website at http://www.emulex.com.

Click drivers, downloads, and documentation on the left side of the screen.  On the next page under Storage and System Supplier Qualified and Supported HBAs, select the EMC link.  On the Support Resources for EMC page, select the link for the correct Emulex HBA version and select Linux on the next page.

Find the listing for the Linux v7.x-series driver and select the appropriate link to download the lpfc_2.4_driver_kit-7.1.14-4.tgz file.

d.    Install the Emulex driver’s tar archive onto your system by uncompressing and extracting the source files from the tar archive as follows:

cd /home/emulex
tar zxvf lpfc_2.4_driver_kit-7.1.14-4.tgz


The initial uncompression will create a new directory and will provide you with the following files within the new directory:

lpfc_2.4_driver_kit-7.1.14-4/
lpfc_2.4_driver_kit-7.1.14-4/elxlpfc
lpfc_2.4_driver_kit-7.1.14-4/lpfcdfcdriver-1.0.13-1.noarch.rpm
lpfc_2.4_driver_kit-7.1.14-4/lpfc-install
lpfc_2.4_driver_kit-7.1.14-4/README


Contained within the newly created directory is the lpfc-install script.  This script will install both the lpfc and the lpfcdfc drivers. These driver RPMs are installed in the /usr/src/lpfc directory.  No options are needed when executing this script.

After the RPMs are installed into the /usr/src/lpfc directory, the RPMs then are executed so that the drivers will be built and installed into the currently running kernel.  The script then modifies /etc/modules.conf.  The lpfc driver host adapter line will be appended to the /etc/modules.conf file for each instance of an Emulex HBA.

The options line containing the addition of the scsi_allow_ghost_devices and max_scsi_luns parameters will also be appended to the file.  This will allow the host to correctly identify the disconnected LUN 0 that is reported when attached to a Symmetrix Storage Array as well as allow the SCSI stack to scan up to 255 devices.

 

After modifying the /etc/modules.conf file, the last action performed by the installer is to create a new ramdisk.  The elxlpfc is an initialization script for the lpfcdfc driver.  The elxlpfc script is also installed so that the lpfcdfc driver is configured to start and stop during system boot up and shutdown.

e.     Install the Emulex driver:

cd /home/emulex/lpfc_2.4_driver_kit-7.1.14-4
./lpfc_install


The output from running the installer script will appear.

Example of a newly modified /etc/modules.conf:

Note: 
The last three lines of the file have been newly added by the installer script.

[root@l82bi250 /]# more /etc/modules.conf
alias eth0 tg3
alias eth1 tg3
alias eth2 tg3
alias scsi_hostadapter mptbase
alias scsi_hostadapter1 mptscsih
alias usb-controller usb-ohci
alias scsi_hostadapter2 lpfc
alias scsi_hostadapter3 lpfc
options scsi_mod max_scsi_luns=256 scsi_allow_ghost_devices=1


The scsi_allow_ghost_devices parameter is enabled by default in SLES 8 SP3.  Therefore, the installer script will not add the parameter to the /etc/modules.conf file for SLES 8 SP3 installations.

f.     Reboot the host so that the lpfc driver can be loaded through the newly created ramdisk.

 

 

 

METHOD TWO:

 

This section guides you through the process of installing and utilizing the Emulex DKMS RPM for the Emulex v7.1.14 driver for RHEL 2.1 and 3.0 distributions. 

Note:  The DKMS RPM method does not function properly with SLES 8 distributions and may not be used.

The DKMS RPM will build and install the lpfc and lpfcdfc drivers and modify your /etc/modules.conf file.  The host adapter line will be appended to the /etc/modules.conf file for the lpfc driver.  The options line containing the addition of the scsi_allow_ghost_devices and max_scsi_luns parameters will also be appended to the file. The DKMS RPM will install the Emulex driver as a module.

Note:  After the driver installation, the system should be rebooted so that the lpfc driver may be loaded through the newly created ramdisk.

 

a.     Boot into the qualified and supported kernel into which the driver will be installed.  Ensure that the kernel sources and the gcc compiler tools are installed.

b.    Create a directory to which you will save the tar archive:

mkdir /home/Emulex
cd /home/emulex


c.     Download the correct HBA driver version.  Open a browser and access the Emulex website at http://www.emulex.com.

Click drivers, downloads, and documentation on the left side of the screen.  On the next page under Storage and System Supplier Qualified and Supported HBAs, select the EMC link.  On the Support Resources for EMC page, select the link for the correct Emulex HBA version and select Linux on the next page.

Find the listing for the Linux v7.x-series driver and select the appropriate link to download the lpfc_2.4_dkms_kit-7.1.14-2.tar.gz file.

d.    Install the Emulex driver’s tar archive onto your system by uncompressing and extracting the source files from the tar archive as follows:

cd /home/emulex
tar zxvf lpfc_2.4_dkms_kit-7.1.14-2.tar.gz


The initial uncompression will create a new directory and will provide you with the following files within the new directory:

lpfc_2.4_driver_kit-7.1.14-4/
lpfc_2.4_driver_kit-7.1.14-4/dkms-2.0.4-1.noarch.rpm
lpfc_2.4_driver_kit-7.1.14-4/lpfc_2.4_dkms_kit-7.1.14-2.tar.gz
lpfc_2.4_driver_kit-7.1.14-4/lpfc_2.4_driver_kit-7.1.14-4
lpfc_2.4_driver_kit-7.1.14-4/lpfc_2.4_driver_kit-7.1.14-4.tar.gz
lpfc_2.4_driver_kit-7.1.14-4/lpfcdfcdkms-1.0.13-2.noarch.rpm
lpfc_2.4_driver_kit-7.1.14-4/lpfcdkms-7.1.14-2.noarch.rpm
lpfc_2.4_driver_kit-7.1.14-4/README


e.     If you do not already have DKMS installed on your system, then install the DKMS RPM contained within the newly created directory.  If DKMS is already installed on the system, then skip to the next step to perform the Emulex driver installation.

rpm -ivh dkms-2.0.4-1.noarch.rpm

f.     Install the Emulex lpfc driver DKMS RPM as follows:

rpm -ivh lpfcdkms-7.1.14-2.noarch.rpm

The output from the installation will appear.

Example of a newly modified /etc/modules.conf:

Note: 
The last three lines of the file have been newly added by the installer script.

[root@l82bi250 /]# more /etc/modules.conf
alias eth0 tg3
alias eth1 tg3
alias eth2 tg3
alias scsi_hostadapter mptbase
alias scsi_hostadapter1 mptscsih
alias usb-controller usb-ohci
alias scsi_hostadapter2 lpfc
alias scsi_hostadapter3 lpfc
options scsi_mod max_scsi_luns=256 scsi_allow_ghost_devices=1


g.    Install the Emulex DFC driver DKMS RPM:

rpm -ivh lpfcdfcdkms-1.0.13-2.noarch.rpm

h.     Use the DKMS command to verify that the drivers have been built and installed successfully.

For example:
[root@l82bi250 /]# dkms status
lpfc, 7.1.14, 2.4.21-27.0.1.ELsmp, i686: installed (original_module exists)
lpfcdfc, 1.0.13, 2.4.21-27.0.1.ELsmp, i686: installed


i.  Reboot the host.

Caution:  If the lpfcdfc driver is loaded, then it must be unloaded prior to the lpfc driver. Use the following commands to unload the lpfc driver:

modprobe –r lpfcdfc
modprobe –r lpfc

 

 

3.   

Install the Emulex Application:

Install the Emulex Applications Kit as follows:

 

The lpfc driver must be installed first because HBAnyware is dependent upon the existence of the lpfc driver.

 

a.     Create a directory to which the application kit will be saved:

mkdir /home/emulex_apps

b.    Download the Applications Kit from the Emulex website and save it to the newly created directory.  The name of the Application Kit is elxlinuxapps-2.0a20-7.1.14-1.tar.

c.     Change to the newly created directory and uncompress and extract the source files from the tar archive:

cd /home/emulex_apps
tar xvf elxlinuxapps-2.0a20-7.1.14-1.tar


The initial uncompression will create a new directory and will provide you with the following files within the new directory:

[root@l82bi250 /home/emulex_apps]# tar xvf elxlinuxapps-2.0a20-7.1.14-1.tar
enterprise_kitfiles/
install
uninstall
README.txt
README_SSC.txt


Note:  Contained within the existing directory is the install script.  When the installation script is run, it will automatically install HBAnyware, the lputil utility, the HBAAPI libraries, and the lpfcdfc libraries and utility.

d.    Within the newly created enterprise_kitfiles/ directory are the applications to be installed:

[root@l82bi250 emulex_apps]# ls -la enterprise_kitfiles/
hbaapi_2.0.f.tgz
lputil_16a10.tgz
EmlxApps300a15.tgz
lpfcutil_2.4_lib_kit-1.0.13-1.tgz
scripts/


e.     To install the Application Kit, change to the directory and run the installation script:

cd /home/emulex_apps/enterprise_kitfiles
./install


f.     HBAnyware is a GUI-based application so the console may not be used.  To start up the HBAnyware application, run the following commands:

cd /usr/sbin/hbanyware
./hbanyware


 

4.   

Edit driver config file as required:

If necessary, the lpfc.conf file with its parameter settings can be edited as required.

 

Note:  Default settings and descriptions of the driver parameters can be located in the EMC Fibre Channel with Emulex Host Bus Adapters and the v7.x-Series Driver in the Linux Environment manual (P/N 300-002-303).

 

 

 

 

·        Determine WWN of new HBA for Linux

 

Overview

This procedure describes how to determine the WWN of the newly installed HBA.

 

 

1.   

Determine HBA WWN:

To determine the WWN of the newly installed HBA, at the command line use one of the following forms:

 

cat /proc/scsi/qla2300/# (instance number could be 0, 1, 2, 3,  …)

Or for Emulex:

cat /proc/scsi/lpfc/# (instance number could be 0, 1, 2, 3,  …)

This can also be verified by looking at the Fibre Channel Switch Port that the HBA is plugged in to.

 

 

 

7Table of Contents

 

·        Creating switch zones

 

Overview

For directions specific to Brocade switches, refer to the Brocade Fabric Manager Administrator’s Guide, which is located on Powerlink under the following location:

 

Home > Support > Documentation/White Paper Library > Hardware/Platforms Documentation > Connectrix Directors and Switches > Maintenance/Administration

 

Please refer to the section Managing Zones, which will provide the background information needed to configure and zone your fabric.

 

Note: There are multiple versions of the user guide available. Be sure to reference the version specific to your Fabric Manager version.

 

3.   

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

 

 

4.   

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.

 

5.   

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.

 

It should also be noted that HBAs in an HP-UX host only show as logged in while there is active I/O.  However, if an entry exists in the login history table, it indicates that the HBA did log into the FA at some point.

 

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

 

 

6.  

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.

 

 

7.  

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.

 

 

8.  

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.

 

 

9.  

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;

 

10.  

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.

 

 

11.  

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.

 

 

12.  

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

 

 

 

 

 

13.  

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.

 

 

14.  

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.

 

 

15.  

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

 

 

16.  

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

 

 

17.  

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

 

 

18.  

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). !

 

 

19.  

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.

 

 

20.  

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.

 

 

 

21.  

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

 

 

22.  

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

 

 

23.  

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

 

24.  

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 Linux

 

Overview

This procedure describes how to make the devices or LUNs available or visible to a Linux host. It describes how to use the fdisk command to label and partition devices.

 

The Symmetrix devices will be represented in /proc/scsi/scsi and can be viewed by using:

 

more /proc/scsi/scsi.

 

Additional sd and sg filenames may need to be created because the number created by default in the kernel is usually less than 128 device filenames. 

 

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 with this procedure. 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.

 

 

25.  

Partition devices:

The fdisk command allows a single disk device to be partitioned. To partition the Symmetrix devices, verify that you are logged in as root and perform the steps below for each new device that requires partitioning as follows:

 

a.      Enter the following command:

fdisk /dev/<device_name>

where <
device_name> is the LUN device-name

For example:  fdisk /dev/sdb

b.      Type m (for help) and press Enter to display a menu of options.

Type
x (for expert functionality) and press Enter.  Type m and press Enter to see another menu of options.

c.      From the main fdisk menu, type n and press Enter to add a new disk partition.

d.      Type t and press Enter to change a partition’s system ID.

e.      Type L and press Enter for a list of hex codes for system Ids.  (Linux is type 83; Linux swap is 82.)

f.       Type p and press Enter to print the partition table so you can verify that the selections look correct.

g.      Type w and press Enter to write the table to disk and exit fdisk.

h.      Repeat steps c through g for each new Symmetrix device.

i.        If you want to display the partition numbers created after Linux recognizes them, view the file:

more / proc/partitions

 

 

26.  

Create filesystems on partitions:

Once each Symmetrix device has been formatted, partitions, and labeled, you must create a filesystem in order to make the partition useable.

 

To create a new filesystem:

 

a.   Enter the following mkfs command:

mkfs /dev/<device_name>/<partition_number>

where <device_name> is the LUN device name and <partition_number> is the partition number

Examples:

mkfs /dev/sdb1
mkfs –j/dev/sbd1
mkreiserfs –h r5 /dev/sdb1

b.      When prompted to confirm the construction of a new filesystem, type Y and press Enter.

 

 

27.  

Create mount directory:

Once the filesystem for each Symmetrix disk device has been created, you must create a mount directory for each device as follows:

 

mkdir /<mount_point>

For example:  

 

mkdir /mnt/sdb

 

where /mnt/sdb is the complete path for the new filesystem

 

 

28.  

Mount the file systems:

To mount each filesystem, enter the mount command as follows:

 

mount -t <filesystem type> /dev/<device_partition_name> <mount_point>

 

Examples:

 

mount –t ext2 /dev/sdb1 /mnt/sdb

mount –t ext3 /dev/sdb1 /mnt/sdb

mount –t reiserfs /dev/sdb1 /mnt/sdb

 

This mounts the partition /dev/sdb1 onto the mount point /mnt/sdb as the filesystem type specified.

 

This mount command is required every time the host is rebooted.  If preferable, the filesystem can be mounted automatically at boot time by adding this information to the /etc/fstab file.  Once the filesystems are mounted, data can be written to and read from them.

 

 

 

7Table of Contents

 

 

 

 

·        Installing PowerPath software on a Linux host

 

Overview

This procedure describes how to install PowerPath on a Linux host.

 

Note: This procedure is specific to the installation of PowerPath version 4.5.x, which is the current shipping version for Linux hosts.  For instructions on installing other 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 Linux Installation and Administration Guide

 

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

 

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://Powerlink.EMC.com.

 

·         For RHEL 3.0 and for all SuSE SLES 8 distributions, verify you have 256 sd and sg devices in the /dev directory.  This prerequisite is required even if the devfs file system is mounted over /dev.

·         Ensure that the PowerPath driver’s major numbers (232-247) are not already in use. If the major numbers are already in use, the driver fails to install at system boot time and issues the following error:

emcp: Device or resource busy


·         Ensure that there is only one path (physical connection) per logical device.

 

 

29.  

Mount the PowerPath CD-ROM or grab from  website:

Install PowerPath software as follows:

 

a.     Verify that you are logged in as root.

b.    Perform the applicable substep:

·         To install from a CD-ROM: 

Insert the PowerPath installation CD-ROM and create the directory /cdrom to be the mount point for the CD-ROM by entering:

mkdir /cdrom

Mount the PowerPath CD on /cdrom by entering:

mount -o ro /dev/cdrom /cdrom

Change to the directory for your operating system:

For SLES, enter: cd /cdrom/LINUX/2.6/pp4.5.x/sles

For RHEL and Asianux, enter: cd /cdrom/LINUX/2.6/pp4.5.x/rhel

·         To installing from a compressed archive:

Download the PowerPath 4.5 archive from http://powerlink.emc.com Resources/Tools CS Support Downloads and Patches Downloads D-R PowerPath for Linux.  Untar the PowerPath archive by entering:

tar -xzf EMCpower.LINUX.4.5.<
release>.tar.gz

 

 

30.  

Install PowerPath

Install the PowerPath software as follows:

 

c.      Install PowerPath by entering the following command:

rpm –i EMCpower.LINUX-4.5.<release>.<package>.rpm

where <package> is:

Package Name

 

Description

sles.x86_64

 

PowerPath 4.5.x on SLES x86_64 platforms.

sles.ia64

 

PowerPath 4.5.x on SLES IA64 platforms.

sles.i386

 

PowerPath 4.5.x on SLES i386 platforms.

rhel.x86_64

 

PowerPath 4.5.x on RHEL and Asianux x86_64 platforms.

rhel.ia64

 

PowerPath 4.5.x on RHEL IA64 platforms.

rhel.i386

 

PowerPath 4.5.x on RHEL and Asianux i386 platforms.

 

 

 

31.  

Register PowerPath

After the installation completes, you must register PowerPath on the host:

 

a.      Locate the PowerPath License Key Card, delivered with the PowerPath media kit, which has your license registration key printed.  

b.   Enter the following command:

/etc/emcpreg –install