This procedure describes how to add standalone clients to the NIM environment. Standalone clients are machines that, once installed, can obtain a boot image and mount all file systems from the local hard disk, unlike diskless and dataless clients which depend on remote servers.
From one of the following interfaces, use Method A if the client machine is not running or if the client does not have AIX installed. Method A can also be used if BOS is to be installed on the client and the client is to be network-booted manually or to initiate the install from a force-push operation. This procedure automatically adds NIM networks when needed.
From one of the following interfaces, use Method B if the client machine has AIX already installed.
If the NIM client being defined is on a network that is not currently defined in the NIM environment, the niminit command will fail. If this is the case, use Method A: of this procedure to define the client on the NIM master, and then follow the steps in Method B: to complete the configuration.
wsm
# lslpp -L bos.sysmgt.nim.client
# installp -acXd /dev/cd0 bos.sysmgt.nim.client
On the NIM master, enter:
# nim -o define -t standalone -a platform=PlatformType \ -a netboot_kernel=NetbootKernelType \ -a if1=InterfaceDescription \ -a net_definition=DefinitionName -a ring_speed1=SpeedValue \ -a cable_type1=TypeValue -a iplrom_emu=DeviceName MachineName
Example 1:
To add the machine with host name machine1 with the following configuration:
host name=machine1 platform=chrp kernel=up network type=ethernet subnet mask=255.255.240.0 default gateway=gw1 default gateway used by NIM master=gw_master cable type=bnc network boot capability=yes (no emulation needed)
enter the following command sequence:
# nim -o define -t standalone -a platform="chrp" \ -a netboot_kernel="up" -a if1="find_net machine1 0" \ -a cable_type1="bnc" \ -a net_definition="ent 255.255.240.0 gw1 gw_master" machine1
Example 2:
To add the machine with host name machine2 with the following configuration:
host name=machine2 platform=chrp netboot_kernel=up network type=token ring subnet mask=255.255.225.0 default gateway=gw2 default gateway used by NIM master=gw_master ring speed=16
enter the following command sequence:
# nim -o define -t standalone -a platform="chrp" \ -a netboot_kernel="up" -a if1="find_net machine2 0" \ -a ring_speed1="16" \ -a net_definition="tok 255.255.225.0 gw2 gw_master" machine2
# niminit -a name=ClientDefinitionName -a master=MasterName \ -a pif_name=Interface -a platform=PlatformType \ -a netboot_kernel=NetbootKernelType -a ring_speed1=SpeedValue \ -a cable_type1=TypeValue -a iplrom_emu=DeviceName
Example 1:
To add the machine with host name machine1with the following configuration:
host name=machine1 NIM master's host name=master_mac primary interface adapter=en0 platform=chrp kernel=up cable type=bnc network boot capability=yes (no emulation needed)
enter the following command sequence:
# niminit -a name=machine1 -a master=master_mac \ -a pif_name=en0 -a platform=chrp -a netboot_kernel=up \ -a cable_type1=bnc
Example 2:
To add the machine with host name machine2 with the following configuration:
host name=machine2 NIM master's host name=master_mac primary interface adapter=tr0 platform=chrp netboot_kernel=up ring speed1=16
enter the following command sequence:
# niminit -a name=machine2 -a master=master_mac \ -a pif_name=tr0 -a platform=chrp -a netboot_kernel=up \ -a ring_speed1=16
To verify that the niminit operation completed successfully, enter the following command at the NIM client:
# nimclient -l -l MachineObjectName
The system returns output similar to the following:
Standalone2: class = machines type = standalone Cstate = ready for a NIM operation platform = chrp netboot_kernel = up if1 = Network2 standalone2 08005acd536d cable_type1 = bnc iplrom_emu = /dev/fd0 prev_state = customization is being performed cpuid = 000247903100 Mstate = currently running Cstate_result = success
If the system output to this query indicates any errors, you must validate all of your data, checking for accurate spelling, nonduplication of NIM names, and so forth, and redo the niminit operation.
Be sure to coordinate this operation with the system administrator of the NIM master, and ensure that all NIM object names are unique in the entire NIM environment.