AN304XSTUDHINT

V8.
cover
Front cover
Power Systems for AIX Virtualization I: Implementing

Virtualization
(Course code AN30)
Student Exercises
with hints
ERC 4.0
Student Exercises with hints
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International
Business Machines Corp., registered in many jurisdictions worldwide.
The following are trademarks of International Business Machines Corporation, registered in
many jurisdictions worldwide:
Active Memory
BladeCenter
DS8000
Enterprise Storage Server
HACMP
i5/OS
POWER Hypervisor
Power
PowerVM
POWER7
SystemMirror
AIX 6
DS4000
Electronic Service Agent
Express
IBM Systems Director Active
Energy Manager
Notes
Power Systems
PowerHA
POWER6
pSeries
Tivoli
AIX
DS6000
EnergyScale
Focal Point
Initiate
Passport Advantage
Power Systems Software
PowerPC
POWER7+
Redbooks
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or
both.
Windows and Windows NT are trademarks of Microsoft Corporation in the United States,
other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Java and all Java-based trademarks and logos are trademarks or registered trademarks
of Oracle and/or its affiliates.
Other product and service names might be trademarks of IBM or other companies.
March 2013 edition

The information contained in this document has not been submitted to any formal IBM test and is distributed on an as is basis without
any warranty either express or implied. The use of this information or the implementation of any of these techniques is a customer
responsibility and depends on the customers ability to evaluate and integrate them into the customers operational environment. While
each item may have been reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results will
result elsewhere. Customers attempting to adapt these techniques to their own environments do so at their own risk.
Copyright International Business Machines Corporation 2009, 2013.

This document may not be reproduced in whole or in part without the prior written permission of IBM.
Note to U.S. Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to restrictions
set forth in GSA ADP Schedule Contract with IBM Corp.
V8.0
TOC
Contents
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Exercises description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Exercise 1. Power Systems documentation overview . . . . . . . . . . . . . . . . . . . . . . . 1-1
Exercise 2. Processor virtualization configuration . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Exercise 3. Integrated Virtual Ethernet configuration . . . . . . . . . . . . . . . . . . . . . . . 3-1
Exercise 4. Virtual Ethernet adapter configuration . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Part 1: Configuring a virtual Ethernet connection (simple configuration) . . . . . . . . 4-2
Part 2: Configuring additional VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Exercise 5. Virtual I/O Server and client partition configuration . . . . . . . . . . . . . . 5-1
Exercise 6. SEA failover setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Part 1: Setting the virtual Ethernet adapters and trunk priority . . . . . . . . . . . . . . . . 6-5
Part 2: Create the SEA failover feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Part 3: Testing the SEA failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Part 4: (Optional) Setting the VIO server IP address on an additional virtual Ethernet
adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
Exercise 7. Dual VIO server configuration with MPIO in the client partition . . . . . 7-1
Part 1: Create the VSCSI client and server adapters . . . . . . . . . . . . . . . . . . . . . . . 7-5
Part 2: Create the virtual target device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Part 3: MPIO failover tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Part 4: (Optional) Working with MPIO paths' priority . . . . . . . . . . . . . . . . . . . . . . 7-15
Exercise 8. Virtual Fibre Channel adapter configuration . . . . . . . . . . . . . . . . . . . . . 8-1
Exercise 9. Manage service events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Part 1: Service Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Part 2: SFP: Check and close events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
Exercise 10. PowerVM system maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Part 1: Update the Virtual I/O Server software . . . . . . . . . . . . . . . . . . . . . . . . . . .
Part 2: Using viosbr to backup the virtual and logical configuration . . . . . . . . . . .
Part 3: Using cron to schedule tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10-1
10-2
10-4
10-7
Exercise 11. (Optional) File-backed virtual disk and virtual media repository
configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Part 1: Create a file-backed virtual disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Part 2: Create a virtual media repository and a blank virtual DVD-RAM . . . . . . . 11-7
Copyright IBM Corp. 2009, 2013

Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Contents
iii
Part 3: Backup/restore your client LPAR OS to the virtual optical media device . 11-8
iv
Power Virtualization I

V8.0
TMK
Trademarks
The reader should recognize that the following terms, which appear in the content of this
training document, are official trademarks of IBM or other companies:
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International
Business Machines Corp., registered in many jurisdictions worldwide.
The following are trademarks of International Business Machines Corporation, registered in
many jurisdictions worldwide:
Active Memory
BladeCenter
DS8000
Enterprise Storage Server
HACMP
i5/OS
POWER Hypervisor
Power
PowerVM
POWER7
SystemMirror
AIX 6
DS4000
Electronic Service Agent
Express
IBM Systems Director Active
Energy Manager
Power Systems
PowerHA
POWER6
pSeries
Tivoli
AIX
DS6000
EnergyScale
Focal Point
Passport Advantage
Power Systems Software
PowerPC
POWER7+
Redbooks
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or
both.
Windows and Windows NT are trademarks of Microsoft Corporation in the United States,
other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Java and all Java-based trademarks and logos are trademarks or registered trademarks
of Oracle and/or its affiliates.
Other product and service names might be trademarks of IBM or other companies.

Trademarks
vi

V7.0.2
pref
Exercises description
Exercise instructions: This section describes what you should
accomplish. There are no definitive details regarding how to perform
the tasks. You are given the opportunity to work through the exercise
given what you learned in the unit presentation.
Exercises description

vii
viii

V7.0.2
EXempty
Exercise 1. Power Systems documentation

overview
(with hints)
What this exercise is about

In this exercise, students find the key documentation that supports the
objectives of this course.
What you should be able to do

At the end of this exercise, you should be able to:
Access the documentation for IBM POWER6 and POWER7
processor-based servers and partitioning
Introduction
In this exercise, you will find the key pieces of documentation that
cover the configuration of LPARs on IBM POWER6 and POWER7
processor-based servers.
Requirements
This workbook.
A student workstation with IP connectivity to the Internet and
equipped with a web browser.
Exercise 1. Power Systems documentation overview

1-1
Exercise instructions with hints

Preface
All exercises depend on the availability of specific equipment in your classroom. You will
need a computer system configured with a network connection that can access an HMC
and the corresponding system and LPARs.
The web page URLs in this exercise were correct when this course was written. By
nature, web pages tend to change over time; therefore, ask your instructor if you have
trouble navigating the websites.
Access IBM Systems hardware and AIX documentation

In this exercise, you discover the documentation to support the managed systems and
LPARs. You can refer to this documentation as you work through the rest of the exercises
in this course. This exercise requires Internet access.
Some web addresses or names are subject to modification. If a link does not work exactly
as described or has been changed, notify your instructor.
Hardware information and support

__ 1. Go to http://www.ibm.com. Click the Products tab, then click Systems > Power
Systems (AIX, IBM i, Linux) in the context menu and explore this page. This page
contains information about the current POWER processor-based models. A large
number of links, useful documents, and detailed information are available.
Depending on your interest, click the different links and explore the information that
is available.
__ 2. Go to http://www.ibm.com. Click the Support and downloads tab, follow the
context menu, click Support by products, and then go to Servers & Systems. This
will take you to the Support for IBM Systems page. From the Select product or
service type for support list, select Power. Select a Power System model from the
Hardware drop-down list, and click Go. Explore the page, follow the different links in
the Configuration, Documentation, Diagnostic, and Problem resolution menus.
__ 3. Use the following web address to access the IBM Systems Information Center:
http://publib.boulder.ibm.com/eserver. This page is the entry point for
hardware as well as software information. Click the IBM Systems Hardware
Information Center link.
When you are in the main IBM Systems Hardware Information Center, use the
search option on the left side of the screen to find the topics related to the following
phrases:
Logical partition overview
Partitioning with the HMC
1-2

V7.0.2
EXempty
__ 4. Go to the AIX Information Center. Use the following URL:

http://publib.boulder.ibm.com/eserver
Click AIX Information Center link and, if the next page provides choices, select the
AIX 7.1 link.
When you are at the resulting IBM Systems Information Center page, select AIX
PDFs. This topic contains links to PDF versions of the AIX documentation.
__ 5. Go to the Power Systems Software website and see what is available:
http://www.ibm.com/systems/power/software. Click the PowerVM Virtualization without limits link. Navigate the page and the different tabs.
__ 6. Find Linux information for POWER6 and POWER7 processor-based servers by
visiting this site: http://www.ibm.com/systems/power/software/linux
__ 7. Let your instructor know you have completed the exercise.
End of exercise
Exercise 1. Power Systems documentation overview

1-3
1-4

V7.0.2
EXempty
Exercise 2. Processor virtualization configuration

(with hints)

This exercise covers configuring shared processor partitions and the
advanced processor options. Students use the lparstat command to
see configuration information and statistics specific to micro-partitions.

Configure a micro-partition with shared processor options
Configure virtual processors
Enable and disable SMT on AIX
Configure capped and uncapped partitions
View processor-related configuration and statistics with the
lparstat command
Introduction
In this exercise, you will configure the advanced processor options for
AIX partitions and use tools to view processor-related configuration
and performance information.
Requirements
This workbook.
A computer with a web browser and a network connection to an
HMC running Version 7 configured to support a POWER7
processor-based system.
Utility for running Telnet or SSH.

2-1

Preface
All exercises in this unit depend on the availability of specific equipment. You will
need a computer system connected to the World Wide Web, a web browser, a
Telnet program, and a utility for running SSH. You will also need a managed
system capable of running shared processor partitions. All lab systems need to
be accessible to each other on a network.
All hints are marked by a sign.
The hints in this exercise reflect results obtained on a Power System Model 750
with sixteen 3.0 GHz processors and a partition running AIX V7.1 Technology
Level 1 SP 3. Your system's specific results might differ, but the overall
conclusions should be true for your system.
View system configuration and configure processor options

__ 1. Using Telnet, log in to your assigned LPAR and run the lparstat command. What is
the current configuration of your partition for the following settings?
Type of processors: ____________________
Processor mode: ____________________
SMT: ____________________
Number of logical CPUs: ____________________
Here is an example lparstat command and its output:
# lparstat
System configuration: type=Dedicated mode=Donating smt=4 lcpu=4
mem=2048MB
%user %sys %wait %idle physc vcsw
----- ----- ------ ------ ----- ----0.0
0.4
0.0
99.6 0.25 106895367
Based on the above output, the answers to the above questions are:
Type of processors: Dedicated
Processor mode: Donating
SMT: 4
Number of logical CPUs: 4
__ 2. Shut down your assigned LPAR. You do not need to wait for it to shut down to
continue to the next step.
In the Telnet window to your partition, issue the shutdown -F command.
2-2

V7.0.2
EXempty
__ 3. Using your web browser, connect to your assigned HMC. Log in by typing hscroot.
__ 4. In this step, you will alter the Normal partition profile for your partition.
__ a. Open the Normal profile properties window for your partition.
Go to the Systems Management application on the HMC. Expand the Servers
information, and then show the partition table view for your server.
Select the partition by checking the check box in the Select column.
Choose the Configuration > Manage Profiles task from the Tasks menu or
from the tasks pad. In the pop-up window, check the profile name (Normal), and
choose Edit from the Actions menu.
__ b. Change the profile to use shared processors. Configure the processing units to
be 0.1 minimum, 0.6 desired, and 1.0 maximum. Leave the properties window
open for a few more steps until you have finished configuring the profile.
Click the Processors tab in the Logical Partition Profile Properties window
that pops up.
In the Processing mode box, select the Shared radio button.
In the Processing units box, enter 0.1 for the minimum, 0.6 for the desired, and
1.0 for the maximum parameters.
Do not click the OK button yet.
__ c. Change both the virtual processor minimum setting and the virtual processor
desired setting to 1. (One or both of these values may already be set to 1.) Set
the virtual processor maximum setting to the maximum allowed for the maximum
number of processing units configured in your partition. Do not click the OK
button yet.
On the same Processors tab you used in the last step, enter a 1 in the
Minimum virtual processors field, enter a 1 in the Desired virtual processors
field, and enter a 10 in the Maximum virtual processors field.
On POWER7 hardware, the maximum number of virtual processors allowed is
10 times the value entered for maximum processing units.
__ d. Set the sharing mode to uncapped by clicking the Uncapped check box, and set
the weight to 100. Click the OK button.
On the same Processors tab you used in the last step, click the Uncapped
check box and enter the value of 100 in the Weight box.

2-3
The Processors tab should now look like the example below.
__ 5. Activate your partition with the newly modified Normal profile.

Your logical partition might still be selected from the last operation. If it is not,
click the check box in the Select column to select it.
To activate the partition, access the Operations menu and choose the Activate
task.
On the screen that pops up, the Normal profile should already be highlighted.
Click the Open a terminal window or console session check box, and then
click OK.
__ 6. When your partition has finished booting, log in and use the lparstat command to
check the configuration.
Log in to your partition and run the lparstat command. The output should
reflect the changes you made in the partition profile.
2-4

V7.0.2
EXempty
Here is an example lparstat command and its output that shows the new
settings.
# lparstat
System configuration: type=Shared mode=Uncapped smt=4 lcpu=4
mem=2048MB psize=16 ent=0.60
%user %sys %wait %idle physc %entc lbusy vcsw phint
----- ----- ------ ------ ----- ----- ------ ----- ----0.0
0.0
1.6
98.4 0.00
0.0
12.8 63060
4
__ 7. Log in to the HMC command line using SSH and use the lshwres command to view
the processor settings for the partition. Notice the new processor settings.
The command syntax follows. Replace MSname with the actual managed system
name and lparname with the actual LPAR name.
lshwres -r proc -m MSname --filter "lpar_names=lparname" --level lpar
Here is an example command and its output for the managed system named
sys464 and a partition named sys464_partition1:
hscroot@sys194-hmc:~> lshwres -r proc -m sys464 --filter \
"lpar_names=sys464_partition1" --level lpar
lpar_name=sys464_partition1,lpar_id=1,curr_shared_proc_pool_id=0,curr
_shared_proc_pool_name=DefaultPool,curr_proc_mode=shared,curr_min_pro
c_units=0.1,curr_proc_units=0.6,curr_max_proc_units=1.0,curr_min_proc
s=1,curr_procs=1,curr_max_procs=1,curr_sharing_mode=uncap,curr_uncap
_weight=100,pend_shared_proc_pool_id=0,pend_shared_proc_pool_name=D
efaultPool,pend_proc_mode=shared,pend_min_proc_units=0.1,pend_proc_
units=0.6,pend_max_proc_units=1.0,pend_min_procs=1,pend_procs=1,pen
d_max_procs=10,pend_sharing_mode=uncap,pend_uncap_weight=100,run_pro
c_units=0.6,run_procs=1,run_uncap_weight=100
__ 8. From the console window or from a Telnet session to your logical partition, use the
lparstat AIX command with the -i option and view the information available. Use
the man page for lparstat if you have questions about the output of this command.
The output of the AIX lparstat -i command shows the processor and memory
resources settings for your partition.

2-5
Example lparstat -i output:

Node Name
: sys464_partition1
Partition Name
: sys464_partition1
Partition Number
: 1
Type
: Shared-SMT-4
Mode
: Uncapped
Entitled Capacity
: 0.60
Partition Group-ID
: 32769
Shared Pool ID
: 0
Online Virtual CPUs
: 1
Maximum Virtual CPUs
: 10
Minimum Virtual CPUs
: 1
Online Memory
: 2048 MB
Maximum Memory
: 4096 MB
Minimum Memory
: 1024 MB
Variable Capacity Weight
: 100
Minimum Capacity
: 0.10
Maximum Capacity
: 1.00
Capacity Increment
: 0.01
Maximum Physical CPUs in system
: 16
Active Physical CPUs in system
: 16
Active CPUs in Pool
: 16
Shared Physical CPUs in system
: 16
Maximum Capacity of Pool
: 1600
Entitled Capacity of Pool
: 60
Unallocated Capacity
: 0.00
Physical CPU Percentage
: 60.00%
Unallocated Weight
: 0
Memory Mode
: Dedicated
Total I/O Memory Entitlement
: Variable Memory Capacity Weight
: Memory Pool ID
: Physical Memory in the Pool
: Hypervisor Page Size
: Unallocated Variable Memory Capacity Weight: Unallocated I/O Memory entitlement
: Memory Group ID of LPAR
: Desired Virtual CPUs
: 1
Desired Memory
: 2048 MB
Desired Variable Capacity Weight
: 100
Desired Capacity
: 0.60
Target Memory Expansion Factor
: Target Memory Expansion Size
: Power Saving Mode
: Disabled
2-6

V7.0.2
EXempty
__ 9. Run the lparstat command with an interval of 1 and count of 4. Notice the fields
that are displayed. Without the interval and count arguments, the statistics shown
are from the last boot.
Example lparstat output:
# lparstat 1 4
%user %sys %wait %idle physc %entc lbusy vcsw phint
----- ----- ------ ------ ----- ----- ------ ----- ----0.1
0.8
0.0
99.1 0.01
1.8
0.5
332
0
0.0
0.6
0.0
99.4 0.01
1.3
0.0
312
0
0.0
0.8
0.0
99.2 0.01
1.6
0.0
278
0
0.0
0.6
0.0
99.4 0.01
1.1
0.0
221
0
__ 10. What is the available shared processing pool statistic that might or might not display
in the lparstat output? If it does not display in the lparstat output on your system,
configure it so that it does. How do you do this?
Once you reconfigure the partition, run lparstat again to make sure the statistic
displays in the output.
The statistic is app. It is not visible in the lparstat output shown in the hints for
the previous step.
To configure the partition to show this app statistic, go to the HMC Systems
Management application and back to the LPAR table view. Select your partition
and choose Properties on the Tasks menu or from the Tasks pad. Click the

2-7
Hardware tab. Click the Processors tab. Click the Allow performance
information collection check box, as shown in this example:
Click OK.
Run lparstat again in your partition. You should see a new app field, which is
the amount of available (that is, free) shared processing units in the shared
processor pool. If the app statistic does not appear in the lparstat output, make
sure you enabled it correctly. If you confirm that you enabled it correctly and it
still does not appear, shut down your partition and reactivate it.
Here is an example lparstat output with this app field:
# lparstat 1 4
%user %sys %wait %idle physc %entc lbusy
app vcsw phint
----- ----- ------ ------ ----- ----- -------- ----- ----0.1
0.8
0.0
99.2 0.01
1.6
0.0 15.00
234
0
0.0
0.6
0.0
99.4 0.01
1.3
0.0 14.23
279
0
0.0
0.6
0.0
99.4 0.01
1.2
2.4 14.99
220
0
0.0
0.6
0.0
99.4 0.01
1.1
0.0 15.18
226
0
__ 11. Disable simultaneous multi-threading (SMT); then run the lsdev -c processor
command to list the virtual processors. You should see the output like this:
# lsdev -c processor
proc0 Available 00-00 Processor
2-8

V7.0.2
EXempty
The output shown above lists one available processor called proc0. Your LPAR has
0.60 processing units. Can you explain what this output of the lsdev command
means?
To disable simultaneous multi-threading, use the smtctl -m off command.
The lsdev command lists the processors that the operating system sees. When
a partition is using dedicated processors, lsdev shows physical processors.
When a partition is using shared processors, lsdev shows virtual processors
(that is, the number of physical processors the partition thinks it has). Since your
partition is now running with shared processors and has only one virtual
processor, the lsdev -c processor command will report one available processor.
Also, observe the logical processors (lcpu) using the lparstat command. There
should be only 1 lcpu per virtual processor when SMT is disabled:
# lparstat
System configuration: type=Shared mode=Uncapped smt=Off lcpu=1
__ 12. Enable 2-way and 4-way simultaneous multi-threading, and run the lsdev -c
processor command again. Is the output different? Why or why not?
The lsdev command output is the same because this is a shared processor
partition and it lists virtual processors (not logical processors).
__ 13. Run the lparstat command to list the logical processors. Observe the 2-way and
4-way simultaneous multi-threading (SMT) supported by POWER7.
POWER7 supports 2-way and 4-way SMT. To enable 2-way SMT, use the
smtctl -t 2 command. Observe the logical processor (lpcu) count using the
lparstat command:
# lparstat
System configuration: type=Shared mode=Uncapped smt=On lcpu=2
To enable 4-way SMT, use either the smtctl -m on command or the smtctl -t
4 command. Again, observe the lparstat output:
# lparstat
__ 14. Dynamically add two more virtual processors. Run the lsdev -c processor
command again. What does the output show?
To dynamically add two more virtual processors, go to the Systems
Management application on the HMC. In the LPAR table view, select the
partition and choose Dynamic Logical Partitioning > Processor > Add or
Remove on the menu.

2-9
In the window that opens, enter 3 in the Virtual processors box in the Assigned
column. Click OK.
Go back to your partition's terminal window, and run lsdev -c processor again.
The output should look similar to this:
# lsdev -c processor
Now AIX sees three processors. These are the virtual processors.
__ 15. Run the lparstat command again with no options. How many logical processors
are in the partition?
The lparstat command will show twelve logical processors (lcpu=12) because
there are three virtual processors configured in the partition and simultaneous
multi-threading 4 is enabled. There are four logical processors for each virtual
processor. We know that simultaneous multi-threading is enabled because the
lparstat command shows smt=4 in the configuration line at the top.
# lparstat
app vcsw phint
----- ----- ------ ------ ----- ----- -------- ----- ----0.0
0.0
0.1
99.9 0.00
0.0
0.9 13.69 465840
5
Overviewing shared processor utilization

__ 16. Open a Telnet session to your LPAR, and run the following command to put a
processing load on the system:
yes | sum &
You can minimize this window. Leave this command running for the rest of the
exercise.
__ 17. Open a second Telnet session or a console window for your partition. Run the
following command:
lparstat 1 4
Look at the %entc and physc columns value. What do you notice?
2-10 Power Virtualization I

V7.0.2
EXempty
Example command and output:

# lparstat 1 4
app vcsw phint
----- ----- ------ ------ ----- ----- -------- ----- ----57.2
2.8
0.0
39.9 1.34 224.1
16.6 13.45 13744
0
57.3
2.7
0.0
39.9 1.34 223.7
16.5 14.56 13624
0
57.3
2.7
0.0
40.0 1.34 224.1
15.8 13.74 13740
0
57.3
2.7
0.0
40.0 1.34 223.9
15.4 11.70 13678
0
Some things to notice include:
This is an uncapped partition because the total %entc exceeds 100%.
The %entc value is above 220% of the LPAR capacity entitlement of 0.6.
The physc value is approximately 1.34 and corresponds to the physical
CPU capacity consumed by your LPAR. When you are using 1.34 physc
with a configured entitled capacity of 0.6, it is correct to see the %entc at
approximately 224%.
__ 18. From the output of lparstat 1 4, what is the capacity of the shared processor
pool? Also, are there any excess cycles available? How could you answer this
question?
The psize value displayed in the initial configuration line of the output indicates
the number of processors in the shared pool. As an alternative, you can look at
this line in the lparstat -i output:
Active CPUs in Pool
: 16
To find out if there are available cycles in the pool, you can run lparstat 1 4
and look at the value in the app column to see if there is any available shared
processor pool capacity. Here is an example command and its output:
# lparstat 1 4
app vcsw phint
----- ----- ------ ------ ----- ----- -------- ----- ----57.2
2.8
0.0
40.0 1.34 222.5
16.2 13.28 13521
0
57.1
3.0
0.0
39.9 1.34 223.8
3.6 13.17 2252
0
57.3
2.8
0.0
39.9 1.34 223.7
16.6 13.17 13680
0
57.6
2.8
0.0
39.6 1.34 223.6
17.1 13.81 13707
0

2-11
In the lparstat with an interval output, we see that app is not zero. The
available (unused) capacity in the shared processor pool depends on the
consumption of all the configured LPARs using the shared processor pool on
your system. Depending on what activity is running on the other LPARs, the app
column value can be different from the example.
In this example, the app column value shows that approximately 13 processor
units are available in the shared processor pool.
__ 19. From the HMC Systems Management application, dynamically change the virtual
processor setting back to one. Run the lparstat 1 4 command again. What do you
notice? Can you explain the physc value?
Example command and its output:
# lparstat 1 4
app vcsw phint
----- ----- ------ ------ ----- ----- -------- ----- ----72.7
2.9
0.0
24.4 1.00 166.6
30.0 13.56 22902
6
71.1
2.8
0.0
26.1 1.00 166.6
30.8 13.86 23658
0
71.1
2.8
0.0
26.2 1.00 166.6
30.0 14.26 23694
6
71.1
2.9
0.0
26.1 1.00 166.6
31.5 13.74 23574
0
Some things to notice include:
- %entc decreased and is at approximately 166%. This is consistent with a
partition configured as uncapped where it has one virtual processor and has
an entitled capacity of 0.6. It is using a physc of 1.00, which is consistent with
using the entire capacity of one virtual processor for this uncapped partition.
When you are using 1.0 physc but are configured for 0.6 entitled capacity, it is
correct to see the %entc value at 166%.
__ 20. Your assigned LPAR should still be running the "yes | sum &" command. In the
second terminal window to your partition, run the lparstat 1 4 command; then
dynamically change your partition to be a capped mode partition. In the second
terminal window to your partition, run the lparstat 1 4 command again. Compare
the two outputs. What do you notice?

V7.0.2
EXempty
Example lparstat 1 4 command output when the partition is uncapped:

# lparstat 1 4
app vcsw phint
----- ----- ------ ------ ----- ----- -------- ----- ----72.3
2.9
0.0
24.7 1.00 166.2
32.2 13.27 23694
6
73.6
3.3
0.0
23.1 1.00 166.6
31.8 14.51 23541
6
71.0
2.8
0.0
26.2 1.00 166.6
31.5 12.86 23652
3
72.4
2.9
0.0
24.7 1.00 166.6
31.2 13.47 23649
0
To change the partition from uncapped to capped, go to the HMC Systems
Management application. In the LPAR table view, select your partition and
choose Dynamic Logical Partitioning > Processor > Add or Remove. In the
window, uncheck the Uncapped check box. Click OK.
Example lparstat 1 4 command output when the partition is capped:
# lparstat 1 4
System configuration: type=Shared mode=Capped smt=4 lcpu=4 mem=2048MB
psize=16 ent=0.60
app vcsw phint
----- ----- ------ ------ ----- ----- -------- ----- ----70.8
3.1
0.0
26.1 0.60 99.9
31.2 13.60 14448
3
70.9
3.2
0.0
26.0 0.60 100.0
31.8 14.45 14469
0
70.9
3.0
0.0
26.0 0.60 100.0
30.2 14.12 14433
0
71.1
3.0
0.0
25.9 0.60 100.0
31.0 14.36 14283
0
What you should notice about the two outputs is that the physc in the capped
partition only goes as high as the entitled capacity, which is 0.60. The %entc now
does not go higher than 100% (or much higher due to rounding issues).
__ 21. This ends the exercise. Stop the "yes | sum &" command, and close any terminal
windows that are open. Contact your instructor for instructions on what to do next.
End of exercise

2-13

V7.0.2
EXempty
Exercise 3. Integrated Virtual Ethernet

configuration
(with hints)

This exercise has students configure a partition to use a logical host
Ethernet adapter (LHEA) logical port as its network device. The host
Ethernet adapter (HEA) is also referred to as the Integrated Virtual
Ethernet (IVE) adapter.

Add a logical port from the HEA to a partition's configuration
Configure networking on the LHEA port interface
Introduction
In this exercise, you will configure a LHEA logical port in a partition,
configure the interface for this port, and run a network performance
command to view statistics about the logical port.
Requirements
This workbook.
A workstation with a web browser connected to a network.
A managed system connected to the same network as the
workstations.
A system from which to start an SSH session to the HMC.
Exercise 3. Integrated Virtual Ethernet configuration

3-1

Preface
All exercises of this unit depend on the availability of specific equipment in your
classroom. You will need:
- A computer system with a web browser.
- A managed system configured with at least one partition per student.
- A system from which to execute remote commands to the HMC (through
SSH): All lab systems need to be accessible to each other on a network.
Hints are provided for exercises in case you need them and to provide solutions
for the exercise steps. All hints are marked by a sign.
View managed system and LPAR configuration

In this exercise, the goal is to configure your assigned LPAR to use an HEA logical port and
configure it so that it has network connectivity.
__ 1. Connect to the HMC using a web browser. Login as hscroot.
__ 2. Go to the Systems Management application on the HMC. Go to the LPAR table
view. Do not select any LPAR.
__ 3. Open the task to see the HEA configuration by making sure no partitions are
selected, and then selecting the Hardware Information > Adapters > Host
Ethernet task.
Note that in the lab configuration, the machines are single node systems; therefore,
there is only one HEA. You should get a window similar to the following example:
3-2

V7.0.2
EXempty
__ 4. Select the Physical Port Location Code T1 as follows:
Then select the Configure button and view the various attributes of the HEA. Keep
the default values. How many logical ports per physical port group are available to
be configured on your system?
You can tell by looking at the MCS value in the Host Ethernet Adapters window.
Given the example shown in the hints above, the MCS value is two and there is
no logical port assigned to an LPAR; therefore, available logical port IDs are one
through eight.
You might want to select the Help button to get additional information
about these attributes.
Select OK or Cancel to exit.
__ 5. Close the Host Ethernet Adapters window.
__ 6. Open a terminal window to your LPAR, and run the lsdev -c adapter -S a AIX
command to see if there are any available host Ethernet devices. There should not
be any. Use the -S a flag so that devices listed as Defined do not appear in the
lsdev output.

3-3
With only your partition selected, run the Console Window > Open Terminal
Window task. Log in as root.
Here is an example of the command and output that shows no HEAs. You should
only see physical Ethernet adapters:
# lsdev -c adapter -S a
ent0 Available 00-00 2-Port 10/100/1000 Base-TX PCI-Express Adapter
(14104003)
(14104003)
fcs0 Available 01-00 8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)
fcs1 Available 01-01 8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)
vsa0 Available
LPAR Virtual Serial Adapter
__ 7. Shut down your assigned LPAR. You do not have to wait for it to shut down to go to
the next step.
Run the shutdown -F AIX command.
__ 8. Edit your LPAR's Normal profile to include an HEA logical port. Use the following
information for assigning an LHEA port:
Table 1: LHEA port assignment
Student LPAR Name
HEA
HEA
number:
Physical Physical
Port ID Port Group
First managed system
student 1
partition1
0
1
student 2
partition2
0
1
student 3
partition3
0
1
student 4
partition4
0
1
student 5
partition5
0
1
student 6
partition6
0
1
Second managed system
student 7
partition7
0
1
student 8
partition8
0
1
student 9
partition9
0
1
student 10 partition10
0
1
0
1
0
1
HEA
logical
Port ID
1
2
3
4
5
6
1
2
3
4
5
6
With only your partition selected, run the Configuration > Manage Profiles
task.
Select the Normal profile, and then run Edit on the Actions menu.
Go to the Logical Host Ethernet Adapter (LHEA) tab.
3-4

V7.0.2
EXempty
Select the physical port ID 0 of the port group 1. Here is an example where
physical port ID 0 is selected:
Click Configure.
Select the logical port for your partition according to the information in Table 1
above. Here is an example with logical port ID 1 selected:
Click OK to apply the logical port change.

Click OK to apply the change to the profile.
Do not close the Manage Profiles window yet.
__ 9. Ensure that your partition has 2 GB of memory. Configuring an HEA port requires
that your LPAR has at least 768 MB of memory.
Click Close to close the Managed Profiles window.

3-5
__ 10. Activate your LPAR with its Normal profile.

Your LPAR should still be selected. Run the Operations > Activate task and
activate it with its Normal profile. If you still have a console window for the
partition, you do not have to check the check box for a terminal window. If you do
not have a console window, check the check box.
__ 11. Once your LPAR has booted, log in to its console. Run the lsdev -c adapter -S a
AIX command again. You should see these two new devices:
ent2 Available Logical Host Ethernet Port (lp-hea)
lhea0 Available Logical Host Ethernet Adapter (l-hea)
The logical numbers (ent# and lhea#) for the devices might be different on your
system.
__ 12. Run the lsparent -Cl ent2 command to see the parent of the LHEA (lp-hea). The
logical number (ent#) for the device might be different on your system.
# lsparent -Cl ent2
lhea0 Available Logical Host Ethernet Adapter (l-hea)
__ 13. Open a virtual console to your LPAR. Use the smit tcpip fastpath to list your
TCP/IP configuration. Record the host name, IP address, network mask and default
gateway here.
Host name: ____________________
IP address: ____________________
Network mask: ____________________
Default gateway: ____________________
__ 14. Use the virtual console session to run the ifconfig AIX command to bring down
and detach the existing Ethernet interface. This should be a physical Ethernet
adapter that has logical device name ent0 (en0 interface). The logical number (ent#)
for the device might be different on your system.
# ifconfig en0 down
# ifconfig en0 detach
__ 15. Use the smit tcpip fastpath to configure the Ethernet interface for the logical host
Ethernet port. Use the Minimum Configuration & Startup SMIT menu option.
If the adapter's name is ent2, configure its interface en2. Use the following
information to configure this interface:
Reuse the host name, IP address, netmask, and gateway you recorded
previously.
Use the down arrow to move to the bottom of the SMIT panel and answer
yes to the START Now line.
Press Enter to run the SMIT panel.
3-6

V7.0.2
EXempty
Type ESC 0 to exit SMIT.

__ 16. Use the ping AIX command to verify that your network interface can communicate
on the network. Ping the IP address of your HMC.
Here is an example of a successful ping where hmcIP would be the actual HMC's IP
address:
# ping hmcIP
PING 10.6.140.40: (10.6.140.40): 56 data bytes
64 bytes from 10.6.140.40: icmp_seq=0 ttl=64 time=0 ms
Type CTRL C to stop the ping.
__ 17. Run entstat -d on the new ent# device. Page through the statistics that are
available for this type of device. You can also try the following command:
lsslot -c port
__ 18. Looking at the LHEA port assignments in Table 1 on page 3-4, what if you had to
configure an LHEA port on your LPAR for the best performance for lots of network
traffic to external hosts? What physical HEA port would you use?
Document that physical port ID here: ____________________
Since all the LPARs are using physical port 0, you should configure your partition
for the other physical port if there will be lots of network traffic to external hosts.
In that case, your LPAR would not share the same physical port as the other
LPARs.
Note, however, that all the logical ports associated with the same physical port
allow partition-to-partition communication. LPARs that configure logical ports on
the same physical ports can use internal LPAR-to-LPAR communications. If your
LPAR was only going to have heavy traffic to other LPARs, using the same
physical port, and thus the same HEA internal switch, would make more sense.
__ 19. Inform your instructor that you have finished this exercise.
End of exercise

3-7
3-8

V7.0.2
EXempty
Exercise 4. Virtual Ethernet adapter configuration

(with hints)

This exercise covers the configuration of a virtual Ethernet network for
LPAR communication. It explores the operations involved with
managing virtual Ethernet adapters.

Configure a network communication between two partitions
through virtual Ethernet adapters, and test the POWER Hypervisor
provided VLAN connection
Configure a virtual adapter with additional VID and a VLAN adapter
in your AIX partition
Introduction
In this exercise, you create and configure a virtual Ethernet adapter
and test the connectivity between your partition and another student's
partition. You will use both the HMC graphical interface and HMC
commands to complete the tasks.
Requirements
This workbook.
A workstation with Web UI to access the HMC over an IP.
A POWER7 processor-based managed system connected to the
same network as the workstations.
A system from which to start SSH sessions to the HMC and
partitions.

4-1

Preface
This exercise depends on the availability of specific equipment in your
- A managed system configured with at least one partition per student running
AIX V7.1.
- A system from which to execute remote commands to the HMC (using web
user interface or SSH).
- Network connectivity that is set up to allow all the systems to communicate
properly.
for the exercise steps. All hints are marked by a sign. Also, please note that the
screen shots in this and subsequent exercises are suggestive in nature and the
screens you will see might differ depending on the hardware setup or the version
of the HMC and VIOS. Ensure that you understand the steps, and if you have
any doubt, feel free to speak to your instructor.
Part 1: Configuring a virtual Ethernet connection (simple configuration)

In this part of the exercise, you use the HMC to create a virtual Ethernet adapter for your
partition, and you configure the virtual Ethernet adapter and the corresponding AIX
interface. You and another student will use the same VLAN ID for the virtual Ethernet
adapter configuration. You will test the connection to the partition configured on the same
VLAN and check that you are not able to ping other partitions.
The following diagram shows the network topology that students will configure during part
one of the exercise. It represents the partitions hosted on a managed server for student
4-2

V7.0.2
EXempty
one through student six. A similar partition configuration is set up on another system for
students seven to twelve.
POWER Hypervisor
__ 1. Start your browser, connect to the HMC, and log in using the user and password that
has been provided for you in the class instructions. Navigate to the LPAR table view
for your system, and check the status of your partition. Your partition should be
running for this part of the exercise. If it is not, activate it using the Normal profile.
Continue to step two without waiting for the activation to complete.
Click the Systems Management link in the HMC navigation area.
Click your managed system in the list of servers.
Select your LPAR in the working pane; then use the Tasks menu to request the
partition activation (Operations > Activate).
__ 2. Dynamically add a virtual Ethernet adapter to your partition. Create the adapter with
the lowest available virtual slot number, and assign it the virtual LAN ID value as
mentioned in the table below.
Table 2: Virtual Ethernet adapter configuration
Student
Managed
Port
IP address
number
system
default
VLAN ID
1
first
1
1.1.1.1
2
first
1
1.1.1.2
3
first
2
1.1.1.3
4
first
2
1.1.1.4
5
first
3
1.1.1.5
6
first
3
1.1.1.6
7
second
1
1.1.1.7
8
second
1
1.1.1.8
9
second
2
1.1.1.9
10
second
2
1.1.1.10
11
second
3
1.1.1.11

4-3
Student
number
Managed
system
Port
IP address
default
VLAN ID
12
second
3
1.1.1.12
Select your LPAR in the working pane, and then use the Context menu or the
Tasks pad to access the Dynamic Logical Partitioning > Virtual Adapters
task.
On the Actions menu, select Create > Ethernet Adapter...
In the screen that pops up, change the VLAN ID to the corresponding value and
click OK. Do not select any other check boxes, and verify that the VSwitch field
is set with the default ETHERNET0(Default) value. Here is an example where
the virtual LAN ID of 1 is entered for the partition 1:
4-4

V7.0.2
EXempty
The Virtual Adapter dialog screen should now look like this:
Click OK to create the virtual Ethernet adapter.

__ 3. Since you added the virtual Ethernet adapter dynamically, what must you do to have
AIX recognize the new device? Open an ASCII terminal to your partition using SSH
or Telnet, log in as root, and run the cfgmgr command to configure the virtual
Ethernet adapter. Use the lsdev command to see the list of configured devices, and
then verify that there is one new virtual Ethernet adapter available.
The important step is to run the cfgmgr command.
Here are example commands and outputs. In this example, ent3 is the new
virtual Ethernet adapter.
# lsdev -Cc adapter | grep ent
ent0 Available 00-00 2-Port 10/100/1000 Base-TX PCI-Express
ent2 Available
Logical Host Ethernet Port (lp-hea)
# cfgmgr
# lsdev -Cc adapter -Sa | grep ent
ent2 Available
ent3 Available
Virtual I/O Ethernet Adapter (l-lan)
Adapter (14104003)
Adapter (14104003)
Adapter (14104003)
Adapter (14104003)
In the following steps, you will use commands to check the virtual Ethernet
configuration from the AIX command-line interface.
__ 4. Use the entstat -d command to check the port VLAN ID of the virtual Ethernet
adapter.

4-5
Here is example command and output information.

# entstat -d ent3 | grep ID
Invalid VLAN ID Packets: 0
Port VLAN ID:
1
VLAN Tag IDs: None
Switch ID: ETHERNET0
__ 5. Use the lscfg AIX command to list the virtual slot ID of the virtual Ethernet adapter.
Virtual slot ID is mentioned in the physical location code; use the lscfg
command.
Here is example command and output information. In this example, the virtual
Ethernet adapter is connected to virtual slot ID 2.
# lscfg -l ent3
ent3
U8233.E8B.1084AER-V1-C2-T1 Virtual I/O Ethernet Adapter (l-lan)
__ 6. List the MAC address of the virtual Ethernet adapter from the AIX CLI. You can use
lscfg or entstat.
Here are example commands and outputs.
# entstat -d ent3 | grep Address
Hardware Address: 06:06:eb:31:e8:02
# lscfg -vl ent3 | grep Address
Network Address.............0606EB31E802
__ 7. Log in to the HMC CLI using the ssh command, and list the configuration of the
virtual Ethernet adapter on your partition.
Here are example commands and output.
hscroot@hmc109:~> lshwres -r virtualio --rsubtype eth -m sys464
--level lpar --filter lpar_names=sys464_partition1
lpar_name=sys464_partition1,lpar_id=1,slot_num=2,state=1,is_required=
0,is_trunk=0,ieee_virtual_eth=0,port_vlan_id=1,vswitch=ETHERNET0,addl
_vlan_ids=,mac_addr=0606EB31E802,allowed_os_mac_addrs=all,qos_priorit
y=none
__ 8. View the virtual network topology. Access the HMC web user interface, select your
partition, and use the Dynamic Logical Partitioning > Virtual Adapters task. On
the Actions menu, select Create > Ethernet Adapter.... In the screen that pops up,
click the View Virtual Network, select your VLAN, and look at the network details.
Click Close and Cancel twice to exit without creating a new virtual adapter.
4-6

V7.0.2
EXempty
An example screen is shown below. You may not see the details of the other
partition using the same VLAN ID if the other student has not yet dynamically
added the virtual Ethernet adapter.
__ 9. Now it is time to configure the AIX Ethernet interface. Use the smitty chinet
fastpath, and select the interface corresponding to the virtual adapter. In the
example from the last step, you would configure the en3 interface. Use the IP
address mentioned in Table 2 on page 4-3 according to your student number, set
255.255.255.0 for the netmask, and change the current STATE to up. Press the
Enter key to run the command, and press F10 or Esc 0 to exit SMIT when the
operation is completed successfully.
__ 10. List the IP routing table of your partition, and verify that IP routes are created using
the corresponding interface.

4-7
Here are example commands and output.

# netstat -rn
Routing tables
Destination
Gateway
Flags
Refs
Route Tree for Protocol Family 2 (Internet):

default
10.6.140.254
UG
1
1.1.1.0
1.1.1.1
UHSb
0
>
1.1.1/24
1.1.1.1
U
0
1.1.1.1
127.0.0.1
UGHS
0
1.1.1.255
1.1.1.1
UHSb
0
10.6.140.0
10.6.140.41
UHSb
0
>
10.6.140/24
10.6.140.41
U
1
10.6.140.41
127.0.0.1
UGHS
2
10.6.140.255
10.6.140.41
UHSb
0
127/8
127.0.0.1
U
5
Use If
655 en2
0 en3
3 en3
2 lo0
0 en3
0 en2
1099
8
0
16776
en2
lo0
en2
lo0
Exp Groups
__ 11. Coordinate with the other student who is using the same VLAN for his or her
partition on the same managed system (refer to Table 2 on page 4-3). Ping his or
her partition IP address on the 1.1.1.X network. Verify that the two virtual Ethernet
adapters can communicate.
# ping -c 3 1.1.1.2
PING 1.1.1.2: (1.1.1.2): 56 data bytes
----1.1.1.2 PING Statistics---3 packets transmitted, 3 packets received, 0% packet loss round-trip
min/avg/max = 0/0/0 ms
__ 12. Test the speed of the virtual network; 1 megabyte should be transferred in less than
10 milliseconds. This test should not be considered as a performance
measurement; it is just given as an example. Use the ftp command to connect to
your partner's partition using the 1.1.1.X network; then type binary to transfer as
binary form, and type the following command to send 1 MByte:
put "|dd if=/dev/zero bs=1M count=1" /dev/null
4-8

V7.0.2
EXempty

# ftp 1.1.1.2
Connected to 1.1.1.2.
220 sys464_partition2 FTP server (Version 4.2 Tue Oct 19 16:17:02 CDT
2010) ready.
Name (1.1.1.2:root): root
331 Password required for root.
Password:
230-Last unsuccessful login: Tue May 4 16:02:15 CEDT 2010 on
/dev/pts/0 from st
or_nim
230-Last login: Sat Jan 5 00:16:30 CET 2013 on ftp from ::ffff:1.1.1.1
230 User root logged in.
ftp> binary
200 Type set to I.
ftp> put "|dd if=/dev/zero bs=1M count=1" /dev/null
200 PORT command successful.
150 Opening data connection for /dev/null.
1+0 records in.
1+0 records out.
226 Transfer complete.
1048576 bytes sent in 0.01098 seconds (9.325e+04 Kbytes/s)
local: |dd if=/dev/zero bs=1M count=1 remote: /dev/null
ftp>bye
__ 13. Verify that you cannot ping a partition defined on a different VLAN.
Here is an example showing the ping command and its output.
# ping -c1 1.1.1.3
PING 1.1.1.3: (1.1.1.3): 56 data bytes
----1.1.1.3 PING Statistics---1 packets transmitted, 0 packets received, 100% packet loss

4-9
Part 2: Configuring additional VLANs

In this part of the exercise, you will dynamically change the configuration of your partition
so that it can participate on two VLANs.
The following diagram shows the network topology that students will configure during part
two of the exercise. Notice that the part one configuration remains unchanged, and you will
perform the steps to add the additional VLAN. The final configuration allows all partitions in
the same server to communicate each other.
A similar configuration is set up on the other managed server for students seven to twelve.
__ 14. Dynamically change the virtual Ethernet adapter's configuration so that it can
participate on two VLANs. Specify the additional VLAN ID 4. In a later step, you will
configure the respective network interface with an IP address according to the
following table.
Table 3: Additional VLAN ID configuration
Student
IEEE 802.1Q
IP Address for the
number
Additional VLAN ID
new VLAN
interface
1
4
4.4.4.1
2
4
4.4.4.2
3
4
4.4.4.3
4
4
4.4.4.4
5
4
4.4.4.5
6
4
4.4.4.6
7
4
4.4.4.7
8
4
4.4.4.8
9
4
4.4.4.9
10
4
4.4.4.10
11
4
4.4.4.11
12
4
4.4.4.12
Click the Systems Management link in the HMC navigation area.
Expand the Servers list so that you can select your managed system.

V7.0.2
EXempty
Select your LPAR in the working pane, and then use the Context menu or the
Tasks pad to access the Dynamic Logical Partitioning > Virtual Adapters
task.
Select the virtual Ethernet adapter that you created earlier. Click the Edit option
in the Actions menu.
In the window that opens, select the IEEE 802.1q compatible adapter check
box and enter the second VLAN ID in the Add VLAN ID field. Then click the Add
button so that the VLAN ID appears in the Additional VLAN IDs list.
Here is an example:
Click OK on this screen, and then click OK again to close the Logical Partition
Profile Properties window.
__ 15. In a terminal connected to your partition, run lsdev -C | grep ent to list all
Ethernet adapters. Is a VLAN device entry listed?
_________________________________________________________________

4-11
Here is an example command and its output.

# lsdev -C | grep ent
ent0 Available 00-00
Adapter (14104003)
ent1 Available 00-01
Adapter (14104003)
ent2 Available
ent3 Available
2-Port 10/100/1000 Base-TX PCI-Express

2-Port 10/100/1000 Base-TX PCI-Express
No VLAN entry is in this output.

__ 16. Use the entstat -d command to check the port VLAN IDs of the virtual Ethernet
adapter. Does the additional VLAN ID show up in the output?
Here is example command and output information showing the newly added
additional VLAN ID in the VLAN Tag IDs field.
# entstat -d ent3 | grep ID
Port VLAN ID:
1
VLAN Tag IDs:
4
__ 17. Use the smit addvlan fastpath command to create a new AIX VLAN pseudo device
instance associated with the additional VLAN ID using the virtual Ethernet adapter
that you created previously. Do not specify a VLAN priority in the SMIT menu.
Here is an example of the addvlan SMIT screen where the VLAN ID 4 has been
entered:
Add A VLAN
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
ent3
[4] +#
[] +#
VLAN Base Adapter

* VLAN Tag ID
VLAN Priority
__ 18. List all Ethernet adapters in your partition. Is there a new AIX VLAN device entry
now? ____________________________________________________________

V7.0.2
EXempty
You should now see a VLAN pseudo device listed in the lsdev output. Here is an
example of the lsdev command and its output showing that there is now a new
ent4 instance listed as a VLAN.
# lsdev -C | grep ent
ent0
Available 00-00
(14104003)
ent1
Available 00-01
(14104003)
ent2
Available
ent3
Available
ent4
Available
2-Port 10/100/1000 Base-TX PCI-Express Adapter

VLAN
__ 19. Use the smit chinet fastpath command to configure the interface of the new VLAN
device. Select the interface, and use the IP address mentioned in Table 3 on
page 4-10. It should be similar to 4.4.4.x, where x is your student number. Use
255.255.255.0 for the network mask, and set the current state to up. Press Enter to
execute the command.
__ 20. In this part of the lab exercise, all the students on the same server have a network
interface defined on the VLAN ID number 4 and configured with an IP address on
the 4.4.4.x subnet. Synchronize with another student and ping his or her partition
using the corresponding 4.4.4.X address. Is the ping successful now?
Here is an example showing the ping command and its output. Partition1 pings
partition3 successfully.
# ping -c 2 4.4.4.3
PING 4.4.4.3: (4.4.4.3): 56 data bytes
----4.4.4.3 PING Statistics---2 packets transmitted, 2 packets received, 0% packet loss round-trip
min/avg/max = 0/0/0 ms
Adding a second virtual Ethernet adapter using a port default VLAN ID instead of an
additional VID on the single virtual Ethernet adapter would have resulted in an
equivalent TCP/IP configuration. For this reason, AIX VLAN adapters are not
frequently used in the virtualized environment.
__ 21. Shut down your partition using the shutdown -F AIX command.
__ 22. Let your instructor know when you have completed the exercise.
End of exercise

4-13

V7.0.2
EXempty
Exercise 5. Virtual I/O Server and client partition

configuration
(with hints)

This exercise covers the installation and configuration of a virtual I/O
server and an AIX client partition. It covers the setup of a virtual
Ethernet LAN, an SEA for network access, and a VSCSI environment
that provides disks for the client partition.
For your information, another optional lab exercise is available at the
end of the course. It covers the setup of a virtual media repository and
the creation of a file-backed VSCSI disk.

Create a virtual I/O server partition
Install the virtual I/O server operating system
Configure the virtual I/O server to support a virtual client partition:
- Configure an SEA
- Configure a VSCSI environment
Create the virtual client partition
Install AIX from a network installation management server
Introduction
This exercise is presented in two topics.
The first topic contains two parts:
- Part 1: Create the VIO server partition
- Part 2: Install the virtual I/O server operating system
The second topic contains four parts:
- Part 1: Configure an SEA on the virtual I/O server
- Part 2: Configure a VSCSI disk on the virtual I/O server
- Part 3: Create the client LPAR
Exercise 5. Virtual I/O Server and client partition configuration

5-1
- Part 4: Install the AIX client partition operating system
Requirements
This workbook
A workstation with web UI to access the HMC over an IP.
5-2

V7.0.2
EXempty

Preface
This exercise depends on the availability of specific equipment in your
- A managed system to configure a VIO server and an AIX V7.1 partition.
- A NIM server prepared with corresponding resources.
- A system from which to execute remote commands to the HMC (using SSH)
and to access the HMC web user interface.
- Network connectivity that is set up to allow all the systems to communicate
properly.
for the exercise steps. All hints are marked by a sign.
The following diagram shows the configuration that you will implement during
this lab.
- In Topic 1, you will create and install the VIO server partition.
- In Topic 2, you will configure an SEA and a vhost in the VIO server to provide
virtual resources for a client partition; then you will create and install the client
partition.
Notice that two kinds of LUNs are assigned to the Fibre Channel adapter of your VIO
Server partition.
Non-shared LUNs (LUNS assigned to only one Fibre Channel adapter):
One of the non-shared LUNs will be used as the rootvg disk for the installation of
the VIO server operating system. It should be 30 GB in size.
The other non-shared LUN (8 GB in size) will be used in an optional exercise for
creating a file backed pool.

5-3
Shared LUNs (LUNS assigned to several Fibre Channel adapters):

You will use one of the shared LUNs (10 GB in size) for your client partition AIX
installation.
It is not necessary to share this LUN for this exercise because you build a unique
configuration VIO server. The LUN is shared because in a following exercise you
will work as a team with another student and share resources to build a secure
environment with a dual VIO server configuration.
Several 10 GB shared LUNs have been set up for the class. Each student will select one of
these LUNs to install the client LPAR operating system.
When performing LPAR creation tasks, use the VLAN IDs and LPAR names assigned by
your Instructor.
Topic 1 - Part 1: Create the VIO server partition

In this part of the exercise, you will use the physical slots of your existing assigned LPAR
as the physical slots for the virtual I/O server partition.
__ 1. If your partition is running, shut it down. While you are waiting for the partition to shut
down, open the partition's properties window and note all the physical I/O slots that
have been assigned to it. Write them down here (it will be used later in the VIOS
definition).
Ethernet adapter slot: _______________________________________________
Fibre Channel adapter slot: ___________________________________________
Issue the shutdown -F command if your partition is running.
In the HMC interface, select your assigned partition in the work area, and choose
Properties in the Tasks pad. Select the Hardware tab and then the I/O sub-tab,
and note all the slots that the partition currently owns. In the following example,
this partition either owns or is remembered to have owned slot C4 and C6.
5-4

V7.0.2
EXempty
Make a note of the complete slot number information for each adapter, not just
the last portion of the slot, for example C4. This is because some managed
systems may have multiple I/O enclosures, and each enclosure may have a slot
called C4. The complete slot information identifies the I/O enclosure that
contains the slot.
__ 2. When your assigned partition is shut down, close any open console window, and
then delete the partition.
Select your assigned partition in the work area; then choose Operations >
delete.
__ 3. Create a virtual I/O server partition. Use the partition name provided by your
instructor, and name the profile Normal. The VIOS partition will use the physical I/O
resources of the partition that you deleted in the previous step so that it can have
access to a storage subsystem.
The following table shows the managed server allocation for all the students
attending the class. One managed server is shared by six students. See your
instructor for the LPAR name information.
Table 4: Student and VIOS allocation
Student ID
Virtual I/O
VIO server
server partition
partition ID
name
First managed server
Student 1
1
Student 2
2
Student 3
3
Student 4
4
Student 5
5
Student 6
6
Second managed server
Student 7
7
Student 8
8
Student 9
9
Student 10
10
Student 11
11
Student 12
12
The following table shows all the parameters and values needed for the
configuration of your VIO server partition. You will use this information to fill in the
corresponding fields of the Create LPAR Wizard. All the wizard steps are listed in
the left column of the table.

5-5
Table 5: VIO configuration details

Wizard step
Parameter or action
Partition ID
Partition name
Create Partition
Mover service partition
Partition Profile
Processors
Processing Settings
Memory Settings
I/O
5-6
Profile name
Shared
Minimum processing units
Desired processing units
Maximum processing units
Shared processor pool
Minimum virtual processors
Desired virtual processors
Maximum virtual processors
Uncapped
Weight
Minimum memory
Desired memory
Maximum memory
Active Memory Expansion
Two slots must be added as
required (One Fibre Channel and
one Ethernet adapter).
Value
Your student ID
Provided by the
instructor
Check or uncheck
(does not matter, this
is for partition
mobility)
Normal
0.1
0.6
1.0
DefaultPool (0)
1
1
10
Yes (check box)
128
1 GB
2 GB
4 GB
Not checked
Refer to the values
recorded in Step 1.

V7.0.2
EXempty
Wizard step
Virtual Adapters
Logical Host Ethernet

Adapters (LHEA)
HCA
Optional Settings
Profile Summary
Parameter or action
Value
Maximum virtual adapters
50
Actions -> Create Virtual
Adapter -> Ethernet Adapter...
Adapter ID
11
ETHERNET0
VSwitch
(Default)
Student number (for
Port Virtual Ethernet
example, student
seven uses VLAN 7)
This adapter is required for
Not checked
partition activation.
IEEE 802.1q
Not checked
Use this adapter for Ethernet
Checked
bridging
Trunk priority
1
Actions -> Create Virtual
Adapter -> SCSI Adapter...
Adapter ID
12
Not checked
Keep the option
Any client partition can connect.
selected.
Skip this step.
Skip this step.
Boot modes
Normal
To create a new partition, click the Systems Management link in the HMC
navigation area, click Servers, and then select your managed system.
In the Tasks pad, click Configuration > Create Logical Partition > VIO Server.
When the Create Lpar Wizard opens, name your partition using the information
provided by your instructor. Use your student number as the partition ID.

5-7
The Create Lpar Wizard should look similar to this example:
Click Next and proceed to use the wizard to create the partition, using the
specified profile name, processor and memory settings, and I/O physical slot
resources. Remember that selecting an I/O slot is not enough; you need to click
Add as Required above the list.
Click Actions to create the virtual adapters. Continue to click Next until you
reach the Profile Summary panel. Remember to set 'Maximum virtual adapters'
to 50, because you will need these adapter IDs in subsequent exercises.
You can go back to a previous wizard step at any time by clicking in the left
navigation pane.
Skip the LHEA step. Click Next.
Skip the HCA step. Click Next.
Verify that the configuration is what you want, and then click Finish.
Topic 1 - Part 2: Install the VIO server partition from NIM

__ 4. The NIM resource has already been allocated on the NIM master for installing your
virtual I/O server. Ask your instructor for confirmation.
5-8

V7.0.2
EXempty
__ 5. You need an IP address for the VIO server partition, and you need to know the NIM
server IP address for the network boot operation. Also, an IP address will be needed
in the next part of the exercise for the AIX virtual client partition. Ask your instructor
for your assigned IP addresses. Enter them in the following table.
Table 6: IP addresses for your partitions
VIO server IP address
NIM server IP address
Netmask
Gateway address
AIX client IP address
__ 6. From the Server Management application of the HMC, activate your Virtual I/O
Server LPAR using the SMS boot mode.
On the HMC, click the name of your managed system and select your partition
in the working area.
From the Tasks pad or the Context menu, click Operations > Activate >
Profile. The Activate Partition menu opens with a selection of partition profiles.
Ensure that the correct profile is highlighted.
Select Open a terminal window or console session to open a virtual terminal
window.
Click Advanced to open the advanced options menu.
For the boot mode, select SMS.
Click OK and then OK again to start the activation.
__ 7. Interact with the menus. Choose the Setup Remote IPL (Initial Program Load)
menu option, and select the network adapter device. You should see the physical
Ethernet adapter, which might be a dual port device, and the virtual Ethernet adapter
(interpartition logical LAN). Choose the first port of the physical adapter, and press

5-9
Enter. In the following example, the item number two must be chosen to select port
1 of the physical adapter.
__ 8. Select the IP Protocol Version of IPv4. Select the Network Service of BOOTP.
__ 9. On the Network Parameters panel, select 1 IP Parameters.
__ 10. In the next screen (IP Parameters), there are four options. Type the number of the
option you want to alter. For example, press 1 and then the Enter key to alter the
Client IP address. Type the value, and then press Enter.
For the values to enter, refer to Table 6 on page 5-9. If uncertain, ask your instructor
for help.
__ a. Enter your virtual I/O server's IP address for the client IP address. Do not enter
your AIX partition's IP address. Doing so will result in having an AIX image
installed for the VIOS rather than a VIOS image. The NIM server uses the client
IP address to identify what image to serve to that client.
__ b. Enter the NIM server's IP address for the server IP address.
__ c. Enter the gateway IP address (if necessary for NIM to VIOS network
communication).
__ d. Enter the subnet mask. The VIOS will use the same subnet mask as your AIX
LPAR.
__ e. For example:

V7.0.2
EXempty
When done, press the Esc key to go to the Network Parameters menu. Press 2 to
select 2 Adapter Configuration. Disable the spanning tree (if it is not already
disabled). Press 2 then 2 again to disable. Note that the name of the option is
Spanning Tree Enabled. This is always the option name regardless of whether it is
enabled. Press Esc to go back to the Adapter Configuration.
__ 11. Ask your instructor to confirm the speed value. Suggested values for the
speed/duplex settings are auto/auto. Press Esc to go back to the Adapter
Configuration menu. Press Esc again to go back to the Network Parameters
menu.
__ 12. Press 3 to select 3 Ping Test. Press 1 to execute the ping test. Wait for a few
seconds, and the message Ping Success should display if the ping test succeeded.
Press any key to return to the Ping Test screen. Otherwise, talk to your instructor in
case of a ping test failure.
__ 13. Press M to go back to the Main Menu; then select 5 Select Boot Options.
__ 14. Specify the PCI Ethernet adapter to be the boot device. Press 1 to select Select
Install/Boot Device. Select 6 Network, and select 1 BOOTP. In the next screen
(Select Device), the Ethernet adapters are listed. Choose the same adapter as the
one you have just configured in the previous steps. Type the corresponding number,
and press Enter.
In the following example, item number two must be chosen to select Port 1 of the
physical adapter.
__ 15. Press 2 for Normal Mode Boot; then select 1 Yes when asked Are you sure you
want to edit System Management Services? to exit SMS and do a Normal Mode
boot.
__ 16. You will see the network boot output in the window. Eventually, you will see the
Virtual I/O Server installation process. Respond as you normally would to select the
system console and language.
__ 17. Your terminal screen should display the Installation and Maintenance screen.
Press 2 and Enter to select Change/Show Installation Settings and Install.
__ 18. Press 1 and Enter to select Disks where you want to install(hdisk0). You will notice
that several disks are available for selection. Be careful to select the disk with the
size of 30720 MB (30 GB). There should only be one disk of this size.

5-11
You should see a screen like this one.

Note
In this example, hdisk0 is of 30 GB size. On your system, the 30 GB disk may not be
hdisk0.
__ 19. Accept your disk choice by pressing 0 to continue with choices listed above.
__ 20. You should be back at the System Backup Installation and Settings panel. Start
the installation by selecting 0 to continue with the installation process. When the
installation completes, the LPAR reboots to a logon screen.
Depending on your environment, the install might take as little as six minutes.
__ 21. The partition will reboot when the installation is complete. When the installation
completes and the LPAR reboots, log in as padmin and use the password provided
by your instructor.
__ 22. Use the configuration assistant command for the VIOS, cfgassist, to set the date
and time zone for the partition. The cfgassist command is menu-driven and allows
administrators to manage some of the initial setup requirements of the Virtual I/O
Server. The new time zone will take effect after the next time the operating system
reboots. You can also use the chdate command to change the date and time zone.

V7.0.2
EXempty
You should see a screen like this one:
From the cfgassist menu, select Set Date and TimeZone.

You can also use the chdate command and the following option in the CLI
(where mmddHHMMYYYY is the actual month, date, hour, minutes, and year,
and TZ is the time zone):
chdate mmddHHMMYYYY -timezone TZ
For example, set the date to 2013, January 4th, 7:30 for Finland:
chdate 010407302013 -timezone WET-2WET

5-13
__ 23. Type help to list all commands available on the VIOS.

Here is the output of the help command for release 2.1.3.10-FP23 of the Virtual I/O
Server. Use the ioslevel command to determine your Virtual I/O Server software
release level.
Install Commands
ioslevel
license
lpar_netboot
lssw
oem_platform_level
oem_setup_env
remote_management
updateios
Security Commands
lsfailedlogin
lsgcl
viosecure
mkldap
ldapadd
ldapsearch
snmpv3_ssw
mkkrb5clnt
LAN Commands
cfglnagg
cfgnamesrv
entstat
fcstat
hostmap
hostname
lsnetsvc
lstcpip
mktcpip
chtcpip
netstat
optimizenet
ping
prepdev
rmtcpip
seastat
startnetsvc
stopnetsvc
traceroute
vasistat
UserID Commands
chuser
lsuser
mkuser
passwd
rmuser
Device Commands
chdev
chkdev
chpath
cfgdev
lsdev
lsmap
lsnports
Maintenance Commands
alt_root_vg
backup
backupios
bootlist
cattracerpt
chdate
chlang
cfgassist
cl_snmp
cpvdi
dsmc
diagmenu
errlog
fsck
invscout
ldfware
loginmsg
lsfware
lslparinfo
motd
mount
pdump

V7.0.2
EXempty
lspath
mkpath
mkvdev
mkvt
rmdev
rmpath
rmvdev
rmvt
vfcmap
Physical Volume Commands
lspv
migratepv
Logical Volume Commands
chlv
cplv
extendlv
lslv
mklv
mklvcopy
rmlv
rmlvcopy
Volume Group Commands
activatevg
chvg
deactivatevg
exportvg
extendvg
importvg
lsvg
mirrorios
mkvg
redefvg
reducevg
syncvg
unmirrorios
Storage Pool Commands
chbdsp
chsp
lssp
mkbdsp
replphyvol
restore
restorevgstruct
save_base
savevgstruct
showmount
shutdown
snap
snmp_info
snmp_trap
startsysdump
starttrace
stoptrace
svmon
sysstat
topas
uname
unmount
viostat
vmstat
viosbr
wkldmgr
wkldagent
wkldout
artexget
artexset
artexmerge
artexlist
artexdiff
Monitoring Commands
cfgsvc
lssvc
postprocesssvc
startsvc
stopsvc
Shell Commands
awk
cat
chmod
clear
cp
crontab

5-15
mksp
rmbdsp
rmsp
Virtual Media Commands
chrep
chvopt
loadopt
lsrep
lsvopt
mkrep
mkvopt
rmrep
rmvopt
unloadopt
date
ftp
grep
head
ls
man
mkdir
more
mv
rm
sed
stty
tail
tee
vi
wall
wc
who
__ 24. On occasion, you might need the oem_setup_env command to access the AIX root
user shell. From here, you can invoke AIX commands and access SMIT if desired.
Type exit to get out of the oem_setup_env shell.
The purpose of this oem_setup_env command is to allow customers to install OEM
software needed to support storage solutions. All configuration commands of the
virtual I/O server should be performed through the padmin user CLI rather than the
root user CLI.
__ 25. Let your instructor know when you have completed the exercise topic.
Topic 2 - Part 1: Configure an SEA on the virtual I/O server

Now that your virtual I/O server is installed, you can configure an SEA. This SEA is needed
to provide network access for the AIX client partition. (This client LPAR will be created in
the next part of Topic 2).
__ 26. Use the lsdev command to list the adapters. You should see all the adapters,
including the network adapters (the physical Ethernet adapter and the virtual
Ethernet adapter). Record the names of the virtual Ethernet and the physical
Ethernet adapters. You should see two Ethernet adapter instances associated with a
dual port physical Ethernet adapter; record the name of the first physical port of the
list.
Physical Ethernet adapter names: _____________________________________
Virtual Ethernet adapter name: ________________________________________

V7.0.2
EXempty
Here is the output from the lsdev command:

$ lsdev -type adapter
name
status
description
ent0
Available
(14104003)
ent1
Available
(14104003)
ent2
Available
fcs0
Available
8Gb PCI Express Dual Port FC Adapter
(df1000f114108a03)
fcs1
Available
8Gb PCI Express Dual Port FC Adapter
(df1000f114108a03)
pager0 Available
Pager Kernel Extension
vasi0
Available
Virtual Asynchronous Services Interface (VASI)
vbsd0
Available
Virtual Block Storage Device (VBSD)
vhost0 Available
Virtual SCSI Server Adapter
vsa0
Available
LPAR Virtual Serial Adapter
__ 27. List only the virtual adapters and use grep to restrict it to only show the ones for
Ethernet. You should see the virtual I/O Ethernet adapter.
Here is example output for this command:
$ lsdev -virtual | grep -i ethernet
ent2 Available Virtual I/O Ethernet Adapter (l-lan)
__ 28. Using the lsdev command, check that the attribute media_speed of your physical
Ethernet adapter matches the configuration of the physical switch, and set it to the
new value if necessary. The AIX and VIOS default setting and the default of most
switches is auto-negotiation. Ask your instructor if the switch is not using
auto-negotiation and, if so, which values are configured.
If the adapter is dual port, assume that the first port is the cabled port. Your
instructor will inform you if that is not the case.
$ lsdev -dev ent0 -attr media_speed
Here is example output for this command:
value
Auto_Negotiation
Here is an example for changing the media speed for adapter ent0. DO NOT
ACTUALLY CHANGE THE ATTRIBUTE UNLESS IT IS NECESSARY:
$ chdev -dev ent0 -attr media_speed=100_Full_Duplex
__ 29. For this step, make sure you are logged in to your VIO partition using a console
terminal window from the HMC. Using the mkvdev command, create the SEA. Use
the ent0 physical device, and the virtual Ethernet adapter. Use your student number

5-17
as the VLAN ID. Use the -migrate and -auto flags of the mkvdev command to
migrate the IP configuration from the physical Ethernet adapter to the generated
SEA interface. This will generate an entX adapter (where X is the next numeric suffix
in the series used for the Ethernet adapters) and the related interfaces, enX and
etX.
Be aware that you cannot configure an IP address on the interfaces related to either
the physical Ethernet adapter or the virtual Ethernet adapter which are being used
by the SEA.
The following example creates an SEA that maps the physical Ethernet adapter
ent0 to the virtual Ethernet adapter ent2, using ent2 as the default adapter and 1
as the default VLAN ID. The IP configuration from the interface en0 is migrated
to the interface en3 of the generated SEA.
$ mkvdev -sea ent0 -vadapter ent2 -default ent2 -defaultid 1 -migrate
-auto
en0 changed
ent3 Available
en3
et3
en3 changed
inet0 changed
In this example, the virtual Ethernet switch will use this SEA to bridge any traffic
on VLAN ID 1 that needs to be sent to the physical network.
__ 30. List the virtual adapters. You should see the SEA. Record its device name:
$ lsdev -virtual
__ 31. Use the entstat command to list the Ethernet statistics of the SEA.
Use the command:
entstat -all <SEA adapter> | more
__ 32. Ping your HMC to test that your configuration worked.
Here is an example of the ping command and output.
ping 10.6.140.40 2
PING 10.6.140.40: (10.6.140.40): 56 data bytes
----10.6.140.40 PING Statistics---2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0/0/0 ms
__ 33. Use the lstcpip command to display the routing table.

V7.0.2
EXempty
Here is an example command.

lstcpip -routtable
Topic 2 - Part 2: Configure a VSCSI disk on the virtual I/O server

The purpose of this part is to create a VSCSI disk that will be used by a virtual I/O client
partition. In the next part of this exercise you will create an LPAR that will use this VSCSI
disk.
__ 34. Log in to the Virtual I/O Server, and verify that the VSCSI server adapter is available.
Also, using the lsmap command, check the mapping between physical, logical, and
virtual devices. (There should not be any virtual target devices at this point.)
The two commands you need to use are lsdev -virtual to find the name of the
VSCSI server adapter, and lsmap -all to see any physical devices mapped to
the VSCSI server adapter.
Here is an example from the lsdev command output that shows the vhost0
adapter:
$ lsdev -virtual | grep SCSI
vhost0
Available Virtual SCSI Server Adapter
Here is example of the lsmap command output.
$ lsmap -all
SVSA
Physloc
Client Partition ID
--------------- -------------------------------------------- -----------------vhost0
U8233.E8B.1084AER-V1-C12
0x00000000
VTD
NO VIRTUAL TARGET DEVICE FOUND
Note the virtual adapter slot number that you defined when creating the VIOS
partition.
__ 35. Now check to see that you have available disks on your VIOS partition. The number
of disk devices visible will depend on the specific configuration of the systems being
used for the class. It is expected that you should see eight hdisk devices in the
output of the lsdev command. For example:
$ lsdev -type disk
name
hdisk0
hdisk1
hdisk2
hdisk3
hdisk4
hdisk5
hdisk6
hdisk7
status
Available
Available
Available
Available
Available
Available
Available
Available
description
MPIO Other FC
MPIO Other FC
MPIO Other FC
MPIO Other FC
MPIO Other FC
MPIO Other FC
MPIO Other FC
MPIO Other FC
SCSI
SCSI
SCSI
SCSI
SCSI
SCSI
SCSI
SCSI
Disk
Disk
Disk
Disk
Disk
Disk
Disk
Disk
Drive
Drive
Drive
Drive
Drive
Drive
Drive
Drive

5-19
Each VIOS partition should be configured with two non-shared LUNs. If eight disks
are visible, this means there are six shared LUNs visible in the VIOS. In some
environments, there may be twelve shared LUNs visible on each VIOS.
__ 36. Now you must create a virtual target device that maps one FC SCSI physical disk to
the VSCSI server adapter defined on your virtual I/O server. This virtual disk will be
used for your AIX client LPAR operating system installation.
One LUN of 10 GB size has been defined during the lab setup for each student, and
these LUNs have been assigned to all Fibre Channel adapters of your managed
system (shared LUNs). This configuration will be needed for the next lab exercise
(dual VIO server environment with MPIO setup).
Each student on a managed system will use one of these LUNs; this step and the
information in Table 7 will determine the LUN assignment for each student.
__ a. First, check which physical hdisk devices are of 10 GB size. Execute the
following script from your Virtual I/O Server CLI; it displays disk size in MB:
lsdev | grep hdisk | while read a b
do
print "$a \c"
echo bootinfo -s $a | oem_setup_env
done
Here is an output example; hdisk1 to hdisk6 are 10 GB in size.
hdisk0
hdisk1
hdisk2
hdisk3
hdisk4
hdisk5
hdisk6
hdisk7
30720
10240
10240
10240
10240
10240
10240
8192
__ b. Record the hdisk numbers reported as 10 GB in ascending order in the following

table. For example, based on the previous command output, record hdisk1 in the
first row, hdisk2 in the second row, and so forth, up to hdisk6 in the last row.
Table 7: hdisk name for student allocation
10 GB size hdisk Student #
name
student 1 / student 7

V7.0.2
EXempty
__ c. Select from the table the hdisk that you will use as a backing device for your
client partition; for example, based on the previous command output:
student1 uses hdisk1

and so on
The normal lab setup for this class has six students sharing a single managed
system. When the class has twelve students, student 7 to student 12 are
configured on a second managed system. Each managed system has a
separate set of six shared LUNs, so the 10 GB devices visible to students 1 to 6
are separate from the set of devices visible to students 7 to 12.
__ d. Run the following command: lsdev -dev hdisk# -attr | grep lun_id
(where hdisk# is your selected disk), and write down the unique lun_id.
lun_id: ________________________________________________________
Here is an example of the command and output.
$ lsdev -dev hdisk3 -attr | grep lun_id
lun_id
0x3000000000000
Logical Unit Number ID False
Note
The hdisk name (hdiskX) is defined during the configuration sequence (cfgmgr), and
the associated disk number is related to the configuration order. The configuration is
done in order of increasing lun_id values of the LUNs assigned to the Fibre Channel
adapter.
You can run the following command: lsdev -dev hdisk# -attr | grep lun_id
This will show you the unique lun_id for the related LUN.
__ 37. Modify the reserve_policy parameter of your 10 GB disk devices from single_path to
no_reserve. These modifications are needed for the next exercises (MPIO setup in a
dual VIOS environment), and cannot be performed when the disk is in use. Run the
following command for this hdisk of 10 GB:
$ chdev -dev <hdisk#> -attr reserve_policy=no_reserve
__ 38. Create the virtual target device using the following command:
mkvdev -vdev hdiskY -vadapter vhost0 -dev lparX_vtd
(where hdiskY is your hdisk number and X is your student number).
Here is an example mkvdev command.
$ mkvdev -vdev hdisk2 -vadapter vhost0 -dev lpar2_vtd
lpar2_vtd Available

5-21
__ 39. List your virtual adapter device mapping by using the lsmap command. View the
output details, and check the lun_id in the physical location field.
Here is an example of the output from the lsmap command:
$ lsmap -all
SVSA
Physloc
Client Partition ID
-------------- ----------------------------------------- -----------------vhost0
U8233.E8B.1084AER-V1-C12
0x00000000
VTD
lpar1_vtd
Status
Available
LUN
0x8100000000000000
Backing device
hdisk1
Physloc
U5877.001.RCH8623-P1-C6-T1-W500507680140B855-L1000000000000
You can also the use lsmap -vadapter vhost0 command.

__ 40. Use the lspv command to list the volume group information for the disks. Notice that
no volume group information has been added to the hdisk being used as a backing
device.
Here is an example lspv command and output.
$ lspv
NAME
STATUS
hdisk0
active
hdisk1
hdisk2
hdisk3
hdisk4
hdisk5
hdisk6
hdisk7
PVID
VG
00f784aee0fd700a
rootvg
none
none
none
none
none
none
none
None
None
None
None
None
None
None
Remember that you must be careful before using disks of the VIO server for LVM
operations. They might have no volume group information shown but are possibly
being used as virtual disks for client LPARs. For example, running importvg -vg
myvg hdisk1 on the VIOS CLI will destroy the rootvg of the corresponding client
partition.
Topic 2 - Part 3: Create the client LPAR

Now you will create an LPAR that will use a VSCSI disk and a virtual Ethernet adapter. No
physical I/O resources will be allocated to the partition.
__ 41. Create an AIX LPAR. For the LPAR name and the partition ID, refer to Table 8 on
page 5-23. Check with your instructor whether you need to use a system prefix as

V7.0.2
EXempty
part of the LPAR name. For all other LPAR configuration parameters (partition profile
name, processor settings, memory, and so on), refer to Table 9 on page 5-24.
Skip the physical I/O, and add a virtual Ethernet adapter and a VCSI client adapter.
Note
Management can be simplified by keeping VSCSI adapter slot numbers consistent
between the virtual I/O server and the client partition.
Match the VSCSI client adapter slot number to the slot number of the VSCSI server
adapter (slot number is given in the table). Have this VSCSI client adapter connect
to the VIOS partition's VSCSI server adapter. For example, you could map slot 12
on the VIOS partition to slot 12 on this AIX LPAR.
Table 8: LPAR configuration
Client LPAR
Student number
Client LPAR ID
name
First managed server
Student 1
lpar1
21
Student 2
lpar2
22
Student 3
lpar3
23
Student 4
lpar4
24
Student 5
lpar5
25
Student 6
lpar6
26
Second managed server
Student 7
lpar7
27
Student 8
lpar8
28
Student 9
lpar9
29
Student 10
lpar10
30
Student 11
lpar11
31
Student 12
lpar12
32
The following table shows all the parameters and values needed for the
configuration of your AIX partition. You will use this information to fill in the
corresponding fields of the Create LPAR Wizard. All the wizard steps are listed in
the left column of the table.

5-23
Table 9: LPAR details

Wizard step
Parameter or Action
Value
Your student ID + 20
(see Table 8 above)
lparX (X is your
student ID)
Normal
Partition ID
Create Partition
Partition name
Partition Profile
Processors
Processing Settings
Memory Settings
I/O
Profile name
Shared
Minimum processing units
Desired processing units
Maximum processing units
Shared Processor Pool
Minimum virtual processors
Desired virtual processors
Maximum virtual processors
Uncapped
Weight
0.1
0.6
1.0
DefaultPool (0)
1
1
10
Yes (check box)
128
Minimum memory
Desired memory
Maximum memory
Active Memory Expansion
Skip this step, and click Next.
1 GB
2 GB
4 GB
Not checked

V7.0.2
EXempty
Wizard step
Parameter or Action
Value
Maximum virtual adapters
50
Actions -> Create Virtual Adapter
-> Ethernet Adapter...
Adapter ID
11
ETHERNET0
VSwitch
(Default)
Student number (for
Port Virtual Ethernet
example, student
seven uses VLAN 7)
This adapter is required for virtual
Not checked
server activation.
IEEE 802.1q
Not checked
Use this adapter for Ethernet
Not checked
bridging
Actions -> Create Virtual Adapter
-> SCSI Adapter...
Adapter ID
12
Not checked
Server partition
Select your VIOS
Server adapter ID
12
Virtual Adapters
Logical Host Ethernet

Adapters (LHEA)
HCA
Optional Settings
Profile Summary
Skip this step.

Skip this step.
Boot modes
Normal
On the HMC, select your managed system and choose Create Logical Partition
> AIX or Linux on the Tasks menu.

5-25
In the first wizard panel, enter the partition ID and the partition name from the
LPAR configuration table.
On the second panel, enter Normal as the profile name.

Create a shared processor type of LPAR using the processor settings specified
in the instructions.
Configure the memory using the setting specified in the instructions.
Do not allocate any physical I/O devices, and skip the Physical I/O panel.
Set the 'maximum virtual adapters' to 50.
Create a virtual Ethernet adapter. Click Create Virtual Adapter > Ethernet
Adapter... in the Actions menu. Use the same VLAN ID as your VIO server
partition (VLAN ID is your student number).
Create a SCSI client adapter. Click Create Virtual Adapter > SCSI Adapter... in
the Actions menu. Set the client slot number (Adapter field) to the slot number
that you used for the VIOS partition's VSCSI server adapter (slot number 12 as
referred to in Table 9).

V7.0.2
EXempty
Select your VIOS partition in the Server partition field, and specify the VSCSI
server adapter slot number in the Server adapter ID field. Click OK > Next.
Here is an example of this screen.
If you are not certain which virtual server SCSI adapter to use here, click System
VIOS Info to access the Virtual I/O Server Information window, and select a
virtual server SCSI adapter from here. Click OK to return to the previous pop-up
window.
Here is an example of this screen.
Skip the Logical Host Ethernet Adapters (LHEA) step. Click Next.
Skip the HCA step. Click Next.
Skip the Optional Settings step, and click Finish on the Profile Summary panel.
__ 42. Before activating the client LPAR, modify the VSCSI server adapter configuration on
your virtual I/O server so that it allows only the one client partition and has the
proper client slot number.
Click your managed system name and select your Virtual I/O Server partition in
the work area. Using the Task pad or the Context menu, click Configuration >
Manage Profiles. Select your Normal profile; then select Edit in the Actions
menu.

5-27
On the Virtual Adapters tab, in the listing of the virtual adapters, select the
server SCSI adapter you created, and click Actions > Edit.
Click Only selected client partition can connect.
Use the menu to choose the name of your client partition, such as lpar1.
For the client adapter ID, enter the slot number that was created for the virtual
client SCSI adapter. In the following example, slot 12 was entered:
Click OK and OK again to modify this adapter in the profile and close the profile
properties window.
Topic 2 - Part 4: Install the client LPAR operating system

You will now install your AIX client partition using a NIM environment.
__ 43. The NIM resources for client installation should have already been allocated on the
NIM master. Ask your instructor for confirmation.
__ 44. You need an IP address for the AIX virtual partition, and you need to know the NIM
server IP address for the network boot operation. You already recorded this
information in Table 6 on page 5-9 when installing the VIOS. Ask your instructor if
you fail to find it, and enter them again in the following table.
Table 10: IP addresses for installation of your AIX virtual partition
NIM server IP address
Netmask
Gateway address
(not necessary if server and client are
defined on the same network)
AIX client IP address
The following instructions walk you through the network boot using SMS.

V7.0.2
EXempty
Note
For your information, you can also activate your partition using the lpar_netboot
command from the HMC command-line interface. This HMC command instructs a
partition to boot from the network or retrieves MAC address and physical location
code from network adapters for a partition. It could be useful for operation
automation and scripting.
The lpar_netboot command requires arguments for IP addresses, partition name,

partition profile, name of the managed system that has the partition, and other
network parameters. Look at the following example of the lpar_netboot usage for
partition installation, and view the corresponding arguments:
lpar_netboot -v -f -D -i -t ent -T off -s speed -d duplex
-S nimserver_ip -C lpar_ip -G gateway_ip -K subnet_mask lpar_name
profile_name managed_system_name
-v Verbose output
-f Force close virtual terminal session
-D Perform a server ping, and use successful test adapter
-i Force immediate shutdown
-t Specifies network type ent
-T Enable or disable spanning tree
-s Network adapter speed:auto for a Virtual Eth Adapter
-d Network adapter duplex:auto for a Virtual Eth Adapter
-S Server IP address: Refer to the table above
-C Client IP address: Refer to the table above
-G Gateway IP address: Refer to the table above
-K Subnet mask
Here is an example from the lpar_netboot command.
lpar_netboot -v -f -D -i -t ent -T off -s auto -d auto -S \
10.6.140.35 -C 10.6.140.53 -G 10.6.140.254 -K 255.255.255.0 \
sys464_lpar2 Normal sys464
When the execution of the lpar_netboot command is completed, go to the HMC
GUI, select your LPAR, and open a console window. Interact with the AIX menus to
complete the installation. If you have installed your AIX LPAR using the HMC
lpar_netboot command, skip to Step 58 on page 5-31. If you want to use SMS to
initiate the network boot and install of your LPAR, continue with the next step.
__ 45. Activate your partition using SMS boot mode. Open the virtual console terminal
window.
__ 46. Interact with the SMS menus. Choose the Setup Remote IPL (Initial Program
Load) menu option, and select the network adapter device. You should see the

5-29
virtual Ethernet adapter. Type 1 and press Enter to select the virtual Ethernet
adapter.
__ 47. Select the IP Protocol Version of IPv4; then select the Network Service of
BOOTP.
__ 48. On the Network Parameters panel, select 1 IP Parameters.
__ 49. In the next screen (IP Parameters), there are four options. Type the number of the
option you want to alter. For example, press 1 and then Enter to alter the Client IP
address. Type the value, and then press Enter.
For the values to enter, refer to the information recorded in Table 10 on page 5-28. If
uncertain, ask your instructor for help.
__ a. Type your AIX partition's IP address for the client IP address.
__ b. Type the NIM server's IP address for the server IP address.
__ c. Type the gateway IP address. This field is not required if both client and server
are defined on the same subnet.
__ d. Type the subnet mask.
When done, press the Esc key to go to the Network Parameters menu. Press 2 to
select 2 Adapter Configuration. Disable the spanning tree (if it is not already
disabled). Press 2 and then 2 again to disable. Note that the name of the option is
Spanning Tree Enabled. (This is always the option name regardless of whether it is
enabled.) Press Esc to go back to the Network Parameters menu.
__ 50. Press 3 to select 3 Ping Test. Press 1 to execute the ping test. Wait a few seconds,
and Ping Success should display if the ping test succeeded. Press any key to return
to the Ping Test screen. Talk to your instructor if you have a ping failure and are
uncertain why the ping test failed.
__ 51. Press Esc to escape the Ping Test screen, and press M to go back to the Main
Menu; then select 5 Select Boot Options.
__ 52. Specify the virtual Ethernet adapter to be the boot device. Press 1 to select 1 Select
Install/Boot Device. Select 6 Network, 1 BOOTP, and then 1 to select the virtual
Ethernet adapter. Press 2 for Normal Mode Boot; then select 1 Yes when asked
Are you sure you want to edit System Management Services? to exit SMS and
do a normal mode boot.
__ 53. You will see the network boot output in the window. Eventually, you will see the AIX
installation process. Respond as you normally would to select the system console
and language.
__ 54. Your terminal screen should display the Installation and Maintenance screen. Type 2
and press Enter to select Change/Show Installation Settings and Install.

V7.0.2
EXempty
__ 55. Press 1 and Enter to select disks where you want to install (hdisk0). Verify that you
have a 10 GB disk to use as the AIX partitions rootvg. You should only have one disk
to choose from. This is the virtual disk being served from your VIO server.
__ 56. Accept this disk by pressing 0 to continue with choices listed above.
__ 57. You should be back at the System Backup Installation and Settings panel. Start
the installation by selecting 0 to continue with the choices.
Depending on your environment, the install might take as little as five to ten minutes.
__ 58. When the client partition is booted, log in using root.
__ 59. Using the lsdev command, list the disk device.
To list the disk devices, use lsdev -Cc disk.
Output should now list Virtual SCSI Disk Drive. Here is an example output; notice
the hdisk0 description.
# lsdev -Cc disk
hdisk0 Available
Virtual SCSI Disk Drive
__ 60. Use AIX commands to examine what adapters and devices are being used by this
system. You should see that the VSCSI adapter and disk plus the virtual Ethernet
adapter are in use. The corresponding interface will likely have been configured
during OS installation.
Following are some examples of the commands you might use.
lsslot -c pci
lsdev -Cc adapter
lscfg | grep disk
ifconfig -a
__ 61. Let your instructor know when you have completed the exercise topic.
End of exercise

5-31

V7.0.2
EXempty
Exercise 6. SEA failover setup

(with hints)

This exercise provides experience with configuring high availability in
a virtual Ethernet environment. Students will implement a dual Virtual
I/O Server configuration with an SEA failover configuration.

Implement a highly available network configuration using the SEA
failover feature and test the failover mechanism
Configure the virtual I/O server IP address on an additional virtual
Ethernet adapter
Introduction
By the end of this exercise, the students will have implemented an
SEA failover feature in a dual VIO server environment. Students will
test the failover mechanism.
Requirements
This workbook.
A workstation with a web browser and Internet connectivity for
accessing the HMC and the partitions.
An IBM POWER7 processor-based system.

6-1

Preface
The exercises depend on the availability of specific equipment in your
classroom.
All exercises for this unit depend on the availability of specific equipment in your
lab and at your desk. You will need:
- A managed system is required, configured with two virtual I/O servers
running Version 2.1.3.10-FP23, and two AIX 7.1 client partitions installed.
- Each client partition must have rootvg installed on a VSCSI disk.
- Each client partition must have a virtual Ethernet adapter bridged by an SEA
on the VIO server.
- A system is required from which to execute remote commands to the HMC
(by way of SSH)
Hints are provided for the exercises in case you need them and to provide
solutions for the exercise steps. All hints are marked by a sign.
Introduction
The following diagram represents the network configuration that each team will have set up
at the end of Part 3 of this exercise. The Ethernet adapter names shown in the diagram
6-2

V7.0.2
EXempty
could be different in your system configuration. Additional physical or virtual adapters

would cause different adapter numbering as well.
At the beginning of this exercise, each student should have an assigned virtual I/O server
and client LPAR installed. An SEA is already defined and bridges a unique VLAN. The
bridged VLAN ID depends on the student number.
Important
An SEA implementation must be done carefully to avoid any problem in the network. For
example, mismatching SEA and SEA failover configuration or configuring control channel
adapters in different VLANs can lead to an ARP storm in the physical switches that will
completely flood your network. Here are the requirements for configuring the SEA failover
feature.
One SEA on one VIO server acts as the primary (active) adapter, and the second
SEA on the second VIOS acts as a backup (standby) adapter.
Each SEA will have one virtual Ethernet adapter with the Use this adapter for
Ethernet bridging flag (previously known as the Access external network flag,
or trunk flag) checked.

6-3
- This adapter on both the SEAs must have the same PVID, but will have a
different priority value. If additional IEEE 802.1q VLAN IDs are defined for the
adapter, they must be the same on both VIO servers.
- The priority value defines which of the two SEAs will be the primary and
which will be the backup. The lower the numerical priority value, the higher
the importance, for example an adapter with priority value one will have the
highest importance.
An additional virtual Ethernet adapter, which belongs to a unique VLAN on the
system, is used to create the control channel between the SEAs and must be
specified in each SEA when configured in ha_mode.
- The purpose of this control channel is to communicate between the two SEA
adapters to determine when a failover should take place.
In order to set up the SEA failover feature, two virtual I/O servers must be used, and each
SEA in these VIO servers must bridge the same VLAN. You need to plan this SEA
configuration as a team of two students. Your actual VLAN configuration needs to be
changed to match the VLAN IDs referenced in Table 11 below. This table must be your
reference when setting up the SEA.
Table 11: Team numbers and VLAN IDs
Team #
Students #
Primary VIOS
trunk priority 1
Team 1
Student1
vios1
Student2
Team 2
Student3
vios3
Student4
Team 3
Student5
vios5
Student6
Team 4
Student7
vios7
Student8
Team 5
Student9
vios9
Student10
Team 6
Student11
vios11
Student12
The exercise is presented in three parts.
Secondary
Bridging Control
VIOS
VLAN ID channel
trunk priority 2
VLAN ID
vios2
10
19
vios4
20
29
vios6
30
39
vios8
40
49
vios10
50
59
vios12
60
69
Part 1: Setting the virtual Ethernet adapters and trunk priorities.

In this part, you will work alone on your assigned VIO server. You will remove
your existing SEA configuration and then modify your virtual Ethernet adapter
VLAN ID and set the trunk priority. You will configure an additional virtual
Ethernet adapter for the SEA control channel.
Part 2: Create the SEA failover feature
6-4

V7.0.2
EXempty
In this part, you will synchronize with your teammate to create the SEA device on
your assigned VIO server.
Part 3: Testing the SEA failover feature
You will work as a team to shut down some components in the configuration and
check whether the failover occurs.
Part 4: This is an optional exercise where you set the VIO IP address on an
additional virtual Ethernet adapter.
Part 1: Setting the virtual Ethernet adapters and trunk priority

At this point, the SEAs defined on your team's virtual I/O servers do not bridge the same
VLAN ID. Your existing SEA must be removed in order to modify your virtual Ethernet
adapter VLAN ID configuration. In part one, you work alone on your assigned virtual I/O
server.
__ 1. Your client LPAR must be shut down before performing these steps. Open a virtual
terminal or a Telnet session on your assigned AIX client LPAR, and perform a
shutdown.
Run the shutdown -F command.
__ 2. Open a console terminal window on your assigned Virtual I/O server and record the
IP address, host name, network mask, default gateway, and configured DNS server
IP address. Record the information here.
Host name: _______________________________________________________
IP address: _______________________________________________________
Netmask: _________________________________________________________
Default gateway: ___________________________________________________
DNS server IP address: _____________________________________________
__ 3. Before removing the SEA configuration from your assigned VIO server, you must
remove the IP address on its interface. In your virtual I/O server partition's console
session, use the lsdev command to find out the SEA name. Write down the adapter
name here: _______________
Run the lsdev command. You should see the SEA name ent3 (if you have
followed the steps in the previous exercises).
$ lsdev -virtual | grep Shared
ent3
Available
Shared Ethernet Adapter
__ 4. In your virtual I/O server partition's console session, use the rmtcpip -interface
<interface name> command to remove the virtual I/O server TCP/IP configuration.
Specify the interface name of your SEA.

6-5
Run the command:

$ rmtcpip -interface en3
Parameters to be reset:
Host name: No
Name server: No
Effective immediately: Yes
Routing: No
Answer y to Are you sure?
__ 5. In your Virtual I/O Server partition's console session, use the rmdev command to
remove the existing SEA, and its associated interface devices. Use the SEA adapter
name you wrote down in Step 3.
If the SEA device is ent3, then run the following command sequence:
$ rmdev -dev ent3
$ rmdev -dev en3
$ rmdev -dev et3
__ 6. Edit your assigned VIO server's Normal profile and modify the virtual Ethernet
adapter to use the new virtual LAN ID and priority value determined from Table 11.
Set the Trunk priority value according to your Virtual I/O Server function (primary or
secondary). Keep the Access external network flag checked.
Select your assigned VIO server and then run the Configuration > Manage
Profiles task.
Select the Normal profile, and use the Edit option on the Actions menu to edit
the profile.
6-6

V7.0.2
EXempty
On the Virtual Adapters tab, select the virtual Ethernet adapter (the adapter ID
should be 11), and use the Edit option on the Actions menu to edit the Ethernet
adapter properties.
In the Virtual Ethernet Adapter Properties window, change the VLANID (Port
Virtual Ethernet) to the value specified in Table 11. Set the Trunk priority to the
correct value. (If your Virtual I/O Server is primary, then the Trunk priority is 1. If
your Virtual I/O Server is secondary, the Trunk priority is 2.) Keep the Access
external network check box selected.
Do not close the Logical Partition Profile Properties window yet.
__ 7. Create an additional virtual Ethernet adapter. This adapter must belong to a unique
VLAN on the system. It will be used as a control channel between the two SEAs to
determine when a failover should take place. Use the Adapter ID 13 and set the
VLAN ID as specified in Table 11 on page 6-4. Be sure to use the default VSwitch
ETHERNET0(Default).
On the Virtual Adapters tab, use the Create Virtual Adapter > Ethernet
Adapter... option on the Actions menu to create a virtual adapter.

6-7
When the Create Virtual Ethernet Adapter window opens, set the Adapter ID
and VLAN ID as specified in Table 11 on page 6-4. Do not check the Use this
adapter for Ethernet bridging check box. Here is an example for vios1:
Click OK to save the profile changes; then close the Profile Properties window.
__ 8. Shut down your assigned VIO server. In your virtual I/O server partition's console
session, run the shutdown -force command. When shut down, use the HMC to
activate it using the Normal profile.
To activate the Virtual I/O Server, select your assigned VIO server and the
Operations > Activate > Profile task.
Select the Normal profile; then click OK.
__ 9. When activated, open a virtual terminal on your assigned Virtual I/O Server, and run
the lsdev -virtual | grep ent command. You should see two virtual Ethernet
adapters. If not, do not proceed. Check your partition profile.
Here is an example command and its output, which shows ent2 and ent3. The
Ethernet adapters might have different names in your environment.
$ lsdev -virtual | grep ent
__ 10. In order to be sure that you use the proper virtual Ethernet device names when
creating the SEA, run the entstat -all entX | grep VLAN command (where X is
the adapter number) in your VIO server partition's console session to check the
VLAN ID of each virtual Ethernet adapter. Record which virtual adapter will be used
for bridging your VLAN and which one will be used as the control channel adapter.
Virtual adapter to use for creating the SEA: _______________________________
6-8

V7.0.2
EXempty
Virtual adapter to use as control channel: ________________________________

If your VLAN IDs do not match with the values in Table 11 on page 6-4, do not
proceed. Check your VIO server profile configuration.
Here is an example command and its output, which shows the VLAN IDs for the
ent2 and ent3 devices. In this example, ent2 will be used as the virtual Ethernet
adapter for creating the SEA, and ent3 will be used as the control channel
adapter.
$ entstat -all ent2 | grep VLAN
Port VLAN ID:
10
VLAN Tag IDs: None
$ entstat -all ent3 | grep VLAN
Port VLAN ID:
19
VLAN Tag IDs: None
__ 11. Use the entstat -all entX | grep Switch command to check that both virtual
Ethernet adapters are using the default virtual switch ID ETHERNET0. If not, do not
proceed. Check your VIO server profile configuration.
Here is an example command and its output, which shows ent2 and ent3 using
the switch ID ETHERNET0.
$ entstat -all ent2 | grep Switch
$ entstat -all ent3 | grep Switch
__ 12. Modify your client LPAR VLAN ID. Edit your assigned LPAR's Normal profile, and
modify the virtual Ethernet adapter to use the new virtual LAN ID value. Refer to
Table 11 on page 6-4 for VLAN ID. Do not check the Access external network flag.
Select your assigned LPAR and the Configuration > Manage Profiles task.
Select the Normal profile, and use the Edit option on the Actions menu to edit
the profile.

6-9
On the Virtual Adapters tab, select the virtual Ethernet adapter (the adapter
ID should be 11), and use the Edit option on the Actions menu to edit the
Ethernet adapter properties.
In the Virtual Ethernet Adapter Properties window, change the VLANID to the
value specified in Table 11. Do not check the Use this adapter for Ethernet
bridging flag. Here is an example with lpar1:
Select OK to save the profile; then close the Properties window.


V7.0.2
EXempty
__ 13. Activate your client LPAR using the Normal profile. When up and running, open a
virtual console and run an entstat command to check the VLAN ID of your virtual
Ethernet adapter. The value should reflect your change.
Run the following command to see the VLAN ID of the virtual Ethernet adapter
on your client partition. Here is an example with VLAN 30 on lpar3:
$ entstat -d ent0 | grep "Port VLAN ID"
Port VLAN ID: 30

6-11
Part 2: Create the SEA failover feature

Please read this before proceeding: Mismatching SEA and SEA failover could cause
broadcast storms to occur and affect the stability of the network. When creating the SEA
failover, it is imperative that:
The control channel adapters on both VIO servers must be defined on the same
VLAN. If not, when creating the SEA failover, an ARP storm can flood your
network.
When creating the SEA using the mkvdev command, you specify the control
channel (ctl_chan) attribute and the high availability mode (ha_mode) attribute in
the command.
On a completely new installation, you first define the primary SEA on one VIO
server, and then the secondary SEA on the other VIO server.
Ask your instructor to verify the control channel and virtual adapters configuration before
performing the SEA creation.
__ 14. Check with your teammate that the virtual Ethernet adapters have been created with
the correct VLAN IDs and are using the default switch ID ETHERNET0. If not, do not
proceed. Fix the problem before creating the SEA failover configuration.
__ 15. If your assigned VIO is primary, create your SEA first. If your assigned VIOS is the
secondary, wait for your team partner to indicate that they have created the primary
SEA before proceeding with the remainder of this step.
In your virtual I/O server partition's console session, run the mkvdev command that
will create the SEA. Use the proper device names for the physical adapter (it should
be ent0), the virtual Ethernet adapter (used for bridging your VLAN), and the control
channel adapter. Use the adapter numbers you recorded previously in Step 10 on
page 6-8. Set the ha_mode flag to auto.
Here is an example command to create the SEA using the ent0 physical adapter,
ent2 virtual adapter for bridging, and the ent3 control channel adapter (the ha_mode
is set to auto). Remember to specify the correct default VLAN ID value.
$ mkvdev -sea ent0 -vadapter ent2 -default ent2 -defaultid 30
-attr ctl_chan=ent3 ha_mode=auto
The command should print out that a new device is available, for example:
ent4 Available
en4
et4
If you just created the SEA for the primary VIO, inform your team partner to proceed
with creating the secondary SEA before you continue with the next step.
__ 16. Use the lstcpip command to list out all available Ethernet devices and verify that a
new SEA device was created.

V7.0.2
EXempty

$ lstcpip -adapters
Ethernet adapters:
(14104003)
(14104003)
ent2 Available
ent3 Available
ent4
Available
Shared Ethernet Adapter
Alternatively, the lsdev | grep ent command could have been used to get this
information.
__ 17. Verify the SEA configuration using the lsmap command. Notice that in this output, it
is expected that ent2 is the Virtual Ethernet bridge adapter, ent0 is the physical
Ethernet adapter and ent3 is the control channel.
You should see the following if you issue the lsmap -all -net command:
$ lsmap -all -net
SVEA Physloc
------ -------------------------------------------ent2 U8233.E8B.1084AER-V1-C11-T1
SEA
Backing device
Status
Physloc
ent4
ent0
Available
U5877.001.RCH8623-P1-C4-T1
SVEA Physloc
------ -------------------------------------------ent3 U8233.E8B.1084AER-V1-C13-T1
SEA
NO SHARED ETHERNET ADAPTER FOUND
__ 18. Run the entstat -all <ent#> (replace ent# by your SEA name) command and
check for the following parameters:
The state of the SEA adapter (primary or backup).
Example command and output if your VIO is primary:
$ entstat -all ent4 | grep "^ *State"
State: PRIMARY
Example command and output if your VIO is backup:
State: BACKUP

6-13
The trunk adapter priority value and whether the adapter is active.
Example command and output if your VIO is Primary.
$ entstat -all ent4 | grep Priority
Priority:1
Priority:1 Active: True
Example command and output if your VIO is Backup:
$ entstat -all ent4 | grep Priority
Priority:2
Priority:2 Active: False
The control channel adapter name and its PVID.
$ entstat -all ent4 | grep "Control Channel"
Control Channel PVID: 19
Control Channel Adapter: ent3
Some more SEA attributes can be seen using the lsdev command. You should
see the following information if you run the lsdev -dev ent4 -attr command:
$ lsdev -dev ent4 -attr
$ lsdev -dev ent4 -attr
attribute
value
description
user_settable
accounting
disabled Enable per-client accounting of network statistics
True
ctl_chan
ent3
Control Channel adapter for SEA failover
True
gvrp
no
Enable GARP VLAN Registration Protocol (GVRP)
True
ha_mode
auto
High Availability Mode
True
jumbo_frames no
Enable Gigabit Ethernet Jumbo Frames
True
large_receive no
Enable receive TCP segment aggregation
True
largesend
0
Enable Hardware Transmit TCP Resegmentation
True
netaddr
0
Address to ping
True
pvid
10
PVID to use for the SEA device
True
pvid_adapter ent2
Default virtual adapter to use for non-VLAN-tagged packets
True
qos_mode
disabled N/A
True
real_adapter ent0
Physical adapter associated with the SEA
True
thread
1
Thread mode enabled (1) or disabled (0)
True
virt_adapters ent2
List of virtual adapters associated with the SEA (comma separated)
True
__ 19. The SEA state can also be checked in the error log. Run the errlog command, and
check for an entry with the description BECOME PRIMARY or BECOME BACKUP,
depending if your virtual I/O server is primary or backup. List the detailed information
of these entries.

V7.0.2
EXempty
You should see an entry in the error log similar to the following when you issue
the errlog command on the primary VIO server:
$ errlog -ls
-------------------------------------------------LABEL:
SEAHA_PRIMARY
IDENTIFIER:
E136EAFA
Date/Time:
Sequence Number:
Machine Id:
Node Id:
Class:
Type:
WPAR:
Resource Name:
Resource Class:
Resource Type:
Location:
Tue Jan 8 05:05:43 CET 2013

63
00F015B34C00
sys464_vios1
H
INFO
Global
ent4
adapter
sea
Description
BECOME PRIMARY
Probable Causes
BECOME PRIMARY
Failure Causes
BECOME PRIMARY
Recommended Actions
BECOME PRIMARY
Detail Data
Become the Primary SEA

6-15
You should see an entry in the error log similar to the following when you issue
the errlog command on the secondary VIO server:
$ errlog -ls
--------------------------------------------------LABEL:
SEAHA_BACKUP
IDENTIFIER:
40D97644
Date/Time:
Sequence Number:
Machine Id:
Node Id:
Class:
Type:
WPAR:
Resource Name:
Resource Class:
Resource Type:
Location:
Tue Jan 8 05:24:08 CET 2013

70
00F015B34C00
sys464_vios2
H
INFO
Global
ent4
adapter
sea
Description
BECOME BACKUP
Probable Causes
BECOME BACKUP
Failure Causes
BECOME BACKUP
Recommended Actions
BECOME BACKUP
Detail Data
Become the Backup SEA
__ 20. Configure the shared Ethernet interface with the IP address, host name, network
mask, default gateway, and DNS server IP address (if any) that you recorded in
Step 2 on page 6-5 of this exercise. You can use the mktcpip command or the
cfgassist command to launch the SMIT menu.
Here is the syntax for the mktcpip command for the options you need to use:
mktcpip -interface Interface -hostname Hostname -inetaddr IPaddress \
[ -start ] [ -netmask nmask ] [ -gateway gway ] \
[ -nsrvaddr NameServerAddr [ -nsrvdomain Domain ] ]
Substitute the appropriate configuration information recorded earlier.

V7.0.2
EXempty
__ 21. Using the HMC GUI, you can have a graphical view of the overall network
configuration on your managed system. Select your managed system in the
navigation area; then select Configuration > Virtual Resources > Virtual Network
Management.
Select your managed system and then Configuration > Virtual Resources >
Virtual Network Management. In the example shown below, the VLAN IDs 3, 5,
and 10 are bridged, and you can see the name of the VIO partition and physical
adapter name configured in the SEA performing the bridging. The VLAN 10 is
bridged by two physical adapters. The two physical adapters are listed in the
order of their trunk priority. This window is a global view of the system VLAN
configuration for the selected VSwitch. In the example, the default ETHERNET0
VSwitch is selected. If you create another VSwitch, you will be able to select it
and check its VLAN configuration.

6-17
Only partitions with an available IP address that can be reached by the HMC are
listed in the window.
__ 22. When the Virtual Network Management window opens, select your VLAN ID by
clicking the radio button next to it. A detailed view of the SEAs and the partitions
should be displayed. Check that both of your team's Virtual I/O Servers are listed
with their associated SEA and priority value.
Select your managed system and then Configuration > Virtual Resources>
Virtual Network Management. A window should appear like the one shown
below. In this example, once VLAN ID 10 is selected in the VLANs table, the
additional details are displayed. The additional details consists of two tables. The
first table lists the names of the LPARs that are currently active on the selected
VLAN, along with information (device name and virtual slot number) of the virtual
adapter connected to the VLAN. The second table shows details of any Shared
Ethernet Adapters configured on the selected VLAN, including information on the

V7.0.2
EXempty
physical adapter (including location code), trunk priority, and the name of the VIO
partition that owns the adapter.
Part 3: Testing the SEA failover

In this part of the exercise, you will initiate an SEA failover in two different ways:
By manually changing the SEA ha_mode parameter from auto to standby on the
VIOS with the primary adapter (priority 1); changing the ha_mode must always
be performed from the VIO with the adapter having the highest priority.
By manually shutting down the primary VIOS. In this case, the backup SEA will
detect that the heartbeat messages are no longer received over the control
channel adapter, and a failover will be initiated.
Testing the SEA failover means that you must work as a team with your teammate.
__ 23. Open a Telnet session or a virtual terminal console on your client LPARs, and start a
ping to your HMC IP address. Leave the ping running for the rest of the exercise to
verify that you have continuous connectivity.
__ 24. Open a console window on the VIO server with the primary adapter (the SEA with
trunk priority one. Run the chdev command to switch to the standby adapter.
Change the ha_mode from auto to standby. Check for the ping command running in
your client LPARs.
You might experience (in the ping output) up to a 30-second delay in failover when
using SEA failover. The behavior depends on the physical network switch and the
spanning tree settings.

6-19
Issue the chdev command to change the ha_mode attribute. (Your SEA name
might be different in your configuration.)
$ chdev -dev ent4 -attr ha_mode=standby
ent4 changed
__ 25. Use the entstat command to check whether the failover was successful. In your
VIO server partition with the primary adapter's console session, the status should
have changed from PRIMARY to BACKUP. Perform the checking in the other VIO
server; the status should have changed from BACKUP to PRIMARY.
You should see the following if you issue the entstat command on the VIO
server with the trunk priority of one (your SEA name might be different in your
configuration):
State: BACKUP
You should see the following if you issue the entstat command on the VIO
server with the trunk priority of two (your SEA name might be different in your
configuration):
State: PRIMARY
Optionally, you can check the active status of the trunk adapter. You should see
the following information when running the entstat command on the VIO server
with the trunk priority one:
$ entstat -all ent4 | grep Active
Priority: 1 Active: False
You should see the following information when running the entstat command
on the VIO server with the trunk priority two:
$ entstat -all ent4 | grep Active
Priority: 2 Active: True
__ 26. Check in the error log for a new entry that shows the status change. You should
notice the entry BECOME BACKUP.
You should see the following if you issue the errlog command on the VIO server
with the trunk priority one:
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
40D97644
0108172713 I H ent4
BECOME BACKUP
You should see the following if you issue the errlog command on the VIO server
with the trunk priority two:
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
E136EAFA
0108172713 I H ent4
BECOME PRIMARY

V7.0.2
EXempty
__ 27. Change the ha_mode back from standby to auto. Use the entstat command to
check whether the fallback is successful.
Check for the ping command running in your client LPARs. Note that you might
experience up to 30 seconds of delay in fallback when using SEA failover. The
behavior depends on the physical network switch and the spanning tree settings.
$ chdev -dev ent4 -attr ha_mode=auto
ent4 changed
__ 28. Test the SEA failover by performing a shutdown of the VIO server with the primary
trunk adapter. Be sure to first shut down the client LPAR that has a VSCSI disk
served by this VIO server. Wait for the AIX LPAR to have a state of Not Activated in
the HMC interface before shutting down the VIO server.
Open a virtual console on the client LPAR and run the shutdown command.
# shutdown -F
Open a virtual console on the VIO server and run the shutdown command.
$ shutdown -force
__ 29. On the running VIO server, use the entstat command (entstat -all
<SEA_adapter> | grep -i state) to check whether the SEA has failed over to the
standby adapter.
__ 30. Activate the VIO server that was previously shut down. When the VIO server has
booted, login as padmin and use the entstat command to check whether the SEA
has failed back to the primary adapter.
After a reactivation of the VIO server, the SEA always fails back to the VIO with
the primary adapter.
__ 31. Activate the client LPAR that was previously shut down.
__ 32. That is the end of part three of the exercise. Notify your instructor that you are
finished. The next part is an optional exercise.

6-21
Part 4: (Optional) Setting the VIO server IP address on an additional

virtual Ethernet adapter
Note
Setting an IP address on the SEA interface is the more common approach when you
decide to configure TCP/IP on the VIO server. If you use the SEA remote address to ping
feature, you need to set an IP address on the SEA interface; however, there are some
cases where configuring an IP address on the SEA interface is not recommended, for
example, with some installation specific situations that require optimum virtual Ethernet
performance. Another reason is when performing LPAR mobility in a dual VIO environment.
Defining an additional virtual Ethernet adapter to carry the IP address is the solution. This
has the advantage of providing IP configuration flexibility. In a dual VIO server configuration
with the SEA failover setup, you could remove the one SEA configuration without losing
network access to the VIO server.
In part 4 of this exercise, you will configure an additional virtual adapter and set the VIO
server IP address on its interface.
The following diagram helps you identify your configuration at the end of part 4:

V7.0.2
EXempty
__ 33. Use the HMC to dynamically create an additional virtual Ethernet adapter on your
assigned VIO server. Use the adapter ID 14, and use the same VLAN ID that you
used in part one of the exercise when you configured your SEA failover. Refer to
Table 11 on page 6-4 if needed.
Go to the Server Management application on the HMC.
Select your assigned VIO server, and use the Dynamic Logical Partitioning >
Virtual Adapters task.
On the Actions menu, select Create Virtual Adapter > Ethernet Adapter...

6-23
In the screen that pops up, set the correct VLAN ID, and then click OK. Here is
an example screen on vios4 (verify that the VSwitch field is set to ETHERNET0
(Default) value):
Your Virtual Adapters dialog should now look like this:
Click OK. The dynamic operation should succeed.

__ 34. Make the dynamic change on your assigned VIO server persistent across
reactivations of the partition by saving the current configuration and overwriting the
existing Normal profile.
Select your assigned VIO server, and open the Configuration > Save Current
Configuration task.

V7.0.2
EXempty
Select the option Overwrite existing profile, and make sure that Normal is the
selected profile. Click OK to save the changes, then click Yes to confirm that you
want to overwrite the existing profile.
__ 35. Since you added the virtual Ethernet adapter dynamically, you must run a cfgdev
command to have the VIO recognize the new device; then, verify that there is one
new virtual Ethernet adapter available. Use the -virtual option to lsdev to see
only virtual devices.
Here are example commands and outputs. In this example, ent5 is the new
virtual Ethernet adapter.
$ cfgdev
$ lsdev -virtual | grep ^en
ent4 Available Shared Ethernet Adapter
__ 36. In your virtual I/O server partition's console session, use the rmtcpip -interface
<interface name> command to remove the virtual I/O server TCP/IP configuration.
Specify the interface name of your SEA. You can check the SEA name using the
lsmap -all -net command.
Run the command:
$ rmtcpip -interface en4
Parameters to be reset:
Host name: No
Name server: No
Effective immediately: Yes
Routing: No
Are you sure? (y/N)y
__ 37. Configure the newly created virtual Ethernet adapter interface with the IP address,
host name, network mask, default gateway, and DNS server IP address that you
recorded in Step 2 on page 6-5 at the beginning of this exercise. You can use the
mktcpip command, or the cfgassist command to launch the SMIT menu.
Here is the syntax for the mktcpip command for the options you need to use:
mktcpip -interface Interface -hostname Hostname -inetaddr IPaddress \
[ -start ] [ -netmask nmask ] [ -gateway gway ] \
[ -nsrvaddr NameServerAddr [ -nsrvdomain Domain ] ]
Substitute the appropriate configuration information (recorded at the beginning of
this exercise).
End of exercise

6-25

V7.0.2
EXempty
Exercise 7. Dual VIO server configuration with

MPIO in the client partition
(with hints)

This exercise provides experience in configuring high availability in a
VSCSI environment. Students will implement a dual Virtual I/O Server
configuration with multipath I/O in the client partitions.

Set up a high availability disk environment with MPIO configured in
the client partition
Introduction
The purpose of the exercise is to give the students some experience in
implementing a high availability configuration which includes dual VIO
servers and MPIO set up in the client partition.
Requirements
This workbook.
A workstation with a web browser and Internet connectivity.
IBM POWER7 processor-based system.
Exercise 7. Dual VIO server configuration with MPIO in the client

7-1

Preface
- A managed system, configured with two VIO servers Version 2.1 or later and
two AIX V7.1 client partitions installed.
- Each client partition must have rootvg installed on a VSCSI disk.
- Each client partition must have a virtual Ethernet adapter bridged by an SEA.
- A system is needed from which to execute remote commands to the HMC
(using SSH).
Introduction
In this exercise, you will configure two VIO servers to provide redundant paths to your
VSCSI disk resource. In this exercise, you will set up MPIO for AIX in your client LPAR and
test the configuration.
7-2

V7.0.2
EXempty
The diagram below represents the VSCSI configuration that each team will have set up at
the end of part 3 of this exercise. The adapter names shown in the diagram could be
different in your system configuration. Additional virtual adapters would cause different
adapter numbering as well.
In order to set up MPIO in a client LPAR, two Virtual I/O Servers must be used. Each VIO
server must serve the same shared LUN to the client LPAR. This LUN must be accessible
by both the VIO servers. The VSCSI disk in the client LPAR will have two MPIO paths
provided by two different VIO servers. Each VSCSI client adapter in the client LPAR must
be connected to a VSCSI server adapter in a different VIO server.
Your actual VSCSI configuration needs to be changed to match the diagram above. You
need to add a VSCSI client-server configuration between your client LPAR to your
teammate's VIO server, and then create a new virtual target device that refers to the
backing LUN.
You need to plan this MPIO configuration as a team of two students. During this exercise,
you will have to perform some steps as a team or work on your teammate's VIO server.
Refer to the table below for your team number.

7-3
Table 12: Team numbers

Managed
Managed System 1
system
Team
number
Student
number
Virtual
I/O
Server
name
Client
LPAR
name
Managed System 2
3
10
11
12
vios1
vios2
vios3
vios4
vios5
vios6
vios7
vios8
vios9
vios10
vios11
vios12
lpar1
lpar2
lpar3
lpar4
lpar5
lpar6
lpar7
lpar8
lpar9
lpar10
lpar11
lpar12
The exercise is presented in four parts.

Part 1: Create the VSCSI clients and server adapters
You will add a VSCSI client/server communication between your client LPAR and
your teammate's VIO server.
Part 2: Create the virtual target device
You will create a virtual target device on your teammate's Virtual I/O Server to
get the shared LUN accessible to your assigned client LPAR.
Part 3: MPIO failover tests
Shut down some components in the configuration to see how the redundant
architecture reacts.
Part 4 (optional): Working with MPIO paths priority
Work with the MPIO path's priority. This part is optional.
7-4

V7.0.2
EXempty
Part 1: Create the VSCSI client and server adapters

At this point, your client LPAR has a VSCSI disk served by your assigned VIO server. You
must create a VSCSI client/server relationship between your assigned client LPAR and
your teammate's VIO server. Your client LPAR will have two VSCSI client adapters, each
one mapping to one of the two VIO servers.
__ 1. Using the HMC, select your teammate's VIO server and dynamically add a VSCSI
server adapter. Use adapter ID 16. This server adapter is not required (that is, you
do not have to check the box to make it a required adapter).
Note
For example, if you are student1, your teammate is student2. You must work on student2's
VIO server (vios2), and your teammate (student2) must work on vios1.
Go to the HMC interface, and go to the LPAR table view.

To dynamically add a virtual I/O adapter, select the VIOS partition name and run
the Dynamic Logical Partitioning > Virtual Adapters task.
Run the Create Virtual Adapter > SCSI Adapter... task on the Actions menu.
In the window that opens, configure the adapter ID 16. Select the option Only
selected client partition can connect, then select your partition from the drop
down list. Enter 16 as the Client adapter ID.
Click OK, and then click OK again to complete the operation.
In this example, student1 creates the VSCSI adapter ID 16 on VIOS2.
__ 2. Log in to the VIOS partition and run cfgdev. List out the virtual devices to verify it
was created. Note the new vhost name. If you have been following the instructions,
it should be called vhost1.
New vhost name is: _________________________________________________

7-5
The output from lsdev -virtual | grep vhost should look like this if you have
been following the instructions in this exercise:
$ cfgdev
$ lsdev -virtual | grep vhost
vhost0
Available
vhost1
Available
__ 3. Using the HMC, select your assigned client LPAR and dynamically add a VSCSI
client adapter. Use the client adapter ID 16. Have it point to your teammate's VIOS
partition and adapter ID 16. This client adapter is not required (that is, you do not
have to check the box to make it a required adapter).
To dynamically add a virtual I/O adapter, select your assigned LPAR and run the
Dynamic Logical Partitioning > Virtual Adapters task.
Run the Create Virtual Adapter > SCSI Adapter... task on the Actions menu.
In the window that opens, configure the adapter ID. Choose your teammate's
VIOS and the adapter ID.
Click OK, and then click OK again to complete the operation.
In this example, student1 creates VSCSI slot number 16 on lpar1.
__ 4. To configure the new VSCSI adapter, run cfgmgr on your assigned client LPAR.
Check that the new device (vscsi1) is available.
Your lsdev -Cc adapter output should look like the following:
# lsdev -Cc adapter | grep vscsi
vscsi0 Available Virtual SCSI Client Adapter
vscsi1 Available Virtual SCSI Client Adapter
__ 5. Using the HMC, save the current configuration of your assigned LPAR and your
teammate's VIO server into new profiles. Name these new profiles Normal-mpio.
7-6

V7.0.2
EXempty
Note
Do not forget to perform this step or you will lose all your dynamic operations
previously performed in case of a shutdown-reactivate of your partitions.

Select your teammate's VIO server, and run the Configuration > Save Current
Configuration task.
In the window that opens, specify the new profile name: Normal-mpio.
Click OK to complete the operation.
Perform the same operation for your assigned LPAR. Here is an example with
lpar1.

7-7
Part 2: Create the virtual target device

At this point, you have a VSCSI client/server relationship between the two Virtual I/O
Servers and your assigned client LPARs. Your client LPAR now has two VSCSI client
adapters, each mapping to one of the two Virtual I/O Server LPARs.
You must create a virtual target device on your teammate's VIO server in order to map the
physical disk device used as VSCSI disk in your assigned LPAR.
__ 6. Identify the physical disk number used as a VSCSI disk by your assigned client
LPAR (this is the hdisk device you selected when you set up your client LPAR in a
previous exercise). You can identify it by performing the following: open a virtual
terminal to your assigned Virtual I/O Server, and then run the lsmap command to
identify the hdisk mapped to vhost0. Record this hdisk number here:
Here is an lsmap command output example on vios1 showing hdisk1 is allocated
to vhost0.
$ lsmap -vadapter vhost0
SVSA
Physloc
Client Partition ID
--------------- -------------------------------------------- -----------------vhost0
U8233.E8B.1084AER-V1-C12
0x00000015
VTD
Status
LUN
Backing device
Physloc
lpar1_vtd
Available
0x8100000000000000
hdisk1
U5877.001.RCH8623-P1-C6-T1-W500507680140B855-L1000000000000
__ 7. Now that you know the disk number, use the lspv command to determine the
physical volume ID of that disk. Record this PVID here:
________________________________________________________________
Here is an lspv command output example on VIOS1 showing the PVID of
hdisk1.
$ lspv
NAME
hdisk0
hdisk1
hdisk2
hdisk3
hdisk4
hdisk5
hdisk6
hdisk7
PVID
00f784aee0fd700a
00f784ae17ad9d8b
00f784ae1822ad34
none
none
none
none
none
VG
rootvg
None
None
None
None
None
None
None
STATUS
active
__ 8. Now go to your teammate's Virtual I/O Server and identify the physical volume ID of
the hdisk device you recorded in the previous step. Open a virtual terminal to your
teammate's Virtual I/O Server. Run the lspv command to list the physical volumes
and locate the hdisk device. Record this hdisk number here: _________________
7-8

V7.0.2
EXempty
Here is an lspv command output example on VIOS2 showing hdisk1.

$ lspv
NAME
hdisk0
hdisk1
hdisk2
hdisk3
hdisk4
hdisk5
hdisk6
hdisk7
PVID
00f784aee103cdab
00f784ae17ad9d8b
00f784ae1822ad34
none
none
none
none
none
VG
rootvg
None
None
None
None
None
None
None
STATUS
active
__ 9. On your teammate's Virtual I/O Server, run the lsdev command to check if the
reserve policy attribute for this disk is set to no_reserve. If it is not, run the chdev
command to change the attribute value.
Here is an example with hdisk1:
$ lsdev -dev hdisk1 -attr | grep reserve_policy
reserve_policy single_path
Reserve Policy
$ chdev -dev hdisk1 -attr reserve_policy=no_reserve
hdisk1 changed
True
__ 10. On your teammate's Virtual I/O Server, run the mkvdev command to create the
virtual target device. Use the disk number you identified previously and the VSCSI
server adapter vhost1. Give it a target device name that make sense to you. For
example, if your assigned client LPAR is lpar1, name your target device lpar1_vtd.
Here is an example:
$ mkvdev -vdev hdisk1 -vadapter vhost1 -dev lpar1_vtd
lpar1_vtd Available
__ 11. On your teammate's Virtual I/O Server, run the lsmap -vadapter vhost1 command
to check that you have the correct backing storage mapping.
The output of lsmap -vadapter vhost1 should be similar to the following if
running on vios2. This example shows hdisk1 as the backing device with a virtual
target device name of lpar1_vtd. In this example, the Client Partition ID is 21
(0x15 in hexadecimal), confirming that this storage is being used by lpar1.
SVSA
Physloc
Client Partition ID
--------------- -------------------------------------------- -----------------vhost1
U8233.E8B.1084AER-V2-C16
0x00000015
VTD
Status
LUN
Backing device
Physloc
lpar1_vtd
Available
0x8100000000000000
hdisk1
U5877.001.RCH8623-P1-C7-T1-W500507680140B855-L1000000000000
__ 12. Log in to your assigned client LPAR and run the cfgmgr command to configure the
new MPIO path; then run the lspath command to verify that the VSCSI disk device

7-9
is accessible from two different paths. You should see two paths enabled for the
hdisk0 device.
The output of lspath should be similar to the following if running on lpar1. This
example shows there are two paths to the hdisk0 device.
# lspath
Enabled hdisk0 vscsi0
Enabled hdisk0 vscsi1
Part 3: MPIO failover tests

To perform the MPIO failover steps, you cannot work alone. You need to work with your
teammate. You will perform a shutdown of one of your team's Virtual I/O Servers that will
impact both teams' client LPARs.
Coordinate with your teammate before proceeding.
__ 13. You need to work with your teammate to perform these steps. Shut down one of
your Virtual I/O Servers by running the shutdown -force command.
$ shutdown -force
__ 14. When the Virtual I/O Server is shut down, open a virtual terminal on each client
LPAR served by this Virtual I/O Server.
__ 15. Run the lspath command on both LPARs to check the status of the paths to hdisk0.
$ lspath
__ 16. What are the statuses of the paths? Can you explain why?
The client LPAR that has its primary path served by the Virtual I/O Server that
has been shut down has one of its path statuses set to Failed (the path using
vscsi0). The other LPAR still has both path statuses marked as Enabled; the
path using the Virtual I/O Server that has been shut down is not marked as
Failed. This behavior is normal because the health check algorithm has not been
activated on the client LPARs (the hcheck_interval attribute is set to 0). When the
health check alogrithm is disabled, and the LPAR is using the failover path
selection algorithm, the status of the primary path is always updated (since the
LPAR detects that the path is no longer functioning), while the status of the
inactive path is not updated since the LPAR is not using it.
__ 17. Use the HMC GUI to activate the Virtual I/O Server shut down in Step 13. Use the
profile Normal-mpio. You do not need to wait for the partition to complete the boot
sequence before proceeding with the next step.
__ 18. On each client LPAR virtual terminal, run the chdev command to enable the health
checking function for the MPIO capable device hdisk0. Set the checking interval to
six. Remember to reboot each AIX instance after changing the value. If you
shutdown the partition, use the Normal-mpio profile to activate.

V7.0.2
EXempty
Use the following command to change the value of the parameter:

# chdev -l hdisk0 -a hcheck_interval=6 -P
A reboot of AIX is needed as the parameter cannot be changed dynamically, it
can only be changed in the ODM. It is not necessary to shutdown and then
reactivate the partition, only the operating system needs to reboot.
# shutdown -Fr
__ 19. When the client LPARs have booted, open a virtual terminal and check (using the
lspath command) which MPIO path is the active path for hdisk0.
Answer: __________________________________________________________
The following command sequence shows how to determine the paths available
for a device, and the priority of each path:
# lspath -Ht -l hdisk0
status name
parent path_id
Enabled hdisk0 vscsi0 0
# lspath -AHE -l hdisk0 -p vscsi0
attribute value description user_settable
priority 1
Priority
True
# lspath -AHE -l hdisk0 -p vscsi1
attribute value description user_settable
priority 1
Priority
True
The output shows there are two paths available to hdisk0, and both paths have
the same priority. In this case, path ID 0, which goes through the vscsi0 adapter
will be used by default.
__ 20. Perform a shutdown of one of your team's Virtual I/O Servers again.
$ shutdown -force
__ 21. When the Virtual I/O Server has shut down, check the status of the paths to hdisk0
on each AIX LPAR. Explain what you observe.
Both client LPARs will have one path marked as Failed, and one marked as
Enabled. The failed path will be the one using the VIO server that has been
shutdown. Only one of the LPARs will have been using the failed path as the
primary path. In the other LPAR where the failed path is the non-active path, the
healthcheck algorithm has detected the failure.
The following shows the expected output from the one of the client LPARs. The
path that has failed will depend on which VIO server was shut down. The -H flag

7-11
of lspath includes column headers in the output. The -t flag indicates that each
path description should also include the path ID value.
# lspath -Ht
status name
parent path_id
Failed hdisk0 vscsi0 0

The other client LPAR will have the other path marked as Failed.
# lspath -Ht
status name
parent path_id

Failed hdisk0 vscsi1 1
__ 22. Look at the error log in each AIX partition. You should see an entry indicating that a
path has failed for hdisk0.

V7.0.2
EXempty
The following is an example error log entry indicating a path failure for hdisk0.
The Detail Data section indicates the path ID of the failed path.
# errpt -a
--------------------------------------------------------------------------LABEL:
SC_DISK_ERR7
IDENTIFIER:
DE3B8540
Date/Time:
Sequence Number:
Machine Id:
Node Id:
Class:
Type:
WPAR:
Resource Name:
Resource Class:
Resource Type:
Location:
Tue Jan 8 22:36:19 CET 2013

406
00F784AE4C00
sys464_lpar1
H
PERM
Global
hdisk0
Description
PATH HAS FAILED
Probable Causes
ADAPTER HARDWARE OR CABLE
DASD DEVICE
Failure Causes
UNDETERMINED
Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES
CHECK PATH
Detail Data
PATH ID
0
SENSE DATA
0A00 2800 0084
0000 0000 0000
0000 0000 0000
0000 0000 0000
0000 0000 0000
12B8
0000
0000
0000
0000
0000
0000
0000
0000
0000
0804
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0200
0000
0000
0000
0000
0B00
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
__ 23. Use the HMC GUI to activate the Virtual I/O Server shut down in Step 20. Use the
profile Normal-mpio.
__ 24. When the VIO server has booted and you see the login prompt on the console
window, check the path status again in each client LPAR.

7-13
When the VIO server has booted, it is expected that both client LPARs will show
both paths with a state of Enabled:
# lspath -Ht
status name
parent path_id

__ 25. This is the end of part 3. Notify your instructor that you are finished. The next part is
an optional exercise.

V7.0.2
EXempty
Part 4: (Optional) Working with MPIO paths' priority

To perform these steps, you need to synchronize the actions with your teammate. You will
modify the path priority of your client LPARs to distribute the disk I/O activity to the same
VIO server. If you have followed the exercise steps until now, you will have each client
LPAR using a different VIO server for disk I/O activity.
__ 26. Change the MPIO path priority on your odd numbered client LPAR (that is, lpar1,
lpar3, lpar5, lpar7, and so on) in order to send both client LPARs disk I/O traffic to
the even numbered VIO server (lpar2, lpar4, and so on already use the even
numbered VIO server as the default path). Use the chpath command to change the
priority value of path 0 for hdisk0 from 1 to 2.
Note
The priority change does not require a reboot to take effect.
Open a terminal console on your odd numbered client LPAR. Here is an example
command sequence for an odd numbered LPAR. The first command determines
which parent device is used by the path with path ID 0. The second command
changes the priority of this path.
# lspath -Ht -l hdisk0
status name
parent path_id
# chpath -l hdisk0 -p vscsi0 -a priority=2
path Changed
__ 27. Check that your client LPARs are now using the same VIO server for disk I/O
activity.
__ a. On each client LPAR, open a terminal window and run the following command to
generate some disk I/O traffic:
# dd if=/dev/hdisk0 of=/dev/null
__ b. In a console window on each VIO server, run the topas command. Then type
capital D to monitor the physical disk activity. You should see activity on the
physical disk devices used as backing storage for the VSCSI disks used by your
client LPARs only on the even numbered VIO server.

7-15
The topas command output example shown below is from an odd numbered
VIO server. It shows no disk activity.
Topas Monitor for host:
sys464_vios1Interval:
2
Tue Jan 8 23:41:55 2013
===============================================================================
Disk
Busy% KBPS
TPS
KB-R
ART
MRT
KB-W
AWT
MWT
AQW
AQD
hdisk3
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
hdisk6
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
hdisk2
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
hdisk7
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
hdisk1
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
hdisk5
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
hdisk0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.8
0.0
0.0
hdisk4
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
The topas command output example shown below is from an even numbered
VIO server. It shows disk activity on two backing storage devices, hdisk1 (used
by lpar1) and hdisk2 (used by lpar2).
2
Tue Jan 8 23:42:39 2013
===============================================================================
Disk
Busy% KBPS
TPS
KB-R
ART
MRT
KB-W
AWT
MWT
AQW
AQD
hdisk1
56.9 10.7K
2.5K 10.7K 0.3 461.4
0.0
0.0
0.3
0.0
0.0
hdisk2
47.4 15.1K
3.6K 15.1K 0.1 424.5
0.0
0.0
2.9
0.0
0.0
hdisk6
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
hdisk7
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
hdisk0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.3
0.0
0.0
hdisk3
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
hdisk4
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
hdisk5
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
__ c. Keep the dd command running on each client LPAR (or restart it if it ended).
While monitoring the topas output on the Virtual I/O Servers, open another
terminal window on your odd numbered client LPAR, and change the priority
value of path ID 1 (the path will likely be using vscsi1 as the parent) from one to
two.
Note
The priority change does not require a reboot to take effect.
In a window on your odd numbered client LPAR, use the chpath command. Here
is an example:
$ chpath -l hdisk0 -p vscsi1 -a priority=2
Path changed
__ d. Check that there is disk I/O traffic now on both Virtual I/O Servers (one busy disk
on each VIO server).

V7.0.2
EXempty
The topas command output example shown below is from an odd numbered
VIO server. It shows disk activity only on hdisk1.
2
Wed Jan 9 00:05:23 2013
===============================================================================
Disk
Busy% KBPS
TPS
KB-R
ART
MRT
KB-W
AWT
MWT
AQW
AQD
hdisk1
77.9 15.5K
3.8K 15.5K 0.1
2.6K
0.0
0.0
6.5
0.0
0.0
hdisk6
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
hdisk2
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
hdisk3
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
hdisk7
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
hdisk5
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
hdisk0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
1.8
0.0
0.0
hdisk4
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
The topas command output example shown below is from an even numbered
VIO server. It shows disk activity only on hdisk2.
2
Wed Jan 9 00:06:13 2013
===============================================================================
Disk
Busy% KBPS
TPS
KB-R
ART
MRT
KB-W
AWT
MWT
AQW
AQD
hdisk2
10.4 30.5K
4.0K 30.5K 0.1 683.0
0.0
0.0
7.0
0.0
0.0
hdisk3
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
hdisk6
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
hdisk7
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
hdisk0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
1.5
0.0
0.0
hdisk1
0.0
0.0
0.0
0.0
0.0 733.9
0.0
0.0
6.9
0.0
0.0
hdisk4
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
hdisk5
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
__ e. In a terminal window on your odd numbered client LPAR, and change the priority
value of path ID 0 (the path will likely be using vscsi0 as the parent) from two
back to one, then perform the same change for path ID 1.
In a window on your odd numbered client LPAR, use the chpath command. Here
is an example:
Path changed
Path changed
__ 28. Stop the dd command on your client LPARs. That is the end of this optional
exercise. Notify your instructor that you are finished.
End of exercise

7-17

V7.0.2
EXempty
Exercise 8. Virtual Fibre Channel adapter

configuration
(with hints)

This exercise covers how to access an external LUN by adding a
virtual Fibre Channel adapter to a VIO client partition. Students
dynamically create virtual Fibre Channel adapters on the Virtual I/O
Server and the client logical partition. Then they map the virtual Fibre
Channel server adapter to an NPIV capable physical Fibre Channel
adapter. Students also examine the different NPIV configuration
attributes.

Configure a virtual Fibre Channel server adapter on the Virtual I/O
Server
Configure a virtual Fibre Channel client adapter on the client logical
partition
Use the HMC to work with the WWPN pair
Map the virtual Fibre Channel server adapter to a physical NPIV
capable Fibre Channel adapter port
Access an external LUN using virtual Fibre Channel
Introduction
In this exercise, you will create virtual Fibre Channel adapters (client
and server) to access an external LUN.
You will work alone using your client logical partition and use one
Virtual I/O Server that has an NPIV-capable physical Fibre Channel
adapter installed.
Requirements
This workbook.
Exercise 8. Virtual Fibre Channel adapter configuration

8-1
A computer with a web browser and a network connection to an

HMC running Version 7.3.4 fix pack 2 or later, configured to support
a POWER7 processor-based system.
A Virtual I/O Server at version 2.1 and an AIX 7.1 client logical
partition.
A physical Fibre Channel adapter (NPIV-capable) connected to an
NPIV-capable SAN switch with external LUNs.
Utility for running telnet or SSH.
8-2

V7.0.2
EXempty

Preface
All procedures in this exercise depend on the availability of specific equipment.
You will need a computer system connected to the Internet, a web browser, a
telnet program, and a utility for running SSH. You will also need a managed
system with Fibre Channel adapters (NPIV-capable). All lab systems need to be
accessible to each other on a network.
NPIV (N_Port ID virtualization) is introduced in Virtual I/O Server V2.1. An NPIV-capable
Fibre Channel adapter can be used to provide a path for a logical Fibre Channel adapter.
For the client logical partition, this logical adapter functions similar to a physical adapter.
The NPIV configuration simplifies the management of SAN environments.
You will create virtual Fibre Channel adapters using the following slot convention.
Table 13: Virtual Fibre Channel adapters
Virtual Fibre Channel
Student number
server slot#
Student 1
21
Student 2
22
Student 3
23
Student 4
24
Student 5
25
Student 6
26
Student 7
27
Student 8
28
Student 9
29
Student 10
30
Student 11
31
Student 12
32
Virtual Fibre Channel

client slot#
21
22
23
24
25
26
27
28
29
30
31
32

8-3
__ 1. From the HMC GUI, select your Virtual I/O Server and dynamically create a virtual
Fibre Channel server adapter.
__ a. Use the slot number convention specified in Table 13 above. Specify your
assigned client logical partition and the client adapter ID. Here is an example for
student1:
__ b. Save the current configuration of the VIO partition in a new profile called
Normal-NPIV.
Select your VIO server, and run the Configuration > Save Current
Configuration task.
In the window that opens, select the New profile option, and enter Normal-NPIV
as the profile name.
8-4

V7.0.2
EXempty
Click OK to save the new profile.
__ 2. Log in to the Virtual I/O Server and perform a cfgdev to configure the new virtual
device.
__ 3. Use the lsdev command to check for the new virtual Fibre Channel adapter.
$ lsdev -dev vfchost*
name
status
vfchost0
Available
description
Virtual FC Server Adapter
__ 4. Run the lsmap -all -npiv command to check your vfchost adapter slot number
and status.
$ lsmap -all -npiv
Name
Physloc
ClntID ClntName
ClntOS
------------- ---------------------------------- ------ -------------- -----vfchost0
U8233.E8B.1084AER-V1-C21
21
Status:NOT_LOGGED_IN
FC name:
FC loc code:
Ports logged in:0
Flags:1<NOT_MAPPED,NOT_CONNECTED>
VFC client name:
VFC client DRC:
__ 5. In the next steps, you will map the virtual Fibre Channel server adapter to a physical
port on the physical Fibre Channel adapter.
__ a. Run the lsdev command to identify the physical Fibre Channel adapter in the
Virtual I/O Server. Use the fcs0 adapter unless your instructor tells you to use
another one.

8-5

$ lsdev
name
fcs0
fcs1
-dev fcs*
status
Available
Available
description
8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)
8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)
__ b. Run the lsnports command to list the ports that are capable of N_Port ID
virtualization (NPIV). Verify the fabric attribute is set to 1. This means the adapter
and the SAN switch are NPIV ready.
$ lsnports
name
fcs0
physloc
U5877.001.RCH8623-P1-C6-T1
fabric tports aports swwpns awwpns

1
64
64
2048
2036
__ c. Run the vfcmap command to map your virtual Fibre Channel server adapter to
the physical Fibre Channel adapter port fcs0.
Here is an example, using the vfchost0 virtual adapter:
$ vfcmap -vadapter vfchost0 -fcp fcs0
vfchost0 changed
__ 6. Select your client logical partition and dynamically create a virtual Fibre Channel
adapter.
__ a. Use the slot number convention specified in Table 13 above. Specify the Virtual
I/O Server partition and the server adapter ID (slot number). Here is an example
for student1:
__ b. Log in to your assigned client logical partition and run cfgmgr to configure the
virtual Fibre Channel adapter and its associated child devices.
__ c. Use the lsdev command to check for the new client virtual Fibre Channel
adapter. Check for its Available state.
$ lsdev -Cc adapter | grep fcs
fcs0
Available 21-T1 Virtual Fibre Channel Client Adapter
__ d. Use the lscfg command to check the worldwide port name (the network
address) of the virtual Fibre Channel client adapter.
8-6

V7.0.2
EXempty

$ lscfg -vpl fcs0
fcs0
U8233.E8B.1084AER-V21-C21-T1 Virtual Fibre Channel Client Adapter
Network Address.............C05076054585008A
ROS Level and ID............
Device Specific.(Z0)........
Device Specific.(Z8)........C05076054585008A
Hardware Location Code......U8233.E8B.1084AER-V21-C21-T1
PLATFORM SPECIFIC
Name: vfc-client
Node: vfc-client@30000015
Device Type: fcp
Physical Location: U8233.E8B.1084AER-V21-C21-T1
__ 7. From the HMC GUI, look at your logical partition properties. Select the Virtual
Adapters tab.
__ a. Check your virtual Fibre Channel adapter properties and record the WWPN pair
here:
WWPN: ____________________________
WWPN: ____________________________

8-7
For example:
__ 8. Open an ssh connection to your HMC using putty. Use the lshwres command to
check the virtual Fibre Channel adapters on your client logical partition.
Here is an lshwres example on the managed system named sys464:
hscroot@hmc109:~> lshwres -r virtualio --rsubtype fc -m sys464 --level
lpar --filter lpar_names=sys464_lpar1
lpar_name=sys464_lpar1,lpar_id=21,slot_num=21,adapter_type=client,sta
te=1,is_required=0,remote_lpar_id=1,remote_lpar_name=sys464_vios1,rem
ote_slot_num=21,"wwpns=c05076054585008a,c05076054585008b"
__ 9. Save the partition configuration in a new partition profile. Name the profile
Normal-NPIV. In the subsequent steps, you will use a script that will change the
WWPNs and that script will modify the profile with the name Normal-NPIV, so make
sure you name the profile exactly as specified, including capital letters.
8-8

V7.0.2
EXempty
__ 10. In the next step, you will change the worldwide port numbers to a specific network
address. Each time you create a virtual Fibre Channel adapter, a new WWPN pair is
defined. During the class lab setup, external LUNs were created and mapped to
specific predefined worldwide port names. You must change the WWPN pair of your
virtual Fibre Channel adapter to match these predefined values.
__ a. From the HMC CLI, use the lssyscfg command to retrieve the virtual Fibre
Channel adapter's configuration information. Use the following command
(specify your LPAR name and managed system name):
lssyscfg -m <your managed system> -r prof --filter lpar_names=<your
lpar>,profile_names=Normal-NPIV -F virtual_fc_adapters
Here is example output of the lssyscfg command:
"""21/client/1/sys464_vios1/21/c05076054585008a,c05076054585008b/0"""
This attribute value will be changed in the next step.

__ b. On your logical partition, mount the NFS server directory at /mnt, and then
change directory to /mnt/an30/ex8 where the modify.fc.wwpns.sh script is
located.
# mount <NFS_server_IP>:/export/labfiles /mnt
# cd /mnt/an30/ex8
The script modify.fc.wwpns.sh is provided to change the WWPN pair of your
client virtual Fibre Channel adapter. The script establishes an ssh connection to
the HMC and then executes a chsyscfg command to modify the WWPNs pair
values in the Normal-NPIV profile.
Invoke the script modify.fc.wwpns.sh with the following options:
# ./modify.fc.wwpns.sh <HMC name or HMC IP address> <managed system
name> <lpar name> <student number>
The script will prompt you to enter the password for the hscroot user on the
HMC. Then it will modify the WWPNs for the specified LPAR according to
Table 14 below. Each WWPN value is 16 hexadecimal digits long and, to be
unique in our course configuration, will include your managed system number.
Table 14: WWPN pair
Student
WWPN pair
number
student 1
c<system number>000000000001,c<system number>000000000002
student 2
student 3
student 4
student 5
student 6
student 7

8-9
Student
number
student 8
student 9
student 10
student 11
student 12
WWPN pair
The script uses the chsyscfg command to change the WWPN pair. The
following command is used:
# chsyscfg -r prof -m <your managed system> -i name=Normal-NPIV, lpar_name=<your lpar>,
\"virtual_fc_adapters=\"\"<slot_num>/<adapter_type>/[<remote_lpar_id>]/
[<remote_lpar_name>]/<remote_slot_num>/[<wwpns>]//<is_required>\"\"\"
__ c. From the HMC CLI, use the lssyscfg command to retrieve the virtual Fibre
Channel adapters information for your LPAR. Verify the new values match the
information provided in Table 14. Use the following command specifying your
lpar name and managed system name.
lssyscfg -m <your managed system> -r prof --filter lpar_names=<your
lpar>,profile_names=Normal-NPIV -F virtual_fc_adapters
__ 11. Perform a shutdown of your client logical partition. Then activate it using the
Normal-NPIV profile. Wait for the partition to complete the boot sequence before
continuing to the next step.
__ 12. Log in to your logical partition and verify that a new hdisk is available. Use the lsdev
command to check the disk type. The disk type should not be a virtual SCSI disk but
instead it should some type of Fibre Channel disk.
An example is shown below. The exact type of Fibre Channel disk on your
system may be different:
# lsdev -c disk
hdisk0 Available
hdisk1 Available 27-T1-01 MPIO IBM 2145 FC Disk
__ 13. On the Virtual I/O Server, run the lsmap command to display the mapping between
the physical Fibre Channel adapter port and your virtual Fibre Channel adapter. The
status should be LOGGED_IN.

V7.0.2
EXempty

$ lsmap -all -npiv
Name
Physloc
ClntID ClntName
ClntOS
------------- ---------------------------------- ------ -------------- -----vfchost0
U8233.E8B.1084AER-V1-C21
21 sys464_lpar1
AIX
Status:LOGGED_IN
FC name:fcs0
FC loc code:U5877.001.RCH8623-P1-C6-T1
Ports logged in:1
Flags:a<LOGGED_IN,STRIP_MERGE>
VFC client name:fcs0
VFC client DRC:U8233.E8B.1084AER-V21-C21-T1
__ 14. Let your instructor know that you have completed the exercise.
End of exercise

8-11

V7.0.2
EXempty
Exercise 9. Manage service events

(with hints)

This exercise demonstrates management of a serviceable event from
the HMC GUI as well as diagnostic operations and service tools
configuration of the POWER7 processor-based managed system.

Run diagnostics in a partitioned environment to generate an event
Manage connection monitoring for servers
Check the operation of the SFP application
Introduction
In this exercise, you run a diagnostic and check the configuration of
the SFP service tool by running two tests and verifying that the events
are logged.
Requirements
This workbook.
A workstation with a web browser connected to the Internet.
Access to an HMC and a POWER7 processor-based managed
system connected to the same network as your workstation.

9-1

Preface
All exercises of this chapter depend on the availability of specific equipment in your
- A computer system with Internet access and a web browser installed from
which to execute remote commands to the HMC (using SSH).
- A managed system configured with at least one partition.
- All lab systems need to be accessible to each other on a network.
Hints are provided for the exercises in case you need them and to provide solutions for
the exercise steps. All hints are marked by a sign.
Part 1: Service Tools

This first part of this exercise requires you to check the SFP configuration on the HMC.
__ 1. You will need one AIX partition that is running for this exercise. If your managed
system does not have at least one partition running, activate one with its default
partition profile.
__ 2. Log in to your partition. Check that the /var file system is not full on your partition.
Log in to your partition. Use the command df /var to find out the percent used.
# df /var
Filesystem 512-blocks
/dev/hd9var
262144
Free %Used Iused %Iused Mounted on

47360
6%
353
2% /var
If /var is too full, use the following command to increase it by 64 MB:

chfs -a size=+64M /var
__ 3. Make sure the date in your partition is not 90 days off from the date on the HMC. If
the date on the partition and the HMC are more than 90 days out of sync, the
serviceable events will be deleted on the HMC. Change the LPAR date and time if
needed.
Log in to your partition and type the date command.
Log in to the HMC GUI interface, and go to the HMC Management application.
In the Operations section, click Change Date and Time, and check that the
date and time displayed is correct. The time difference between the HMC date
and time and the partition date and time should not be more than 90 days out of
sync.
__ 4. Check that all of the RMC daemons are running on the partition. This operation is
related to the Dynamic Resource Allocation.
9-2

V7.0.2
EXempty
On the partition, run the command: lssrc -a | grep rsct_rm. This command
will list the daemons responsible for HMC and partition communication (among
other functions).
Example output of lssrc command:
# lssrc -a | grep
IBM.CSMAgentRM
IBM.ServiceRM
IBM.DRM
IBM.MgmtDomainRM
IBM.ERRM
IBM.LPRM
IBM.SensorRM
IBM.AuditRM
IBM.HostRM
rsct_rm
rsct_rm
rsct_rm
rsct_rm
rsct_rm
rsct_rm
rsct_rm
rsct_rm
rsct_rm
rsct_rm
2818170
4128906
4522182
6750232
active
active
active
active
inoperative
inoperative
inoperative
inoperative
inoperative
The output shows that the typical RMC daemons are active. Do not worry if your
list is not exactly the same as the one above. Some individual daemons are only
active when they are needed.
Run the command startsrc -g rsct_rm if all the daemons are in an inactive
state.
__ 5. Is the managed system enabled for Connection Monitoring?
From the HMC GUI session, go to the Service Management application. In the
Connectivity task section, choose Manage Connection Monitoring. The
managed system should display Enabled in the State column, as shown in the
example below.

9-3
__ 6. Based on the configuration of your HMC, how many minutes does the connection
have to be disconnected for the event to be considered a network outage?
From the Connection Monitoring Setup window, as shown in the last step's
hint, the number of disconnected minutes considered to be an outage is 15.
__ 7. Test that the HMC is configured to log serviceable events to the SFP. Use the Create
a Serviceable Event procedure from the HMC to perform the test. Later in this
exercise, you will check for the HMC event in SFP (Manage Serviceable Events).
In the Service Management application, choose Create Serviceable Event on
the selected menu.
In the pop-up window, click the Test automatic problem reporting check box.
In the Problem Description field, write a comment containing your student
9-4

V7.0.2
EXempty
number and HMC as shown in the example below. Click Request Service once
you have entered the comment.
In the pop-up window, click OK to exit the HMC problem reporting test.
__ 8. Perform a test for your managed server to make sure that server events will be
logged into HMC SFP.

9-5
In the Systems Management application, click Servers. In the right pane, click
the corresponding check box to select your managed system. In the Task menu,
select Serviceability > Create Serviceable Event.
In the pop-up window, click the Test automatic problem reporting check box,
add a problem description text containing your student number and your server
name, and click Request Service as shown in this example:
9-6

V7.0.2
In the pop-up window, click OK to exit the problem reporting test.
EXempty
__ 9. Perform a test from a partition to make sure that it will log events with SFP. From the
HMC GUI, select your partition and open a terminal window. Log in to your partition
as root and run the following oppanel diagnostic test:
__ a. Run diag at the AIX shell prompt. Press Enter to continue.
__ b. Choose Diagnostic Routines. It should already be highlighted; simply press
Enter.
__ c. Choose System Verification. It should already be highlighted; simply press
Enter.
__ d. Use the cursor keys to scroll down to oppanel, and press Enter to select; then
press F7 to commit.
__ e. When asked if you want to proceed to create a test serviceable event, use the
cursor keys to select Yes, and press Enter. On the next screen, press Enter to
continue.
__ f.
When asked if you want to report this problem to the Service to Service Focal
Point, use the cursor keys to select Yes, and press Enter. This procedure should
log an event from this partition in SFP, but it might take a few minutes. You will
check for this event later in this exercise. After a few minutes, you should see the
System Attention Indicator appear next to your partition name. You do not have
to wait to see this indicator to proceed to the next step.
__ g. Press F10 to exit the diagnostic program.

9-7
Part 2: SFP: Check and close events

Earlier in this exercise, you performed three tests to verify the operation of SFP. The first
was a test from the HMC, the second was a server diagnostic test, and the third was an
operator panel (oppanel) diagnostic test from a partition. In this part, you will check SFP for
these events and close them.
__ 10. From the HMC GUI, go to the Service Management application. Choose Manage
Serviceable Events from the task list on the right part of the screen. You can also
use the Tool icon located at the bottom of the left pane of the HMC GUI to start the
Manage Serviceable Event menu.
This pop-up menu allows you to filter the output so that you can find the events you
need to see. Feel free to explore the options. When you are ready, at the top of the
screen choose to see all open events. Click OK.
__ 11. Several students in the class are using the same HMC, therefore the next screen will
probably list multiple instances of each of the three types of serviceable events
which this exercise has you generate. Look for your new events; use the Number of
days to view criteria and specify one day to verify that your specific events were
logged. The newest events will be at the top of the list. You might need to grow the
window or scroll to the right to see the descriptive text.
Below is an example Serviceable Event Overview screen. The first line is the
oppanel test run in an LPAR (reference code 651-199), the second is the managed
server test (reference code B3031007), and the last is the HMC test (reference code
B3031107). Click on each reference code to see a description of the problem it
represents.
In the example below, you can tell the oppanel test came from the managed system
from the Failing MTMS column and the machine type model number of 8233-E8B,
which is a managed system, with serial number 1084AER. The Reporting name
column is not shown in the example below. You can tell that the HMC test came from
the HMC itself from the machine type model number of 7042-CR5 (with serial
number 1099CBA), which is an HMC.
9-8

V7.0.2
EXempty
Look for your tests on your HMC. If they are not there, troubleshoot the issue that is
causing the event or events not to be logged.
Have you waited at least one or two minutes for the event to be logged?
Are the RMC daemons running on the partition? Remember that in Step 4 you
checked this.
Attempt to dynamically remove a small amount of memory from the partition
where the oppanel test was performed. Did this work? If yes, then the event
should be logged in SFP since both DLPAR and the service tools use the
network connection between the HMC and the partitions and the RMC daemons
for communication.
__ 12. Select a managed service event and choose View Details from the Selected
dropdown menu.

9-9
Select a service event in the table, and choose View Details from the Selected
dropdown menu, as shown in the example below:
__ 13. View the information available for the selected event. Use the scroll bar on the right
of the table to look at the detailed information. In the example below, you can see
the oppanel test run from a partition named sys464_lpar1, and the Reporting
Primary Unit Name is the sys464 managed system.
Click Cancel to return to the Serviceable Events Overview window.

V7.0.2
EXempty
__ 14. You can identify the oppanel event you created based on the Reporting partition
name displayed in the details of the event. For the HMC and managed system test
events, you will have use the scroll bar on the right of the table to scroll down to the
Description field to see the comment that was entered when the test event was
generated, as shown in the example below:
__ 15. Identify the events you generated, then select each one and close them. To do this,
select an event and choose Close Event from the Selected menu. Enter your name
and the comment just a test. Click the Close Events button, and then click Yes.
When you are finished closing your events, click the Cancel button to exit the
Serviceable Events Overview window. Click Cancel again on the remaining
Manage Serviceable Events window.
Note
Typically, customers do not close events unless they are absolutely sure what
caused the problem. In this case, you caused the errors, therefore it is acceptable
for you to close these events now.
End of exercise

9-11

V7.0.2
EXempty
Exercise 10.PowerVM system maintenance

(with hints)

This exercise provides you with an opportunity to perform a couple of
the most popular PowerVM maintenance tasks.

Update the Virtual I/O Server software to a newer fix level
Backup the device configuration of the Virtual I/O Server using the
viosbr command. (The viosbr command includes device
attributes, as well as logical and virtual device mapping
information.)
Use cron to schedule the Virtual I/O Server backup
Introduction
The Virtual I/O Server software continues to change. Some of the
updates fix problems and others add new functionality. The latest
available level of software is always considered the recommended
level. This software can be acquired by anonymous FTP, HTTP (web
browser), and ISO images. This exercise uses files which were
previously downloaded using FTP.
The last part of this exercise demonstrates how cron can be used to
schedule a backup of the Virtual I/O Server.
Requirements
This workbook.
A VIO server partition.
Access to a directory containing a VIO fix pack.
Exercise 10. PowerVM system maintenance

10-1

Preface
All procedures in this exercise depend on the availability of specific equipment in
your classroom.
Part 1: Update the Virtual I/O Server software

At the time of writing, the current fix pack was 26. This was downloaded to an NFS server
assigned to your class. Your instructor might direct you to install a newer fix.
Your system has a combination of availability options including MPIO for disk redundancy
and shared Ethernet adapter failover for the virtual Ethernet. You will update each Virtual
I/O Server; one at a time to avoid impacting your client LPARs.
Note
You need to plan the VIO server updates as a team of two students. Refer to the table
below for your team number. In each team, the student with the odd number ID should
complete part 1 of the exercise first. The student with the even number ID should wait until
the student with the odd number ID indicates they have completed the update of their VIO
server. In this way, the two AIX client partitions will have access to the network and their
VSCSI disks at all times.
Table 15: Team numbers

Managed
Managed System 1
system
Team
number
Student
number
Virtual
I/O
Server
name
Client
LPAR
name
Managed System 2
3
10
11
12
vios1
vios2
vios3
vios4
vios5
vios6
vios7
vios8
vios9
vios10
vios11
vios12
lpar1
lpar2
lpar3
lpar4
lpar5
lpar6
lpar7
lpar8
lpar9
lpar10
lpar11
lpar12
__ 1. Select your Virtual I/O Server and perform the following steps:
__ a. All interim fixes currently applied must be manually removed before applying the
fix pack. Use the emgr command to list and remove the interim fixes (there
should not be any interim fixes on your system).
$ oem_setup_env
# emgr -P

V7.0.2
EXempty
__ b. If the output from the emgr command indicates there are interim fixes applied on
your system, remove each one individually using the following command:
# emgr -r -L <fix label name>
__ c. When all interim fixes have been removed, return to the VIO CLI environment.
# exit
__ d. All uncommitted updates must be committed prior to installing new updates.
Execute the following command:
$ updateios -commit
__ e. The Virtual I/O Server fix pack 26 is available on an NFS server if using
Montpellier remote facilities (Your instructor might direct you to install a newer fix
directly from the IBM Fix Central website, or another NFS location). Execute the
following command to mount the remote directory:
$ mount <NFS_server_IP>:/export/labfiles /mnt
__ f.
With fix pack 26, there is now a method to verify the VIOS update files before
installation. This process requires access to openssl by the padmin user, which
can be accomplished by creating a link. To verify the VIOS update files, follow
the steps below. Replace <fixpath> with the path name of the directory that
contains the fixes you are using. If you are using the Montpellier remote facilities,
the fixpath directory should be an30/ex10
$
#
#
#
$
$
$
oem_setup_env
ln -s /usr/bin/openssl /usr/ios/utils/openssl
ls -al /usr/ios/utils
exit
cp /mnt/<fixpath>/ck_sum.bff /home/padmin
chmod 777 /home/padmin/ck_sum.bff
ck_sum.bff /mnt/<fixpath>
__ g. Execute the following command to install the updated Virtual I/O Server
software:
$ updateios -dev /mnt/an30/ex10 -install -accept
Once the command examines the software contained in the specified directory,
you will have to confirm that the installation should proceed. The software
installation could take 30 minutes or more to complete.
__ h. When the installation has completed, execute the following command to set
authorization for the PAdmin role. Note the space between the - character and
the PAdmin role. You will be prompted to enter the password for the padmin user.
$ swrole - PAdmin
__ i.
Run the following command to accept the new licence agreement:

$ license -accept

10-3
__ j.
Reboot the Virtual I/O Server to implement the changes.

$ shutdown -force -restart
__ k. When the partition has rebooted, log on as padmin and run ioslevel to list the
new software level.
$ ioslevel
If Fix Pack 26 is installed, the command output is 2.2.2.1.
__ 2. If your student ID is an odd number, inform your teammate that you have completed
the update of your VIO partition. Your teammate can now perform the update of their
VIO partition.
Part 2: Using viosbr to backup the virtual and logical configuration

This part of the exercise will use the viosbr command to backup the virtual and logical
configuration of the Virtual I/O Server. This viosbr command backs up all the relevant data
to recover a Virtual I/O Server after a new installation.
__ 3. Use the viosbr command to backup all the device attributes, as well as logical and
virtual device mappings on your Virtual I/O Server to a backup file called
myvios-backup.
Example command:
$ viosbr -backup -file myvios-backup
__ 4. Use the viosbr command to list the available backup files.
Example command and expected output:
$ viosbr -view -list
myvios-backup.tar.gz
Note that the backup file is compressed.
__ 5. Use the viosbr command to display the contents of the backup file.

V7.0.2
EXempty

$ viosbr -view -file myvios-backup.tar.gz
Details in: myvios-backup
===============================================================
Controllers:
============
Name
---iscsi0
pkcs11
pager0
vasi0
vbsd0
fcs0
fcs1
sfwcomm0
sfwcomm1
fscsi0
ent0
fscsi1
ent1
ent2
ent3
sfw0
fcnet0
fcnet1
Phys Loc
--------
U8233.E8B.0681B9R-V7-C32769-L0-L0
U8233.E8B.0681B9R-V7-C32769
U8233.E8B.0681B9R-V7-C32769-L0
U5877.001.9K8D880-P1-C6-T1
U5877.001.9K8D880-P1-C6-T2
U5877.001.9K8D880-P1-C6-T1-W0-L0
U5877.001.9K8D880-P1-C6-T2-W0-L0
U5877.001.9K8D880-P1-C6-T1
U5877.001.9K8D880-P1-C4-T1
U5877.001.9K8D880-P1-C6-T2
U5877.001.9K8D880-P1-C4-T2
U8233.E8B.0681B9R-V7-C11-T1
U8233.E8B.0681B9R-V7-C13-T1
U5877.001.9K8D880-P1-C6-T1
U5877.001.9K8D880-P1-C6-T2
Physical Volumes:
=================
Name
---hdisk0
hdisk1
hdisk2
hdisk3
hdisk4
hdisk5
hdisk6
hdisk7
Phys Loc
-------U5877.001.9K8D880-P1-C6-T1-W500507680140B855-L0
U5877.001.9K8D880-P1-C6-T1-W500507680140B855-L1000000000000
U5877.001.9K8D880-P1-C6-T1-W500507680140B855-L2000000000000
U5877.001.9K8D880-P1-C6-T1-W500507680140B855-L3000000000000
U5877.001.9K8D880-P1-C6-T1-W500507680140B855-L4000000000000
U5877.001.9K8D880-P1-C6-T1-W500507680140B855-L5000000000000
U5877.001.9K8D880-P1-C6-T1-W500507680140B855-L6000000000000
U5877.001.9K8D880-P1-C6-T1-W500507680140B855-L7000000000000
Optical Devices:
================
Tape Devices:
=============
Ethernet Interfaces:
====================
Name
---en0
en1
en2
en3
en4

10-5
IP Address
Auto
------------10.6.140.142
-
Hostname
-------sys474_vios7
Storage Pools:
==============
SP Name
------rootvg
PV Name
------hdisk0
File Backed Storage Pools:

==========================
Optical Repository:
===================
Ether Channel Adapters:
=======================
Shared Ethernet Adapters:
=========================
Name
Physical Adapter
------------------ent4
ent0
Default Adapter
--------------ent2
Virtual Adapters
---------------ent2
Virtual Server Adapters:

========================
SVSA
Phys Loc
----------vhost0
U8233.E8B.0681B9R-V7-C12
VTD
--lpar7_vtd
vhost1
lpar8_vtd
U8233.E8B.0681B9R-V7-C16
Virtual Suspended Adapters:

===========================
Virtual Suspended Devices:
========================
Suspend Device
Phys Loc
--------------------suspended0
LPM Adapters:
=============
LPM Adapter
----------vioslpm0
SVFC Adapters:
==============
Name
---vfchost0
Phys Loc
--------
FC Adapter
---------fcs0
Phys Loc
-------U8233.E8B.0681B9R-V7-C27

V7.0.2
EXempty
VBSD Pools:
===========
VRM(AMS) Pages:
===============
RSCT:
=====
ct_node_id
----------86d2665eee35318c
Cluster:
========
Cluster
-------
State
-----
Virtual Log Repositories:

=========================
Virtual Log Repository
State
-------------------------vlogrepo0
AVAILABLE
Part 3: Using cron to schedule tasks

In this part of the exercise you will use cron to schedule tasks. In the following steps, you
use cron to schedule a backup of the Virtual I/O Server.
__ 6. Use the crontab command to schedule the creation of a mksysb backup of your
Virtual I/O Server into a file called vios_backup located in the /home/padmin
directory at 11am.
Use the crontab -e command to edit the crontab file for the padmin user. Add
the following on one line to the file, and then save the file and quit the editor:
0 11 * * * /usr/ios/cli/ioscli backupios -file ~/vios_backup -mksysb
__ 7. Use the crontab command to view the crontab file of the padmin user.
Use the crontab -l command to view the crontab file for the padmin user. The
output should reflect the entry you created in the previous step.
End of exercise

10-7

V7.0.2
EXempty
Exercise 11.(Optional) File-backed virtual disk and

virtual media repository configuration
(with hints)

This exercise covers the configuration of VSCSI devices.

Configure a partition to use a VSCSI disk hosted by the Virtual I/O
Server
Configure a partition to use the optical media drive configured as a
VSCSI device and hosted by the Virtual I/O Server
Optionally, test a system backup/restoration using the virtual DVD
Introduction
In this exercise, you will configure the Virtual I/O Server to host VSCSI
devices for AIX partitions. This includes configuring storage resources
and virtual target devices to provide clients with access to file-backed
disks and file-backed optical devices.
Requirements
This workbook.
A workstation with a web browser connected to a network.
Exercise 11. (Optional) File-backed virtual disk and virtual media

11-1

Preface
- A managed system configured with one VIO server (Version 1.5.2 or later)
and one client LPAR (AIX 7.1) per student.
- A system from which to execute remote commands to the HMC (by way of
SSH): All lab systems need to be accessible to each other on a network.
- One available disk of 8 GB size attached to the VIO server for creating a
storage pool.
Introduction
The goal of this exercise is to create a VSCSI disk backed by a file, create a virtual media
repository, and back up your client LPAR operating system to a blank virtual DVD-RAM. At
the end of the exercise, you will restore your client LPAR backup from the virtual
DVD-RAM.
This exercise is presented in three parts:
Part 1: Create a file-backed virtual disk.
Part 2: Create a virtual media repository and a blank virtual DVD-RAM.
Part 3: Backup/restore your client LPAR OS to the virtual optical media device.
Part 1: Create a file-backed virtual disk

__ 1. Open a virtual terminal or a Telnet session to your assigned VIO server. In the
Virtual I/O Server CLI, list all of the disks. Use the lspv command to also see where
rootvg resides.

V7.0.2
EXempty
Here is an example command and its output that shows rootvg on hdisk0. The
disks on your lab system might or might not have PVIDs associated with all of
the disks.
$ lspv
NAME
hdisk0
hdisk1
hdisk2
hdisk3
hdisk4
hdisk5
hdisk6
hdisk7
PVID
00f784aee0fd700a
00f784ae17ad9d8b
00f784ae1822ad34
none
none
none
none
none
VG
rootvg
None
None
None
None
None
None
None
STATUS
active
__ 2. For performing this exercise, you must use a non-shared hdisk device of 8 GB in
size. In your configuration the VIO server should have one non-shared LUN that is
8 GB in size. You can determine which disk is 8 GB in size by issuing the following
command sequence:
$
>
>
>
>
lspv | while read a b

do
echo "$a \c"
echo bootinfo -s $a | oem_setup_env
done
The output should show there is one disk with a size of 8192.
Record the hdisk number here: _______________________________
Note
For the rest of the exercise, we will assume that hdisk7 is the 8 GB hdisk.
__ 3. Use the mksp command to create a new logical volume storage pool. Only include
hdisk7 in this storage pool. Call the storage pool datasp.
Example command to create a new logical volume storage pool:
$ mksp -f datasp hdisk7
__ 4. View the output of lspv to verify that hdisk7 is in the datasp volume group (storage
pool). Also, run the lssp command to verify the datasp storage pool (LVPOOL).

11-3
Example commands and their outputs:

$ lspv
NAME
hdisk0
hdisk1
hdisk2
hdisk3
hdisk4
hdisk5
hdisk6
hdisk7
$ lssp
Pool
rootvg
datasp
PVID
00f784aee0fd700a
00f784ae17ad9d8b
00f784ae1822ad34
none
none
none
none
00f015b31d5ea7f3
Size(mb)
30656
8120
VG
rootvg
None
None
None
None
None
None
datasp
Free(mb) Alloc Size(mb)

23808
64
8120
8
STATUS
active
active
BDs Type
0 LVPOOL
0 LVPOOL
__ 5. Create the file-backed disk storage pool inside the datasp storage pool. Name it
fbpool and make it 1 GB in size.
$ mksp -fb fbpool -sp datasp -size 1G
fbpool
File system created successfully.
1040148 kilobytes total disk space.
New File System size is 2097152
__ 6. Now create a file-backed virtual disk device called fb_disk1 in the fbpool storage
pool. Make the disk 500 MB in size and associate it with the VSCSI server adapter
defined on your VIO server. If you have been following the instructions in the
previous exercise, this should be vhost0. When you run the command to create the
disk device, note the new virtual target device name.
The new virtual target device name for the FB disk device is:
_________________________________________________________________
Example command and its output. In the example below, you can note that the
new VTD name is vtscsi0.
$ mkbdsp -sp fbpool 500m -bd fb_disk1 -vadapter vhost0
Creating file "fb_disk1" in storage pool "fbpool".
Assigning file "fb_disk1" as a backing device.
vtscsi0 Available
fb_disk1
__ 7. View the lsmap output for your vhost0 adapter to verify the configuration. You should
notice the new virtual target device and its associated backing device.

V7.0.2
EXempty
Here is an example command and its output:

SVSA
Physloc
Client Partition ID
--------------- -------------------------------------------- -----------------vhost0
U8233.E8B.1084AER-V1-C12
0x00000015
VTD
Status
LUN
Backing device
Physloc
lpar1_vtd
Available
0x8100000000000000
hdisk1
U5877.001.RCH8623-P1-C6-T1-W500507680140B855-L1000000000000
VTD
Status
LUN
Backing device
Physloc
vtscsi0
Available
0x8200000000000000
/var/vio/storagepools/fbpool/fb_disk1
U5877.001.RCH8623-P1-C6-T1-W500507680140B855-L1000000000000
__ 8. View the lsdev -virtual output and see the description for the your new virtual
target device.
Here is an example command and its output. Note the description for the new
vtscsi device.
$ lsdev -virtual | grep vtscsi0
vtscsi0
Available
Virtual Target Device - File-backed Disk
__ 9. Log in to your client LPAR and run the lsdev -c disk -S a command; then run
cfgmgr, and then run lsdev -c disk -S a again. You should see the new disk
device.
# lsdev -c disk -S a
hdisk0 Available
# cfgmgr
# lsdev -c disk -S a
hdisk0 Available
hdisk1 Available

__ 10. Now you have a new virtual disk. Let us look at some commands to view information
about that disk. Let us first make a new volume group with this disk in it.
Make a volume group named newvg on your AIX LPAR using the new disk. The new
disk is probably called hdisk1. Here is the mkvg command and its output. Also, use
the lspv or lsvg command to verify that the new volume group was created.

11-5

# mkvg -y newvg hdisk1
0516-1254 mkvg: Changing the PVID in the ODM.
newvg
# lspv
hdisk0
00f784ae17ad9d8b
hdisk1
00f784ae1d67cfa0
hdisk2
none
# lsvg
rootvg
newvg
rootvg
newvg
None
active
active
__ 11. Optional step: Use SMIT to create a 100 MB file system in the newvg volume group
with the mount point /newfiles. Mount the file system, and verify that you can
access it.
You have just successfully added a file-backed virtual disk to your AIX LPAR.
To create a file system, use the smitty storage command.
Choose File Systems from the menu.
Choose Add / Change / Show / Delete File Systems from the menu.
Choose Enhanced Journaled File Systems from the menu.
Choose Add an Enhanced Journaled File System from the menu.
You will need to choose the correct volume group. Highlight newvg, and press
Enter.
In the input screen, change the unit size to Megabytes. (You can press the Tab
key to change it.)
Use the arrow to move down once, and then, for number of units, enter 100.
Move the arrow down once, and enter a mount point name of /newfiles.
Press Enter to create your new file system, then exit the SMIT tool.
Type mount /newfiles to mount the file system. Run the mount command to
view your new file system.

V7.0.2
EXempty
Part 2: Create a virtual media repository and a blank virtual DVD-RAM

In this part of the exercise, you will create a virtual media repository in your datasp storage
pool (volume group) that you created in part one of this exercise.
__ 12. At your VIOS partition's CLI, use the lssp command to view all of your storage
pools. You should have two logical volume pools named rootvg and datasp and one
file-backed pool named fbpool.
$ lssp
Pool
rootvg
datasp
fbpool
Size(mb)
30656
8120
1016
Free(mb) Alloc Size(mb)

23808
64
7096
8
515
8
BDs
0
0
2
Type
LVPOOL
LVPOOL
FBPOOL
__ 13. Create a 6 GB virtual media repository with the mkrep command. Create it in the
datasp logical volume storage pool that you created previously in this exercise.
$ mkrep -sp datasp -size 6G
Virtual Media Repository Created
Repository created within "VMLibrary_LV" logical volume
__ 14. List the details of the media repository, and check its size.
$ lsrep
Size(mb) Free(mb) Parent Pool
6118
6118 datasp
Parent Size
8120
Parent Free
952
__ 15. Create a 5 GB blank virtual optical media disk in the repository. Create it with the
name aixopt1. It will be read-write by default (this command takes about one minute
to complete).
Example mkvopt command to create the 5 GB size virtual optical media disk.
$ mkvopt -name aixopt1 -size 5G
__ 16. View the repository again, and verify that the virtual optical media disk was created.
$ lsrep
6118
998 datasp
Parent Size
8120
Name
aixopt1
File Size Optical

5120 None
Parent Free
952
Access
rw

11-7
__ 17. Now the VIOS partition has a virtual media repository and one virtual blank
DVD-RAM. The next few steps will have you make the virtual optical device
available to a partition. Create a file-backed virtual optical device, and associate it
with the vhost adapter already serving the backing devices to your assigned client
LPAR. It should be vhost0.
Example command and its output (where the vhost name is vhost0):
$ mkvdev -fbo -vadapter vhost0
vtopt0 Available
__ 18. Load your aixopt1 media disk in the new virtual optical device.
Example command:
$ loadopt -vtd vtopt0 -disk aixopt1
__ 19. Now view the repository, and see what is different in the output from the last lsrep
command that you ran in Step 16.
Here is an example command and its output. Notice that the Optical column now
lists the virtual target device name of the virtual optical device.
$ lsrep
6118
998 datasp
Parent Size
8120
Name
aixopt1
File Size Optical

5120 vtopt0
Parent Free
952
Access
rw
__ 20. Log in to your client LPAR and run the lsdev -Cs vscsi command; then run
cfgmgr, and then run lsdev -Cs vscsi again. You should see the new VSCSI
optical device served by the VIO server.
# lsdev -Cs vscsi
hdisk0 Available
hdisk1 Available
# cfgmgr
# lsdev -Cs vscsi
cd0
Available
hdisk0 Available
hdisk1 Available

Virtual SCSI Optical Served by VIO Server

Part 3: Backup/restore your client LPAR OS to the virtual optical media

device
Now you have a virtual optical media drive loaded with a blank virtual DVD-RAM and ready
to be used by your client LPAR. You will back up your client LPAR operating system onto
this blank DVD-RAM.

V7.0.2
EXempty
__ 21. Log in to your client LPAR and run the smitty sysbackup command to create a
system backup image (mksysb) in UDF format to your virtual DVD-RAM from the
system rootvg.
From the smitty sysbackup fast path, select Backup up this system to DVD.
Select 2 no to the question Use an existing mksysb image?
Select 2 UDF (Universal Disk Format) to the question DVD backup media
format?
In the SMIT panel that is displayed (example shown below) enter /dev/cd0 in
the DVD-RAM Device field, then press Enter to execute the operation.
Back Up This System to UDF DVD
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
DVD-RAM Device
[]
mksysb creation options:

Create map files?
Exclude files?
Disable software packing of backup?
Backup extended attributes?
File system to store mksysb image
(If blank, the file system
will be created for you.)
no
no
no
yes
+
+
+
+
[]
If file systems are being created:

Volume Group for created file systems
[rootvg]
Advanced Customization Options:

Do you want the DVD to be bootable?
Install bundle file
File with list of packages to copy to DVD
Location of packages to copy to DVD
Customization script
User supplied bosinst.data file
Debug output?
User supplied image.data file
Back up encrypted files?
Back up DMAPI filesystem files?
yes
[]
[]
[]
[]
[]
no
[]
yes
yes
+
/
/
+/
/
/
+
/
+
+
When you create a system backup using the smitty sysbackup menu, the mkcd
command is invoked and creates a temporary file system to store the mksysb file
before copying it to the DVD. If you get an error message stating that there are
not enough free partitions to satisfy the allocation request, you need to free some
disk space in the rootvg volume group and restart the backup.

11-9
Example output from a successful backup is shown below:

Initializing mkcd log: /var/adm/ras/mkcd.log...
Verifying command parameters...
Creating image.data file...
Creating temporary file system: /mkcd/mksysb_image...
Creating mksysb image...
Creating list of files to back up.
..
Backing up 103584 files............
103584 of 103584 files (100%)
0512-038 mksysb: Backup Completed Successfully.
Populating the CD or DVD file system...
Copying backup to the CD or DVD file system...
....
Building chrp boot image...
Removing temporary file system: /mkcd/mksysb_image...
__ 22. You now have a virtual DVD-RAM media that contains a bootable mksysb. This
DVD-RAM can be used to restore the client LPAR in case of recovery. The next step
is to restore this bootable media image to your client LPAR.
__ a. Shut down your assigned client LPAR.
Issue a shutdown command:
$ shutdown -F
__ b. Wait until the partition has a state of Not Activated, then activate your partition
selecting the SMS boot mode. Open the virtual console terminal window and
interact with the menu.
__ c. In the main menu, select the option 5 Select Boot Options, and then option 1
Select Install/Boot Device. Select option 3 CD/DVD Device Type and then
option 1 SCSI Media Type. Select the media adapter. If there is a choice, select
the media adapter in virtual slot 12. You should then see something like this:
---------------------------------------------------------------Select Device
Device Current Device
Number Position Name
1.
SCSI CD-ROM
( loc=U8233.E8B.1084AER-V21-C12-T1-L8300000000000000 )
Select device 1 SCSI CD-ROM, and select task 2 Normal Mode Boot. Select 1
Yes to confirm that you want to exit System Management Services and start
the boot sequence.

V7.0.2
EXempty
__ d. Type 1 and press Enter to select the system console if prompted.

__ e. Type 1 and press Enter to select the language.
__ f.
Your terminal screen should now display the Installation and Maintenance
menu. Type 2 and press Enter to select Change/Show Installation Settings
and Install.
__ g. Press 1 and select hdisk0 as the disk where you want to install. The hdisk0
should be a 10 GB size disk. Accept by pressing 0 to continue with choices
indicated above.
__ h. Start the installation by selecting 0 to continue with the choices. Depending on
your mksysb size, the install might take as little as five to 10 minutes. When the
client partition is booted, log in using root.
__ 23. That is the end of this exercise. Notify your instructor that you are finished.
End of exercise

11-11

V8.0
backpg
Back page

AN304XSTUDHINT

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

AN304XSTUDHINT

Încărcat de

Drepturi de autor:

Formate disponibile

V8.

Power Systems for AIX Virtualization I: Implementing

Student Exercises with hints

March 2013 edition

Copyright International Business Machines Corporation 2009, 2013.

Copyright IBM Corp. 2009, 2013

Student Exercises with hints

Copyright IBM Corp. 2009, 2013

Copyright IBM Corp. 2009, 2013

Student Exercises with hints

Copyright IBM Corp. 2009, 2013

Copyright IBM Corp. 2009, 2013

Course materials may not be reproduced in whole or in part

Student Exercises with hints

Copyright IBM Corp. 2009, 2013

Exercise 1. Power Systems documentation

What this exercise is about

What you should be able to do

Copyright IBM Corp. 2009, 2013

Exercise 1. Power Systems documentation overview

Course materials may not be reproduced in whole or in part

Student Exercises with hints

Exercise instructions with hints

Access IBM Systems hardware and AIX documentation

Hardware information and support

Copyright IBM Corp. 2009, 2013

__ 4. Go to the AIX Information Center. Use the following URL:

Copyright IBM Corp. 2009, 2013

Exercise 1. Power Systems documentation overview

Course materials may not be reproduced in whole or in part

Student Exercises with hints

Copyright IBM Corp. 2009, 2013

Exercise 2. Processor virtualization configuration

What this exercise is about

What you should be able to do

Copyright IBM Corp. 2009, 2013

Exercise 2. Processor virtualization configuration

Course materials may not be reproduced in whole or in part

Student Exercises with hints

Exercise instructions with hints

View system configuration and configure processor options

Copyright IBM Corp. 2009, 2013

Copyright IBM Corp. 2009, 2013

Exercise 2. Processor virtualization configuration

Course materials may not be reproduced in whole or in part

Student Exercises with hints

__ 5. Activate your partition with the newly modified Normal profile.

Copyright IBM Corp. 2009, 2013

Copyright IBM Corp. 2009, 2013

Exercise 2. Processor virtualization configuration

Course materials may not be reproduced in whole or in part

Student Exercises with hints

Example lparstat -i output:

Copyright IBM Corp. 2009, 2013

Copyright IBM Corp. 2009, 2013

Exercise 2. Processor virtualization configuration

Course materials may not be reproduced in whole or in part

Student Exercises with hints

Copyright IBM Corp. 2009, 2013

Copyright IBM Corp. 2009, 2013

Exercise 2. Processor virtualization configuration

Course materials may not be reproduced in whole or in part

Student Exercises with hints

Overviewing shared processor utilization