Host To Storage SAN Implementation

Host to Storage SAN
Implementation
Lab Guide
Education Services
October 2007
Host to Storage SAN Implementation
Lab Guide
Copyright:
Copyright 1996, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007 EMC Corporation. All Rights
Reserved.
EMC believes the information in this publication is accurate as of its publication date. The information is
subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO
REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN
THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY
OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable
software license.
EMC, ICDA (Integrated Cached Disk Array), and EMC2 (the EMC logo), and Symmetrix, are registered
trademarks of EMC Corporation. EMC and SRDF are trademarks of EMC Corporation.
All other trademarks used herein are the property of their respective owners.
Copyright 2007 EMC Corporation. All Rights Reserved.
Version 5.5
Page 2 of 197
Lab Guide
Trademark Information:
EMC
Trademarks
EMC2, EMC, Symmetrix, Celerra, CLARiiON, CLARalert, Connectrix, Dantz,

Documentum, HighRoad, Legato, Navisphere, PowerPath, ResourcePak,
SnapView/IP, SRDF, TimeFinder, VisualSAN, and where information lives are
registered trademarks and EMC Automated Networked Storage, EMC
ControlCenter, EMC Developers Program, EMC OnCourse, EMC Proven,
EMC Snap, Access Logix, AutoAdvice, Automated Resource Manager,
AutoSwap, AVALONidm, C-Clip, Celerra Replicator, Centera, CentraStar,
CLARevent, CopyCross, CopyPoint, DatabaseXtender, Direct Matrix, Direct
Matrix Architecture, EDM, E-Lab, Enginuity, FarPoint, FLARE, GeoSpan,
InfoMover, MirrorView, NetWin, OnAlert, OpenScale, Powerlink,
PowerVolume, RepliCare, SafeLine, SAN Architect, SAN Copy, SAN
Manager, SDMS, SnapSure, SnapView, StorageScope, SupportMate,
SymmAPI, SymmEnabler, Symmetrix DMX, Universal Data Tone, and
VisualSRM are trademarks of EMC Corporation. All other trademarks used
herein are the property of their respective owners.
Third Party
Trademarks
AIX is a registered trademark of International Business Machines Corporation.

Brocade, SilkWorm, SilkWorm Express, and the Brocade logo are trademarks
or registered trademarks of Brocade Communications Systems, Inc., in the
United States and/or in other countries. Compaq and the names of Compaq
products referenced herein are either trademarks and/or service marks or
registered trademarks and/or service marks of Compaq. Hewlett-Packard, HP,
HP-UX, OpenView, and OmniBack are trademarks, or registered trademarks of
Hewlett-Packard Company. McDATA, the McDATA logo, and ES-2500 are
registered trademarks of McDATA Corporation. Microsoft, Windows, and
Windows NT are either registered trademarks or trademarks of Microsoft
Corporation in the United States and/or other countries. NobleNet is a
registered trademark of Rogue Wave Software, Inc. SANbox is a trademark of
QLogic Corporation. Sun, Sun Microsystems, the Sun Logo, SunOS and all
Sun-based trademarks and logos, Java, the Java Coffee Cup Logo, and all Javabased trademarks and logos, Solaris, and NFS, are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States and other countries.
UNIX is a registered trademark of The Open Group.
Version 5.5
Page 3 of 197
Lab Guide
Document Revision History:
Rev #
V 5.5
File Name
Host to Storage SAN
Implementation Lab Guide
Date
October, 2007
Version 5.5
Page 4 of 197
Lab Guide
Table of Contents: Host to Storage SAN Connectivity
Copyright: ........................................................................................................................... 2
Trademark Information: ......................................................................................................3
Document Revision History: ...............................................................................................4
Table of Contents: Host to Storage SAN Connectivity ......................................................5
Lab Exercise 1: Site Environment Qualification .....................................................................7
Lab Exercise 1.................................................................................................................... 8
Part 1: Basic Steps............................................................................................................ 8
Lab Exercise 1.................................................................................................................... 9
Part 2: Logical Site Inspection and Data Gathering...........................................................9
Lab Exercise 1.................................................................................................................. 14
Part 3: Qualification of SAN System Components........................................................... 14
Lab Exercise 1.................................................................................................................. 15
Part 4: Compile, Document and Publish Results............................................................. 15
Lab Exercise 2: SAN/Switch Configuration ..........................................................................24
Lab Exercise 2.................................................................................................................. 25
Part 1: M-Series Switch and Director Configuration Procedures (Connectrix Manager
9) ...................................................................................................................................... 25
Lab Exercise 2.................................................................................................................. 34
Part 2: B-Series Switch Configuration Procedures .......................................................... 34
Lab Exercise 2.................................................................................................................. 37
Part 3: MDS-Series Switch Configuration Procedures .................................................... 37
Lab Exercise 3: Attaching Hosts and Configuring Host Bus Adapters (HBAs), Part 1 ......... 43
Lab Exercise 3.................................................................................................................. 44
Part 1: Array Port Allocation ............................................................................................44
Lab Exercise 3.................................................................................................................. 45
Part 2: Install Required Patches ......................................................................................45
Lab Exercise 3.................................................................................................................. 46
Part 3: Install HBA Driver and Firmware..........................................................................46
Lab Exercise 4: Configuring Zoning .....................................................................................69
Lab Exercise 4.................................................................................................................. 70
Part 1: Connectrix Manager Zoning for M-Series Directors/Switches (Connectrix
Manger 9.x) ...................................................................................................................... 70
Lab Exercise 4.................................................................................................................. 74
Part 2: M-Series Connectrix Manager Basic Zoning........................................................ 74
Lab Exercise 4.................................................................................................................. 75
Part 3: B-Series Web Tools Zoning ..................................................................................75
Lab Exercise 4.................................................................................................................. 79
Part 4: MDS Switch CLI Zoning Configuration................................................................. 79
Lab Exercise 4.................................................................................................................. 83
Part 5: Post Zoning Tasks ...............................................................................................83
Lab Exercise 5: Array Configurations EMC Symmetrix..................................................... 84
Version 5.5
Page 5 of 197
Lab Guide
Lab Exercise 5.................................................................................................................. 85

Part 1: Preamble: The Array Environment Configuration Array Host Port Allocations..... 85
Lab Exercise 5.................................................................................................................. 86
Part 2: Installing Solutions Enabler (SE) - UNIX.............................................................. 86
Lab Exercise 5.................................................................................................................. 89
Part 3: Discovering and Viewing the Storage Environment ............................................. 89
Lab Exercise 5.................................................................................................................. 93
Part 4: Modifying Storage Host Port (FA ports) Configuration Settings ........................... 93
Lab Exercise 6: Array Configurations EMC CLARiiON ....................................................96
Lab Exercise 6.................................................................................................................. 97
Preamble : The Array Configuration Array Host Port Allocations ..................................... 97
Lab Exercise 6.................................................................................................................. 98
Part 1: Installing CLARiiON Procedure Generator........................................................... 98
Lab Exercise 6................................................................................................................100
Part 2: Installing Navisphere.......................................................................................... 100
Lab Exercise 6................................................................................................................107
Part 3: Discovering Storage ..........................................................................................107
Lab Exercise 7: Configuring HBAs and Host Specific Files................................................ 113
Lab Exercise 7................................................................................................................114
Part 1: Integrating the Host to an EMC Fibre Channel Environment - UNIX ................. 114
Lab Exercise 8: Assigning Storage .................................................................................... 117
Lab Exercise 8................................................................................................................118
Part 1: Solutions Enabler - Symmetrix........................................................................... 118
Lab Exercise 8................................................................................................................123
Part 2: Navisphere CLARiiON .................................................................................... 123
Lab Exercise 9: Multipathing Installing EMC PowerPath ................................................ 128
Lab Exercise 9................................................................................................................129
Part 1: Multipathing in Solaris........................................................................................129
Lab Exercise 9................................................................................................................131
Part 2: Multipathing in AIX.............................................................................................131
Lab Exercise 9................................................................................................................135
Part 3: Multipathing in HP-UX........................................................................................135
Lab Exercise 9................................................................................................................137
Part 4: Multipathing in Windows ....................................................................................137
Lab Exercise 10: LVM Implementation ..............................................................................139
Lab Exercise 10..............................................................................................................140
Part 1: LVM Implementation in HP-UX ........................................................................... 140
Lab Exercise 10..............................................................................................................150
Part 2: HP-UX Volumes with PV-Links Multipathing...................................................... 150
Lab Exercise 10..............................................................................................................157
Part 3: LVM Implementation on AIX .............................................................................. 157
Lab Exercise 11: Managing Storage in the SAN Environment .................................... 160
Lab Exercise 12: Reclaiming Storage and SAN Resources........................................ 173
Appendix 1: Installing lpfc driver in Solaris Environment............................................. 181
Appendix 2: Commands.............................................................................................. 189
Version 5.5
Page 6 of 197
Lab Guide
Lab Exercise 1: Site Environment Qualification

Purpose:
The goal of this lab is to qualify all SAN related components of the
site. Gather data on the following components which need to be
qualified:
A. Host: HBA; firmware; OS version; platform support; LVM
(logical volume manager) support
B. Switch: firmware; ISL count; hops to storage; FA to switch
connectivity
C. Array: microcode version; host-port configuration; available
free storage
Using the worksheets in this lab, in conjunction with available online tools, gather the necessary data to complete the qualification.
Objectives:
References:
This lab is designed to be completed in both the classroom and

datacenter.
A. Physical and logical inspection
B. Data gathering
C. Analysis
D. Document and publish results
Host to Storage SAN Implementation Student Resource Guide
Version 5.5
Page 7 of 197
Lab Guide
Lab Exercise 1
Part 1: Basic Steps
Step Action
1
Using the worksheets in this lab, gather the required data on the environment.
A. Capture data locally, make notes of software revisions and current
configurations
B. Gather data electronically using EMC grab or other scripts
C. Analyze data, complete SAN host worksheet with storage allocations
D. Working with EMC Support Matrix and Product Guides, develop
recommended steps and/or procedures to complete upgrades and site
preparation
Data gathering in this lab will be used for planning and qualification.
Additionally, such data on the environment will be used to develop final
documentation and records of what was accomplished in the planning and build
process.
By documenting the process and current status of the environment, records will
be kept. To maintain records, or review currently implemented systems at an
EMC customer site, please visit:
http://omega.eng.emc.com/omega/
Remember, the website is for internal use only.
Version 5.5
Page 8 of 197
Lab Guide
Lab Exercise 1
Part 2: Logical Site Inspection and Data Gathering
Capture the following details:
Host
1
2
3
4
Model
Operating Environment version and patch level
HBA model and firmware level
LVM (logical volume manager) version and type (e.g. native or Veritas)
Gather the necessary data using the following OS specific commands. Record your
results in the space provided:
AIX
Step Action
1
Model
#indicates model number
uname M

#Shows release version and release of OS
uname rv
#Reports the latest installed maintenance level (patch level) of

the system.
oslevel

# List all devices in the system, search for fibre channel
# Youll want to search for something like: FC Adapter
lsdev |more
#List device drivers (including HBAs) installed in the system:
lsdev C c driver
Version 5.5
Page 9 of 197
Lab Guide
#Find LVM software installed on system
lslpp L bos.rte.lvm
#Finds all software sets installed on system
lslpp L |more
#Gather all system specific information, save to /tmp

snap g
Solaris
Step Action
1
Model
#Model number, OS version, and latest kernel patch applied
uname a

#Show summary information regarding system OS and patch level
showrev

#Print hardware configuration data including all I/O cards
installed in the system
/usr/platform/`uname -i`/sbin/prtdiag -v |more
#Print HBA firmware version

#Print long output for all installed software subsystems
pkginfo l lpfc (just for Emulex)
pkginfo L |more
#Look for ODS and VRTS on the system
pkginfo L |grep i ods
pkginfo L |grep i vrts
Version 5.5
Page 10 of 197
Lab Guide
Linux
Step Action
1
uname a

#Print HBA information
#Print long output for all installed software subsystems
lspci |grep (Emulex or Qlogic)
HP-UX
Step Action
1
Model
uname a

#Display version and type of HP-UX
swlist l bundle

#Print HBA firmware version
#Print long output for installed HBAs
ioscan fnC fc
#Look for LVM software information
swlist l product PH* |more
Version 5.5
Page 11 of 197
Lab Guide
Windows
Step Action
1
Model, Operating Environment version and patch level
#Model number, OS version, and latest kernel patch applied. From
DOS:
winver

#Display version and type of HBAs
Right click My Computer manage Device Manager->SCSI and RAID
controllers
If the systems are known to have specific HBA models, check with the
vendor tools to access local configuration tools. For example, check for
lputil on UNIX for Emulex cards.
Version 5.5
Page 12 of 197
Lab Guide
GRAB Utility
NOTE: If you are not an EMC employee or do not have physical access to the
equipments, please skip to LAB 2.
Lastly, before leaving the site, try running the EMC Grab utility to gather data and
experiment with the grab output. The grab utility can be sourced from:
ftp://ftp.emc.com/pub/emcgrab
Step
1
Action
Once connected, select either Unix or Windows to download the appropriate
compressed file. For example:
ftp> bin
200 Type set to I.
ftp> get emcgrab_AIX_v3.7_1.tar
After downloading the emcgrab file, uncompress the tar file, using tar. For
example:
tar -xvf emcgrab_AIX_v3.7_1.tar
Run the grab script and save the output. Once the data has been collected,
visit the GS Tools website at: http://toolbox.isus.emc.com/
This site will list other utilities which are useful for gathering data and for
analyzing the output from grab files (e.g. look for the link to the Heat (Host
Environment Analysis Tool) utility under the Analysis Tools menu)
Analyze all data and prepare it for input into the host matrix worksheet for
system planning.
Version 5.5
Page 13 of 197
Lab Guide
Lab Exercise 1
Part 3: Qualification of SAN System Components
Qualification of each host, HBA, software component, switch, and array within a SAN
can be both a tedious and time-consuming task. Leverage any online tools available to
help save time and aid in the qualification process.
Manually qualify your SAN systems by researching each component building towards
and aggregate plan by using the EMC Support Matrix. Available at:
http://www.emc.com/interoperability/matrices/EMCSupportMatrix.pdf OR as a zip:
http://www.emc.com/interoperability/matrices/EMCSupportMatrix.zip
As an alternative you can use e-lab navigator:
http://elabnavigator.emc.com
Version 5.5
Page 14 of 197
Lab Guide
Lab Exercise 1
Part 4: Compile, Document and Publish Results
Using the following spreadsheets, create a version representing the current
configuration and one for your recommended target system upgrades. The second
spreadsheet should list all upgrades and recommendations for the steps in performing
the upgrades. If all work can be done at once, simply remove the steps and proceed
with the following order:
OS upgrade
HBA firmware upgrade
LVM software patch/upgrade
Any other miscellaneous upgrade
Version 5.5
Page 15 of 197
Lab Guide
Status
not started
Version 5.5
Host Collection tab of this workbook.

Booting off the symm? (LUN limit)
Metas: striped or concatenated how many members, size of hypers.
LUN limit per FA.
LUN limit per HBA.
Fanout ratios.
Bit Settings in BIN file - VCMDB on proper FA ports.
PowerPath/DMP/PVLinks.
Cluster considerations: VCS, SUN Cluster, GAB, Quorum other.
OPS
Backup: EDM or other; Tape SCSI or FC bridges. STG Gatekeepers.
The host (mgmt station) where ESN Manager will be installed and its IP
address. Gatekeepers.
Timefinder/BCV: no allocation to servers or allocated to backup server, or
other servers? Gatekeepers.
SRDF: R1 R2 relationship. Gatekeepers.
Enough ports on the switches? Include HBAs, FAs, ISLs, Bridges.
If adding disk, is there enough cache?
Email notification: will it be used and who is (are) the recipient(s).
IP configuration for Connectrix Service Processor and/or fibre channel
switches.
Will remote workstations be used for managing the Connectrix Manager
Server (CMS); if so, IP addresses and host names?
Connectrix firmware level?
Cascaded Fabrics?
Is cabling within guidelines? (9 micron-20km, 50 micron-500m, 62.5
micron-300m)
Hop count OK? (including patch panels)
Task
EMC Design Checklist
Page 16 of 197
Assigned To
Comments
The following document is from the Checklist Worksheet within the EMC Planning and Design Guide workbook. The full
EMC Planning and Design Guide Workbook is available at: http://powerlink.emc.com
Site Design Check List:
Modem phone numbers for each Connectrix Service Processor (CMS).

Connectrix Manager software version?
Will SNMP be used for error trapping? if so, the Community name,
recipient IP address and whether write authorization is enabled.
Serial Numbers for Connectrix
Modem phone numbers for each Symmetrix.
Symmetrix Microcode level
Serial Numbers for Symmetrix
Version 5.5
Page 17 of 197
Lab Guide
Lab Guide
IP Configuration
Physical Location
Connectrix SNMP Configuration
IP Address:
Default Gateway:
Details
Version 5.5
Location
SNMP Server:
SNMP Server IP:
Community String:
Password:
Subnet Mask:
Device Name
Manufacturer
Model Number
Firmware
Mgmt Software version
Serial Number
Cabinet Serial No.
Number of
Blades/Modules
Number of Total Ports
Dial Home Number
Domain
Mode
Connectrix Hardware Information

Table
Page 18 of 197
Site ID XXXXXXX
Not Configured
Not Configured
Not Configured
Not Configured
Switch 1
Site ID XXXXXXX
Not Configured
Not Configured
Not Configured
Not Configured
Switch 2
Site ID XXXXXXX
Not Configured
Not Configured
Not Configured
Not Configured
Switch 3
The following document is from the Hardware Info Worksheet within the EMC Planning and Design Guide workbook. The
full EMC Planning and Design Guide Workbook is available at: http://powerlink.emc.com
Site Hardware Information Worksheet
Physical Location
Director Cards
Multiprotocol Directors
EA/RA Director Cards
SA Director Cards
FA/RA Director Cards
Storage
Cache
General
Symmetrix Array Configuration

Table
Version 5.5
Location
Model Number
Serial Number
Device Name
Enginuity Version
Dial Home Number
Total Existing
Configuration
# Drives 36GB
# Drives 73GB
# Drives 146GB
# Drives 181GB
Vacant Drive Bays
Total Raw Disk (GB)
Used Ports
Free Ports
Used Ports
Free Ports
Used Ports
Free Ports
Used Ports
Free Ports
Total DA Cards
Free Slots
Page 19 of 197
Site ID XXXXXXX
8530
8530
Site ID XXXXXXX
Array 2
Array 1
Site ID XXXXXXX
Array 3
Lab Guide
(Continued)
SP B Cache
SP A Cache
CLARiiON Cache
General
CLARiiON Array Configuration

Table
Version 5.5
Model Number /
FLARE
Serial Number
SP A Name
SP A IP Address
SP A Subnet Mask
SP A Default Gateway
SP B Name
SP B IP Address
SP B Subnet Mask
SP B Default Gateway
Enforce Fair Access
ClarAlert Tel. Number
Page Size
Low Watermark
High Watermark
Read Cache
Write Cache
Total Cache
Read Cache
Write Cache
Total Cache
Page 20 of 197
Array 1
Array 2
Array 3
Lab Guide
Physical Location
Version 5.5
Location
Storage Data
# of DPEs
# of DAEs
# drives 181GB
# drives 146GB
# drives 73GB
# drives 36GB
Vacant Drive Bays
CLARiiON Array Configuration

Table (Continued)
Page 21 of 197
Site ID XXXXXXX
Array 1
Site ID XXXXXXX
Array 2
Site ID XXXXXXX
Array 3
Lab Guide
Lab Guide
Vendor
Model
OS
Patch
Level
Application
OS Information
Host
Name
Host Identification
Number
of HBA &
Type
Version 5.5
Cluster
HBA
Driver
Page 22 of 197
HBA F/W
HBA Information
Host SAN Summary Matrix
Host SAN Matrix: Data Gathering Current Environment
Array
Boot
Total
Required
Storage
MultiPath
SYMM
CLI
Other Configuration Information
The following document is from the Hosts Worksheet within the EMC Planning and Design Guide workbook. The full
EMC Planning and Design Guide Workbook is available at: http://powerlink.emc.com
Host Planning Worksheet Qualification Stage
Vendor
Model
OS
Patch
Level
Application
OS Information
Cluster
Host
Name
Host Identification
Version 5.5
Number
of HBA &
Type
HBA
Driver
Array
Boot
Page 23 of 197
HBA F/W
HBA Information
Host SAN Summary Matrix
Host SAN Matrix: Target Environment Code Upgrade Recommendations
Total
Required
Storage
Multipath
SYMM
CLI
Other Configuration Information
Lab Guide
Lab Guide
Lab Exercise 2: SAN/Switch Configuration

Purpose:
The goal of this lab is to configure all SAN switch and directors for
the local environment. The following will be expected:
A. Latest possible firmware installed on all switches and
directors
B. Set all ports to auto-detect/auto-negotiate speed
C. Set all ports for generic fabric use
D. Create aliases for all array host port (FAs)
E. Set domain IDs on each director
Using the instructions in this lab, configure the switches to support
a mixed host SAN environment.
Objectives:
References:
This lab is designed to be completed in the classroom

A. Verify switch firmware
B. Change domain ID to make unique in entire environment
C. Create VSANs for unique storage connectivity
environment
D. Configure ports on switches and directors to accept
negotiable logins and generic fabric connections
E. Connect host cables to directors/switches (arrays should
already be connected and logged in
Version 5.5
Page 24 of 197
Lab Guide
Lab Exercise 2
Part 1: M-Series Switch and Director Configuration Procedures
(Connectrix Manager 9)
Using Connectrix Manager, complete the following tasks to configure the switch:
*All steps require that the administrator be logged into the Connectrix Manager Console
Review firmware currently installed and running on the switch/director:
Step Action
1
Login to the switch/director
On the Physical Map, right-click a switch icon and select Properties from the
menu.
Version 5.5
Page 25 of 197
Lab Guide
Check the currently running version of code.
Set / Check that all ports are set to auto-negotiate/auto-detect link speed
Step Action
1
On the Physical Map, right-click a switch icon and select Element Manager
option
Version 5.5
Page 26 of 197
Lab Guide
From the top most menu bar, select the Configure menu item and select Port.
Check negotiate speed and set ports to either G-port or F-port on the Configure
Ports Window
Version 5.5
Page 27 of 197
Lab Guide
Once changes have been made to a port, click Activate. When the warning
window opens, click OK to accept changes
Version 5.5
Page 28 of 197
Lab Guide
Changing Switch/Director Domain IDs

Step Action
1
On the Physical Map, right-click a product icon and select Element Manager
option
Select from the main top menu, Maintenance then select Set Online State
Version 5.5
Page 29 of 197
Lab Guide
Set the switch to Offline state
Select the Configure menu from the top menu bar, then select Operating
Parameters
Version 5.5
Page 30 of 197
Lab Guide
Select the Domain tab and change the Preferred Domain ID to a decided upon
value.
Click OK when complete
Set the switch online state to Online
Close the Maintenance window
Version 5.5
Page 31 of 197
Lab Guide
Creating WWN Aliases / Nicknames

Step Action
1
From the main window in Connectrix Manager, highlight a Switch.
2
Select the Configure menu from the top menu bar and select Nicknames
Version 5.5
Page 32 of 197
Lab Guide
Find and select the WWN of the component for which the nickname will be created
Type in the nickname in the format of:

Array###_director### e.g. dmx662_15cB
When finished adding nicknames, click OK
Version 5.5
Page 33 of 197
Lab Guide
Lab Exercise 2
Part 2: B-Series Switch Configuration Procedures
In this section configure the B-series switch/director similarly to the M-series environment.
Each of the following configuration steps will be shown via the Brocade WebTools Switch
Explorer web based interface, followed by the CLI procedure. The base requirement for
connecting to the Brocade environment is a host with a supported browser and the latest
required JVM (Java Virtual Machine) installed.
Step Action
1
Review firmware currently installed and running on the switch/director:
From the main GUI window, look for Fabric OS version directly below the hardware
display, in the Switch Information frame.
Main GUI Configuration Window
CLI command: firmwareshow

2
Set / Check that all ports are set to auto-negotiate/auto-detect link speed
From the main GUI window select any port in the hardware display. This will bring
up the Port Administration window which will have several configuration options:
Port Administration Services Window / Port Configuration Wizard
Version 5.5
Page 34 of 197
Lab Guide
To configure port settings:

A. Having selected the port to configure, select Edit Configuration. This will
bring up the Port Configuration Wizard.
B. Leave the port type as it is unless instructed otherwise. Hit next and select
the speed. Confirm the changes by clicking Finish.
CLI command:
portCfgShow - Displays configuration for all ports.
portCfgSpeed <port #> <speed #> - Set the port speed in Gbps. For auto
negotiate set speed to 0.
Changing Switch/Director Domain IDs

From the main GUI window, select the Admin
button from the button row
directly below the hardware display. This will open the Switch Admin window.
From this window it is possible to both put the switch offline and change the domain
ID.
A. Disable the switch (take offline in the fabric):
If the switch is currently online, it will not be possible to change the Domain
ID. First, the switch will need to be taken offline.
Domain ID and Switch Status Shown from Main GUI Window
Version 5.5
Page 35 of 197
Lab Guide
From the within the Switch Status area, select the Disable radio button. Next,
click Apply. A prompt will be displayed confirming the change, select OK. Once
the switch is off-line itll be possible to change the Domain ID.
Domain ID Accessible After Switch Off-Line
B. Change the value in the Domain ID box to the pre-determined agreed upon
value. Once the value has been changed, select Apply and follow the
prompt to activate the changes. Once all off-line changes have been made,
bring the switch back on-line by selecting Enable from the Switch Status
area.
CLI command:
switchDisable - Disables the switch.
configure Configure switch-parameters (make sure to disable switch)
Fabric parameters (yes, y, no, n): [no] y Configure Fabric parameters
Domain: (1..239) [1] <#> - Type desired domain id number.
switchEnable Enables the switch.
Creating WWN Aliases / Nicknames

button at the bottom left corner of Web Tools.
Select Zone Administration
From within the Zone Administration window, select the tab for Alias. Click the
New Alias button to create and name a new alias. Once the alias has been
named, it is then possible to select WWNs from the Member Selection List to
apply to the named alias. Save changes once complete.
CLI command:
alicreate <name>, <member>/alidelete <name> - Create or Delete Zone Alias.
aliadd <name>, <member>/aliremove <name>, <member> - Add or Remove Members
to an existing Alias.
Version 5.5
Page 36 of 197
Lab Guide
Lab Exercise 2
Part 3: MDS-Series Switch Configuration Procedures
The following procedures are a high-level of how to use the MDS CLI to configure some
switch, port, and zone settings in an MDS environment. As on the other switch platforms, it
is a good idea to take configuration backups and notes before proceeding with any changes
to an existing environment.
The first step in working in the MDS environment should include some investigation of the
current switch configuration and connectivity.
Show the current software
Step Action
1
Check the version and determine via the EMC Support Matrix whether the switch
code needs to be upgraded.
show version
Show version will output all code versions running on all modules. The code
implementation is interested in is both the kickstart and system code.
Version 5.5
Page 37 of 197
Lab Guide
Next, look at any currently running-config on the switch.

show running-config
It is good practice to save the output of running-configuration before making any

changes. This allows to rebuild the configuration from a pre-implementation state if
there is a need to back-out any changes / modifications to the environment.
3
Investigate and view what entries are currently in the fibre channel name server
database.
#Show Fibre Channel Name Server Database
Show fcns database
Version 5.5
Page 38 of 197
Lab Guide
After verifying current configuration and status of the switch, begin configuring it for
connectivity in a fabric environment. First, well open the ports and configure the ports which
have hosts attached for the proper fibre channel SAN connectivity:
Step Action
1
Enter configuration mode, select interfaces to change, open ports, change xmit
speed, etc.
#Enter Terminal Configuration Mode
config t
#Select Interface
interface fc1/1
#Set to not shutdown
no shut
#End Configuration
end
Next, review the changes and make sure that the desired effect has been
committed. Run the command:
#review changes
show port internal info interface fc1/1
Version 5.5
Page 39 of 197
Lab Guide
Next, open all ports for fibre login:

#Enter configuration mode
config t
#Choose all switch ports
interface fc1/1-16
#Set no shut option
no shut
#End configuration
end
Copy the running-config to start-up. This ensures that your changes will persist
between reboots/reloads of the switch environment.
#Copy the current configuration to the configuration on startup
copy running-config startup-config
Issue the show running-config command to show the current configuration of

ports:
#show the current configuration
show running-config
Again, look at the Name Server database:

#look at nameserver database
show fcns database
Version 5.5
Page 40 of 197
Lab Guide
Look at the FLOGI database

#look at the Fabric Login Database
show flogi database
Configure the speed of ports in the MDS SAN environment.

#enter configuration mode
config t
#choose the port
interface fc1/1
#set speed to auto
switchport speed auto
#end configuration
end
Version 5.5
Page 41 of 197
Lab Guide
Create a VSAN in an MDS SAN Environment

At the time of VSAN creation, it is possible to assign domain IDs and ports to
the VSAN. This is the premise on which zoning will be implemented in the MDS
environment.
Create our VSAN. Use something similar to the VSAN list below for your
environment.
VSAN 10 mgmt vsan
Follow these steps to perform the configuration:
#enter configuration mode
config t
#enter vsan configuration mode
vsan database
#create a vsan
vsan <domain id> name <vsan name>
#add ports to the vsan
vsan <domain id> interface <fc#/#>
#end configuration
end
10
Save the configuration changes to the environment by running:

#save to startup config
Version 5.5
Page 42 of 197
Lab Guide
Lab Exercise 3: Attaching Hosts and Configuring Host

Bus Adapters (HBAs), Part 1
Purpose:
Objectives:
References:
The goal of this lab is to:

A. Connect HBAs to SAN directors / switches
B. Install required HBA firmware and device drivers
C. Configure HBA settings for use in an EMC environment
the data center.
A. Apply any required patches / maintenance releases for the
Operating Systems to be qualified/approved for support
B. Connect host HBAs to each switch
C. Document connections using worksheets from lab 1
D. Install qualified/approved HBA driver and firmware
Version 5.5
Page 43 of 197
Lab Guide
Lab Exercise 3
Part 1: Array Port Allocation
Host OS
Type
HP-UX
Solaris
Windows
AIX
Array Port 1
Port 2
2cB
15cB
5006048ACCC8BDA1
5006048ACCC8BDAE
15cA
2cA
5006048accc8bd8e
5006048accc8bd81
15cA
2cA
5006048accc8bd8e
5006048accc8bd81
15cA
2cA
5006048accc8bd8e
5006048accc8bd81
Port Port
3
4
Bit
Settings
Volsetaddr
DMX
662
662
662
662
Input your Array Host Port Allocations Below:
A. For specific director configuration settings, refer to the EMC Support Matrix, available either on
http://powerlink.emc.com or http://www.emc.com/interoperability/matrices/EMCSupportMatrix.zip View array details (E.G. Symmetrix DMX Series), Fibre Bit Settings
Version 5.5
Page 44 of 197
Lab Guide
Lab Exercise 3
Part 2: Install Required Patches
It may be necessary to install vendor updates to the system in order to have it operate
properly in a SAN attached environment. Additionally, the latest patch cluster or
maintenance levels may be required in order for the system to be fully supported in an
EMC SAN environment. Using the data gathered in Lab One, and the qualification that
was performed previously, determine if the system needs to be upgraded. If the system is
deemed to be at an appropriate patch level, skip this step and proceed to installing and
configuring the HBAs.
HP-UX:
Install latest PHKL bundles for both HBAs and the Operating Environment. HP Patches are
available from:
http://support.hp.com
To install PHKL bundles:
swinst l /location/to/depot
Solaris:
Install latest approved/supported patch cluster. Patch clusters are publicly available at:
http://sunsolve.sun.com
To install Sun patch clusters:
./install_cluster nosave
AIX:
Install latest supported maintenance level for the version of AIX being deployed in the
environment. AIX maintenance kits are available from:
http://www.ibm.com/support/
To install AIX maintenance kits:
installp
Windows:
Install the latest Service Pack. MS Service Packs are available from:
http://www.microsoft.com
To install:
Run the installer from the Microsoft web.
Version 5.5
Page 45 of 197
Lab Guide
Lab Exercise 3
Part 3: Install HBA Driver and Firmware
Solaris Emulex LP-9802 / LP-10000
Following these steps, the HBA will be verified, software installed, and configured:
Verify that the HBA is installed in the system
Install the driver
Find the WWN for the HBAs
Check for HBA to switch login
Configure the HBA driver file
For Solaris 10 follow these steps, instructions for version below Solaris 10 can be found in
the appendix ?
Step Action
1
Search for the HBAs installed on the system
prtdiag |grep i lpfc
Version 5.5
Page 46 of 197
Lab Guide
Acquire the latest driver, firmware, and boot code for the Solaris Emulex HBA
A.
B.
C.
D.
E.
F.
G.
Open the Emulex website in a browser: http://www.emulex.com

Click on the support link at the top menu
Select EMC from the suppliers list
Click on the appropriate HBA for the server (shown above)
Download the Firmware from this page.
Select Solaris on the right hand menu.
Click on the appropriate OS version under SAN Foundation Suite drivers,
documentation, utilities and migration information for the SFS FCA
Drivers
H. Download the Driver, Readme, and Manual
I. FTP the driver to a safe location (var/tmp/emulex) in the Solaris host
Version 5.5
Page 47 of 197
Lab Guide
Uncompress Emulex code and install driver

Change to the /var/tmp/emulex directory (to which you copied the Driver and
Applications kit) and untar the kit:
cd /emulex
tar xvf emlxu_kit-xxx.tar
A. When the untar is complete you will find these components:
emlxu_install Emulex Fibre Channel Solaris driver and Application installation

file
emlxu_uninstall Removes driver
EMLX_emlxu Directory with the installation files
B. Install the package:

./emlxu_install
<Removing old EMLXemlxu package>
pkgrm: ERROR: no package associated with <EMLXemlxu>
<Expanding emlxu_kit-1.00n-sparc.tar>
<Adding new package>
Processing package instance <EMLXemlxu> from </tmp/emulex>
Emulex LightPulse Fibre Channel Adapter Utilities (usr)(sparc)
1.00n,REV=2006.04.19.16.36
COPYRIGHT 2004-2006 Emulex. All rights reserved.
Using </> as the package base directory.
## Processing package information.
Version 5.5
Page 48 of 197
##
##
##
##
Lab Guide
Processing system information.

Verifying package dependencies.
Verifying disk space requirements.
Checking for conflicts with packages already installed.
The following files are already installed on the system and are
being
used by another package:
/opt <attribute change only>
Do you want to install these conflicting files [y,n,?,q] y
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <EMLXemlxu> [y,n,?]
y
Installing Emulex LightPulse Fibre Channel Adapter Utilities (usr)
as <EMLXemlxu>
## Installing part 1 of 1.
[ verifying class <none> ]
Installation of <EMLXemlxu> was successful.
<Cleaning directory>
<emlxu_install complete>
<Execute "emlxu_remove" when ready to uninstall>
DO NOT REBOOT YET!
Edit any necessary files as described under Incorporating EMC Fibre

Channel on page 2-16 of the EMC Fibre Channel with Emulex Host
Bus Adapters in the Solaris Environment document.
Reboot the host with the -r (reconfigure) option:

reboot r
C. Upgrade firmware:
If the firmware is compressed, extract it
Copy the firmware file to the appropriate directory
/opt/EMLXemlxu/downloads
cp XXXXXX.all /opt/EMLXemlxu/downloads
Start the EMLXADM Device Management Utility

/opt/EMLXemlxu/bin/emlxadm
Select the adapter number to update.
Version 5.5
Page 49 of 197
Lab Guide
Type the download firmware command and path to the firmware.

download_fw ../downloads/tdxxxxx.all
When prompted to confirm download, type y
Once the new firmware is installed change HBAs by typing:

hba
Repeat the last 4 steps for each installed HBA
D. Upgrade Boot Code

Copy the appropriate file for the HBA to the opt/EMLXemlxu/downloads
directory.
cp TXXXXXX.PRG /opt/EMLXemlxu/downloads/
Start the EMLXADM Device Management Utility

/opt/EMLXemlxu/bin/emlxadm
Version 5.5
Page 50 of 197
Lab Guide
Type the download fcode command and path to the firmware.

Note: Dont get confused with the download boot command, you are
required to upgrade the fcode
download_fcode ../downloads/TXXXXXX.PRG
When prompted to confirm download, make sure the current version is

LOWER than the version you are installing, if it is, go ahead with the
installation by typing Y If Its not, abort the installation
Once the new firmware is installed change HBAs by typing:

hba
Repeat the last 4 steps for each installed HBA
E. Once upgrades are complete, reboot the host to have all changes take effect.
To reboot:
/usr/sbin/reboot -- -rv
Once the host has rebooted, check for the availability of the Emulex HBA the WWN
should be found in /var/adm/messages:
cat /var/adm/messages |grep WWN
Version 5.5
Page 51 of 197
Lab Guide
IBM AIX 5.X LX FC 5716/6227/6228/6239

Install the driver
Configure the HBA driver
Step Action
1
Verify that the HBA is installed and accepted by the AIX system. Run the following
command, and grep for fcs and fc as the fibre adapter names:
A. Issue the lscfg command to get a listing of all configured components within
the system:
lscfg
B. View the details for each fcs device configured on the system, note WWNs.
lscfg v l <fcs#>
Version 5.5
Page 52 of 197
Lab Guide
C. Access http://www.ibm.com/support Use the Search option to find the HBA

model, select the Download option.
Download the xxxsvcptfs.tar from the site and copy it (by ftp) to the host.
Untar the file and remember the directory where files were extracted. In our case
(/tmp/hba_driver/xxxsvscrptfs.tar)
tar vvf /tmp/hba_driver/xxxsvscrptfs.tar
Install HBA Driver:

A. Use the Software Installation and Maintenance feature on AIX System
Management Interface Tool (SMIT) to precede the package installation on the
host.
smit
B. Select Software Installation and Maintenance Menu
Version 5.5
Page 53 of 197
Lab Guide
C. Select Install and Update Software Menu
D. Select Install and Update from ALL Available Software
E. Set the installation method

a. Input the absolute path to the folder where you extracted the files in the
Input Devices section.
* INPUT device / directory for software
Version 5.5
/tmp/hba_driver
Page 54 of 197
Lab Guide
b. In the Software to Install section press F4 to chose from a list of

software.
c. Next to every software file press F7 to select, when youre done
choosing hit the Enter key
d. Leave everything else as it is and hit the Enter key to execute. When
prompted for confirmation hit the Enter key again.
Version 5.5
Page 55 of 197
Lab Guide
e. Once the installation completes a report is shown with the status. Make
sure everything installed correctly and press F10 to exit.
Version 5.5
Page 56 of 197
Lab Guide
HP 9000 - HP-UX A5158A/A6239A

Install the driver
Configure the HBA driver
Step Action
1
Verify the HBA is installed and accepted by the system
To determine whether the HBA is installed and accepted in the HP-UX system, run
the following commands. The command set will differ depending on what type of HBA
is actually installed, these commands will work with HPQ A5158A HBAs. Lastly, after
issuing the command fcmsutil, the WWN of HBAs will be listed, write it down.
A. Issue the lsdev command with the fc class argument
lsdev -C fc
B. View driver device files in the device tree

ls -l /dev//td*
C. If the driver device files exist, view each driver instance using the fcmsutil
binary. fcmsutil is located in /opt/fcms/bin
/opt/fcms/bin/fcmsutil /dev/td0
Version 5.5
Page 57 of 197
Lab Guide
Download of Driver, Firmware and Manuals

A.
B.
C.
D.
E.
F.
Log into the HP website at http://www.hp.com

Click on the Software and Driver Downloads.
In the search box type: PCI 2GB Fibre Channel Adapter
Click on HP PCI 2GB Fibre Channel Adapter
Select your current operating system.
Download the Driver and Firmware.
G. FTP the driver to your host and save it in a location you will remember, in this
case /tmp/hba_driver
3
Download the FCMS dependency patch, PHKL_23939.

A. Open HP Resource Center website on a browser: http://itrc.hp.com
B. In the Maintenance and Support for HP Products section select Patch
Database. It might be required for you to sign up.
C. Search for PHKL_23939 in the Search Box.
D. Download and FTP the patch (and required dependencies) to the host in a
location you will remember, in this case /tmp/hba_driver/patches/
Version 5.5
Page 58 of 197
Lab Guide
Install Patches
A. Untar the patch file
tar xvf /tmp/hba_driver/patches/ hpux__11.00_XXXXXX.tar
B. Once the tar is finished running, there should be a script called

create_depot_hp-ux_11 (for A5158A cards installed on machines running HPUX 11.00). Run this script to setup the depot location within the /tmp/bundle
location.
/tmp/hba_driver/patches/create_depot_hp-ux_11
C. Verify that the file has been downloaded correctly using the swlist command.
NOTE: You must specify the complete path of the source depot for the swlist and
swinstall commands.
swlist -d @ /tmp/bundle/depot >
The output should be the following
# Initializing...
# Contacting target "hpdev-64"...
#
# Target:
hpdev-64:/tmp/bundle/depot
#
#
# Bundle(s):
#
BUNDLE
B.11.00
Patch Bundle
Version 5.5
Page 59 of 197
Lab Guide
(The patch for the A5158A

B.11.00.10
PCI Tachyon TL/TS
Fibre Channel card will be included in this bundle)
D. To install the product on a stand-alone system, run the following command:

swinstall -s /tmp/hba_driver/patches/depot
E. Using the ALT key and arrow navigate to the ACTIONS menu, hit enter and
select INSTALL
F. Wait until the Install Analysis is complete and then select OK, accept any
confirmation and wait for install completion.
Version 5.5
Page 60 of 197
Lab Guide
G. When the installation is complete press Done and when prompted to Reboot
accept.
Install Driver
A. To install the driver on a stand-alone system, run the following command:
swinstall -s /tmp/hba_driver/ FibrChanl-00_XXXXXX.depot
B. Using the ALT key and arrow navigate to the ACTIONS menu, hit enter and
select INSTALL
C. Wait until the Install Analysis is complete and then select OK, accept any
confirmation and wait for install completion
D. When the installation is complete press Done and when prompted to Reboot
accept.
Configure the Driver

A. There are no configuration steps for the driver. However, after loading a driver
or patching the base install with a PHKL bundle, the host should be rebooted to
ensure stability and that the latest code has been loaded.
B. After reboot, once again list the fibre devices using the fcmsutil binary and
check to make sure that the devices are still online and available
Version 5.5
Page 61 of 197
Lab Guide
Windows 2000/2003 with Emulex LP-10000

Install the driver
Step Action
1
Acquire the latest driver, firmware, and boot code for the Windows Emulex HBA.
Go to: Emulex Web site. Locate the appropriate code for the card to be installed
and configured. Download of Driver, Firmware and Manuals:
Download of Driver, Firmware and Manuals:
A. Access http://www.emulex.com/emc/support/index.jsp
B. Select your HBA on the Symmetrix and CLARiiON table
C. Choose the Firmware and download it. Download the firmware version
zipped file to the Windows host and unzip it. Create an /emulex directory and
copy the executable file
Version 5.5
Page 62 of 197
Lab Guide
D. Choose the OS type to download the driver from the Resources section on
the right.
E. Download the driver on the FC Port Driver column. Copy the zip file to the
/emulex directory created previously.
Install HBA driver

A. Boot the host (if necessary) with Windows 2000 or Windows 2003.
B. From the Windows taskbar, click Start, Programs, Administrative Tools,
Computer Management.
Version 5.5
Page 63 of 197
Lab Guide
F. In the left pane of the Computer Management window, click the Device
Manager icon.
G. This step depends on the HBA model and Windows version. If Windows
automatically detects the HBA, you will follow an upgrade procedure,
otherwise you will follow an install procedure:
LP9802DC-E / LP10000-E / LP10000DC-E
Double-click the Other Devices icon in the right pane; then

double-click the instance of Fibre Channel
LP9802-E
Double-click the Other Devices icon in the right pane; then

double-click the instance of Fibre Channel
Double-click the SCSI and RAID Controllers icon in the right

pane; then double-click the instance of Emulex LP9000 Fibre
Channel Host Adapter. Follow the instructions under Updating the
HBA Driver in a Windows 2000 or Windows 2003 Host on page 219.
H. In the Properties window that appears, click the Driver tab.

I. Click Update Driver.
J. Click Next to start the driver wizard.
K. Select Display a list of the known drivers for this device so that I can
Version 5.5
Page 64 of 197
Lab Guide
choose a specific driver, then clicks Next.

L. Select SCSI and RAID Controllers, and then click Next.
M. Click Have Disk.
N. Enter a path to the diskette containing the driver (A:\, for example), or use
the browse function to locate the driver; then click OK.
O. Select the appropriate driver
Windows 2000/Windows 2003 SCSIPort (Fabric or Loop):

Emulex LightPulse <HBA model> - Multi-protocol Port
Driver
Note: If you select the wrong <HBA model> from the list, you will
receive an Incompatible Hardware warming message. Select No
to cancel the update and return to the selection windows, and
then select the correct model. When the correct model is
selected, the warning message will not appear.
P. In the next window, click Next.
Q. Click YES to continue the installation.
R. Click Finish to complete the installation.
S. When the system requests that you reboot the system, select NO; then click
Close.
T. When the system again requests that you reboot the system, select NO;
Version 5.5
Page 65 of 197
Lab Guide
then click Close.

U. If there are more Emulex HBAs installed, repeat steps 4 through 17 for each
remaining HBA.
V. When all adapters have had their drivers updated, select Yes to the reboot
prompt. If you are not promoted to reboot, reboot anyway.
W. After the reboot has completed, install the EMLXApps Application kit that
was included with the driver. To do this, expand the setupapps.exe
contained in the EMLXApps .zip file, and run the setupapps.exe program.
This install updates the Windows installer to v2.0 and then installs three
Emulex applications; the Port driver configuration tool (ELXCFG.EXE), the
mini-port driver configuration tool (LPUTILNT.EXE), and the HBAnywhere
Application. Follow the instructions during the Application Kit installation and
complete the installation.
X. For Windows 2000 only, run the exlcfg.exe tool and follow these procedures:
Updating the Shortcut on page 2-31 of the EMC Fibre
Channel with Emulex Host Bus Adapters in the Windows
Environment document.
Changing the Configuration on page 2-33 of the EMC Fibre
Channel with Emulex Host Bus Adapters in the Windows
Environment document.
Notes:
LP9802 requires minimum driver revision 2.13a4 for SCSIPort or 1.00A15 for STORPort
drivers.
LP10000-E, LP10000DC-E and LP9802DC-E require minimum driver revision 2.21a0 for
SCSIPort or 1.00A15 for STORPort drivers.
Install Firmware
b) Change to the /emulex directory (to which you copied the executable
file) and run the firmware version executable.
c) Follow the instructions to install the firmware.
Version 5.5
Page 66 of 197
Lab Guide
Linux with Emulex

Find the Kernel version
Install the driver
Step Action
1
Verify the HBA is installed and accepted by the system.
To determine whether the HBA is installed and accepted in the Linux system, run
the following commands.
A. Issue the dmesg command
dmesg |grep scsi
Acquire the latest driver for the Linux Emulex HBA. Goto: Emulex Web site. Locate
the appropriate code for the card to be installed and configured.
A. Access http://www.emulex.com/ts/index.jsp
B. From the Emulex home page, select the EMC link
Version 5.5
Page 67 of 197
Lab Guide
C. Select your HBA on the list

D. Under Drivers for (your OS), click on the driver version in the Resource
section at the right of the page.
E. Download the file to the Linux host (create a /emulex directory) and
uncompress it using tar xzvf command (the initial uncompression will
create a new directory)
3
Install HBA Driver:

A. Execute the script (./lpfc_install)
B. Reboot the host so that the lpfc driver can be loaded through the newly
created ramdisk
Version 5.5
Page 68 of 197
Lab Guide
Lab Exercise 4: Configuring Zoning

Purpose:

Create a zone for each host HBA for the fabric it is attached to
Objectives:
References:

the data center.
A. Using either M-Series, B-Series or MDS-Series
switch management tools, create zones for hosts in
the environment
B. Reboot hosts to have all configuration settings,
patches, and zoning to take effect
Version 5.5
Page 69 of 197
Lab Guide
Lab Exercise 4
Part 1: Connectrix Manager Zoning for M-Series
Directors/Switches (Connectrix Manger 9.x)
Following these procedures, implement zones for all hosts in the environment using MSeries Connectrix Manager. Once zones have been created, load the zones to the
appropriate ZoneSet.
Step Action
1
Login to the Connectrix Manager application
2
Right click on the switch and select Zoning
Version 5.5
Page 70 of 197
Lab Guide
On the Zoning Library click on New Zone button
At the Product/Ports column expand the switch to find the WWN logged in
Add the WWNs you wish to be members of your zone to the Zones column
Version 5.5
Page 71 of 197
Lab Guide
Once selecting Zones select File then New from the top menu bar within the
Zoning Library window
Create more zones as desired
Move the new zones to the desired Zone Set in Zone Sets column
Click on Activate button
Version 5.5
Page 72 of 197
10
Verify the changes and click OK
11
Select Yes to activate and wait the activation
Lab Guide
Version 5.5
Page 73 of 197
Lab Guide
Lab Exercise 4
Part 2: M-Series Connectrix Manager Basic Zoning
Creating a Zone
Step Action
1
Open the browser and access the switch M-series IP-Address (refer to lab
configuration book)
User = Administrator
Password = *********
2
Select your switch on the main screen and click on Configure, Zoning.
Insert a zones name. For example, to create a zone for the host hp3-68, hba0 to
Storage device DMX800 Symm id 187900662, FA 15c Port b use a zone name that
reminds this setup. For instance, create the name hp3-68_hba0_dmx662_15cb
Choose the members WWN (for the hp3-68 the WWN is 50:06:0B:00:00:07:7C:40
) that will be added and select to the zone. (make this step for the other member,
in this case, the Symm DMX800, port 15cB, WWN 50:06:04:8A:CC:C8:BD:AE).
Select your zone to the Zone Set and select Activate.
Version 5.5
Page 74 of 197
Lab Guide
Lab Exercise 4
Part 3: B-Series Web Tools Zoning
In some datacenter / storage environments, B-Series switches and directors are used as
an alternative to M-series products. Detailed here are the steps to create zones, aliases,
and activate new configurations to the switches.
Step Action
1
Create Zones for newly created Configuration and move into Configuration
Open the Zone Administration
window from the main GUI window.
A. Click on the Zone tab on the upper left-hand tab bar.
B. Then, click the Create button to make a new zone.
C. Once the zone has been named, click OK to proceed.

D. From the left-hand side of the window, there is a sub-window called
Member Selection List. Within this sub-window, find the WWNs which will
be added to the newly created zone. Once the desired WWN has been
Version 5.5
Page 75 of 197
Lab Guide
located, click the Add Member > button in the middle of the screen. This
will add the WWNs to the defined zone in the Name box directly above the
Member Selection List.
E. If the WWN is not found, or currently off-line, select to manually add the
WWN by selecting Edit from the top most menu bar then selecting Add
WWN. By performing an Add WWN the WWN will automatically be added
to the currently open zone.
F. Once all required Zones are created, select Zoning Actions from the top
most menu bar then select Save Config Only. This will save the zone
information but not activate any changes to the switch.
Version 5.5
Page 76 of 197
Lab Guide
Move zones into Configurations (ZoneSets)

Once both configurations and zones have been configured, it is appropriate to
move zones into a Configuration, thus defining what is allowed to connect via the
particular switch which is being configured.
Once changes have been made to the configuration (zones added or removed),
once again select the Zoning Actions menu from the top most menu, and then
select Save Config Only.
Version 5.5
Page 77 of 197
Lab Guide
Activate newly created Configuration for each director/fabric

From within Zone Administration, select Zoning Actions from the top-most
menu bar, then select Enable Config. Then, select the config to enable on the
switch/director. Click OK to activate/enable the changes.
Version 5.5
Page 78 of 197
Lab Guide
Lab Exercise 4
Part 4: MDS Switch CLI Zoning Configuration
Next, well configure zoning and all associated configurations for zoning in our MDS
environment. The first thing to continue configuring from the previous lab is the preferred
domain ID for each VSAN. This may not be a tactical step for all environments. It is useful to
give VSANs unique domain IDs since then they can be setup for inter-vsan-routing.
Step Action
1
Preferred domain Ids for VSAN 5, 10:
Run the fcdomain command for each vsan in the environment.
Restart the VSANs if required
config t
fcdomain domain <domain id> preferred vsan <vsan #>
fcdomain restart vsan <vsan #>
Configuring Zoning:
Look for the ports you want to join into a zone together. Eg. AIX WWN to Symm
show fcns database
Version 5.5
Page 79 of 197
Lab Guide
As shown in the above screen, VSAN 20 includes the unix ports, fc1/4, fc1/9, and
fc1/14. This was setup when in the previous lab the ports were included as part of
the VSAN creation.
A. First, configure aliases for the ports, if desired
config t
fcalias name <alias name> vsan <vsan #>
Add the fcalias name, and then add a pwwn to assign to the name. From
this point, zoning can be completed either by fcalias, fcid, pwwn, etc.
member pwwn <WWN>
exit
B. Create your zoning; first create your zoneset, assign it to a particular vsan
Version 5.5
Page 80 of 197
Lab Guide
zoneset name <zoneset name> vsan <vsan #>
From within the zoneset submenu, create your zone. This is called creating
the zone inline
zone name <descriptive_zone_name>
Add the members to the zone, in this example, we add by fcalias, since
fcaliases have been configured. Zones can also be constructed by domain
location, fcid, fwwn, pwwn, interface (ports), ip-address, symbolicnodename.
member fcalias <dmx fc alias>
member fcalias <host fc alias>
end the configuration by:

end
exit
C. Activate the zoneset

Lastly, return to config mode to activate the zoneset. Zoneset activation
happens from with the zoneset menu and zoneSets are assigned to preconfigured VSANs.
zoneset activate name UNIX_VSAN20_zoneSet vsan 20
D. Backup modifications
Before finishing, backup the switch configuration to two locations. The first
location should be local switch startup memory. This allows the
configuration to persist between reboots. Secondly, if possible save the
configuration to another host in the environment. This can be done using
Version 5.5
Page 81 of 197
Lab Guide
one of the following protocols: scp; sftp; ftp; tftp;

Backup the config to another filename on the switch, and then copy the
backup to another location:
copy running-config sw03_2007_03_15.cfg
Move the backup to another host/location:

copy sw03_2007_03_15.cfg
ftp://user@10.127.56.77/export/home/user/ sw03_2007_03_15.cfg
Finally, capture the output of running-config and save the output on another
host offline. In worst case scenarios, configurations can be re-written from
output of the running-configuration
show running-config
Version 5.5
Page 82 of 197
Lab Guide
Lab Exercise 4
Part 5: Post Zoning Tasks
Once the zones have been created and added to the currently configured and running
ZoneSets, verify the host HBAs have logged into the switch and are online. In some cases,
it maybe required to reboot the server to have the HBA driver restart. Follow these
instructions to reboot different host environments
Solaris:
/usr/sbin/reboot -- -r
The above command performs a reconfiguration reboot. When passing the r option at
reboot, the Solaris kernel will be rebuilt.
HP-UX:
ioscan
insf -e
/usr/sbin/reboot (reboot only if the commands above do not work)
AIX:
emc_cfgmgr or cfgmgr
/usr/sbin/reboot (reboot only if the commands above do not work)
Linux:
modprobe r hba_module
modprobe hba_module
(reboot if the commands above do not work)
Windows:
Start Menu->Shutdown->Restart
Version 5.5
Page 83 of 197
Lab Guide
Lab Exercise 5: Array Configurations EMC Symmetrix

Purpose:
Objectives:
References:
The goal of this lab is to verify and configure an EMC Symmetrix

storage array within the environment. For each host type in the
environment, there should be two host ports (FA) for connectivity.
Using EMC Solutions Enabler, verify the configuration of the array
and make configuration changes as necessary. Be sure to enable
the correct FA bit settings for each host in the environment.
Lastly, check that there is proper redundancy in within the
environment and that the right ports are connected to the right
fabrics.

the data center.
A. Install and license EMC Solutions Enabler
B. Discover environment
C. View settings for each director
D. Modify director settings as required for each Operating
System in the SAN environment
E. View storage in the array, verify that there are appropriate
number of LUNs and other required devices in the system
F. Complete the LUN Masking worksheet this worksheet
will serve as the planning document for assigning LUNs to
the hosts in the environment
G. Map hypers (LUNs) to the appropriate FA ports
Version 5.5
Page 84 of 197
Lab Guide
Lab Exercise 5
Part 1: Preamble: The Array Environment Configuration Array
Host Port Allocations
Host OS
Type
HP-UX
Solaris
Windows
AIX
Array Port 1
Port 2
2cB
15cB
5006048ACCC8BDA1
5006048ACCC8BDAE
15cA
2cA
5006048accc8bd8e
5006048accc8bd81
15cA
2cA
5006048accc8bd8e
5006048accc8bd81
15cA
2cA
5006048accc8bd8e
5006048accc8bd81
Port Port
3
4
Bit
Settings
Volsetaddr
DMX
662
662
662
662
Input your Array Host Port Allocations Below:
Management Environment
In the event there is no access to, or no EMC ControlCenter Management system, install
Solutions Enabler on the newly SAN attached host. Solutions Enabler is available from the
following location:
http://powerlink.emc.com Resources / Tools CS Support Downloads and
Patches Downloads S - Z Solutions Enabler
Additionally, the software is available on the student resource CD in the Solutions Enabler
directory. License keys for the product are in the Solutions Enabler folder, in the file
symapi_licenses.dat
Version 5.5
Page 85 of 197
Lab Guide
Lab Exercise 5
Part 2: Installing Solutions Enabler (SE) - UNIX
Step Action
1
Acquire the software, and copy to the UNIX host:
Download it from host or as shown above, FTP it from another host.

2
Login to the UNIX host and unpack the source

cd /tmp
tar xvf HP-UX_rt_V632.tar
NOTE: In this example the file has a .tar extension, in other versions it can have
different extensions.
Run the installation script to install Solutions Enabler:
./emc_install.csh
Version 5.5
Page 86 of 197
Lab Guide
Answer the prompts with Y (yes) to create directories. Once prompted:

What would you like to do?, Answer (i) to install the product. Next, enter the
number of the software which should be installed (01). For example:
For the following prompts, answer accordingly:

Install All EMC Solutions Enabler Shared Libraries and Run Time
Environment (Y) Y
Install EMC Solutions Enabler 64-bit Shared Libraries ? [N] N
Install Single-threaded Symapi Shared Libraries ? [N]: N
Install Shared Libraries That Will ONLY Allow Monitoring Capability? [N] N
Install Symmetrix Command Line Interface (SYMCLI) ? [Y] Y
Install EMC Solutions Enabler SRM Database Run Time Components ? [N] N
Install Option to Enable JNI Interface for EMC Solutions Enabler APIs ?
[N] N
Install Option to Enable EMC Solutions Enabler Star Component? [N] N
Do you want to save /opt/emc/SYMCLI/V5.4.1? [N]: N
You will then be alerted to:
Unpacking files ... This may take a few minutes ...
Version 5.5
Page 87 of 197
Lab Guide
When the installation is finished, select X to exit the installer
Next, license the product. Enter a key for each product which will be licensed (see
the symapi_licenses.dat file on the support/resources CD):
/opt/emc/SYMCLI/V6.3.2/bin/symlmf
The product is now installed, licensed, and ready for use. Proceed to the next
section to begin configuring the storage array environment
Version 5.5
Page 88 of 197
Lab Guide
Lab Exercise 5
Part 3: Discovering and Viewing the Storage Environment
Step Action
1
Verify that Solutions Enabler is installed in the environment:
Run symcli with no arguments to see if it is in the path and installed:
symcli
Discover the storage environment

symcfg discover
If symcfg discover executes without error, run a list to see what was found:
symcfg list
What did symcfg list output? List the following:

Array / SymmID: ___________________________________________
Model: ___________________________________________________
Mcode Version: ____________________________________________
Number of Symm Devices: ___________________________________
Do these values reflect the earlier data gathering efforts?
_________________________________________________________
Version 5.5
Page 89 of 197
Lab Guide
Once Solutions Enabler is installed and licensed, and the array is configured and
verified to be online, begin viewing and configuring array ports
View the Array Port
symcfg sid <symm id> FA ALL list
Next, view settings, in detail per director

symcfg
-sid <symm id> FA <fa> v list
Version 5.5
Page 90 of 197
Lab Guide
Look at Director Bit Settings
View all storage in the environment:

Using the Solutions Enabler symdev command, view all storage within the array and
make note of what devices should be used on each host in your environment- refer
to group worksheets to see what devices should be made available to the hosts
within your setup.
symdev sid <symm id> list
Version 5.5
Page 91 of 197
Lab Guide
Document device selection for hosts in the lab environment (work with instructor
define exact requirements): refer to the masking table on the Config guide
Hostname
symdev #
LUN #
Type
Meta mbrs
Version 5.5
Notes
Page 92 of 197
Lab Guide
Lab Exercise 5
Part 4: Modifying Storage Host Port (FA ports) Configuration
Settings
When adding different host systems to the SAN attached array, it may be necessary to
make changes to the settings/configurations of the host ports. Solutions Enabler or
ControlCenter can make these configuration changes to the array. Make the changes
required, per the EMC Support Matrix, to support the different host environment types in
the lab environment. Configuration changes / modifications with Solutions Enabler are
shown in this lab.
Step Action
1
Setting up two host ports for HP-UX connectivity (Volume Set Addressing)
HP-UX requires volume_set_addressing to be set on the ports in which they will
connect to. VSA mode allows for octal addressing of devices on the HP-UX
designated FA ports.
A. build a symconfigure script file (fa_port_cfg.cmd)on a SAN attached host
(ControlCenter server) or server with Solutions Enabler
B. Verify that symconfigure can communicate and execute commands to the

local Symmetrix
symconfigure sid 662 verify
Version 5.5
Page 93 of 197
Lab Guide
C. Run symconfigure command to run symcfg script:

symconfigure <symm id> f fa_port_cfg.cmd preview
symconfigure sid <symm id> f fa_port_cfg.cmd commit
D. View FA Port configuration changes:

symcfg sid <symm id> FA <fa> v list
Mapping Devices with Solutions Enabler

To use Solutions Enabler to map devices within the array, use the following steps
as a guideline to assign additional devices (LUNs) to host ports:
A. Create a configuration mapping file contain the following commands.
Exchange device id/numbers in this file as appropriate to map specific
devices and assign specific LUN addresses
File: map_hp68_metas.cmd
map dev 002e to dir 2C:1 target=0, lun=006;
map dev 0042 to dir 2C:1 target=0, lun=007;
B. To verify / list available target ids, vbus availability, and lun numbers, issue
the following command per FA port target:
symcfg sync
symcfg -sid 662 -FA 2C -address list
C. Once the changes have completed, verify that all devices are now mapped:
symcfg discover
symdev sid 662 list |more
Version 5.5
Page 94 of 197
solaris_0_78
9
solaris_1_78
9
001-007
001-007
Volume
Numbers
Totals
solaris_1
solaris_0
Host Alias
Storage
Alias
LUN Masking Worksheet
01-007
001-007
SCSI
LUNs
(decimal
)
Version 5.5
001-007
001-007
SCSI
LUNs
(hex)
M2
M2
STD
STD
Type
Quantit
y
Page 95 of 197
Protectio
n
LUN Assignments
Lab Guide
8.43
8.43
Size
(GB)
59.01
59.01
Usable
Storage
(GB)
Assigne
d BCVs
Lab Guide
Lab Exercise 6: Array Configurations EMC CLARiiON

Purpose:
Objectives:
References:
The goal of this lab is to verify and configure an EMC CLARiiON

storage array within the environment. For each host type in the
environment, there should be two SP ports for connectivity. Using
EMC Navisphere Manager, verify the configuration of the array
and make configuration changes as necessary. Check that there
is proper redundancy in within the environment and that the right
ports are connected to the right fabrics.

the data center.
A. Install CLARiiON Procedure Generator and run setup to
build procedures for new SAN install
B. Install and license EMC Navisphere
C. Discover environment
D. View storage in the array, verify that there are appropriate
number of LUNs and other required devices in the system
E. Complete the LUN Masking worksheet this worksheet will
serve as the planning document for assigning LUNs to the
hosts in the environment
Version 5.5
Page 96 of 197
Lab Guide
Lab Exercise 6
Preamble : The Array Configuration Array Host Port
Allocations
Host OS Type SP Port 1
HP-UX
Solaris
Windows
AIX
SP Port 2
Port 3
Port 4
CLARiiON
Lower A
Lower B
Upper A
Upper B
Management Environment
CLARiiON management can be performed using Navisphere Manager or Navisphere CLI.
You can install CLI on Unix and/or Windows hosts. Navisphere Manager jar files can be
installed on Windows hosts. Navisphere is available from the following location:
http://powerlink.emc.com -> Home -> Support -> Software Downloads
Additionally, the software is available on the student resource CD in the Navisphere
directory.
Navisphere licenses have already been installed on the array.
Version 5.5
Page 97 of 197
Lab Guide
Lab Exercise 6
Part 1: Installing CLARiiON Procedure Generator
Note: If you are a customer please skip to lab 6.2
Step Action
1
Download latest Procedure Generator from:
http://www.cs.isus.emc.com/csweb2/dgweb/CPG/clarproc.exe
2
Save program to temporary directory
Double-click clarproc.exe to begin installation, choose al Default options
Once installation completes, run the CLARiiON Procedure Generator from the
StartPrograms Menu.
Version 5.5
Page 98 of 197
Lab Guide
Select your environment configuration to get the exact procedures on configuration

of the CLARiiON.
Version 5.5
Page 99 of 197
Lab Guide
Lab Exercise 6
Part 2: Installing Navisphere
Agent/CLI - UNIX
Step Action
1
Get the file from your Resource CD
2
FTP the zip/tar file to the Solaris server
Unpack the file using unzip, uncompress or WinZip

unzip SUN_AGNT_CLI_6.24.1.5.0.zip
Install the package

A. For Solaris, the distribution is in native datastream package format.
pkgadd d NAVIAGNT.pkg
B. Type ALL and press Enter
Version 5.5
Page 100 of 197
Lab Guide
Follow the release notes to install Navisphere Agent/CLI on a platform other than
Solaris.
4
Start the agent
5.
Add Security File, the username and password must already exist
/opt/Navisphere/bin/naviseccli -AddUserSecurity -scope 0 -user claradmin
-password claradmin
Version 5.5
Page 101 of 197
Lab Guide
Verifying connectivity
/opt/Navisphere/bin/naviseccli h <SP IP Address> getcrus
Each SP has its own IP so to verify connectivity, you have to run it against both SP
CLARiiON Data:
IP of SP A: _____________
IP of SP B: _____________
Version 5.5
Page 102 of 197
Lab Guide
Navisphere UI Windows
Step Action
1
Get the content of Navisphere Agent and CLI for Windows from the Resource CD
2
Install the Navisphere Agent and CLI in Windows

A. If needed extract the .zip file
B. Double-click Navisphere Agent and Install it, choose default options
Version 5.5
Page 103 of 197
Lab Guide
C. Do the same with Navisphere CLI. Make sure you install Navisphere
Secure CLI
Version 5.5
Page 104 of 197
Lab Guide
Open Microsoft Internet explorer and point to the IP address of the SP

Username is claradmin
Password is claradmin
When you login to the CLARiiON for the first time, it will ask you to initialize
security. The username and password combination is set during that time. You
will have an opportunity to view this configuration when you login through the UI.
Version 5.5
Page 105 of 197
Lab Guide
Login screen
When you login for the first time, you will notice the storage array objects.
Navisphere Worksheet:
1. What are the objects you see above?
2. What is the role of each object?
3. Which objects do you think you need to configure storage?
4. Expand each of the objects and observe
Version 5.5
Page 106 of 197
Lab Guide
Lab Exercise 6
Part 3: Discovering Storage
Next, we will use Navisphere to obtain the storage configuration of the CLARiiON.
Note: These tasks can be performed using the CLI as well as Web UI. We will be using the
CLI for this and consequent labs
Step Action
1
Number of disks in the storage array
/opt/Navisphere/bin/naviseccli -h 10.127.96.128 getdisk | grep "Bus "
or for a specific disk:

/opt/Navisphere/bin/naviseccli -h 10.127.96.128 getdisk | grep #_#_#
Disk number is of the format Bus#_Enclosure#_slot#

For example, a disk in slot 5 enclosure 0 attached to Bus 0 would be referenced as
0_0_5
getdisk without any arguments lists all the disks. The output is very verbose so using
a pipe to regular expression parser such as grep will print a summary.
Version 5.5
Page 107 of 197
Lab Guide
How many disks are in the array and what are their sizes?
________________________________________________________________
2
Number of Raid groups

/opt/Navisphere/bin/naviseccli h <SP name> getrg [rg id]
Version 5.5
Page 108 of 197
Lab Guide
How many raid groups are in the array and how many disks are in each? Which
disks are they (list using the Bus#_Encl#_slot# convention discussed above)?
__________________________________________________________________
What raid types does the raid group support?
__________________________________________________________________
How many LUNs can be configured in this Raid group?
Number of LUNS
/opt/Navisphere/bin/naviseccli h <SP name> getlun [lun id]
getlun without any arguments lists all the disks. The output is very verbose so using
a pipe to regular expression parser such as grep will print a summary.
Version 5.5
Page 109 of 197
Lab Guide
How many LUNs have been bound on the array? What are their capacities? Which
SP is each LUN bound to?
Storage groups
/opt/Navisphere/bin/naviseccli h <SP name> storagegroup list
Version 5.5
Page 110 of 197
Lab Guide
Cache
/opt/Navisphere/bin/naviseccli h <SP name> getcache
Version 5.5
Page 111 of 197
Lab Guide
Version 5.5
Page 112 of 197
Lab Guide
Lab Exercise 7: Configuring HBAs and Host Specific

Files
Purpose:

A. Configure HBA settings for use in an EMC environment
Configure host specific files for allowing LUN access in an EMC
SAN environment
Objectives:
References:

the data center.
A. Configure HBA for use in EMC SAN environment
B. Verify local system settings are properly configured for use
in EMC SAN environment (e.g. system file settings)
Version 5.5
Page 113 of 197
Lab Guide
Lab Exercise 7
Part 1: Integrating the Host to an EMC Fibre Channel
Environment - UNIX
Configure HBA Driver & System Specific Files
AIX
To configure an AIX system to connect to an EMC SAN, the emc_odm support fileset must
be installed. The EMC ODM fileset can be be acquired at:
ftp://ftp.emc.com/pub/elab/aix/ODM_DEFINITIONS
Step Action
1
To configure the AIX host for EMC Fabric attach:
Download the correct ODM for the version of AIX being configured. In this
case, acquire the EMC.AIX.5.3.0.0.tar.Z file
Uncompress and untar the source file in /tmp/emc
Install the EMC ODM support fileset
A. Verify first if the ODM has already been installed if it has been installed,
you will see the following (minimum, more filesets for HA):
B. Load ODM
cd /tmp/emc;
cp EMC.AIX.X.X.X.X /usr/sys/inst.images
C. Invoke SMIT to install the ODM

smit installp
D. Select Install & Update from latest Available Software

Select your EMC.AIX.X.X.X.X package from /usr/sys/inst.images
Version 5.5
Page 114 of 197
Lab Guide
E. Lastly, verify that ODM was installed properly:

lslpp L EMC*
Run the EMC Config command:

/usr/lpp/EMC/Symmetrix/bin/emc_cfgmgr
If the host is correctly zoned and connect (logged in) to the SAN, the Symmetrix
VCMDBDEVICE should be visible after this step. Run inq to view devices.
/usr/lpp/EMC/Symmetrix/bin/inq.aix32
After the emc_cfgmgr command completes its run, the AIX host is now configured
for the EMC SAN environment.
NOTE: It is required to run the emc_cfgmgr program whenever devices are presented (Standard
and BCV devices) to an AIX host. Additionally, if volume t/l addresses change, or storage is
remapped to the host, the emc_cfgmgr program should be run.
Version 5.5
Page 115 of 197
Lab Guide
Sun Solaris
The Leadville driver (emlxs) implicitly does persistent port binding, therefore no further
configuration needs to be made at this time.
HP-UX
If the HP-UX server has been properly patched and brought up-to-date, no further software
installation needs to be made at this time.
Linux
If the HBAs BIOS has been properly configured according EMC specifications, no further
software installation needs to be made at this time.
Verify Local System Settings
AIX
Verify that the EMC ODM fileset has been installed:
Lslpp L EMC*
Solaris
Add the following attributes to /etc/system on a Sun System for support / compatibility within
an EMC SAN environment
Run devfsadm to scan for new devices, if it fails, reboot.
devfsadm
reboot -- -r
HP-UX
If the HP-UX server has been properly patched and brought up-to-date, no further software
configuration needs to be made at this time.
Linux
If the HBAs BIOS has been properly configured according EMC specifications, no further
software installation needs to be made at this time.
Windows
If the Windows server has been properly patched and brought up-to-date, no further
software configuration needs to be made at this time.
Version 5.5
Page 116 of 197
Lab Guide
Lab Exercise 8: Assigning Storage

Purpose:

Assign storage for each host which is now SAN attached. Using
the LUN Masking worksheet, included in this section, work with
the instructor to identify and assign LUNs to the host
Objectives:
References:

the data center.
A. Using EMC Solutions Enabler (SYMCLI), assign storage
as required for the SAN attached host
B. Reboot hosts to acquire newly assigned storage
Version 5.5
Page 117 of 197
Lab Guide
Lab Exercise 8
Part 1: Solutions Enabler - Symmetrix
Managing the VCMDBDEVICE (Volume Access Database) includes actions such as

viewing, backing up, and assigning LUNs. To perform such administrative actions, within the
EMC SAN environment, use the symmask and symmaskdb commands within the Solutions
Enabler software set. With the newly created and mapped devices, use the
symmask/symmaskdb commands to perform these actions:
Initialize the VCMDBDEVICE (VCMDB)

List HBA to VCMDB
Set to setup access to the LUNs over the configured host ports
List VCMDB
List host HBA to array FA port logins
List devices available within array
Backup the latest version of the VCMDB
Step Action
1
Initialize the VCMDB (symmaskdb)
symmaskdb sid <symm id> init f newinit.db
Log in the host HBA registry into VCM (symmask)

symmask discover hba
Version 5.5
Page 118 of 197
Lab Guide
List current host HBA registry within VCM (symmask)

symmask list hba
Setup access. Allow access to a range of devices over an array host port to a
specific host WWN. The devices can be separated by commas or if you want a
range, use a colon (01A2:01AF) . These are symmetrix device IDs, not LUN IDs.
Remember to assign dual path to the devices:
symmask sid <symm id> wwn <WWN> dir <FA> p <port #> add devs <devices
to add>
Since you are assigning dual path to the same devices, accept the alert which
states:
The following devices are already assigned in at least one entry:
Would you like to continue(y/[n])? y
Once all symmask entries have been issued to allow access to devices in the SAN,
issue a refresh command
symmask refresh
Version 5.5
Page 119 of 197
Lab Guide
List the entire contents of the VCMDBDEVICE (symmaskdb)

symmaskdb sid <symm id> list database
List contents by component

symmaskdb sid <symm id> dev <dev #> list assignment v
Version 5.5
Page 120 of 197
Lab Guide
List host HBA to FA port logins

symmask sid <symm id> list logins
List devices available within the array assigned to a specific host component
symmaskdb sid <symm id> host <wwn> list capacity
10
Backup the last working copy (loaded on the array) of the VCMDBDEVICE
symmaskdb -sid <symm_id> -f sid662_vcmbackup_03192007.vcm backup
Version 5.5
Page 121 of 197
Lab Guide
Reboot SAN Attached Hosts

As documented in Lab 4.5, reboot the host environments to discover the newly assigned
storage. Upon successful reboot, the host should see the devices which have been
assigned in the lab. If no devices are available, troubleshoot the environment following this
basic troubleshooting list:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Is the host HBAs logged into the fabric(s)?

Is the zoning correct?
Are the array host ports (FAs) logged into the fabric?
Are the entries for volume access correct within the VCMDBDEVICE? Are the correct
WWNs listed?
Has the latest configuration to the VCMDB been refreshed?
Are the local configuration files on the host correct (e.g. sd.conf; HBA configuration files,
etc.)?
Does the host require an additional configuration scan?
Does the host see the VCMDBDEVICE from the array? If so, the host can communicate
to the array, perhaps zoning or other configurations are incorrect.
Is your host permitted access to the correct volume number, lun ID, etc.?
Are the volumes and FA ports correctly implemented for your host environment? Are the
volumes assigned/mapped to the correct FA ports?
Version 5.5
Page 122 of 197
Lab Guide
Lab Exercise 8
Part 2: Navisphere CLARiiON
Assigning storage in a CLARiiON has the following components
1. If raid group does not exist, select disks for a raid group. If raid group exists, proceed
to step 3
2. Create raid group
3. Create LUN from the raid group
4. Create storage group
5. Add LUN to the storage group
6. Register the host
7. Connect the host to the storage group
We will be using Navicli to perform these steps:
Action
Step
1
Select disks
Example: Get disks in array with SP ip 10.127.96.128 (use your SP IP for this)
/opt/Navisphere/bin/naviseccli -h 10.127.96.128 getdisk
Disk 1:___________________________
Disk 2:___________________________
Disk 3:___________________________
Disk 4:___________________________
Format for disk list: Bus#_Enclosure#_slot#
Version 5.5
Page 123 of 197
Lab Guide
Create a raid group

Example: Create a Raid group with ID 10 and disks 9, 10 and 11 from Bus0, Encl 0
/opt/Navisphere/bin/naviseccli -h 10.127.16.210 createrg 10 0_0_9 0_0_10
0_0_11
Raid group ID: _________________________________

Raid group type (depends on the number of disks added to the group)
3
Create LUN from raid group

Example: Create a LUN with ID 15 in RG 10 bound to SP A with capacity 2GB and
read, write cache enabled.
/opt/Navisphere/bin/naviseccli -h 10.127.96.128 bind r5 15 -rg 10 -rc 1 wc 1 -sp a -sq gb -cap 2
LUN parameters:
ID: ____________________________________________
Bound to SP: ____________________________________
RG ID: _________________________________________
LUN Raid type: __________________________________
Read cache: Y/N
Write cache: Y/N
Size: ___________________________________________
Version 5.5
Page 124 of 197
Lab Guide
Create storage group

Example: Create a storage group with name mysg
/opt/Navisphere/bin/naviseccli -h 10.127.96.128 storagegroup -create gname mysg
Add LUN to storage group

Example: Add LUN ID 15 (ALU 15) to storage group mysg with HLU 2
/opt/Navisphere/bin/naviseccli -h 10.127.96.128 storagegroup -addhlu gname mysg -hlu 2 -alu 15
Register the host

Example: Register a host attached to the SP
/opt/Navisphere/bin/naviseccli -h 10.127.96.128 register
Example: Verify port information about the HBA from the host. Verify that both
HBAs show up.
/opt/Navisphere/bin/naviseccli -h 10.127.96.128 port list hba
Version 5.5
Page 125 of 197
Lab Guide
Connect host to the storage group

Example: Connect host sundev3-77 to Storage group mysg
/opt/Navisphere/bin/naviseccli -h 10.127.96.128 storagegroup
-host sundev3-77 -gname mysg
-connecthost
List storage group

Example: List storage group mysg
/opt/Navisphere/bin/naviseccli -h 10.127.96.128 storagegroup -list -gname
mysg
Version 5.5
Page 126 of 197
Lab Guide
Reboot SAN Attached Hosts

As documented in Lab 4, reboot the host environments to discover the newly
assigned storage. Upon successful reboot, the host should see the devices which
have been assigned in the lab. If no devices are available, troubleshoot the
environment following this basic troubleshooting list:
Is the host HBAs logged into the fabric(s)?

Is the zoning correct?
Are the array host ports logged into the fabric?
Are the correct WWNs for the HBA listed in the storage group?
Are the local configuration files on the host correct (e.g. sd.conf; HBA
configuration files, etc.)?
Does the host require an additional configuration scan?
Is your host permitted access to the correct lun ID, etc.?
Is the host registered and connected?
Version 5.5
Page 127 of 197
Lab Guide
Lab Exercise 9: Multipathing Installing EMC

PowerPath
Purpose:
Objectives:
This lab is predicated on the fact that the following environment

has been installed and configured:
A. 1 or more hosts SAN attached
B. Hosts are zoned
C. Storage has been assigned to hosts in the environment

A. Install EMC PowerPath and test its functionality
B. Reboot server to configure PowerPath
References:
Version 5.5
Page 128 of 197
Lab Guide
Lab Exercise 9
Part 1: Multipathing in Solaris
PowerPath on Solaris now includes PowerVolume. This section will describe how to install
both PowerPath and PowerVolume but only how to configure PowerPath in the
environment. The target version of PowerPath is: 5.0.6
Step Action
1
Acquire source package, either via Powerlink or resource CD and ftp it to a location
(/tmp/pp) on your host.
2
Move software to directory on target machine and unzip the package

cd /tmp/pp
gunzip EMCPower.SOLARIS.5.X.X.GA.XXXX.tar.gz
tar xvf EMCPower.SOLARIS.5.X.X.GA.XXXX.tar.gz
Once the package is unpacked from the tar.gz file, install using pkgadd
pkgadd -d .
Select All and follow default locations for installation targets

4
Select default options during installation by pressing Enter
After installation completes, quit the installation:

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:q
Version 5.5
Page 129 of 197
Lab Guide
After installation, register the product using the key found in the PowerPath directory
on the resource CD:
empreg install
Check the registration

/etc/powermt check_registration
After key registration, configure PowerPath by running /etc/powermt config and

then powermt display to check all paths
Note: In some environments, PowerPath will not operate properly upon completion of the install and
licensing. Rebooting the host in this case usually clears the problem.
/etc/powermt config
/etc/powermt display
Version 5.5
Page 130 of 197
Lab Guide
Lab Exercise 9
Part 2: Multipathing in AIX
Setup access to the array and configure volumes/devices to be working on the system first.
Step Action
1
Acquire source package, either via Powerlink or resource CD and ftp it to a location
(/tmp/pp) on your host.
2
Unpack the source

cd /tmp/pp/
gunzip EMCPower.AIX.5.X.X.tar.gz
tar xvf EMCPower.AIX.5.X.X.tar.gz
Verify that the package is there

Install the product, from the same directory,
installp ad . EMCpower
When the software is installed, the following will be listed

Version 5.5
Page 131 of 197
Lab Guide
Perform the following post-installation steps:

A. Register the product by issuing the command:
emcpreg -install
B. Check the registration

powermt check_registration
Version 5.5
Page 132 of 197
Lab Guide
C. Configure and display the power device paths

powermt config; powermt display; powermt display dev=all
D. Configure the PowerPath devices from within smit, perform the following:
smitty p
Select Devices->PowerPath Disk->Configure All PowerPath Devices
E. After smit completes configuring all PowerPath devices, run the following rc
setup:
Version 5.5
Page 133 of 197
Lab Guide
rc.emcpower start
PowerPath is now installed and properly configured in the environment.
Version 5.5
Page 134 of 197
Lab Guide
Lab Exercise 9
Part 3: Multipathing in HP-UX
PowerPath on HP-UX now includes PowerVolume. This section will describe only how to
install PowerPath and how to configure PowerPath in the environment. The target version of
PowerPath is: 5.0.6
The details for installing PowerPath in a HP-UX environment can be read in the document,
PowerPath for HP-UX Installation and Administration Guide
Step Action
1
Acquire source package, either via Powerlink or resource CD and FTP it to you
host
2
Move software to directory on target machine and unzip the package

mkdir /tmp/pp
mv EMCpower.HP.X.X.X.tar.gz /tmp/pp
cd /tmp/pp
gunzip EMCpower.HP.X.X.X.tar.gz
tar xvf EMCpower.HP.X.X.X.tar
Once the package is uncompressed from the tar.gz file, install using swinstall
swinstall x autoreboot=true x mount_all_filesystems=false s
/tmp/pp/EMCPower.HP.X.X.X.tar EMCpower
After the swinstall process completes, the host will reboot. After reboot,
administrative tasks must be performed before PowerPath will operate properly.
License PowerPath. Using the registration key found on the resource CD, license
the product by running the following command:
emcpreg install
Once installation completes, configure PowerPath and display the paths available
to storage. Run the following commands:
powermt config
powermt display
powermt display dev=all
Version 5.5
Page 135 of 197
Lab Guide
Version 5.5
Page 136 of 197
Lab Guide
Lab Exercise 9
Part 4: Multipathing in Windows
Step Action
1
Acquire source package, either via ftp or resource CD the resource CD is in
Windows format so it is possible to mount the CD directly on the Windows server
2
Copy the software from CD to a pre-defined directory (e.g. C:\emc\software)
Run the package which was copied to the directory by double-clicking on the
package
Follow the Install Shield installer prompts to install the package. Accept or change
defaults for installation location (most likely and recommended is to accept defaults)
Enter license key once prompted (license key: XIPV-YFP3-H3RM-YTVG-AP9PVXQP)
Version 5.5
Page 137 of 197
Lab Guide
Click Add to have the entered key registered with the product configuration
Click OK to register and complete the installation
Click Finish to complete the installation
Reboot server to have PowerPath activate and configure
Testing PowerPath
After installing PowerPath, verify that all devices are operating correctly and that the host
sees the devices which were planned for. If additional configuration work or troubleshooting
is required, this is the time in which to address any issues before proceeding.
Version 5.5
Page 138 of 197
Lab Guide
Lab Exercise 10: LVM Implementation

Purpose:
Objectives:
References:
The goal of this lab is to create basic LVM objects using the newly
assigned EMC storage presented to the host. Volumes may be
created with either the native LVM package or via third party
package such as Veritas VxVM.

datacenter.
A. Verify SAN devices are presented to the host
B. Verify and initialize volume management package on the
host.
C. Create a simple volume using 1 or more SAN devices on
the local host
D. Create a filesystem (FS) on the newly created volume and
mount the volume. Add the volume to local files to have it
mount on reboot
E. Write test data to the new volume
F. Document the mapping of the host volume to: LVM group>devices->SAN devices->EMC storage devices->physical
devices within the array
Version 5.5
Page 139 of 197
Lab Guide
Lab Exercise 10
Part 1: LVM Implementation in HP-UX
From a telnet or SSH window, connect to a host. We will performing all operations using
sam
Step Action
1
Confirm that the host sees the new devices
ioscan fnC disk
Create special /dev/dsk and /dev/rdsk files

insf e
Start SAM; Select Disks and Filesystems

sam
Version 5.5
Page 140 of 197
Lab Guide
Select: Volume Groups
Hit tab to go to the menu, navigate to Actions, press enter and select Create
Version 5.5
Page 141 of 197
Lab Guide
Edit new volume group properties by navigating to them and hitting Enter
Volume group Name: myvg
Version 5.5
Page 142 of 197
Lab Guide
Disks: Hit enter on Select disks, navigate to desired disks and select by pressing
Enter
Hit enter on Modify Default Volume-Group Options

Look at the properties
Version 5.5
Page 143 of 197
10.
Lab Guide
Hit enter on Configure Disks

Look at the options, make sure you are not adding the VCMDB to your Volume
Group
11
Tab to Ok and press Enter to complete the creation of the Volume Group, when
the new volume group is created go to File and Exit.
Version 5.5
Page 144 of 197
Lab Guide
12
Now select Logical Volume from the Menu and press Enter
13
On the next windows go to Actions Create
Version 5.5
Page 145 of 197
Lab Guide
14
On the Create New Logical Volumes popup set the Volume Group to myvg
15
Next, hit Enter on Define New Logical Volume(s)
Set the following parameters:

LV Name: myvol
LV Size: 500
Mount: /myfs
Version 5.5
Page 146 of 197
Lab Guide
A. Hit enter on Modify LV Defaults go to Striping and select Use Striping
B. Hit enter on Modify FS Defaults
Version 5.5
Page 147 of 197
Lab Guide
C. Go to Add and press Enter
D. Next go to OK and complete the Logical Volume
Version 5.5
Page 148 of 197
Lab Guide
E. Exit sam
16
Verify that new filesystem is mounted

bdf
Version 5.5
Page 149 of 197
Lab Guide
Lab Exercise 10
Part 2: HP-UX Volumes with PV-Links Multipathing
PV Links is a multipathing feature that ships with HP-UX, and that is tightly integrated with
the native Logical Volume Manager. PV Links thus serves as a native alternative to
PowerPath on HP-UX hosts only. PV Links provides failover capability, but cannot
dynamically balance load over multiple active paths to a LUN. This lab exercise will
familiarize you with deploying HP-UX volumes with PV Links providing the multipathing.
Step Action
1
Ensure that PowerPath is not installed on the HP-UX system.
swlist | grep i power
If installed, PowerPath should be removed using swremove before proceeding.

2
Confirm that all disks are visible via two paths to the HP-UX system.
The recommended path configuration for PV Links implementation is: one primary
path and one alternative (or secondary) path to each LUN. The primary and
alternative paths should use distinct HBAs and Symmetrix FA ports. For a
CLARiiON-attach, the primary and alternative paths should use one port each on
different SPs e.g. SPA-0 and SPB-0.
Run ioscan to get a listing of all available disks on the system. The example here is
specific to a Symmetrix-attach.
ioscan fnC disk | more
Version 5.5
Page 150 of 197
Lab Guide
The ioscan listing should be similar to the above. Here there are two controllers
i.e. HBAs - c24 and c28, and Symmetrix LUNs visible via both controllers.
Use symcfg to verify that each LUN is accessible via two different FA ports:
symcfg sid <###> -FA <FA and Port> address list
Version 5.5
Page 151 of 197
Lab Guide
In our example above, we see that our four Symmetrix LUNs are accessible via two
FA ports, 16B and 03A.
Next, run the symmaskdb command to verify that each HBA can access all LUNs via
its own distinct FA port:
symmaskdb sid <###> list database
Version 5.5
Page 152 of 197
Lab Guide
Note that the Identifier column shows the WWPN (ending in 74e6 and 74d6) of
the HBA connected to each of the two FA ports.
4
Check FA port settings with the symcfg command for each FA port. For PV Links, in
addition to the V-bit (Volume Set Addressing), the C-bit (Common Serial Number)
should also be enabled:
symcfg sid <symm id> SA <fa> v list | grep Common
Version 5.5
Page 153 of 197
Lab Guide
Change FA port settings if needed.

In our example, the Common Serial Number bit is disabled and needs to be
enabled. This is done using symconfigure. The screenshot below shows the
appropriate script file to be supplied to symconfigure f to enable Common Serial
Number:
After the symconfigure commit step, verify that the new FA port settings are correct
using symcfg.
6
Make a directory and the device file named group for the new volume group that will
contain the multipathed devices.
mkdir /dev/my_vg
Next, use the mknod command to create the group device file for the volume group.
For major device number, specify the value 64. For minor device number, use
0xNN0000 where NN is in the range 00 through 09. The screenshot below shows the
procedure.
The output of ls l /dev/*/group shows that the minor device number 0x000000
is already in use for the volume group vg00. So for my_vg, we use the number
0x010000:
ls l /dev/*/group
mknod /dev/my_vg/group c 64 0x0<##>0000
Version 5.5
Page 154 of 197
Lab Guide
Initialize the primary path device only, for each LUN, using pvcreate.
pvcreate /dev/rdsk/c#t#d#
Note that each controller can provide a primary path for some LUNs, and a
secondary path for all other LUNs. This enables static load-balancing by spreading
the traffic to multiple LUNs over both available paths.
In the example above, the c24 path is the desired primary for LUN 1, while the c28
path is the desired primary for LUN 2.
8
Add the primary paths to the volume group using vgcreate. Then specify the
alternate paths to the volume group using vgextend :
vgcreate /dev/my_vg
/dev/dsk/c24t0d1
/dev/dsk/c28t0d2
vgextend /dev/my_vg
/dev/dsk/c28t0d1
/dev/dsk/c24t0d2
Version 5.5
Page 155 of 197
Lab Guide
Verify the presence of both primary and Alternate Link for each physical volume
in the volume group. This information is at the tail-end of the listing from:
vgdisplay v my_vg
10
Build logical volumes within the volume group my_vg, and filesystems on the logical
volumes. This is done in the same way as in the previous lab (10.1).
11
Switch the primary and secondary paths for one physical volume, using the
pvchange command:
pvchange s /dev/dsk/c28t0d1
Rerun vgdisplay v my_vg, and verify that the primary and alternate devices have
changed for this physical volume.
vgdisplay v my_vg
Version 5.5
Page 156 of 197
Lab Guide
Lab Exercise 10
Part 3: LVM Implementation on AIX
From a telnet or SSH window, connect to a host. We will be performing all operations
using smit. You are free to perform these operations using the command line.
Step Action
1
Confirm that all disks are visible to the system
A. Using inq
inq
B. Using smit
Devices -> List Devices -> List All Defined devices
Version 5.5
Page 157 of 197
Lab Guide
Note all the disks you will be using

VG name = myvg
myvg-01 = __________________________
myvg-02 = __________________________
myvg-03 = __________________________
myvg-04 = __________________________
Version 5.5
Page 158 of 197
Lab Guide
Run EMC Configuration Manager

emc_cfgmgr
Proceed to Volume group creation

smit
System Storage Management (Physical & Logical Storage) Logical Volume
Manager Volume Groups Add a Volume Group
Volume Group Name = myvg

Physical Volume names from Step 1
4
Create a filesystem
Version 5.5
Page 159 of 197
Lab Guide
Lab Exercise 11: Managing Storage in the SAN

Environment
Purpose:

A. Unmap and map devices to host (FA) ports
B. Unmap devices and return devices to freepool
C. Move devices from host to another in the environment
D. Map meta devices
Create a single simple large meta to assign to one SAN attached
host this meta could be used for either expansion, backup-todisk purposes, or boot from SAN array
Objectives:
Group A:
A. unmap and unassign all volumes from server A1-SUN1
B. Map assign meta device to A1-SUN1
Group B:
A. Map and assign two meta volumes to host A1-NT1
B. Map and assign 1 meta volume to host A2-SUN3
Group C:
A. Move 10 volumes from A3-SUN1 to A3-NT
(unmap/unassign from A3-SUN1, map and assign to A3NT)
Group D:
A. Zone host A4-SUN2 to Symm, disconnect from CLARiiON,
map and assign 2 meta volumes
Final, extra credit, Create a new Meta:
A. Using Solutions Enabler, create a single concatenated
meta volume. The meta volume should consist of at least
5 hyper volumes
B. Additionally, create a second meta device for use as a
boot volume for the host environment. Plan on making the
volume at least 8.43GB in size
C. Configure the host to access the meta volumes perform
all necessary SAN configurations to allow the host to
access the newly created meta
D. Create filesystem, volume group, etc. for this new volume
E. Write test data to the volume
Version 5.5
Page 160 of 197
Lab Guide
Make a note within the SAN configuration worksheets identifying

the meta volume and each meta member
SAN attached hosts will have storage reconfigured.
References:
Version 5.5
Page 161 of 197
Lab Guide
Step Action
1
Removing device access permissions
The first step in changing storage configurations for a host(s) is to remove access
(lun masking) to any host which might be able to access the device. This is
performed via SYMCLI in a Symmetrix environment and navicli in a CLARiiON
environment.
Remove access to devices 001 005 for host with HBA 50060b0000077f12 on FA
15cB
A. Output the current contents of the VCMDB to a file
symmaskdb -sid <symm id> list database >/tmp/vcmdb.list
B. Backup the existing VCMDB before making any changes

symmask sid <symm id>
backup file /var/tmp/nameofbackupfile.bak
C. View /parse the file listing which WWNs are to be removed (or list HBAs on
server using symmask)
grep <WWN> /tmp/vcmdb.list
symmask list hba v
D. Remove devices which will be presented to host WWNs via the SAN
symmask -sid <symm id>
devs <DEV RANGE>
-wwn <WWN> -dir <FA> -p <port #> remove
E. Alternatively, remove the WWN from the VCMDB thus removing any access
priveledges
symmask sid <symm id> delete wwn <WWN>
F. Refresh the VCMDB with the updated configuration

symmask -sid <symm id> refresh
Write disabling devices to perform unmap

In order to unmap a device from a FA (host) port on a Symmetrix array, it is
required to write_disable the device. By write disabling the device, access is
explicitly denied to any host or I/O component in the entire environment. Once the
device is re-mapped to a different array, it is not necessary to write enable. For this
example, devices 025, 026, 027 in symmetrix 084 will be write disabled and
unmapped.
A. Identify the device to be write_disabled and unmapped:
symdev -sid <symm id> list |more
0008 Not Visible

0009 Not Visible
-
***:* 01B:CB
2-Way Mir
N/Grp'd
(m) RW
***:* 16B:CE
2-Way Mir
N/Grp'd
(m) RW
Version 5.5
Page 162 of 197
000A Not Visible

-
Lab Guide
***:* 01A:CE
2-Way Mir
N/Grp'd
(m) RW
By looking in the 10th column listing, it is show that the device is set to RW (write
enabled) and that it is currently not grouped (8th column listing)
B. Create Symmetrix device group
symdg create unmap_grp -type REGULAR
C. Add the devices to the group

symld -g unmap_grp add dev 025
D. List the device group to see contents

symdg show unmap_grp
Group Name:
unmap_grp
Group Type
Device Group in GNS
Valid
Symmetrix ID
Group Creation Time
Vendor ID
Application ID
Number
Number
Number
Number
Number
Number
Number
of
of
of
of
of
of
of
:
:
:
:
:
:
:
REGULAR
No
Yes
000187900084
Fri Jul 30 12:46:53 2004
EMC Corp
SYMCLI
STD Devices in Group

:
Associated GKs
:
Locally-associated BCVs
:
Locally-associated VDEVs
:
Remotely-associated BCVs (STD RDF):
Remotely-associated BCVs (BCV RDF):
Remotely-assoc'd RBCVs (RBCV RDF) :
3
0
0
0
0
0
0
Standard (STD) Devices (3):

{
-------------------------------------------------------------------Sym
Cap
LdevName
PdevName
Dev Att. Sts
(MB)
-------------------------------------------------------------------DEV001
N/A
0025
RW
449
DEV002
N/A
0026
RW
449
DEV003
N/A
0027
RW
449
}
Looking at the Sts column, at the end of the output, see that the devices are listed
as RW.
E. Perform the write_disable on the group, thus write disabling all devices in
the group
symld -g unmap_grp write_disable
Write Disable ALL devices in group 'unmap_grp' on
ALL Directors, ALL Ports (y/[n]) ? y
Version 5.5
Page 163 of 197
Lab Guide
F. Once the write disable is complete, list the device group and check for WD
in the STS field
symdg show unmap_grp
Group Name:
unmap_grp
Group Type
Device Group in GNS
Valid
Symmetrix ID
Group Creation Time
Vendor ID
Application ID
Number
Number
Number
Number
Number
Number
Number
of
of
of
of
of
of
of
:
:
:
:
:
:
:
REGULAR
No
Yes
000187900084
Fri Jul 30 12:46:53 2004
EMC Corp
SYMCLI
STD Devices in Group

:
Associated GKs
:
Locally-associated BCVs
:
Locally-associated VDEVs
:
Remotely-associated BCVs (STD RDF):
Remotely-associated BCVs (BCV RDF):
Remotely-assoc'd RBCVs (RBCV RDF) :
4
0
0
0
0
0
0
Standard (STD) Devices (4):

{
-------------------------------------------------------------------Sym
Cap
LdevName
PdevName
Dev Att. Sts
(MB)
-------------------------------------------------------------------DEV001
N/A
0025
WD
449
DEV002
N/A
0026
WD
449
DEV003
N/A
0027
WD
449
}
G. Once the write disable operations are complete, the Symmetrix device
group can be destroyed since it is no longer needed/required
symdg -force delete unmap_grp
Unmapping device from FA ports

In order to unmap the devices from FA ports, it is necessary to create symconfigure
scripts. The scripts can be created using any text editor on the machine from which
symconfigure will be run.
Sample unmap symconfigure script: (# is a comment; commands end with a semicolon; one command per line; substitute devices and FA ports as required)
#
#
UNMAP DEV <symdevname>[:<symdevname>] FROM DIR
#
< ALL:ALL | ALL:<port_number> | <director_num>:ALL |
#
<director_num>:<port_number> >
#
[devmask_access = <remove | retain>];
#
unmap
dev 0035 from dir 1C:0;
unmap
dev 0035 from dir 1C:1;
Version 5.5
Page 164 of 197
Lab Guide
Once the symconfigure unmap command file has been constructed, verify that
symconfigure is operating and then run the script:
symconfigure -sid <symm id> verify
symconfigure sid <symm id> commit f unmap.cmd
Mapping devices to FA ports

List available addresses per FA port within the Array:
List available free address space on each target FA for the host
symcfg sid <symm id> list FA <FA> p <port #> address
Build a map command file with the devices and required target/lun addresses.
Listed here is a sample map file:
map_aix.cmd:
map
dev 0057 to dir 15d:0 target=0, lun=002;
map
Version 5.5
Page 165 of 197
Lab Guide
map
map
dev 005a to dir 15d:0 target=0, lun=005;
Once the map file is complete, run the script through symconfigure:
symconfigure sid <symm id>
f <filename> commit
Once the mapping is complete, again list the devices in the array (run symcfg
discover first) to make sure all is as configured (expected).
After verification, provide access to the newly assigned storage with symmask.
Extra: Create Meta Devices

Identify free space within the SAN array
Synchronize the local symapi database with the array and list the configured array.
symcfg discover
symcfg list
List available free address space on each target FA for the host
symcfg sid <symm id>
list FA <FA> p <port #> address
Version 5.5
Page 166 of 197
Lab Guide
Make note of two free TID LUN addresses:

Address 1: ____________________________
Address 2: ____________________________
List all devices within the array, comparing devices with what is assigned in
the VCMDB
symdev sid <symm id> list
Version 5.5
Page 167 of 197
Lab Guide
symmaskdb sid <symm id> list database
Version 5.5
Page 168 of 197
Lab Guide
Note two free meta head devices:

Meta Head 1: _________________________
Meta Head 2: _________________________
Compile a list of available devices for building the two required meta devices
List of devices for Meta Head Dev 1:
List of devices for Meta Head Dev 2:
Verify that symconfigure is operational
Version 5.5
Page 169 of 197
Lab Guide
Build the symconfigure command file

Using a familiar text editor, create a command file which will create the two meta
devices for use in the create of the meta devices. A sample command file will look
something like:
form
meta from dev 005B, config=striped stripe_size=1920;
add dev 005C to meta 005B;
add dev 005D to meta 005B;
add dev 005E to meta 005B;
add dev 005F to meta 005B;
add dev 0060 to meta 005B;
add dev 006A to meta 005B;
add dev 006B to meta 005B;
add dev 006C to meta 005B;
add dev 006D to meta 005B;
add dev 006E to meta 005B;
Run the symconfigure command file

Once the command file for building the meta devices is complete, check the syntax
with symconfigure:
symconfigure sid <symm id> f <filename> preview
If all configurations check, and the changes are ready to be committed, run the
symconfigure command with the commit option.
symconfigure sid <symm id> f <filename> commit
Once the command finishes successfully, you should be able to view the newly
created devices with symdev
symdev sid <symm id> show <dev> |more
Version 5.5
Page 170 of 197
Lab Guide
Map the newly configured volumes to host (FA) ports

Using symconfigure, it is possible to map the device to the appropriate host port in
the array. Create the symconfigure map file for configuring the mapping for the
device. The map command file should look something like:
map
dev
map
dev
map
dev
map
dev
map
dev
0056 to dir 15c:0 target=0, lun=009;

0057 to dir 15d:0 target=0, lun=002;
005a to dir 15d:0 target=0, lun=005;
Test the syntax of the command file by issuing a preview before attempting a
commit.
symconfigure sid <symm id> f <filename> preview
If the command passes a syntax check, proceed with the commit:

symconfigure sid <symm id> f <filename> commit
Lastly, these newly created devices must be accessible and configured to be seen
on the hosts. As done in previous labs, perform the required volume masking and
host configuration in order to have the host access the new meta volumes.
Version 5.5
Page 171 of 197
Lab Guide
Use the following simple worksheet to note the final meta configuration in the
environment:
Host Name
Ibmdev1-76
Meta Device
(head)
005b
FA Port
Mapping
15D:0
Version 5.5
Meta Members
003,005,006:013
Page 172 of 197
Lab Guide
Lab Exercise 12: Reclaiming Storage and SAN

Resources
Purpose:
Objectives:
References:
The goal of this lab is to reclaim all storage and SAN ports for the
services in the environment.

the data center.
A. Unmount/unconfigure volumes from the host
B. Stop and unconfigure PowerPath
C. Un-install CC Master and Host agent (if present)
D. Remove any volume group created to use SAN volumes
E. Remove device to host LUN masking in the VCMDB
clear all host WWNs for the environment
F. Dissolve any meta volumes created in the environment
G. Un-map any device used in the environment and return
the devices to the un-mapped freepool
H. Remove zones created to configure servers to SAN
environment
I. Reboot and verify that the host no longer sees any SAN
storage
Update documentation to reflect all changes made to the
environment
NOTE: This section includes an example of one host type, HP-UX. The functions of
removing a host from a SAN and unconfiguring a volume are generic and should be
applicable to most host platforms.
Version 5.5
Page 173 of 197
Lab Guide
Step Action
1
Unmount/Unconfigure Volumes From the Host
A. First, determine which volumes are mounted to the host. This can be
accomplished with either CLI or the system administration tool, sam.
Run, bdf to determine what is currently mounted as a block device. This
command can be substituted by df k
bdf
B. Unmount the volume by running:

umount /myfs
C. Verify that the volume has been unmounted by running bdf again
bdf
D. Remove any entries for /dev/vg00/lvol5 (/myfs) from the local filesystems
file (/etc/fstab or /etc/vfstab)
Version 5.5
Page 174 of 197
Lab Guide
Stop and Unconfigure PowerPath

Remove PowerPath by running:
swremove x autoreboot=true EMCpower
Windows Hint: Control Panel->Add Remove Software->PowerPath

Solaris hint: use pkgrm EMCpower
AIX Hint: use installp u package_name
Once PowerPath has been removed, it maybe required to reboot the host (HPUX). Once remove/reboot is completed, check that PowerPath has been
removed:
HP-UX: swlist
AIX: lslpp ad |grep i EMCpower
Solaris: pkginfo |grep i EMCpower
3
Un-install CC Master and Host Agent

Verify if the host is running ECC agents:
ps ef
|grep i ecc
If the host is found to be running ECC agents, run the uninstall_master.sh

script found in /usr/ecc
/usr/ecc/uninstall_master.sh
Version 5.5
Page 175 of 197
Lab Guide
After installation is complete, the uninstall script will prompt:

Master Agent uninstallation complete.
If there are no other products installed under /usr/ecc
you may also want to manually delete the following:
/usr/ecc/uninstall_master.sh (this script)
/usr/ecc (base directory)
Remove SAN Volume and Host Volume Group

A. List the volume to be removed. Run:
lvdisplay /dev/<volume group>/<volume name>
Version 5.5
Page 176 of 197
Lab Guide
B. Remove the volume, run:

lvremove <volume name>
C. Display volume group, run:

vgdisplay <volume group>
D. Remove the volume group. From SAM, select the volume group, then
choose to remove.
Version 5.5
Page 177 of 197
Lab Guide
Special procedure to remove HP-UX volume group when using PV Links.

E. First, remove all logical volumes that use the Symmetrix or CLARiiON LUNs
with the lvremove command, or using SAM as described earlier.
Next, remove all alternative links within the volume group using vgreduce (see
the screenshot below for syntax). Then remove all except one primary link
within the volume group again using vgreduce.
Finally, destroy the volume group using vgremove.
Version 5.5
Page 178 of 197
Lab Guide
Remove device to host LUN masking in the VCMDB

View the currently configured VCM and ascertain which WWNs are assigned
devices to be removed. A practical way to accomplish this task is to:
A. Output the current contents of the VCMDB to a file
symmaskdb -sid <symm id> list database >/tmp/vcmdb.list
B. Backup the existing VCMDB before making any changes

symmask sid <symm id> backup file /var/tmp/<backup_file>
C. View /parse the file listing which WWNs are to be removed (or list HBAs on
server using symmask)
grep <WWN> /tmp/<backup_file>
symmask list hba v
D. Remove devices which will be presented to host WWNs via the SAN
symmask -sid <symm id> -wwn <WWN> -dir <fa> -p <port #> remove devs
<device range>
E. Alternatively, remove the WWN from the VCMDB thus removing any access
privileges
symmask sid <symm id> delete wwn <WWN>
F. Refresh the VCMDB with the updated configuration

symmask -sid <symm id> refresh
Version 5.5
Page 179 of 197
Lab Guide
Dissolving meta volumes

If there are any configured meta volumes within the environment, dissolve them,
thus releasing any meta members to the disk freepool. The dissolve actions can
be executed by the Solutions Enabler, symconfigure command. Shown here is a
sample dissolve action.
<cmd file>
dissolve
meta dev ###;
meta dev ###;
meta dev ###;
meta dev 4c9;
Once the command file is written, execute the commands in the file by running the
file against symconfigure:
symconfigure sid <symm id> f <file> commit
Unmapping devices
Once devices have been dissolved and access revoked, it is appropriate to unmap
from the array host ports (Symm FA ports)..
Use the Solutions Enabler symconfigure command to unmap devices from array
host ports.
<cmd file>
unmap
dev ### from dir 16C:1;
unmap
dev 4c9 from dir 16C:1;
After writing the command file, run the commands through symconfigure:
symconfigure sid <symm id> f <file> commit
Remove zones
Using either B-Series WebTools or M-Series Connectrix Manager, remove zones
from the active zone Sets.
Version 5.5
Page 180 of 197
Lab Guide
Appendix 1: Installing lpfc driver in Solaris Environment

Purpose:
Objectives:
References:
The goal of this lab is to install the lpfc driver in a Solaris

Environment. This driver has been replaced by emlxs driver

the data center. The objective is to successfully install the Solaris
lpfc driver
Version 5.5
Page 181 of 197
Lab Guide
Install Solaris lpfc driver

Step Action
1
Search for the HBAs installed on the system
prtdiag |grep i lpfc
Acquire the latest driver, firmware, and boot code for the Solaris Emulex HBA
J.
K.
L.
M.
N.
O.
P.
Q.
Open the Emulex website in a browser: http://www.emulex.com

Click on the support link at the top menu
Select EMC from the suppliers list
Click on the appropriate HBA for the server (shown above)
Download the Firmware from this page.
Select Solaris on the right hand menu.
Download the Driver, Readme, and Manual
FTP the driver to a safe location (var/tmp/emulex) in the Solaris host
Version 5.5
Page 182 of 197
Lab Guide
Uncompress Emulex code and install driver, and Emulex HBA Anywhere Utility
F. Change to the /var/tmp/emulex directory (to which you copied the Driver
and Applications kit) and untar the kit:
cd /emulex
tar xvf Solaris-xxx.tar
G. When the untar is complete you will find these components:
lpfc-yyy-sparc.tar (where yyy is the driver revision) Emulex

Fibre Channel Solaris driver
EmlxAppsZZZ.tar (where ZZZ is the HBAnywhere version) Emulex
Applications kit (containing: lputil, HBAAPI, and HBAnywhere)
readme.first.txt
H. Install the driver, To access help during installation press ? or ??

tar xvf lpfc-yyy-sparc.tar
pkgadd -d .
Select package(s) you wish to process (or 'all' to process all
packages). (default: all) [?,??,q]: <ENTER>
Rebuild manual pages database for section 7d [y,n,?] <ENTER>
Section 7d of the online man pages contains the manual pages for
lpfc. Normally the catman command can be run to create preformatted
versions of the online manual from the nroff(1) input files. Each
manual page is examined and those whose preformatted versions are
missing or out of date are recreated. If any changes are made,
catman recreates the windex database. Depending on your system, this
operation can take from 1 to 10 minutes. If you enter N, the catman
will be skipped, allowing the installation to complete quickly. The
skipped catman command will be output for the administrator to run
later, if desired.
Use IP networking over Fibre Channel [y,n,?]: <N>
No disables IP networking through the Emulex card. FC-IP is not supported in Emulex HBAs
Do you want to continue with the installation of <lpfc> [y,n,?]: <Y>
The installation package continues the installation.
packages). (default: all) [?,??,q]: <Q to quit installation>
DO NOT REBOOT YET!
I. Install the Emulex Application Kit

tar xvf EmlxAppsZZZ.tar
pkgadd -d .
packages). (default: all) [?,??,q]: Select HBAnywhere
***IMPORTANT NOTICE ***
Version 5.5
Page 183 of 197
Lab Guide
This machine must now be rebooted in order to ensure safe operation.

Do you want to continue with the installation of <HBAnywhere> [y,n?]
<Y>
The installation package continues the installation, when it finishes:
packages). (default: all) [?,??,q]: <Q>
CAUTION! EMC does not support the Emulex HBAnywhere GUI.
Edit any necessary files as described under Incorporating EMC Fibre

Channel on page 2-16 of the EMC Fibre Channel with Emulex Host
Bus Adapters in the Solaris Environment document.
Reboot the host with the -r (reconfigure) option:

reboot r
J. Upgrade firmware:
Copy the firmware file to the appropriate directory /usr/sbin/lpfc
cp XXXXXX.all /usr/sbin/lpfc
Start the Firmware Utility

/usr/sbin/lpfc/lputil
Select option 3 Firmware Maintenance.

Select option 1 Load Firmware Image.
Type the full file name of the image file and press ENTER
Select option 0 Return to Main Menu.
Repeat steps 3 through 7 for any other adapters.
Version 5.5
Page 184 of 197
Lab Guide
K. Upgrade Boot Code

Upgrade the firmware of the HBA as describe above
Copy the appropriate file for the HBA to the /usr/sbin/lpfc directory.
For the LP-10000 card, use the TO141A2.PRG file. For other files for
other HBAs, refer to the Emulex documentation
Start the fcode update utility:
Select option: 3 Firmware Maintenance
Select the appropriate action:
1. PCI Bus; select: 1 - Load Firmware Image
2. S/Bus; select: 6 - Load FCode Image
Enter the full name of the image file
Select option: 0 Return to Main Menu
Repeat steps 4 through 8 for any other adapters
L. Once upgrades are complete, reboot the host to have all changes take effect.
To reboot:
/usr/sbin/reboot -- -rv
Once the host has rebooted, check for the availability of the Emulex HBA the WWN
should be found in /var/adm/messages:
grep lpfc* /var/adm/messages |more
Version 5.5
Page 185 of 197
Lab Guide
Edit Configuration Files for Solaris lpfc driver

To ensure that the Solaris host will interact and perform properly with an EMC array, the
following files must be edited:
/kernel/drv/lpfc.conf Emulex driver configuration file

/kernel/drv/sd.conf Solaris sd driver configuration file
/etc/system Solaris system specific configuration file
Step Action
1
Setting up lpfc.conf:
A. Setup persistent binding for the Emulex HBAs must be done for both the
lpfc.conf and sd.conf files. Use the /usr/sbin/lpfc/lputil binary to
setup persistent binding in the lpfc.conf file:
1
2
3
4
5
6
Select: 5 persistent bindings
Select desired HBA

Select: 5 Bind automapped targets
For bind all auto-mapped targets, answer Y (yes)
Select: 2, to bind by port name
Note: Array port WWNs will only be accessible/seen from within lputil once zones have been
created between the host HBA and array FA ports. Setup persistent binding with the lputil after
zoning has been created.
Version 5.5
Page 186 of 197
Lab Guide
B. Following the procedures found on page 27, in EMC Fibre Channel with
Emulex Host Bus Adapters in the Solaris Environment. Configure the
HBAs in the Solaris host. This document is found in the TOOLS/Solaris
directory of the resource CD
Edit the /kernel/drv/lpfc.conf to contain the following values:
log-verbose = 0x10
log-only = 1
fcp-bind-WWNN = lputil tool to setup
automap = 2
fcp-on = 1
lun-queue-depth = 20
tgt-queue-depth = Symmetrix = 512 | CLARiiON CX = 512
no-device-delay = 0
xmt-que-size = 256
scan-down = (for FC-SW) 0
linkdown-tmo = 60
nodev-holdio = 0
nodev-tmo = 60
num-iocbs = 2048
topology = (FC-SW) 2
All other values can be left at their default settings.
Setting up /kernel/drv/sd.conf:
Modify /kernel/drv/sd.conf to have the following definitions for each target ID that
needs to support multiple LUNs:
name=sd parent=lpfc target=X lun=Y hba=lpfcZ;
Where:
X is the target number that corresponds to the fcp_bind_WWNID lpfcZtX.
This target number is displayed in the lpfc.conf file
Y is the LUN number that corresponds to Symmetrix volume mapping on the
Symmetrix port WWN. Make sure this lun value is decimal and not hex.
Z is the lpfc driver instance number that corresponds to the
fcp_bind_WWN_ID lpfcZtX
A sample /kernel/drv/sd.conf file will look like:
Version 5.5
Page 187 of 197
Lab Guide
Setting /etc/system values:

The following configuration values should be added to /etc/system:
sd_max_throttle=20 (applies to both standard SCSI and fibre channel)
set scsi_options = 0x7F8
set sd:sd_io_time = 0x3C (with PowerPath, otherwise set to 0x7F8)
A sample /etc/system
Once all changes have been made, reboot the host to have changes take effect.
Version 5.5
Page 188 of 197
Lab Guide
Appendix 2: Commands
:: M-SERIES (McDATA) COMMANDS ::

M-SERIES Switch Commands
View=
config ip show
Config> ip
(new IP and Subnet mask)
Show> switch
Show> switch
Show > system
Show> nameserver
Show> loginServer
Show> nameServer
Show.Fabric> nodes
Maint > system > setOnlineState
M-SERIES Zoning Commands
Config.Zoning> addWwnMem: <zoneName> <wwn>
Config.Zoning> addZone: add a new zone to the working area
Config.Zoning> activateZoneset: activation of changes
Config.Zoning> showactive: shows actively connected running zoneset
Config.Zoning> clearZone: clear WWNs in a zone
Config.Zoning> deletezone: remove zone from the running config
Config.Zoning> showPending: show pending zones
Config.Zoning> renameZone:<oldzonename><newzonename>
Config.Zoning> deleteWwnMem:<zonename><wwn>
Config.Zoning> renameZoneSet:<zoneSetName>
Version 5.5
Page 189 of 197
Lab Guide
:: MDS-SERIES (CISCO) COMMANDS ::

MDS-SERIES Switch Commands
ip address 191.168.123.234 255.255.255.0
View =
show running-config
show environment shows status of all installed hardware components
show flogi database shows database list of all FLOGI events
show interface brief lists the interfaces and status
MDS-SERIES Zoning Commands
zone name TestZone1 vsan 4
- creates a zone
member fwwn 10:01:10:01:10:ab:cd:ef
zoneset name Zoneset1 vsan 4
- creates a zoneset
zoneset activate name Zoneset1 vsan 4
zone copy active-zoneset full-Zoneset1 vsan 4
copy running-config start-up config copy from source to startup configuration
vsan database go into vsan configuration mode
show zoneset shows all zonesets that are active
show zone vsan <#> - shows all zones active in vsan
show zoneset active displays the active zoneset
show vsan shows the vsans on the switch
Version 5.5
Page 190 of 197
Lab Guide
:: B-SERIES (BROCADE) COMMANDS ::

B-SERIES Switch Commands
switchDisable offline
switchEnable online
ipAddrSet
ipAddrShow
configure change switch parameters
routehelp routing commands
switchShow display switch info
supportShow full detailed switch info
portShow # - display port info
nsShow Name server contents
nsAllShow NS for full fabric
fabricShow fabric information
B-SERIES Zoning Commands
zoneCreate Zone1, 20:00:00:e0:69:40:07:08; 50:06:04:82:b8:90:c1:8d
cfgCreate Test_cfg, Zone1; Zone2
cfgSave saves zoning information across reboots
cfgEnable Test_cfg
zoneShow or cfgShow shows defined and effective zones and configurations
zoneAdd adds a member to a zone
zoneRemove removes a member from a zone
zoneDelete deletes a zone
cfgAdd adds a zone to a zone configuration
cfgRemove removes a zone from a zone configuration
cfgDelete deletes a zone from a zone configuration
cfgClear clears all zoning information/ must disable the effective configuration
cfgDisable disables the effective zone configuration
:: NAVICLI COMMANDS ::
navicli h <SP IP> getsp verify connectivity
navicli h <SP IP> storagegroup list all info about existing groups
navicli h <SP IP> getrg -lunlist list all existing raid groups and LUNS
navicli h <SP IP> getdisk shows numbers of disks in storage array
navicli h <SP IP> getrg <rg id> shows the number of raid groups
navicli h <SP IP> get lun <lun id> - lists all the disks
navicli h <SP IP> storagegroup list displays storage groups
navicli h <SP IP> getcache shows the cache
navicli h <SP IP> storagegroup create gname <name> - creates a new storage group
navicli h <SP IP> storagegroup addhlu gname <name> -hlu <#> -alu <#> - assigns LUNs to
storage group
navicli h <SP IP> storagegroup connecthost host <hname> -gname <gname> - assigns host to
storage group
Version 5.5
Page 191 of 197
Lab Guide
:: POWERPATH COMMANDS ::
powermt manage powerpath environment
powercf configure powerpath devices
emcpreg manage powerpath license registration
emcpupgrade convert powerpath configuration files
:: INQ ::
INQ
Inq h
list options and syntax
Inq hba
list hba wwn
Inq btl
display Bus Target and Lun
Inq show_vol
display Symmetrix Volume Number.
Inq winvol
show Windows filesystems
Inq dev ## page0 Raw unformatted data on a single device
Inq -clariion
display CLARiiON device information
:: SOLUTIONS ENABLER COMMANDS ::
Symcfg Commands
symcfg discover discover the storage environment
symcfg list -list local and remote symmetrixes
symcfg list clariion -list clariions
symcfg -dir all list - To get configuration and status information about all directors
symcfg list v lists whether the Symmetrix director has device masking turned on
symcfg list FA all list lists all fibre directors in a Symmetrix system
symcfg list -dir all -address -sid 6196 - identify the address information for devices
symcfg list -dir all -address -available -sid 6196 -returns the next available LUN address
symcfg list -lockn all - list of visible Symm exclusive locks
symcfg -sid 098712341357 -lockn 15 release - release a lock on a Symmetrix array.
Symconfigure Commands
symconfigure sid <sid> -f <filename> preview checks file to make sure it is ok to exe
symconfigure sid <sid> -f <filename> commit makes the changes from file
symconfigure sid <sid> -f <filename> prepare
Symdev Commands
symdev list -list all devices on symm
symdev sa p list -list devices maped to that one FA
symdev list bcv or rdf1 -list all bcv or rdf1 volumes
symdev list noport
- list devices not mapped to any FE ports
symdev list -clariion
Version 5.5
Page 192 of 197
Lab Guide
:: SOLUTIONS ENABLER COMMANDS :: Continued

Commands to see devices
sympd list lists the Symmetrix devices that the host can see
sympd list vcm lists all the physical device name in the device masking database
syminq
syminq -cid
- list Clariion devices
syminq hba fibre -list HBA
syminq -pdevfile
symdisk
Symmaskdb Commands
symmaskdb list devs lists all devices accessible to an HBA on a specified Symmetrix system
symmaskdb remove removes the meta member devices
symmaskdb restore restores a database from a specified file
symmaskdb backup backs up a database to a specified file
Symmaskdb init - deletes and creates a new VCMDB
Symmask Commands
symmask add devs adds a device to the list of devices that a WWN can access in the database
symmask remove devs removes a device from the list of devices that a WWN can access in the
database
symmask delete deletes all access rights for a WWN in the database
symmask replace allows one HBA to replace another
symmask refresh refresh vcmdb to all FA ports
symmask login lists for each Fibre director which hosts and HBAs are logged in to a Symmetrix
system
symmask list HBAs lists the WWN of the Fibre HBAs on this host
symmask -sid 381 -wwn 50060B000024F9F6 -dir 16C -p 1 set heterogeneous on HP_UX
Other SYMCLI Commands
symdg -creates/deletes/renames device groups
symld - addes & removes devices to a deivce group
symbcv associates/disassociate BCV with device groups
symmir performs (split/establish/restore) BCV mirror commands against device groups
symclone performs (split/establish/restore/activate/terminate/recreate)
symsnap performs (restore/activate/terminate/recreate)
symrdf performs (split/establish/restore/failover/update/failback/suspend/resume) against RDF
device groups
symcg Performs operations on a Symmetrix RDF composite group
symrslv - Displays logical-to-physical mapping information about a logical object that is stored on a disk.
symstat - Displays statistics information about a Symmetrix, any or all directors, a device group, a disk, or
a device.
symioctl - sends I/O control commands to application
Version 5.5
Page 193 of 197
Lab Guide
:: Windows HOST COMMANDS ::

Windows 2003 server SP1 Device Commands
SystemInfo -- Displays detailed configuration information about a computer and its operating system
Shutdown /r /f --forced reboot
Netstat -- Displays active TCP connections, ports on which the computer is listening
mstsc /v: 255.255.255.255 /console --launches a Remote desktop Connection
net use \\ComputerName\ShareName\volume -- Connects a computer to a computer shared resource
Windows 2003 server SP1 LVM Commands

Diskpart rescan -- Locates new disks that may have been added to the computer
Diskpart list disk -- Displays a list of disks and information about them,
Diskpart select disk --Selects the specified disk and shifts the focus to it.
Diskpart detail disk -- Displays the properties of the selected disk and the volumes on that disk.
MountVol -- Creates, deletes, or lists a volume mount point.
Diskpart assign -- Assigns a drive letter or mount point to the volume with focus.
Diskpart extend --Extends the volume with focus into next contiguous unallocated space
Diskpart import -- Imports a foreign disk group into the local computer's disk group
Format /FS:filesystem --Specifies the type of the file system (FAT, FAT32, or NTFS).
FSutil volume dismount
:: Linux HOST COMMANDS ::
Linux Software Installation
rpm -hiv
Linux Device Commands
lsmod
modprobe r
lspci
/usr/sbin/lpfc lun_scan all
Cat /proc/scsi/lpfc/ x (x is the instance number of the HBA)
Linux Filesystem commands
fdisk
e2fsadm
lvcreate
lvremove
lvextend
Version 5.5
Page 194 of 197
Lab Guide
:: AIX/IBM HOST COMMANDS ::

AIX Software Installation
/usr/lpp
Software Directory
lslpp -L all List installed software
lslpp -f fileset
List all files
instfix i
List installed patches
installp
-Install a software package
rmdev
-Remove a device
AIX Device Commands
lscfg lists all comfigured components
smit or smitty system management utility
cfgmgr cofigures devices and optionally installs device software
lscfg v <interface> - lists all attributes (WWNs) for a device
emc_cfgmgr configures symmetrix devices
mkbcv
- makes BCV visable to AIX to avoid locking during boot
(1) chdev -l fcsX -a init_link=pt2pt P To change INIT Link flags parameter
(2) chdev -l fscsiX -a fc_err_recov=fast_fail P Fabric Event Error RECOVERY
Policy
(3) cfgmgr v
AIX Filesystem Commands

lsvg l vgname displays volumes, with a specified volume group
lsdev C
Device Listing
lspv -l hdisk#
Disk Label
lslv
List Logical Volume
mkdev configures a disk device masking sue it is available as a physical volume
mkvg groups one or more physical devices into a volume group
mount mounts a filesystem
Version 5.5
Page 195 of 197
Lab Guide
:: SUN/SOLARIS HOST COMMANDS ::

SOLARIS Software Installation
ptree a
Shows all running processes in a tree format
showrev p
Displays currently installed Solaris patches
prtconf prints system configurations
modinfo displays info about loaded kernel modules
pkginfo lists installed software packages
pkgadd install software packages
pkgrm removes installed software packages
SOLARIS Device Commands
devinfo print device specific information about disk devices
drvconfig generates special device files
uname prints system type, name, kernel, build, patch revision
reboot -- -r reboots system to discover configuration changes
/etc/system system files
/kernel/drv/sd.conf lists of available target ids and luns
/kernel/drc/lpfc.conf - used for persistent binding
/var/adm/messages system messages
SOLARIS Filesystem Commands
Solaris Volume Manager Administration Guide - http://docs.sun.com/app/docs/doc/816-4520
format
Disk partitioning and maintenance program
sysdef
Device Listing
prtvtoc
Disk Label
metadevadm
Checks device ID configuration.
metainit
Configures volumes.
metastat
Displays the status of volumes or hot spare pools.
metaset
Administers disk sets.
newfs v makes a UFS filesystem on disk drive or partition within a diskdrive

zpool create mypool c1t2d0
- ZFS pool creation
Version 5.5
Page 196 of 197
Lab Guide
:: HP/UX HOST COMMANDS ::

HP/UX Software Installation
sysdef analyzes current running system
swlist l bundle displays version and type of HP-UX
swlist -l patch
List installed patches
HP/UX Device Commands
insf e install special device files
ioscan scans system hardware
sam System administration tool
dd if=/dev/cxtxdx of=/dev/zero count=1 makes HP register with a Clariion thru LUNZ device
fcmsutil /dev/td1 List HBA wwn
lsdev C disk list device drivers in the system
mknod makes a directory, special, or ordinary file
/var/adm/syslog.log system log files
/stand/system system configuration file
HP/UX Filesystem commands
vgscan scan physical volumes for LVM volume groups
vgdisplay displays info about LVM volume groups
vgcreate creates a LVM volume group
lvdisplay displays LVM logical volumes
lvcreate creates LVM logical volumes
pvdisplay display info about physical volumes within an LVM volume group
pvcreate creates a physical volume within a LVM volume group
Version 5.5
Page 197 of 197

Host To Storage SAN Implementation - Lab Guide

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Host To Storage SAN Implementation - Lab Guide

Transféré par

Droits d'auteur :

Formats disponibles

Host to Storage SAN

Copyright 2007 EMC Corporation. All Rights Reserved.