Uc434s.c.02 Lab PDF

Accelerated SAN Essentials
UC434S C.02
Lab guide
Use of this material to deliver training without prior written permission from HP is prohibited.
UC434S C.02
Lab guide
Use of this material to deliver training without prior written permission from HP is prohibited.
 Copyright 2009 Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice. The only warranties for HP
products and services are set forth in the express warranty statements accompanying such products
and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
This is an HP copyrighted work that may not be reproduced without the written permission of HP.
You may not use these materials to deliver training to any person outside of your organization
without the written permission of HP.
Microsoft®, Windows®, Windows® XP, and Windows Vista™ are U.S. registered trademarks of
Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
Export Compliance Agreement

Export Requirements. You may not export or re-export products subject to this agreement in violation
of any applicable laws or regulations.
Without limiting the generality of the foregoing, products subject to this agreement may not be
exported, re-exported, otherwise transferred to or within (or to a national or resident of) countries
under U.S. economic embargo and/or sanction including the following countries:
Cuba, Iran, North Korea, Sudan and Syria.
This list is subject to change.
In addition, products subject to this agreement may not be exported, re-exported, or otherwise
transferred to persons or entities listed on the U.S. Department of Commerce Denied Persons List;
U.S. Department of Commerce Entity List (15 CFR 744, Supplement 4); U.S. Treasury Department
Designated/Blocked Nationals exclusion list; or U.S. State Department Debarred Parties List; or to
parties directly or indirectly involved in the development or production of nuclear, chemical, or
biological weapons, missiles, rocket systems, or unmanned air vehicles as specified in the U.S.
Export Administration Regulations (15 CFR 744); or to parties directly or indirectly involved in the
financing, commission or support of terrorist activities.
By accepting this agreement you confirm that you are not located in (or a national or resident of)
any country under U.S. embargo or sanction; not identified on any U.S. Department of Commerce
Denied Persons List, Entity List, US State Department Debarred Parties List or Treasury Department
Designated Nationals exclusion list; not directly or indirectly involved in the development or
production of nuclear, chemical, biological weapons, missiles, rocket systems, or unmanned air
vehicles as specified in the U.S. Export Administration Regulations (15 CFR 744), and not directly
or indirectly involved in the financing, commission or support of terrorist activities.
Printed in USA
Lab guide
March 2009
Fabric Documentation
Module 1 — Lab 1
Objective
After completing this lab, you will have sufficient documentation to allow you to
reference your connected SAN hosts, targets and fabric switches.
Requirements
Before beginning this lab, it is assumed that:
You have SAN hosts, disk targets and switches to document.
You may not complete this lab entirely before continuing to the next module.
However you should make every effort to return to it when ‘missing’ information
becomes available to you.
UC434S C.02 © 2009 Hewlett-Packard Development Company, L.P. L1 - 1

Fabric documentation
One of the most important aspects in SAN support is clear and current
documentation of the environment. In this exercise you will complete a ‘cut-down’
version of the documentation required for a production SAN. Documentation should
be considered an ‘organic’ entity – continually evolving and updating. Remember –
in a ‘support’ situation your documentation will assist you and your support co-
workers problem solve more efficiently and effectively.
Topology diagram
L1 - 2 © 2009 Hewlett-Packard Development Company, L.P. UC434S C.02

Host documentation
Example Host Name BL20-362 BL20-363
IP address 1 192.168.136.212 192.168.136.213
IP address 2
ILO/MP IP 192.168.136.220 192.168.136.221

HBA 0 Node WWN 20:00:00:00:c9:4d:33:9c 20:00:00:00:c9:4d:24:dc
Port WWN 10:00:00:00:c9:4d:33:9c 10:00:00:00:c9:4d:24:dc
HBA 1 Node WWN 20:00:00:00:c9:4d:33:9d 20:00:00:00:c9:4d:24:dd
Port WWN 10:00:00:00:c9:4d:33:9d 10:00:00:00:c9:4d:24:dd
Fabric A Switch name EdgeA1 EdgeA1
Domain,Port 2,4 2,5
AD member None None
Zone member BL20-362Zone BL20-363Zone, BackupZone
Fabric B Switch name EdgeB1 EdgeB1
Domain,Port 5,4 5,5
AD member AD1 AD1
Zone member BL20-362Zone BL20-363Zone, BackupZone
In the above example the fields have been completed for two host systems connected
to two fabric switches. Zoning and Admin Domain information has been included
along with switch name and domain ID & port information.
1. Use the tables in the following pages to document similar details for your
SAN hosts. You may need to return to this document later in the class to
complete all the data fields.

Host Documentation
Host Name
IP address 1
IP address 2
ILO/MP IP
HBA 0 Node WWN
Port WWN
HBA 1 Node WWN
Port WWN
Fabric A Switch name
Domain,Port
AD member
Zone member
Fabric B Switch name
Domain,Port
AD member
Zone member
Host Documentation
Host Name
IP address 1
IP address 2
ILO/MP IP
HBA 0 Node WWN
Port WWN
HBA 1 Node WWN
Port WWN
Domain,Port
AD member
Zone member
Domain,Port
AD member
Zone member
Host Documentation
Host Name
IP address 1
IP address 2
ILO/MP IP
HBA 0 Node WWN
Port WWN
HBA 1 Node WWN
Port WWN
Domain,Port
AD member
Zone member
Domain,Port
AD member
Zone member
Host Documentation
Host Name
IP address 1
IP address 2
ILO/MP IP
HBA 0 Node WWN
Port WWN
HBA 1 Node WWN
Port WWN
Domain,Port
AD member
Zone member
Domain,Port
AD member
Zone member
Array documentation
Array Documentation
Array name MSA1500 CS SGA050502F

Firmware 7.00 FC Port Speed 2Gb/s
Node WWN 50:05:08:b3:00:90:f2:80
PortWWN 50:05:08:b3:00:90:f2:81
PortWWN 50:05:08:b3:00:90:f2:89
PortWWN
PortWWN
Management host name/IP BL20-362
LUN name/No. Capacity RAID level Presented to (host) No. Paths
Logical drive 1 12GB 1+0 BL20-363 2
Logical drive 2 8GB RAID5 BL20-363 2
In the above example the fields have been completed for a single disk array. You
may not be able to complete the entire form immediately but bear it in mind while
you progress through SAN discovery and lab exercises during this class.
1. Complete the following array documentation forms for the array(s) in your
fabric. As you create additional (or remove) logical drives during your class,
remember to add/remove them to the list.

Array Documentation
Array name
Firmware FC Port Speed
Node WWN
PortWWN
PortWWN
PortWWN
PortWWN
Management host name/IP

Array Documentation
Array name
Firmware FC Port Speed
Node WWN
PortWWN
PortWWN
PortWWN
PortWWN
Management host name/IP

Switch documentation
Switch name EdgeA1 Domain ID 2
IP address 192.168.136.28 F/W version 6.1.0c
Switch WWN 10:00:00:05:1e:03:62:57
Serial number USB640W819 Role Subordinate
Active zone set mastercfg
Switch port detail
# Speed Port type Device WWPN
0 N4 E port 10:00:00:05:1e:03:ab:d8
1 N4 E port Trunk port, master 0
2 N4 E port 10:00:00:05:1e:03:5c:b6
3 N4 E port Trunk port, master 2
4 N2 F port 10:00:00:00:c9:4d:33:9d
5 N2 F port 10:00:00:00:c9:4d:24:dd
6 N2 F port 50:06:0b:00:00:29:e5:aa
7 N2 F port 50:05:08:b3:00:90:f2:81
8
9
10
11
12
13
14
15
In the above example the fields have been completed for a single fabric switch. You
may not be able to complete the entire form immediately but bear it in mind while
you progress through SAN discovery during this class.
2. Complete the following switch documentation forms for the switches in your
fabric. Additional forms have been included to capture the details of ALL
fabric switches in your environment.

Fabric Switch Documentation
Switch name Domain ID

IP address F/W version
Switch WWN
Serial number Role
Active zone set
Switch port detail
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15


Switch WWN
Serial number Role
Active zone set
Switch port detail
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15


Switch WWN
Serial number Role
Active zone set
Switch port detail
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15


Switch WWN
Serial number Role
Active zone set
Switch port detail
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15


Switch WWN
Serial number Role
Active zone set
Switch port detail
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15


Switch WWN
Serial number Role
Active zone set
Switch port detail
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
You have successfully completed this lab.


Brocade switch exploration
Module 3 — Lab 1
Objectives
After completing this lab, students will be able to:
Connect to a fabric switch using Web Tools and the CLI
Verify the status of the switch by using specific commands
Requirements
To complete this lab, you need:
A HP B-Series fabric switch with firmware version 6.1.x or later
A client (server or workstation) with Telnet
Network connectivity between the client workstation and the fabric switches
The IP addresses of the fabric switches
The login name and password of the admin account for the switches
UC434S C.02 © 2009 Hewlett-Packard Development Company, L.P. L3.1 – 1

Connecting to a fabric switch

Using Web Tools
Logging into the fabric switch using Web Tools
Web Tools is a graphical user interface (GUI) that enables administrators to monitor
and manage single or small fabrics, switches, and ports from a standard
workstation. It is an optionally licensed product that runs on the Brocade Fabric OS.
Note
Java 1.6 (minimum) must be installed on the workstation that you will use to
connect to the Web Tools interface.
1. From your Windows workstation or server, launch the web browser. In the
Address field, enter the IP address of the switch:
http://<IPaddress>
Note
Web Tools also supports the HTTPS protocol, if that protocol is enabled for the
switch.
After your workstation downloads some Java files from the switch you should
enter your login credentials at the Upfront Login prompt:
When the Web Tools windows launches you may see an Internet Explorer page
behind the user interface. This browser window is now of no use to you so you
may ignore it or close it down. Doing so will not affect your management
interface.
L3.1 – 2 © 2009 Hewlett-Packard Development Company, L.P. UC434S C.02

The Web Tools interface will launch:
Web Tools
Note
If you are using the HP Virtual Lab you should hover your mouse pointer over the
switch that you wish to manage, displaying a context menu. Hover over ‘Web
Interface’ and you will see the display change to show the username:password.
Click to launch Web Tools.
You may see the Switch Events pane instead of the Switch Information pane pictured
above.

The Switch Explorer View is the first web page that displays when you connect to a
switch. The Switch Explorer includes:
Fabric Tree — Displays a navigation menu of icons for all switches in the
fabric.
Manage — Provides easy access to fabric-level administration tasks.
Monitor – Access to Name Server and other monitoring tools
Switch View — Display real-time information about the selected switch.
Switch Information page — Displays a synopsis of useful information about the
selected switch.
Port Status information — Displays real-time information about the port
including status lights, and in-use lights.

Tasks Pane
The Fabric Tree displays a list of all the switches in the fabric. When you select a
switch from this view it is displayed in the Switch View. You can display switches in
the Fabric Tree list by Name, IP address, or worldwide name (WWN).

Switch graphic
The Switch View graphic is an interactive display of the particular switch you have
selected from the Fabric Tree. The Web Tools interface replicates in real-time the
switch you have selected. The displays in Web Tools correspond to the front of the
actual switch and its various switch and port LEDs.
Ports that are in use are displayed as well as unused ports. You can click a port in
this window to open a dialog box that displays information about that port. If you
only wish to see detail of a specific port then you can right click the port to enter a
context-sensitive menu:

Port status and statistics

To view port status information, throughput statistics and sfp data you should double-
click the port that you are interested in and the Port Administration window will
appear:
The Port Administration window has a ‘Basic’ and ‘Advanced’ mode. These modes
not only allow more/less configuration options, they also operate to display
more/less context data within each selected option. For example, the additional
information displayed for SFP in Advanced mode:

What is the SFP wavelength of the port that you are interrogating? (this information
can be found in the advanced section of the ‘SFP’ tab – you will need to use ‘Show
Advanced Mode’ to access it)
_______________________________________________________________________
What do you think that the units are?
_______________________________________________________________________
Switch Admin window
Click the Switch Admin link in the Manage section of the Tasks pane to access the
switch administration functions. The tabs in the resulting window may be license
dependant. For example:
Switch parameter configuration
Network configuration
User management
Routing options
Firmware Download
License and feature management

Performance Monitor
Use the Performance Monitor button to graphically display throughput (megabytes

per second) for each port and for the entire switch.

Fabric Events
Where the Switch Events tab provides a running log of events for your switch, the
Fabric Events window shows fabric-wide events. Both may be filtered using the ‘Filter’
option. Both are searchable and may be sorted by field/column.

Accessing the switch using the Telnet

Use the Telnet button from the Switch View to access the switch using Telnet. You must
have administrative privileges to access the Telnet option. Telnet must also be
enabled for your switch.exit
1. Launch Web Tools.

2. From the Fabric Tree, select the desired switch. The Switch View displays.
3. Click the ‘Telnet/SSH Client’ link within the Tasks pane or select it from the Tools
menu.
4. You will be presented with the following dialog box:
5. You may enter a path to your preferred Telnet or SSH client on the local machine
or click OK. You will need to OK the following error message to launch the
local machine default Telnet client if you have not indicated an alternative path.
6. Enter a username and password.

7. Enter the exit command to close the Telnet session. You will be returning to the
command line interface later in this lab exercise.

Fabric Summary
The Fabric Summary view summarizes the physical configuration of the fabric from
the perspective of the “local domain” (the domain of the switch currently being
displayed in the Switch View). The Fabric Topology includes information about the
“destination domains” (all other domains in the fabric) and the paths between each
destination domain and the local domain.
Note
You may not see more than one domain if your switch is isolated

Name Server
The Name Server Table View provides the name server entries listed in the Simple
Name Server database. This includes all name server entries for the fabric, not only
those that are situated in the local domain. Each row in the table represents a N-Port
connection to the fabric. E-Ports are not listed in the Name Server.

Zone Administration
A Zoning license and administrative privileges are required to access the Zone
Administration view. If a switch or device is added or removed from the network, it is
necessary to save the changes and re-launch the Zone Administration view for the
changes to take effect. You will return to Zoning in a later lab exercise.

Logging into a fabric switch using Telnet

To perform the initial login into a fabric switch:
1. Open a Telnet connection to one of the fabric switches from your Windows
workstation or open a Telnet session from your HP-UX server. The IP addresses of
the switches should have been provided to you. Consult your instructor to obtain
the IP addresses of the switches if they have not already been provided for you.
Note
If you are using the hpvl then you will see a Telnet link on your lab group
home page when you hover your mouse pointer over your switch.
From a command prompt, enter:

# Telnet <IP address>
The login prompt is displayed if the Telnet connection successfully found the
switch on the network.
2. Enter the user ID admin at the login prompt. Press Enter.
3. Enter the admin password. Press Enter.
4. Verify that the login was successful. A prompt is displayed showing the switch
name and user ID to which you are logged on with.
You are now logged on to the switch.

Basic switch commands

You can view information about the switch and port status.
As you saw in a previous exercise, the Switch Explorer in Web Tools displays basic
switch information, such as name, status, Fabric OS version, domain ID, IP address,
WWN, and current zone configuration. To display information about the switch and
port status using the CLI:
1. Using a Telnet connection, enter the switchshow command at the command
line. This command displays a switch summary and a port summary.
The following example displays the switchshow command.
Record the information provided by the switchshow command.

2. What is the switch role?

.................................................................................................................
3. What is the switch Domain ID?
.................................................................................................................
4. Are there any active zoning configurations?
.................................................................................................................

Viewing port status

This command displays port status information.
1. Using a Telnet connection, enter the portshow command at the command line.
This command displays a summary of a specified port.
switch:admin>portshow 4
2. What is the WWN of the device connected to this port?

.................................................................................................................
3. The same information can be viewed using Web Tools. Return to your Web
Tools session. From the main page, in the top left pane, click the graphical
representation of port 4. Leave the current window open.

Switch enable/disable procedures

The following section describes how to disable and enable a switch.
Disabling and enabling a switch

To disable a switch:
1. From the Web Tools interface click the Switch Admin link within Tasks or choose
Switch Admin from the Manage menu.
2. The default tab shown is the Switch tab. From this tab, in the Switch Status
section, change the radio button to Disable. Click Apply.
All Fibre Channel ports on the switch are taken offline. If the switch was part of a
fabric, the fabric reconfigures.
The switch must be disabled before making configuration changes (using
configure or configDefault) or before running many diagnostic tests. All
commands that require the switch to be disabled send an error if invoked while
the switch is enabled.
The switch does not need to be disabled before rebooting or powering off.
As each port is disabled, the front panel LED changes to a slow flashing yellow.
3. In the Switch Status section, change the radio button to Enable. Click Apply.
All Fibre Channel ports that passed the POST test are enabled. If the switch was
part of a fabric, it rejoins the fabric.
As each port is enabled, the front panel LED changes to green for online ports,
black for disconnected ports, or yellow for uninitialized ports.
4. Leave the current window open.

Disabling/enabling a port
To disable a port, follow these steps:
1. From the Switch View image of the switch in Web Tools, right click the port that
you wish to interrogate and select Port Admin from the resulting menu.
Ports in the Port Administration window appear listed in the FC Ports Explorer
pane to the left. When the General tab is selected in the body of the window
control buttons are visible. Port online options include Enable, Disable, Persistent
Enable and Persistent Disable. Functions not available appear greyed.
2. To disable a specific port, select the appropriate port in the FC Ports Explorer
pane and click the ‘Disable’ button in the window main body. Click Yes when
asked to confirm.
If the port is connected to another switch, the fabric may reconfigure. If the port
is connected to a port in a Node, that port will no longer be available to the
fabric.
The front panel LED of a disabled port flashes yellow with a two second cycle.
3. Leave the Web Tools session open.
4. Using a Telnet session, enter the portdisable command using the following
syntax:
switch:admin>portdisable portnumber
Specify the port number that you want to disable.

5. Verify that the port has been disabled using switchshow:
switch:admin>switchshow
6. Further verify that the port is disabled by using portshow:

switch:admin>portshow portnumber
Notice that the ‘portState’ value shows ‘Offline’.
To enable a port, follow these steps:

7. From Telnet, enter the portenable command at the command line, using the
following syntax:
switch:admin>portenable portnumber
If the port is connected to another switch, the fabric may reconfigure. If the port
is connected to one or more devices, these devices become available to the
fabric.
The front panel LED of an enabled and online port is green.
8. Verify that the port has been enabled using switchshow:
switch:admin>switchshow

9. Return to the Prot Administration window and select the port that you disabled
previously and click ‘Enable’ in the main body of the window. Click Yes when
asked to confirm.
10. Close the window to complete this task.

Setting the switch Domain ID

The Domain ID, as it applies to B-Series switches, is a unique number between 1 and
239 that identifies the switch to others in the fabric.
To configure the Domain ID:
1. Using Web Tools, from the Switch Admin window, click the Switch tab (visible in
both Basic and Advanced modes). Notice that the Domain ID field is grayed
out. The switch must be disabled to configure the Domain ID.
2. In the Switch Status section, select the Disable radio button. Click Apply and
then click Yes to confirm.
3. Enter a unique number between 1 and 239. Click Apply → Yes.
4. Enable the switch. Click Apply → Yes
5. You may verify that the Domain ID has changed by using the switchShow
command at the command prompt.

Backing up system configuration settings

Important
! HP strongly recommends saving the configuration after the initial configuration
changes and periodically thereafter.
To back up the system configuration, you must use:

FTP when connecting to Windows or UNIX machines
Use these steps to upload a backup copy of the configuration settings to a host
computer using Web Tools:
You may need to install IIS and the ftp service if you wish to use your Windows host
to perform this task. Instructions are given on the following page.
1. Using Web Tools, from the Switch Admin window of your first switch, click the
Configure tab. If you do not see the Configure tab then you may need to switch
to Advanced mode.
2. Click the Upload/Download sub-tab.
3. Click the Config Upload to Host radio button.
4. Enter the user name, password, file name (e.g. config.txt) and host IP
information. Click Apply.
You can monitor the progress by looking at the Upload/Download Progress bar
on the Upload/Download sub-tab.

Using CLI to back up your configuration

You can also use the command line interface (CLI) to back up your configuration. Use
these steps to upload a backup copy of the configuration settings to a host computer
using CLI:
1. Your instructor will provide you with the host location of where the FTP service is
running. The instructor will also provide you with a user name and password.
NOTE Your HP-UX host is running the ftp daemon already. If you feel comfortable
doing so then you may use the unix host for this upload.
If you wish to use the Windows host for this task then you may need to install
the ftp service using the following steps:
• Navigate to ‘Add/Remove Programs’ and select the ‘Add/Remove
windows components’ button to the left of the window.
• In the ‘Windows component wizard’ double click the ‘application
server’ item. In the dialog box that opens double click the
‘Internet Information Services (IIS)’ item. Then check the tick box
for ‘File Transfer Protocol (FTP) Service’ (you will see other boxes
will be auto-selected also).
• Click ‘OK’ twice and then choose ‘Next’ to install the chosen
items.
• During the install you may be prompted to provide the location of
an i386 directory. If you are using the hpvl then you will find it at:
C:\i386 or your instructor will be able to give you its location.
• Click ‘Finish’ and close any open windows when the installation is
complete.
N.B. You will need to change the default permissions for the FTP site to
allow write access.
2. Connect to your switch if you are not already. At the command line enter the
following command:
# configupload
3. When prompted, provide the IP address, the user name, file name, protocol,
and password.
4. The following graphic shows an example of the configuration file generated

when viewed in WordPad..

You have completed this lab


Cisco switch management – simulation
Module 3 — Lab 2
Objectives
After completing this lab students will be able to:
Install Fabric Manager and Device Manager
Configure a VSAN
Configure Port Channels
Configure Zoning
Upgrade switch firmware
Requirements
To complete this lab you need:
A Windows host system
Cisco Simulation installation files (your instructor will provide these for you or
show you where to obtain them)

Installation and operation of the simulator

1. Double click ‘setup.exe’ and follow the instructions on the screen. Accept all
defaults.
2. When installed double click the icon on your desktop to launch the simulator.
You may work through all five of the labs sequentially. Don’t forget that you
can review the objectives of each lab by selecting ‘Lab Guide PDF’ from the
‘Help’ menu.
The rest of this lab will be completed WITHIN the simulation

Windows HBA information and configuration
Module 4 — Lab 1a
Objectives
View HBA information for your Windows host
Use the Emulex HBAnywhere utility
Requirements
A Windows host system with Emulex HBAs or a blade with Emulex mezzanine
cards
Fibre Channel switch to connect them to
Emulex software installation files (your instructor can provide these for you)
UC434S C.02 © 2009 Hewlett-Packard Development Company, L.P. L4.1a – 1

HBA information from ProLiant System Management homepage

1. Launch the web browser on your SAN connected Windows server and type
the following URL: https://localhost:2381 or use the link to the System
Management homepage in the Start menu.
2. Once you have logged in to the homepage using the administrator account
select the ‘External Storage Connections’ link in the ‘Storage’ section at the
bottom centre of the page.
Note now how externally

connected systems (MSA1500’s
in this case) appear. Not all
SAN attached arrays are visible
in this section.
3. You will see something like the following:
L4.1a – 2 © 2009 Hewlett-Packard Development Company, L.P. UC434S C.02

Document the I/O slot, Node Wide Name and the Port World Wide Name for
each Host Bus Adaptor below:
I/O
slot:_______________________________________________________________
Node World Wide
Name__________________________________________________
Port World Wide
Name___________________________________________________
I/O
slot:_______________________________________________________________
Node World Wide
Name__________________________________________________
Port World Wide
Name___________________________________________________
You will need this information later so make sure that you record it accurately.
You can close the System Management Homepage now.
Installation and use of Emulex HBAnywhere

1. Double click the ‘cpqsetup.exe’ file in the HBAnywhere folder. If you are
using the hpvl then you will find it at: Z:\hba\HBAnywhere\
(your instructor will direct you to it if you cannot find it).
2. Click install on the dialog box – there are no selections to be made and,
once the software has installed click ‘Close’ to close the installation summary
window.
3. From the Start Menu choose ‘Programs’, ‘Emulex’ and then click
‘HBAnywhere’ (for those of you who are familiar with ‘lputilnt’ you will see
this here also).

HBAnywhere will discover other Emulex HBAs in your fabric zone. To avoid
confusion or mis-management you can configure HBAnywhere to only display
local HBAs by choosing that option in the ‘View’ menu.

4. View the entry for your local HBAs. You will see the part number followed by
a World Wide Name. Is this the Port or Node WWN?
______________________________________________________________________
5. Select an entry and view the changes to the content pane:
These are the main tabs for configuring your HBA and gaining feedback on
what it has discovered in the fabric.
6. Select the ‘Port Attributes’ tab. Which Class(es) of Service does the port
support?
______________________________________________________________________

7. Select the ‘Target Mapping’ tab. Document the information that you see:
WWPN WWNN D_ID SCSI ID
This information will assist you later so ensure that you document it accurately.
Note that these Mappings are Automatically updated – you may disable this
Automapping function or change the bind type at a later stage.
8. Are there any Persistent Bindings active?
_________________________________
When are persistent bindings most likely to be used?
______________________________________________________________________
9. Review the ‘Driver Parameters’ tab. Scroll down to the bottom of the list of
parameters and record the value and description for the ‘Topology’ entry: (it
will help if you click it once to select it in the list)
______________________________________________________________________

HBA driver update

Use your Windows Computer Management console to check the driver version for
your Emulex HBA:
1. To update the driver installed on your system you will need the latest driver
installation file from HP. If you are using the hpvl then you find driver files at:
Z:\hba\Emulex driver\. Your instructor will be able to help you locate this
file if you cannot find it.
2. Double click the driver installation file (cp006500.exe) and then choose
‘Install’ to commence installation.
3. Reboot when the installation is complete.
4. Verify the new driver version when your system has rebooted.


Installing and using the SANsurfer utility for
QLOGIC HBAs in Windows 2003
Module 4 — Lab 1b
Objectives
After completing this lab, you should be able to:
Install the qlogic SANsurfer utility
Access the graphical interface
Inspect and modify the default HBA settings
Create a persistent binding to a remote target.
Requirements
This lab supplements the existing Emulex HBA lab and should be followed in
the event that you have a host with a qlogic Host Bus Adaptor.
UC434S C.02 © 2009 Hewlett-Packard Development Company, L.P. L4.1b – 1

Installing the SANsurfer HBA configuration utility

You may skip this section of the lab if SANsurfer is already installed.
Installation
1. Locate and double click the SANsurfer installation file:
sansurferxxxxxxxxx_windows_install.exe.
2. If the firewall requests that you confirm the ‘run’ command then do so
and follow the first steps by clicking ‘Next’.
3. Select the ‘SANsurfer FC HBA Manager’ option indicated above (you

will only need this selection for the following lab) and then choose
‘Next’.
4. The next installation step will prompt you to select the installation path –
accept the default and choose ‘Next’.
L4.1b – 2 © 2009 Hewlett-Packard Development Company, L.P. UC434S C.02

Installing and using the SANsurfer utility for QLOGIC HBAs in Windows 2003
5. Install the application shortcuts in the ‘Current Users Profile’ and click
‘Next’.
6. Choose ‘Next’ again at the next step to accept the creation of the
Desktop Icon and then click ‘Install’ at the summary screen.
7. Do NOT select the tick box shown above. Doing so will enable the
Qlogic failover configuration – you do not want this. Choose ‘Next’.

8. Click ‘Done’ at the final screen and you will have successfully installed
the utility.
Login and Management
In order to begin HBA management you first need to ‘Connect’ and select
“localhost” or your desired alternative hostname from the list.
Select ‘localhost’ and click ‘Connect’

In the navigation pane to the left of the window you should see the HBA
ports for the host that you have connected to and, upon selection of one of
those ports, to the right you should see port properties (see diagram on next
page)
Select one of the ports in the navigation pane and then click the
‘Information’ tab to display some of the port properties. What is the Port
Name (WWN) of this port?
______________________________________________________________
What is the Port ID? _____________________________________________
What is the Actual Connection Mode? _______________________________

What is the Actual Data Rate?______________________________________
Port and target status icons

Icon indicates failed port or
connection down
Icon indicates LUN or target
device offline
Icon indicates LUN or target
device online
Select either ‘Port0’ or ‘Port1’ in the navigation pane and click the ‘Device
List’ tab, the image below shows an example:


How do the entries in the ‘Port ID’ column relate to your zoning if it’s
enabled on the FC switch?
__________________________________________________________________
__________________________________________________________________
__________________________________________________________________
Which service in the fabric (i.e. on the FC switch) can help you to relate the
24 bit fabric address (or ‘Port ID’) to the Port WWN a node?
__________________________________________________________________
Select either ‘Port0’ or ‘Port1’ in the navigation pane and click the ‘Statistics’
tab.
You will see a statistics chart for your HBA port similar to the one shown
below:
Check the ‘Auto Poll’ box in the bottom right corner of the window and then
click the button. The following dialogue box should appear:

Type ‘10’ in the ‘Sampling Rate’ box and

click ‘OK’
You should now find that the ‘Update’ button is greyed out and the chart
will automatically refresh.
Select either ‘Port0’ or ‘Port1’ in the navigation pane and click the ‘Settings’
tab.
Click the ‘Connection Options’ drop-down list. What options are
displayed?
__________________________________________________________________
__________________________________________________________________
__________________________________________________________________
__________________________________________________________________
Under what circumstances would you want to check the ‘Enable HBA Port
BIOS’ box?
__________________________________________________________________
__________________________________________________________________
__________________________________________________________________
Select either ‘Port0’ or ‘Port1’ in the navigation pane and click the ‘Link
Status’ tab.
The content page shows each visible (i.e. within the HBA port’s zone)
storage port WWN.
List the column headings on this page:
1. ____________________________________________________________
2. ____________________________________________________________
3. ____________________________________________________________
4. ____________________________________________________________
5. ____________________________________________________________
You have now finished this lab.
HP-UX HBA information and configuration
Module 4 — Lab 2
Objectives
View HBA information for your HP-UX host
Requirements
A HP-UX host system with Agilent HBAs
Fibre Channel switch to connect them to

HBA information
FCMSUTIL
The fcmsutil command is a diagnostic tool to be used for the TACHYON TL A5158A
and TACHYON XL2 A6795A Fibre Channel Host Bus Adapters. This command
provides the ability to perform Fibre Channel Test and Echo functionality, read the
card's registers, etc. This command requires the use of a device file to indicate the
interface over which the requested command needs to be performed.
You will first need to determine how many HBAs are in your system and what type
thy are.
1. To do this use the ioscan command in the following format
Ioscan –fnCfc
You will see output resembling that below:
# ioscan –fnCfc
2. Now that you know the device file names of your HBAs you can run the
fcmsutil command thus:

3. Run the command for both (or all) of your HBAs and document their Node
World Wide Name and Port World Wide Name below
/dev/fcd0
WWNN_________________________________________________________________
_
WWPN__________________________________________________________________
/dev/fcd1
WWNN_________________________________________________________________
_
WWPN__________________________________________________________________
You will need this information later so ensure that you document it accurately
4. Document also the speed of connection for each HBA port and it’s topology
/dev/fcd0
Link speed_______________________________________________________
Topology________________________________________________________________
Given the ‘Topology’, is it an ‘N’ or an ‘NL’ port? __________________
/dev/fcd1
Link speed_______________________________________________________
Topology________________________________________________________________
Given the ‘Topology’, is it an ‘N’ or an ‘NL’ port? __________________
5. Run the following command to query the Name Server:

fcmsutil /dev/fcdx ns_query_ports (where x corresponds to
the HBA device file)

Record your results below:
/dev/fcd0 /dev/fcd1
10

6. Use the ‘get remote all’ switch (e.g. fcmsutil /dev/fcdX get remote all) to
gather information on remote disk targets. [For more information about the
other switches and options for this command type: fcmsutil]
Example output:
Record the Target Port World Wide Name and the Target Node World Wide
Name values for each target device that you can see:
Target 1
WWNN_________________________________________________________________
WWPN__________________________________________________________________
Target 2
WWNN_________________________________________________________________
WWPN__________________________________________________________________
Target 3 (if you can see one)
WWNN_________________________________________________________________
WWPN__________________________________________________________________

How might this information help you when you configure your zoning?
_________________________________________________________________________
_________________________________________________________________________
_________________________________________________________________________
_________________________________________________________________________

Windows HBA information using fcinfo
Module 4 — Lab 3
Objectives
View HBA information for your Microsoft Windows host using fcinfo.
Requirements
A Windows 2003 Server host system with Fibre Channel HBAs installed.
Fibre Channel switch to connect your host to.

HBA information - FCINFO

FCINFO is a tool for gathering configuration information on your Fibre Channel SAN
based on the SNIA HBAAPI for management of Fibre Channel Host Bus Adapters
and discovery of SAN resources.
If fcinfo is not installed on your host system you must install it first. If you are using
the HPVL then you will find the file fcinfo_x86.zip on the network drive (Z:\). Ask
your instructor if you are not sure where to find the installation file.
1. Extract this archive to your local machine (C:\YourFolderName) and navigate

to the folder you created. You will see a file called fcinfo_x86.msi which you
should double click to begin the install process.
2. Accept the terms of the license agreement and click ‘Install’.
3. Click ‘Finish’ when the installer has finished.
To use fcinfo you need to run cmd.exe first.
1. Open a Command Prompt window and type fcinfo.
2. To access more detailed information use:

fcinfo /details

3. Run the fcinfo /details command and document the Node World
Wide Name and Port World Wide Name for both HBAs below
adapter index 0 (ai:0)

WWNN_________________________________________________________________
_
WWPN__________________________________________________________________
adapter index 1 (ai:1)

WWNN_________________________________________________________________
_
WWPN__________________________________________________________________
You will need this information later so be sure to document it accurately.
4. Run the following command to return a list of visible ports:

fcinfo /ports (/details optional)
How do you think that this information might differ when you have implemented
zoning?
_________________________________________________________________________
_________________________________________________________________________
_________________________________________________________________________
_________________________________________________________________________

Now that you have established that your HBA port can communicate with other ports
in the fabric, use the command fcinfo /mapping to view any LUNs that are
presented to your host.
5. Type fcinfo /mapping /ai: followed by the adapter index (usually 0 or
1). e.g. fcinfo /mapping /ai:1

6. Use the /top switch to query the name server database within the fabric.
Spend some time reviewing the output, there is a formidable amount of useful
data here. Effectively this command displays the nameserver content of each
switch in BOTH of your fabrics.
7. How might Zoning in the fabric affect this output?
_________________________________________________________________________
_________________________________________________________________________
_________________________________________________________________________
_________________________________________________________________________
Try to remember to test the effect of Zoning on this output when you have completed
your fabric zoning lab.


MSA configuration with ACU —
Windows 2003
Module 5 — Lab 1
Objectives
Configure the MSA1000 and MSA1500cs using Array Configuration
Utility (ACU) to create arrays and logical drives with the required
redundancy.
Implement LUN masking on the MSA
Configure the drives under Windows and test Selective Storage
Presentation.
Prerequisites
Requires:
A SAN connected Windows server
An SAN connected HP-UX server (optional)
An unconfigured MSA1000 or MSA1500cs with at least four hard
drives and one controller
ACU version 7.0 or later installed. The ACU component is available
from the HP storage website or with the CD supplied with the controller.

Procedure
ACU—Navigation
1. Complete the table below with the information you have gathered from
host HBA labs. You will need it when configuring Selective Storage
Presentation.
Server Name World Wide ID (HBA)
2. Launch the ACU. Click Start → All programs → HP System Tools →

Array Configuration Utility.
3. Select whether or not you would like to enable remote access. If asked
choose local mode. If you are not presented with this choice the ACU
has defaulted to local mode.

MSA configuration with ACU — Windows 2003
On the left side of the screen, select the MSA1500 controller that you wish
to configure.
Each time you run the ACU, it analyzes the configuration of the array
controllers installed in the system. From the Main page, you have
various options to change or reconfigure your controller.
• Express Configuration
Select Express Configuration to be asked a few simple questions
and allow the controller to be configured automatically.
• Configuration Wizards
Select Configuration Wizards to configure your controller through
a series of wizards, which will guide you through the process.

Before you continue take a moment to investigate the ‘More Information’ link
that you will see when you have an array selected:
You can see highlighted above a controller World Wide Name. Use your
knowledge of switch interrogation to determine if this is the controller Node
World Wide Name or it’s Port World Wide Name. Make a note of your
World Wide Name below:
__________________________________________________________________

Creating an Array and Logical Drives

1. Select Configuration Wizards.
2. Assuming that the controller is not configured, you will be prompted to
create an array. Select Create an Array.
3. Select Begin.
4. You are asked to select the physical drives that you want to use in the
array. Select Select All. Click Next.
5. You have configured an array. Click Finish.

6. The configuration view now shows an array called Array A. To

configure logical drives for the array, select Create a logical drive →
Begin → Next.

7. Record the RAID levels that are supported by this controller.

....................................................................................................
....................................................................................................
....................................................................................................
....................................................................................................
8. Complete the Wizard to achieve the following configuration:

Create two logical drives (ignore any unused space) and accept all
defaults:
Logical drive 1—12GB, RAID 5, default stripe size
Logical drive 2—8GB, RAID 1+0, default stripe size
If necessary begin the Wizard again to create the second Logical drive.
N.B. If you are sharing an array with your lab partner but have your own
Windows host then create four drives so that you may have two each.

You are presented with a summary of the configuration. You must now save
the configuration. Click the Save button and, if you can see the controller,
observe the LCD on controller 1 (right side).
9. You will be returned to the main configuration wizards screen.

10. Choose exit wizard.

11. On your server, launch Windows Computer Management.
Caution
Do not Initialize your newly discovered Windows drives in the following
step.
12. From within the Computer Management window select Disk

Management. Click cancel when prompted to Initialize the disks. You
will do this later.
Note
If the new storage is not visible you may wish to reboot your host
13. Verify that both hosts can see the newly configured drives. Leave the
Disk Management window open.
Why can you see two of each LUN represented here?

__________________________________________________________________
__________________________________________________________________
__________________________________________________________________
__________________________________________________________________

What might you be able to do about this?

__________________________________________________________________
__________________________________________________________________
__________________________________________________________________
__________________________________________________________________

Configuring Selective Storage Presentation (LUN ~Masking)

1. From the Common Tasks main menu, select Selective Storage
Presentation.
.
2. Click Begin to start, which brings up another screen that will allow you
to enable SSP for the controller. Record the default setting for SSP.
....................................................................................................
Note
SSP is enabled on a controller basis. Once enabled, host access must be
specified for each logical drive.
3. Click Enable to enable SSP (Disable SSP is the default). Click OK.

4. Under the Connection Name column, rename each connection

according to the server names you recorded earlier in this lab.
5. In the Logical drive column, select logical drives 1 and 2. Assign them
exclusive access by both HBAs in server 1. You will need to give the
connection a name as shown above.
N.B. If you are sharing an array with a lab partner who has their own
Windows Host then you must configure access to ALL LUNS for each host at
this stage. i.e. Logical drives 1 & 2 presented to host A and Logical drives
3 & 4 presented to host B.
Note
If you can see more hosts than your own and your lab partners’ then SSP
may not allow you to proceed past this step unless you set ALL other Host
Modes to ‘Default’.
6. When finished assigning SSP access, click OK → Finish.

7. You are now presented with a summary of the configuration. You must
now save the configuration. Click the Save button and you will be
presented with the following dialog box:
Click OK to proceed.

Disk Configuration in Windows

Note
Depending on how you perform the following procedure, the Disk
Wizard may or may not start.
1. Return to the Disk Management window and refresh the window.

2. Windows should automatically update the accessible drives according
to the SSP configuration.
3. As you have already cancelled the ‘Initialize Disk and Upgrade
Wizard’ you will need to right click where shown in the graphic below
and choose ‘Initialize Disk’ from the pop-up menu.

4. Select which disks to write a signature to. Select both Disk 1 and Disk
Click Next.

5. You should see your two new drives, represented twice, as unallocated.
6. Right-click on the first unallocated disk (Disk 1 pictured above) . Select

New Partition.
7. The New Partition Wizard launches. Click Next to continue.
8. Accept the default of ‘Primary partition’. Click Next to continue
9. Select Next to continue, accepting the default partition size (the entire
disk).
10. Select the drive letter that will be used to identify the drive. Click Next.
11. Check the Perform a Quick Format box and give a Volume label if
required, then click Next.

12. Verify your selections and click Finish to complete the task.
N.B. Do NOT format the second representation of your LUN. We will be

installing Multi-Path failover software in the next lab to mask this.
13. Create a volume on your second disk (Disk 3 above), repeating steps 6-
12.

14. You should now see your two new volumes.
In the next lab you will be installing the Microsoft MPIO software to mask the
additional instance of these LUNs.

Configuring MSA volumes for HP-UX (optional)

In this part of the lab you will repeat steps that you have already completed
to make ready LUNs for your HP-UX host.
1. Create an additional Logical Drive for your Unix host. You may wish
to use the manual method this time rather than the Wizard that you
used before. You will need to use your Windows host to complete
this part of the process.
2. When the process is complete make a note of the Logical Drive
number. _________________________________________________
3. Make the appropriate changes to Selective Storage Presentation for
your MSA to allow your HP-UX host to have visibility of the new
Logical Disk. REMEMBER – you will need to set the Host Mode to
‘HP’ for each HBA.
4. Open a telnet session to your HP-UX host if you have not already
done so.
5. Use the ioscan -fnCdisk command to view the new MSA Luns:
6. Use insf –e to install device drivers for the new LUN and you are then
ready to format the LUN with a file system.
You have successfully completed this lab


Configuring MPIO and monitoring paths
Module 5 — Lab 2
Objectives
Install Microsoft Windows Multipath I/O (MPIO) Full Featured DSM software
and management interface
Change load balance settings
Use the MPIO performance monitor
Requirements
To complete this lab, you will need the following hardware and software for
configuring a Windows 2003 host:
One server with:
• Windows 2003 operating system
• Two HBAs in the host
• A disk array (we will be using MSA1500 for this lab)
• Installation files for HP MPIO FF DSM for MSA (Active-Active) or Basic DSM
for Active-Passive arrays such as the MSA1000 (you will not be able to load
balance)
In addition, you must meet the following SAN requirements:
Each host must have a connection to each fabric

Installing MPIO for Windows

Use the following procedure for installing the MPIO software:
1. From the installation source, double-click launch.exe to begin the installation.
The splash screen displays.
Note
Ask your instructor for the location of the MPIO zip files. You will need to extract
them to your local machine (c:\MPIO). For this exercise we will be using version
3.00.00 of the MPIO DSM and MGR.
2. Click Install HP MPIO Full Featured DSM for MSA1000/1500 (Active-Active) Disk
Arrays to begin the installation. You will basically agree to everything and
accept the defaults.
3. Click Next on the Welcome screen
4. On the License Agreement screen, click Yes.
5. If you are reminded to close other applications, click OK when you have done
this.
6. After reading the Information screen, click Next.
7. On the Select Destination Location screen, click Next to accept the default
location.
8. You may see a pop-up regarding the installation components. Click OK if you
see this
9. On the Select Components screen, verify that the MPIO framework and HP DSM
are checked (the HP DSM entry might be greyed) and then click Next.
10. Click Install to begin the installation
11. Click Finish to complete the installation.
12. If prompted to restart your computer, click Yes.

Installing the MPIO GUI

Use the following procedure for installing the MPIO GUI:
1. Double-click HPMpioDsmManagerSetup.exe to begin the installation. The splash
screen displays.
Note
Ask your instructor for the location of the MPIO zip files. You will need to extract
them to your local machine (c:\MPIO). For this exercise we will be using version
3.00.00 of the MPIO DSM and MGR.
2. At the Welcome screen, click Next to continue.

3. On the License Agreement screen, accept the terms of the license agreement and
click Next.
4. Read the Information screen and click Next.
5. Accept the warning message and action it if necessary, OK.
6. On the Choose Destination Location screen, click Next.
7. Accept installing the default feature set, Next.
8. Click Install to begin the installation.
9. On the Notification Editor screen, click Cancel. In production you may wish to
complete the details in this dialog box to enable email alerting upon path
failure.
10. Click Finish to complete the installation.

Review how your host now represents visible volumes.
The additional representation of the LUN is now no longer visible (the paths have
been consolidated by the MPIO multi-path filter driver).

Changing load balance settings within MPIO

To use the MPIO DSM manager to change load balance settings, follow this
procedure:
1. Select Start → All Programs → Hewlett-Packard → MPIO DSM Manager →
Management Console to start the management console.
2. Select HP MPIO DSM Manager.
3. Expand the WWN for the MSA you want to manipulate.
4. Right-click the LUN for which you want to change the load balancing setting.
Select the appropriate load balance setting.
Note
If you select Set Load Balance None, one path is preferred and all other paths
are marked alternate. If you have load balancing set to any other setting, all
paths are marked active.

5. Right click a particular path and change it to the preferred path.
Full-featured MPIO provides path management with no load balancing and the
ability to change a LUN from being active in a multipath environment to a single
preferred path.
Using the MPIO performance monitor

To use the MPIO performance monitor, follow these steps:
1. Start a session between the server and a virtual disk on the MSA. Select Start →
All Programs → Hewlett Packard → MSA DSM → Path Performance to start the
performance monitor.
2. Right-click the perfmon display, click Add Counters, and under Performance
object, select HP DSM High Performance Provider and choose a counter from the
list for each Disk instance (listed on the right).

3. When you have added your chosen counters try writing some data to your
volumes and view the perfmon graphical output.
Using hpdsm command line tool

1. Select Start → All Programs → Hewlett Packard → MSA DSM → HPDSM CLI
to open the path to HPDSM.exe.
2. To display a list of available commands type: hpdsm help
3. To list all devices (LUNS) visible to the host type: hpdsm devices.
4. For a full list including available paths and controller connections type:
hpdsm devices all.
5. To view the path details to a particular LUN (device) type: hpdsm paths
device=X (where X is the desired device).
6. You may also change the load balancing policy using the command: hpdsm
set device=x policy=policy (where X is the desired device and
policy is the desired load balancing policy).
• No_Load_Balance (NLB)
• Round_Robin (RR)
• Shortest_Queue_Requests (SQR)
• Shortest_Queue_Bytes (SQB)
• Shortest_Queue_ServiceTime (SQST)
How might you verify the change to the load balancing policy?
_________________________________________________________________

Fabric Failover
Module 5 — Lab 3
Objectives
Consider the steps required to failover fabric traffic in a controlled way
Appreciate what happens when fabric failover occurs due to hardware failure
Requirements
At least two connected HP B-Series fabric switches with firmware version 5.x or
later
A client (server or workstation) with Telnet
Network connectivity between the client workstation and the fabric switches
The IP addresses of the fabric switches
The login name and password of the administrator account for the switches
Hosts running Multi-path software
LUNs presented to those hosts from a SAN disk array

Controlled Failover
The intent for this part of the lab is to manually fail ALL traffic over to a single fabric
so that you may bring the other fabric down in a controlled manner. You will need
to work with your lab partners to ensure that you are failing your traffic over on the
same fabric.
1. First ensure that your host has visibility of it’s SAN-based LUNs. If you are using
MPIO DSM manager then launch Computer management and decide which
path will be your preferred one.
2. Right click on that path and select Set Preferred Path
3. Repeat this for all other LUNs that you have connected.
4. When you are happy that all traffic is on one fabric then you may disable a
switch or all switches in the remaining (quiet) fabric to prove your test.
5. Why might you want to do this?
.................................................................................................................
.................................................................................................................
.................................................................................................................
.................................................................................................................

Fabric Failover
Disaster simulation
In this part of the lab you will be testing the path failover capabilities of the MPIO
software. During this test it may be a useful gauge to have data in transit during the
disaster simulation (switch outage). Consider making a large write to your SAN
volume or maybe streaming video from your SAN volume to your host at this time.
1. Confirm visibility of your SAN volumes and that they are load balancing (SQST
being the default).
2. Begin the transfer of data – the more you can transfer the better!
3. Disable or reboot a switch in the data path and observe the results at your host.
You can monitor the state of the paths using the MPIO DSM Manager.


Fabric Zoning
Module 6 — Lab 1
Objectives
Create, configure, establish, and modify zones on a single switch.
Create a configuration using only domain/port identifiers.
Create a configuration using only Worldwide Name (WWN) identifiers.
Create a configuration that mixes Domain/port and WWN identifiers.
Requirements
Before proceeding with this lab, verify the following:
Confirm that your fabric switch is isolated. If you are not sure how to verify this
then contact your instructor.
Confirm that your hosts and disk array are connected and logged in to the
fabric. Consider the nsshow or switchshow commands.

Domain/port zoning
1. From your first switch, connect using Telnet. Note what your Domain ID is for this
switch.
# switchshow
2. Create aliases for ports 4-7 using hard addresses. (Domain and port numbers).
# alicreate “ali_port4”, “[your switch domain ID],4”
Note that you should use the Domain_ID of YOUR switch!
Important
! Aliases are case-sensitive. They can greatly simplify the administrative process;
however, they are not required to define zones.
3. Display the aliases and their information.

# alishow
4. Create a zone for your storage and Windows hosts.

# zonecreate "Win_zone", "ali_port4;ali_port7"
A Windows host and your MSA

5. Create a zone for your storage and Unix host.
# zonecreate "Unix_zone", "ali_port6;ali_port7"
Your Unix host and your MSA

6. Create a configuration named cfgport including the zone.
# cfgcreate "cfgport", "Win_zone;Unix_zone”
7. Enable the cfgport configuration, there is an implicit save in doing this.

# cfgenable “cfgport”
8. Display all of the zone and configuration information.

# cfgshow
9. View the zoning configuration by port.

# portzoneshow
10. From the information you see, and from what you have learned about zoning,
do you see any problems with the configuration?
.................................................................................................................
.................................................................................................................

Fabric Zoning
The effect of the zoning on the topology

11. If you were to unplug the Windows host from port 4 and move it to port 8, could
the server still see the disk storage? Can you explain why?
.................................................................................................................
.................................................................................................................
12. Assume the host is back to its original port and you were to move the storage to
another port. Can the host still see the disks? Explain your result.
.................................................................................................................
Adding to a configuration
When zoning is disabled, the fabric is in a allAccess mode and devices can freely
access other devices in the fabric. You can determine the status of this behavior
using the command: defZone --show. When zoning is enabled, zoning is
enforced throughout the fabric and devices can communicate only within their zones.
Note
After zoning is enabled, if a device is not defined in a zone, that device will exist
in a zone all by itself. The device will be isolated and be inaccessible to other
devices in the fabric.
13. Disable the configuration cfgport.

# cfgdisable

Zoning using Web Tools

1. Now that you have learned how to create a zone using the CLI commands, you
can perform the same steps using the Web Tools.
2. Launch Web Tools.
3. Click the Zone Admin link within the Manage tasks pane
4. Select the Zone tab. Notice that the Win_zone is present. Notice that on the
right side, ports 4 and 7 are listed as members of the zone.
5. You will now create a new zone named other_zone that includes ports 5 and 7.
a. Click New Zone.
b. Enter other_zone and click OK.
c. Confirm that other_zone is selected in the Name field, and in the Member
Selection List column expand ‘Ports & Attached Devices’ and then
CTRL+click ports 5 and 7 and click Add Member.
6. Using the same steps, create a third zone named third_zone that includes ports
6 and 7.
Fabric Zoning
7. Select the Zone Config tab.

8. Create a ‘New Zone Config’ called guicfgport.
9. Add the two new zones form your ‘Zones’ list to the guicfgport configuration.
10. Click the Enable Config button and select guicfgport from the resulting list. Click
OK and, when prompted, answer the default messages.

Create a configuration using WWN zoning
1. Disable the configuration guicfgport by selecting Zoning Actions → Disable

Zoning.
2. Delete the zone Win_zone.
3. What are the WWNs of the devices connected to your fabric? (you have
documented them previously)
.................................................................................................................
.................................................................................................................
.................................................................................................................
.................................................................................................................
4. Create a zone named WWNzone.
5. Add the WWPNs that reside on port 4 and port 7 to WWNzone.
6. Add the new zone your chosen configuration and enable it.
Estimate the effect of the zoning on the topology.

1. If you were to unplug the MSA from the port it was on and move it another port,
could the host still see the disks? Explain your response.
.................................................................................................................
.................................................................................................................
.................................................................................................................
.................................................................................................................
2. View the output of the portzoneshow command.
3. Disable the configuration.

Fabric Zoning
Create a configuration using both port and WWN zoning

1. Create a zone where the host is zoned using port zoning and the storage is
zoned using WWN zoning.
2. Create a new configuration for this zone. Save the configuration.
3. Enable the configuration.
4. Display the zone and configuration information.
5. What happens when you move the storage subsystem port? Explain.
.................................................................................................................
.................................................................................................................
6. What happens when you move the host port? Explain.
.................................................................................................................
.................................................................................................................
7. Can you explain the difference in the results?
.................................................................................................................
.................................................................................................................
Clearing the zoning configurations

1. Disable the configuration.
# cfgdisable
2. Remove any zoning configurations.

# cfgclear
# cfgsave
3. Verify that everything is cleared.

# cfgshow
Please ensure that you have completed the 3 steps in this

section

Final zoning – Important!

1. Having seen the different ways in which zoning can be configured select your
favorite method (Port, World Wide Name or Mixed) and your favorite access
method (CLI or Web Tools) and create your final zoning configuration that
will remain active for the duration of your class. This Zone Config should
allow your host ports to have access to your storage ports.
2. When you have completed this Zone Config and enabled it let your instructor
know.

Merging B-Series Fabrics
Module 6 — Lab 2
Objective
After completing this lab, you should be able to merge two fabrics together in a
minimally disruptive manner.
Requirements
You and your lab partner have active zone cfg’s on your
switches
Ports 0-3 are disabled on your edge switch.

Merging B-series fabrics

Connecting fabrics running different zoning configurations
1. Please ensure that you have a cfg (zone set) enabled on your edge switches
before you proceed to the next step.
Record the name of the active cfg ………………………………………………………..
2. Enable ports 2 and 3 on both edge switches. This action will encourage the
switches to try to merge in to a single fabric.
3. From an Edge switch Telnet session observe and record what you see.
.................................................................................................................
.................................................................................................................
You might find the switchShow command useful for this.
It is likely that your switches have failed to merge (i.e they

are segmented) due to certain incompatibilities. These
incompatibilities might be non-identical fabric parameters,
duplicated domain ID or (in this case) zone conflict.
The following steps will enable you to merge your fabric

switches without compromising your zoning scheme on
either switch.

Merging two fabrics using the configUpload and

configDownload commands
1. Disable ports 2 and 3 on both switches.
2. From a Telnet session to fabricA, run the configUpload command to save the
fabric’s zoning configuration to a host.
3. From a Telnet session to fabricB, run the configUpload command to save the
fabric’s zoning configuration to the same host as the fabricA configuration was
saved to.
4. Using WordPad, edit the fabricB configuration file so that it contains only the
zoning information and save it as file name B_zone_config.txt. For example, the
new file (in its entirety) should resemble the following (you will see your own
alias, zone and cfg entries):
Note
Notice that the output starts with the line [Zoning] and ends with the [End]
delimiter.
[Zoning]
cfg.B_Config:B_Zone
zone.B_Zone:MSA_PT2; WIN_PT2
alias.MSA_PT2:1,1
alias.WIN_PT2:1,0
enable:B_Config
Note that this content is included

[Defined Security policies] as it constitutes the entire end of
the file, from [Zoning] to [End]. It
[Active Security policies] is important to include this in all of
the following steps in this lab to
ensure that the switch is able to
[FICU SAVED FILES]
parse the file when you
‘download’ it back to the switch
[fcRouting] later.
N.B. The markup in this example
[iSCSI] is for demonstration only. Your file
might contain different entries as
[Banner] its content is switch firmware
dependent
[End]
Caution
If you do not edit this file, when later using the configDownload command,
you risk overwriting the domain IDs, fabric parameters, and licenses, depending
on the switch type.
5. Using WordPad, edit the fabricA configuration file such that it contains only the
zoning information and save it as file name A_zone_config.txt. For example, the
new file (in its entirety) should look similar to the following (you will see your
own alias, zone and cfg entries):
Note
Notice the output below starts with the line [Zoning] and ends with the line
[End]. The final version of your file should use both delimiters still.
[Zoning]
cfg.A_Config:A_Zone
zone.A_Zone:MSA_PT1; WIN_PT1
alias.MSA_PT1:2,1
alias.WIN_PT1:2,0
enable:A_Config
[Defined Security policies]
[Active Security policies]
[FICU SAVED FILES]
[fcRouting]
[iSCSI]
[Banner]
[End]
Caution
If you do not edit this file you risk overwriting domain IDs, fabric parameters,
and licenses, depending on the switch type.

Creating the merged configuration

1. Using WordPad, create a new file called C_zone_config.txt.
2. Copy the contents of the A_zone_config.txt zoning information and
B_zone_config.txt zoning information into the C_zone_config.txt file.
3. Delete the lines in the file that contain duplicate markup. This should result in a
file that starts with the title [Zoning] entry and ends with the title [End] entry. The
result should resemble the following output:
[Zoning]
cfg.A_Config:A_Zone
alias.MSA_PT1:2,1
alias.WIN_PT1:2,0
enable:A_Config
cfg.B_Config:B_Zone
alias.MSA_PT2:1,1
alias.WIN_PT2:1,0
enable:B_Config
[FICU SAVED FILES]
[fcRouting]
[iSCSI]
[Banner]
[End]

4. Next, delete the two lines that start with the word ‘enable:’. The edited output
should resemble the following:
[Zoning]
cfg.A_Config:A_Zone
alias.MSA_PT1:2,1
alias.WIN_PT1:2,0
cfg.B_Config:B_Zone
alias.MSA_PT2:1,1
alias.WIN_PT2:1,0
[FICU SAVED FILES]
[fcRouting]
[iSCSI]
[Banner]
[End]

5. Next, delete the two lines that start with the word ‘cfg.’. The edited output should
reassemble the following:
[Zoning]
alias.MSA_PT1:2,1
alias.WIN_PT1:2,0
alias.MSA_PT2:1,1
alias.WIN_PT2:1,0
[FICU SAVED FILES]
[fcRouting]
[iSCSI]
[Banner]
[End]
6. Lastly, create a new zoning configuration entry line in the file called C_Config by
adding a line consisting of all the zones from both fabrics. Also you’ll need to
insert a new enable entry as below. The edited output should resemble the
following (you will see your own alias, zone and cfg entries):
Note
Notice in the following output that there is a new cfg line entry called C_Config
which consists of the two zones: A_Zone and B_Zone.

[Zoning]
cfg.C_Config:A_Zone;B_Zone
alias.MSA_PT1:2,1
alias.WIN_PT1:2,0
alias.MSA_PT2:1,1
alias.WIN_PT2:1,0
enable:C_Config
[FICU SAVED FILES]
[fcRouting]
[iSCSI]
[Banner]
[End]
7. Save the file.

Using configDownload to download the combined zoning

configuration to the two fabrics
1. Disable the switch in FabricB by using the switchDisable command.
2. Run the configDownload command to download the merged configuration
file (C_zone_config.txt) to the disabled switch in FabricB.
3. Use the switchEnable command to enable the FabricB switch. When you
enable the FabricB switch, the C_Config zoning configuration information will
become part of fabricB and become the effective configuration.
4. Issue the cfgshow command and verify that the new merged zoning
configuration is in effect.
5. Disable the switch in FabricA by using the switchDisable command.
6. Run the configDownload command to download the merged zoning
configuration file (C_zone_config.txt) to the disabled switch in FabricA.
7. Use the switchEnable command to enable the FabricA switch. When you
enable the FabricA switch, the C_Config zoning configuration information will
become part of fabricA and become the effective configuration.
8. Issue the cfgshow command and verify that the new merged configuration is
in effect.
9. Enable ports 2 and 3 on both switches, and observe what happens. Issue the
fabricShow command from any switch and determine how many switches are
present in the fabric. Record the results here.
.................................................................................................................
.................................................................................................................
10. Based on your experience with this lab, when designing SANs, what factors
should be considered to ensure that SANs can be merged with a minimum
amount of effort?
.................................................................................................................
.................................................................................................................

Splitting the fabric

1. Disable ports 2 and 3 on both switches and observe the results. Does this
interrupt I/Os generated from the servers? Why or why not?
.................................................................................................................
.................................................................................................................
2. Enable ports 2 and 3 on both switches and observe the results. Is the fabric
operational?
.................................................................................................................

SanDesigner installation and configuration
Module 7 — Lab 1
Objectives
Install and create a san design using SanDesigner
Requirements
25 MB of free disk space for installation
To use SAN Designer, the following applications must be installed on a
host where SAN Designer is installed:
Java 2 Runtime Environment (JRE), SE v1.5 or later
Microsoft Excel viewer
Microsoft Visio viewer
This lab does not go through the process of e-mailing the report to HP for the
To install SAN Designer, complete the following steps:
1. Copy the SanDesigner application from the depot to c:\Compaq

2. The program is available for Download from the following site:
http://h18006.www1.hp.com/storage/networking/sandesigner.html
3. Run the SANDesigner1.3_Setup.exe install package to install SAN Designer files.
Review and accept the license agreement. By default, the SAN Designer files
and documentation are installed in the following location: c:\Program
files\Hewlett-Packard\HP SAN Designer
NOTE: Ensure that JRE1.5 or later is installed on the host.

All server numbers, blades, storage and fabric options are

flexible and are the personnel preference of team
members and are not defined in the lab.
Using San Designer
HP StorageWorks Essentials SAN Designer enables you to design a new SAN, or

view and modify an existing SAN design.
Designing a SAN
Launch the HP StorageWorks Essentials SAN Designer 1.3 software by double-

clicking the SAN Designer shortcut icon from the desktop. The SAN Designer
welcome screen is displayed.

The following options are available in SAN Designer welcome screen:
• Design a new SAN - Select this option to design a new SAN.

• View or Modify a saved SAN Design - Select this option to view or modify a
saved SAN design.
Click Next to view the Select Server/Blade window.
Specifying server details
The Select Server/Blade window displays details of servers and blade systems in the
SAN. The Select Server/Blade window enables you to add, modify, and delete a
server and a blade system group.

To add a server group, complete the following steps:
1. On the Select Server/Blade window, click the Server group tab. The server
group details are displayed.
2. Enter a convenient name (optional) for the server group in the Server group box.
3. Enter the number of servers in this group in the Server Count box. The number
must be between 1 and 100.
4. Select the operating system from the Server OS drop-down list.
5. Select the operating system version for the selected OS from the OS Version
drop-down list.
6. Enter the number of HBA fabric connections for each server in the server group
in the HBA fabric connections for each server box. The number must be between
1 and 16.
7. Click the Add Server Group button to add this group. The server group is listed
in the Server Group table.
Adding a blade system group
To add a blade system group, complete the following steps:

1. On the Select Server/Blade window, click the Blade system group tab. The
blade server group details are displayed.
2. Enter a convenient name (optional) for the blade system group in the Blade
system group box.
3. Select the blade system class from the Blade system class drop-down list.
NOTE: Only C-Class blade servers are supported in SAN Designer 1.2.
4. In the Full Height Server Blades panel, enter the following details: a. Enter the
number of full height server blades for this group in the Server blade count
box. The number must be between 1 and 100. Enter the number of HBA
fabric connections for each full height server blades in the HBA count per
server blade box.
NOTE: Full height blade server can have a maximum of 3 HBAs for C-Class blade servers.
5. In the Half Height Server Blades panel, enter the following details: a. Enter the
number of half height server blades in this group in the Server blade count box.
The number must be between 1 and 100. b. Enter the number of HBA fabric
connections for each half height server blades in the HBA count per server
blade box.

NOTE: Half height blade server can have a maximum of 2 HBAs for C-Class blade
servers.
5. Click the Add Blade System Group button to add this group. The blade system
group is listed in the Blade Group table.
NOTE: The table contains the full and half height blade server values. The rows in
the table display the values in full\half Height format. For example 12\1 under the
heading "Count (F\H)" indicates a selection of 12 full heights and 1 half height
blade server.
After entering server and blade details, click Next to enter storage details.
Specifying storage details
The Select Storage window displays the storage details of your SAN. The Select
Storage window enables you to add, modify, and delete a storage group.

Adding a storage group
To add a storage group, complete the following steps:

1. Enter a convenient name (optional) of the storage group in the Storage Group
box.
2. Enter the number of storage devices in this group in the Storage Count box. The
number must be between 1 and 100.
3. Select the storage model from the Storage Model drop-down list. If required,
select the number of fabric connections for each server in the Fabric Connections
for each Storage Model drop-down list.
NOTE: The number of fabric connections for each array is disabled for EVA
4000/4100, EVA 6000/6100, and EVA 8000/8100 disk arrays because the
numbers of ports in these arrays are always the same.

4. Click the Add Storage Group button to add this group. The storage group is
listed in the storage group table.
5. After entering storage details, click Next to enter fabric details.
Specifying fabric details
The Select Fabric window displays the fabric and switch details of your SAN.
To specify fabric details, complete the following steps:

1. From the Select Switch Series drop-down list, select the switch series. Selecting the
HP StorageWorks 8/20q switch series does the following: • Disables the Blade
system group tab in the Select Server/Blade window. • Lists only the suitable
switch operating systems and storage models in the Select Server/Blade and the
Select Storage windows.
2. Enter the port count growth in percentage in the Port Count Growth box. The
number must be between 1 and 100. Port count growth is the estimated
additional fabric port requirements for future needs.
3. In the Preference panel, select one of the following options:
• Optimize for Performance

• Optimize for Cost
• Cost and Performance
4. In the Availability panel, select one of the following options based on the level of
redundancy for your fabric:
• No Single Point of Failure with 4 Redundant Fabrics (NSPoF4)

• No Single Point of Failure with 2 Redundant Fabrics (NSPoF2)
• Single Fabric

After entering fabric details, click Next to view your SAN summary. The View SAN
Summary window is displayed.
Viewing SAN summary The SAN Summary window provides a summary of the SAN

The View SAN Summary window displays the following: A summary of information
about servers, storage, and fabric in the currently selected SAN components section,
and a graphical depiction of the SAN topology in the SAN Topology section.
• The Print SAN Design window enables you to print your SAN design
• The Save SAN Design window enables you to save the SAN design
• The Contact Information window enables the specification for contact
information. These details are part of the processed report.
• SAN Designer enables you to send your SAN design requirements to HP for
analysis. Information about your SAN design requirementsthis is stored as a
.hpsd file. This file is available in the following folder: <Install_Dir>\Hewlett-
Packard\HP SAN Designer\reports.
In this lab we will not be attaching and sending on to the HP SAN Design team for a
detailed report.
This ends the lab.


SanVisibility installation and configuration
Module 7 — Lab 2
Hardware and software requirements
Standard LAN connectivity with target FC switches
• 25 MB of free disk space for installation

• To use HP StorageWorks SAN Visibility, following are the necessary applications
that need to be installed on a host where HP StorageWorks SAN Visibility is
installed:
• Internet Explorer v5.01 or later
• Java 2 Runtime Environment (JRE), SE v1.5
• Microsoft Excel viewer
• Microsoft Visio viewer
• Brocade SMI Agent (110.4.0a) installed for SMI-S based data collection.
Supported operating systems
Supports Microsoft Windows system with any of the following operating systems:
• Microsoft Windows 2000 Server with Service Pack 4
• Microsoft Windows Server 2003 Standard or Enterprise edition with Service
Pack 1
• Microsoft Windows XP Professional edition with Service Pack 2
Installing HP StorageWorks SAN Visibility
The HP StorageWorks SAN Visibility package is available for download from the
following website:
http://h18006.www1.hp.com/storage/networking/sansolutions.html.

Copy the SanVisibilty software from the depot and save into a folder on the chosen
windows server, for example, C:\Compaq and run the P StorageWorks SAN
Visibility install package, from this location.
Run SANVisibility_Setup.exe, and follow the steps to install HP StorageWorks SAN

Visibility files. Review and accept the license agreement. By default, the HP
StorageWorks SAN Visibility files and documentation are installed in the following
folder: C:\Program Files\Hewlett-Packard\hp SANVisibility
A message is displayed on completion of the SAN Visibility software installation
NOTE: Ensure that JRE1.5 (or higher) is installed on the host

Using HP StorageWorks SAN Visibility
Launch the HP StorageWorks SAN Visibility software by double-clicking the SAN

Visibility shortcut icon on the desktop. This displays the HP StorageWorks SAN
Visibility welcome screen
Click OK to view the SAN Visibility GUI.

The SAN Settings window displays SAN details. It enables you to add and modify
the SAN group
Adding SAN details
To add SAN details, complete the following steps:
1. Click SAN Settings from the navigation area. SAN Settings window is displayed
in the main display area.
2. The default SAN name, MySAN, is displayed in the SAN Name box; rename
MySan to <your name_SAN> by entering the details of the SAN in the SAN
Name box.
3. Click Rename. The SAN name appears in the SAN explorer area.
Switch Group Name is a logical name to represent the collection of cascaded

switches in the SAN. To enter the Switch Group Name, complete the following steps:
1. Enter the name of your switch group in the Switch Group Name box. The default
switch group name, MySwitchGroup, is displayed in the Switch Group Name
box. Rename to your labgroupxx_Sanx and number e.g.: <labgroup10_SANA>.

2. Click Add. The switch group name appears in the SAN explorer area under the
SAN name.
3. Click Next to enter the switch details.
.Specifying switch details
To add a switch, complete the following steps:

1. Click Switch Settings from the navigation area. The Switch Settings window is
displayed in the main display area.
2. Enter the IP Address of one of the switches to scan. Select Discover cascaded
switches check box to discover all the cascaded switches. Enter the access
information, as required, to initiate data capture for the selected switch.
3. Enter the Brocade login and password.

4. Select a switch group from the Switch Group Name drop-down list.
5. Click Add. The switch becomes a part of the named group if it is a valid and
supported switch.
6. Click Discover Switch to discover valid switches
7. Select a switch group from the Switch Group Name drop-down list and click
Add. The switch becomes a part of the named group. The list of detected
switches is added to the specified switch group, and the details are displayed in
the message area.
Specifying customer details
The Customer Details window enables you to enter your contact information, your
SMTP server details, and your preferences for receiving additional HP product
information.
Add contact details

1. Click Customer Details from the navigation area. Customer Details window
appears in the main display area.
2. Enter your contact information in the Customer Details window, enter the e-mail
address of your instructor. These details are part of the processed report.
3. de-Select Automatically email the collected raw data on completion check box
4. In the SMTP Server field enter smtp.hpvl.hp.com
5. Click next

Initiating data collection
1. Select a switch group from the Choose switch group for data collection
dropdown list, or select For all switch groups check
2. Select Capture Performance data check box to capture the performance data for
all the switch groups in the SAN.
3. For Report Format select HTML Report and Microsoft Excel Report formats.
4. Click Start Data Collection to initiate data collection for a specific switch group,
or for all the switch groups depending on the requirement. A message is
displayed in the message area on successful completion of the data collection.

5. Select yes to view and send the data.

6. View files by selecting next File or Prev File when finished select close.
7. Select Default Mail Client
8. Select File, and then the option Send Later, select ok at the prompt.

It is also possible to send the raw data to HP at a later date, so that it can be
processed and a report generated and return to the e-mail specified in the report. To
Achieve this attach the <SAN_Name>.hp file located at: c:\program files\Hewlett-
Packard\hp SANVisibility\reports\ to your email, where <SAN_Name> is the name
of your SAN entry. This is .Email is a raw data file and is sent to:
SAN_Visibility@hp.com with the following subject line: "HP StorageWorks SAN
Visibility 3.1 Report Request". An automated email response is mailed back to you
confirming the receipt of the raw data file. On completion of the SAN analysis, you
receive a detailed SAN Visibility report containing the SAN topology map, device
inventory, high level SAN summary, and recommendations. It normally takes up to 1
business day to send back the processed report.
Install excel viewer and Visio Viewer the software is located in the share depot.
After the install of Visio and Excel navigate to z:\tools\SanVisibilityReport
Double Click on the file HPVL_20090213-043447-HTML.hppr

On the Decrypting Processed Report select yes. A San Visibility Report will be
displayed. Allow any blocked content to view the full report.
Check through all the information collected in the report.

That ends this lab.

iSCSI LUN Mapping
Module 8 — Lab 1
Objectives
Set up iSCSI target devices
Connect an iSCSI initiator to iSCSI targets
Write data through to these targets
Requirements
Two Windows host systems (one will act as a target and one will be an initiator)
Network connectivity between them
A raw (unformatted) SAN-resident volume
iSCSI initiator and target software (your instructor can provide this for you)
UC434S C.02 © 2009 Hewlett-Packard Development Company, L.P. L8 – 1

Before you start – Important!

In order to complete this lab you will need to have an un-formatted SAN-based lun
presented to your chosen iSCSI target host server. You may use multi-path software if
you require. Work with your lab partner to decide which of your systems you will
use to fulfill the target and initiator roles.
Installing the iSCSI target software

To create an iSCSI target device for a remote initiator to map you should first install
the target software and configure the storage for presentation. The software that you
will use for this lab is called Starwind and will operate using an evaluation license.
1. Locate the Starwind.exe file and double click it. (You will accept all of the
default installation settings that follow). If you are using the hpvl then you will
find this file at: Z:\iscsi\.
2. On the following screen click ‘Next’
3. Accept the license agreement and choose ‘Next’
4. Allow the software to select the default install location and click ‘Next’
5. Select the default of ‘Full Installation’ on the following screen and click ‘Next’
6. Allow the installer to create a default Start Menu folder and click next
7. Permit the creation of a desktop icon and select ‘Next’
8. Finally, review the installation options and click the ‘Install’ button
9. When the installation has completed, click ‘Finish’. The Starwind service will
start but you may not see the management interface yet.
10. Right click the new Starwind icon in the system tray beside the clock and select
the topmost option ‘Start Management’ to launch the management GUI.
L8 – 2 © 2009 Hewlett-Packard Development Company, L.P. UC434S C.02

iSCSI LUN Mapping
11. You will see an entry in the management interface for ‘localhost:3260’. Right
click this item and choose ‘Connect’ from the pop-up menu. A new window will
appear requiring a Username and Password.
12. Enter the password ‘test’ to match the username and click ‘OK’
13. You will see a new window appear which reminds you that you are using an
evaluation license. To clear it click ‘OK’

14. You will see that sample device is already in the list. This device is a RAM Drive
which you may mount on your iSCSI initiator later on but we will create a new
LUN now.
15. From the icon bar at the top of the GUI click ‘Add Device’ and you will see the
following window:
16. For this lab we will choose ‘Disk Bridge device’ which is used to allow us to
present the raw (without a file system) LUN which we have ready. Check the
radio button and choose ‘Next’

iSCSI LUN Mapping
17. The ‘Disk Bridge device parameters’ dialog appears after the software searches
for disk devices.:
In the main box select the device (RAW disk) that you wish to present. You will
see all eligible devices including those which already have a file system. Notice
that a ‘Read-only mode’ is available (do not check this). To proceed, click ‘Next’.
18. You will need to select a name by which your target will be recognized.
Although this step is labeled ‘Optional’ it would appear not to be. Type a name
and click ‘Next’.
19. Choose ‘Next’ at the summary screen and then choose ‘Finish’

20. In the management interface for Starwind you should now see the newly added
target:
You have successfully created an iSCSI target

iSCSI LUN Mapping
iSCSI initiator
In order to connect to your iSCSI target you will need to install an initiator on your
OTHER Windows system. In a production situation you may consider using specific
iSCSI hardware for this job but for the purpose of this lab you will use the Microsoft
iSCSI initiator software to append the driver stack for your system’s existing network
interface card.
1. Find the iSCSI initiator installation file (Initiator-2.05-build3392-x86fre.exe) and
double-click it. If you are using the hpvl then you will find the file at: Z:\iscsi\.
2. Click ‘Next’ at the first screen
3. The following window shows the installation options:
The image shows the options that you need to select, enter a checkmark in all
the boxes as indicated and choose ‘Next’. If the multipathing option is greyed
out you may be using a system with only 1 NIC which won’t support
multipathing.
Agree to the license terms and click ‘Next’ to continue the installation.
4. Click ‘Finish’ at the next screen when the installation has completed.
5. You are likely to be asked to reboot your host at this time. Please do so.

Configuring the iscsi initiator
1. The installation will install a Desktop icon (Microsoft iSCSI Initiator). Double
click it to launch the configuration window.
2. Review the five tabs of this configuration window. You will need to first add a
target portal by clicking ‘Add’ on the ‘Discovery tab as pictured below.
3. Enter the IP address or DNS name of your iSCSI portal (this is the address of the
target server that you configured earlier in this lab). You may review the
‘Advanced’ section although the default settings will work well enough for us at
this stage. Click ‘OK’ when you are done.

iSCSI LUN Mapping
4. Ensure that your Target Portal has been found and properly connected. You
should see the following entry (albeit with the details that you entered):

5. Now that the Target Portal has been added you should see its target devices
displayed in the ‘Targets’ tab. If you do not then click the ‘Refresh’ button and
wait for the discovery cycle to complete.
6. You will see the name of the target device that you added earlier in this lab.
Select the disk target that you configured earlier and click the ‘Log On’ button.
7. Check the box illustrated in the image below to ensure that your connection
persists across reboots and then click ‘OK’

iSCSI LUN Mapping
8. The entry in the ‘Status’ column for your target should now read ‘Connected’.
Check the ‘Persistent Targets’ tab to ensure that your target has an entry.
9. Click ‘OK’ to close the iSCSI dialog box and you are ready to format your
target.
10. Treat your new raw presentation as any other raw LUN now and use the Disk
Management tool to format it and mount the file system.
11. Once this is complete you will be able to write data to your new iSCSI volume.
You have successfully created an iSCSI volume

Review
1. Prepare another drive from your SAN disk array and present it via your iSCSI
Target host. When naming the LUN how might you follow the default iSCSI
naming convention? Document your chosen name below:
.................................................................................................................
2. What is the default iSCSI name that your iSCSI initiator has been given? You
should be able to see the connected initiator presented below the target device
in the StarWind management console.
.................................................................................................................
3. If you were to present a LUN to two iSCSI initiators in a read/write mode what
risks do you face? Would this be acceptable in a cluster?
.................................................................................................................
.................................................................................................................
.................................................................................................................
.................................................................................................................

iSCSI LUN Mapping
Further exploration
This section of the lab is optional and you may try all or just some of these ideas for
further exploration:
1. Try creating a RAM drive from your iSCSI target software (256MB will probably
be sufficient for this demonstration). Present this to your iSCSI initiator – when in
disk management on the initiator machine do you notice a difference between
the RAM disk and the SAN array disk presentations?
.................................................................................................................
2. Ask your instructor to show you where to find an ISO image and use this to
present a ‘Virtual DVD’. You will need to refresh the list of iSCSI targets on your
initiator machine before you can connect to this.
You have completed the iSCSI lab


Data Center Fabric Manager - DCFM
Module 11 — Lab 1
System Requirements:
Windows® 2003 Server, 2 GHz, 1G Ram
Data Center Fabric Manager and Fabric manager cannot coexist on the same
system, DCFM automatically uninstalls an instance of Fabric Manager during the
installation process of DCFM.
Installing Enterprise trial on a Windows systems
1. from one of your Windows servers navigate to the share depot and copy
Z:\Data Center Fabric Manager to c:\Compaq
2. navigate to C:\compaq\Data Center Fabric Manager\Windows
3. Double click install.exe
4. Click Next on the Introduction screen.

5. Read the agreement on the License Agreement screen, select I accept the terms
of the License Agreement and click Next.
6. Select the location for your system’s application files
c:\Program Files\DCFM 10.0) on the Select Install Folder screen and click Next.
7. Review the displayed installation summary on the Pre-Installation Summary
screen and click Install.
8. Make sure the Launch DCFM Configuration check box is selected (default) on
the Installation Complete screen, and click Done.
9. Click Next on the Welcome screen.
10. Select No on the Copy Data and Settings screen and then click Next.

11. Select External FTP Server on the FTP Server screen and click Next.
12. Complete the following steps on the Server IP Configuration screen.
a. Select an address from the Switch - Server IP Configuration Preferred Address

list. This should be the address of the server that DCFM is being installed on.
b. Click Next.

13. Accept all defaults on the Server Port Configuration screen
14. Next
15. Verify your configuration information on the Server License Summary screen and
click Next.
16. Select the Start Client check box on the Start Server screen.
17. Select Finish.

At the login screen enter the following account details:
User ID Administrator
Password password
Click OK on the DCFM Login banner

Setting up discovery
To discover specific IP addresses or subnets, complete the following steps.

1. Select Discover > Setup. The Discover Setup dialog box displays. Click on add,
and a new window appears with a heading of Address Properties.
2. Enter the details of Fabric name the IP address of one switch in your
labgroup, and admin and password, and then click OK.
3. Once the switches are discovered a display similar to this will be seen.

Close the Discover Setup window and return to the main DCFM window.
The Data Center Fabric Manager that has been installed is a 75 day trial version, as
such major features are disabled.

In your Topology map or the navigation to the left select one switch so it is
highlighted in blue.
1. From the Configure menu – Element Manager
a. Select Hardware
What does this do? …………………………………………………..
b. Select Port
What does this do? …………………………………………………..
c. Select Admin
What does this do? …………………………………………………..
2. Configure - Zoning
What does this do? …………………………………………………..
3. Configure - Names
What does this do? …………………………………………………..
4. Configure - Troubleshooting.
a. Traceroute
What does this do? …………………………………………………..

b. Fabric device Sharing.
What does this do? …………………………………………………..
5. Configure - IP Troubleshooting.
What does this do? …………………………………………………..
6. Select monitor – Reports – Generate – select – ok
Once the report is finished a fabric summary report will be automatically

displayed, an example is displayed above.
7. On the DCFM main Window select Domain ID.
What does this do to the fabric display? …………………………………..
8. On the DCFM main Window select Decimal.
What does this do to the fabric display? …………………………………….
This Ends the lab for DCFM


Fabric security
Module 12 — Lab 1
Objectives
Identify the switch port types
Configure a port speed
Configure a port type
Configure a port name
Create a Switch Connection Control policy
Create a Device Connection Control policy
Requirements
Telnet and Web Tools access to a B-series switch running firmware 6.1.0 or later.

Configuring ports
To configure the switch, you will use Web Tools and a Telnet session. HP
recommends that you leave each connection tool open and switch between the tools
as required.
Port types
Before continuing, it is necessary that you can identify the different types of ports.
1. What is an L_port?
.................................................................................................................
2. What is an E_port?
.................................................................................................................
3. What is an N_port?
.................................................................................................................
4. What is an NL_port?
.................................................................................................................
5. What is an F_port?
.................................................................................................................
6. What is an FL_port?
.................................................................................................................
7. What is a G port?
.................................................................................................................
8. What is a U port?
.................................................................................................................

Fabric security
Viewing the port configuration

You can configure the switch port for specific port types.
1. Using Telnet, view the current port configuration by using the portcfgshow
command.
2. Using Web Tools, from the Switch Admin window of your first switch, click the
Ports tab. As seen in the previous lab, you can gather port configuration
information and port status from this view.
3. View the output from the portflagsshow command and compare it with
portcfgshow.

Persistent port disable

There are two ways that an administrator can disable ports on an individual basis.
A simple portdisable command will disable a port until the next reboot and the
portcfgpersistentdisable command will keep the port disabled across
reboots.
Why might you wish to persistently disable a port or ports on a fabric switch?
_________________________________________________________________________
_________________________________________________________________________
_________________________________________________________________________
_________________________________________________________________________
1. If you have two unpopulated ports on your switch (2 and 3) you may use
these for this step, else choose two others which won’t disrupt your access to
LUNs. Apply the standard command to one and the persistent disable
command to the other and reboot the switch (if you wish to skip the POST
during boot then use the fastboot command). Do your ports behave as
expected when the switch has rebooted?______________________________
2. Explore the Web Tools version of this same process and repeat if you wish.
Do you see the same results?________________________________

Fabric security
Configuring a port name

Use the portname command to assign or display a port name. With both the
operands present, the port name string will be assigned to the port. With only the
port name operand, the previously assigned port name will be displayed. With no
operands, the port names of all the ports present will be displayed.
The port name is a string of length 32 characters or less. It may consist of white
spaces or printable characters, excluding the characters comma and semi-colon. By
default, a port has no name until it is explicitly assigned by the user. A null string
(that is no port name operand specified) is used as the default port name when a
port had no user assigned name. A port name can be reset to the default value by
executing the portname command with the second operand as a null string.
Like all other configurable port attributes, port name will be persistent across reboots
and power cycles. It will not be affected by configdefault command but it will
be cleared by portcfgdefault.
1. Assign a port name to the Windows host that is connected to the switch on port
0. When assigning names, be descriptive. Assign your port using the following
syntax:
# portname 0, W2K3_HBA0
2. Verify the change.

# portname
3. Using Web Tools, from the Switch Admin window, click the Ports tab.
4. Scroll to the right until you see the Port Name column. Notice that the name of
port 0 has been changed to W2K3_HBA.
5. Using Web Tools, name the other ports that are connected to your switches by
double-clicking the appropriate field to edit the name. Configure the port names
for all connected devices on both switches. Click Apply → Yes.
To help confirm and verify the ports by identifying the devices including a HP-UX
host and the host ports of an EVA, perform the next exercise.

Deny E-port
You may wish to configure ports in your fabric to deny an ISL connection. You can
achieve this with the portcfgeport command.
Why might you wish to do this?
_________________________________________________________________________
_________________________________________________________________________
_________________________________________________________________________
_________________________________________________________________________
1. You should have two E-ports (ports 0 and 1) which connect your edge switch
to the core.
2. What will happen to the fabric if you issue a command to prevent these two
ports from functioning as E-ports?
_________________________________________________________________________
_________________________________________________________________________
_________________________________________________________________________
_________________________________________________________________________
3. Use the command portcfgeport #,0 to invoke this denial for both of
your E-ports. What is the switchshow output when this has been
completed?
_________________________________________________________________________
_________________________________________________________________________

Fabric security
Use the Web Tools port configuration wizard to re-enable E-port status.

Connection Control Policies

Your switch has two connection control policies:
• Switch Connection Control (SCC) policy—Used to restrict which other
switches can join the fabric.
• Device Connection Control (DCC) policies—Used to restrict which Fibre
Channel device ports can connect to which Fibre Channel switch ports.
These policies are part of a larger security set of policies known as Access Control
List (ACL) policies which includes FCS (controlling which switches can make
configuration changes within the fabric) and IPFilter (filtering management traffic
according to IP address and TCP/UDP port).
Switch Connection Control (SCC)

1. You can issue the secPolicyShow command to show active policies within
the fabric. You should see the following: (Advise your instructor if you see
any policies documented here).
2. Using the web tools interface, open the Switch Admin window and navigate
to the ‘Security Policies’ tab (you will need to switch to ‘Advanced Mode’ to
see this tab).

Fabric security
3. Click ‘Edit’ and you will see the ACL Policy Configuration Wizard. If you
clicked from the SCC sub-tab then you should see the SCC box checked.
Click ‘Next’ to move to Step 2.
4. In Step 2 you will define the members of the policy (identify other switches
permitted to join the fabric). To select policy members click the ‘Create’
button.
5. If you wish to add all the available switches to the policy you can click the
‘Add All’ button, else you may select the switches individually and click ‘Add
Switch’. Add ALL the switches to the policy and click ‘OK’.
6. Review the Defined Policy Set switches and click ‘Next’ to move to Step 3.
7. Click Finish to save the policy.
8. The policy is saved but no yet activated. Click ‘Activate’ to do this and then
confirm.

9. You can see the Active Policy Set members in web tools and the command
line:
10. Try to modify the SCC policy to exclude the ‘Core’ Switch. What is the
impact on your fabric and what CLI commands might you use to investigate
this?
_________________________________________________________________________
_________________________________________________________________________
_________________________________________________________________________
_________________________________________________________________________

Fabric security
Device Connection Control (DCC)

Using the same method as creating the SCC you will now create a DCC to
restrict/allow device WWNs access to the fabric.
1. Select the DCC sub-tab and click ‘Edit’. You will see that, in Step 1, the DCC
tick box is checked. Click ‘Next’ to continue.
2. In Step 2 click ‘Create’ to allow selection of your policy members. For the
sake of this exercise you will create a policy that deliberately excludes one of
your hosts (to examine the impact of this exclusion). You have a greater
choice of member type for DCC configuration. Here we will use Port
WWNs.
3. As you might have multiple defined DCC policies you will need to give this
policy a name. Choose DCC_POLICY_001.
4. Access control for B-Series switches requires that the administrator specify
switch ports via which this DCC Policy acts. You will need to select either the
occupied (by F-Ports) switch ports or all active ports on your edge switches in

order for this Policy to permit access. You can see this in the previous
graphic.
5. After returning to the wizard click ‘Next’ and then ‘Finish’ to return to the
Security Policies tab.
6. Click ‘Activate’ and then ‘OK’ to confirm. Your policies are now active. Run
the secPolicyShow command to verify.
7. Run the switchShow command to see the effect of excluding one of the
device WWNs.
8. In order to permit access to that excluded port you should ‘Modify’ the Policy
and add it. Remember to ‘Activate’ the Policy once you have saved this
change else the exclusion will remain in force.
Finally, ensure that your security Policies permit all access required in order to
continue with your lab sessions.
You have completed this lab.

Installing HP StorageWorks Storage Mirroring
Module 13 — Lab 1
Objectives
verify the installation requirements
install HP StorageWorks Storage Mirroring onto a Windows host
Requirements
This exercise requires the following resources:
HP StorageWorks Storage Mirroring installation CD (or files shared on the
network)
Access to the following hardware:
for each student group (2 students):
• 2 Windows Hosts

Lab activity: the training environment

To be able to successfully implement HP StorageWorks Storage Mirroring, you have
to identify the systems that are going to run this software.
You have to make sure that the prerequisites for installation are properly met and you
have to document this information.
Activity directions
In this lab, you will have to identify the following and gather some additional
information that will be used in the following labs:
1. Identify the following components of your training environment:
• Windows server 1
• Windows server 2
• Attached storage configuration
• Network configuration
Familiarizing with the lab environment

Windows Server 1 – this will host one instance of Storage Mirroring
Windows Server 2 – this will host another instance of Storage Mirroring
For all labs, you will team up in groups of two students running one pair of Windows
servers. This will allow all students to perform all lab tasks.

Identify the servers

For the following lab activities, the manuals will only refer to “Windows Server 1”
and “Windows Server 2”. Work with your lab partner to decide whose host system
will fulfill which role. If you have documented this information already then please
refer to that documentation.
Windows Server 1
Name: ……………………………………………..
2 NICs installed ? O YES O NO
Type of NIC 1 ……………………………………………..

IP-address NIC 1 ……………………………………………..
Subnet mask NIC 1 ……………………………………………..
Gateway address NIC 1 ……………………………………………..
DNS Server NIC 1 ……………………………………………..
Type of NIC 2 ……………………………………………..

IP-address NIC 2 ……………………………………………..
Subnet mask NIC 2 ……………………………………………..
DNS Server NIC 2 ……………………………………………..
Operating system ……………………………………………..

Operating system service pack ……………………………………………..
Domain ……………………………………………..
Disk Space / Partition Layout ……………………………………………..
……………………………………………..
……………………………………………..
……………………………………………..
OS administrator login ……………………………………………..
OS administrator password ……………………………………………..
Other Software installed ……………………………………………..
……………………………………………..
……………………………………………..
Windows Server 2
Name: ……………………………………………..
2 NICs installed ? O YES O NO
Type of NIC 1 ……………………………………………..

IP-address NIC 1 ……………………………………………..
Subnet mask NIC 1 ……………………………………………..
DNS Server NIC 1 ……………………………………………..
Type of NIC 2 ……………………………………………..

IP-address NIC 2 ……………………………………………..
Subnet mask NIC 2 ……………………………………………..
DNS Server NIC 2 ……………………………………………..
Operating system ……………………………………………..

Operating system service pack ……………………………………………..
Domain ……………………………………………..
Disk Space / Partition Layout ……………………………………………..
……………………………………………..
……………………………………………..
……………………………………………..
OS administrator login ……………………………………………..
OS administrator password ……………………………………………..
Other Software installed ……………………………………………..
……………………………………………..
……………………………………………..

Retrieve software and tools

Your instructor will provide you either with a CD or the login information for a
network share to download the software onto your server.
Also, your instructor will provide you with an Evaluation key to be able to activate HP
StorageWorks Storage Mirroring for a 30-days period.
30-day evaluation code : eval
In case you are working on remote equipment or in the HPVL:

Network share for downloading the installation files:
……………………………………………...............................................................
Network share login ……..………………………………………..
Network share password …………..…………………………………..
In case you are using this remote share, follow this procedure:
2. Login to your Server (Windows 1 or 2)
3. Create the following directory:
C:\OVSM_install
4. Copy all files from the network share into this directory
In case you are using an installation CD, follow this procedure:
5. Insert the Storage Mirroring installation CD into the CD-drive of your Server
(Windows 1 or 2)

Installing Storage Mirroring

Use these instructions if you are installing Storage Mirroring for the first time or if you
have completely uninstalled any previous version of Storage Mirroring.
1. Close any open applications.
2. You may need to extract the zip file to a local drive. Open the directory that
you extracted the files in to.
3. Start the installation by double clicking setup_1819.exe (or similar).
Note
If you are using the HPVL the zip file is located at: Z:\SWSM\
4. When the Storage Mirroring installation program begins, the Welcome screen is
displayed. Click Next to continue.
5. Review and accept the Storage Mirroring license agreement to continue with the
installation program. Click Next to continue.
6. On the Storage Mirroring Setup dialog box, there are two selections available:
• Client and Server Components—Installs the Storage Mirroring server and
client components on the local machine.
• Client Components Only—Installs the Storage Mirroring client on the local
machine.
Select Client and Server Components and click Next to continue.
7. Select the type of Storage Mirroring installation.
• Complete—All program features will be installed.
• Custom—Allows you to choose which program features will be installed.
Select Complete and click Next to continue.

You will be prompted to enter your User Name, Organization, and Activation Code.
The code is a 16-character, alphanumeric activation code which applies the
appropriate Storage Mirroring license to your installation. Enter the activation code
“eval” and click Next to continue.
Note
If you have entered an incorrect or blank activation code, you will be prompted
that the code is incorrect and that the Storage Mirroring source and target
modules will not load. When prompted to continue, select Back and reenter your
activation code.
If you have entered an evaluation code, the expiration date will be displayed and
you will be prompted that the Storage Mirroring source and target modules will
not load after that date. When prompted to continue, select Next to continue.
8. Review the registration information and confirm that it is accurate by clicking
Next.
If you click Back, you will be returned to the registration information screen to
correct the information.
9. Storage Mirroring uses system memory to store data in queues.
Specify the maximum amount of system memory to be used for the Storage
Mirroring queues.
Set this value to 256MB and click Next to continue.
Note
The default setting is 128 MB. If you set it lower, Storage Mirroring will use less
system memory, but you will queue to disk sooner which may impact system
performance. If you set it higher, Storage Mirroring will maximize system
performance by not queuing to disk as soon, but the system may have to swap
the memory to disk if the system memory is not available. In general, the amount
of memory Storage Mirroring and other applications on the server are
configured to use should be less than the amount of physical memory on the
system to prevent low memory conditions.

10. When the Storage Mirroring system memory queue is exhausted, Storage
Mirroring will queue to disk.
Specify the size and location of the disk queue.
Accept the default Disk Queue Folder location and leave the default entry for
Unlimited Maximum Disk Space Usage
Note
By default, the disk space is set to Unlimited which will allow the queue usage to
automatically expand whenever the available disk space expands.
11. Click Next to continue.

12. The Storage Mirroring security information screen appears next. Review this
information and click Next to continue with the installation.
13. If you are satisfied with the selections you have made and are ready to begin
copying the Storage Mirroring files, click Install.
14. After the files have completed copying, click Finish to exit the installation
program.
Note
If you do not restart your computer when prompted, you must reboot the system
prior to starting Storage Mirroring.

15. Reboot the machine, if you have not already done so.
16. After the server has rebooted and you have logged in again, open the Storage
Mirroring Management Console by selecting Start, Programs, Storage
Mirroring, Management Console.
17. When the Welcome screen appears, mark Don’t display this startup screen
again and click Cancel.
18. Log in to your machine by double-clicking the machine in the left pane of the
Management Console. Notice the security icon changes after you have logged
in.
19. Exit out of the Management Console.
Congratulations, you have successfully installed Storage Mirroring.


SWSM Basic Operations
Module 13 — Lab 2
Objectives
set up replication
Requirements
This exercise requires the following resources:
D:\Utilitiess\AllMyData directory with three text files on the source
machine
F:\RepSetTest directory with a test file to add to the replication set
You may choose not to use these drive letters.

Replication sets and connections

1. Log on to your servers (Windows 1 and Windows 2)
2. If not already existing, create the following directories:
D:\Utilities\AllMyData
Create 3 files in this directory named ValuedDoc.txt, ValuedDoc2.txt, and
ValuedDoc3.txt
F:\RepSetTest
Create one file in this directory named test.doc
During this lab, each student in the group should use the server of the other
student in their group as a replication target.
3. Using My Computer or Explorer, look for the following two files in
C:\Program Files\StorageWorks\Storage Mirroring.
a. dbltake.db
b. connect.sts
4. Did you find the files?

O YES O NO
These files are associated with the Storage Mirroring ‘Replication Set’
and are saved to this location when the ‘Replication Set’ is first created.
5. Open the Storage Mirroring Management Console by selecting Start, Programs,
Storage Mirroring, Management Console.
6. Log in to your machine by double-clicking the machine in the left pane of the
Management Console. Notice the security icon changes after you have logged
in.

7. Create a replication set called MyData. Include the \Utilities\AllMyData

folder in your replication set.
a. To create a replication set first right click on the host where the data to be
replicated resides and click New and then Replication Set as shown in the
graphic.
b. When you have named the Replication Set find the folder that you wish to
replicate and click in the adjacent box to add a tick. If you select this folder
now it will show blue highlighted and in the content pane you will see the
folder contents also ticked:

c. Right click on the Replication set name and choose Save as shown above.
When you save the replication set it creates (or updates in the case of
modifying an existing replication set) the file DblTake.db.
8. After saving your replication set, look again for the dbltake.db and
connect.sts files.
9. Did you find the files?
O YES O NO
10. Why?
…………………………………………………………………………………..
11. Establish a connection between your source and another machine. Use the All-
to-One mapping but change the D: drive to the G: drive. (The target path
should be G:\SourceServer\MyData\D\.)
a. To establish a connection you should right click on the replication set and
select Connection Manager

b. Select the Replication Set, Target Server and modify the Target Path as
specified above.
c. If there is more that 1 route to the Target Server then you may alter the
network path used for replication.
d. Click Connect to complete the process.

12. After the connection is established, monitor the status of mirroring using the
following columns in the right pane of the Management Console.
• Mirror Status—Calculating, percentage of completion, then Idle
• Sent Bytes
• Sent Mirror Bytes
• Remaining Mirror Bytes
13. Complete the following steps on the target machine
a. Using My Computer or Explorer on the target, look for
SourcServerName.db in C:\Program
Files\StorageWorks\Storage Mirroring. This is a copy of the
replication set database from the source. It is a real-time copy of
dbltake.db.
b. Look in G:\SourceServer\MyData\D\. There should be three files
(ValuedDoc.txt, ValuedDoc2.txt, and ValuedDoc3.txt). This
confirms that mirroring of the MyData replication set did occur.
c. Leave the Explorer window open on the target machine.

14. Complete the following steps on the source machine

a. Using My Computer or Explorer on the source, go to
D:\Utilities\AllMyData.
b. Open a second Explorer window on the source and go to
F:\RepSetTest.
c. Tile your two Explorer windows and the Management Console so that you
can see all three of them.
d. Create a change in the replication set by adding a new document to the
\AllMyData directory. To do this drag and drop, test.doc from
F:\RepSetTest to D:\Utilitys\AllMyData.
e. In the Management Console, monitor the following statistics.
Replication Status—Will display Ready before you begin, may change
to Replicating while transmitting the test.doc file to the target, then
return to Ready when complete.
Sent Bytes
Queued Replication Bytes
Sent Replication Bytes
15. On the target, look at the open Explorer window and see the test.doc file
appear.
16. On the source, from the open Explorer window showing
D:\Utilities\AllMyData, delete one of the files.
17. On the target, look at the open Explorer window and see the deleted file
disappear.
18. On the source, disconnect the connection by right-clicking on it and selecting
Disconnect.
19. Close the Management Console and the open Explorer windows.

Further exploration
1. Create a new replication set but this time when you create the initial connection
in ‘Connection Manager’ go to the ‘Bandwidth’ tab and limit the bandwidth for
replication traffic to 128Kbps. You might even wish to try scheduling a
bandwidth limit.
2. Play around with the compression settings for replication – how much
compression did you achieve?
.................................................................................................................
Congratulations, you have successfully created a replication set, made a connection,

and mirrored & replicated data.


B-series Trunking
Module 14 – Lab 2
Objective
After completing this lab, you should be able to enable and disable switch trunking
on B-series switches.
HPVL instruction
You will be working with the other administrator in your ‘new’ fabric. Fabric A
comprises Core switch A and Edge switches A1 & A2 and Fabric B consists of Core
switch B and Edge switches B1 & B2. Find your lab partner first and work together
for this lab exercise.
Requirements
You have completed the previous labs
The Edge switches have inter-switch links (ISL) on ports 0 & 1 which are
connected to the Core switches. Switches are all B-series.
Ports 0, 1, 2 and 3 are disabled on your edge switch

Enabling and disabling trunking on switches

Enabling trunking
If you have not already disabled ports 0-3 then please do so now (or all of your ISL
ports if they are NOT ports 0-3). Your fabric will now be segmented.
1. Ensure trunking is disabled on each of your switches by issuing the following

command: switchcfgTrunk 0.
2. Open a Port Admin window from Web Tools. Notice that the Trunking Enabled
column shows ‘false’ for every port. You may need to switch to Advanced Mode
to see this.
3. Issue a licenseshow to ensure that a trunking license is installed on each of your

switches.
Note
If the trunking license is not loaded on one of your switches, request the license
from your instructor.
4. Enable ports 0 & 1 for your Edge switch.
Note
If you are using the HPVL then you will also need to enable the Core switch ports
0 &1 for connection to Edge switch 1 and core switch ports 4 & 5 for connection
to Edge switch 2.

B-series Trunking
5. Issue the islShow command from your Edge switch. How many ISLs are shown?
.................................................................................................................
6. Enable trunking on all of the ISL ports of each switch by issuing the following
commands on both switches:
(Where the first number refers to the port area reference and after the comma a
0 disables trunking and a 1 enables trunking on the specified port).
portCfgTrunkPort 0, 1
portCfgTrunkPort 1, 1
Note
You can enable trunking on all ports by executing the switchcfgTrunk 1
command. If you are using the hpvl you may wish to do this for your Core
switch.
7. switchShow and trunkShow are commands that display trunking membership

information or trunk groups. The first configured ISL that comes up in a group is
the trunk master. Execute these two commands on each switch and record the
trunking master port here:
.................................................................................................................
8. The other ISLs in a trunk are slave links. Which commands could you use to
identify the slave trunking port links?
.................................................................................................................
.................................................................................................................
.................................................................................................................
9. portCfgShow shows if the port is enabled for trunking. Execute the command
and record the results here.
.................................................................................................................
10. Using the output from the islshow command, what is the bandwidth of the ISL?
.................................................................................................................

Displaying switch information

11. Execute the switchShow command and determine the Worldwide Name
(WWN) of the destination fabric you have trunked to. Record the WWN here.
.................................................................................................................
Additional task
You now have a trunk from both edge switches to your core switch. You may wish to
present a MSA volume to a host across the fabric and then use IOMeter again to test
the cross-fabric performance.
Finally you should enable ports 2 and 3 again.
You have completed this lab successfully.

Uc434s.c.02 Lab PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Uc434s.c.02 Lab PDF

Uploaded by

Copyright:

Available Formats

Accelerated SAN Essentials

UNIX® is a registered trademark of The Open Group.

Export Compliance Agreement

UC434S C.02 © 2009 Hewlett-Packard Development Company, L.P. L1 - 1

L1 - 2 © 2009 Hewlett-Packard Development Company, L.P. UC434S C.02

ILO/MP IP 192.168.136.220 192.168.136.221

UC434S C.02 © 2009 Hewlett-Packard Development Company, L.P. L1 - 3

HBA 0 Node WWN

HBA 1 Node WWN

HBA 0 Node WWN

HBA 1 Node WWN

HBA 0 Node WWN

HBA 1 Node WWN

HBA 0 Node WWN

HBA 1 Node WWN

Array name MSA1500 CS SGA050502F

L1 - 6 © 2009 Hewlett-Packard Development Company, L.P. UC434S C.02

UC434S C.02 © 2009 Hewlett-Packard Development Company, L.P. L1 - 7

L1 - 8 © 2009 Hewlett-Packard Development Company, L.P. UC434S C.02

UC434S C.02 © 2009 Hewlett-Packard Development Company, L.P. L1 - 9

Fabric Switch Documentation

Switch name Domain ID

L1 - 10 © 2009 Hewlett-Packard Development Company, L.P. UC434S C.02

Fabric Switch Documentation

Switch name Domain ID

UC434S C.02 © 2009 Hewlett-Packard Development Company, L.P. L1 - 11

Fabric Switch Documentation

Switch name Domain ID

L1 - 12 © 2009 Hewlett-Packard Development Company, L.P. UC434S C.02

Fabric Switch Documentation

Switch name Domain ID

UC434S C.02 © 2009 Hewlett-Packard Development Company, L.P. L1 - 13

Fabric Switch Documentation

Switch name Domain ID

L1 - 14 © 2009 Hewlett-Packard Development Company, L.P. UC434S C.02

Fabric Switch Documentation

Switch name Domain ID

You have successfully completed this lab.

UC434S C.02 © 2009 Hewlett-Packard Development Company, L.P. L1 - 15

L1 - 16 © 2009 Hewlett-Packard Development Company, L.P. UC434S C.02

UC434S C.02 © 2009 Hewlett-Packard Development Company, L.P. L3.1 – 1

Connecting to a fabric switch

L3.1 – 2 © 2009 Hewlett-Packard Development Company, L.P. UC434S C.02

The Web Tools interface will launch:

UC434S C.02 © 2009 Hewlett-Packard Development Company, L.P. L3.1 – 3

L3.1 – 4 © 2009 Hewlett-Packard Development Company, L.P. UC434S C.02

UC434S C.02 © 2009 Hewlett-Packard Development Company, L.P. L3.1 – 5

L3.1 – 6 © 2009 Hewlett-Packard Development Company, L.P. UC434S C.02

Port status and statistics

UC434S C.02 © 2009 Hewlett-Packard Development Company, L.P. L3.1 – 7

Switch Admin window

L3.1 – 8 © 2009 Hewlett-Packard Development Company, L.P. UC434S C.02

Use the Performance Monitor button to graphically display throughput (megabytes

UC434S C.02 © 2009 Hewlett-Packard Development Company, L.P. L3.1 – 9

L3.1 – 10 © 2009 Hewlett-Packard Development Company, L.P. UC434S C.02

Accessing the switch using the Telnet

1. Launch Web Tools.

6. Enter a username and password.

UC434S C.02 © 2009 Hewlett-Packard Development Company, L.P. L3.1 – 11

L3.1 – 12 © 2009 Hewlett-Packard Development Company, L.P. UC434S C.02

UC434S C.02 © 2009 Hewlett-Packard Development Company, L.P. L3.1 – 13

L3.1 – 14 © 2009 Hewlett-Packard Development Company, L.P. UC434S C.02

Logging into a fabric switch using Telnet