Provisioning process for AIX

For provisioning IBM AIX servers, the BMC Server Automation system uses IBM Network Installation Manager (NIM) software. This topic describes the phases of provisioning with NIM.

BMC Server Automation provisioning integrates with existing NIM environments for remote provisioning. Key NIM resources used in the provisioning process include Shared Product Object Tree (SPOT), lpp_source, mksysb, script, fb_script, resolve_conf, and bosinst_data.

Click the thumbnail below for a full-size image depicting the provisioning process.

The following numbered steps correspond to numbers in the image shown above.

1. Create system package and data store instance, import device, and run Provision Job:
   • Create a system package that contains all the instructions needed to install an operating system over the network.
   • Create a data store instance that points to the location of a data store, which is where you store sets of installation files that are used for provisioning operating systems.
   • Register the target device's MAC address (and optional additional information) with the BMC Server Automation system by importing the device.
   • Create and run the Provision Job.
2. Reboot the target
   Connect to the service console (HMC) on the AIX target and boot the target to the SMS menu. From the SMS menu, configure the IPL settings to point at the NIM master. Then boot the target to the network.
3. Target contacts NIM master
    The AIX target contacts the NIM master for its base operating system installation instructions.
4. NIM master begins OS installation
    The NIM master begins the base OS installation as defined by the files shipped to the NIM master by the BMC Server Automation Application Server.
5. Application Server monitors OS installation
    The BMC Server Automation Application Server monitors the base operating system installation job on the NIM master and moves the target to "provisioned" on its completion.
6. Target reboots to new OS
    The AIX target reboots and comes up to the new operating system, or to the SMS menu, from which you can then boot it to the new operating system.
    Optionally, the NIM master installs the RSCD agent, which is necessary for managing the server with BMC Server Automation. A registration event occurs to enter the target machine's information into the BMC Server Automation system so the server can be managed from the BMC Server Automation Console.
7. Provisioning runs Batch Job for additional configuration
    Optionally, the provisioning process can run a job that performs additional configuration of the target machine. For example, a Batch Job can install and configure all necessary applications on the target machine.