A60 LPARVirtual Xstudhint

V4.
cover
Front cover
System p LPAR and Virtualization I: Planning and Configuration

(Course code AU73)
Student Exercises with Hints

ERC 4.0
IBM Certified Course Material
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 is a registered trademark of International Business Machines Corporation. The following are trademarks of International Business Machines Corporation in the United States, or other countries, or both: AIX Chipkill Enterprise Storage Server iSeries OpenPower POWER4 POWER Hypervisor Redbooks System i5 System Storage xSeries AIX 5L eServer HACMP LoadLeveler OS/400 POWER5 PowerPC RS/6000 System p TotalStorage AS/400 Electronic Service Agent i5/OS Micro-Partitioning POWER POWER5+ pSeries SP System p5 Virtualization Engine
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. AMD, and combinations thereof, is a trademark of Advanced Micro Devices, Inc. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.
March 2007 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 2004, 2007. All rights reserved. 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.
V4.0
TOC
Contents
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Exercises Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Exercise 1. Documentation Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Exercise 2. System Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Exercise 3. HMC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Exercise 4. System Power Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Exercise 5. Configuring Logical Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Exercise 6. Partition Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 Exercise 7. Dynamic Logical Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1 Exercise 8. Advanced Processor Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1 Exercise 9. Virtual I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1 Exercise 10. Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1 Exercise 11. Service Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1 Exercise 12. HMC and Managed System Maintenance . . . . . . . . . . . . . . . . . . . . . . 12-1
Copyright IBM Corp. 2004, 2007

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
Contents
iii
iv
System p LPAR and Virtualization I
V4.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 is a registered trademark of International Business Machines Corporation. The following are trademarks of International Business Machines Corporation in the United States, or other countries, or both: AIX Chipkill Enterprise Storage Server iSeries OpenPower POWER4 POWER Hypervisor Redbooks System i5 System Storage xSeries AIX 5L eServer HACMP LoadLeveler OS/400 POWER5 PowerPC RS/6000 System p TotalStorage AS/400 Electronic Service Agent i5/OS Micro-Partitioning POWER POWER5+ pSeries SP System p5 Virtualization Engine
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. AMD, and combinations thereof, is a trademark of Advanced Micro Devices, Inc. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.

Trademarks
vi
V4.0
pref
Exercises Description
The exercises in this book line up by name and number with the lecture units. Complete all Lets Reviews or Checkpoints in the lecture unit for each unit before doing the hands-on exercises.
Exercises Description
vii
Text highlighting
The following text highlighting conventions are used throughout this book: Bold Identifies file names, file paths, directories, user names, principals, menu paths, and menu selections. Also identifies graphical objects such as buttons, labels, and icons that the user selects. Identifies links to Web sites, publication titles, is used where the word or phrase is meant to stand out from the surrounding text, and identifies parameters whose actual names or values are to be supplied by the user. Identifies attributes, variables, file listings, SMIT menus, code examples, and command output that you would see displayed on a terminal, and messages from the system. Identifies commands, subroutines, daemons, and text the user would type.
Italics
Monospace
Monospace bold
viii
V3.1.0.1
EXempty
Exercise 1. Documentation Discovery

What This Exercise Is About
In this exercise, students will find the key documentation that support the objectives of this course.
What You Should Be Able to Do

At the end of the lab, you should be able to: Access the documentation for IBM POWER5 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 POWER5 processor-based servers.
Requirements
This workbook A computer with WebSM and a network connection to an HMC configured to support partitions. Optionally, the computer can be connected to the Internet and have a Web browser.
Exercise 1. Documentation Discovery
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 WebSM and a network connection to an HMC. The Web page URLs in this exercise were correct when this course was written. By nature, Web pages tend to change over time so ask your instructor if you have trouble navigating the Web sites. If you are using an AIX workstation for this lab, you may run into an error when you click an Adobe .pdf file from your browser. If this happens, simply set your PATH shell variable to include the path of the Acrobat Reader by executing this shell command: export PATH=$PATH:/usr/lpp/Acrobat4/bin Hints are provided for lab exercises in case you need them and provide solutions for the lab exercise steps. All hints are marked by a sign.
Access IBM Systems hardware and AIX 5L documentation

This exercise has you discover the documentation to support the managed systems and logical partitions. You can refer to this documentation as you work through the rest of the exercises in this course. __ 1. If you have World Wide Web (WWW) Access: Go to the IBM Systems Hardware Information Center on the World Wide Web. You can go to http://www.ibm.com and search for Information Center, then under Servers go to the IBM Systems Hardware Information Center. Or, you can use this URL: http://publib.boulder.ibm.com/eserver and click the IBM Systems Hardware Information Center link. Once you are at the main IBM Systems Hardware Information Center, click the link Map of pSeries books to the information center in the center of the page to view a chart of the documentation available. If you do not have World Wide Web access: A copy of the Information Center is installed on the HMC. Access this Information Center by opening up a Web browser and connect to the HMC using the following URL where HMChostname is the actual host name of your HMC. You may need to use the fully qualified host name for the HMC. http://HMChostname:4412 The Information Center on the World Wide Web is kept up to date with documentation changes. The version on your HMC may be out of date, depending on the level of HMC code that is installed.
__ 2. From the IBM Systems Hardware Information Center, use the navigation bar on the left side of the screen to find the following topics. If you are using the HMCs version
1-2
V3.1.0.1
EXempty
of the Information Center you may find that it has less information than the WWW version. Installing AIX 5L in a partition Partitioning your server Managing your server using the HMC Expand the IBM System Hardware Information Center link at the top of the navigation bar. Underneath you should see the following headings. Look at the information available in each section: Installing operating systems Partitioning the server Managing your server and devices -> Hardware Management Console
__ 3. In the IBM System Hardware Information Center, click the Service provider information. Then click Reference codes. View the reference code information available. If you encounter errors later in the course (or back at your office) you can use this to look up specific progress or error codes.
__ 4. Go to the System p and AIX Information Center. You can search for this from http://www.ibm.com by using the keywords AIX Information Center and select the appropriate link, or go to one of the following URLs: http://publib.boulder.ibm.com/infocenter/pseries or http://publib.boulder.ibm.com/eserver and select the IBM eServer pSeries and AIX Information Center link. Once you have found the System p and AIX Information Center, look for the following topics and see what information is available: AIX documentation Under AIX resources, find the Whats new in AIX 5.3 topic.
__ 5. If you have WWW access, go to the System p library on the World Wide Web and see what types of information are available. Use the URL provided below. Be sure to look at the AIX library. The URL is: http://www-1.ibm.com/servers/eserver/pseries/library
__ 6. If you have WWW access, go to the Advanced POWER Virtualization Web site and see whats available: http://www-03.ibm.com/systems/p/apv/index.html
Copyright IBM Corp. 2004, 2007 Exercise 1. Documentation Discovery 1-3
__ 7. Another important Web site is the main technical support Web site for IBM System p servers. The URL is: http://www-03.ibm.com/servers/eserver/support/unixservers Visit this technical support Web site and use the Other product support sites drop-down list to also find the HMC technical support site and the Virtualization software support sites.
__ 8. If you have WWW access, find Linux information for POWER5 processor-based servers by visiting this site: http://www.ibm.com/systems/p/linux/
__ 9. If you have WWW access, go to the main IBM System p servers Web site: http://www.ibm.com/systems/p/ Depending on your interest, click the pictures (or the View links) of the entry systems, the mid-range systems, or the high-end systems. Each link will give detailed information about the various models. Note: Instead of typing in the URL for the main pSeries site, you can go to www.ibm.com, click Products and Services, and then click System p5 (pSeries) under Systems & Servers.
__ 10. Let your instructor know you have completed the lab exercise.
End of exercise
1-4
V3.1.0.1
EXempty
Exercise 2. System Hardware Components

This exercise covers performing a hardware inventory and reviews location codes on LPAR-capable POWER5 processor-based servers.

At the end of the lab, you should be able to: Identify configured resources within a partition
Introduction
In this exercise you will identify system resources of a POWER5 processor-based LPAR-capable system. This exercise was written specifically for use with a partition running AIX 5L V5.3.
Requirements
This workbook A workstation connected to the Internet and a browser A partition running AIX 5L Version 5.3
2-1

Preface
All exercises depend on the availability of specific equipment in your classroom. Your instructor will provide the IP addresses for the systems and login information. Hints are provided for lab exercises in case you need them and provide solutions for the lab exercise steps. All hints are marked by a sign.
Gather System Information

This section has you use commands to identify system resources that are configured in your partition. These are standard AIX 5L commands with which you may already be familiar. __ 1. From your teams workstation, telnet to your assigned partition and log in as root. telnet hostname
__ 2. Use AIX 5L commands such as uname, lsattr, lsdev, lscfg, and lsslot to discover the following information about your partition. View the man pages for the commands for syntax help and to interpret the output. __ a. Display the managed system serial number. Example command and output: # uname -u IBM,03062A87G
__ b. Display the partition ID number and the partition name of the partition you are using. Example command and output: # uname -L 1 LPAR1
__ c. List the number of processors in your partition. Example command and output in which there is one processor: # lscfg | grep Proc Model Implementation: Multiple Processor, PCI bus + proc0 Processor
2-2
V3.1.0.1
EXempty
__ d. List the amount of memory configured in your partition. Example command and output which shows 1280 MB of memory: # lsattr -El sys0 -a realmem realmem 1310720 Amount of usable physical memory in Kbytes False
__ e. List the disks and their AIX 5L location codes that are configured in your partition. Example command and output which shows three disks: # lsdev -Cc disk hdisk0 Available 03-08-00-3,0 16 Bit LVD SCSI Disk Drive hdisk1 Available 03-08-00-4,0 16 Bit LVD SCSI Disk Drive hdisk2 Available 03-08-00-5,0 16 Bit LVD SCSI Disk Drive
__ f.
List Ethernet adapters installed in your partition. Example command and output which shows the dual-port integrated adapter:
# lscfg | grep ent Model Implementation: Multiple Processor, PCI bus + ent0 U787F.001.DPM166X-P1-T5 2-Port 10/100/1000 Base-TX P CI-X Adapter (14108902) + ent1 U787F.001.DPM166X-P1-T6 2-Port 10/100/1000 Base-TX P CI-X Adapter (14108902)
__ g. List all I/O slots configured in your partition. Example command and output which shows three integrated I/O slots (T5, T7, and T10):
# lsslot -c slot # Slot U787F.001.DPM166X-P1-T5 U787F.001.DPM166X-P1-T7 U787F.001.DPM166X-P1-T10 Description Logical I/O Slot Logical I/O Slot Logical I/O Slot Device(s) pci5 ent0 ent1 pci4 usbhc0 usbhc1 pci3 sisscsia0
__ h. List SCSI adapters in your partition. Example command and output which shows one dual-port SCSI adapter: # lscfg | grep scsi
+ sisscsia0 U787F.001.DPM166X-P1 SCSI Adapter + scsi0 U787F.001.DPM166X-P1-T10 SCSI Adapter bus + scsi1 U787F.001.DPM166X-P1-T11 SCSI Adapter bus PCI-X Dual Channel Ultra320 PCI-X Dual Channel Ultra320 PCI-X Dual Channel Ultra320
2-3
Physical and Logical Location Codes

Identifying physical and logical location codes is important. The steps in this section will help to reinforce the relationship between the physical and the logical location codes. Your managed system should be powered on with all partitions active for this exercise. __ 3. Using the information provided in the output of the lsdev and lscfg commands, answer the following:
__ a. Identify the location codes (both AIX 5L and physical) for hdisk0 (or the first disk in your partition). AIX 5L:
Physical:
Each partition will have a different answer. You can use lscfg | grep hdisk0 to see the physical location code and lsdev -Cc disk to see the AIX 5L location code. Example commands and output which shows that hdisk0 is connected to the adapter in slot T10: # lscfg | grep hdisk0 + hdisk0 U787F.001.DPM166X-P1-T10-L3-L0 16 Bit LVD SCSI Disk Drive (73400 MB) # lsdev -Cc disk | grep hdisk0 hdisk0 Available 03-08-00-3,0 16 Bit LVD SCSI Disk Drive
__ b. Identify the location codes of the network card in your partition. AIX 5L:
Physical:
Each partition will have a different answer. You can use the commands: lscfg | grep ent and lsdev | grep ent Example commands and output which shows that ent0 is connected to the adapter in slot T5: # lscfg | grep ent
2-4
V3.1.0.1
EXempty
Model Implementation: Multiple Processor, PCI bus + ent0 U787F.001.DPM166X-P1-T5 2-Port 10/100/1000 Base-TX PCI-X Adapter (14108902) # lsdev | grep ent ent0 Available 05-08 2-Port 10/100/1000 Base-TX PCI-X Adapter (14108902)
__ c. Identify how many processor(s) your partition is using.
AIX 5L:
Physical:
Each partition will have a different answer. You can use the commands: lsdev | grep Proc and lscfg | grep Proc Example commands and output which shows proc0 as the only processor: # lsdev | grep Proc proc0 Available 00-00 Processor # lscfg | grep Proc Model Implementation: Multiple Processor, PCI bus + proc0 Processor
End of exercise
2-5
2-6
V3.1.0.1
EXempty
Exercise 3. HMC Configuration

This exercise covers the configuration and basic operations of the HMC.

At the end of the lab, you should be able to: Download and install the WebSM client Use HMC applications to view information and configure features Set the HMC date and time Add and use HMC user accounts Configure and assign task roles and managed resource roles Run HMC commands using SSH
Introduction
In this exercise, you will check the configuration of the HMC, download and install the WebSM client, investigate HMC applications, and run HMC commands.
Requirements
This workbook A Windows 2000, Windows XP, or Linux (with Intel processor) workstation with a Web browser and connected through a network to the HMCs An assigned partition running AIX 5L
3-1

Preface
This lab covers basic operations of the HMC. This includes discovery of HMC application functions, and HMC user definition and modification. All exercises depend on the availability of specific equipment in your classroom. Hints are provided for lab exercises in case you need them and provide solutions for the lab exercise steps. All hints are marked by a sign.
Lab Exercise for Topic 1 Install WebSM Client Application on Student Workstation
In this section, you will download the WebSM client application from the HMC to your PC or Linux workstation. If you have an AIX 5L V5.3 workstation, the WebSM client is already installed and you can skip to step 2. __ 1. Install the WebSM client application on your student PC or Linux workstation. __ a. To do this, open a Web browser and type in the following as the Web address, where XXXX is the IP address or fully qualified host name of your HMC system: http://XXXX/remote_client.html __ b. You will need to log in with the username of hscroot and the password given to you by the instructor. If the login fails, ask your instructor if there is a different password. __ c. Select the InstallShield application. __ d. Click the correct operating system, download the file to your system, and execute it. (For Linux workstations, you may need to change the permissions of the file to allow it to be executed.) __ e. When you execute the setup.exe file, the InstallShield Wizard will load and run. __ f. If you are prompted for Java security requests, select Grant for all requests.
__ g. You will need to click Next a few times and then Finish to complete the installation process. You may be asked if you want to overwrite existing information; answer Yes. __ h. This process should put an icon on your Windows desktop for the Web-based System Manager.
__ 2. Run the WebSM client by double-clicking the icon on the Windows PC or by typing wsm at the Linux shell prompt. On the login screen, enter the fully qualified domain name or the IP address (provided by instructor) of the HMC in the host name field. Press Enter. Wait a few
3-2 System p LPAR and Virtualization I Copyright IBM Corp. 2004, 2007
V3.1.0.1
EXempty
seconds for the handshaking process to complete, then enter the username of hscroot and the password. The HMC console interface will load. Ignore the second log window that opens on Windows PCs and do not close it. It can be minimized.
__ 3. By clicking around the HMC applications, discover what version and release of software is running on the HMC. The HMC version is the major version number for the HMC software, and the release level is the minor point release level. Open the Licensed Internal Code Maintenance application. Then open the HMC Code Update application. Scroll to the STATUS section near the bottom of the screen. The HMC version and release levels (and build date) are listed.
__ 4. Using the Server Management application on the HMC, identify all partitions that are running, and list their names here.
Open the Server and Partition application, then open the Server Management application. Expand the list of partitions and look for any with a state of Running. In the following example, LPAR1 and LPAR2 are listed as running:
__ 5. The HMC supports one virtual terminal window per partition. This window is the console for the partition. Open the terminal window to a partition. If you have an assigned partition for your lab group, use that partition. Close the terminal window. Right-click the mouse button on the partition name, and choose Open Terminal Window on the pop-up menu to open the virtual console. Wait a moment and another window will open. This is the virtual console to that partition.
Copyright IBM Corp. 2004, 2007 Exercise 3. HMC Configuration 3-3
On Microsoft Windows systems, click the X in the upper right hand corner of the window to close it. On X-windows versions of WebSM, use the window banner menu to close the window.
__ 6. The HMC has its own system clock and there is one system clock in the managed system. Each partition can run its own time because the time of day clock is virtualized for each of the partitions. Find the HMC application where the time zone, date, and time can be changed. View all of the time zones available. Do not change the configuration. Be sure to use the Cancel button to exit out of the window. Open the HMC Management application, then open the HMC Configuration application. Select the Customize Console Date and Time task. In the pop-up window, use the pull-down for the time zone field. Look at the options. Click the Cancel button to exit without making any changes.
__ 7. From the HMC interface, access the Information Center and search for server setup. From here you can find information about how to set up the managed system and see more documentation that is available. When the Information Center window opens up in a browser, notice the address that is used. You should notice that the address is to your HMC. You are viewing the copy of the Information Center on your HMC. In the navigation window in the HMC interface, choose the Information Center and Setup Wizard application. Select the Launch the IBM Systems Hardware Information Center option. A Web browser will open with the Information Center that is stored on your HMC. Notice the address at the top; it should include your HMCs host name. For example, this address shows the Information Center stored on the HMC with the lou-hmc.beaverton.ibm.com host name:
In the search window, enter the string server setup.

V3.1.0.1
EXempty
The search results window will open with many matches. Click a few to see what server setup information is available. Close the browser window when you are finished looking.
__ 8. Another way to find help is to use the Help menu item in the HMC interface. Use this Help menu item to identify the application that will allow you to format media on the HMC. To find this answer, access the Help menu item in the HMC menu bar. For example:
In the pop-up Help window, select the magnifying glass in the upper left corner, then type in the string format media into the Find: field, then press the Enter key. For example:
Notice the second option is Format Removable Storage. Choose this item. The Help window will show you how to find the application to use. Answer: Licensed Internal Code Maintenance -> HMC Code Update -> Format Removable Media
__ 9. In the HMC Help window, click the book icon in the upper left corner of the window. Notice the structure of the information; each of the main HMC applications is listed and if you expand the information under each, you will see a list of tasks on which you can receive help. Open and close a few of the applications to see the help information available.
3-5
If you closed the Help window from the previous step, access the Help menu item again in the HMC menu bar. For example:
In the pop-up Help window, select the book icon in the upper left corner and view the information. For example:
__ 10. Using the Information Center, the Help menu, or simply by exploring, find the application on the HMC that will allow you to schedule an operation. Which application is this? HMC Management -> HMC Configuration -> Schedule Operations
__ 11. Find the application with which you can view console events. Use this application to see what kinds of events have happened on your HMC. The applications is: HMC Management -> HMC Configuration application. Choose View Console Events. It may take a few moments for this window to appear.
3-6
V3.1.0.1
EXempty
__ 12. Examine the network configuration settings for the HMC. Find where to set the DNS information, the routing information, and the host name. HMC Configuration -> Customize Network Settings
__ 13. Change the firewall configuration on the HMC to allow SSH traffic. It may already be configured to allow SSH traffic, if so, leave the configuration as is. The application is HMC Configuration -> Customize Network Settings. Go to the LAN Adapters tab in the pop-up window. Select the second Ethernet port (eth1), click the Details... button, and go to the Firewall tab. In the firewall window, there are two white panels. The upper panel has all of the options. Select Secure Shell with the port of 22:tcp. This is the SSH port. Click the Allow Incoming button. You will probably get a pop-up notice that says it is already allowed. If so, simply cancel out of all of the network configuration windows and leave the configuration as is.
__ 14. Find the application that will let you ping one of the other HMCs from your HMC. ping another HMC and see if it was successful. Notify the instructor if it is not successful. HMC Management -> HMC Configuration -> Test Network Connectivity Here is what the Test Network Connectivity task (the ping utility) on the HMC looks like:
After you click OK on the ping utility, a working window shows you the output of the ping command. Look for the success message. For example:
3-7
Accessing ASMI
ASMI was covered in Unit 2 of this course, however in Exercise 2 you did not have the WebSM remote client installed on your workstation. Now that WebSM is available, explore the ASMI application in the following steps. __ 15. Access the ASM interface running on the Service Processor. To do this, connect to the HMC with the WebSM remote client. Go to the Service Applications -> Service Focal Point -> Service Utilities. Select the correct system and choose the Launch ASM Menu option from the Selected menu. Log in as admin or the login (and password) that the instructor provided.
__ 16. Once in ASMI, view the various screens and see what tasks are available. Do not change any configuration parameters.
__ 17. Let your instructor know when you have completed the lab exercise for this topic.
Lab Exercise for Topic 2 HMC Users

In this section you will create custom HMC users. Please do not change the password for the hscroot user!
__ 18. If you do not already have it running, bring up the WebSM client by double clicking the icon on the Windows PC or by typing wsm at the Linux shell prompt.
3-8
V3.1.0.1
EXempty
On the login screen, enter the fully qualified domain name or the IP address (provided by instructor) in the host name field. Press Enter. Wait a few seconds for the handshaking process to complete, then enter the username of hscroot and the password.
__ 19. Open the HMC Management application on the HMC. Then open the HMC User application and create a new user on the HMC named hscpe0# where # is the number of your lab team. Give this user the hmcservicerep role. Assign abc1234 for the password. (Passwords must be at least 7 characters.) Select the HMC Management application, then select the HMC Configuration application. Access the HMC Users application, click the Manage HMC Users and Access option. In the User Profiles pop-up box that appears, choose the User -> Add menu option. Another pop-up box will appear. Enter hscpe0# (where # is the number of your lab team) in the User ID field. Enter a description such as New Service Rep. Enter abc1234 in the Password: and Confirm password: fields. Click AllSystemResources if it is not highlighted in the Managed Resource Roles box. In the Task Roles box, click the hmcservicerep role. Click the OK button to create this user.
__ 20. Create another HMC user called hscop# (where # is the number of your team), and give this user the hmcoperator role. Assign abc1234 as the password to the new user. This step creates a new user in the same way as the previous step, with the only difference being the user will be assigned hmcoperator capabilities instead of hmcservicerep. When you have created this user, you should see a list of users similar to this:
3-9
__ 21. Open up a second WebSM remote client application and log in with your hscop# (where # is the number of your team) account. Can you add a new user while you are logged in as hscop#? Try to perform other tasks and see if the hmcoperator is allowed to do them. When you are done, close the WebSM remote client window where you are logged in as hscop#. Note: You can see the login name in the WebSM remote client application window in the lower right corner. An hmcoperator is not allowed to add users. The Manage HMC Users and Access item is not available to you.
__ 22. From the WebSM window where you are logged in as hscroot, access the Information Center and search for user management. From here you can view tables that list what tasks the various standard task roles can perform. In the navigation window in the HMC interface, choose the Information Center and Setup Wizard application. Select the Launch the IBM Systems Hardware Information Center task. A Web browser will open with the Information Center that is stored on your HMC. In the search window, enter the string user management. The search results window will open with many matches. In the example below, the first one, HMC user management tasks, is the one you should look for:
Select the HMC user management tasks link. Look back at the main browser window. You will see a table with a list of tasks and which users, with the default task roles, can perform those tasks.
__ 23. Create a new user that has a custom managed resource role for LPAR1 only. This user should only be able to use the HMC console interface (not the command line) and should only be able to open a terminal window to LPAR1. Then, start another instance of WebSM, connect to the HMC, and log in as the new user you just created. Make sure the only task the new user can perform is to open a terminal window to LPAR1. When you are finished testing you can close this second WebSM remote client window.
V3.1.0.1
EXempty
Remember that you must create a customized task role and a customized managed resource role before creating a new user based on these. Select the HMC Management -> HMC Users application on the HMC. Select Manage Access Task Roles and Managed Resource Roles. The Customize User Roles window will pop up with the Managed Resource Roles radio button selected. Here is an example:
Use the Edit -> Add menu to add a new managed resource role called LPAR1only. In the Available Objects window, double-click the Managed system name to open the folder. Choose LPAR1 and click the Add button to add that resource to the Current Objects box. Click OK to finish. Here is an example of this window. You can double-click the Managed System folder in the Current Objects folder to check the configuration, as shown here:
After you click the OK button on the Add Role window (shown above), that window will close and you will be back in the Customize User Controls window. Click the Task Roles radio button like this to access the customize user controls for task roles:
3-11
Use the Edit -> Add menu option to create a new task role called OpenConsole. An Add Role window will open like the one shown below. The Based on: pull-down list should read hmcservicerep. In the large box on the lower left part of the window, open the Console Tasks folder (left-click on it twice). Then open the Partitions folder. Select the Open Terminal Window task (as shown below) and click the Add button to add it to the Current Tasks list. Here is an example:
Click OK to finish creating the task role. Close the Customize User Tasks window. Now you need to add a user with the new managed resource task and the new task role that you just created. In the HMC Users window, select the Manage HMC Users and Access option. In the pop-up window, use the User -> Add menu option to create a user called newuser#, where # is the number of your lab group, with a password of abc1234. The users description could be simply New User. Click the
V3.1.0.1
EXempty
LPAR1only managed resource task and the OpenConsole task role. Click OK to finish. Here is an example of that window:
Close any remaining user profiles windows. Start another instance of WebSM, connect to the HMC, and log in as the new user you just created. Once the WebSM client appears, open the Server and Partition application. Then open the Server Management application. Click the + sign next to the managed system name to expand the objects. Click the + next to the partitions item so that you can see the partition names. You should only be able to see LPAR1. Click with the mouse button on the LPAR1 partition name to select it. Right-click the mouse button on the LPAR1 partition name to bring up the pop-up menu. Notice the options on the menu. The Create menu and Dynamic Logical Partitioning options are there, but the sub-options for these menus are unavailable. Open Terminal Window should be the only option available to newuser#. Here is what you should see:
3-13
Choose the Open Terminal Window option, to make sure your user can perform this task. Then close the terminal window and close the WebSM client application.
__ 24. In the WebSM remote client application where you are logged in as hscroot, remove all the users that you created in this exercise. Go back to the HMC Management -> HMC Users application. Select the Manage HMC Users and Access task. In the pop-up window, select one of the users you created in this exercise, then choose User -> Remove on the menu. Confirm that you want to remove the users by clicking Yes. Remove all three users you created (hscpe0#, hscop#, and newuser#) and any others that you might have created. Close the User Profiles window.
HMC Remote Access

__ 25. Add another HMC to your WebSM client application. Log in to that HMC and see what partitions are running. To add another HMC to your WebSM application, use the Console -> Add -> Hosts... menu and type in the HMCs host name. For example:
3-14 System p LPAR and Virtualization I
V3.1.0.1
EXempty
Here is where you type in the host name. Click Add after you type in the host name:
After the new HMC is added, it will appear in the navigation window like this:
3-15
Click the new HMCs host name with the left mouse button. You will be prompted to login. The login should be the same (hscroot) because that is the way the training lab has been set up, but you may have different logins for different HMCs at your office. Once you log in, you will be able to access all of the HMC applications.
__ 26. Remove the new HMC that you added in the last step to the WebSM Navigation Area. To remove the HMC that you just added in the last step, access the Console -> Remove -> Hosts... menu as shown below:
In the window that pops up, select the new HMCs name, the click the Remove button. The window should look like this:
V3.1.0.1
EXempty
Another window will pop up and you will be asked whether you wish to continue, click Yes.
__ 27. Check that remote access using SSH is enabled on the HMC. Open the HMC Management application. Then open the HMC Configuration application. Select the Enable or Disable Remote Command Execution option and make sure that this feature is checked. Click OK to close the window. We already checked in a previous exercise step that the firewall allows Secure SHell (SSH) access.
__ 28. You will need to use SSH (Secure SHell) to connect to the HMC to run its commands. You will log in using the hscroot account. Windows-based workstation: You should see an icon on your desktop to access the SSH utility. (An example utility that provides SSH connections is the PuTTY utility.) Run the utility and enter the host name or IP address of the HMC. You may need to click SSH in the utility window. Linux or AIX workstation: From a shell, use the ssh command to connect to the HMC. Example shell command where hmchostname is the actual hostname of the HMC: ssh -l hscroot hmchostname Locally from the real HMC: Right-click the mouse off of the main HMC application screen. Pick the menu option to open an SSH session. This will open a window to the restricted shell on the HMC.
Copyright IBM Corp. 2004, 2007 Exercise 3. HMC Configuration 3-17
From an AIX 5L partition: You can also telnet into your AIX 5L partition and use the ssh command from there. Try out one of these methods to log in to the HMC command line.
HMC Command Line Commands

In this section you will use SSH to execute HMC commands remotely to gather system information, learn about HMC command syntax, and find help information. For the following steps, list the exact command you used for future reference. __ 29. To learn more about the HMC commands and their syntax, use the HMC man pages. Once you have logged in, run the following commands: echo $PATH (This will show which directories contain commands you can run.)
ls /usr/hmcrbin (List out one of the directories in your PATH variable.) man lssyscfg (To see information for the lssyscfg command.)
A few commands do not have man pages. If you find one, run the command with either the --help or the --usage option for usage information. Look over the commands and you will see some patterns in the way they are named. For example, while lshwres (list-hardware-resources) will list information about system resources, the chhwres (change-hardware-resources) will allow you to change the hardware resource configuration for partitions.
__ 30. Optional: You may use the shell command set -o vi to use vi style command line editing to make your login session easier. Likewise, set -o emacs can be used for emacs style editing.
__ 31. Optional: When you view man pages at the HMC command line and then type q to close the man page, the entire man page may disappear. If you prefer that the portion of the man page you were viewing to stay visible when you press q, then change the TERM variable to ansi. To change the TERM variable, issue this command: export TERM=ansi
__ 32. Many of the commands have very long outputs. Try this command where msname is the name of your managed system and see what information is given: lssyscfg -m msname -r sys To find out your managed system name, run the following HMC command: lssyscfg -r sys -F name
V3.1.0.1
EXempty
Here is an example lssyscfg command and its output where the managed system name is sputnik: hscroot@sputnik-hmc:~> lssyscfg -m sputnik -r sys name=sputnik,type_model=9131-52A,serial_num=062A87G,ipaddr=192.1 68.255.254,state=Operating,sys_time=10/18/2006 19:58:30,power_of f_policy=1,cod_mem_capable=0,cod_proc_capable=1,hca_capable=1,hu ge_page_mem_capable=1,micro_lpar_capable=1,os400_capable=0,5250_ application_capable=0,redundant_err_path_reporting_capable=1,sha red_eth_failover_capable=1,sni_msg_passing_capable=0,sp_failover _capable=0,vet_activation_capable=1,virtual_io_server_capable=1, assign_5250_cpw_percent=0,max_lpars=20,max_power_ctrl_lpars=1,se rvice_lpar_id=none,curr_sys_keylock=norm,pend_sys_keylock=norm,c urr_power_on_side=temp,pend_power_on_side=temp,curr_power_on_spe ed=fast,pend_power_on_speed=fast,curr_power_on_speed_override=no ne,pend_power_on_speed_override=none,power_on_type=power on,powe r_on_option=standby,pend_power_on_option=standby,power_on_method =02,power_on_attr=0000,sp_boot_attr=0000,sp_boot_major_type=08,s p_boot_minor_type=01,sp_version=00030030,mfg_default_config=0,cu rr_mfg_default_ipl_source=a,pend_mfg_default_ipl_source=a,curr_m fg_default_boot_mode=norm,pend_mfg_default_boot_mode=norm
__ 33. Now try the same lssyscfg command with filters added so only certain fields are shown. Many of the commands can use filters. You have to add the --headers option to see the headers for each field. (Substitute msname for your managed systems name.) lssyscfg -m msname -r sys -F name,type_model --header Here is an example lssyscfg command and its output (the slash at the end shows that the command continues on the next line): hscroot@sputnik-hmc:~> lssyscfg -m sputnik -r sys -F \ name,type_model --header name,type_model sputnik,9131-52A
__ 34. One HMC may be connected to multiple managed systems. Find the command which will show a list of all online managed systems connected to this HMC and their machine type and serial numbers. Here is the command:
3-19
lssyscfg -r sys -F name,type_model,serial_num --header Output example: (There is only one managed system listed named sputnik.)
hscroot@sputnik-hmc:~> lssyscfg -r sys -F name,type_model,serial_num --header name,type_model,serial_num sputnik,9131-52A,062A87G
__ 35. Using the same command with different options, find the current state of a specific managed system and its operator panel. Here is the command: lssyscfg -r sys -m msname -F name,state --header (Substitute msname for your managed systems name.) Output example:
hscroot@sputnik-hmc:~> lssyscfg -r sys -m sputnik -F name,state --header name,state sputnik,Operating
__ 36. Try out this command and see what it does: lshmc -v This command displays vital product data for the HMC. Output example: hscroot@sputnik-hmc:~> lshmc -v "vpd=*FC ???????? *VC 20.0 *N2 Wed Oct 18 13:16:10 PDT 2006 *FC ???????? *DS Hardware Management Console *TM eserver xSeries 336 -[7310CR3]*SE 10E705A *MN IBM *PN Unknown *SZ 1058738176 *OS Embedded Operating Systems *NA 9.47.87.170 *FC ???????? *DS Platform Firmware *RM V6R1.0 "
V3.1.0.1
EXempty __ 37. What command will list all of the HMC users? Here is the command: lshmcusr Output example: hscroot@sputnik-hmc:~> lshmcusr name=hscroot,taskrole=hmcsuperadmin,description=HMC Super User,pwage=99999,resourcerole=ALL: name=root,taskrole=hmcsuperadmin,description=root,pwage=99999,re sourcerole=ALL:
__ 38. Discover which command will list out all active partitions which support dynamic LPAR operations. Here is the command: lspartition -dplar Example output:
hscroot@sputnik-hmc:~> lspartition -dlpar <#0> Partition:<1*9131-52A*062A87G, sputnik171.beaverton.ibm.com, 9.47.87.171> Active:<1>, OS:<AIX, 5.3>, DCaps:<0x3f>, CmdCaps:<0xb, 0xb>, PinnedMem:<203> <#1> Partition:<2*9131-52A*062A87G, sputnik172.beaverton.ibm.com, 9.47.87.172> Active:<0>, OS:<, >, DCaps:<0x0>, CmdCaps:<0x0, 0x0>, PinnedMem:<0> <#2> Partition:<2*9111-520*106A7DD, mir155.beaverton.ibm.com, 9.47.87.155> Active:<1>, OS:<AIX, 5.3>, DCaps:<0x3f>, CmdCaps:<0xb, 0xb>, PinnedMem:<137>
__ 39. Figure out the command syntax for lshwres so that it displays all of the processor information on the managed system. Here is the command: lshwres -r proc -m msname --level sys (Where msname is the name of the managed system.) Example output:
hscroot@sputnik-hmc:~> lshwres -r proc -m sputnik --level sys configurable_sys_proc_units=2.0,curr_avail_sys_proc_units=0.7,pend_avail_sys_ proc_units=0.7,installed_sys_proc_units=2.0,max_capacity_sys_proc_units=2.0,d econfig_sys_proc_units=0.0,min_proc_units_per_virtual_proc=0.1,max_virtual_pr ocs_per_lpar=64,max_shared_proc_pools=1
3-21
__ 40. Figure out the command syntax for lshwres so that it displays all of the memory information for the partitions on the managed system. Here is the command: lshwres -r mem -m msname --level lpar (Where msname is the name of the managed system.) Example output:
hscroot@sputnik-hmc:~> lshwres -r mem -m sputnik --level lpar lpar_name=LPAR1,lpar_id=1,curr_min_mem=1024,curr_mem=1280,curr_max_mem=1536,p end_min_mem=1024,pend_mem=1280,pend_max_mem=1536,run_min_mem=1024,run_mem=128 0,curr_min_num_huge_pages=0,curr_num_huge_pages=0,curr_max_num_huge_pages=0,p end_min_num_huge_pages=0,pend_num_huge_pages=0,pend_max_num_huge_pages=0,run_ num_huge_pages=0,curr_bsr_arrays=null lpar_name=LPAR2,lpar_id=2,curr_min_mem=1024,curr_mem=1280,curr_max_mem=1536,p end_min_mem=1024,pend_mem=1280,pend_max_mem=1536,run_min_mem=1024,run_mem=128 0,curr_min_num_huge_pages=0,curr_num_huge_pages=0,curr_max_num_huge_pages=0,p end_min_num_huge_pages=0,pend_num_huge_pages=0,pend_max_num_huge_pages=0,run_ num_huge_pages=0,curr_bsr_arrays=null lpar_name=VIOS,lpar_id=3,curr_min_mem=256,curr_mem=512,curr_max_mem=1024,pend _min_mem=256,pend_mem=512,pend_max_mem=1024,run_min_mem=256,run_mem=128,curr_ bsr_arrays=null
__ 41. On the HMC command line, open a terminal to a partition. Log in to the partition then log out and break the connection to return to the HMC command line. To create the virtual terminal to the partition: mkvterm -p partitionname -m msname (Where partitionname is the name of your partition in the Server Management application and not its host name. msname is the name of the managed system.) You will then see the AIX 5L login prompt. Log in as root. Then you can type exit to log out. At the new login prompt enter a tilde then a dot ( ~.), you will have to answer y to confirm that you want to terminate the connection, then the connection will be broken. Output example for terminating session: (Notice that you do not actually see the . or the y) AIX Version 5 (C) Copyrights by IBM and by others 1982, 2006. Console login: ~ Terminate session? [y/n]
V3.1.0.1
EXempty
You can also try the vtmenu command. Run vtmenu then pick an LPAR from the list. (If the command tells you that the TERM variable is unknown, choose vt320 from the list of choices.) Once the console session successfully opens, close the session as you did with the mkvterm command.
__ 42. If you still have time in the lab, try out other commands you find in /usr/hmcrbin on the HMC. Use Appendix C in your Student Guide as a reference. Make sure the commands only list information and do not change the system configuration.
__ 43. Let your instructor know when you have completed the lab exercise.
End of exercise
3-23
V3.1.0.1
EXempty
Exercise 4. System Power Management

This exercise demonstrates power on and off procedures of managed systems.

At the end of the lab, you should be able to: Power on a managed system using these power-on options: - Partition Standby, System Profile, or Partition Auto Start Power off the managed system
Introduction
In this exercise, you will control power to a managed system with both the graphical HMC applications and with HMC command line commands.
Requirements
This workbook A workstation with WebSM connected to a network A POWER5 processor-based managed system connected to the same network as the workstations
4-1

Preface
All exercises depend on the availability of specific equipment in your classroom. Hints are provided for lab exercises in case you need them and provide solutions for the lab exercise steps. All hints are marked by a sign.
Power On/Off Procedures

__ 1. All groups should initiate a proper shutdown to their partitions. In the WebSM remote client application connected to your HMC, go to the Server Management application. Right-click a running partition. Select Open Terminal Window on the menu and log in. Shut down the partition with the shutdown -F command. If your group has multiple partitions, shut them all down. Close the partition console windows. Wait until all partitions have a state of Not Activated before proceeding.
__ 2. Once all of the partitions are in the Not Activated state, power down the managed system from your WebSM HMC session. Bring up WebSM on your workstation. In the Server Management application, select the managed system by left-clicking the name. For example:
Right-click the name and you will be given a pop-up menu. Select Power Off Managed System. Choose the Normal power off option in the window that pops up. For example:
4-2
V3.1.0.1
EXempty
__ 3. When the system is completely powered off, power it on using the Partition auto start power on option. Select the managed system name and choose the Power On menu item. For example:
In the next screen, choose the Partition auto start option, then click OK. For example:
Copyright IBM Corp. 2004, 2007 Exercise 4. System Power Management 4-3
__ 4. What did the Partition auto start option do? We will test this feature more extensively in a future lab exercise. The system should power on to the Standby state and no partitions will probably have started because they should not have been configured to auto start.
__ 5. Open an SSH session with the HMC and use an HMC command to power off the managed system. Use the fast power off option. What command did you use? You will need to use an SSH tool on your student workstation to log in to the HMC. Your partitions are not running so you cannot log in to a partition to ssh to the HMC. Look for PuTTY or similar login tool if you have a Windows system, or for an AIX or Linux system, use the ssh command. Connect to the HMC using SSH. Once you log in to the HMC, use this HMC command to power off the managed system normally: chsysstate -r sys -m managedsysname -o off
V3.1.0.1
EXempty __ 6. Use the HMC command to check the state of the managed system to make sure it is powered off. What command did you use? At the HMC shell prompt use this HMC command to check state of the managed system: lssyscfg -r sys -m managedsysname -F state --header The output should be: state Power Off
__ 7. In your WebSM client, what indication is there that the managed system is ready for you to power it on? The State should show Power Off like this:
__ 8. Using WebSM, power on the system to the Standby state. Select the managed system name and choose Power On on the menu. Choose the Partition standby power on option in the pop-up window.
__ 9. While the system is powering on, go back to your SSH session on the HMC. Use the lssyscfg command to view all information about the managed system. You can use the --help option to lssyscfg to view the syntax of the command and see all the options. HMC command: lssyscfg -r sys -m managedsysname Here is an example of the command and its output:
Copyright IBM Corp. 2004, 2007 Exercise 4. System Power Management 4-5
hscroot@sputnik-hmc:~> lssyscfg -r sys -m sputnik name=sputnik,type_model=9131-52A,serial_num=062A87G,ipaddr= 192.168.255.254,state=Power Off,sys_time=10/20/2006 17:55:18, power_off_policy=1,cod_mem_capable=0,cod_proc_capable=1,hca_capa ble=1,huge_page_mem_capable=1,micro_lpar_capable=1,os400_capable =0,5250_application_capable=0,redundant_err_path_reporting_capab le=1,shared_eth_failover_capable=1,sni_msg_passing_capable=0,sp_ failover_capable=0,vet_activation_capable=1,virtual_io_server_ca pable=1,assign_5250_cpw_percent=0,max_lpars=20,max_power_ctrl_lp ars=1,service_lpar_id=none,curr_sys_keylock=norm,pend_sys_keyloc k=norm,curr_power_on_side=temp,pend_power_on_side=temp,curr_powe r_on_speed=fast,pend_power_on_speed=fast,curr_power_on_speed_ove rride=none,pend_power_on_speed_override=none,power_on_type=power on,power_on_option=standby,pend_power_on_option=standby,power_o n_method=02,power_on_attr=0000,sp_boot_attr=0000,sp_boot_major_t ype=08,sp_boot_minor_type=01,sp_version=00030030,mfg_default_con fig=0,curr_mfg_default_ipl_source=a,pend_mfg_default_ipl_source= a,curr_mfg_default_boot_mode=norm,pend_mfg_default_boot_mode=nor m
__ 10. From your SSH session, run the command which will list all partitions configured on your managed system. What command did you use? This command gives just the partition names: lssyscfg -r lpar -m managedsysname -F name --header Here is an example of the command and its output. In this example, name is the header and there are three partitions configured on the managed system specified as sputnik in the command. hscroot@sputnik-hmc:~> lssyscfg -r lpar -m sputnik -F \ name --header name LPAR1 LPAR2
__ 11. Your system should have powered up to the Standby state by now. Verify this either with an HMC command or by looking at the WebSM window. Notice the State column for the managed system in this example:
4-6
V3.1.0.1
EXempty
Alternatively, you could use the lssyscfg command on the HMC command line. For example: lssyscfg -r sys -m managedsysname -F state --header The output should be: state Standby
__ 12. From your SSH session, run the command which will list not only all partitions configured on your managed system, but their states. What command did you use? Here is the command: lssyscfg -r lpar -m managedsysname -F name,state --header Here is an example of this command and its output: hscroot@sputnik-hmc:~> lssyscfg -r lpar -m sputnik -F \ name,state --header name,state LPAR1,Not Activated LPAR2,Not Activated
__ 13. Power off the managed system once again using either WebSM or the HMC command line. To power off the managed system from WebSM, select the managed system name, right click, and choose Power Off Managed System on the pop-up menu.
4-7
Alternatively, from the HMC command line, you can use this command to power off the managed system. Be sure to replace managedsysname with the actual managed system name. chsysstate -r sys -m managedsysname -o off
__ 14. Power on the managed system using the Normal system profile name. We will discuss how to configure system profiles later in the course. Using this profile should power on your managed system and automatically start your partitions. Select the managed system name, right click, and choose the Power On menu item. In the next screen, choose the System profile start option. Select the Normal system profile name at the bottom of the screen. Here is an example showing the pop up window after you select the managed system name and choose Power On on the menu. Notice that the System Profile option is selected and the Normal system profile is selected. Click OK to power on the system.
4-8
V3.1.0.1
EXempty
End of exercise
4-9
V3.1.0.1
EXempty
Exercise 5. Configuring Logical Partitions

This exercise covers the configuration of partitions and partition profiles, and the activation of partitions.

At the end of the lab, you should be able to: Create a logical partition Create a logical partition profile Configure resources for partition profiles Set the boot option for a partition profile Manually activate a partition
Introduction
In this exercise, you will become familiar with the HMC applications and menus which allow you to create and configure partitions. You will also manually activate partitions.
Requirements
5-1

Preface
All exercises of this chapter depend on the availability of specific equipment in your classroom. You will need a computer system and a managed system accessible to each other on a network. Hints are provided for lab exercises in case you need them and provide solutions for the lab exercise steps. All hints are marked by a sign.
Initializing Partition Profile Data

__ 1. In this exercise, we will delete all existing partition data and recreate it from scratch. First, lets document the current configuration data so you can recreate the same configuration. __ a. Document the processor and memory information: Partition Name: LPAR1 LPAR2 Min/Des/Max Processors: Min/Des/Max Memory:
Total Configured: Total Installed: To find out the values for processors and memory, go to the HMC Server Management application. Expand all of the partition information so that you can see the partition profile names. For example:
5-2
V3.1.0.1
EXempty
Select each of the default partition profiles for the partitions to see the processor and memory configuration information. On your training system, the profiles may not be named default, and if so, use the profiles with the check marks beside their names. Select the default profiles, right-click, and choose Properties on the pop-up menu. Go to the Processors tab for the processor information for the table above. Go to the Memory tab for the memory information for the table above. Do not close the Properties window yet; you will need it for the next step.
__ b. Document the I/O slot allocations for the partitions on the managed system:
Partition name: _______________________
Partition name: _______________________
To get the I/O slot allocation information, use the Physical I/O tab in the partition profile Properties screen. Use the Profile I/O devices panel in the lower part of the window, and expand all the bus information by clicking the icons next to the bus names.
5-3
In the following example, you would document that this partition has configured slots T5, T7, and T10.
When you have all of the resource information documented you can close the Properties pop-up window. You will have to do this for each partition on your managed system. If other lab groups are using your managed system, work together as a team to document all of the partition configurations.
__ 2. Working with the other students that are using the same managed system, re-initialize the HMC partition profile data. All partitions must first be in the Not Activated state, so stop any running partitions. Initialize the partition data by selecting the managed system name and using the Profile Data -> Initialize menu option. The Initialize step will take a moment and will delete all partition data. When the initialization is done you should not see any partitions. The Server Management application should look similar to the following example:
5-4
V3.1.0.1
EXempty
Planning LPAR Configurations

Each lab group will create at least one partition. You will have to work together to make sure you do not have resource conflicts. __ 3. Take the total system memory and subtract 512 MB. Take what is left over and divide it equally between the partitions that will be created on this system. The amount must be a multiple of the LMB size on the system. How much memory will that give your groups partition? If you do not know how much system memory your managed system has, go to the Server Management application, select the managed system name, right-click, and choose Properties on the pop-up menu. In the Properties screen, go to the Memory tab and look at the value for Installed Memory at the top. Here is an example of this Memory tab. This system has 4096 MB (4 GB) of memory.
If you have a system with 4096 MB of memory, subtracting 512 MB will leave you with 3584 MB to use for partitions. If you will be creating two partitions, splitting
Copyright IBM Corp. 2004, 2007 Exercise 5. Configuring Logical Partitions 5-5
this amount evenly will give each partition 1792 MB of memory. This will be what you use for the Desired amount when you configure each partition.
__ 4. Take the total number of whole processors on the system, and divide them equally as much as possible between the partitions. How many whole processors will your partition have? If you do not know how many processors your managed system has, in the Server Management application, select the managed system name, right-click, and choose Properties on the pop-up menu. In the Properties screen, go to the Processors tab and look at the value for Installed processing units at the top. Here is an example of this Processors tab. This system has 2.0 processing units or 2 whole (dedicated) processors.
If you create two partitions, then you will have one whole dedicated processor for each partition.
__ 5. For your new partitions, you will use the same I/O allocations that you documented in a previous step of this exercise.
__ 6. You will need to set a unique LPAR ID number. Coordinate with any other lab groups on your managed system so that each partition has a unique number.
5-6
V3.1.0.1
EXempty
Creating and Configuring LPARs

__ 7. The managed system must be powered on in the Standby or Operating state. Check the state of the system. Look at the State column in the Server Management application to see the system state. In this example, the state is Operating:
If the state is Power Off, then you will have to power on the managed system. Select the managed system name, right-click, and choose Power On on the pop-up menu. Choose Partition Standby as the Power On option. Wait for the system to have the Standby state before proceeding to the next step.
__ 8. Select the managed system in the HMC GUI, right-click, and choose Create -> Logical Partition. The Create Logical Partition Wizard task window will appear.
__ 9. In the Create Logical Partition wizard, enter the unique partition ID and the partition name. The partition names must be unique on the managed system, so if there are multiple lab groups working on the same managed system, coordinate with the other groups to make sure your partition name is unique. Make sure the AIX or Linux button is selected at the bottom. Click the Next button on the bottom of the screen to advance to the next screen. For example:
5-7
__ 10. The next screen will ask if this partition will be part of a workload management group. Answer No then click Next to advance to the next screen. Here is an example of this screen:
5-8
V3.1.0.1
EXempty
__ 11. In the next screen, name the partition profile default. Here is an example screen where you name the partition profile:
__ 12. Using the memory and processor planning you performed in previous steps and the I/O slot planning information that you documented earlier in this exercise, allocate the resources for the partition profile. While you are on the memory, processor, and I/O screens, try the following: __ a. On the memory screen, attempt to allocate an amount of minimum memory that is more than the desired memory. What happens? It will not let you do this and you will get a warning message.
__ b. On the memory screen, attempt to allocate more memory than is available on the system. What happens? It will not let you do this and you will get a warning message.
__ c. Set the desired memory to the planned amount and the minimum and maximum values to 256 MB below and above the desired, respectively. You may type in the amounts or use the up and down arrows next to the input boxes. Here is an example configuration.
Click the Next button to advance to the next screen.
__ d. Configure your partition for dedicated processors. On the next screen, click the Dedicated button to configure dedicated processors. Click the Next button to advance to the next screen.
__ e. On the processors screen, type in the correct number of processors for your partition. The minimum and desired amounts can be equal. Set the maximum amount to all of the processors on the system. Here is an example screen:
V3.1.0.1
EXempty
Click the Next button to advance to the next screen.
__ f.
On the I/O screen, attempt to allocate a slot that another lab team is allocating to their partition profile. Are you able to do this? Why? Yes, you will be allowed to do this. The HMC cannot predict what partitions will run simultaneously so it will not prevent you from adding slots that are already listed in another partition profile.
__ g. Click through the I/O slots and notice the location codes and types of adapters. Notice what is included under each bus.
__ h. Configure the I/O slot allocations so that the profile accurately recreates what you documented in a previous step of this exercise. Configure the slot that controls the DVD drive as a desired slot (that is., do not mark it as Required). This adapter is labeled Other Mass Storage Controller which is slot T12 on a p5-520. Below is an example of the I/O configuration screen where the T5, T7, T10, and T12 slots are configured. (Some systems will have the buses numbered differently.) To add slots, select them in the top window and click the Add as required or Add as desired button on the right. They will appear in the bottom window. Use the Add as desired button for the Other Mass Storage Controller.
5-11
Click on the Next button to advance to the next screen.
__ i.
Click the Next button on the I/O Pools screen.
__ j.
On the Virtual I/O Adapters screen, click the No button, and click Next.
__ k. Click the Next button on the Power Controlling Partitions screen.
__ l.
On the Optional Settings screen, configure your partition to automatically start with the managed system and leave the boot mode on Normal. Here is an example screen where the auto start option has been selected and the boot mode is set to Normal:
V3.1.0.1
EXempty
Click on the Next button to advance to the next screen. __ 13. The next screen is the Profile Summary. Check all of your configuration options, and if everything is correct, click the Finish button to create the partition. Here is an example Profile Summary screen:
5-13
__ 14. Check the HMC Server Management application to make sure the partition was created. You should see your new partition and its profile listed in the Server Management application. Here is an example:
__ 15. Manually activate the partition, and select the option to open a terminal window. Boot to SMS and select the boot device. Select the partition name, right click, and choose Activate on the popup menu. A new window will open. Click the box that says Open a terminal window or console session.
V3.1.0.1
EXempty
To boot a partition into SMS mode, click on the Advanced button. You can see this button in the screenshot below. In the Advanced window, override the boot mode and set it to SMS. Then click OK, and OK again, to activate the partition.
Once you are in SMS, select the boot disk (try the first adapter you find, and the first disk you find). Then exit the SMS menus. This will boot your partition.
__ 16. Once it is activated, shut down the partition. Login to the partition in a terminal window and use the shutdown -F command to shut it down.
__ 17. Coordinate with any other lab groups working on your managed system to power off the managed system. Power it off normally (not fast). Then power it on with the auto start power on option. Did your partition auto start? To power off the system, select the managed system name, right click and choose Power Off Managed System on the popup menu. Choose Normal power off in the window that opens. Then click the OK button. To power on the system, select the managed system name, right click and choose Power On on the popup menu. In the window that opens, choose the Partition auto start option, then click OK. Once the managed system reaches the Operating state, your partition should activate automatically.
__ 18. For the next exercise, you will need two running partitions on the managed system. If only one of the systems logical partitions has been recreated after initializing the managed system, create a second LPAR named LPAR2. Name its profile default. Use the same memory and processor configuration as LPAR1 and use the I/O slot configuration that you documented for LPAR2.
__ 19. Activate LPAR2 with an open terminal window to SMS and select the proper boot device. Make sure the partition boots successfully.
End of exercise
V3.1.0.1
EXempty
Exercise 6. Partition Operations

This exercise explores the operations involved in managing partitions including the activation and shutting down of partitions, the creation of system profiles, and backup and restore of profile data.

At the end of the lab, you should be able to: Activate and shut down partitions Modify, copy, and delete partition profiles Create, delete, copy, and activate system profiles Open and close terminal windows Backup and restore partition profile data Troubleshoot partition activation errors
Introduction
In this exercise, you will manage the partition operations of a managed system. Using the HMC, you will start and stop partitions, open virtual terminal windows, obtain current configuration information, use system profiles, and backup and restore partition profile data.
Requirements
This workbook A workstation with WebSM connected to a network A POWER5 processor-based managed system connected to the same network as the workstations A system from which to start an SSH session to the HMC
6-1

Preface
All exercises of this chapter depend on the availability of specific equipment in your classroom. Youll need: - A computer system with the WebSM client installed - A managed system configured with at least 2 partitions - A system from which to execute remote commands to the HMC (via SSH) - All lab systems need to be accessible to each other on a network. Hints are provided for lab exercises in case you need them and provide solutions for the lab exercise steps. All hints are marked by a sign.
Working with Partition Profiles

__ 1. Connect to the HMC using the WebSM client.
__ 2. Go to the Server Management application on the HMC.
__ 3. Copy the profile for your lab groups partition. Name the copy Alternate. To copy a profile, expand the partition information in the Server Management application. Select the profile name, right click, and choose Copy on the menu. In the window that opens, type Alternate for the new profile name.
__ 4. Alter this new profile so that the desired memory is 256 MB more than the current setting. Leave the minimum memory setting as it is. You may need to increase the maximum amount to be at least the desired amount. To alter a profile, select the profile, right click, and choose Properties on the menu. To alter the memory configuration, click on the Memory tab. Change the desired setting to 256 MB more than the current setting. If necessary, increase the maximum setting to a value at least as large as the desired setting.
__ 5. What is the default profile name for your running partition? The default partition profile has the icon with the check mark. It should be the profile named default.
6-2
V3.1.0.1
EXempty
__ 6. Change the default profile to the new Alternate profile. Select the partition name, right click, and choose the Change Default Profile option on the menu. In the window that pops up, use the pull down menu to change the default profile to the Alternate profile.
__ 7. What is the current memory overhead on your managed system? Select the managed system, and choose Properties on the menu. Click on the Memory tab. Subtract the Current memory available for partition usage from the total Configurable memory. For example, in this system shown in the following screen shot, the amount of memory overhead is 176 MB. (4096 MB - 3920 MB = 176 MB)
__ 8. Is there any Available memory? If so, document how much. On the Memory tab for the managed system properties, look at the Available memory field. In the example screen shown above, the amount is 336 MB. You can close the properties window.
6-3
Activating and Deactivating Partitions

__ 9. Using the WebSM interface to the HMC, check the state of your partition (or one of your partitions). How can you tell if its running? Look at the State column in the Server Management application on the HMC. The state of your partition will be Running if it is running.
If the partition is not running, continue to the next step. If the partition is running, stop it and close the terminal window if there is one. To stop a partition you can do one of the following: Login to the operating system running in the partition and initiate the proper operating system shut down command. This is the quickest way. In an AIX 5L partition, issue the shutdown -F command. You can shut down a partitions operating system from the HMC WebSM Server Management application by selecting the partition name, right clicking, and choosing Shut Down Partition on the popup menu. In the window that pops up, choose the Operating System option and click OK. You can use the HMC command chsysstate from an SSH session. For example: chsysstate -m managedsystemname -o osshutdown -r lpar \ -n lparname (where managedsystemname and lparname are the actual names. You can also add --immed for immediate shutdown.) To close the terminal window, click the X in the upper corner of the terminal window to close it.
__ 10. Using the HMC, activate your partition with the profile named default. Watch the partition state and when it is back to Running, you can move on to the next step. Select the partition name, right-click and choose Activate from the menu. Choose the profile named default and click OK.
__ 11. With the partition in the Running state, open a virtual terminal window. Attempt to open another terminal window. Did it allow you to? Why or why not? Select the partition name, right-click and choose Open Terminal Window from the menu. You can not have more than one open terminal window for a partition.
__ 12. At this point, your partition has been activated with the profile named default. Perform all of the steps required to result in the partition running with the profile called Alternate that you created in a previous step.
V3.1.0.1
EXempty
The steps are: Log in to the operating system and execute the operating system shut down command (shutdown). Once the partition state is Not Activated in the HMC interface, select the partition name, right-click and choose Activate from the menu. In the popup dialog box, select the Alternate profile, and click OK.
__ 13. Check the memory that was allocated to your partition and the available memory on the managed system. Is this what you expected? The partition should now have 256 MB more memory than it did before. To check this, select the managed system name, right click, and choose Properties on the popup menu. Go to the memory tab. The Available memory should have been reduced by 256 MB and the amount of memory for your partition should have been increased by 256 MB. Note that back in step 4, if you had increased the maximum amount of memory for the Alternate profile, then more memory might have been consumed for page tables, If so, you would see that the available memory for the managed system would be reduced by more than 256 MB.
__ 14. Stop your partition. login to the partition as the root user and issue the shutdown -F command. Alternatively, select the partition, right click, and choose the Shut Down Partition menu option.
__ 15. Schedule your partition to activate tomorrow, at any 10:00 AM. Once youve successfully scheduled this activation, delete this operation. To schedule an operation, on the HMC, go to the HMC Management application. From there choose the HMC Configuration application. Choose Schedule Operations from the list of options. Choose your partition name in the window that pops up. Click OK. On the Options menu, choose New. Choose the Activate on an LPAR option. Click OK. Choose tomorrows date and 10:00:00 AM. Click on the Options tab. Notice that you can choose the profile name. Click the Save button. Click OK on dialog window that tells you the operation was added.
6-5
To delete this operation, select it in the Customized Scheduled Operations window, and choose Delete from the Options menu. Click OK on the confirmation dialog window. You can now close out of the Customized Scheduled Operations window.
Using HMC Remote Commands for Partition Operations

__ 16. From an SSH session, use the HMC command to start your partition using the profile named default. What is the command that you used? HMC Command (Replace managedsystename and partitionname with the actual names.): chsysstate -r lpar -o on -m managedsystemname -n partitionname \ -f default The use of the backslash character in command examples means that the rest of the command wrapped to a second line. Replace the italicized items in the command with the actual names for the items on your system.
__ 17. Use the lssyscfg and lshwres HMC commands to find the information requested below. Use the --help option to each command to see syntax information. Write down the command that you used. __ a. List the names of all the partitions on a managed system. Here is the command: lssyscfg -r lpar -m managedsystemname -F name Example command and output on a system named sputnik: hscroot@sputnik-hmc:~> lssyscfg -r lpar -m sputnik -F name LPAR2 LPAR1
__ b. Use the HMC command to find out the state of your partition. What is the state? What is the command that you used? There are two ways to use the lssyscfg HMC command to find out the state of the partition. The first example below shows all partitions and their states. The second example below shows only the partition named LPAR2 by using a filter for the lpar_names field. In the example commands below, the name of the managed system is sputnik.
hscroot@sputnik-hmc:~> lssyscfg -r sputnik -m sputnik -F name,state --header
V3.1.0.1
EXempty
name,state LPAR2,Running LPAR1,Running hscroot@sputnik-hmc:~> lssyscfg -r lpar -m sputnik --filter \ "lpar_names=LPAR2" -F name,state --header name,state LPAR2,Running
__ c. List the names of all of the profiles for a particular partition by using a filter. In the following command, the partitions ID number is one. In the output below, it has two profiles, default and Alternate. lssyscfg -r prof -m managedsystemname \ --filter lpar_ids=1 -F name,lpar_name --header Example command and output on a system named sputnik: hscroot@sputnik-hmc:~> lssyscfg -r prof -m sputnik --filter \ "lpar_ids=1" -F name,lpar_name --header name,lpar_name default,LPAR1 Alternate,LPAR1
__ d. View the memory resources currently in use by the partitions. Here is the command: lshwres -m managedsystemname -r mem --level lpar \ -F lpar_name,run_mem --header Example command and output on a system named sputnik: hscroot@sputnik-hmc:~> lshwres -m sputnik -r mem --level lpar \ -F lpar_name,run_mem --header lpar_name,run_mem LPAR1,2048 LPAR2,1792
__ e. View the processor resources currently in use by the partitions. Here is the command:
6-7
lshwres -m managedsystemname -r proc --level lpar \ -F lpar_name,run_procs --header Example command and output on a system named sputnik: hscroot@sputnik-hmc:~> lshwres -m sputnik -r proc --level lpar -F lpar_name,run_procs --header lpar_name,run_procs LPAR1,1 LPAR2,1
__ f.
Find out the state of the managed system. Here is the command: lssyscfg -r sys -m managedsystemname -F state --header Example command and output on a system named sputnik: hscroot@sputnik-hmc:~> lssyscfg -r sys -m sputnik -F state --header state Operating
__ g. List all of the managed system names and their IP addresses that this HMC manages. What is the command that you used? Here is the command: lssyscfg -r sys -F name,ipaddr --header Example command and output: hscroot@sputnik-hmc:~> lssyscfg -r sys -F name,ipaddr --header name,ipaddr sputnik,192.168.255.254
Creating and Modifying System Profiles

__ 18. Create a system profile named Group# (where # is the number of your lab group). Add your Alternate partition profile for your partition to this system profile. If available, add the Alternate partition profile for another partition on your system.
6-8
V3.1.0.1
EXempty
In the Server Management application, select System Profiles, right click, and choose Create -> System Profile on the popup menu. In the window that pops up, enter Group# (where # is the number of your lab group) for the name of the system profile. Click on the expand icon next to your partition name in the left hand box. Click on the Alternate profile and click the Add >> button. This should add the partition name and its profile name to the System Profile box on the right. Then click the OK button to create the system profile. Heres an example of the System Profile window:
__ 19. Check the system profiles in the Server Management application to make sure your Group# system profile was created. Heres what you should see in the Server Management application under the System Profiles section:
__ 20. Validate the Group# system profile and resolve any conflicts. Select the Group# system profile name, right click, and choose Validate on the popup menu.
6-9
You should see a message that there are no resource conflicts.
__ 21. Copy the Group# system profile and call it DeleteMe# where # is the number of your lab group. Select the Group# system profile, right click, and choose Copy on the popup menu. In the window that pops up, enter DeleteMe#, where # is your lab group number. Click OK.
__ 22. Activate the Group# system profile. In the Activate System Profile window that pops up, choose to Validate the system profile before activation and to Continue to activate remaining partitions if activation failures occur. Then click the Continue button. What happens? Select the Group# system profile name, right click, and choose Activate on the popup menu. First an Activate System Profile window will pop up as seen below. Check both boxes.
What happens is that you will get a warning that your partition is running and will not be activated.
__ 23. Shut down your partition using the chsysstate HMC command. Watch the state column in the Server Management HMC application. When the state is Not Activated, continue to the next step.
V3.1.0.1
EXempty
Here is the syntax of the chsysstate HMC command to shutdown a partition. Replace managedsystemname with the actual managed system name and replace lparname with the actual name of the LPAR. chsysstate -m managedsystemname -o shutdown -r lpar \ -n lparname
__ 24. Activate your Group# system profile. Did your partition activate? Select the Group# system profile name, right click, and choose Activate on the popup menu. The partition should activate successfully.
Deleting Partitions, Partition Profiles, and System Profiles

__ 25. Delete the Alternate profile for your partition. Were you able to delete it? What must you do first before deleting this profile? Your partition should be running using the Alternate partition profile as specified in your System Profile. You cannot delete a profile that was last used to activate a running partition. Shutdown the partition first. Second, you cannot delete a partition profile which is the default profile. If the profile named Alternate is still the default, make the profile named default the default profile. Then, select the Alternate partition profile name, right click, and choose Delete on the popup menu.
__ 26. Check the Group# system profile. Is the deleted partition profile (Alternate) in the Group# system profile? Select the Group# system profile, right click, and choose Properties on the popup menu. Your partition and its Alternate profile should no longer be listed in the System Profile.
__ 27. Delete your Group# and DeleteMe# system profiles. Select the system profile name, right click, and choose Delete on the popup menu. A window will popup and ask you to confirm. Click OK.
Backing Up and Restoring Partition Profile Data

Copyright IBM Corp. 2004, 2007 Exercise 6. Partition Operations 6-11
WARNING: The Profile Data menu that you will use in this section contains an option called Initialize. Do not use this Initialize option. When you initialize profile data, you return the HMCs partition profile data to its original (unconfigured) state. All profiles on the HMC are deleted if you perform this task. The rest of the HMC configuration settings, such as its network configuration and users, are not affected. STOP: Did you read the warning above? __ 28. Make sure that the managed system has one extra partition that you do not need. You may have to quickly create one extra partition. Create a partition by selecting the managed system name, right clicking, and choosing Create -> Logical Partition on the menu. Give your partition and its profile a name. On the Virtual I/O Adapters screen be sure to check the No option. All of the other screens you can just click through using the defaults. You wont be activating this partition so it doesnt matter what configuration you give it.
__ 29. Backup the LPAR configuration data. Select the managed system name, right click, and choose Profile Data -> Backup on the popup menu. In the window that appears, type in a name for your backup and click OK.
__ 30. Delete the non-essential partition that you just created. Select the partition name, right click, and choose Delete on the popup menu. Click OK in the window that pops up.
__ 31. Restore the LPAR configuration data using the Backup priority option. You may perform this step only if all of the lab groups work together, or if your lab group is the only one working on the managed system. Once the profile data is restored, check the list of partitions in the Server Management application. Is your deleted partition back in the list? It should be. Select the managed system name, right click, and choose Profile Data -> Restore on the popup menu. In the Profile Data Restore window that pops up, select your backup file name. Select the Backup priority option then click OK. Heres an example of this Profile Data Restore window.
V3.1.0.1
EXempty
__ 32. Login to the HMC command line and list out the detailed contents of the /var/hsc/profiles/* directory. The backup files are stored underneath a subdirectory named after the serial number for the managed system. Check the timestamp of the backup file that you created and the backupFile file. In the following example, the Group1 backup file has a time of 21:57 and a date of Oct 19th. hscroot@sputnik-hmc:~> ls -l /var/hsc/profiles/* /var/hsc/profiles/062A87G: total 96 -rw-r--r-- 1 root root 32768 2006-10-19 22:00 backupFile -rw-r--r-- 1 root root 32768 2006-10-19 21:57 Group1 -rw-r--r-- 1 root root 32768 2006-10-06 14:07 OriginalConfig
__ 33. Make a change in a partitions profile and save it. Then check the time stamp again on the backupFile file. It should have changed. Using the same example as in the last step, look at the timestamp for the backupFile file as shown below. Noticed that it changed when you changed the profile. hscroot@sputnik-hmc:~> ls -l /var/hsc/profiles/* /var/hsc/profiles/062A87G: total 96
-rw-r--r-- 1 root root 32768 2006-10-19 22:10 backupFile -rw-r--r-- 1 root root 32768 2006-10-19 21:57 Group1 -rw-r--r-- 1 root root 32768 2006-10-06 14:07 OriginalConfig
__ 34. Delete your backup file using the HMC Server Management application. Select the managed system name, right click, and choose Profile Data -> Remove on the popup menu. In the window that pops up, select the backup filename, and click OK.
__ 35. Delete the non-essential partition that was restored from your backup file.
Utilization Data Management

__ 36. Enable your managed system to collect utilization data management information. If it is already enabled, leave the configuration as it is and click Cancel to close the window. If you enabled the data collection, you may need to wait a few minutes before continuing to the next step to view the data. On the HMC, go to the Utilization Data Management application which is under Server and Partition. Click on the Change Settings for Utilization Data Collection task. Click on All Managed Systems or click on Select from the following, then select the managed system and click the Enable checkbox. Then click OK. Here is an example:
V3.1.0.1
EXempty
__ 37. Next, youll view the data. Go to the Utilization Data Management application, click on the View Utilization Data task. In the window that pops up, use the pull down menu at the top to choose the name of your managed system. Then, notice the Beginning time/date: input box and the Ending time/date: input box. The beginning time and date will be 24 hours before the ending time/date. You can leave it as is, or change the time and date. Click OK when youre done. Here is an example View Events window:
__ 38. A window will popup with a list of events. Events are state changes or System Pool/Lpar Samplings which give resource utilization data. Here is an example of a Utilization Events listing:
__ 39. To view more detail, select an event and click OK. If you have a state change type of event in your Utilization Events window, select one of these to see more detail. Then click OK to close the window. Heres an example of a state change event properties window:
__ 40. Now well look at resource utilization data. In the Utilization Events window, select one of the System/Pool/Lpar Sampling events. Click OK. Here is an example of what you might see:
__ 41. Notice in the example screen above (in the previous step), that the Sample type is System. Change this to a sample type of LPAR. Use the View menu in the upper left corner to change the sample type:
V3.1.0.1
EXempty
__ 42. Look at the available LPAR sample data. Notice the processor configuration information that is displayed. Here is an example of LPAR utilization data. In this window, we can see two LPARs and their processor configuration.
__ 43. Now change the view to Pool and look at the information shown. This course has not yet covered the description of the shared processing pool. This data will make more sense later after the Advanced Processor Options unit is covered. Here is an example of Pool utilization data:
__ 44. Close all Utilization Data Management windows and notify your instructor that you have completed the exercise.
End of exercise
6-17
V3.1.0.1
EXempty
Exercise 7. Dynamic Logical Partitioning

The objective of this lab exercise is to provide hands-on experience for dynamically adding, removing, and moving resources to and from logical partitions on IBM POWER5 processor-based systems. Students will also use commands to verify and troubleshoot DLPAR operations.

At the end of the lab, you should be able to: Dynamically remove, add, and move processors, memory, and I/O slots to and from logical partitions Perform AIX operations to remove and add devices in a partition to support dynamic LPAR operations Verify that DLPAR function is operational
Introduction
In this exercise, you will manage the movement of resources dynamically between partitions on a managed system. You will use the HMC graphical interface and HMC commands to complete the tasks.
Requirements
7-1

Preface
All exercises of this chapter depend on the availability of specific equipment in your classroom. You will need: - A computer system connected to the World Wide Web and a Web browser - A managed system configured with at least 2 partitions - 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 lab exercises in case you need them, and provide solutions for the lab exercise steps. All hints are marked by a sign.
Lab Exercise for Topic 1 Dynamic LPAR Operations

This section will explore the dynamic movement of resources to and from partitions. After each operation, check the managed system properties to verify the movement of resources. If any dynamic operations will affect a partition that belongs to a different lab group be sure to first notify them before acting. The managed system should be powered on in the Operating state. The partitions must be running. If the partitions or the HMC were just rebooted, you will need to wait up to 5-7 minutes before attempting any DLPAR operations. __ 1. Log on to the HMC GUI either from the HMC itself or from the WebSM application on your student workstation.
__ 2. One of the partitions will be assigned to your lab group. Can you tell which partition profile your partition is currently using? Select the partition name and go to its property sheet. Go to the General tab and look for the line that lists the Current Profile. You can also expand the partition information in the Server Management application. The profile that was used will have Last Activated in the State column.
__ 3. If your partition is using dedicated processors, change it to use 0.8 shared processing units. Now that you know the active profile, select this profile name, right-click, and choose Properties on the menu.
7-2
V3.1.0.1
EXempty
Go to the Processors tab. If the partition is using dedicated processors, change it to shared. Set the desired processing units amount to 0.8. Re-activate the partition.
__ 4. Check to see if the managed system has any free resources. What did you do to find this out? From the Server Management application, select the managed system name, right-click the mouse button and choose Properties from the popup menu. Go to the Processors, I/O, and Memory tabs and see if there are any free resources. For example, in the graphic below, you can see that there is 1344 MB of available memory:
7-3
On the Processors tab, on this example system, you can see that there are 0.4 processing units available:
7-4
V3.1.0.1
EXempty
On the I/O tab, look for the word Unassigned in the Owner column (ignore the I/O Pool ID column). In the following example we see that slots C3, C4, C5, and C6 are not currently assigned to any partitions:
__ 5. In this step, you will perform processor DLPAR operations. __ a. If your system has free processing units, dynamically add 0.1 processing units to your partition. If your system does not have free processing units, go to step 5c below. In the Server Management application, select your group's partition name. Right-click and choose Dynamic Logical Partitioning -> Processor Resources -> Add on the menu. Enter 0.1 in the units to add box and click OK.
__ b. Watch the progress on the HMC interface. When the processing units have been successfully added, check the managed system properties screen (on the Processors tab) to see that the processing resources were added.
7-5
__ c. Remove 0.1 processing units from your partition. In the Server Management application, select your group's partition name. Right-click and choose Dynamic Logical Partitioning -> Processor Resources -> Remove on the menu. Enter 0.1 in the units to remove box and click OK.
__ d. Move 0.1 processing units to another partition, if possible. In the Server Management application, select your group's partition name. Right-click and choose Dynamic Logical Partitioning -> Processor Resources -> Move on the menu.
__ 6. In this step, you will perform a memory DLPAR operation. Move one LMB of memory from your partition to another partition. Verify that the memory was moved and then move the LMB back to your partition. In the Server Management application, select your group's partition name. Right-click and choose Dynamic Logical Partitioning -> Memory Resources -> Move on the menu. To put the memory back, select the other partition first, then go to the same menu option (Dynamic Logical Partitioning -> Memory Resources -> Move).
__ 7. In this step, you will perform I/O slot DLPAR operations. __ a. Select your partition and choose Dynamic Logical Partitioning -> Physical Adapter Resources -> Add from the menu. Choose an empty slot (if available) from the list, then click OK.
__ b. If the slots we added actually contained adapters, what would you need to do now so that AIX would recognize the new devices? You need to execute the cfgmgr command. The lsdev -C command will let you see the new devices.
__ c. In the Dynamic Logical Partitioning -> Physical Adapter Resources -> Remove screen, notice the list that is shown. The HMC will not allow you to remove I/O slots that are listed as required for your partition. Remove one of the I/O slots that you added in the last step.
7-6
V3.1.0.1
EXempty
Using HMC Commands from a Secure Shell for DLPAR

Use SSH to log in to the HMC and try out these HMC commands to remotely check the processor, memory, and I/O slot resources for your partitions and perform DLPAR operations. Use lshwres --help or chhwres --help for usage information. __ 8. List the available processor information for the LPARs on the managed system. Notice the various fields. lshwres -m managedsystemname -r proc --level lpar Here is sample output for a managed system named sputnik: hscroot@sputnik-hmc:~> lshwres -m sputnik -r proc --level lpar lpar_name=LPAR1,lpar_id=1,curr_shared_proc_pool_id=0,curr_proc_m ode=shared,curr_min_proc_units=0.1,curr_proc_units=0.7,curr_max_ proc_units=2.0,curr_min_procs=1,curr_procs=1,curr_max_procs=2,cu rr_sharing_mode=cap,curr_uncap_weight=0,pend_shared_proc_pool_id =0,pend_proc_mode=shared,pend_min_proc_units=0.1,pend_proc_units =0.7,pend_max_proc_units=2.0,pend_min_procs=1,pend_procs=1,pend_ max_procs=2,pend_sharing_mode=cap,pend_uncap_weight=0,run_proc_u nits=0.7,run_procs=1,run_uncap_weight=0 lpar_name=LPAR2,lpar_id=2,curr_shared_proc_pool_id=0,curr_proc_m ode=shared,curr_min_proc_units=0.1,curr_proc_units=0.9,curr_max_ proc_units=1.0,curr_min_procs=1,curr_procs=1,curr_max_procs=2,cu rr_sharing_mode=uncap,curr_uncap_weight=128,pend_shared_proc_poo l_id=0,pend_proc_mode=shared,pend_min_proc_units=0.1,pend_proc_u nits=0.9,pend_max_proc_units=1.0,pend_min_procs=1,pend_procs=1,p end_max_procs=2,pend_sharing_mode=uncap,pend_uncap_weight=128,ru n_proc_units=0.9,run_procs=1,run_uncap_weight=128
__ 9. To list just a few of the fields, try this command: lshwres -m managedsystemname -r proc --level lpar \ -F lpar_name,curr_proc_units --header You may try different field names with the -F option to produce a custom report. Here is sample output for a managed system named sputnik: hscroot@sputnik-hmc:~> lshwres -m sputnik -r proc --level lpar \ -F lpar_name,curr_proc_units --header lpar_name,curr_proc_units LPAR1,0.7 LPAR2,0.9
7-7
__ 10. List available memory and I/O information with the following commands. Note the value of the cur_mem field for all partitions for use in a future step. lshwres -m managedsystemname -r mem --level lpar lshwres -m managedsystemname -r io --rsubtype slot Here is sample output for a managed system named sputnik for these two commands: hscroot@sputnik-hmc:~> lshwres -m sputnik -r mem --level lpar lpar_name=LPAR1,lpar_id=1,curr_min_mem=512,curr_mem=1280,curr_ma x_mem=2048,pend_min_mem=512,pend_mem=1280,pend_max_mem=2048,run_ min_mem=512,run_mem=1280,curr_min_num_huge_pages=0,curr_num_huge _pages=0,curr_max_num_huge_pages=0,pend_min_num_huge_pages=0,pen d_num_huge_pages=0,pend_max_num_huge_pages=0,run_num_huge_pages= 0,curr_bsr_arrays=null lpar_name=LPAR2,lpar_id=2,curr_min_mem=512,curr_mem=1296,curr_ma x_mem=2048,pend_min_mem=512,pend_mem=1296,pend_max_mem=2048,run_ min_mem=512,run_mem=1296,curr_min_num_huge_pages=0,curr_num_huge _pages=0,curr_max_num_huge_pages=0,pend_min_num_huge_pages=0,pen d_num_huge_pages=0,pend_max_num_huge_pages=0,run_num_huge_pages= 0,curr_bsr_arrays=null hscroot@sputnik-hmc:~> lshwres -m sputnik -r io --rsubtype slot unit_phys_loc=U787F.001.DPM166X,bus_id=2,phys_loc=C4,drc_index=2 1010002,lpar_id=none,slot_io_pool_id=none,description=Empty slot ,"feature_codes=0,0,0",pci_vendor_id=FFFF,pci_device_id=FFFF,pci _subs_vendor_id=FFFF,pci_subs_device_id=FFFF,pci_class=FFFF,pci_ revision_id=FF,bus_grouping=0,iop=0,parent_slot_drc_index=none,d rc_name=U787F.001.DPM166X-P1-C4 unit_phys_loc=U787F.001.DPM166X,bus_id=3,phys_loc=T12,drc_index= 21010003,lpar_name=LPAR1,lpar_id=1,slot_io_pool_id=none,descript ion=Other Mass Storage Controller,feature_codes=none, pci_vendor_id=105A,pci_device_id=1275,pci_subs_vendor_id=105A,pc i_subs_device_id=1275,pci_class=0180,pci_revision_id=01,bus_grou ping=0,iop=0,parent_slot_drc_index=none,drc_name=U787F.001.DPM16 6X-P1-T12 unit_phys_loc=U787F.001.DPM166X,bus_id=3,phys_loc=T10,drc_index= 21020003,lpar_name=LPAR1,lpar_id=1,slot_io_pool_id=none,descript ion=SCSI bus controller,feature_codes=none,pci_vendor_id=1069,pc i_device_id=B166,pci_subs_vendor_id=1014,pci_subs_device_id=02D3 ,pci_class=0100,pci_revision_id=04,bus_grouping=0,iop=0,parent_s lot_drc_index=none,drc_name=U787F.001.DPM166X-P1-T10
7-8
V3.1.0.1
EXempty
unit_phys_loc=U787F.001.DPM166X,bus_id=3,phys_loc=C3,drc_index=2 1030003,lpar_id=none,slot_io_pool_id=none,description=Empty slot,"feature_codes=0,0,0",pci_vendor_id=FFFF,pci_device_id=FFFF ,pci_subs_vendor_id=FFFF,pci_subs_device_id=FFFF,pci_class=FFFF, pci_revision_id=FF,bus_grouping=0,iop=0,parent_slot_drc_index=no ne,drc_name=U787F.001.DPM166X-P1-C3 unit_phys_loc=U787F.001.DPM166X,bus_id=3,phys_loc=C5,drc_index=2 1040003,lpar_id=none,slot_io_pool_id=none,description=Empty slot,"feature_codes=0,0,0",pci_vendor_id=FFFF,pci_device_id=FFFF ,pci_subs_vendor_id=FFFF,pci_subs_device_id=FFFF,pci_class=FFFF, pci_revision_id=FF,bus_grouping=0,iop=0,parent_slot_drc_index=no ne,drc_name=U787F.001.DPM166X-P1-C5 unit_phys_loc=U787F.001.DPM166X,bus_id=3,phys_loc=C6,drc_index=2 1050003,lpar_id=none,slot_io_pool_id=none,description=Empty slot,"feature_codes=0,0,0",pci_vendor_id=FFFF,pci_device_id=FFFF ,pci_subs_vendor_id=FFFF,pci_subs_device_id=FFFF,pci_class=FFFF, pci_revision_id=FF,bus_grouping=0,iop=0,parent_slot_drc_index=no ne,drc_name=U787F.001.DPM166X-P1-C6 unit_phys_loc=U787F.001.DPM166X,bus_id=4,phys_loc=T7,drc_index=2 1010004,lpar_name=LPAR1,lpar_id=1,slot_io_pool_id=none,descripti on=Universal Serial Bus UHC Spec,feature_codes=none,pci_vendor_i d=1033,pci_device_id=0035,pci_subs_vendor_id=1033,pci_subs_devic e_id=0035,pci_class=0C03,pci_revision_id=43,bus_grouping=0,iop=0 ,parent_slot_drc_index=none,drc_name=U787F.001.DPM166X-P1-T7 unit_phys_loc=U787F.001.DPM166X,bus_id=4,phys_loc=T5,drc_index=2 1020004,lpar_name=LPAR1,lpar_id=1,slot_io_pool_id=none,descripti on=PCI 10/100/1000Mbps Ethernet UTP 2-port,"feature_codes=5706,5 706,5706",pci_vendor_id=8086,pci_device_id=1079,pci_subs_vendor_ id=1014,pci_subs_device_id=0289,pci_class=0200,pci_revision_id=0 3,bus_grouping=0,iop=0,parent_slot_drc_index=none,drc_name=U787F .001.DPM166X-P1-T5 unit_phys_loc=U787F.001.DPM166X,bus_id=4,phys_loc=C1,drc_index=2 1030004,lpar_name=LPAR2,lpar_id=2,slot_io_pool_id=none,descripti on=SCSI bus controller,feature_codes=none,pci_vendor_id=1014,pci _device_id=028C,pci_subs_vendor_id=1014,pci_subs_device_id=02C0, pci_class=0100,pci_revision_id=11,bus_grouping=0,iop=0,parent_sl ot_drc_index=none,drc_name=U787F.001.DPM166X-P1-C1 unit_phys_loc=U787F.001.DPM166X,bus_id=4,phys_loc=C2,drc_index=2 1040004,lpar_name=LPAR2,lpar_id=2,slot_io_pool_id=none,descripti on=PCI 1Gbps Ethernet UTP,"feature_codes=5701,5701,5701",pci_ven dor_id=8086,pci_device_id=1026,pci_subs_vendor_id=1014,pci_subs_ device_id=0269,pci_class=0200,pci_revision_id=04,bus_grouping=0, iop=0,parent_slot_drc_index=none,drc_name=U787F.001.DPM166X-P1-C 2
7-9
__ 11. There is a lot of information when listing the slot rsubtype, so try this command which lists just a few of the fields. lshwres -m managedsystemname -r io --rsubtype slot \ -F lpar_name,description,drc_name --header Here is sample output for a managed system named sputnik: hscroot@sputnik-hmc:~> lshwres -m sputnik -r io --rsubtype \ slot -F lpar_name,description,drc_name --header lpar_name,description,drc_name null,Empty slot,U787F.001.DPM166X-P1-C4 LPAR1,Other Mass Storage Controller,U787F.001.DPM166X-P1-T12 LPAR1,SCSI bus controller,U787F.001.DPM166X-P1-T10 null,Empty slot,U787F.001.DPM166X-P1-C3 null,Empty slot,U787F.001.DPM166X-P1-C5 null,Empty slot,U787F.001.DPM166X-P1-C6 LPAR1,Universal Serial Bus UHC Spec,U787F.001.DPM166X-P1-T7 LPAR1,PCI 10/100/1000Mbps Ethernet UTP 2-port,U787F.001.DPM166X-P1-T5 LPAR2,SCSI bus controller,U787F.001.DPM166X-P1-C1 LPAR2,PCI 1Gbps Ethernet UTP,U787F.001.DPM166X-P1-C2
__ 12. Dynamically move 16 MB (or one LMB) from your partition to another partition with this command: chhwres -r mem -o m -p sourcepartition \ -t destinationpartition -m managedsystemname -q 16 -w 0 Here is an example of a command which moves 16 MB from LPAR1 to LPAR2 on the sputnik managed system: hscroot@sputnik-hmc:~> chhwres -r mem -o m -p LPAR1 -t LPAR2 \ -m sputnik -q 16 -w 0
__ 13. Check that the memory was moved with the lshwres command. The command syntax is: lshwres -m managedsystemname -r mem --level lpar Example output for a managed system named sputnik:
V3.1.0.1
EXempty
hscroot@sputnik-hmc:~> lshwres -m sputnik -r mem --level lpar lpar_name=LPAR1,lpar_id=1,curr_min_mem=512,curr_mem=1264,curr_ma x_mem=2048,pend_min_mem=512,pend_mem=1264,pend_max_mem=2048,run_ min_mem=512,run_mem=1264,curr_min_num_huge_pages=0,curr_num_huge _pages=0,curr_max_num_huge_pages=0,pend_min_num_huge_pages=0,pen d_num_huge_pages=0,pend_max_num_huge_pages=0,run_num_huge_pages= 0,curr_bsr_arrays=null lpar_name=LPAR2,lpar_id=2,curr_min_mem=512,curr_mem=1312,curr_ma x_mem=2048,pend_min_mem=512,pend_mem=1312,pend_max_mem=2048,run_ min_mem=512,run_mem=1312,curr_min_num_huge_pages=0,curr_num_huge _pages=0,curr_max_num_huge_pages=0,pend_min_num_huge_pages=0,pen d_num_huge_pages=0,pend_max_num_huge_pages=0,run_num_huge_pages= 0,curr_bsr_arrays=null In the output above, LPAR1 has 1264 MB of memory and LPAR2 has 1312 MB of memory. Depending on which partitions you were using as source and targets, the amount should be 16 MB different from the last time you checked.
__ 14. Using the HMC GUI, schedule a DLPAR operation to add one LMB of memory tomorrow (at any time) to your partition. In the HMC GUI, go to the HMC Management application. Then go to the HMC Configuration application. Click Schedule operations. In the window that pops up, select your partition name, such as in this example, and click the OK button at the bottom.
In the next window to pop up, go to the menu bar and pull down the Options menu. Choose the New option. In the next window, select Dynamic Reconfiguration, then click OK. Here is an example:
7-11
Another window will open and you should be on the Date and Time tab. Select a time tomorrow for the operation. Here is an example:
If you want, click the Repeat tab and enter anything you wish.
V3.1.0.1
EXempty
Then, on the Options tab, choose Memory for the resource, Add for the operation, and 16 MB for the amount. Then click the Save button. For example:
__ 15. Once you create your scheduled operation and click the Save button, then you should return to the Customize Scheduled Operations window and you will see your operation listed. Check to make sure it was added, then select it and delete it. For example:
7-13
__ 16. Let your instructor know when you have completed the lab exercise for this topic.
V3.1.0.1
EXempty
Lab Exercise for Topic 2 DLPAR Troubleshooting

This portion of the lab exercise goes with the Topic 2 lecture materials. You should not proceed if your instructor has not covered the Topic 2 presentation. __ 17. Log in to the HMC GUI and ping your LPAR to check connectivity. In the HMC GUI, go to the HMC Management application, then the HMC Configuration application, and choose Test Network Connectivity from the list of options. A pop-up window will appear. Type in the IP address of your LPAR and see if the ping is successful. If the ping is successful, the Working window will report a success. Here is an example of the ping (Test Network Connectivity) option:
__ 18. Log in to your partition and verify that the RMC daemons are running. Use the command lssrc -g rsct_rm Here is the command with example output: # lssrc -g rsct_rm Subsystem Group IBM.ERRM rsct_rm IBM.HostRM rsct_rm IBM.CSMAgentRM rsct_rm
PID 221312 250012 159868
Status active active active

7-15
IBM.AuditRM IBM.DRM IBM.ServiceRM IBM.LPRM
rsct_rm rsct_rm rsct_rm rsct_rm
241804 237716 184388 233636
active active active active
Alternately, you can use the ps -ef | grep rsct or lssrc -a | grep rsct commands.
__ 19. What command do you use to see if the partitions RMC subsystem knows the IP address of the HMC? Run the command on your partition. The command is lsrsrc IBM.ManagementServer Here is sample output where the HMC has an IP address of 9.47.88.170: # lsrsrc IBM.ManagementServer Resource Persistent Attributes for IBM.ManagementServer resource 1: Name = "9.47.88.170" Hostname = "9.47.88.170" ManagerType = "HMC" LocalHostname = "9.47.88.171" ClusterTM = "9078-160" ClusterSNum = "" ActivePeerDomain = "" NodeNameList = {"sputnik171.beaverton.ibm.com"}
__ 20. Stop the RMC daemons in your partition. To stop the RMC daemons use this command: # /usr/sbin/rsct/bin/rmcctrl -z
__ 21. Try to use DLPAR to remove one LMB of memory. What happens? When the RMC daemons are stopped, go to the HMCs Server Management application, select your group's partition name. Right-click and choose Dynamic Logical Partitioning -> Memory Resources -> Remove on the menu. Fill in 16 MB (if that is your LMB size) as the amount. You may have to wait a few minutes for the error window. Eventually you should receive an error such as this one:
V3.1.0.1
EXempty
__ 22. Start the RMC daemons on the LPAR. Immediately after you run the command to start the RMC daemons, attempt the memory remove operation again. If you get an error (some lab groups will and some will not), wait a few minutes and try again. Make sure DLPAR is operational before proceeding to the next step. To start the RMC daemons run the following commands: # /usr/sbin/rsct/bin/rmcctrl -A # /usr/sbin/rsct/bin/rmcctrl -p Once you run those commands, go to the HMCs Server Management application, select your group's partition name. Right-click and choose Dynamic Logical Partitioning -> Memory Resources -> Remove on the menu. Fill in 16 MB (if that is your LMB size) as the amount. You may have to wait a few minutes for either the error window or the success message.
__ 23. Log in to the HMC command line. What command can you use to verify that the HMC is ready for DLPAR? The command is lspartition -dplar Here is example output: hscroot@sputnik-hmc:~> lspartition -dlpar <#0> Partition:<1*9131-52A*062A87G, sputnik171.beaverton.ibm.com, 9.47.87.171> Active:<1>, OS:<AIX, 5.3>, DCaps:<0x3f>, CmdCaps:<0xb, 0xb>, PinnedMem:<198> <#1> Partition:<2*9131-52A*062A87G, sputnik172.beaverton.ibm.com, 9.47.87.172>
Copyright IBM Corp. 2004, 2007 Exercise 7. Dynamic Logical Partitioning 7-17
Active:<1>, OS:<AIX, 5.3>, DCaps:<0x3f>, CmdCaps:<0xb, 0xb>, PinnedMem:<183>
End of exercise
V3.1.0.1
EXempty
Exercise 8. Advanced Processor Concepts

This lab covers configuring subprocessor allocations and the configuration options associated with shared processors.

At the end of the lab, you should be able to: Configure a Micro-Partition with sub-processor entitled capacity Configure virtual processors Enable and disable SMT on AIX 5L V5.3 Configure capped and uncapped partitions View advanced processor related information with lparstat
Introduction
In this exercise you will configure the advanced processor options for AIX 5L partitions.
Requirements
This workbook A workstation with WebSM connected to a network. A POWER5 processor-based managed system connected to the same network as the workstations
8-1

Preface
All exercises of this chapter depend on the availability of specific equipment in your classroom. You will need a computer system connected to the World Wide Web and a Web browser. You will also need a POWER5 processor-based managed system capable of running LPARs. All lab systems need to be accessible to each other on a network. Hints are provided for lab exercises in case you need them and provide solutions for the lab exercise steps. All hints are marked by a sign.
View System Configuration and Enable/Disable SMT

__ 1. Log in to your partition 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. This example output assumes that in the last exercise for Dynamic Logical Partitioning that you changed your partition from using dedicated processors to using shared processors. # lparstat System configuration: type=Shared mode=Capped smt=On lcpu=2 mem=1264 psize=2 ent=0.70 %user %sys %wait %idle physc %entc lbusy vcsw phint ----- ---- ----- ----- ----- ----- ------ ---- ----0.0 0.0 0.1 99.9 0.00 0.0 0.2 3567515 2162 Based on the above output the answers to the above questions are: Type of processors: Shared Processor mode: Capped SMT: On (enabled)
V3.1.0.1
EXempty
Number of logical CPUs: 2
__ 2. Run the command that is used to view the state of simultaneous multi-threading. Is simultaneous multi-threading enabled in your partition? Here is an example smtctl command and its output. It shows that simultaneous multi-threading is enabled, which should be the case in your partition. # smtctl This system is SMT capable. SMT is currently enabled. SMT boot mode is set to disabled. SMT threads are bound to the same virtual processor. proc0 has 2 SMT threads. Bind processor 0 is bound with proc0 Bind processor 1 is bound with proc0
__ 3. If SMT is enabled, disable it. Check the lparstat command and the smtctl command again to make sure it is disabled. What is the number of logical CPUs now? Enable simultaneous multi-threading again. Use smtctl -m off to disable simultaneous multi-threading. Here is an example lparstat command and its output. It shows that simultaneous multi-threading is now off and the number of logical CPUs is one. # lparstat System configuration: type=Shared mode=Capped smt=Off lcpu=1 mem=1264 psize=2 ent=0.70 %user %sys %wait %idle physc %entc lbusy vcsw phint ----- ---- ----- ----- ----- ----- ------ ---- ----0.0 0.0 0.1 99.9 0.00 0.0 0.2 1045604650 2197 Here is an example smtctl command and its output. It shows that SMT is disabled. # smtctl
8-3
This system is SMT capable. SMT is currently disabled. SMT boot mode is set to disabled. SMT threads are bound to the same virtual processor. proc0 has 1 SMT threads. Bind processor 0 is bound with proc0 The number of logical CPUs should now be one. Use smtctl -m on to enable simultaneous multi-threading.
Configure Shared Processors

__ 4. Shut down your partition. Log in to your partition and issue the shutdown -F command.
__ 5. Alter the profile named default for your partition so that it has 0.8 desired processing units. (It may already be set to 0.8 from the last exercise.) Set the minimum to 0.6 and the maximum to 1.0. To change the partition profile, go to the Server Management application on the HMC. Expand the partition information, select your partitions profile name (default), right-click, and choose Properties on the menu. Click the Processors tab in the Logical Partition Profile Properties window that pops up. In the Processing mode box, make sure the Shared radio button is selected. In the Processing units box, enter 0.6 for minimum, 0.8 for the desired, and 1.0 for the maximum parameters. Do not click the OK button yet. You will do this after Step 7 below.
__ 6. Set the virtual processor maximum setting to the maximum allowed for the maximum number of processing units configured in your partition. On this same Processors tab you used in the last step, enter the value of 10 for the maximum virtual processors. The maximum virtual processors allowed is ten times the processing units.
__ 7. Set the sharing mode to uncapped and set the weight to 100.
8-4
V3.1.0.1
EXempty
On this same Processors tab you used in the last step, click the Uncapped check box and enter the value of 100 in the Weight box. Your Processors tab should now look like the example below. When you have finished configuring the shared processors, click the OK button at the bottom of the screen. This will apply your changes to the profile and close the window.
__ 8. Activate the partition and open a terminal window to it. To activate the partition, select the partition name (or the profile name), right-click, and choose Activate on the pop-up menu. On the screen that pops up, if there is not a terminal window already for this partition, click the Open a terminal window or console session check box, then click OK.
8-5
__ 9. Log in to the partition. Use the lparstat command to examine the current configuration. The output of lparstat should reflect the changes you made in the partition profile. Here is an example lparstat command and its output that shows the new processor settings. # lparstat System configuration: type=Shared mode=Uncapped smt=On lcpu=2 mem=1024 psize=2 ent=0.80 %user %sys %wait %idle physc %entc lbusy vcsw phint ----- ---- ----- ----- ----- ----- ------ ---- ----0.0 0.0 13.5 86.5 0.00 0.0 7.2 359374 39
__ 10. Log in to the HMC using SSH and use the lshwres command to view the processor settings for your partition. Notice the new processor settings. The command is: lshwres -r proc -m managedsystemname --filter "lpar_names=lparname" --level lpar Here is an example command and its output for the managed system named sputnik and a partition named LPAR1: hscroot@sputnik-hmc:~> lshwres -r proc -m sputnik --filter \ "lpar_names=LPAR1" --level lpar lpar_name=LPAR1,lpar_id=1,curr_shared_proc_pool_id=0,curr_proc_m ode=shared,curr_min_proc_units=0.6,curr_proc_units=0.8,curr_max_ proc_units=1.0,curr_min_procs=1,curr_procs=1,curr_max_procs=10,c urr_sharing_mode=uncap,curr_uncap_weight=100,pend_shared_proc_po ol_id=0,pend_proc_mode=shared,pend_min_proc_units=0.6,pend_proc_ units=0.8,pend_max_proc_units=1.0,pend_min_procs=1,pend_procs=1, pend_max_procs=10,pend_sharing_mode=uncap,pend_uncap_weight=100, run_proc_units=0.8,run_procs=1,run_uncap_weight=100
Dynamic Operations with Shared Processors

__ 11. Use the Dynamic Logical Partitioning menu options to perform the following steps. __ a. Remove 0.1 processing units from your partition. Do not change any other parameters. Did this work?
8-6
V3.1.0.1
EXempty
To perform the DLPAR operation, select the partition name in the Server Management application on the HMC. Choose the Dynamic Logical Partitioning -> Processor Resources -> Remove menu options. In the window that opens up, enter 0.1 in the Processing units to remove box near the bottom of the screen. Click the OK button. This should succeed.
__ b. Watch the progress on the HMC interface. When the command has completed, use lparstat from the partition to check to verify that 0.1 processing units were removed. You can use lparstat to see if the processing units were removed. The output of this lparstat command shows that the entitled capacity (ent) is now 0.7 and this should match your partition: # lparstat
8-7
System configuration: type=Shared mode=Uncapped smt=On lcpu=2 mem=1024 psize=2 ent=0.70 %user %sys %wait %idle physc %entc lbusy vcsw phint ----- ---- ----- ----- ----- ----- ------ ---- ----0.0 0.0 3.8 96.2 0.00 0.0 2.2 419903 66
__ c. Add 0.1 processing units back to your partition. Use lparstat to check the configuration. To perform the DLPAR operation, select the partition name in the Server Management application on the HMC. Choose the Dynamic Logical Partitioning -> Processor Resources -> Add menu options. In the window that opens up, enter 0.1 (or .1) in the Processing units to add box near the bottom of the screen. Click the OK button. This should succeed.
8-8
V3.1.0.1
EXempty
In your partitions terminal window, type lparstat. You should now see the ent parameter set to 0.80.
__ 12. Use the chhwres HMC command to dynamically remove 0.1 processing units from your partition. Check that they were removed with the lshwres HMC command. The following example commands are for a partition named LPAR1 and a managed system named sputnik. Change these parameters as necessary for your system. Example command to remove the 0.1 processing units: chhwres -r proc -o r -p LPAR1 -m sputnik --procunits 0.1 -w 0 Here is an example lshwres command and its output. Notice the curr_proc_units field is now 0.7. hscroot@sputnik-hmc:~> lshwres -r proc -m sputnik --filter \ "lpar_names=LPAR1" --level lpar lpar_name=LPAR1,lpar_id=1,curr_shared_proc_pool_id=0,curr_proc_m ode=shared,curr_min_proc_units=0.6,curr_proc_units=0.7,curr_max_ proc_units=1.0,curr_min_procs=1,curr_procs=1,curr_max_procs=10,c urr_sharing_mode=uncap,curr_uncap_weight=100,pend_shared_proc_po ol_id=0,pend_proc_mode=shared,pend_min_proc_units=0.6,pend_proc_ units=0.7,pend_max_proc_units=1.0,pend_min_procs=1,pend_procs=1, pend_max_procs=10,pend_sharing_mode=uncap,pend_uncap_weight=100, run_proc_units=0.7,run_procs=1,run_uncap_weight=100
__ 13. Try to remove 0.2 processing units from your partition with the chhwres command. What happened? Why? Your partition had 0.7 processing units and the partitions minimum setting is 0.6. The attempt to remove the 0.2 will fail because you can not go below the minimum. Here is an example chhwres command and the error that will result: chhwres -r proc -o r -p LPAR1 -m sputnik --procunits 0.2 -w 0 Your request goes below the profile's required processing unit limit. You can remove or move 0.1 or fewer processing units. Please retry the operation.
8-9
Advanced Processor Operations

__ 14. Use the lparstat AIX 5L V5.3 command with the -i option in your partition and view the information available. Use the man page for lparstat to see more information about this command. The output of this AIX 5L V5.3 lparstat -i command shows the processor and memory resources settings for your partition. Example lparstat -i output: Node Name Partition Name Partition Number Type Mode Entitled Capacity Partition Group-ID Shared Pool ID Online Virtual CPUs Maximum Virtual CPUs Minimum Virtual CPUs Online Memory Maximum Memory Minimum Memory Variable Capacity Weight Minimum Capacity Maximum Capacity Capacity Increment Maximum Physical CPUs in system Active Physical CPUs in system Active CPUs in Pool Unallocated Capacity Physical CPU Percentage Unallocated Weight : : : : : : : : : : : : : : : : : : : : : : : : sputnik171 LPAR1 1 Shared-SMT Uncapped 0.70 32769 0 1 10 1 1024 MB 2048 MB 512 MB 100 0.60 1.00 0.01 2 2 2 0.00 70.00% 0
__ 15. 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. The command has similar output as sar -P ALL 1 4, however there are additional columns related to partitions. Example command and its output: # lparstat 1 4 System configuration: type=Shared mode=Uncapped smt=On lcpu=2 mem=1024 psize=2 ent=0.70
V3.1.0.1
EXempty %user %sys %wait %idle physc %entc lbusy vcsw phint ----- ---- ----- ----- ----- ----- ------ ---- ----0.1 0.4 0.0 99.5 0.01 0.8 0.0 252 0 0.0 0.3 0.0 99.7 0.00 0.5 0.0 256 0 0.0 0.2 0.0 99.8 0.00 0.5 0.0 252 0 0.0 0.2 0.0 99.8 0.00 0.5 0.0 252 1
__ 16. There is an additional column in the lparstat output that can be enabled. The additional column is the available shared processing pool (app) statistic which shows unused processing resources in the shared processor pool for that interval. Directions are below to enable the viewing of this statistic. After you have configured the statistic to be shown, run the lparstat command and make sure you have made the change. Steps to enable the app statistic: 1. In the HMCs Server Management application, select your partition name, right-click, and choose Properties on the pop-up menu. 2. Click the Hardware tab. 3. Click the Processors and Memory tab. 4. Click the Allow shared processor pool utilization authority check box as shown in this example:
5. Click the OK button. 6. You do not have to reactivate your partition.

Copyright IBM Corp. 2004, 2007 Exercise 8. Advanced Processor Concepts 8-11
7. Run lparstat again in your partition. You should see a new app field which is the amount of unutilized shared processing units in the shared processor pool. 8. Here is an example lparstat output with this new app field which shows that there is 2.0 processing units that are unused during the time lparstat was run. Unused does not mean unallocated; unused means the partitions are not actively using those processing resources. # lparstat 1 4 System configuration: type=Shared mode=Uncapped smt=On lcpu=2 mem=1024 psize=2 ent=0.70 %user %sys %wait %idle physc %entc lbusy app vcsw phint ----- ---- ----- ----- ----- ----- -------- ---- ----0.1 0.4 0.0 99.5 0.01 0.8 0.0 2.00 255 0 0.0 0.3 0.0 99.7 0.00 0.5 0.0 2.00 254 0 0.0 0.2 0.0 99.8 0.00 0.5 0.0 2.00 252 0 0.0 0.2 0.0 99.8 0.00 0.5 0.0 2.00 250 0
__ 17. Disable simultaneous multi-threading, then run the lsdev -Cc processor command to list the virtual processors. You should see the same output as this: # lsdev -Cc processor proc0 Available 00-00 Processor This command shows one processor called proc0. The partition has 0.70 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).
__ 18. Enable simultaneous multi-threading and run the lsdev -Cc processor command again. Is the output different? Why or why not? To enable simultaneous multi-threading, use the smtctl -m on command. The lsdev command output is the same because this is a shared processor partition and it lists virtual processors (not logical processors).
__ 19. Dynamically add two more virtual processors. Run the lsdev -Cc processor command again. What does the output show?
V3.1.0.1
EXempty
To dynamically add two more virtual processors, go to the Server Management application on the HMC. Select the partition name, right-click, and choose Dynamic Logical Partitioning -> Processor Resources -> Add on the menu. In the window that pops up, enter a 2 in the Virtual processors to add box at the very bottom of the screen. Click OK. Go back to your partitions terminal window and run lsdev -Cc processor again. The output should look similar to this: # lsdev -Cc processor proc0 Available 00-00 Processor proc2 Available 00-02 Processor proc4 Available 00-04 Processor Now AIX 5L sees three processors. These are the virtual processors.
__ 20. Run the lparstat command again. How many logical processors are in the partition? The lparstat command will show 6 logical processors (lcpu=6) because there are three virtual processors configured in the partition and simultaneous multi-threading is enabled. There are two logical processors for each virtual processor. # lparstat System configuration: type=Shared mode=Uncapped smt=On lcpu=6 mem=1024 psize=2 ent=0.70 %user %sys %wait %idle physc %entc lbusy app vcsw phint ----- ---- ----- ----- ----- ----- -------- ---- ----0.0 0.0 0.5 99.5 0.00 0.0 0.7 0.54 934190 335
End of exercise
8-13
V3.1.0.1
EXempty
Exercise 9. Virtual I/O

This lab covers the installation and configuration of a Virtual I/O Server, clients, and Virtual Ethernet.

At the end of the lab, you should be able to: Configure a virtual Ethernet connection between two partitions Install the Virtual I/O Server software Configure a Virtual I/O Server Configure a virtual SCSI client
Introduction
In this exercise, students will configure a virtual Ethernet connection between two partitions, install the Virtual I/O Server software, and configure a Virtual I/O Server and virtual SCSI client.
Requirements
9-1

Preface
All exercises of this chapter depend on the availability of specific equipment in your classroom. You will need: - A managed system configured with at least 2 partitions running AIX 5L V5.3 - A system from which to execute remote commands to the HMC (using SSH) - All lab systems need to be accessible to each other on a network - A CD with Virtual I/O Server software Hints are provided for lab exercises in case you need them and provide solutions for the lab exercise steps. All hints are marked by a sign.
Lab Exercise for Topic 1 Configuring a Virtual Ethernet Connection

In this part of the exercise, you will create a virtual Ethernet adapter in your partition. Either you or another lab group that shares your managed system will create another virtual Ethernet adapter in a second partition. These two virtual adapters will be configured for the same VLAN. You will configure the virtual adapters and test that the partitions can ping each other. __ 1. Connect to the HMC using the WebSM client. Go to the Server Management application. Your partition should not be running for this part of the exercise. If it is running, shut it down. You may go to Step 2 below without waiting for the shutdown to complete.
__ 2. Add a virtual Ethernet adapter to the default profile of your partition. Create the adapter in the lowest available virtual slot, and assign it the virtual LAN ID value of 1. Go to the Server Management application on the HMC. Expand the partition list so that you can see the default profile for your partition. Select the default profile, right-click, and choose Properties on the pop-up menu. Go to the Virtual I/O Adapters tab. Then click the Ethernet tab.
9-2
V3.1.0.1
EXempty
Click the Create adapter... button. On the next screen, the slot number will be entered for you. Enter a 1 for the virtual LAN ID if it is not already set to 1. Do not click any other check boxes. Here is an example where the virtual LAN ID entered is 1:
9-3
Click the OK button to create the virtual Ethernet adapter. On this example system, the virtual adapters screen now looks like this:
9-4
V3.1.0.1
EXempty
You will need to click OK once more to close this profile properties window and return to the Server Management application.
__ 3. The goal is for at least two LPARs on the same managed system to have virtual Ethernet adapters configured with the same Port VLAN ID. The virtual slot numbers do not need to match. If there is another group of students using LPARs on your managed system, they will create a virtual Ethernet adapter with the port VLAN ID of 1. If your group is the only one on your managed system, then add a virtual Ethernet adapter with the same configuration (that is, with a virtual LAN ID of 1) to the default profile of another AIX 5L partition. Follow the same steps as in step 2 above for a second LPAR.
__ 4. Activate your partition using the default profile, and open a terminal window. If your lab group is the only one on your managed system, activate both partitions. Select your partition name, right click, and choose Activate on the pop-up menu. Select the default profile, click the check box next to Open a terminal window or console session, and click OK to activate.
__ 5. In the console window that opens for your partition, log in to AIX, and verify that there is one new virtual Ethernet adapter. Here is an example command and its output. In this example, ent1 is the new virtual Ethernet adapter and ent0 is a physical adapter.
# lsdev -Cc adapter | grep ên ent0 Available 04-08 10/100/1000 Base-TX PCI-X Adapter (14106902) ent1 Available Virtual I/O Ethernet Adapter (l-lan)
__ 6. Use the smit chinet fastpath to configure the virtual Ethernet interface. Select the interface. Use 10.0.0.1 for the IP address, use 255.0.0.0 for the Network mask, and set the current state to Up. Press Enter to run the command. If your lab group is the only one on your managed system, configure the second partitions virtual Ethernet interface. Use 10.0.0.2 for the IP address for the second partition. Coordinate with any other lab groups on your managed system so that there are no duplicate IP addresses.
__ 7. ping your own IP address to verify it is working. Then ping the remote partitions IP address to verify that the two virtual Ethernet adapters can communicate.
9-5
Here is an example of the ping command and its output when the ping is successful. # ping 10.0.0.1 PING 10.0.0.1 (10.0.0.1): 56 data bytes 64 bytes from 10.0.0.1: icmp_seq=0 ttl=255 time=0 ms 64 bytes from 10.0.0.1: icmp_seq=1 ttl=255 time=0 ms ^C --- 10.0.0.1 ping statistics --2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 0/0/0 ms ping 10.0.0.1
__ 8. When all ping tests are successful, shut down your partition or, in the case where you configured two partitions, shutdown both partitions. You do not have to wait for the partitions to completely shut down to go to the next step.
Configuring Additional VLANs

In this part of the exercise, you will change the configuration of a partition so that it can participate on two VLANs. __ 9. In LPAR1s default profile, change the virtual Ethernet adapters configuration so that it can participate on two VLANs. Go to the Server Management application on the HMC. Expand the partition list so that you can see the default profile for your partition. Select the default profile, right click, and choose Properties on the popup menu. Go to the Virtual I/O Adapters tab. Go to the Ethernet tab. Select the virtual Ethernet adapter that you created in a previous step. Click the Properties... button. In the window that pops up, click the IEEE 802.1Q compatible adapter checkbox and add the other VLAN ID to the Additional virtual LAN list. Dont forget to click the Add button so that the VLAN ID appears in the Additional virtual LAN IDs: list.
9-6
V3.1.0.1
EXempty
Here is an example:
Click OK on this screen, then OK again to close the partition properties window.
__ 10. Activate the partition using the profile you just edited.
__ 11. When the partition is fully booted, log in to the partition and run lsdev -C | grep ê in the AIX partition to list all Ethernet interfaces. Is there a VLAN entry listed? Here is an example command and its output.
# lsdev -C | grep ê en0 Available 04-08 en1 Available ent0 Available 04-08 ent1 Available et0 Defined 04-08 et1 Defined Standard Ethernet Network Interface Standard Ethernet Network Interface 10/100/1000 Base-TX PCI-X Adapter (14106902) Virtual I/O Ethernet Adapter (l-lan) IEEE 802.3 Ethernet Network Interface IEEE 802.3 Ethernet Network Interface
There is no VLAN entry in the above output.
9-7
__ 12. Use the smit addvlan fastpath to create a new VLAN pseudo device that accesses VLAN 2 using the virtual Ethernet adapter that you created. Here is an example of the addvlan SMIT screen where the VLAN ID 2 has been entered: Add A VLAN Type or select values in entry fields. Press Enter AFTER making all desired changes. [Entry Fields] ent1 2]
VLAN Base Adapter * VLAN Tag ID
__ 13. List all Ethernet interfaces in your partition. Is there a VLAN entry now? You should now see a VLAN pseudo device listed in the lsdev output. Here is an example command and its output. Notice there is now an ent2 listed as a VLAN.
# lsdev -C | grep ê en0 Available 04-08 en1 Available en2 Defined ent0 Available 04-08 ent1 Available ent2 Available et0 Defined 04-08 et1 Defined et2 Defined Standard Ethernet Network Interface Standard Ethernet Network Interface Standard Ethernet Network Interface 10/100/1000 Base-TX PCI-X Adapter (14106902 Virtual I/O Ethernet Adapter (l-lan) VLAN IEEE 802.3 Ethernet Network Interface IEEE 802.3 Ethernet Network Interface IEEE 802.3 Ethernet Network Interface
__ 14. Log in to the HMC and try the lshwres command shown below. Replace msname with your managed systems name. Notice all of the information that the command output provides. lshwres -r virtualio --rsubtype eth -m msname --level lpar Here is an example command and its output for a system named sputnik. The output for your HMC may have different results. Notice in this output below that LPAR1 has an additional VLAN ID of 2. hscroot@sputnik-hmc:~> lshwres -r virtualio --rsubtype eth -m sputnik --level lpar lpar_name=LPAR1,lpar_id=1,slot_num=2,state=0,is_required=0,is_trunk =0,ieee_virtual_eth=0,port_vlan_id=1,addl_vlan_ids=,mac_addr=C6C2FB 672E4C lpar_name=LPAR2,lpar_id=2,slot_num=2,state=1,is_required=0,is_trunk =0,ieee_virtual_eth=1,port_vlan_id=1,addl_vlan_ids=2,mac_addr=C6C2F CA4E1E4
V3.1.0.1
EXempty __ 15. What if you had several virtual Ethernet devices? How would you figure out which Ethernet interface (such as ent2 or ent3 for example) was configured with which VLAN IDs? What AIX 5L commands would you use? The lscfg command shows the location codes for devices. For example, in this command we grep for the ent1 device and we see it is in virtual slot 2 (C2).
# lscfg | grep ent1 * ent1 U9131.52A.062A87G-V2-C2-T1 Ethernet Adapter (l-lan) Virtual I/O
Now, view the partitions profile properties on the HMC and see which virtual Ethernet adapter is in virtual slot 2. Open the properties for this device and the Virtual LAN ID and any additional VLAN IDs will be listed. (Or, you can use the lshwres command output on the HMC.) Another way to do this for additional VLAN devices is to log in to the partition, and use the lsattr -El entX command, in which entX is the VLAN pseudo device that you added with SMIT. Here is an example of the output of this command: # lsattr -El ent2 base_adapter ent1 VLAN Base Adapter True vlan_tag_id 2 VLAN Tag ID True
9-9
Lab Exercise for Topic 2 Installing Virtual I/O Server Software from Product Media
In this part of the exercise, if there is more than one lab group on your managed system, you will have to work together on these steps. You will use the physical disks of one of your partitions as the disks for the Virtual I/O Server partition. __ 17. In a running partition, run the bootlist -m normal -o command to find out which is the boot disk for the partition. Here is an example command and its output. In this example, hdisk0 is the bootdisk: # bootlist -m normal -o hdisk0
__ 18. Now that you know which hdisk is the bootdisk, find out its location code with the lscfg | grep hdisk# command where hdisk# is the bootdisk. Write down the location code. Here is an example command and its output. In this example, for hdisk0, you would write down: C1-T1-L3-L0. # lscfg | grep hdisk0 + hdisk0 U787F.001.DPM166X-P1-C1-T1-L3-L0 SCSI Disk Drive (73400 MB) 16 Bit LVD
This information is important so that you do not install the Virtual I/O Server software on to your AIX 5L boot disk.
__ 19. Shut down this partition. While you are waiting for the partition to shut down, open the partitions profile properties and note all of the physical I/O slots that it has configured. Write them down here. Issue the shutdown -F command. Select the partitions profile, right-click, and choose Properties on the menu. Go to the Physical I/O tab and note all the slots configured in the bottom half of the screen labeled Profile I/O devices. In the example shown below, this partition is configured with the slots C1 and C2.
V3.1.0.1
EXempty
__ 20. Create a Virtual I/O Server partition called VIOS and name the profile default. The VIOS partition will take the physical I/O resources of one of the partitions (such as LPAR1) so that it can boot. Using the example previously shown, this would be C1 and C2. Be sure to include the DVD drive if you are using a DVD installation, which on a p5-520 is slot T12. For memory and processing resources, give it sufficient resources so that it can activate successfully. For example: Memory: Minimum=512 MB, Desired=1 GB, Maximum= 2GB Shared processors: Minimum=0.1, Desired=0.4, Maximum=2.0 To create a new partition, go to the Server Management application on the HMC. Select the Partitions icon, right-click, and choose Create -> Logical Partition.
9-11
When the Create Logical Partition Wizard window opens, name your partition VIOS and click the Virtual I/O server partition environment radio button at the bottom. Continue to create the partition with the wizard, using the planned for processing and memory resources, and the I/O slots that you noted above.
__ 21. Insert the Virtual I/O Server DVD into the drive connected to the Virtual I/O Server logical partition. (For remote classrooms, the DVD may already be in the media drive or your instructor may have additional instructions for using a NIM server.)
__ 22. Activate the Virtual I/O Server logical partition using the Diagnostic with default boot list boot mode. On the HMC, right-click the partition to open the menu. Select Activate. The Activate Partition menu opens with a selection of partition profiles. Ensure the correct profile is highlighted. Select Open a terminal window or console session to open a virtual terminal window. Select the Advanced button to open the advanced options menu. For the boot mode, select Diagnostic with default boot list. Click OK and then OK again to start the activation.
__ 23. Interact with the menus as if you were restoring an AIX mksysb image. Choose the Change/Show Installation Settings... menu option and make sure the second hdisk is selected, or at least a disk that is not the same as the one you identified earlier as the AIX 5L boot disk. Remove hdisk0, if that was your AIX 5L boot disk used by the partition that you shut down. Double check this. If this is not done correctly you will overwrite your AIX 5L image.
__ 24. The partition will reboot when the installation is complete. If the activation fails, the bootlist is incorrect and the partition is trying to boot a Virtual I/O Server type partition with a regular AIX image (that is on hdisk0). Go to SMS and change the bootlist to the second disk. You will need to refer to the location code for the boot disk that you noted above. You may already be in SMS if the partition failed to boot. If not, activate the partition, override the boot modes and choose SMS. To boot from the correct disk, from the main SMS menu choose option 5: Select Boot Options.
V3.1.0.1
EXempty
Choose 1: Select Install/Boot Device. Choose 5: Hard Disk. Choose 1: SCSI. Choose the first (or only) media adapter in the list. Choose the second disk. Choose 2: Normal Boot. Choose 1: Yes. (You are sure you want to exit SMS.)
__ 25. When the Virtual I/O Server is booted, log in using the padmin login. You will be prompted to change the password; use abc1234 as the new password.
__ 26. Accept the license for the Virtual I/O Server product. In the CLI, enter the license -accept command.
__ 27. Set the date and time zone for the partition. The new time zone will take effect after the next operating system boot. Enter this command 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: chdate 123107302005 -timezone PST8PDT If you get an error with the chdate command, then use the oem_setup_env command and set the date and time with SMIT or AIX 5L commands. Use exit to return to the Virtual I/O Server CLI.
__ 28. Type the help command to see what CLI commands are available. Here is the output of the help command for release 1.3.0.0 of the Virtual I/O Server. Use the ioslevel command to determine your Virtual I/O Server software release.
Install Commands ioslevel license lssw oem_platform_level oem_setup_env remote_management updateios LAN Commands cfglnagg Security Commands lsfailedlogin lsgcl viosecure UserID Commands chuser lsuser mkuser passwd rmuser
9-13
cfgnamesrv entstat hostmap hostname lsnetsvc lstcpip mktcpip chtcpip netstat optimizenet ping rmtcpip startnetsvc stopnetsvc traceroute vasistat Device Commands chdev chpath cfgdev lsdev lsmap lspath mkpath mkvdev mkvt rmdev rmpath rmvdev rmvt 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
Maintenance Commands backupios bootlist cattracerpt chdate chlang diagmenu errlog fsck invscout ldfware loginmsg lsfware lslparinfo motd mount pdump restorevgstruct savevgstruct showmount shutdown snap startsysdump starttrace stoptrace sysstat topas unmount viostat wkldmgr wkldagent wkldout Shell Commands awk cat chmod clear cp crontab date ftp grep head ls man mkdir more mv rm sed stty tail tee vi
V3.1.0.1
EXempty
redefvg reducevg syncvg unmirrorios Storage Pool Commands chsp lssp mkbdsp mksp rmbdsp
wall wc who
__ 29. Type in oem_setup_env to get an AIX 5L root shell. From here you can invoke AIX 5L V5.3 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 software needed to support storage solutions. All configuration of the Virtual I/O Server should be from its command line interface.
__ 30. Shut down the VIOS partition. To shut down the VIOS partition at the Virtual I/O Server command line, use the command shutdown with no options.
Configuring a Virtual SCSI Disk

Now that your Virtual I/O Server is installed, you can configure a virtual SCSI server adapter. __ 31. On the HMC, add a virtual SCSI server adapter to the default profile for the Virtual I/O Server. Use slot 3 even though slot 2 may be available. The client should have its virtual slot 3 available, and for ease of management, it is good to have the slots match particularly in a complex configuration to easily see which slots are. Click the box to allow any partition to connect. Select the partition profile for the VIOS partition, right-click, and choose Properties on the pop-up menu. Go to the Virtual I/O Adapters tab. This should bring you to the SCSI tab. If not, click the SCSI tab. Click the Create server adapter... button. The window that appears is shown below. You can keep all of the defaults. Make note of the slot number. The slot number is 3 in the example below.
9-15
Click OK to create the adapter. The SCSI tab should look similar to this example:
V3.1.0.1
EXempty
Click OK again to close the profile properties.
__ 32. You will use one of your other partitions as a virtual SCSI disk client partition. For the purpose of this exercise, use the partition that still has its own physical devices. That is, do not use the partition that has the physical devices that you gave to the Virtual I/O Server partition. If the partition is not running: In the default profile for this client partition, add a virtual SCSI client adapter in its virtual slot 3. Have it connect to the VIOS partitions virtual slot 3. If the partition is running: Use the Dynamic Logical Partitioning menu to add a virtual SCSI client adapter in its virtual slot 3. Have it connect to the VIOS partitions virtual slot 3. Also add this virtual adapter to the default profile in case you re-activated it later. To add the adapter to the default profile: In the Server Management application on the HMC, select the partition profile for the client partition, right-click, and choose Properties on the pop-up menu. In the partitions properties window, go to the Virtual I/O Adapters tab. Click the SCSI tab if you are not already there. Click the Create client adapter... button. There will already be a slot number listed for you in the window. Change the slot number (if necessary and if possible) to 3 to match the slot number that you used for the VIOS partitions server adapter. Then, in the Connection settings area, choose the VIOS partition and select the slot number on the VIOS partition in which you just created the server adapter. Here is an example of this screen:
9-17
Click OK and OK again to create this adapter in the profile and close the properties window. To add the adapter with the Dynamic Logical Partitioning menu: Select the partition name, right-click, and choose Dynamic Logical Partitioning -> Virtual Adapter Resources -> Add/Remove from the menu. The SCSI tab is the default tab. Click the Create client adapter... button. There will already be a slot number listed for you in the window. Change the slot number (if necessary and if possible) to 3 to match the slot number that you used for the VIOS partitions server adapter. Then, in the Connection settings area, choose the VIOS partition and select the slot number on the VIOS partition in which you just created the server adapter. Here is an example of this screen:
Click OK and OK again to create this adapter in the profile and close the properties window.
__ 33. Modify the server virtual adapter configuration so that it only allows the one client partition and has the proper client slot number. Select the partition profile for the VIOS partition, right-click, and choose Properties on the pop-up menu. Go to the Virtual I/O Adapters tab. On the SCSI tab, in the listing of the virtual adapters, select the SCSI adapter you just created and click the Properties... button. In the Slot connection settings area, click the radio button for Only selected client partition can connect.
V3.1.0.1
EXempty
Use the pull-down to choose the name of your client partition, such as LPAR2. For the client partition slot number, enter the slot that was created for the virtual client SCSI adapter. In the example below, slot 3 was entered:
Click OK and OK again to modify this adapter in the profile and close the profile properties window.
__ 34. Activate the Virtual I/O Server partition.
__ 35. Log in to the Virtual I/O Server and verify that the virtual SCSI server adapter is available. Also, check the mapping to the virtual slot (there should be no mapping yet). The two commands you need to use are lsdev -virtual to find the name of the virtual SCSI server adapter, then use lsmap -vadapter vhost0 where vhost0 is the name of the adapter to see any devices mapped to it. Here is example output of the lsdev command which shows the new vhost0 adapter: $ lsdev -virtual name status vhost0 Available vsa0 Available description Virtual SCSI Server Adapter LPAR Virtual Serial Adapter
Here is example output of the lsmap command.
9-19
$ lsmap -vadapter vhost0 SVSA Physloc Client Partition ID --------------- ------------------------------------------ -----------------vhost0 U9131.52A.062A87G-V3-C3 0x00000000 VTD NO VIRTUAL TARGET DEVICE FOUND
__ 36. Now, check the location code of hdisk0 on your VIOS partition to see if it matches the AIX 5L boot disk that your client partition used to use. You can use the following CLI command (where hdisk0 is the correct disk): $ lsdev -dev hdisk0 -vpd | grep hdisk In Step 18 in this exercise, the example boot disk for the AIX 5L partition was C1-T1-L3-L0. This should match the output of the lsdev command as shown below: $ lsdev -dev hdisk0 -vpd | grep hdisk hdisk0 U787F.001.DPM166X-P1-C1-T1-L3-L0 16 Bit LVD SCSI Disk Drive (73400 MB)
__ 37. Also check which disk rootvg resides in your VIOS partition. Here is an example lspv command output which shows rootvg on hdisk1: $ lspv NAME hdisk0 hdisk1 PVID none 000253620a922d14 VG None rootvg STATUS active
__ 38. Associate hdisk0 as backing storage with the virtual server SCSI adapter. Use the entire disk as the backing storage. This example command associates physical volume hdisk0 with the vhost0 adapter: $ mkvdev -vdev hdisk0 -vadapter vhost0
__ 39. Check the output of lsdev -virtual to verify that your new target device is listed. The output of lsdev -virtual should now show: $ lsdev -virtual name status vhost0 vsa0 vtscsi0 description
Available Virtual SCSI Server Adapter Available LPAR Virtual Serial Adapter Available Virtual Target Device - Disk
V3.1.0.1
EXempty __ 40. Use lsmap -vadapter vhost0 to verify the mapping of the virtual target. If your adapter is not vhost0, use the proper vhost name. The output of lsmap -vadapter vhost0 should now show:
$ lsmap -vadapter vhost0 SVSA Physloc Client Partition ID --------------- ---------------------------------- -----------------vhost0 U9111.520.10DEF9E-V3-C3 0x00000001 VTD LUN Backing device Physloc vtscsi0 0x8100000000000000 hdisk0 U787A.001.DPM11KP-P1-C1-T1-L3-L0
__ 41. If the client partition is in the Not Activated state, activate it. Once it is fully booted, log in as root and use lsdev -Cc disk to see the new virtual SCSI disk. If the client is already running, and you added the virtual SCSI adapter dynamically, log in to the partition and run the following commands: lsdev -Cc disk, then the cfgmgr command, then run lsdev -Cc disk again to see the new virtual disk. Example commands and their outputs for a client that is already running. If the client was just activate, its lsdev -Cc disk output should look like the last commands output below which shows a new Virtual SCSI Disk Drive. # lsdev -Cc disk hdisk0 Available 03-08-00-3,0 16 Bit LVD SCSI Disk Drive hdisk1 Available 03-08-00-4,0 16 Bit LVD SCSI Disk Drive # cfgmgr # lsdev -Cc disk hdisk0 Available 03-08-00-3,0 16 Bit LVD SCSI Disk Drive hdisk1 Available 03-08-00-4,0 16 Bit LVD SCSI Disk Drive hdisk2 Available Virtual SCSI Disk Drive
__ 42. You have successfully created a virtual SCSI disk and had a client partition access it. Now, you will remove the configuration. In the client partition, use rmdev to remove the virtual disk. Here is an example command where the virtual disk is hdisk2: rmdev -l hdisk2 -d
__ 43. In the next step, you are going to dynamically remove the client partitions virtual SCSI adapter from its virtual slot. What other device do you need to remove from the operating system before removing the virtual adapter on the HMC? Remove this
Copyright IBM Corp. 2004, 2007 Exercise 9. Virtual I/O 9-21
device from the operating system. If you cannot figure out what this is, continue on to the next step and the HMC will give you an error which will tell you the device you must remove. The device that must be removed is the virtual SCSI client adapter device. Look up the name of this device with lsdev. Here is an example command which shows the vscsi0 device: # lsdev ent1 vsa0 vscsi0 -Cc adapter | grep Virtual Available Virtual I/O Ethernet Adapter (l-lan) Available LPAR Virtual Serial Adapter Available Virtual SCSI Client Adapter
Use rmdev to remove the adapter. For example: rmdev -l vscsi0 -d
__ 44. Using the HMC, remove the virtual SCSI client adapter from the partition dynamically. In the HMC Server Management application, select the partition name, right-click, and choose Dynamic Logical Partitioning -> Virtual Adapter Resources -> Add/Remove from the menu. The SCSI tab is the default tab. Select the adapter in slot 3 and click the Delete button. Click OK to complete the operation. Here is an example error that the HMC will present if you do not delete the virtual SCSI adapter from the operating system before trying to dynamically remove it from the partitions resources:
V3.1.0.1
EXempty __ 45. On the HMC, remove the virtual SCSI client adapter from the default profile for the client partition. In the Server Management application, select the default profile for the client partition. Right-click and choose Properties on the menu. Go to the Virtual I/O Adapters tab. On the SCSI tab, in the listing of the virtual adapters, select the SCSI adapter you just created and click the Delete button. Click OK to close the properties window.
__ 46. Let your instructor know that you have completed the exercise. Ask if there is time to complete the optional lab steps.
OPTIONAL EXERCISE: Configure an Optical Device as a Virtual SCSI Device

In this part of the lab, you will configure the optical media device as a virtual SCSI device. The VIOS partition should have the slot which controls the physical optical media device allocated to it and you will configure the cd0 device to be available in a client partition.
__ 47. Log in to the VIOS partition and shut it down with the shutdown command.
__ 48. Check the default profile for the VIOS partition to make sure it has the physical slot with the description of Other Mass Storage Controller allocated to it. If it does not, perform the steps to allocate it to the VIOS partition profile. Do not close the profile properties yet; the next step has you make more changes. Open the default partition profile properties for the VIOS partition and look for the Other Mass Storage Controller slot on the Physical I/O tab in the bottom area labeled Physical I/O devices. The slot should be there, as this was mentioned as part of the I/O configuration instructions in Step 20 in this exercise. If the slot is not allocated to the VIOS partition, use the managed system properties to find out which partition has it. Use DLPAR to remove it from one of the AIX 5L partitions and then add it to the VIOS partition profile.
__ 49. In the VIOS default partition profile, add another virtual SCSI server adapter.
9-23
On the Virtual I/O Adapters tab, on the SCSI tab, click the create SCSI server adapter... button. In the window that pops up, configure the adapter to be in slot 4. Choose your client partitions slot 4 as the remote client. For example:
Click OK then OK again to complete the operation.
__ 50. Activate the VIOS partition with its default profile.
__ 51. Once it is booted, log in to the VIOS partition. List out the virtual adapters. You should now see a new vhost# adapter. Example command and output which shows a new vhost1 adapter: $ lsdev -virtual name status vhost0 Available vhost1 Available vsa0 Available vtscsi0 Available description Virtual SCSI Server Adapter Virtual SCSI Server Adapter LPAR Virtual Serial Adapter Virtual Target Device - Disk
__ 52. Configure cd0 as the backing storage associated with the new vhost1 adapter. Notice the new device name. An example command to make cd0 the backing storage on vhost1: $ mkvdev -vdev cd0 -vadapter vhost1 vtopt0 Available
V3.1.0.1
EXempty __ 53. Check the output of lsdev -virtual to verify that your new adapter is listed. The output of lsdev -virtual should now show a second Virtual Target Device - Optical Media. In the example below, this new device is vtopt0: $ lsdev -virtual name status vhost0 Available vhost1 Available vsa0 Available vtopt0 Available vtscsi0 Available description Virtual SCSI Server Adapter Virtual SCSI Server Adapter LPAR Virtual Serial Adapter Virtual Target Device - Optical Media Virtual Target Device - Disk
__ 54. Use lsmap -vadapter vhost1 to verify the mapping of the virtual target. The output of lsmap -vadapter vhost1 should now show:
$ lsmap -vadapter vhost1 SVSA Physloc ------------ ---------------------------------------vhost1 U9131.52A.062A87G-V3-C4 VTD LUN Backing device Physloc vtopt0 0x8100000000000000 cd0 U787F.001.DPM166X-P4-D2
Client Partition ID -----------------0x00000000
__ 55. You have finished configuring a new virtual SCSI server adapter and backing storage which is an optical device. Now you need to configure the client partition. The client partition should still be running and it has its network interface configured, so you can do this dynamically. Dynamically add the new virtual SCSI client adapter in virtual slot 4. Specify the VIOS partitions virtual slot 4 in the configuration. In the HMCs Server Management application, select the client partition profile name, right-click, and choose the Dynamic Logical Partitioning -> Virtual Adapter Resources -> Add/Remove menu option. Click the Create client adapter... button. In the next window, configure the adapter to be in slot 4, and point it to the VIOS partition and the slot 4 on the VIOS partition. For example:
9-25
Click OK and then OK again to create the client adapter and close the properties window.
__ 56. Log in to the client partition and run cfgmgr to discover new devices.
__ 57. In the client partition, list all of the available devices. You can use the -S a option to lsdev so that you only see Available devices and not those listed as Defined, if there are any devices listed as defined. You should now see a cd# device. Note: The value of the # of the cd# device name will depend on if there was already a cd0 previously in this partition and it was never deleted from the ODM database (with the -d option of rmdev). Here is an example command and its output. # lsdev -S a | grep cd cd1 Available Virtual SCSI Optical Served by VIO Server
You have successfully added the cd0 device to a client partition which is a virtual SCSI device hosted by the Virtual I/O Server. You can now use this device as if it were physically allocated to the client partition.
End of exercise
V3.1.0.1
EXempty
Exercise 10.Operating Systems

This exercise covers the installation of AIX 5L V5.3 into a partition.

At the end of the lab, you should be able to: Install AIX 5L V5.3 in a partition
Introduction
You will use a NIM master or CDs to install AIX 5L 5.3 in a partition.
Requirements
This workbook A workstation with WebSM connected to a network A POWER5 processor-based managed system connected to the same network as the workstations A NIM master configured to support the client partitions or a set of distribution CDs and physical access to the DVD drive of the managed system
Exercise 10. Operating Systems
10-1

Preface
All exercises of this chapter depend on the availability of specific equipment in your classroom. You will need a computer system connected to the World Wide Web and a Web browser. You will also need a managed system and a NIM master running AIX 5.3 or a set of AIX 5.3 distribution CDs and physical access to the managed system. All lab systems need to be accessible to each other on a network. This exercise assumes you are already familiar with installing from a Network Installation Manager (NIM) master. Hints are provided for lab exercises in case you need them and provide solutions for the lab exercise steps. All hints are marked by a sign.
Check NIM Master Configuration

__ 1. Log in to the NIM master as team0#, where # is your lab group number. __ 2. Make sure the NIM master is running the AIX 5L V5.3. What command did you use? oslevel will report the operating system version.
__ 3. Check the host IP address, the subnet mask, and the gateway IP address of the NIM master. Use the lsattr -El en0 command to find out the NIMs IP address and subnet mask information. Use netstat -rn to find out the default gateway address. NIM Internet Address: NIM Subnet Mask: NIM Gateway Address: _______________________ _______________________ _______________________
Allocating NIM Resources for Client Installation

__ 4. On the NIM master, invoke SMIT with the smitty command with the fast path to the NIM configuration information: smitty nim_bosinst You will be asked to choose a TARGET for the operation. This is asking you to select the client host on which you want to load AIX. Highlight your partitions host name and press Enter to select it. If you do not know the host name for your partition, ask your instructor. __ 5. You will need to enter the following information on the next few entry screens:
V3.1.0.1
EXempty
__ a. Pick mksysb for the TYPE of installation. __ b. Select the name of the mksysb image. For this training exercise, there may be only one and it is probably named something obvious like generic_sysb. If you are not sure what name to use, ask the instructor. __ c. Pick a SPOT source. There may be an obvious choice such as one called 53spot but ask your instructor which one to pick if you are not sure. __ d. Pick an LPP source. There may be an obvious choices such as one called 53source but ask your instructor which one to pick if you are not sure. This time when you press Enter you will get to a multiple entry form. __ 6. In the next form, scroll down a bit and to the question: Initiate reboot and installation now? Set the value to no. To change the value, press ESC 4, highlight your choice, and press Enter. (Note: This is a mksysb installation so we do not have to answer yes to the question Accept new license agreements? Back home, if you were to do an rte or spot installation, you would have to answer yes to this question.) Enter the form. Press Enter once again when you are asked Are you sure? When it is done, exit out of SMIT (ESC 0). __ 7. It is always a good idea to verify that the NIM configuration information is correct. __ a. Go back into SMIT with this fast path: smitty nim_lsalloc
__ b. Pick the client you want to check (your partition) and confirm that the information is correct. Exit SMIT.
Activate a Partition and Initiate the AIX 5L Installation

Here are some definitions that you will need in this section: - The Client IP address is your partitions IP (Internet) address. - The Server IP address is the NIM masters IP address. - The Gateway IP address is the gateway that the client uses to access the network to which your NIM master is connected. - The Subnet Mask is the netmask that your partition will need to use.
10-3
__ 8. Activate your partition using the SMS boot mode. Open the virtual console terminal window. Access the HMC applications using WebSM. Open the Server and Partition application, then the Server Management application. Select the partition name. Right-click the mouse button and choose Activate on the menu. In the pop-up menu, make sure the default profile is highlighted. Click the Advanced... button. Click the down arrow box next to Boot mode: Choose SMS in the list of options, then click OK. Back in the Activate window, click the check box next to Open a terminal window or console session Click the OK button. Your partition will now activate and stop at the SMS level. A console window to the partition will open.
__ 9. In the SMS menu, press the 2 key to select 2 Setup Remote IPL.
__ 10. If the next screen lists NIC adapters, choose a network adapter.
__ 11. Press the 1 key to select 1 IP Parameters.
__ 12. In the next screen there are four options. Type the number of the option you wish to alter. For example, press 1, then the Enter key to alter the Client IP address. If you do not know what addresses to use, ask your instructor. __ a. Enter your partitions IP address for the Client IP address. __ b. Enter the NIM servers IP address for the Server IP address. __ c. Enter the network gateway address for the Gateway IP address __ d. Enter the subnet mask such as 255.255.255.0 for the Subnet Mask. __ e. Press the Esc key to exit to the Network Parameters menu.
__ 13. Press the 2 key to select 2 Adapter Configuration.
V3.1.0.1
EXempty
__ 14. To save time, you can disable the Spanning tree. Press 2, then 2 again to disable. Press Esc to go back to the Network Parameters menu.
__ 15. Press the 3 key to select 3 Ping Test. Press a 1 to execute the ping test. After a moment or two, it should say Ping Success if the ping test succeeded. Press any key to return to the Ping Test screen.
__ 16. Press Esc to escape out of the Ping Test screen.
__ 17. Set the bootlist to specify the Ethernet adapter, then press the x key to exit SMS. The next screen will ask if you are sure you want to exit SMS. Type a 1 to choose yes and press Enter.
__ 18. You will see the network boot output in the window. After some time (perhaps 15 - 20 minutes), you should then see the AIX Welcome screen. Log in and answer the AIX installation question regarding the console, the language, and so forth.
__ 19. Once you have completed the installation, you may reboot the partition. You may leave your partition running at the end of this lab.
End of exercise
10-5
V3.1.0.1
EXempty
Exercise 11.Service Tools

This exercise demonstrates diagnostic operation and service tools configuration of the POWER5 processor-based managed system.

At the end of the lab, you should be able to: Run diagnostics in a partitioned environment Check the operation of the Service Focal Point application Turn off the System Attention Indicator for a partition
Introduction
In this exercise you will run a diagnostic and check the configuration of the Service Focal Point service tool by running two tests and verifying that the events are logged.
Requirements
Exercise 11. Service Tools
11-1

Preface
All exercises of this chapter depend on the availability of specific equipment in your classroom. You will need: - A computer system with the WebSM client installed - A managed system configured with at least 1 partition - A system from which to execute remote commands to the HMC (using SSH) - All lab systems need to be accessible to each other on a network. Hints are provided for lab exercises in case you need them and provide solutions for the lab exercise steps. All hints are marked by a sign.
Service Tools
This first part of this exercise will have you check the Service Focal Point configuration on the HMC. __ 1. You will need one AIX 5L partition which 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 filesystem 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 /dev/hd9var 512-blocks 262144 Free %Used 247360 6% Iused %Iused Mounted on 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, then the Serviceable Events will be deleted on the HMC. Log in to your partition and type the date command. Log in to the HMC WebSM interface, go to the HMC Management application, then HMC Configuration. Click Customize Console Date and Time, and check that this time is correct. The time difference between the HMC date and time and the partitions 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 was covered in the Dynamic Resource Allocation unit in this course (Unit 7).
V3.1.0.1
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 rsct_rm IBM.ERRM IBM.HostRM IBM.ServiceRM IBM.DRM IBM.CSMAgentRM IBM.AuditRM IBM.LPRM rsct_rm rsct_rm rsct_rm rsct_rm rsct_rm rsct_rm rsct_rm 258176 241788 233592 278664 245902 270470 221316 active active active active active active active
The above output shows that the typical RMC daemons are active. Do not worry if your list is not exactly the same as the one above; if there are some daemons listed, then the RMC daemons are active. Some individual daemons are only active when they are needed.
__ 5. Is the managed system enabled for Connection Monitoring? From the WebSM session, go to the HMC Service Focal Point application. Choose Service Utilities from the options. Choose Connection Monitoring from the Actions menu. The managed system should have Enabled in the State column as shown in the example below.
11-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 steps hint, the number of disconnected minutes considered an outage is 15.
__ 7. Test that the HMC is configured to log serviceable events to Service Focal Point. This procedure was explained in the lecture materials. You will check for the event in Service Focal Point later in this exercise. In the Service Utilities application, select the managed system, and choose Create Serviceable Event on the Selected menu. In the pop-up window, click the Test automatic problem reporting check box and click the Request Service button as shown in this example:
__ 8. Perform a test from a partition to make sure that it will log events with Service Focal Point. 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. Arrow down to oppanel and press Enter to select.
V3.1.0.1
EXempty
__ e. Press F7 to commit and Enter to continue. __ f. When asked if Is this correct?, arrow down to No and press Enter. On the next screen press Enter to continue.
__ g. When asked if you want to report this to Service Focal Point, answer Yes. Press F10 to exit the diagnostic program. __ h. This procedure should log an event from this partition in Service Focal Point but it may take about 5 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 step 8. Here is an example of a System Attention Indicator for LPAR2:
__ 9. Find out if your system is enabled for Call-Home. Go to the Remote Support application and choose Customize Service Settings. Check for Enabled in the State column for your managed system. The following example shows that events on the HMC and the managed system named lou will both be reported to IBM.
11-5
Service Focal Point - Check and Close Events

Earlier in this exercise, you performed two tests to verify the operation of Service Focal Point. The first was a test from the HMC and the second was an operator panel (oppanel) diagnostic test from a partition. In this section, you will check Service Focal Point for these events and close them. __ 10. Go to the Service Focal Point application. Choose Manage Serviceable Events from the options. This screen allows you to filter the output so 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. The next screen should list two or more lines which are reported serviceable events. Look for both of your new events; use the date and time to verify that your specific events were logged. The newest events will be at the top of the list. You may 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 and the second is the HMC test. Notice the descriptions. In the example below, you can tell the oppanel test came from the managed system from the Reporting name column (which states lou, the name of the managed system) and the machine type model number of 9111-520 which is a managed system. The Reporting name column is not shown in the example below. You can tell the HMC tests came from the HMC itself from the reporting name of lou-hmc and the machine type model number of 7310-CR3 which is an HMC.
V3.1.0.1
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 5 minutes for the event to be logged? Are the RMC daemons running on the partition? Step 3 above had you check 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 Service Focal Point 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 the Display character test failed event and choose View Details from the Selected menu. View the information available. Click Cancel to return to the Serviceable Events Overview window.
__ 13. Once you find your events, 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, then click Yes. When you are finished closing both your events, click the Cancel button to exit the Serviceable Events Overview window. Then 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 error, so it is okay to close it. __ 14. Turn off the System Attention Indicator for your partition. Recall that the oppanel test turned this on for your partition. Go to the Service Focal Point application. Choose Service Utilities. Select your managed system name. Choose System Attention LED... from the Selected menu.
Copyright IBM Corp. 2004, 2007 Exercise 11. Service Tools 11-7
Here is an example of the window that will pop up:
Your partition should have an Active LED State like LPAR2 above. This means that the System Attention Indicator is on. Select the partition name, choose Partition Operations, and Deactivate partition LED from the menu as shown above. After the indicator is deactivated, cancel out of all the Service Utilities windows. Check your partition in the Server Management application. The System Attention Indicator should not be showing next to your partitions name.
End of exercise
V3.1.0.1
EXempty
Exercise 12.HMC and Managed System Maintenance

This exercise provides practice for maintenance procedures on the HMC.

At the end of the exercise, you should be able to: Schedule backup of critical console data View HMC update information (if connected to Internet) View managed system firmware release and service pack level Create and import a system plan to the HMC
Introduction
In this exercise, you will schedule a critical console backup and determine if the HMC needs corrective service applied.
Requirements
Exercise 12. HMC and Managed System Maintenance
12-1

Preface
All exercises of this chapter depend on the availability of specific equipment in your classroom. Hints are provided for lab exercises in case you need them and provide solutions for the lab exercise steps. All hints are marked by a sign.
Backup Critical Console Data

__ 1. You can make a critical console data backup interactively or schedule it for a regular time. Find the Backup Critical Console Data application on the HMC interface. Perform a critical console backup to your AIX 5L partition using ftp. You will need at least 1 GB of space in the file system on the remote system for the backup file. If there is not enough space in the root file system on the remote system, create a user with a home directory in a file system with enough space. When the backup is finished, check that the file was created in roots (or the users) home directory and delete it. In real life, it is not a good idea for backup files to be created in roots home directory and you should create a backup user to perform this procedure. Go to the Licensed Internal Code Maintenance application on the HMC. Access the HMC Code Update application. Click Back up Critical Console Data. In the pop-up window, choose Send back up critical data to a remote site and click the Next button. In the next pop-up window, enter the remote servers host name. This will be the host name of your AIX 5L partition. Enter the User ID of root and roots password. Click OK to start the backup.
__ 2. Schedule a critical console data backup for 3 p.m. every Monday of every week. Go to the HMC Management application on the HMC. Click the HMC Configuration application. Click Schedule Operations. In the first pop-up window, choose the name of your HMC. In the next window, select Options -> New from the menu. In the next pop-up window, make sure Backup Critical Console Data line is highlighted and click the OK button. In the next window, there are two tabs. In the Date and Time tab, enter todays date and enter 3 p.m. as the time.
V3.1.0.1
EXempty
Click the Repeat tab. To set up a weekly backup, click the second round radio button titled Set up a repeated scheduled operation. Pick Monday as day of the week on which the backup will occur. In the Options area on the Repeat tab, to make a weekly interval, enter a 1 in the Interval box meaning there is one week between each occurrence. Also, enter some number of repetitions, such as 52 for an entire year. This specifies how many weeks in a row the backup will occur. On the Options tab, notice the options. Click the Save button when you are finished. You should now see the Customized Scheduled Operations window and your entry should be listed in the window.
__ 3. Delete your scheduled backup operation. In the Customized Scheduled Operations window, select the operation you just created, choose Options on the menu and choose Delete.
HMC Corrective Service

__ 4. Find the current HMC software version on your HMC. View this on the Licensed Internal Code -> HMC Code Update application. Look in the Status area of the screen.
__ 5. If your lab system has Internet access, use a Web browser to go to this Web site: https://www14.software.ibm.com/webapp/set2/sas/f/hmc Find the latest HMC version information. You should be on the Corrective service tab. Click the Downloads link. Notice the Readme column. You can click the View link in the Readme column for specific information about the fix and instructions on how to install it.
Managed System Licensed Internal Code updates

__ 6. Use the HMC to find the firmware release and service pack level on your managed system. View this on the Licensed Internal Code Maintenance -> Licensed Internal Code Updates application. Click the Change licensed internal code for the current release option.
12-3
In the pop-up window, choose your managed system. There is probably only one choice. If there is more than one, then this HMC is managing more than one system. You will need to know the system type, model, and serial number for the appropriate managed system. In the next pop-up window, choose View system information. In the next pop-up window, choose None and click OK. The next window to open should look like the example shown below. (Be patient. It takes a minute to open.) The firmware release for this example system is 240 and the service pack level is 261.
__ 7. In you have access to the Internet, open a browser and find out if there is a more recent firmware release or service pack level for your managed system. The Web site is: http://www14.software.ibm.com/webapp/set2/firmware. PLEASE DO NOT LOAD ANY FIXES. Go to the Web page and for the purposes of this exercise, use the first option and search by machine type and model. For example, search on 9131-52A or 9111-520. A new fix might be listed as SF240_261. This tells us that the release matches our example system (240), and that we are at the latest fix (261). Here is what you might see:
Click the Desc link for a fix to see more information.
V3.1.0.1
EXempty
System Planning Tool

In this section of the exercise, you will create a system plan and import it into your HMC. Note: The SPT tool only runs on Windows PCs, so if your student workstations are AIX 5L or Linux-based, then you will not be able to complete the rest of this exercise. If this is the case, let your instructor know that you have completed the lab exercise. __ 8. The SPT planning tool should be loaded on your student workstation already. Look for an icon on your desktop or ask your instructor if it is loaded. If it is not, and you have access to the Internet, go to http://www.ibm.com/servers/eserver/support/tools/systemplanningtool and download and install SPT.
__ 9. Start the SPT tool. When it opens, click the Create a new system plan link. On the next screen, make sure the Create a new system (advanced) radio button is selected and click Next. Go through the SPT panels and save a system plan that is compatible with your managed system. You can save it to your student workstation. The goal is to create a system plan that could be imported to your HMC. Here is an System Type screen with example entries:
On the next screen, choose descriptions for partitions that would be compatible on your system. Then, click Next. For example:
12-5
On the next screen, configure the processor resources and then click Next. For example:
Configure the memory and virtual I/O resources on the next screen and click Next. For example:
V3.1.0.1
EXempty
On the system virtual adapters screen, specify slots for the virtual adapters. You can simply use the defaults if you wish. Then click Next. For example:
Check over the settings on the System Summary page, then click Finish. Next, you will see a screen like the following. Notice the Not valid message under planning steps. You need to now specify the I/O slots for the partitions.
12-7
Click the Place hardware link. On the next screen, there is a list of controllers on the left. As you click each one, it shows you the valid positions for the controller in the PCI-X slots. Configure the partitions with a few I/O slots. Do not worry about the red (bad) validation messages because we can plan to have disk and network requirements met by using virtual devices. Click the OK button at the bottom when you are done configuring I/O slots. Click the Save option at the top of the window. Save the file to your student workstation.
__ 10. Next, ftp the system plan file to one of your LPARs. (You can also close the SPT tool window if it is still open.) Put the *.sysplan file in a place you can find it, for example, C:\Documents and Settings\Administrator. Bring up a Command Prompt window and if necessary cd to that directory. Type ftp followed by the IP address of your LPAR. Log in as root. Use the following FTP command to copy the file to your LPAR. The file name in this example is file.sysplan. ftp> put file.sysplan ftp> bye
__ 11. In your WebSM remote client, go to the System Plans application and import your system plan. Click Import System Plan. Enter the host name, user ID, and password for the partition to which you copied the *.sysplan file. Enter the name of the directory that contains the file and click Import. Here is an example screen that was successful:
V3.1.0.1
EXempty
__ 12. Shut down all partitions on your managed system. (Otherwise, you will receive an error that there are partitions running.)
__ 13. Go to the Managed System Plan task and deploy the system plan from there. It is likely that you will get an error that the deployment failed. This is because the hardware that you choose for your system in the SPT tool must match the hardware on your actual system. You performed all of the steps to nearly deploy the plan on your lab system. Back in your own lab, you will need to know the exact processor feature and I/O hardware that is in your system to deploy system plans. Click the Manage System Plan link. You should see your sysplan file listed. Select it. Click the Deploy... button. This will start the Deploy System Plan wizard program. Click Next twice to start the deployment.
__ 14. Let your instructor know that you have completed the exercise. This is the final unit and exercise for this course.
End of exercise
12-9
V4.0
backpg
Back page

A60 LPARVirtual Xstudhint

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

A60 LPARVirtual Xstudhint

Transféré par

Droits d'auteur :

Formats disponibles

V4.

System p LPAR and Virtualization I: Planning and Configuration

Student Exercises with Hints

IBM Certified Course Material

Student Exercises with Hints

March 2007 edition

Copyright IBM Corp. 2004, 2007

Student Exercises with Hints

System p LPAR and Virtualization I

Copyright IBM Corp. 2004, 2007

Copyright IBM Corp. 2004, 2007

Student Exercises with Hints

System p LPAR and Virtualization I

Copyright IBM Corp. 2004, 2007

Copyright IBM Corp. 2004, 2007

Student Exercises with Hints

System p LPAR and Virtualization I

Copyright IBM Corp. 2004, 2007

Exercise 1. Documentation Discovery

What You Should Be Able to Do

Copyright IBM Corp. 2004, 2007

Exercise 1. Documentation Discovery

Student Exercises with Hints

Exercise Instructions with Hints

Access IBM Systems hardware and AIX 5L documentation

System p LPAR and Virtualization I

Copyright IBM Corp. 2004, 2007

Student Exercises with Hints

System p LPAR and Virtualization I

Copyright IBM Corp. 2004, 2007

Exercise 2. System Hardware Components

What You Should Be Able to Do

Copyright IBM Corp. 2004, 2007

Exercise 2. System Hardware Components

Student Exercises with Hints

Exercise Instructions with Hints

Gather System Information

System p LPAR and Virtualization I

Copyright IBM Corp. 2004, 2007

Copyright IBM Corp. 2004, 2007

Exercise 2. System Hardware Components

Student Exercises with Hints

Physical and Logical Location Codes

System p LPAR and Virtualization I

Copyright IBM Corp. 2004, 2007

__ c. Identify how many processor(s) your partition is using.

Copyright IBM Corp. 2004, 2007

Exercise 2. System Hardware Components

Student Exercises with Hints

System p LPAR and Virtualization I

Copyright IBM Corp. 2004, 2007

Exercise 3. HMC Configuration

What You Should Be Able to Do

Copyright IBM Corp. 2004, 2007

Exercise 3. HMC Configuration

Student Exercises with Hints

Exercise Instructions with Hints

Student Exercises with Hints

In the search window, enter the string server setup.

Copyright IBM Corp. 2004, 2007

Exercise 3. HMC Configuration

Student Exercises with Hints

System p LPAR and Virtualization I