Configuring the NIM master and creating basic installation resources using SMIT

Edit online

Use this procedure for configuring the NIM master and creating basic installation resources using SMIT.

  1. Insert the AIX® Volume 1 media into the appropriate drive of the designated master machine.
  2. To install the bos.sysmgt.nim.master fileset, enter the smit install_latest fast path.
  3. Using the LIST option, select /dev/cd0 for the INPUT device/directory for software.
  4. Specify bos.sysmgt.nim.master as the SOFTWARE to install.
  5. Accept the default values for all other fields on this screen. After successful completion of this installation, exit SMIT.
  6. To configure the NIM master, enter the smit nim_config_env fast path.
  7. Using the LIST option, select the Primary Network Interface for the NIM Master.
  8. Using the LIST option, select /dev/cd0 for the Input device for installation / images field.
  9. If you will be supporting diskless and dataless clients, select yes at the Create Diskless/Dataless Machine Resources? field, and supply names for the resources to be created.
  10. Select yes at the Remove all newly added NIM definitions and file systems if any part of this operation fails? field. This will make it easier to restart this procedure if failures occur.
  11. Accept the default values for all other fields on this screen.
Notes:
  1. Depending on the speed of your machine, creating the basic NIM resources could be a lengthy process.
  2. This procedure provides the capability for much more than just configuring the NIM master and creating the lpp_source and SPOT resources. However, for this simple configuration, only a subset of the available functions will be used. Advanced NIM administrators can use the SMIT screens accessed through this procedure to create a more complex environment.
  3. As you develop a better understanding of configuration tasks, you may prefer to not automatically undo all configuration when failures occur (as in step 10 in the previous procedure). Continuing from the last point of failure results in faster configuration for experienced administrators.