Join / Log in
Starting system management services without an HMCTo get a boot console, you have to access the ASMI, seeWhat is Service Processor And How To Access ItASMI (Advanced System Management Interface)If you have access to the console of the LPAR, you start the LPAR and while the "IBM IBM IBM" messages are displayed,you hit the 1 on the keyboard to access the SMS menu.The SMS menu is the BIOS of the LPAR, here you can select your boot device.Example Using SMS To Choose Boot DeviceInstallation from USB seehttps://www.ibm.com/support/knowledgecenter/ssw_aix_71/rnbase715/rnbase715.html
Chapter "Installing AIX using a USB flash memory stick"
The initial question was "In 1 disk he install AIX 7.1 and in other disk he install AIX 7.2. Now he will boot AIX 7.1 sometime and AIX 7.2 in some other time."
and "Would they be able to install AIX from a USB drive and avoid the need for the DVD drive in the configuration ?".So, no need for alt_rootvg. Simply select the correct adapter and boot device in the SMS menu. And installation of AIX from USB runs on the same way, see
Using and taking advantage from USB devices and AIX. Just download the AIX flash image from IBM, put it on the stick by "dd", assign the USB adapter to the LPAR and select the USB adapter in the SMS menu (SMS=system management services).The SMS menu appears after starting the LPAR in the console of the LPAR by pressing the 1 key as the LPAR boot logo comes up:IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM1 = SMS Menu 5 = Default Boot List
Press the 1 key multiple times when you see the above line, else the boot continues !
As we use HMCs, I don't know how to access the AIX console with ASMI, but there is an IBM description of this:https://www.ibm.com/support/knowledgecenter/POWER6/iphb6/startsms_asmi.htmsaying:If you have are not using an HMC to start the system management services, complete one of the following tasks:
BTW: an inactive rootvg that's not made by alt_rootvg install can be accessed (as every other inactive VG) by importvg. The only point is not to access a filesystem while its active otherwise. That's what a maintenance boot does too.
Yes, I was wrong, sorry.
So the only way to access a non-alt_rootvg seems the maintenance boot by network, DVD or USB (with an AIX level even or higher as the accessed rootvg).
Achim,>So the only way to access a non-alt_rootvg seems the maintenance boot by network, DVD or USB (with an AIX level even or higher as the accessed rootvg).Or.. boot from this disk in normal mode. It's really the rootvg, it's bootable, I don't see any problems with it.Don't think about the VG name. It's just a label in the ODM. Do you know that:-there is the information about the filesystem name in the LV structure (LVCB) on the disk;-there is the information about the LV name in the VG structure (VGDA) on the disk;-but there is NO information about the VG name on this disk, i.e. VG don't know it's own name!What happens when AIX boots? In simple words, firmware load the kernel from the specified disk sector; then the kernel "decides":"OK, I am an AIX kernel, I've just booted from some hdisk. So there should be VG on this disk; the VG name should be ROOTVG, because it's a rule"and reads the rest VG-realted information from the VGDA.To AIX experts: I've described the part of AIX boot progress in simple terms; I know that I've missed a lot.