Setting up virtualization: the basics

Transcription

1 3 Chapter 3. Setting up virtualization: the basics This chapter introduces the basics of configuring a virtual environment on an IBM System p server. The Virtual I/O Server installation and configuration is covered in its entirety and a basic scenario of configuring a Virtual I/O Server along with deploying client partitions is also demonstrated. The topics include: Getting started Creating a Virtual I/O Server partition Virtual I/O Server software installation Basic Virtual I/O Server scenario Interaction with UNIX client partitions Using the System Planning Tool for deployment Using system plans to document the configuration Copyright IBM Corp. 2004, 2005, 2007, All rights reserved. 135

2 3.1 Getting started This section provides the following information about the operating environment of the Virtual I/O Server: 3.1.1, Command line interface on page 136 of the Virtual I/O Server, also named the IOSCLI 3.1.2, Hardware resources managed on page , Software packaging and support on page Command line interface The Virtual I/O Server provides a restricted, scriptable command line interface (IOSCLI). All Virtual I/O Server configurations should be made on this IOSCLI using the restricted shell provided. Important: Only supported 3rd party storage configuration should be done under the oem_setup_env shell environment. The cfgassist command offers smit menus for common configuration tasks, as shown in Figure 3-1. Figure 3-1 The Config Assist for VIOS menu 136 PowerVM Virtualization on IBM System p: Introduction and Configuration

3 The following Virtual I/O Server administration activities are done through the Virtual I/O Server command line interface: Device management (physical and virtual) Network configuration Software installation and update Security User management Installation of OEM software Maintenance tasks For the initial login to the Virtual I/O Server, use the padmin user ID, which is the primary administrator. Upon login, a password change is required. There is no default. Upon logging into the Virtual I/O Server, you will be placed into a restricted Korn shell, which works the same way as a regular Korn shell with some restrictions. Specifically, users cannot do the following: Change the current working directory. Set the value of the SHELL, ENV, or PATH variable. Specify the path name of the command that contains a redirect output of a command with a >, >, <>, or >. As a result of these restrictions, you are not able to run commands that are not accessible to your PATH variable. These restrictions prevent you from directly sending the output of the command to a file, requiring you to pipe the output to the tee command instead. After you are logged on, you can enter the help command to get an overview of the supported commands, as in Example 3-1. Example 3-1 Supported commands on Virtual I/O Server Version 1.5 $ help Install Commands ioslevel license lssw oem_platform_level oem_setup_env remote_management updateios Security Commands lsfailedlogin lsgcl viosecure mkldap ldapadd ldapsearch snmpv3_ssw mkkrb5clnt Chapter 3. Setting up virtualization: the basics 137

4 LAN Commands cfglnagg cfgnamesrv entstat fcstat 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 UserID Commands chuser lsuser mkuser passwd rmuser Maintenance Commands alt_root_vg backup backupios bootlist cattracerpt chdate chlang cfgassist cl_snmp dsmc diagmenu errlog fsck invscout ldfware loginmsg lsfware lslparinfo motd mount pdump replphyvol restore restorevgstruct save_base savevgstruct showmount shutdown snap snmp_info snmp_trap startsysdump starttrace stoptrace svmon sysstat 138 PowerVM Virtualization on IBM System p: Introduction and Configuration

5 mklvcopy rmlv rmlvcopy Volume Group Commands activatevg chvg deactivatevg exportvg extendvg importvg lsvg mirrorios mkvg redefvg reducevg syncvg unmirrorios Storage Pool Commands chbdsp chsp lssp mkbdsp mksp rmbdsp rmsp Virtual Media Commands chrep chvopt loadopt lsrep lsvopt mkrep mkvopt rmrep rmvopt unloadopt topas uname unmount viostat vmstat wkldmgr wkldagent wkldout Monitoring Commands cfgsvc lssvc startsvc stopsvc Shell Commands awk cat chmod clear cp crontab date ftp grep head ls man mkdir more mv rm sed stty tail tee vi wall wc who Chapter 3. Setting up virtualization: the basics 139

6 To receive further help about these commands, use the help command, as shown in Example 3-2. Example 3-2 Help command $ help errlog Usage: errlog [[ -ls][-seq Sequence_number] -rm Days]] Displays or clears the error log. -ls -seq -rm Displays information about errors in the error log file in a detailed format. Displays information about a specific error in the error log file by the sequence number. Deletes all entries from the error log older than the number of days specified by the Days parameter Hardware resources managed The PowerVM feature (Standard or Enterprise) that enables Micro-Partitioning on a server provides the Virtual I/O Server installation media. A Virtual I/O Server partition with dedicated physical resources to share to other partitions is also required. The following minimum hardware requirements must be met to create the Virtual I/O Server: POWER5 or POWER6 server The Virtual I/O capable machine. Hardware Management Console or IVM Storage adapter Physical disk Ethernet adapter Memory The HMC is needed to create the partition and assign resources or an installed IVM either on the predefined partition or pre-installed. The server partition needs at least one storage adapter. If you want to share your disk to client partitions, you need a disk large enough to make sufficient-sized logical volumes on it. This adapter is needed if you want to allow securely routed network traffic from a virtual Ethernet to a real network adapter. At least 512 MB of memory is required. Similar to an operating system, the complexity of the I/O subsystem and the number of the virtual devices have a bearing on 140 PowerVM Virtualization on IBM System p: Introduction and Configuration

7 the amount of memory required, such as when using multiple paths to SAN storage devices. The Virtual I/O Server is designed for selected configurations that include specific models of IBM and other vendor storage products. Consult your IBM representative or Business Partner for the latest information and included configurations. Virtual devices exported to client partitions by the Virtual I/O Server must be attached through supported adapters. An updated list of supported adapters and storage devices is found at: Careful planning is recommended before you begin the configuration and installation of your Virtual I/O Server and client partitions. Depending on the type of workload and needs of an application, it is possible to mix virtual and physical devices in the client partitions Software packaging and support Installation of the Virtual I/O Server partition is performed from a special DVD-ROM that is provided to clients that order the PowerVM feature. For the p5-590 and p5-595, this feature is included. The Virtual I/O Server software is only supported in Virtual I/O Server partitions. The Virtual I/O Server DVD-ROM installation media can be installed in the following ways: Media (assigning the DVD-ROM drive to the partition and booting from the media). The HMC (inserting the media in the DVD-ROM drive on the HMC and using the installios command). Using the DVD-ROM media together with the NIM server and executing the smitty installios command (the secure shell needs to be working between NIM and HMC). NIM by copying the DVD-ROM media to the NIM server and generating NIM resources for installation. Chapter 3. Setting up virtualization: the basics 141