Cover Log Sheet for a Symmetrix Procedure

Procedure created on: 10/28/10 5:54 PM Before you continue with this particular procedure you might want to record the event: Site Activity and Event Record : When using Solutions Enabler, SYMCLI and SYMAPI normally captures significant events and command actions to a daily log file. y On UNIX: /var/symapi/log/symapi-yyymmdd.log y On Windows: C:\Program Files\EMC\Symapi\log\symapi-yyyymmdd.log In addition, for your own change management practices, you may want to use the following tables to document the changes you are making while following this procedure: Activity Event Time: Date/Time: Task Activity or Event: Task being executed: Performed by: Array Information: Array Serial Number

Symmetrix Enginuity Version

Software in configuration Host Name: Host Operating System: Solutions Enabler (SYMCLI) Symmetrix Management Console (SMC) EMCSCF for z/OS Mainframe PowerPath

Version Installed Version Version Version |Patch

The following attached document is a Symmetrix Procedure for your site requirements.

Provisioning a New Host

Switch Type: Cisco HBA Type: Emulex Operating System: Solaris

This user customizable document was created and tailored to your site configuration input, using the Symmetrix Procedure Generator on March 24, 2011.

Report Problems: If you find any errors in this procedure or have comments regarding the generator, please send email to SymmetrixprocedureGeneratorComments@emc.com. Be sure to reference any modules by the correct filename (located to the right-top of the module title).

EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 www.EMC.com

Symmetrix Customer Procedure Generator Version 3.1.1 Page 3

some functions described in this procedure may not be supported by all revisions of the software or hardware you have currently in use. All other trademarks used herein are the property of their respective owners. As part of the effort to continuously improve and enhance the performance and capabilities of the Symmetrix product line.1. AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Therefore. questions.com. including your host operating system. refer to the E-Lab Interoperability Navigator on Powerlink. For the most up-to-date listing of EMC product names.INFORMATION ABOUT THIS PROCEDURE: The Symmetrix Procedure Generator you just ran allows you to create this customized document specifically tailored for your site needs. or qualifies various operating systems interoperability with Symmetrix functionality. and distribution of any EMC software described in this publication requires an applicable software license. see EMC Corporation Trademarks on EMC. All rights reserved." EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION. If you have any concerns. Since the procedure content base on Powerlink is continually being updated and refined. 2008. contact your local sales representative. THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS. It steps you through the completion of a specific Symmetrix array management activity or host setup task that can be completed without the involvement of Remote Technical Support. EMC periodically releases new versions of its hardware and software. concerning your host environment status and storage system. Published March 24. it is recommended to rerun the procedure generator for your selected procedure every 30 days to ensure currency and release control of your printed copy. copying. SMC. Symmetrix Customer Procedure Generator Version 3. or need assistance with an implementation. or EMCSCF) is up-to-date and is installed on your host as the prime storage management tool. Use. Host implementation cost is not covered under Warranty or Maintenance. 2011 EMC believes the information in this publication is accurate as of its publication date.1 Page 4 . regarding your environment or this procedure. The information is subject to change without notice. ® Copyright © 2007. All of the generated procedures assume that you check the Symmetrix Procedure Generator release notes to insure your selected storage management software (SYMCLI. 2009 EMC Corporation. For the most up-todate information on specific requirements.

A series of procedures take you from installing HBAs. InstallSetupEmlxHBASolarisa_sym001 y Installing Emulex HBA(s) on a Solaris Host 3 Done Overview These procedures are based on content from the following EMC manual: y EMC Host Connectivity Guide for Sun Solaris y EMC Support Matrix Solaris These documents can be obtained from the EMC Powerlink website at: http://Powerlink.1. zoning. configuring failover support. Table of Contents Install/Setup Emulex HBA/Driver Environment on Solaris InstallSetupEmlxHBASolaris_sym001 Using various procedures. HBA firmware and drivers. HBA firmware and drivers.1 Page 5 . Denotes a checkpoint y y y y y y y y y y y y y y y Installing Emulex HBA(s) on a Solaris Host 5 Updating Emulex HBA firmware for Solaris 6 Downloading the latest Emulex HBA driver for Solaris 8 Installing an Emulex HBA driver on a Solaris host 9 Editing the Solaris system file 10 Configuring an Emulex HBA driver for Solaris failover support 11 Creating switch zones 13 Adding Symmetrix Devices 14 Mapping Devices within Symmetrix 18 Masking Devices 23 Creating a Device Group 28 Adding persistent bindings to Solaris Emulex kernel files 30 Adding LUNs to the Solaris config file for Emulex HBA 30 Making LUNs or Devices available to Solaris 32 Installing PowerPath software on a Solaris host 34 ProvisionNewSolaris_sym001 Provisioning a new Solaris host This document for Solaris describes how to setup a new host for the Symmetrix storage management environment.EMC. A series of procedures take you from installing HBAs.com 1. mapping/masking devices. 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.TABLE OF CONTENTS: To link immediately to a specific page within this procedure. to configuring kernel files and LUNs. position the cursor over the page number on the right and click. and configuring failover to configuring kernel files and LUNs. Set Jumpers on adapter board Review your host computer documentation for slot recommendations that meet or exceed … Symmetrix Customer Procedure Generator Version 3. this document for Solaris.

2.EMC.1. … … 3. Install Adapter in card slot With host system power off. Repeat the installation steps for each host in which you are installing Fibre Channel HBAs. These procedures are based on content from the following EMC manuals: y EMC Host Connectivity Guide for Sun Solaris y EMC Support Matrix Solaris These documents can be obtained from the EMC Powerlink website at: http://Powerlink.the HBA capabilities: 64-bit. Note: The LP9002S-E and LP9002DC-E have no user-programmable jumpers. The adapter installs into a single-sloted PCI bus. Apply power and boot Reapply power and allow the system to boot normally.com Symmetrix Customer Procedure Generator Version 3. Set the HBA jumpers as shown in the figure below to enable it for use with the Solaris host. 33 MHz. Table of Contents InstallSetupEmlxHBASolarisb_sym001 y Updating Emulex HBA firmware for Solaris 3 Done Overview Refer to release notes provided with the driver for information that might be unique to new driver revisions. install the HBA(s) by following the instructions included with your adapter.1 Page 6 .

com Click drivers.awc (for example: cd390a7. HBA Model LP8000E-EMC LP9002-E LP9002C-E LP9002DC-E LP9002S-E LP9802-E LP10000-E LP10000DC-E LP11000-E LP11002-E LPe11000-E LPe11002-E File (where XXX is the version) ddXXX.all (for example: td180a2. select the EMC link.awc (for example: rf390a7.emulex. /usr/sbin/lpfc.all) Symmetrix Customer Procedure Generator Version 3.all) tdXXX.awc) cdXXX.all) tdXXX. click the appropriate firmware link to download the desired file to the appropriate directory. On the next page. Download the firmware Each Emulex Fibre Channel controller has a flash upgradeable firmware and BIOS. On the Support Resources for EMC page. Download the latest firmware: a. it is necessary to keep only the firmware up to date. b. Open a browser and access the Emulex website at http://www. On the next page. e. downloads. rfXXX.1.awc (for example: dd390a7. under Storage and System Supplier Qualified and Supported HBAs. select the link for the correct Emulex HBA version.awc) hdXXX. since the BIOS is applied only when using connected storage as a boot device.all (for example: td180a2. c.all) tdXXX.all (for example: hd100a2.all (for example: td180a2. and documentation on the left side of the screen.1.awc) … d. In most instances.1 Page 7 .

Firmware Maintenance. Find and select the listing for the appropriate driver. Review the E-Lab Interoperability Navigator (ESM) for the latest information on approved HBAs and drivers. the host must reboot for the upgrade firmware to take effect.2. select the link for the correct Emulex HBA version and select Solaris on the next page. be sure to use the latest versions supported by EMC. e. for example) and press Enter.1 Page 8 . select the EMC link. f. 1. Extract the downloaded file to the directory created earlier.x or older. Create a directory to which you will save the driver. c. If the HBA driver is version 5. Table of Contents InstallSetupEmlxHBASolarisc_sym001 y Downloading the latest Emulex HBA driver for Solaris 3 Done Overview When installing or upgrading drivers.awc. d. cd390a7. downloads.emulex. d.1. and documentation on the left side of the screen. On the Support Resources for EMC page. For example: mkdir /emulex … b. e. Install the firmware Follow these steps to install the firmware: a. Select option 3 ± Firmware Maintenance. Download the HBA driver To download the latest HBA driver: a. Start the firmware update utility: . c./lputil … a. For any other adapters. Table of Contents Symmetrix Customer Procedure Generator Version 3. Open a browser and access the Emulex website at http://www. g. Select option 0 ± Return to Main Menu. Click drivers. b. f. Type the full file name of the image file (as shown in the table above. Select the adapter number to update. Select option 1 ± Load Firmware Image.com. On the next page under Storage and System Supplier Qualified and Supported HBAs. Note: Select the proper release for the HBA you are configuring. repeat these steps beginning with the step above where you select option 3 .

Make selection to rebuild When prompted if you want to rebuild the manual pages database for section 7d. … 4. if desired. and documentation) readme.tar pkgadd -d . The skipped catman command will be output for the administrator to run later. the catman will be skipped. If you need help. Depending on your system. read the following note and press either Y or N. … 5. If you enter N. type ? or ?? and press Enter. HBAAPI. … 3.first. HBAnyware. Normally the catman command can be run to create preformatted versions of the online manual from the nroff(1) input files.Emulex Applications kit (containing lputil. Each manual page is examined and any with preformatted versions that are missing or out of date are recreated.1. press Enter. Note: Section 7d of the online manpages contains the manual pages for lpfc. allowing the installation to complete quickly.InstallSetupEmlxHBASolarisd_sym001 y Installing an Emulex HBA driver on a Solaris host 3 Done Overview This procedure describes how to install an Emulex HBA driver on a Solaris host.tar … When the untar is complete you will find these components: y lpfc-yyy-sparc. If any changes are made. catman recreates the windex database.tar (where zzz is the application kit version) . this operation can take from 1 to 10 minutes.tar (where yyy is the driver revision) . Select the package When prompted to select the packages you wish to process: y y To accept the default value.Emulex Fibre Channel Solaris driver y EmlxAppsZZZ-Solaris. press N to disable IP networking through the Emulex card. 1.txt y 2. Disable IP networking When prompted if you want to use IP networking over Fibre Channel. Untar the kit Change to the /emulex directory (where you copied the Driver and Applications Kit) and untar the kit: cd /emulex tar xvf Solaris-xxx. … Symmetrix Customer Procedure Generator Version 3. Refer to release notes provided with the driver for information that might be unique to new driver revisions. Install the driver Enter the following (including the period) to install the driver: tar xvf lpfc-yyy-sparc.1 Page 9 .

press Q at the prompt to quit the installation package. Table of Contents InstallSetupEmlxHBASolarise_sym00 2 … … … y Editing the Solaris system file 3 Done Overview This procedure describes how to edit the /etc/system file. Select the package When prompted to select the packages you wish to process. as follows: tar xvf EmlxAppsZZZ-Solaris.tar). Note: EMC has not qualified the Emulex HBAnyware GUI with Solaris.gz tar xvf HBAnyware-VVV-sparc. Note: Run the unpack_apps script to obtain correct package version if you are installing the Emulex application kit version 300a76 (EmlxApps300a76-Solaris. Finish the installation The installation package continues the installation. 8. Install the Emulex Applications Kit Install the Emulex Applications Kit. Confirm the installation When prompted if you want to continue with the installation.tar. Please contact Emulex for support on HBAnyware GUI. where ZZZ is the application kit version and VVV is the HBAnyware version. press Y to confirm the installation. press Y to confirm the installation. 1. 11. 10.1 Page 10 .6. When it finishes.1.tar pkgadd ±d . select HBAnyware and press Enter.tar gunzip HBAnyware-VVV-sparc. Ignore reboot message A message appears stating that you must reboot the server. Ignore this message and DO NOT reboot at this time (you will reboot at the end of this procedure). 12. This setting prevents the host from issuing warning messages when non-disruptive operations are performed on the EMC storage system: set sd:sd_io_time = 0x3C set sd:sd_max_throttle = 20 … Symmetrix Customer Procedure Generator Version 3. 9. Refer to release notes provided with the driver for information that might be unique to new driver revisions. Confirm the installation When prompted if you want to continue with the installation of HBAnyware. press Q at the prompt to quit the installation package. Finish the installation The installation package continues the installation. Make entry for an I/O timeout and throttle Add a couple of lines to set the I/O timeout and throttle. … … … … 7. When it finishes.

conf) is created automatically by pkgadd. refer to the EMC Fibre Channel with Emulex Host Bus Adapters in the Solaris Environment manual.1. The file contains important information about how the driver should behave. P/N 300-001-156 (available on http://www. Symmetrix Customer Procedure Generator Version 3. For descriptions of the variables. If using PowerPath or DMP failover software. edit the file as shown in the table in step 1. If necessary. Refer to the E-Lab Interoperability Navigator (ESM) for more information.2.emulex. The configuration file (/kernel/drv/lpfc.1 Page 11 .com). … InstallSetupEmlxHBASolarisf_sym001 Table of Contents y Configuring an Emulex HBA driver for Solaris failover support 3 Done Overview This procedure describes how to configure the Emulex HBA driver for failover support on a Solaris host. verify that the installed HBA drivers will support it. Save the file Save the changes you made to the /etc/system file.

Make a copy of the kernel Before editing the current /kernel/drv/lpfc.1 Page 12 . such as greatly increased I/O delays.1.conf file.bak … Note: Using improper settings can cause erratic behavior.1. ip-class 3 fcp-class 3 use-adisc 0 extra-io-tmo 0 post-ip-buf 128 Save the file Save the changes you made to the lpfc. use the following command to make a copy of it in case the file is lost or errors are made: cp /kernel/drv/lpfc.conf /kernel/drv/lpfc. 0x10 0x10 1 1 FC-AL:4 FC-SW:2 16-digit BCD with leading zeroes 16-digit BCD with leading zeroes 6-digit BCD with leading zeroes 1 1 20 20 Symmetix 512 Symmetrix 512 n/a n/a n/a n/a 1 0 0 or 1 0 or 1 256 256 FC-AL:1 FC-AL:1 FC-SW:n/a FC-SW:n/a 60 60 1 0 60 60 0 0 2048 2048 1024 1024 FC-AL:4 FC-AL:4 FC-SW:2 FC-SW:2 3 3 3 3 0 0 0 0 n/a n/a … CiscoZoning_sym001 Table of Contents Symmetrix Customer Procedure Generator Version 3.conf file. Variable Default Value 0 1 2 none none none 1 30 0 n/a n/a 1 0 or 1 256 1 30 0 30 0 256 128 0 Recommended Settings for Symmetrix If no PowerPath or VERITAS DMP PowerPath or VERITAS DMP log-verbose log-only fcp-bind-method fcp-bind-WWNN fcp-bind-WWPN fcp-bind-DID automap lun-queue-depth tgt-queue-depth lpfcNtM-lun-throttle lpfcNtM-target-throttle no-device-delay network-on xmt-que-size scan-down linkdown-tmo nodev-holdio nodev-tmo delay-rsp-err num-iocbs num-bufs topology 2.conf.

Zoneset is a collection of zones in a single fabric. Refer to EMC Knowledgebase article emc66355 for more information. or FA Failure. refer to: http://www.pdf For the entire Configuration guide.com/en/US/docs/storage/san_switches/mds9000/sw/rel_1_x/1_3/fm/configura tion/guide/FMCfgGuide.cisco. To reduce the chance of data unavailability in the event that an HBA. For information on configuring a zone. … Important: EMC Recommends single initiator zoning. then you must use port zoning. Zoneset requires activation in order to be updated.1 Page 13 . 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).y Creating switch zones 3 Done Overview This procedure describes how to create switch zones using Cisco 9000 series switches.cisco.pdf 3. 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 A A A Zone consists of 2 or more members. Note: If you are using an HP-UX server with QuickLoop zoning.com/en/US/docs/storage/san_switches/mds9000/sw/rel_1_x/1_3/fm/configura tion/guide/ZoneCnfg. switch. the host should have at least one primary path and one alternate path to each FA Symmetrix Customer Procedure Generator Version 3. refer to the following: http://www. with only 1 initiator (HBA) per zone Zone is part of a zoneset .1.

Determine the number of Paths needed.EMC.com Symmetrix Customer Procedure Generator Version 3. 3c is the FA and 0 is the port on the FA. 5. The operations above must be performed on both fabrics for all FAs and HBAs. Use the following command: Symmaskdb ±sid SymmID ±dir 3c ±p 0 list database … Where SymmID is the last four numbers of the Symmetrix serial number.1. Determine zoning configuration Follow these steps to determine your zoning configuration: a. move on to configuring the host. Determine the FA WWN by entering the following command: symcfg ±sid XXXX list ±fa all … b. 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. Table of Contents AddingDevices_sym00 4 y Adding Symmetrix Devices 3 Done Overview This procedure explains how to add or create Symmetrix devices from the array¶s free physical disk space.1 Page 14 . Determine the HBA WWN by referencing the OS-specific commands from provisioning a host section. After verifying that the host is logged in.4. This procedure is based on content from the following EMC manual: y EMC Solutions Enabler Symmetrix Array Controls CLI Product Guide This document can be obtained from the EMC Powerlink website at: http://Powerlink. Determine the Active Zone set name. c. d.

or metamembers will need to precisely match corresponding device sizes. CELERRA FBA. remote_config=DeviceConfig. For possible values. ra_group=n. config=DeviceConfig. The syntax for this command is: create dev count=n. ] [. … where: count = The number of devices to create. a cylinder of an FBA device contains 960 512-byte blocks or. Symmetrix Customer Procedure Generator Version 3. In Symmetrix DMX models. refer to Chapter 1 of the Solutions Enabler Symmetrix Array Management CLI Product Guide. symconfigure ±sid 12345 list ±freespace -units MB 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. VME512 FBA.468 megabytes. remote_disk_group _num=nnn]. ] [. or CKD-3390 for z/OS environments. attribute=ckd_meta | savedev [in pool PoolName] [member_state=ENABLE | DISABLE]. Look for free space To check for available free space before you begin. For example. 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. 0. For additional information about sizing devices in cylinders. or 0. data_member_count=nn] [. Use symdev/sympd show or symdev/sympd list ±cyl commands to see relevant device sizes. [dynamic_capability=[dyn_rdf | dyn_rdf1_only |dyn_rdf2_only].1. see the Solutions Enabler Symmetrix Array Control CLI Product Guide. remote_data_member_count=nn. 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. execute one of the following commands: symconfigure ±sid 12345 list ±freespace -units CYLINDERS or 2. which currently must be fixed block architecture (FBA). In earlier Symmetrix models. or CKD-3380. SRDF devices. [.98 megabytes. emulation=EmulationType. disk_group_num=nnn. size = The size of the device needed in number of cylinders. To calculate the number of cylinders. to see how much free space is available on a Symmetrix with an ID of 000000012345.1 Page 15 . size=Cylinders. config = The desired device configuration type.1. a cylinder of an FBA device contains 1920 512-byte blocks. emulation = The device emulation type.1333 Note: Devices to be used as BCV devices.

6 or 14 for RAID 6 (6+2) and RAID 6 (14+2). dyn_rdf1_only ² Creates a dynamic R1 SRDF device. A disk group is a set of physical disks set aside to be used to create devices of the protection level. member_state = States whether the SAVE device(s) being added should be enabled or disabled in the pool. this indicates that the device should be a striped metadevice. or 6 or 14 for RAID 6 (6+2) and RAID 6 (14+2).1 Page 16 . Possible values are: ckd_meta ² When creating a device with an emulation type of CKD-3380 or CKD-3390.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). dyn_rdf2_only ² Creates a dynamic R2 SRDF device. To see how disk groups are organized in your configuration.). use the following commands: symdisk -sid SymmID list -by_diskgroup and Symmetrix Customer Procedure Generator Version 3. PoolName = The name of the SAVE device pool. The specified dynamic capability will be applied to the local device and the corresponding remote device will be assigned a complementary dynamic capability. Set the value to 3 or 7 for RAID 5 (3+1) and RAID 5 (7+1) or. savedev ² When creating a device. ra_group = The RA group number in the SRDF environment. The device will become part of a pool of devices that are used with TimeFinder/Snap for virtual device Snap operations. 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. Disk group usage may improve the performance of some configurations. Possible values are: dyn_rdf ² Creates a dynamic SRDF device. dynamic_capability = The type of dynamic SRDF device to create.1. The name DEFAULT_POOL is reserved to represent the container of all unpooled devices. It can be from 1 to 12 alphanumeric characters long and include hyphens ( . 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. CKD metadevices must be created in sets of four devices. this option allows you to specify a disk group. remote_config = The desired remote SRDF configuration (if any). this indicates that the device should be a SAVE device. and underscore ( _ ) characters. Managing Configuration Changes disk_group_num = When creating a device.

.. this option allows you to specify a remote disk group.. or EF adapter.. config=2-Way-Mir disk_group=1..Established.cmd against a Symmetrix with an ID of 000000012345.... mvs_ssid=0. Note: If the Symmetrix array being used contains an EA.. size=1100. config=2 -Way-Mir disk_group=1. Submitting configuration changes.. Processing symmetrix 000000012345 { create dev count=4.............cmd is used. and to create the hypers to support the new devices in disk group 1.......... For example... create a command file that contains one or more create dev commands.... } Performing Access checks.... mvs_ssid=1. you should see output that looks something like this: A Configuration Change operation is in progress. Please wait.......... Checking Device Reservations..1 Page 17 . to add four new Symmetrix devices to Symmetrix array 000000012345 as twoway mirrored devices with a size of 1100 cylinders (516 MB) using FBA emulation.. 3.......Allowed... config=2-Way Mir. size=1100 cyl. emulation=FBA.. CA. create a command file that contains the following line: create dev count=4........ 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...... emulation=FBA.symdev -sid SymmID list -diskgroup(nn) remote_disk_group_num = When creating a device. CmdFile = A file containing one or more create dev commands.Allowed. size=1100 . Using a text editor.. such as Notepad or the UNIX vi Editor...... a command line that looks more like this should be used instead: create dev count=4.... a file named adddevices.... disk_group=1.. If that is the case... Establishing a configuration change session..Submitted Symmetrix Customer Procedure Generator Version 3.) For example... use the following command: symconfigure -sid 12345 -file adddevices......1.. (For this procedure.... 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. to commit the commands in a command file named adddevices...... emulation=FBA.cmd -v -noprompt commit When this command is executed.

......... You can map devices to front-end director ports.... Step 151 of 151 steps....Done...... Local: COMMIT...Executing.Prepared............1........ Step 004 of 078 steps.. or a range of devices to consecutive addresses by specifying a starting address................ Step 004 of 078 steps........ Step 111 of 151 steps.. New symdevs: 0918:091B Initiating PREPARE of configuration changes..........................Executing. enter the following command: symdev ±sid SymmID list … where: SymmID = The ID of a specific Symmetrix the symdev command is to be executed against.........Executing... COMMIT requesting required resources.... .........com Symmetrix Customer Procedure Generator Version 3..... It is important to note that when creating devices there is no impact on I/O activity...........Executing...............................Validated.....................Obtained...... Initiating COMMIT of configuration changes........ Step 002 of 078 steps............................. This procedure is based on contents from the following EMC manual: y EMC Solutions Enabler Symmetrix Array Controls CLI Product Guide This document can be obtained from the EMC Powerlink website at: http://Powerlink............ Step 114 of 151 steps.. Verify that the desired devices were created To verify that the desired devices were created....... For example......... execute the following command: symdev ±sid 12345 list The devices that were just created should be displayed at the bottom of the list produced........Executing.. Table of Contents MappingDevices_sym00 2 y Mapping Devices within Symmetrix 3 Done Overview This procedure describes how to map devices within the Symmetrix array. The configuration change session has successfully completed.Validating configuration changes.............................Done..........................Queued.................... to see if new devices were successfully created on a Symmetrix with an ID of 000000012345.....Executing.1 Page 18 ...........EMC.... 4...... Terminating the configuration change session........

7. execute the following command: symdev ±sid 12345 list -noport Examine the output produced and identify the Symmetrix devices you want mapped. to obtain a list of Symmetrix devices that have not been mapped to a frontend adapter on a Symmetrix with an ID of 000000012345.6.1 Page 19 . to obtain a list of front-end adapters available on a Symmetrix with an ID of 000000012345. 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 … Formatted: Bullets and Numbering where: SymmID = The ID of a specific Symmetrix the symdev command is to be executed against. 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 SYMMETRIX DIRECTORS Status Ident Symbolic Numeric Slot Type DF-1A DF-2A DF-15A DF-16A DF-1B DF-2B DF-15B DF-16B FA-1C FA-2C FA-15C FA-16C RF-1D RF-2D RF-15D RF-16D 01A 02A 15A 16A 01B 02B 15B 16B 01C 02C 15C 16C 01D 02D 15D 16D 1 2 15 16 17 18 31 32 33 34 47 48 49 50 63 64 1 DISK Online 2 DISK Online 15 DISK Online 16 DISK Online 1 DISK Online 2 DISK Online 15 DISK Online 16 DISK Online 1 FibreChannel Online 2 FibreChannel Online 15 FibreChannel Online 16 FibreChannel Online 1 RDF -BI-DIR Online 2 RDF -R1 Online 15 RDF -R1 Online 16 RDF -BI-DIR Online Symmetrix Customer Procedure Generator Version 3.1.1. 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 Formatted: Bullets and Numbering where: SymmID = The ID of a specific Symmetrix the symcfg command is to be executed against. For example. 2. For example.

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 … Formatted: Bullets and Numbering where: SymmID = The ID of a specific Symmetrix the symcfg command is to be executed against. 0850 Not Visible ..Examine the output produced and identify the front-end adapter to which you want Symmetrix devices mapped.AVAILABLE Total ---Mapped Devices: 413 0 00 697 0 00 698 * 0 00 27F 0 00 280 * 0 00 68C 0 00 143 0 00 144 * 0 00 200 0 00 0CC 0 00 0CD * (M) 0 00 100 (M) Symmetrix Customer Procedure Generator Version 3. port 0 on a Symmetrix with an ID of 000000012345. Port = The port number that device information is to be collected for.--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 . 07CD Not Visible . you should see output that looks something like this: Symmetrix ID: 000000012345 Director Device Name Attr Address ---------------------.--.---.... Adapter = The ID of the front-end adaptor that device information is to be collected for.AVAILABLE 068C Not Visible .-------------------.1 Page 20 .----------------------. 0697 Not Visible .AVAILABLE 07D1 Not Visible .-------.-------------Ident Symbolic Port Sym Physical VBUS TID LUN -----.1.---. 08DC Not Visible . execute the following command: symcfg -sid 12345 list -dir 16c -p 0 -address -available When this command is executed.AVAILABLE 0520 Not Visible . to obtain device information for adapter 16C..---.... For example.8. 3.

1 Page 21 . create a command file that contains one or more map dev commands.1. For Sun.cmd is used.] lun=ScsiLun [. 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. 4. a file named mapdevices.Including Metamembers: 638 Available Addresses: 3281 (s) Legend for Available address: (*): The VBUS. awwn = The user-given name or alias WWN of a host HBA port. if updating a VCM database. you must specify a target number. awwn=awwn|wwn=wwn|iscsi=iscsi]. and LUN number. vbus = The virtual bus address for mapping to an FA port if using volume set addressing. the target number should be 0 in a switched fabric environment. iscsi = The iSCSI name. … Formatted: Bullets and Numbering where: target = The SCSI target ID (hex value). Note: For HP-UX operating systems. masking host_lun=lun | dynamic_lun]. device_number=ckd_device_number ] [. AIX. lun = The SCSI logical unit number (hex value). dynamic_lun = The dynamic LUN addressing scheme. if updating a VCM database.) Symmetrix Customer Procedure Generator Version 3. such as Notepad or the UNIX vi Editor. a virtual bus number. [. if updating a VCM database. (For this procedure. Using a text editor. and Windows. 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. vbus=FibreVbus] [.9. when mapping a CKD device to a z/OS host. LUN addressing is assigned based on what may already be in use for that host HBA. TID. wwn = The unique 64-bit World Wide Name (WWN) identifier for an HBA port. device_number = The CKD device number.

......... The configuration change session has successfully completed............Submitted Locking devices.................. Step 003 of 012 steps........ to map Symmetrix device 000C to port 0 of front-end adapter 16C and assign it the LUN number 0CD....... please wait for completion...... } Performing Access checks... Initiating COMMIT of configuration changes. To update the SYMAPI database.......... ........... Processing symmetrix 000000012345 { map dev 000C to dir 16C:0 lun=0CD.1 Page 22 .... you need to complete host addressing by making sure that the host address is recognized in the SYMAPI view.. Terminating the configuration change session...10...........................For example................Done........Executing.... execute the following command: symcfg discover … Formatted: Bullets and Numbering This may takes some time... Symmetrix Customer Procedure Generator Version 3...................... Initiating PREPARE of configuration changes......Executing..................cmd ±v ±noprompt commit When this command is executed.... COMMIT requesting required resources....Established.. Validating configuration changes.........1. use the following command: symconfigure -sid 12345 ±file mapdevices.........Done..........Validated........ you should see output that looks something like this: A Configuration Change operation is in progress... Step 009 of 012 steps..... Please wait. Step 003 of 012 steps...Obtained.............. .....Queued....................... For example.Allowed. create a command file that contains the following lines: map dev 000C to dir 16C:0 target=0... Submitting configuration changes.......... CmdFile = A file containing one or more map dev commands.. Local: COMMIT....Rediscover the SYMAPI database After performing the proper host procedures to update the host view...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 … Formatted: Bullets and Numbering where: SymmID = The ID of a specific Symmetrix the symconfigure command is to be executed against....................... to commit the commands in a command file named mapdevices.....Prepared.......... Establishing a configuration change session..............Allowed.. Checking Device Reservations.....Locked..........cmd against a Symmetrix with an ID of 000000012345. 6...........Executing................ lun=0CD.. 5............11...

Verify that the device mapping was successful To verify that the device specified was successfully mapped to the front-end adapter. port. and HBAs that reside at a host. To perform masking. If the Symmetrix device was successfully mapped. This host will need to have a fiber path to the Symmetrix and be able to see the VCM device and a gatekeeper. SymDevName = The specific Symmetrix device that detailed information is to be displayed for.7. you will need access to a host that has the Solutions Enabler base installed along with the device masking portion licensed.--------PdevName Type Type Num Sts VBUS TID SYMM Host -----------------------------------------------------------------Not Visible N/A FA 16C:0 RW 000 00 0CD N/A } MaskingDevices_sym00 2 y Masking Devices 3 Done 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. to display detailed information about Symmetrix device 000C on a Symmetrix with an ID of 000000012345.EMC. This procedure is based on contents from the following EMC manual: y EMC Solutions Enabler Symmetrix Array Controls CLI Product Guide This document can be obtained from the EMC Powerlink website at: http://Powerlink. execute the following command: symdev ±sid SymmID show SymDevName … Formatted: Bullets and Numbering where: SymmID = The ID of a specific Symmetrix the symdev command is to be executed against.1 Page 23 .-------. execute the following command: symdev ±sid 12345 show 000C Scan the output produced and examine the section titled ³Front Director Paths´.---.1. you should see something that looks like this: Front Director Paths (1): { -----------------------------------------------------------------POWERPATH DIRECTOR PORT LUN --------.12. front-end director ports.---------.com Symmetrix Customer Procedure Generator Version 3. and LUN specified. In a Symmetrix environment. masking defines a relationship between one or more Symmetrix devices. For example.

---------. to display detailed information about Symmetrix device 000C on a Symmetrix with an ID of 000000012345. The syntax for this command is: symmask -sid SymmID -wwn wwn|-awwn awwn|-iscsi iscsi |-aiscsi aiscsi add devs StartSymDev:EndSymDev|SymDevName|SymDevName.13. … Formatted: Bullets and Numbering Using either the appropriate tools on the host or the configuration documentation where this information was recorded earlier.. 3. port.1... If the Symmetrix device has been mapped. -dir DirNumber -p PortNumber [-noprompt] … Formatted: Bullets and Numbering where: Symmetrix Customer Procedure Generator Version 3.--------PdevName Type Type Num Sts VBUS TID SYMM Host ---------------------------------------------------------------------\\. you must map it to a front-end director..1 Page 24 .14. execute the following command: symdev ±sid SymmID show SymDevName … Formatted: Bullets and Numbering where: SymmID = The ID of a specific Symmetrix the symdev command is to be executed against. If a device to be masked has not been mapped.---. For example.\PHYSICALDRIVE7 N/A FA 16C:0 RW 000 00 016 000 } Repeat this step for every device to be masked. 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. and LUN. SymDevName = The specific Symmetrix device that detailed information is to be displayed for. obtain the WWN for the HBA that one or more devices are to be masked to. 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.-------. execute the following command: symdev ±sid 12345 show 000C Scan the output produced and examine the section titled ³Front Director Paths´. port.1. you should see something that looks like this: Front Director Paths (1): { ---------------------------------------------------------------------POWERPATH DIRECTOR PORT LUN --------. Emulex provides a utility called HBAnywhere that can be used to obtain this information. and LUN before continuing with this procedure.. 2. the syminq hba command can be used as well. If Solutions Enabler has been installed on a host. For example. 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.15.

wwn= A valid World Wide Name (WWN). Verify that the device masking was successful To verify that the device(s) specified were successfully masked. Symmetrix Customer Procedure Generator Version 3.) 4.1. iscsi = A valid iSCSI name. PortNumber = A specific port number designation.16. 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. EndSymDev = The last Symmetrix device name in a range. only the Symmetrix device name that is designated as the metadevice head should be specified (via the SymDevName parameter).SymmID = The ID of a specific Symmetrix the symmask command is to be executed against. aiscsi = A user-given name or an alias iSCSI name. Note: When masking metadevices. DirNumber = The specific director number the Symmetrix device was masked for. so that they can only be accessed by an HBA that has the World Wide Name 10:00:00:00:c9:6c:c8:12. SymDevName = One or more specific Symmetrix device names. For example. to mask Symmetrix devices 000C and 000D. execute the following command: symmaskdb ±sid SymmID list database ±dir DirNumber ±p PortNumber … Formatted: Bullets and Numbering where: SymmID = The ID of a specific Symmetrix the symmask command is to be executed against. 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.1 Page 25 . (which have already been mapped to port 0 of front-end adapter 16C on a Symmetrix with an ID of 000000012345). the devices will be masked for multiple HBAs. StartSymDev = The first Symmetrix device name in a range. (If the -noprompt option is specified. awwn = A user-given name in an ASCII WWN format. the masking operation will execute automatically without requiring user intervention. DirNumber = A specific director number designation.

2009 Director Identification : FA-16C Director Port :0 User-generated Identifier Type Node Name Port Name Devices ---------------. 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. a new file name must be provided each time this command is executed. Refresh the Symmetrix director with VCMDB data Update the Symmetrix array with the configuration changes by performing a director refresh operation.----. For example. For example. execute the following command: symmaskdb ±sid 12345 backup ±file BackupDevMaskDB_1 ±noprompt When this command is executed.e. The syntax for this command is: Symmetrix Customer Procedure Generator Version 3. you should see a message that looks something like this: Symmetrix SymMask database backed up to file BackupDevMaskDB_1 from Symmetrix 000000012345 6.PortNumber = The specific port number the Symmetrix device was masked for. The symmaskdb refresh command is used to force a Symmetrix director to refresh its profile tables with the contents of the Device Masking VCMDB.1. you should see output that looks something like this: Symmetrix ID Database Type Last updated at : 000000012345 : Type6 : 03:55:26 PM on Tue Mar 31. the directory that this command is executed from)..--------10000000c96cc812 Fibre 10000000c96cc812 10000000c96cc812000C:000D 5.--------------------------------.18. This causes the Symmetrix director to refresh its WWN/iSCSI-related profile tables in cache with the content data from the device masking VCMDB. 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. Back up the VCMDB The symmaskdb backup command is used to create a backup copy of the Device Masking VCMDB.1 Page 26 … Formatted: Bullets and Numbering .) The backup copy will be stored in the file specified and that file will be written to the current directory (i. BkupFileName = The name of the file to be used to store the backup copy of the Device Masking VCMDB created.17. (You cannot reuse backup file names. execute the following command: symmaskdb -sid 12345 list database ±dir 16C ±p 0 When this command is executed. The syntax for this command is: symmaskdb -sid SymmID backup ±file BkupFileName -noprompt … Formatted: Bullets and Numbering where: SymmID = The ID of a specific Symmetrix the symmaskdb command is to be executed against.

! 7.20. For example.symmask -sid SymmID refresh -noprompt where: SymmID = The ID of a specific Symmetrix the symmaskdb command is to be executed against. 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.19. this command interrogates all SCSI devices available. For example. the SYMAPI configuration database should be updated on all affected hosts/management servers that are running Solutions Enabler. 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). 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. 8. This is done by executing the following command: symcfg discover … Formatted: Bullets and Numbering … Formatted: Bullets and Numbering When executed. 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. make sure that no application or user activity is taking place on the HBAs that are about to be refreshed). 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. 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.1. If no such utility exists. it can take a significant amount of time to complete. execute the following command: symmask ±sid 12345 refresh ±noprompt When this command is executed. make sure no HBAs are accessing devices in the masked channel (in other words. therefore. with AIX you can execute the cfgmgr command. in Windows you can use the Device Manager to scan for hardware changes. CreateDevGroup_sym00 2 Symmetrix Customer Procedure Generator Version 3.1 Page 27 .

For example. and specify that it is a REGULAR device group.com 1. assign it the name TFgroup. Create a new device group The symdg create command is used to create a new device group. Symmetrix devices on Symmetrix array 000000012345 were used.) On the other hand. (Composite groups are used to group devices that reside on different Symmetrix arrays. Examine device groups you already have Since device group names must be unique.23.21. This procedure is based on content from the following EMC manual: y EMC Solutions Enabler Symmetrix Array Management CLI Product Guide This document can be obtained from the EMC Powerlink website at: http://Powerlink. execute a symdg create command that looks like this: symdg create TFgroup ±type REGULAR 3. To view a list of device groups that have already been created. The syntax for this command is: symdg create DgName [-type REGULAR | RDF1 | RDF2 | RDF21] … Formatted: Bullets and Numbering where: DgName = The name to assign to the device group.EMC.22.y Creating a Device Group 3 Done 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. Add Symmetrix devices to the group The symld command is used to add devices to an existing device group. Device groups and composite group definitions are created locally through an attached host. before you attempt to create a new one you should find out what device groups have already been created.) Symmetrix Customer Procedure Generator Version 3. execute the following command: symdg list … Formatted: Bullets and Numbering 2. to create a device group. Individual devices can be added by specifying either the physical device name (add pd) or the Symmetrix device name (add dev).1. 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. as follows: symld -g TFgroup add pd /dev/rdsk/c4t0d0s2 symld -g TFgroup -sid 12345 add dev 000C … Formatted: Bullets and Numbering 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.1 Page 28 .

to verify that a device group named TFgroup was created and the appropriate devices were assigned to it. Verify the device group creation To verify that the device group was successfully created and that the appropriate devices were added to it.4. -------------------------------------------------------------------DEV001 N/A 000C RW DEV002 N/A 000D RW DEV003 N/A 000E RW } Sts 1031 1031 1031 (MB) Setup Solaris Emulex kernel config files and add LUNs KernelBindingEmlxLunsSolaris_sym001 The following procedures specific to Emulex HBAs describe how to add persistent bindings and LUNs to the Solaris kernel config files.24.1. execute the following command: symdg show TFgroup When this command is executed. For example.1 Page 29 . you should see output that looks something like this: Group Name: TFgroup Group Type Device Group in GNS Valid Symmetrix ID Group Creation Time Vendor ID Application ID Number Number Number Number Number Number Number Number Number Number Number Number Number : REGULAR : No : Yes :000000012345 : Mon Mar 23 08:50:17 2009 : EMC Corp : SYMCLI of STD Devices in Group : 3 of Associated GK's : 0 of Locally-associated BCV's : 0 of Locally-associated VDEV's : 0 of Locally-associated TGT's : 0 of Remotely-associated VDEV's(STD RDF): of Remotely-associated BCV's (STD RDF): of Remotely-associated TGT's(TGT RDF) : of Remotely-associated BCV's (BCV RDF): of Remotely-assoc'd RBCV's (RBCV RDF) : of Remotely-assoc'd BCV's (Hop-2 BCV) : of Remotely-assoc'd VDEV's(Hop-2 VDEV): of Remotely-assoc'd TGT's (Hop-2 TGT) : 0 0 0 0 0 0 0 0 Standard (STD) Devices (3): { -------------------------------------------------------------------Sym Cap LdevName PdevName Dev Att. execute the following command: symdg show DgName … Formatted: Bullets and Numbering where: DgName = The name that has been assigned to the device group. Symmetrix Customer Procedure Generator Version 3.

31. repeating them for each adapter. Before you add LUNs to sd. 29. follow these precautions: y Do not delete any original data from this file. LUN Numbers being 0 ± 255. Reboot the server by entering the following command: reboot -. … y The instructions for dynamically adding new devices is described in the Manual Set ± Emulex Documentation Drivers and Software. 30. Select 5. where n is the number of adapters installed in your system.-r Table of Contents KernelBindingEmlxLunsSolarisb_sym001 y Adding LUNs to the Solaris config file for Emulex HBA 3 Done Overview This procedure adds LUNs to the Solaris Emulex config file (sd. 28. ± Bind by port name. follow the steps below.com/ts/docfc/solframe. Devices accessed with Emulex Fibre Channel adapters and Emulex drivers can be up to 512 targets. Select an adapter.conf should contain all Targets and LUNs that a user may want to access. On the menu that appears select 5.KernelBindingEmlxLunsSolarisa_sym001 y Adding persistent bindings to Solaris Emulex kernel files 3 Done Overview The Emulex driver comes with a utility called lputil to set up persistent bindings (among other functions). with a maximum of 256 LUNs per target.1 Page 30 . ± Bind Automapped Targets.htm Symmetrix Customer Procedure Generator Version 3. When prompted. 0-n.emulex. 27.conf). To set up persistent bindings. select Y (yes). When editing the file. 25. which can be obtained from http://www. The file is very sensitive to hidden format characters. Type the following command and press Enter: /usr/sbin/lpfc/lputil … … … … … … … 26. Select 2. y Do not insert hidden format characters.conf. Bind all auto-mapped targets? (Y/N) = >. verify that the HBA and HBA drivers have been installed in the Solaris computer. The Solaris configuration file /kernel/drv/sd. ± Persistent Bindings. Enter all target and LUN values in decimal format and avoid leading zeros (0) when entering the LUN value. EMC storage array devices are addressed using Target IDs and LUNs. and a misplaced tab or other formatting character can make all subsequent entries unreadable.1.

Note: Make sure that only the target=x lun=0 line is specified for any target ID that does not need LUN support. Modify the /kernel/drv/sd. Use the following format to construct entries in the sd. # name="sd" class="scsi" target=17 lun=0. connected to a Fibre Channel HBA. Symmetrix Customer Procedure Generator Version 3. # A small number of LUNs for a RAID array # name="sd" class="scsi" target=17 lun=1.bak … … 2. # You should add any new entries between this line # and the End lpfc auto generated configuration line # name="sd" class="scsi" target=16 lun=0. The lines in bold are added to the file.1. Make a copy of the kernel Before editing the current /kernel/drv/sd. Therefore.1 Page 31 . name="sd" class="scsi" target=6 lun=4.conf file contains entries for LUN 0 only. name="sd" class="scsi" target=5 lun=2.conf file.do NOT alter or delete this line # WARNING: anything you put within this auto -generated section # will be DELETED if you execute pkgrm to remove the lpfc driver # package . name="sd" class="scsi" target=5 lun=3. # You may need to add additional lines to probe for additional # LUNs or targets. name="sd" class="scsi" target=5 lun=5.conf. If the user wants the sd driver to probe only for target=X and lun=Y on adapter lpfcZ.conf file illustrates how to add LUNs.conf file for the target ID and LUN: name=´sd´ class=´scsi´ target=´X´ lun=´Y´. This example adds devices to FA 1 (target 5) and FA 16 (target 6) of a storage system. name="sd" class="scsi" target=5 lun=0.conf file The default sd.1. # name="sd" class="scsi" target=17 lun=2. the class=´scsi´ entries for target=X and lun=Y must be deleted. name="sd" class="scsi" target=6 lun=1.conf. name="sd" class="scsi" target=6 lun=3. This entry will not cancel the effect of any other class=´scsi´ entries for target=X and lun=Y. # name="sd" class="scsi" target=17 lun=3.conf /kernel/drv/sd. The following sample sd. # Start lpfc auto-generated configuration -. name="sd" class="scsi" target=5 lun=1. name="sd" class="scsi" target=6 lun=0. Devices accessed through Fibre Channel using the Emulex adapter and Emulex driver are addressed behind a single target ID with multiple LUNs (up to 256). you must edit the file to add entries for any LUNs with numbers greater than 0 that you will bind in the storage systems connected to the server. You SHOULD delete any lines that represent # lpfc targets or LUNs that are not used. You will add devices under the entries for the lpfc parent. use the following command to make a copy of it in case the file is lost or errors are made: cp /kernel/drv/sd. name="sd" class="scsi" target=5 lun=4. name="sd" class="scsi" target=6 lun=2. This decreases the time needed to reboot the system. to sd.

name="sd" class="scsi" target=6 lun=5. If you must. The following steps are provided only as a general or possible guide and not meant to supersede your site preferences.1 Page 32 . if the HBA is 1. y S is the target ID (0 through 125) of the SP connected to HBA cD. It describes how to use the format command to label and partition devices. For example. This might take a few minutes or so to execute. and the LUN number is 2. Symmetrix Customer Procedure Generator Version 3. For example. it is 1. it may necessary to do a disk or device scan of the I/O bus with this procedure. … Table of Contents MakeLunsAvailSolaris_sym00 2 y Making LUNs or Devices available to Solaris 3 Done Overview This procedure describes how to make the devices or LUNs available or visible to a Solaris host. Driver 6. a reboot will also accomplish the same thing (device discovery). # End lpfc auto-generated configuration -. the target ID of the FA is 0. Solaris disk names have the following form: cDtSdLsP where: y D is the number of the HBA in the server (controller number). y L is the LUN number (0 through 255). you have to reboot the host for the changes in the sd. to perform a device scan (discover) to make the devices visible to the host workstation. as scanning devices can cause pauses and crashes to other operational processes running on this host. apply the necessary operating system native commands. even if the unassigned Target IDs and LUNs were not in sd. for an HBA in slot 2. Under some conditions. you would format the disk by entering the following command: format c1t0d2 Note and Caution: If your host system cannot see the devices.1.conf at the last system reboot. If you can and prefer. the number for an HBA in slot 1 is 0. Solaris assigns these numbers.x or later supports adding new Target IDs and LUNs without rebooting. y P is the partition number on the target. Solaris may assign other numbers to HBAs. at an appropriate low-peak time in your production environ ment.x or older. Reboot the host If you are using Emulex driver 5.conf file to take effect. Be sure you follow your operating system specific administrators guide and/or known site procedures for this operation.do NOT alter or delete this line 3.

label it using the label command. For example. You must use the mount command to mount the file systems that you have created on your storage system. e. select Available Drive Types. use the format command again. enter the following command: mount /dev/dsk/c1t0d0s0 /temp … Table of Contents InstallPowerpathSolaris_sym001 Symmetrix Customer Procedure Generator Version 3. b. 33. to make a file system on partition 0 on the first disk (device). You must specify a character device name to indicate the partition where you want to create the file system. If you use the format command with no arguments. If you have not labeled the disk. c. at the mount point /temp. Mount the file systems: This procedure is the same as for any device used with a Sun operating system.32. At the Specify disk type prompt. Partition and label devices: The version of the format command that ships with Solaris has an auto-configure option that configures devices (disks) for you. d. For example. Create file systems on partitions: Use the newfs command to make file systems on all newly created partitions.1 Page 33 . as follows: a. Specify the block device name of the partition where you created the file system and the mount point directory. enter the following command: newfs /dev/rdsk/c1t0d0s0 … 34. If you want to partition the disk. enter 0 to select the auto-configure option. enter the following command: format diskname … where diskname is in the form explained in the previous section. it displays all disks. At the root prompt. to mount the file system partition 0 of the first disk configured. From the Format menu.1.

EMC. which is the current shipping version for Solaris hosts. Determine if the PowerPath software you are installing requires the removal or presence of a previous version of PowerPath. For example: mount -F hsfs -r /dev/dsk/c0t2d0s0 /cdrom/cdrom0 Symmetrix Customer Procedure Generator Version 3. y. enter mount -F hsfs -r /dev/dsk/cxtydzs0 /cdrom/cdrom0 where x.EMC. 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. Verify that you are logged in as root. This procedure is based on content from the following EMC manual: y PowerPath for Solaris Installation and Administration Guide This document can be obtained from the EMC Powerlink website at: http://Powerlink. 35. For example. y … f. Note: This procedure is specific to the installation of PowerPath version 5. For instructions on installing older versions of PowerPath. refer to the applicable PowerPath installation manual available on PowerLink. Also.x. and whether those patches have any added prerequisites that must be met before you install PowerPath.com Verify the following prior to the installation of PowerPath: y Review the patch ReadMe files to determine which patches (if any) you want to install after PowerPath. If it does not. Some full versions require the previous version to be removed while others do not. and z are values specific to the host¶s CD-ROM drive.0. some patches require the full version to be present while others require it to be removed.com. Insert the CD-ROM in the CD-ROM drive. then you must mount it manually. Mount the PowerPath CD-ROM: Mount the PowerPath CD-ROM as follows: e. The CD should mount automatically. to mount the CD on /cdrom/cdrom0.1.1 Page 34 .y Installing PowerPath software on a Solaris host 3 Done Overview This procedure describes how to install PowerPath on a Solaris host. These documents are available on http://Powerlink.

If you do not have a graphics terminal. f.1 Page 35 . press Enter to accept the default base directory (/opt) or type the path to an alternate base directory and press Enter. At the packages available prompt. enter: cd /cdrom/cdrom0/UNIX/SOLARIS y On Opteron hosts. e. At the prompt for an installation directory for the program files. Install PowerPath Install the PowerPath software as follows: a. g. Change to the /mount_point/UNIX/SOLARIS directory. Make a note of the name and location of the PowerPath base directory for future reference. enter y and press Enter.1. enter: cd /cdrom/cdrom0/UNIX/SOLARIS_i386 c. the installation process creates the EMCPower subdirectory. enter 1 and press Enter. Start the installation by entering: /usr/sbin/pkgadd -d .) b. Note: the required space and period after the -d parameter.36. Symmetrix Customer Procedure Generator Version 3. Enter q and press Enter. (After pkgadd completes. Note: PowerPath installs its files in /basedir/EMCPower. run the script filename command to record pkgadd output in the specified file. d. The screen will display information about the installation. use CTRL-D to stop … recording the output. At the prompt to continue the installation. y On SPARC hosts.

37. If you are registering PowerPath on a Solaris 10 host. Enter the following command: /etc/emcpreg ±install c. … b. e. it can be entered at a later point. Refer to the PowerPath 5. If you failed to enter the registration key during installation. then perform these steps.0. Press Enter and you will see the following output: 1 key(s) successfully registered.1 Page 36 . which is the default policy without a valid PowerPath license.1.x Product Guide or the powermt(1) manpage for more information. Run the powermt set policy command to reset the load balancing and failover policy. Refer to the PowerPath 5. Register PowerPath After the installation completes. Otherwise. Run powermt save to save the settings in the powermt. you need to manually set the policy. rebooting PowerPath after you register the software sets the load balancing and failover policy to the default values. Note: On Solaris 8 and 9 hosts.0. you must register PowerPath on the host: a. WARNING: Failing to enter a registration key will result in the installation of PowerPath SE. which has your license registration key printed. therefore. At the registration key prompt. At the prompt. Locate the PowerPath License Key Card. enter the PowerPath registration key and press Enter.x Product Guide for more information on setting the load balancing and failover policy. delivered with the PowerPath media kit. d. If you enter a valid registration key. Symmetrix Customer Procedure Generator Version 3. However.custom file. Solaris 10 does not require a reboot. type y and press Enter. proceed to the next section. you see a success message. f.

39. Post activities After PowerPath is registered on the host. Symmetrix Customer Procedure Generator Version 3.1 Page 37 . If required by your specific PowerPath version or patch. Install the patch package by entering the following command: patchadd .38.1. unmount the CD-ROM by entering the following command and then ejecting the CD-ROM: unmount /cdrom/cdrom0 b. unmount and eject the CD-ROM.-r Note: If the sd or ssd driver does not exist on the host. install any PowerPath patches from the following URL: http://Powerlink. you will see a forceload failed warning during boot. This file will also state whether you need to reboot the host after the installation of the patch. Enter the following command and remove the CD-ROM: eject … y If vold is not running.EMC. Remove the CD-ROM as follows: y If the CD-ROM volume management daemon vold is running.com … Note: A readme file that explains how to install the patch accompanies every patch release. perform the following: a. Check for patches If necessary. reboot the host by entering: reboot -. You can safely ignore this warning.

Furthermore. 41. emcpmpc. Check for proper install Verify that PowerPath is installed properly on the host as follows: a. Enter the command: devfsadm … New native devices are created.0.1 emcpsapi (PP SAPI Ext 5.1 Page 38 .0.1 emcpsf (PP SF 5.0.0.0) 12be610 12440 . PKGINST: EMCpower NAME: EMC PowerPath CATEGORY: system ARCH: sparc VERSION: 5.1 emcpgpx (PP GPX Ext 5.0.x for Solaris. Make paths visible The operating system must recognize new paths before PowerPath can.1.40. emcpmpap. do not use them until PowerPath is configured in the next step of this procedure.1 emcpcg (PP CG Ext 5.1 emcpdm (PP DM Manager 5.0) Note: The emcpmp.0.0) 7bb7e6d0 3180 .0.0) 7b7a7e10 2c8 . Verify that the PowerPath kernel extension is loaded on the host by entering: modinfo | grep emc You should see output similar to the following: 31 32 33 34 35 36 37 38 7bbfa000 2c28 163 1 emcp (PP Driver 5.1 emcpioc (PP PIOC 5.0) 7b68fe88 78e8 .0) 1336620 21e60 .0_bxxx BASEDIR: /opt VENDOR: EMC Corporation PSTAMP: cambridge951018123443 INSTDATE: Feb 15 2006 08:24 STATUS: completely installed FILES: 286 installed pathnames 5 shared pathnames 38 directories 121 executables 107843 blocks used (approx) b.0.0. and emcpmpaa extensions present in previous releases have been replaced by the emcpmpx extension in PowerPath 5.0) 7bb3a000 30ce8 154 1 emcpmpx (PP MPX Ext 5.0. the HighRoad (emcphr) extension has been removed from PowerPath 5.x. Enter the command: pkginfo -1 EMCpower … You should see output similar to the following: Note: When you install PowerPath on an AMD Opteron host. Symmetrix Customer Procedure Generator Version 3.0) 7ae00000 dada8 .0. however. i386 appears in the ARCH row.

Configure missing devices Examine the output to determine if some storage system logical devices are not configured as PowerPath devices. the expected LUNs are visible and each has the expected number of paths. … … 43. Check the configuration Inspect the new PowerPath configuration as follows: powermt display dev=all. The new path(s) should be displayed with a state of alive. Scan operating system error logs to ensure no errors are logged against the new paths. Save the configuration Save the configuration by running the following command: powermt save … … … 45.1 Page 39 . 44. Table of Contents Symmetrix Customer Procedure Generator Version 3. Verify that each HBA sees only the targets (FAs) to which it is zoned. Correct any issues detected.1. Configure PowerPath Configure PowerPath by running: powermt config.42. Enter the following commands to configure any missing devices: powercf ±q powermt config Rerun the powermt display dev=all command to confirm the following: y y the logical devices are configured as emcpower devices and the correct failover and load balancing policy is set. Check for missing PowerPath devices If you must. check for missing PowerPath devices using the following command: powermt display dev=all 46.

Sign up to vote on this title
UsefulNot useful