Professional Documents
Culture Documents
An30g6 LSG
An30g6 LSG
cover
Front cover
Lab Setup Guide
Power Systems for AIX - PowerVM I:
Implementing Virtualization
Course code AN30G ERC 6.0
October 2016 edition
Notices
This information was developed for products and services offered in the US.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative
for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not
intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or
service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate
and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this
document does not grant you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
United States of America
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer
of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein;
these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s)
and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an
endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those
websites is at your own risk.
IBM may use or distribute any of the information you provide in any way it believes appropriate without incurring any obligation to you.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other
publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other
claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those
products.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible,
the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to
actual people or business enterprises is entirely coincidental.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many
jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM
trademarks is available on the web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml.
© Copyright International Business Machines Corporation 2009, 2016.
This document may not be reproduced in whole or in part without the prior written permission of IBM.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
V11.0
Contents
TOC
Contents
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Lab configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Network requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Skills required to set up the lab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Setup instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Configuration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Hardware setup instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
POWER8 processor-based servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Check HMC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Verification procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Testing the lab exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Performance notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Remote labs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Remote lab setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Virtual machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Instructor and student system checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Host or server systems checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Passwords and IDs checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
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™ AIX 5L™ AIX 6™
AIX® DS4000® DS6000™
DS8000® Electronic Service Agent™ Enterprise Storage Server®
Express® HACMP™ Initiate®
i5/OS™ Micro-Partitioning® Notes®
OS/400® Passport Advantage® POWER Hypervisor™
Power Systems™ Power® PowerHA®
PowerPC® PowerVM® POWER6®
POWER7+™ POWER7® POWER8®
Redbooks® Redpapers™ SystemMirror®
Tivoli® 400®
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Windows is a trademark of Microsoft Corporation in the United States, other countries, or both.
Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of
Oracle and/or its affiliates.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other product and service names might be trademarks of IBM or other companies.
LSG
Overview
The purpose of this lab setup guide is to assist the classroom preparer in setting up the AN30G
classroom lab environment.
If you intend to use IBM remote labs instead of manually setting up an environment, do not use this
guide. Instead, refer to the Training Partner Operations Guide for directions to the IBM Remote Lab
Platform (IRLP).
If you intend to manually set up an environment, use this guide. It is separated into the following
parts:
• "Requirements" on page 2
• "Setup instructions" on page 7
• "Software setup instructions" on page 9
• "Verification procedures" on page 16
• "Remote labs" on page 19
• "Appendix" on page 21
Important
The classroom must be ready to run lab exercises before the first day of class. You might want to
create a virtualized environment that you can maintain and reuse. Test the entire setup thoroughly
to avoid problems during class time. If you experience problems and need assistance, contact the
IBM Help Desk:
Toll-Free: 1-888-502-5511
International: 1-404-238-6000
Email: [email protected]
LSG
Requirements
The following section provides information about how to manually create the lab environment that is
needed to conduct the lab exercises in this course. As the classroom provider, you are responsible
for providing the following configuration for this class. The instructor requires one configuration, and
each student in the class requires a separate configuration. Depending on the course
requirements, instructor and student configurations might be identical.
The total number of systems that are required for a class is the number of instructor systems plus
the number of students and multiplied by the number of student systems that are required for each
student.
1+1 2 Example
For instance, if the instructor requires three systems and each of 12 students requires two systems
each, you make the following calculation:
3 instructor systems + (12 students x 2 systems each) = 27 systems for the class
Hardware requirements
Table 1 lists the hardware needed to prepare one student lab set. When preparing for a class,
multiply the items below by the number of lab sets needed for the class.
The machines listed below represent the minimum needed to perform the exercises in the AN30G
course.
The students need to access an HMC connected to a POWER7 processor-based server to perform
most of the exercises. Only the Power Systems documentation overview exercise does not require
HMC or IBM Power System access. The student access can be accomplished with remote
connections from workstations over a network.
The instructor only needs a way to project the overheads. This might be a PC with a projector.
The host server is an IBM Power 750 (called the managed server). In addition, an AIX 7 NIM server
is also needed to be accessible over a network to install the Virtual I/O Servers operating system
and the client partitions AIX operating system.
LSG
Table 2 provides configuration information for the lab setup. The checklist that is provided in
"Appendix" on page 21 can also help you to set up the lab.
Table 2. Configuration for each system
Machine type Display
System label RAM Hard disk Operating system
and processor resolution
<2.5 GHz or
INSTR_WS <4 GB> <120 GB> <1280 x 800> <Windows 7 or later>
faster Duo Core>
<2.5 GHz or
STUD_WS <4 GB> <120 GB> <1280 x 800> <Windows 7 or later>
faster Duo Core>
LSG
Network requirements
The main networking requirement is that the lab systems (HMC, VIOS, client LPARs, NIM server)
be accessible from the student workstation. The student workstation is commonly a web accessible
portal (such as Citrix) which then provides the needed web browser and PuTTY client. If not using a
portal, then the students need connectivity from their physical workstations (if the lab environment
is within a VPN, then this might require special software such as OpenVPN for the student to have
access). How this connection is provided is up to the provisioning organization. The provisioning
organization is responsible to communicating the connection requirements to the instructor or
course coordinator.
Within the class lab environment all of the platforms (HMC, VIOS, client LPARs, NIM server) must
have connectivity to each other.
Table 3. Required network configurations
Network configuration Classroom requirement
Specify isolated networks or a single network. Single
Specify whether Internet access is required. Required for student workstations
Specify whether a DHCP server is required. Not necessary
Specify whether fixed IP addresses should be assigned. Required
Specify whether promiscuous mode is required. Not necessary
Software requirements
Table 4 lists the software needed to prepare the student and instructor lab sets. When preparing for
a class, be sure you have the correct number of licensed copies of any non-IBM software.
Table 4. Software for one student lab set
Platform use Operating system OS version Applications Notes
Supported web browsers:
Web browser
Firefox 31 or 38 ESR or
Student Windows, Linux, or and ssh tool
later. Chrome 43 or 46.
workstation AIX. (such as
Java Runtime Environment
PuTTY)
(JRE) Version 8 or later.
Latest release and
TL for serving the
NIM Server AIX 7.2
AIX and VIOS
mksysb images
Minimum of Version
Standard HMC 8 Release 8.4.0
The following interim fixes
compatible with Service Pack 1,
are required: MH01639
POWER8 with all latest fixes
applied.
Note
As of August 2016, the initial install of a VIOS partition by students should use an mksysb image of
version 2.2.4.10. Note that this VIOS level should also be used with POWER8 system firmware
level SV840_104 (FW840.20) or newer on POWER8 S822 hardware. Minimum firmware levels for
certain Ethernet adapters should also be used with this system firmware level.
• The 4-port 1 Gb Ethernet adapter (FC 5260/5899) requires minimum firmware level 10240180.
• The 2-port 10 GbE Base-T adapter (FC EN0X/EN0W) requires minimum firmware level
20110140.
• Refer to the IBM Fix Central website to check for any newer requirements for these or other
adapters.
A later VIOS level can be used for installation by students, as long as it is not the most recent one.
The mksysb image must include a VIOS fixpack which students will install as part of an exercise.
The exercises for this class were tested and verified as working correctly by using the following
configuration:
• IBM S822 with system firmware FW840.113 (FW840.22)
LSG
Setup instructions
Configuration information
The following describes the configurations of the student and lab set systems.
LSG
Check HMC configuration
HMC setup must be done according to the following:
__ 1. Log in to the HMC CLI as hscroot. The password is probably either abc123 or abc1234. If
the password has been changed during a previous class, you might be required to reload
the HMC code. Check the HMC code version by using the lshmc -V command. The
minimum level required is V8R8.4.0 with Service Pack 1 and additional patches, as detailed
below:
hscroot@hmc56:~> lshmc -V
"version= Version: 8
Release: 8.1.0
Service Pack: 1
"
__ 2. Delete all other HMC users than the default users (hscroot ... hscpe.). Some HMC users
can exist from a previous class session.
__ 3. Create one HMC user ID for each student in the class. The user ID should use the
hmcsuperadmin Task Role, and the AllSystemResources Resource Role.
__ 4. Configure the HMC to allow remote connection and command execution.
LSG
HMC
__ 1. Log in to the HMC GUI as hscroot using the Enhanced+ login option. The password is
probably either abc123 or abc1234.
__ 2. Select All Systems from the Task Bar, then double-click the server that will be set up for the
course. In the Menu Pod, open PowerVM submenu.
__ 3. Select the Virtual Networks item.
__ 4. If there are any virtual networks listed in the table, delete them by right-clicking the network
name, then selecting the Remove virtual network option.
__ 5. Switch all SR-IOV capable Ethernet adapter to Shared mode. Open the Hardware
Virtualized I/O page. Select the SR-IOV adapter from the combo box, then click Modify
SR-IOV Adapter. Select the Shared checkbox in the Mode Section. Click OK to apply the
settings.
__ 6. Log in to the HMC as hscroot using the Classic login option. The password is probably
either abc123 or abc1234.
__ 7. Click the Server Management application. If the right panel on the Server Management
application is blank, perform the following steps.
__ a. Choose Add Managed System from the Server Management.
__ b. If you know the IP address of the Server Processor, choose Add a Managed System,
enter the IP address and password.
__ c. If you do not know the IP address of the Server Processor, choose Find Managed
Systems, and enter 192.168.255.0 for the beginning IP address and
192.168.255.255 for the ending IP address. This find operation will take few minutes
and should find all the managed systems connected to your network. This is assuming
that no one has changed the IP address on the service processors.
__ 8. Configure four logical partitions on each POWER8 managed system.
- Each LPAR is a dedicated type LPAR. Each LPAR has one dedicated Fibre Channel
adapter for disk attachment and a physical Ethernet adapter as network interface card.
__ 9. Create the partitions, go to the Server Management application on the HMC, select the
managed system name, and choose Create > Logical Partition on the menu. Use the
partition name, partition ID, and default profile name listed in the following table:
LSG
Student
System Name LPAR name LPAR ID Profile name
number:
student 1 partition1 1 Normal
student 2 partition2 2 Normal
student 3 partition3 3 Normal
student 4 partition4 4 Normal
The LPAR names, can be prefixed with the system name and a class number, such as
sys8691_partition1 instead of partition1 (sys869 being the managed system name, and 1
being the class number). This is necessary if multiple classes are to be supported at the
same time to avoid confusion.
Make sure that the Sync Current configuration Capability for each partition is marked as
Sync turned OFF. This should be the default value. If using a script to create the LPARs, the
lssyscfg command shows this attribute of the partition as sync_curr_profile, and the
default value is 0 (off).
__ 10. For each partition profile, use the following Processor and Memory settings. Logical
partitions use Dedicated processors.
__ a. Add one Fibre Channel adapter and one physical Ethernet adapter to the partition
profile. The adapters should be marked as Required.
__ b. No virtual adapters are required for the setup of the class.
__ 11. Define an IP range and IP addresses for the partitions. It is strongly suggested that the
partition name be the same as the partition hostname. Whatever design is chosen, notify
the instructor of the naming scheme.
External Storage
The SAN Storage System has to be configured to provide LUNs for the managed systems. Each
student must have access to three non-shared LUNs and one shared LUN. The shared LUNs must
be accessible to both virtual I/O servers in the student's team for setting up MPIO on the client
partition. Additionally, for the NPIV exercise, one 8 GB LUN per student has to be mapped to the
virtual WWPNs generated by the modify.fc.wwpns.sh script.
LSG
Note
Configure SAN storage for shared and non-shared disks such that the 30 GB non-shared disk
appears first in the LPAR configuration (as hdisk0). The two 8 GB non-shared LUNs should be
observed as hdisk1 and hdisk2. The two 10 GB shared LUNs should appear as hdisk3 and hdisk4.
Note
The differences in LUN sizes are important. Students will have to use different LUN size depending
on the exercise. For example non-shared LUN of 30 GB size is needed for installing the VIO Server
code. A shared LUN of 10 GB size will be use as a virtual SCSI disk for configuring a client logical
partition with MPIO storage, and a non-shared LUN of 8 GB size will be used for creating the virtual
media repository. The simplest way for the students to make a LUN selection during the exercises
is to have different LUN sizes for each purpose, specifically when performing an AIX or VIOS code
installation.
Note
When configuring a system for a class of up to four students, the 10 GB shared LUNs will be zoned
to be visible only on the two FC adapters in a lab set of two partitions. The standard S822 system
will have two lab sets.
The diagram below shows the required SAN LUN setup for one lab set of this course. A standard
IRLP S822 system has two lab sets (four AIX partitions).
LSG __ 12. Non-shared LUN creation: For each managed system, create four non-shared LUNs of 30
GB size and eight non-shared LUNs of 8 GB size. These LUNs must not be shared between
LPARs. Assign one LUN of 30 GB size and two LUNs of 8 GB size per Fibre Channel
Adapter WWPN. When you create the LPAR used to set up the class, you will assign one
Fibre Channel adapter to its profile.
__ 13. Shared LUNs creation: Create and zone two shared LUNs of 10 GB size per lab set.
These LUNs must be shared LUNs, and zoned only for the two Fibre Channel adapters in a
single lab set.
__ 14. Virtual WWPN (Non-shared) LUNs creation: Create four LUNs of 8 GB size each per
managed system. Then use the worldwide port names naming convention shown below to
perform the LUN mapping. These WWPN pairs will be used by the students when
configuring virtual Fibre Channel adapters. Those predefined WWPNs have 16 digits and
must contain the managed system number and the class number as the first four digits after
the initial ‘c’.
__ 15. Virtual WWPN (Non-shared) LUNs creation: Create four LUNs of 8 GB size each per
managed system. Then use the worldwide port names naming convention shown below to
perform the LUN mapping. These WWPN pairs will be used by the students when
configuring virtual Fibre Channel adapters. Those predefined WWPNs have 16 digits and
must contain the managed system number and the class number as the first four digits after
the initial ‘c’.
LSG
Table 7. WWPN pair
Student WWPN pair
number
student 1 c<3 digit system number><one digit class number>00000000001,
c<3 digit system number><one digit class number>00000000002
student 2 c<3 digit system number><one digit class number>00000000003,
c<3 digit system number><one digit class number>00000000004
student 3 c<3 digit system number><one digit class number>00000000005,
c<3 digit system number><one digit class number>00000000006
student 4 c<3 digit system number><one digit class number>00000000007,
c<3 digit system number><one digit class number>00000000008
Note
When configuring multiple managed systems for a class of more than four students, each managed
system will use a set of virtual WWPNs where the last digit ranges from 1 to 8.
LSG
NIM environment requirements
During the exercise, the students will install a Virtual I/O Server and an AIX client logical LPAR. A
pre-existing NIM master is required to provide mksysb images for installing the Virtual I/O Servers
and the client logical LPARs. Use the following information in addition to the normal software
installation procedures to set up additional NIM mksysb resources.
__ 1. mksysb resources must be available for installing the Virtual I/O Servers version 2.2.4.10
and the client AIX LPARs with AIX 7.2 TL0 SP1 or newer.
__ 2. The AIX mksysb image should be customized by extracting the contents of the
an30erc6.tar class tar file into /home/an30.
__ 3. The VIOS mksysb image should be customized by inclusion of the files for a fixpack in a
directory under /home/padmin.
__ 4. The is no manual intervention possible when performing the Virtual I/O Server installation,
so include an appropriate bosinst_data NIM resource in the resource group used to install
VIOS partitions. The bosinst_data resource file should indicate PROMPT=no,
RECOVER_DEVICES=no, and have blank values for all the fields of the target_disk stanza.
__ 5. The lab instructions expect students to interact with the AIX installation menus when
performing the AIX client partition installation, so include an appropriate bosinst_data NIM
resource in the resource group used to install AIX partitions. The bosinst_data resource
file should indicate PROMPT=yes, RECOVER_DEVICES=no, and have blank values for all
the fields of the target_disk stanza.
__ 6. The lab instructions expect hdisk0 inside the AIX client partition to have the hcheck_interval
attribute for hdisk0 at the default value of 0. Do not change this value by using a NIM
customization script.
__ 7. The lab instructions expect students to change the reserve_policy attribute of shared LUNs
from the default value of single_path to a value of no_reserve. Do not change this default
value by using a NIM customization script or using by deploying default IBM rules.
__ 8. The NIM environment needs to have NIM client objects using the naming convention used
in this course. The following logical partition naming convention is used in the exercises.
Each partition name should be prefixed with the manage system name and class number,
for example sys8981_vios1. In case of different naming, inform the instructors. Be sure to
have these NIM objects defined in the NIM master.
- Virtual I/O Servers names: vios1, vios2, vios3, vios4
- Client LPARs names: lpar1, lpar2, lpar3, lpar4
LSG
Important
Enable the bos_inst operation for all of the clients (VIO servers and client LPARs). This way the
students will not have to directly access the NIM master. The students are not being directed to
enable the bos_inst for the installation of this image. It is imperative that IT Support does this and
provide the instructor with the IPs which should be referenced to install these clients! Allocate
bosinst_data resources that require prompted installs for the VIO and AIX client LPARs. The
exercise instructions expect that students will interact with the operating system install menus.
LSG
Verification procedures
Use the following information to verify the LPAR installation and configuration.
__ 1. Verify that the installed AIX mksysb image contains the file
/home/an30/modify.fc.wwpns.sh that was extracted from the AN30G class tar file.
__ 2. Telnet or ssh to each partition and successfully ping the HMC with both the IP address and
the hostname. Use the HMC Management > HMC Configuration > Test Network
Connectivity application on the HMC Classic UI to ping each of the partitions from the
HMC.
__ 3. Test if the dynamic LPAR function works. Dynamically add 256 MB of memory to each
partition. Remove it to get the original desired memory capacity of the LPAR.
Check on each LPAR the available hdisks devices. You should see five hdisk devices
(external LUNs). The LPAR's rootvg should be installed on hdisk0, and it should be 30 GB in
size. Of the remaining disks, two should be 8 GB in size, and two should be 10 GB in size.
# lspv
hdisk0 00f784aee0fd700a rootvg active
hdisk1 none None
hdisk2 none None
hdisk3 none None
hdisk4 none None
# bootinfo -s hdisk0
30720
# bootinfo -s hdisk1
8192
# bootinfo -s hdisk2
8192
# bootinfo -s hdisk3
10240
# bootinfo -s hdisk4
10240
__ 4. Provide the instructor the following information:
__ a. IP addresses (HMC, AIX LPARs, and so on) and login information (user name and
password).
__ b. NIM server access (IP address) and login information (user name and password).
__ c. Class-related NIM object names for AIX installation support (lpp_source, spot, mksysb,
and machine objects). Providing a scheme or naming convention might be acceptable,
in lieu of listing each one.
__ d. For Ethernet Switch ports, if not auto-configuration, provide the speed and duplex mode.
LSG
Reference
The contents of the modify.fc.wwpns.sh script included in the AN30G class tar file is shown
below for reference.
#!/bin/ksh
# script for assigning WWPN pairs to Virtual Fiber Channel adapters
# Course AN30 ERC6.0
# AUGUST 20 2016
#
(($# !=7)) && { print usage "$0 <hmc IP> <hmc userID> <managed system name> <class
number> <lpar name> <profile> <student number>" ; exit 29 ; }
#### variables
hmc=$1
hmcID=$2
system=$3
classno=$4
lpar=$5
profile=$6
student=$7
sys=$(echo $system | cut -c 4,5,6)
wwpns="c${sys}${classno}000000000${studfirst},c${sys}${classno}000000000${studseco
nd}"
# Retrieve the virtual fibre channel adapter and parse the attributes
Important
You should completely verify all of the lab exercises whenever you build the environment as
described in this document. If you create the environment by restoring a backup copy, you should
run enough of the exercises to demonstrate that the copy was properly restored.
The lab exercises were tested in the development environment that is described in this guide. You
should test each exercise in your own lab environment to confirm the setup. Failure to complete an
end-to-end test of the labs might result in unexpected behavior during class.
Be sure to allocate enough time to complete these instructions. The classroom must be ready to
run lab exercises before the first day of class.
Performance notes
Verify that every lab workstation meets or exceeds the minimum hardware requirements.
Insufficient processor speed, memory, or disk space can affect the performance of the lab system.
Consider shutting down any running software on the workstation that is not needed or might be
using system resources.
Security or antivirus software can affect system performance, especially during the installation of
the environment.
Firewalls or proxy servers in the network can cause connectivity and performance issues. If
possible, consider disconnecting the lab workstations from the network.
Disconnect any open file shares, external USB drives, or disks that are connected to the
workstation.
LSG
Remote labs
Introduction
This topic describes the procedures for preparing a virtual image to be deployed in the IBM Remote
Lab Platform.
Note
For information about reserving and accessing remote labs on the IBM Remote Lab Platform, refer
to the Training Provider Operations Guide. IBM strongly encourages you to test the remote lab
access before the class start date. Local network restrictions can cause access problems.
LSG
Virtual machines
This table lists the specific details about the virtual machines that are used in the image for this
course.
Network configuration
This topic is optional. You need this information only if you plan to use static IP addresses for the
virtual machines in the lab image.
Table 9. Static IP addresses
Virtual machine name Static IP address
VM1 xxx.xxx.xxx.xxx
LSG
Appendix
This appendix contains forms that you can use for setting up the classroom. You can print the forms
and place a check mark by each requirement as you fulfill it to track your progress.
LSG
LSG
Important
Be sure to give the instructor a copy of this page with the values that you set.
backpg