Manually Creating VIOS NIM Resources
After having many problems attempting to use installios, the following steps were used to build the necessary NIM resources to allow the installation of IBM's Virtual I/O Server: First, define shell variables pointing to the mounted CD or copied CD contents, and the destination for the NIM objects:
# SRC=/junk/vios-1.2-cd # DST=/csminstall/eznim/vios-1.2
Define NIM client. Substitute appropriate client name, ethernet hardware address, interface name, cable type, subnet mask, client gateway and speed/duplex:
# > > > nim -o define -t standalone -a if1="find_net CLIENTNAME 000a0b0c0d0e ent1" \ -a cable_type1=N/A \ -a netboot_kernel=mp -a net_definition="ent 255.255.255.0 192.168.0.1" \ -a net_settings1="100 half" CLIENTNAME
Define NIM mksysb:
# mkdir ${DST}/mksysb # cp ${SRC}/nimol/ioserver_res/mksysb ${DST}/mksysb/installios_mksysb # nim -o define -t mksysb -a server=master -a location=${DST}/mksysb/installios_mksysb \ > installios_mksysb
Define NIM bundle:
# mkdir ${DST}/bundle # cp ${SRC}/installp/ppc/en_US.bnd ${DST}/bundle # nim -o define -t installp_bundle -a server=master -a location=${DST}/bundle/en_US.bnd \ > installios_bundle
Define NIM lppsource:
# mkdir ${DST}/lpp_source # gencopy -X -d ${SRC}/installp/ppc -t ${DST}/lpp_source/installios_lpp_source \ > $(/usr/bin/cat ${DST}/bundle/en_US.bnd) # nim -o define -t lpp_source -a server=master \ > -a location=${DST}/lpp_source/installios_lpp_source \ > -a source=${DST}/lpp_source/installios_lpp_source installios_lpp_source Preparing to copy install images (this will take several minutes)... 0503-114 gencopy: RPM Product cdrecord* does not exist.
Manually Creating VIOS NIM Resources
0503-114 gencopy: RPM Product mkisofs* does not exist. Now checking for missing install images... warning: 0042-265 c_mk_lpp_source: The image source "/csminstall/eznim/vios1.2/lpp_source/installios_lpp_source" that was used to define the lpp_source is missing one or more of the following from the list of default packages: bos.64bit bos bos.acct ... warning: 0042-267 c_mk_lpp_source: The defined lpp_source does not have the "simages" attribute because one or more of the following packages are missing: bos bos.net bos.diag ...
Define NIM VIOS SPOT resource:
# mkdir ${DST}/spot # nim -o define -t spot -a location=${DST}/spot -a server=master \ > -a source=installios_mksysb installios_spot Creating SPOT in "/csminstall/eznim/vios-1.2/spot" on machine "master" from "installios_mksysb" ... Restoring files from BOS image. This may take several minutes ...
Checking filesets and network boot images for SPOT "installios_spot". This may take several minutes ...
Define NIM bosinst:
# cp ${SRC}/nimol/ioserver_res/bosinst.data ${DST}/installios_bosinst.data # nim -o define -t bosinst_data -a server=master -a location=${DST}/installios_bosinst.data \ > installios_bosinst
Configure NIM ready for client install:
# nim -o bos_inst -a source=mksysb -a spot=installios_spot -a mksysb=installios_mksysb \ > -a bosinst_data=installios_bosinst -a boot_client=no CLIENTNAME
Manually Creating VIOS NIM Resources
warning: 0042-360 m_bos_inst: The SPOT level is older than the mksysb level. Therefore, the BOS installation may encounter problems. Update the SPOT to match the mksysb level or create a new SPOT that has the same level.
Now, the LPAR may be net booted via any method (eg. SMS via HMC).
Security
Access Control: You must have root authority to run the lpar_netboot command.
Examples
1. To retrieve MAC address and physical location code for partition machA with a partition profile machA_prof on a managed system test_sys, type:
lpar_netboot -M -n -t ent "machA" "machA_prof" "test_sys"
2.
To network boot partition machA with a partition profile machA_prof on a managed system test_sys, type: lpar_netboot -t ent -s auto -d auto -S 9.3.6.49 -G 9.3.6.1 -C 9.3.6.234 "machA" "machA_prof" "test_sys" To network boot partition machA with a specific MAC address of 00:09:6b:dd:02:e8 and a partition profile machA_prof on a managed system test_sys, type: lpar_netboot -t ent -m 00096bdd02e8 -s auto -d auto -S 9.3.6.49 -G 9.3.6.1 -C 9.3.6.234 "machA" "machA_prof" "test_sys" To network boot partition machA with a specific physical location code of U1234.121.A123456P1-T6 and a partition profile machA_prof on a managed system test_sys, type: lpar_netboot -t ent -l U1234.121.A123456-P1-T6 -s auto -d auto -S 9.3.6.49 -G 9.3.6.1 -C 9.3.6.234 "machA" "machA_prof" "test_sys" To perform a ping test and a network boot of partition machA with a partition profile machA_prof on a managed system test_sys, type: lpar_netboot -t ent -D -s auto -d auto -S 9.3.6.49 -G 9.3.6.1 -C 9.3.6.234 "machA" "machA_prof" "test_sys"
3.
4.
5.
Manually Creating VIOS NIM Resources
Location
/usr/sbin/lpar_netboot
Manually Creating VIOS NIM Resources
Installing the Virtual I/O Server using NIM
You can use the following procedures to install the Virtual I/O Server into environments managed by the HMC or Integrated Virtualization Manager using Network Installation Management (NIM).
Prerequisites
You need the following files before beginning this procedure. These files are located on the Virtual I/O Server installation media: nimol/ioserver_res/mksysb (the mksysb image)
In addition, the following system requirements must be met: A system running AIX 5.3 with 5300-03 or higher, which contains a file system with at least 700 MB available. A logical partition of type Virtual I/O Server containing an Ethernet adapter connected to an active network for installing the Virtual I/O Server. For information about creating logical partitions, see Creating the Virtual I/O Server logical partition and partition profile. A storage controller containing at least 16 GB of disk space.
After the prerequisites have been met, follow these steps to use NIM to install the Virtual I/O Server: 1. 2. Insert the Virtual I/O Server DVD into the DVD drive. Run the installios command without any arguments to start the installation wizard. The installios wizard then guides you through the process of filling-out the necessary information to start an installation on the Virtual I/O Server or on a Integrated Virtualization Manager. If you run installios on a NIM client, then you are prompted for the location to the bos.sysmgt.nim.master fileset. The NIM client is then configured as a NIM master. For more information about command-line usage of installios, see the installios command. The installios setup process creates the following NIM resources to start the installation: bosinst_data installp_bundle lpp_source mksysb resolv_conf SPOT Client definition
Manually Creating VIOS NIM Resources
If you are installing the Virtual I/O Server logical partition, and if Secure Shell (SSH) and credentials have been configured on the NIM master, then the partition is network-booted from the Hardware Management Console (HMC) to begin the installation. If you are installing the Virtual I/O Server logical partition without SSH, or if you are installing the Integrated Virtualization Manager, then go to step 3. 3. On the system on which the Virtual I/O Server software will be installed, boot the Virtual I/O Server logical partition or the Integrated Virtualization Manager into System Management Services (SMS) mode by following these steps: a. b. To boot the Virtual I/O Server logical partition into SMS: On the HMC, right-click the partition to open the menu. Click Activate. The Activate Partition menu opens with a selection of partition profiles. Be sure the correct profile is highlighted. c. Select the Open a terminal window or console session check box to open a virtual terminal (vterm) window. d. e. f. g. h. i. j. k. Click (Advanced...) to open the advanced options menu. For the Boot mode, select SMS. Click OK to close the advanced options menu. Click OK. A vterm window opens for the partition. In the vterm window, select Setup Remote IPL (Initial Program Load). Select the network adapter that will be used for the installation. Select IP Parameters. Enter the client IP address, server IP address, and gateway IP address. Optionally, you can enter the subnet mask. After you have entered these values, press Esc to return to the Network Parameters menu. l. Select Ping Test to ensure that the network parameters are properly configured. Press Esc twice to return to the Main Menu. m. n. o. p. From the Main Menu, select Select Boot Options. Select Select Install/Boot Device. Select Network. Select the network adapter whose remote IPL settings you previously configured. q. When prompted for Normal or Service mode, select Normal.
Manually Creating VIOS NIM Resources
r. a. b. When asked if you want to exit, select Yes. To boot the Integrated Virtualization Manager into SMS: Begin with the machine turned off. Switch on the machine, and as icons begin to appear from left to right on the bottom of your display, press F1. Note: If the last icon is displayed before pressing F1, then you get the normal mode boot list instead of SMS, so try again. c. d. The System Management Services menu opens. Select Utilities. From the System Management Services Utilities menu, select Remote Initial Program Load Setup. e. f. From the Network Parameters panel, select IP Parameters. Set or change the displayed values so they are correct for your client system. Specify the IP address of the following: g. The client machine you are booting in the client address field. Your NIM master server in the server address field. Your client's gateway in the gateway address field. Your client's subnet mask in the subnet mask field. After you specify the addresses, press Enter to save the addresses and continue. h. i. j. The Network Parameters window opens. Select the Ping option. Select the network adapter to be used as the client's boot device. Verify that the displayed addresses are the same as the addresses you specified for your boot device. If the addresses are incorrect, press Esc until you return to the main menu. Then, go back to step e. If they are correct, continue with k. k. If the addresses are correct, press Enter to perform the ping test. The ping test might take several seconds to complete. l. If the ping test fails, verify that the addresses are correct, and analyze the network problem. If the ping test is successfull, press Enter to acknowledge the success message. m. n. Press Esc until you return to the System Management Services menu. From the System Management Services menu, choose the Select Boot Devices option.
Manually Creating VIOS NIM Resources
o. Select the network adapter to be used for the network boot from the list of displayed bootable devices After the installation is complete, the Virtual I/O Server logical partition or the Integrated Virtualization Manager is ready to be configured and managed. To remove all the NIM resources that were created from the installios setup process, run the installios command with the -u flag. If the installios command fails to perform the cleanup, run installios -u and specify the -f flag to force NIM to reset and deallocate resources to the client. This still leaves the NIM environment, but removes all resources and directory structures created from the installios wizard. If, however, you want to unconfigure NIM, or to uninstall the bos.sysmgt.nim.master fileset and return the NIM master back to a NIM client if it was configured from a NIM client, specify installios -u with a -U flag. You can also install a Virtual I/O Server or a Integrated Virtualization Manager through the SMIT interface. Run smitty installios to get access to the SMIT interface to the installios command. When invoked on a NIM master, the administrator will have access to two options to Setup for Virtual I/O and Integrated Virtualization Manager Installation and Cleanup after Virtual I/O and Integrated Virtualization Manager Installation, where Configure Client as Master for Virtual I/O and Integrated Virtualization Manager Installation is the only available option on a NIM client. Then fill out the specific fields as required from the installios wizard to invoke the installios command to setup the environment to initiate the installation, or to perform a cleanup.