Note: The information contained in this article is structured as help information for the System Management Interface Tool (SMIT) and is not intended for use as a procedural or conceptual article.
Lists the menus for installing the Base Operating System (BOS) and optional software in a network environment. Network Install Management (NIM) manages the installation of standalone machines and the initialization of diskless and dataless machines.
Continue to the next level of SMIT for more information.
Configures the Network Install Management (NIM) master file set on the system you have designated as the master.
Continue to the next level of SMIT to specify the values necessary to begin configuration.
Note: You must have root user authority to configure the NIM master file set.
Specifies the unique identifier you wish to name the object that NIM creates to represent the network that the master's primary interface connects to. Once this object has been created, the name you specify identifies the network in all subsequent NIM operations. NIM does not correlate this name with any physical characteristics that the network might have. You can use any name you like and you should choose a name which is meaningful to you.
Note: There are some restrictions: The name cannot have more than 39 characters, and it cannot consist of any shell, file system, or regular expression meta characters.
The name of the network interface that the master will use as its primary interface. The primary interface identifies the network interface that the master uses to access NIM resources when performing install operations onto the master.
Specifies the port number for NIM network communications between the NIM master and its clients. For example, the port number might be 1058. Select a port number that is not being used. Check the /etc/services file for potential conflicts before selecting a port number.
Specifies the capacity of the Token-Ring network when the network interface is a Token-Ring (4MB or 16MB).
Specify the type of Ethernet cable. The possible values are dix for thick cable, bnc for thin cable, tp for twisted pair, or N/A for Not Applicable. The cable type should be specified only for Standard Ethernet (en) and IEEE 802.3 Ethernet (et) interfaces.
Lists a menu of operations that enable you to manage NIM networks. Operations include creating a network, changing or showing the characteristics of a network, removing a network, and managing routing information for a network.
Note: You must have root user authority to perform any of the network operations.
Lists all networks that have been defined in the NIM environment.
Adds a new network to the NIM database. Each time a network is added to the NIM environment an object representing the network is created in the NIM database.
Continue to the next level of SMIT to specify the type of network you want to add.
Note: You must have root user authority to add a network.
Specifies the type of network you want to add to the NIM environment. Use the List function to display a list of network types.
Displays the type of the network you are adding to the NIM environment. Use the Cancel function to return to the previous screen if you want to change the network type.
Specifies the Internet Protocol (IP) address of the network you are adding to the NIM environment.
Specifies the subnetmask of the specified network you want to add to the NIM environment. A subnetmask is a set of four bytes.
Specifies any information you want to associate with the new network. Consider detailing certain aspects of the addition such as the date, time, or name of the user who created the network. The information you supply may be helpful to future administrators of the same NIM environment.
Displays the characteristics of the specified network and enables you to change some of the network's characteristics if desired.
Continue to the next level of SMIT to specify the name of the network.
Removes a network from the NIM database. You may want to remove a network because you are dissatisfied with the way it was created, or because you no longer want it as part of the NIM environment.
Continue to the next level of SMIT to specify the name of the network you want to remove.
Displays a menu of operations that enable you to manage NIM routing. Operations include listing the existing NIM routes, adding a NIM route, changing or showing the characteristics of a NIM route, and removing a NIM route.
Lists all routes connected to the specified network.
Continue to the next level of SMIT to specify the network name.
Enables the NIM target to boot over the network in system maintenance mode. The maintenance boot operation is set up, but the network boot must be initiated from the target.
Specifies whether the system backup image should be created during the definition of the mksysb resource.
YES indicates that the system backup image to be associated with this mksysb resource will be created as part of this operation.
NO indicates that the system backup image to be associated with this mksysb resource already exists.
Specifies the NIM name of the client to be backed up. This option may be specified only when a system backup image is being created.
Specifies whether the space requirements for the system backup image should be displayed.
When this field is set to YES, the maximum space required for the backup along with the space available is displayed. The mksysb resource is not defined, and the system backup image is not created.
Specifies whether the space requirements for the system backup image should be ignored.
When this field is set to YES, the system image backup is attempted regardless of how much space is available in the target file system.
Specifies whether the system should generate a layout mapping of the logical-to-physical partitions for each logical volume in the root volume group. This mapping is used to allocate the same logical-to-physical partition mapping when the image is restored.
Specify the number of 512-byte physical blocks to write in a single output operation. The write size is the number of blocks multiplied by the block size.
Specifies whether the files and directories listed in the /etc/exclude.rootvg file on the NIM client should be excluded from the backup image being created.
When this field is set to YES, the files and directories listed in the /etc/exclude.rootvg file on the NIM client are excluded from the backup image. When this field is set to NO, all files are included in the backup.
Specifies that the files and directories listed in the file referenced by the exclude_files resource should be excluded from the backup image being created. Leave this field blank to include all files in the backup.
Specifies whether the system backup image should be removed along with the definition of the mksysb resource.
Specifies that port numbers other than the defaults should be used for communication between NIM master and client machines. If no port numbers are specified, the NIM port numbers (nim and nimreg) in the /etc/services file are used. If the nim and nimreg definitions do not exist in the /etc/services file, the following default values are used:
1059 Client Registration
1058 Client Communications.
Specifies the port number that NIM clients use to register themselves with the NIM master. Select a port number that is not currently in use. Check the /etc/services file for potential conflicts.
Specifies the port number for network communications between the NIM master and its clients. Select a port number that is not currently in use. Check the /etc/services file for potential conflicts.
Adds a NIM route to the network you specify. NIM routes are added to networks to enable NIM to determine the connectivity between NIM machines. Continue to the next level of SMIT to specify the network name.
Specifies the network that responds to communications initiated by the originating network.
Specifies whether to override NIM state checking. The default for this field is no.
If the operation fails due to the state of a NIM object, the state can be overridden in some cases by using the force flag.
Displays the characteristics of the specified NIM route and enables you to change some of the NIM route's characteristics if desired.
Routes are added between networks to enable NIM to determine connectivity between NIM machines.
Continue to the next level of SMIT to specify the NIM route whose characteristics you want to view or change.
Identifies the NIM route whose characteristics you want to view or change.
Specifies the name of the network to which the NIM route is connected.
Use the List function to display a list of network names.
Specifies the host name of the gateway used by the originating network to communicate with the specified destination network.
Removes a route from the specified network. Continue to the next level of SMIT to specify the network name.
Note: If the route to the NIM master is removed from the network, the state of the network will become incomplete.
Specifies the NIM route to be removed.
Note: If the route to the NIM master is removed from the network, the state of the network becomes incomplete.
Displays a menu of operations that can be performed on NIM machines. Machine operations include adding a machine, changing or viewing the characteristics of a machine, and removing a machine.
Additional machine operations include managing network interfaces, managing resource allocation, and performing machine control actions.
Lists the machines currently defined in the NIM environment. A machine is created in the NIM database each time a machine is added to the NIM environment. Continue to the next level of SMIT to specify the machine configuration type.
Adds a machine of the specified configuration type to the NIM environment. Each time a machine is added to the NIM environment, an entry representing the machine is added to the NIM database.
Continue to the next level of SMIT to specify the machine's host name.
Specifies the hardware platform type for this machine.
Note: The hardware platform type cannot be changed after the machine is defined.
Specifies the unique name you give to a machine being added to the NIM environment. The name you specify must not contain any special characters, such as $, & <. >, *, and it must contain less than 21 characters. The machine name is used to identify the machine in all NIM operations.
Identifies the interface that the machine will use to access NIM resources. The primary install interface is composed of three to four fields and enables NIM to determine network connectivity between machines. Every machine must have a primary interface.
Specifies the host name of the machine's network interface.
Specifies the logical device name (for example, ent1, fddi2, tok3) of the network adapter that a client uses as its interface.
Identifies the ID of the central processing unit (CPU) of the machine you want to add to the NIM environment. The CPU ID is a number that can be displayed with the uname command.
Specifies information you want to associate with the machine you added to the NIM environment. Consider detailing certain aspects such as the date the machine was added, or the name of the user who added the machine. The information you supply may be helpful to future administrators of the same NIM environment.
Displays the characteristics of the specified machine and enables you to change some of these characteristics if desired. Continue to the next level of SMIT to specify the name of the machine.
Specifies the name of the machine whose characteristics you want to view or change. Use the List function to display a list of existing machine names.
Specifies the name of the machine whose characteristics you are changing or viewing. If you want to change the machine name, use the Cancel function to return to the previous menu.
Displays the execution state of the machine whose characteristics you are viewing or changing.
The shutdown state indicates the machine is in the process of halting or is turned off. The booting state indicates that the machine is in the process of booting, and the running state indicates the machine is ready for use. Note that NIM does not guarantee that these states will always reflect the true execution state of the machine.
Specifies the control state of the machine whose characteristics you want to view or change and reflects the NIM operation that is currently being performed on the machine.
Identifies the central processing unit (CPU) of the machine whose characteristics you want to view or change.
Removes a machine from the NIM environment. You may want to remove a machine because you are dissatisfied with the way it was created, or because you no longer want the machine to participate in the NIM environment.
Continue to the next level of SMIT to specify the name of the machine you want to remove.
Specifies the name of the machine you want to remove from the NIM environment. Use the List function to display the machine currently existing in the NIM environment.
Specifies the name of the machine you want to remove from the NIM environment. Use the Cancel function to return to the previous level if you want to choose a different machine.
Lists a menu of operations that enable you to manage NIM install interfaces. Operations include listing all NIM interfaces, creating a new NIM interface, changing or viewing a NIM interface, and removing a NIM interface.
NIM interfaces are used to facilitate communication between machines in the NIM environment.
Lists all network interfaces currently defined in the NIM environment that are connected to the specified machine. Continue to the next level of SMIT to specify the machine name.
Specifies the name of the machine whose network interfaces you want to list. Use the List function to display the existing machine names.
Adds a connection from a specified machine to a network, allowing the machine additional communication in the NIM environment.
Continue to the next level of SMIT to specify the name of the machine to which the network is to be connected.
Specify the name of the machine that has the network interface.
Displays the name of the machine that has the network interface.
Specifies information about a machine's network communication interface.
Displays information about a machine's NIM interface.
Specifies the name of the machine that has the NIM interface.
Displays the name of the machine that has the NIM interface. If you want to choose a different machine, use the Cancel function to return to the previous menu.
Removes a NIM interface from the definition of the specified machine. Continue to the next level of SMIT to specify the name of the machine.
Specifies the name of the machine from which you want to remove a NIM interface connection. Use the List function to display a list of existing machine names.
Displays the name of the machine from which you are removing a NIM interface. If you want to change the machine name, use the Cancel function to return to the previous level.
Lists a menu of resource operations that enable you to manage the allocation and deallocation of resources for a specified machine configuration.
Lists the NIM resources that have been allocated for use by a specified machine or machine group. Continue to the next level of SMIT to specify the machine or machine group name.
Specifies the name of the machine or machine group whose allocated resources you want to list. Use the List function to display a list of existing machine or machine group names.
Enables you to perform resource allocation, an operation that gives a specified machine or machine group permission to use specified resources. Allocation is a preparatory step for some NIM operations. Continue to the next level of SMIT to choose which resources you want to allocate and to specify a machine or machine group name.
Specifies the name of the machine or machine group to which you want to allocate a resource or resources. Use the List function to display a list of existing machine or machine group names.
Displays a list of network install resources that you can allocate to this machine. Use the arrow and function keys to select the resource you want to allocate.
Remove a specified machine or machine group's permission to use a specified resource or resources. Continue to the next level of SMIT to choose the resources you want to deallocate and to specify a machine or machine group from which the resources are to be deallocated.
Specifies the name of the machine or machine group from which you want to deallocate a resource or resources. Use the List function to display a list of existing machine or machine group names.
Displays a list of network install resources that are currently allocated to this machine. Use the arrow and function keys to select the resource you want to deallocate.
Specifies the NIM operation you want to perform on a machine. Continue to the next level of SMIT to specify the machine on which you want to perform the operation.
Specifies the name of the machine or machine group on which you want to perform a NIM operation. Use the List option to display a list of machines or machine groups.
Displays the name of the machine or machine group on which you are performing a NIM operation. If you want to choose a different machine or machine group, use the Cancel option to return to the previous level.
Specifies which operation you are using on a specified machine. Use the List function to display a list of machine operations.
Specify the flags to use when NIM invokes the installp command during an operation. The flag sign (-) must be included in this field.
Lists a menu of operations that enable you to manage NIM resources. Operations include listing the existing resources, adding a resource, changing or showing the characteristics of a resource, removing a resource, and performing maintenance on a Shared Product Object Tree (SPOT).
Lists all resources of the specified type currently defined in the NIM environment. Continue to the next level in SMIT to specify a resource type.
Specifies the type of resource to be listed. All resources of the type specified and currently existing in the NIM environment are displayed. Use the List function to display the existing resource types.
If you want to perform a different resource operation, use the Cancel function to return to the previous screen.
Adds a resource of the specified type to the NIM environment. Each time a resource is added to the environment, an object representing the resource is created in the NIM database.
Continue to the next level of SMIT to specify the resource type.
Displays a list of resource types. Use the arrow keys to select the type of resource you want to add.
The unique name of the resource you are adding to the NIM environment. The name you supply identifies the resource in the NIM environment.
Displays the type of resource you added to the NIM database. If you want to change the resource type, use the Cancel function to return to the previous screen.
Lists the NIM name of the machine that serves this resource.
The path name on the server where the resource resides.
Specifies which device or NIM resource is to be used when creating the resource.
Specifies any information you want to associate with the resource. Consider detailing certain aspects of the addition such as the date, time, or name of the user who created the resource. The information you supply may be helpful to future users of the same NIM environment.
Displays the characteristics of the specified resource and enables you to change some of the resource's characteristics, if desired. Continue to the next level of SMIT to specify the name of the resource.
Displays a list of network install resources. Use the arrow keys to select the resource you want to view or change.
Displays the name of the resource whose characteristics you choose to view or change.
Specifies the type of resource whose characteristics you choose to view or change.
Specifies the machine that serves the resource.
Displays the path name on the server where the resource is located.
Removes a resource from the NIM environment. Continue to the next level of SMIT to specify the name of the resource you want to remove
Displays a list from which you may select the resource you want to remove from the NIM environment. Use the arrow keys to select the resource you want to remove.
Enables you to change or view the installed file sets of a specified SPOT. Continue to the next level of SMIT to specify the SPOT name.
Specifies the name of the SPOT whose file sets you want to modify. Use the List function to display a list of SPOT names currently existing in the NIM environment.
Displays a list of the SPOT operations you can perform. Use the arrow and function keys to select the operation you want to perform.
Customization is the operation that performs software installation within a SPOT.
Displays the name of the SPOT you want to customize.
Specifies the device or NIM resource that contains the images you want to install into this SPOT.
Specifies the path name of the software you want to install into this SPOT..
Specifies the names of the file sets to be passed to the installp command
Enables you to perform software maintenance on a SPOT. Continue to the next level of SMIT to specify the name of the SPOT.
Specifies the name of the SPOT resource on which you want to perform software maintenance. Use the List function to display a list of SPOT resource names currently existing in the NIM environment.
Displays the name of the SPOT on which you are performing software maintenance. If you want to choose a different SPOT, use the Cancel function to return to the previous screen.
Allows you to list the file sets already installed in an existing SPOT. Continue to the next level of SMIT to specify the name of the SPOT resource.
Specifies the name of the SPOT whose file sets you want to list. Use the List function to display a list of SPOT names currently existing in the NIM environment.
Displays the name of the SPOT whose options you are listing. Use the Cancel function to return to the previous screen if you want to choose a different SPOT.
Specifies the flags to use with the lslpp command.
Enables you to verify the status of a SPOT resource object. Continue to the next level of SMIT to specify the name of the SPOT resource object.
Specifies the name of the SPOT resource object whose status you are checking. Use the List function to display a list of SPOT names currently existing in the NIM environment.
Displays the name of the SPOT resource object whose status you are checking. Use the Cancel function to return to the previous screen if you want to choose a different SPOT.
SPOTs are a complex NIM resource; therefore, they require extra maintenance. The menus in this section enable you to perform NIM operations on SPOTs.
Identifies a specific Network Installation Management route.
Initializes the NIM environment to enable a diskless machine to boot.
Specifies the size (in megabytes) of the client's remote paging space.
Initializes the NIM environment to configure a machine in a dataless configuration.
Specifies the size (in megabytes) of the client's local paging space.
Enables a network diagnostic boot.
Ends any active NIM operation and resets the machine's state. In some cases, the Force option may have to be used to complete this operation.
Performs software customization on a running client.
Initializes the NIM environment to perform a base system installation on the target machine. When the operation completes successfully, the NIM environment has been enabled to install the target, and installation will begin as soon as the target issues a BOOTP request.
Identifies where the BOS runtime files will come from. These files are used to initialize the target's /usr file system.
Performs software maintenance by invoking the installp command on the target.
A list of names of optional packages with which you want to create the lpp_source.
Specifies the name of the NIM installp_bundle resource that is to be used when NIM invokes the installp command.
Specifies the NIM operation that you want to perform.
Specifies whether the NIM master is allowed to push operations on the client.
Select the operation you want to perform from the list that is displayed.
diag - Enables a machine to boot a diagnostic image.
cust - Enables you to install additional software on this machine.
bos_inst - Initiates the base installation process on this machine.
maint - Enables you to perform software maintenance tasks such as commit an applied file set, reject software that is applied, clean up after an unsuccessful installation, or remove software products and their updates.
Specifies the flags that are passed to the installp command. The -a flag applies the specified software or update. The -g flag automatically includes requisite software. The -X flag attempts to expand any file system where there is insufficient space to perform the installation.
Select the operation you want to perform from the list that is displayed.
Specifies the network that, conceptually, initiates communications with another network.
Includes the menus used from a NIM client to perform NIM operations. Includes configuring the NIM client package, managing push permissions, managing resource allocation, and performing a network install. See the next level of SMIT for more information.
Configures the NIM client file set. See the following level of SMIT for more information you need to supply.
Specify the NIM network install interface of the client. The NIM network install interface identifies the network interface the client uses to access resources in the NIM environment.
Specify the name of the device that contains the Initial Program Load (IPL) Read Only Memory (ROM) emulation program media. This is only required when your machine does not have the necessary Boot Protocol (BOOTP) support in its IPL ROM.
Enables or disables the NIM master's push permissions. The NIM master must have push permissions to push NIM operations.
Includes menus to list allocated NIM resources, allocate NIM resources, and deallocate NIM resources. See the next level of SMIT for more information.
Displays the NIM resources that are allocated to this machine.
Displays a list of resources that are available for allocation to this machine.
Initiates a NIM install operation for this machine.
Specifies which NIM install operation to perform.
Create bootable media that contains the IPL ROM emulation program. See the next level of SMIT for the information you need to provide.
Specify the device on the Target Machine where you want to create the bootable IPL ROM emulation.
Specify the NIM client machine on which you are creating the bootable IPL ROM emulation media.
Specify the location local to the master of the IPL ROM emulation image you want to transfer to the device on the target machine.
Specifies the mode that must be used to use the emulation as boot medium. This field toggles between three values: both, norm, and serv.
Attempts to determine the current execution state of the specified client.
Invokes the lslpp command to display file set information for the specified lpp_source.
The network to which the client's primary interface connects.
Specifies whether to automatically expand file systems when space is needed to perform the specified operation.
Rebuilds the table of contents (.toc) file in the lpp_source and determines whether it contains the set of images required to meet the simages requirement.
Specifies the fixes to be installed or queried. Fixes are identified by a unique keyword that can refer to either a single file set update or multiple file set updates that are related in some way. A fix can be identified with an APAR number. If so, it will include all of the file set updates that are necessary to fix the reported software problem that is identified by that number.
This is a resource that represents the location of a file that contains fix keywords. This allows you to group several fixes identified by unique keywords and install them into a SPOT or client machine or to perform a query to determine their installation status.
Displays whether specified fix keywords are installed on a client or SPOT.
Indicates whether you want to display symptom text for the fixes being queried.
Indicates whether a query on a fix or keyword should consider all updates associated with the fix or keyword or just those whose base level file sets are currently installed.
Indicates whether information about each file set associated with a fix or keyword should be displayed.
Specifies whether you want the client you are installing to remain in the NIM environment. Your options are:
YES - Installs the bos.sysmgt.nim.client file set on the client, keeps the client configured as a member of the NIM environment, and has NIM automatically configure the client's network.
NO - Does not install the bos.sysmgt.nim.client file set, does not reconfigure the client as a member of the NIM environment, and does not have NIM automatically configure the client's network.
Specifies whether the BOS installation set up process should attempt to reboot the client. This allows you to enable the BOS installation on a system, but initiate the actual installation at a later time. Your options are:
YES - An attempt will be made to reboot the client immediately after the BOS installation is enabled. This will initiate the installation.
NO - No attempt is made to reboot the client after the BOS installation is enabled. The installation must be initiated at a later time.
Specifies whether the NORMAL mode list of boot devices on the client should be modified to boot from the network. If you want to set up a BOS installation on a running system that has been configured as a NIM client and you want to initiate the installation automatically by rebooting the client at a later time, set this option to YES. You must specify this option (if desired) only when Force Unattended Installation Enablement is set to NO and Initiate Boot Operation on Client? is set to NO.
Choosing YES modifies the list of boot devices on the client so that the primary boot device is its NIM network interface.
When set to YES, this option allows you to install a system that does not currently have the NIM client file set installed and configured.
In order for this operation to work correctly, the following steps must be taken.
Specifies whether a message warning that the system will be reinstalled after the reboot will be sent to users on the target system. This is only applicable if you are rebooting a client for which a BOS installation has been enabled by NIM. Your options are:
YES - Sends a message to all users on the client stating that the system will be reinstalled after the system is rebooted.
NO - Allows the system to reboot and reinstall with no indication to the users.
Displays a menu of operations that can be performed on NIM machine or resource groups. Machine groups provide a means of grouping related NIM machines so that the machines may be operated upon as a logical unit. Similarly, resource groups provide a means of grouping resources so that they may be allocated as a logical unit. Administrative group operations include defining a group, changing or viewing the characteristics of a group, and removing a group. Any control action that can be performed on a machine of a given configuration type (for example, bos_inst on a standalone machine) can also be performed on a group of machines of the same configuration. These operations are also accessible from this menu.
Lists information about groups currently defined in the NIM environment. You can view the names of the groups defined and details about group members.
Adds a group definition to the NIM environment. Machine groups are defined using machine definitions of the same NIM configuration. The next level of SMIT menus lets you choose to define a machine group of a given configuration or a resource group.
Displays the characteristics of a NIM group and lets you to change some of the NIM group characteristics. Continue to the next level of SMIT menu to specify the name of the group.
Removes a machine or resource group from the NIM environment. You may want to remove a group because you are dissatisfied with the way it was created or because the group is no longer valid in the current NIM environment.
Continue to the next level of SMIT to specify the name of the group definition you want to remove.
Lists a menu of resource operations that enable you to manage the allocation and deallocation of resources (including resource groups) for a specified machine or machine group.
Enables you to perform NIM operations on a machine group. Continue to the next level of SMIT to specify the machine group on which you want to perform operations.
Marks the members of a machine group as being either excluded from or included in operations on that group. Group members are included in all operations on that group by default. Any members that are marked as excluded remain excluded until they are included again.
Displays the names and types of all machine and resource groups currently defined in the NIM environment.
Displays the members of NIM groups. Continue to the next level of SMIT to specify the groups whose members you wish to display.
Displays the members of NIM groups including pertinent NIM state information for the members. For machine groups, this option also displays whether a member has been excluded from operations on that group. Continue to the next level of SMIT to specify the groups whose members you wish to display.
Displays detailed NIM database information about members of NIM groups. Continue to the next level of SMIT to specify the groups whose members you want to display.
Adds an entry to the NIM database representing a group of standalone machines.
Adds an entry to the NIM database representing a group of diskless machines.
Adds an entry to the NIM database representing a group of dataless machines.
Adds an entry to the NIM database representing a group of resources.
Adds a machine group definition of the specified configuration to the NIM environment.
The NIM type of the group. You cannot change this field.
The NIM type of the members of the group being defined. This is for informational purposes here and is not part of the final group definition. You cannot change this field.
Choose the machines you want to add to machine group definition.
Displays the characteristics of the specified NIM group and enables you to change some of these characteristics if desired.
The name of the NIM SPOT (Shared Product Object Tree) you want to add to the resource group definition. You can add only one resource of this type to a resource group. Information in this field is optional.
The name of the NIM LPP_SOURCE that you want to add to the resource group definition. You can add only one resource of this type to a resource group. Information in this field is optional.
The names of the NIM INSTALLP_BUNDLEs you want to add to the resource group definition. You can add more than one resource of this type to a resource group.
Specify the names of the NIM SCRIPTs you want to add to the resource group definition. More than one resource of this type may be added to a resource group. This field is optional.
The name of the NIM BOSINST_DATA resource you want to add to the resource group definition. You can add only one resource of this type to a resource group. Information in this field is optional.
The name of the NIM IMAGE_DATA resource you want to add to the resource group definition. You can add only one resource of this type to a resource group. Information in this field is optional.
The name of the NIM MKSYSB resource you want to add to the resource group definition. You can add only one resource of this type to a resource group. Information in this field is optional.
The name of the NIM FIX_BUNDLE resource you want to add to the resource group definition. You can add only one resource of this type to a resource group. Information in this field is optional.
The name of the NIM ROOT resource (for diskless and dataless configurations) you want to add to the resource group definition. You can add only one resource of this type to a resource group. Information in this field is optional.
The name of the NIM PAGING resource (for diskless and dataless configurations) you want to add to the resource group definition. You can add only one resource of this type to a resource group. Information in this field is optional.
The name of a NIM DUMP resource (for diskless and dataless configurations) you want to be add to the resource group definition. You can add only one resource of this type to a resource group. Information in this field is optional.
The name of the NIM HOME resource (for diskless and dataless configurations) you want to add to the resource group definition. You can add only one resource of this type to a resource group. Information in this field is optional.
The name of the NIM SHARED_HOME resource (for diskless and dataless configurations) you want to add to the resource group definition. You can add only one resource of this type to a resource group. Information in this field is optional.
The name of the NIM TMP resource (for diskless and dataless configurations) you want to add to the resource group definition. You can add only one resource of this type to a resource group. Information in this field is optional.
Displays the current members defined for this group. Use the List function to view the full list of members. You cannot change this field.
Specify the NIM machines you want to add to this group definition. These machines will be added before any machines listed in the Members to Remove entry field are removed from the group.
Specify the NIM machines to be removed from this group definition. These machines will be removed after any machines listed in the Members to Add entry field are added to the group.
Enables you to display a log of the output from the installp command when software was installed in the SPOT.
Name of the SPOT whose installation log is to be viewed. You cannot change this field.
Specify the type of installation log to be viewed. The supported log types are:
devinst - Displays output from the installation of key system and device driver software during BOS installation. This log type is applicable to standalone machines only.
niminst - Displays output from the installation of optional software on machines and SPOTs.
bosinst - Displays output from the BOS installation program. This log type is applicable to standalone machines only.
boot - Displays the machine's boot log.
script - Displays output from any customization scripts executed on NIM clients.
nimerr - Displays errors encountered during execution of the nim command.
Enables you to display installation, boot, and customization logs for NIM machines.
Specifies the name of the NIM machine or machine group whose log is to be viewed. You cannot change this field.
When set to yes, the output from the last session recorded in the log is displayed. When set to no, the entire contents of the log is displayed.
This entry is applicable to devinst, script, and niminst logs only. The entire log is displayed for all other log types.
Specifies the name of the group whose members are being included or excluded. You cannot change this field.
When set to yes, all members in the group are excluded from subsequent operations on the group. When set to no, has no effect.
When set to yes, all members in the group are included in subsequent operations on the group (assuming members had been excluded previously). When set to no, has no effect.
Specify the group members that should be excluded from subsequent operations on the group.
Specify the group members that should be included from in operations on the group (assuming members had been excluded previously).
Enables you to remove a machine or resource group from the NIM environment. You may want to remove a group because you are dissatisfied with the way it was created, or because the group is no longer valid in the current NIM environment.
Specifies the name of the NIM group you want to remove from the NIM environment. You cannot change this field.
Specify the name of the machine group that you want as the target of the machine operation.
Specify the operation you are using on a specified machine group.
Specify the name of the NIM group whose members are to be excluded from or included in subsequent NIM operations.
Adds a default NIM route to the NIM network you specify. NIM routes are added to network definitions so NIM can determine the connectivity between NIM machines. When defining a default NIM route, you must specify the default gateway used by machines on the specified network.
Adds a static NIM route between two specified NIM networks. NIM routes are added to network definitions so NIM can determine the connectivity between NIM machines. When defining a static route, you must specify gateways used by each network to get to and from the other network.
Specifies the name of the NIM network for which you are defining a default route. You cannot change this field.
Specify the host name or IP address (dotted decimal value) of the default gateway (or router) used by machines on the network for which a default NIM route is being defined.
Adds a machine definition for the specified host name to the NIM environment. The primary interface of a machine being defined must be associated with a NIM network. If a NIM network does not exist for the specified host name, you will be prompted for additional information. This additional information will be used to define a NIM network with routing information.
Specify the name of a NIM machine group to which the machine being defined will be added. NIM groups are used to group like machines so that common operations can be performed on multiple machines in a single operation. If no NIM groups exist, a group will be defined for the name you specify, and the machine being defined will be added as the group's first member.
Specify the name of the NIM network with which the primary interface of the machine being defined will be associated. The primary interface of each machine in the NIM environment must be associated with a NIM network. Definition of this machine will first create the associated NIM network using the name you specify.
Specifies the type of NIM network that will be defined as a result of adding this machine to the NIM environment. You cannot change this field. If you want to change the network type, use the Cancel function to return to the previous screen.
Enter the subnetmask of the network that will be defined as a result of adding this machine to the NIM environment. The subnet mask should be a dotted decimal value.
Enter the host name or IP address (dotted decimal value) of the default gateway (or router) used by the machine being defined.
Enter the host name or IP address (dotted decimal value) of the default gateway (or router) used by the NIM master.
Select the NIM network to which you wish to add a default route.
Enter the host name of the primary network install interface of the machine you are adding to the NIM environment. Using the IP address of the specified host name, NIM determines whether a NIM network has been defined for machines on the subnet to which the machine being defined is connected. If the NIM network has not been defined, you will be prompted for additional network information so that a NIM network can be defined automatically.
The IP address of the host name you specified does not match any defined NIM networks. A NIM network will be defined automatically for this machine. Select the type of network to which the machine's primary network install interface is connected.
Enter the host name associated with the network install interface you are defining for the specified machine. Using the IP address of the specified host name, NIM determines if a NIM network has been defined for the subnet to which the interface being defined is connected. If the NIM network has not been defined, you will be prompted for additional network information so that a NIM network can be defined automatically.
The IP address of the host name you specified does not match any defined NIM networks. A NIM network will be defined automatically for this interface. Select the type of network to which the interface is connected.
This menu option allows you to select or deselect the name of a NIM resource group to be used for default allocation.
Specify the name of the NIM RESOLV_CONF resource you want to add to the resource group definition. Only one resource of this type may be added to a resource group. This field is optional.
When set to yes, this group is used for default resource allocation.
Choose select to designate the group specified as the default resource group. Choose deselect to end using the group specified as the default resource group.
Enables you to perform software verification checks on software file sets installed in the NIM environment.
Specify the name of the software to verify. If you want to verify a particular file set, specify the full name of that file set. If you want to verify a software package (containing multiple file sets beginning with the same name), specify the common part of the file set name and terminate the name with an * (asterisk). If you want to verify all software on the NIM target, specify all.
Verification can be performed on the consistency of file set versions and file set requisites or on the integrity of the files delivered by software file sets. Select the desired verification mode by specifying yes for only one of the following and no for all others.
When set to yes, NIM verifies the consistency of software versions for file sets with multiple parts (USR and ROOT parts) and for requisites between file sets.
When set to yes, NIM verifies that all files delivered by a particular file set are installed and have the correct length.
When set to yes, NIM verifies that all files delivered by a particular file set have the correct checksum.
When set to yes, NIM verifies the existence and correctness of any links shipped by a file set.
When set to yes, NIM supplies the verbose option to the lppchk command invoked to perform the software verification.
When set to yes, this option updates the software database entries for any files that are found to be inconsistent. This option is valid only when verifying file links or verifying checksums.
Lists menus for configuring and customizing the NIM environment.
Configures this machine as a NIM master and creates a basic NIM environment. After configuration is completed, the NIM environment will have the basic elements needed for performing network installation operations.
The minimum configuration tasks that you can perform through this menu include:
Additional configuration tasks that you can perform through this menu include:
Because the intent of this menu is to configure a new NIM environment, you cannot use this menu on a system where the NIM master has already been initialized.
All resources and file systems defined from this menu are created on this machine. Therefore, you should consider the selection of file systems and volume groups that will be used.
Lists menus for customizing a NIM environment. These menus enable you to perform the following tasks:
Initializes the NIM master, but performs no other configuration of the NIM environment.
Lists menus for creating lpp_source and SPOT resources.
Creates resources that are used by diskless and dataless clients. You can create the following resources: SPOT, ROOT, DUMP, PAGING, HOME, SHARED_HOME, and TMP.
Creates installp_bundle resources that you can use with NIM installation operations. The bundles are equivalent to the system bundles found on this machine in the /usr/sys/inst.data/sys_bundles directory.
Lists menus for defining client machines in the NIM environment. You can define clients individually, or you can list clients in a stanza definition file that can be processed.
Creates both an lpp_source resource and a SPOT resource from installation media. You can create these resources on the NIM master or on any NIM client that is running.
Creates a new lpp_source resource from installation media. You can create the lpp_source on the NIM master or on any NIM client that is running.
Creates a new SPOT resource from installation media. You can create the SPOT on the NIM master or on any NIM client that is running.
Adds a NIM client definition to the NIM environment.
Processes a client definition file and checks the file for correctness. NIM displays information describing the changes that will occur in the NIM environment if the clients are added.
No client definitions are added to the NIM environment at this time. This operation is for verification only. The NIM master must be initialized before you can perform this operation.
Uses the nimdef command to process a client definition file for adding client machines to the NIM environment. All valid client definitions are added to the environment. The NIM master must be initialized before this operation can be performed.
Before you add client definitions from a definition file, you should verify the client definition file by performing the Preview a Client Definition File operation.
Uses the nimdef command to process a client definition file for adding client machines to the NIM environment. No clients are added to the environment at this time, but the commands for adding all valid client definitions are displayed. You can redirect this output to a script and run the script at a later time. The NIM master must be initialized before this operation can be performed.
Specify the name of the network interface that the master uses to access NIM resources when performing install operations onto the master.
Specify the source of the installation images that will be used to populate an lpp_source or to create a SPOT.
Specify the name that will uniquely identify this lpp_source resource in the NIM environment. The name you specify must not contain any special characters, such as $, & \, *, and must contain less than 21 characters.
Specify the name of the directory under which you want the lpp_source to be created.
When set to yes, a file system is created to contain the new lpp_source. The mount point for the new file system is the specified lpp_source directory. No other file system on the system can have the same mount point.
Specify the size of the file system to be created. This value should be an estimate of the space needed for containing the resource. If additional space is needed during resource creation, this size will be expanded automatically.
Specify the volume group where the new file system will be created. The volume group should contain sufficient space for all file systems that will be created in that group.
Specify the name that will uniquely identify this SPOT resource in the NIM environment. The name you specify must not contain any special characters, such as $, & \, *, and must contain less than 21 characters.
Specify the directory under which the SPOT will be created.
When set to yes, a file system is created to contain the new SPOT. The mount point for the new file system is the specified SPOT directory. No other file system on the system can have the same mount point.
Lists menus for installing and maintaining software on NIM clients and SPOTs.
Lists menus for managing diskless and dataless client machines. These menus enable you to can perform the following tasks:
Initiates a Base Operating System installation of a NIM client or a group of NIM clients. You will be prompted for the type of installation you want to perform and the resources that should be used for the operation.
Initializes the resources for a diskless or dataless client. The client machine and its required resources must be defined in the NIM environment before you can perform this operation.
The following resources are used by diskless and dataless clients:
SPOT - Shared Product Object Tree for the client /usr directory.
root - Parent directory for the client / (root) directories.
dump - Parent directory for the client dump files.
paging - Parent directory for the client paging file.
home - Parent directory for the client /home directories.
shared_home - The /home directory shared by clients.
tmp - Parent directory for the client /tmp files.
After you initialize the resources, you must boot the client from the SPOT server.
Resets a diskless or dataless client in the NIM environment. If you choose the option to deallocate all resources from the client, all root data for the client will be removed.
Attention: Uninitializing a client and deallocating all resources destroys all of the client's configuration and user data.
Specify the client machine, group, or resource upon which the operation should be performed.
Specify one of the following installation types for Base Operating System (BOS) install:
rte - Install the BOS from installation images contained in an lpp_source resource.
spot - Install the BOS by copying files from a SPOT resource.
mksysb - Install the BOS by restoring a mksysb image.
Specify the mksysb resource to be restored to the target system. If the installation type for BOS is mksysb, you must specify this resource.
Specify the SPOT resource to be used during the installation of the target system. You must specify this resource for all BOS installation types (rte, spot, and mksysb).
When set to yes, resources are created to support diskless and dataless client machines.
To define a new ROOT resource, specify the name that will uniquely identify this resource in the NIM environment. The name you specify must not contain any special characters, such as $, & \, *, and must contain less than 21 characters.
A ROOT resource is a parent directory for client / (root) directories.
To define a new DUMP resource, specify the name that will uniquely identify this resource in the NIM environment. The name you specify must not contain any special characters, such as $, & \, *, and must contain less than 21 characters.
A DUMP resource is a parent directory for client dump files.
To define a new PAGING resource, specify the name that will uniquely identify this resource in the NIM environment. The name you specify must not contain any special characters, such as $, & \, *, and must contain less than 21 characters.
A PAGING resource is a parent directory for client paging files.
To define a new HOME resource, specify the name that will uniquely identify this resource in the NIM environment. The name you specify must not contain any special characters, such as $, & \, *, and must contain less than 21 characters.
A HOME resource is a parent directory for client /home directories.
To define a new SHARED_HOME resource, specify the name that will uniquely identify this resource in the NIM environment. The name you specify must not contain any special characters, such as $, & \, *, and must contain less than 21 characters.
A SHARED_HOME resource is a /home directory shared by clients.
To define a new TMP resource, specify the name that will uniquely identify this resource in the NIM environment. The name you specify must not contain any special characters, such as $, & \, *, and must contain less than 21 characters.
A TMP resource is a parent directory for client /tmp directories.
Specify the directory under which you want the diskless and dataless client resources to be created.
When set to yes, a file system is created to contain the new diskless and dataless client resources. The mount point for the new file system is the specified Diskless/Dataless resource directory. No other file system on the system can have the same mount point.
When set to yes, NIM installp_bundle resources are created. The bundles are equivalent to the system bundles found on this machine in the /usr/sys/inst.data/sys_bundles directory.
When set to yes, NIM client definitions are added from a NIM client definition file.
Specify the file name of a NIM client definition file.
When set to yes, resources and newly created filesystems are removed if the entire configuration cannot be completed successfully. This option enables you to attempt the entire configuration over again if any errors occur. Because significant amounts of successful work can be erased by the occurrence of a simple problem, the default value for this option is no.
Specify the machine where you want the resource physically defined. This machine may be the NIM master or any NIM client.
When set to yes, a new SPOT is created to support diskless and dataless clients. Usually, a SPOT resource already exists to support NIM installation operations.
Specify the file name of a NIM client definition file.
Specify the machine where you want the resource physically defined. This machine may be the NIM master or any NIM client.
Lists menus for managing the NIM environment. These menus include the AIX Version 4.1 NIM SMIT screens for managing NIM objects and newer screens for other administrative tasks.
Using these menus the NIM administrator may perform the following tasks:
Lists menus for backing up and restoring a NIM database.
Uses the NIM database to rebuild the /etc/niminfo file. The niminfo file contains configuration data necessary for proper operation of the NIM environment.
Uninitializes the NIM master, removes the NIM daemons, and removes all configuration information from the NIM database. An option allows you to back up the NIM database before unconfiguring the environment.
Attention: Because this operation destroys data, you should perform this operation only if you plan to remove or completely reconfigure the NIM master file set.
Displays the contents of a NIM resource in a manner fitting the resource type. Use this operation to examine a resource to determine whether the resource is appropriate for use.
Uses the AIX backup command to save the NIM database and the /etc/niminfo file. This operation also writes the level of the currently installed NIM master file set to the /etc/NIM.level file and includes the /etc/NIM.level file in the backup image.
A backup of a NIM database should be restored only to a system with a NIM master file set that is at the same level or a higher level than the level from which the backup was created.
Configures the NIM master from a database backup. The backup that is used for this operation must have been created from the SMIT screen Backup the NIM Database or from the SMIT screen Unconfigure the NIM Environment. A backup can be restored only if the version of the NIM master file set on the system is at the same level or a higher level than the level from which the backup was created.
This operation uses the AIX "restore" system command.
Specify the name of the file or device where you want the backup of the NIM database to be written.
Specify the name of the file or device from which you want the backup of the NIM database to be restored.
When set to yes, the NIM database is backed up before the NIM environment is unconfigured.
Display the file sets available on an lpp_source.
The file sets available on this lpp_source will be displayed..
Specify the reference machine or spot that you want to compare with the lpp_source. NIM displays the file sets available on the lpp_source and indicators showing whether the file sets are installed on this reference machine or SPOT.
Display the contents of a script resource.
Specify the name of the script you want to display.
Display the contents of a bosinst_data resource.
Specify the name of the bosinst_data resource you want to display.
Display the contents of an image_data resource.
Specify the name of the image_data resource you want to display.
Display the contents of an installp_bundle resource.
Specify the name of the installp_bundle resource you want to display.
Display the contents of a fix_bundle resource.
Specify the name of the fix_bundle resource you want to display.
Displays the contents of a NIM resource in a manner fitting the resource type. Use this option to examine a resource to determine whether the resource is appropriate for use.
Specify the resource that you want to display in this operation.
Specify the lpp_source that is the NIM resource containing the install images for NIM operations.
Select the bosinst_data resource that you want used to perform non-prompted BOS installations of a NIM client.
Select the image_data resource that you want used to customize the creation of volume groups, file systems, and other aspects of the system during the BOS installation of a NIM client.
Select the resolv_conf resource that you want used to configure TCP/IP on the NIM client after the BOS installation.
Select the script resource that is a program you want run on the NIM client after the installation of the base operation system. You can use the script resource to perform any additional tasks on the client that are not normally performed by NIM.
When set to yes, the NIM client file set is installed on the client to support further operation in the NIM environment. The NIM client continues as a NIM client after BOS installation completes.
When set to yes, NIM resources that are defined on the target system are preserved during reinstallation of the Base Operating System. For this option to succeed, the resources served by the target system must reside in user-created file systems.
When set to yes, non-prompted installation is forced of the NIM client. If you set this option to yes, you must specify a bosinst_data resource.
When set to yes, the master attempts to reboot the client machine automatically for reinstallation. For this option to succeed, the client must be running and initialized as a NIM client or have rhost permissions granted to the master.
When set to yes, the master sets the boot list on the client to cause installation to occur at the next reboot. If you want the BOS installation operation to be initialized now and executed later, set this option to yes.
Specify the installp_bundle resource that lists additional file sets you want installed on the system.
Specify the names of additional file sets that you want installed on the system.
Specify command line flags that you want passed from NIM to the installp command to influence the way file sets are installed on the target system.
Specify an lpp_source directory where you want software packages copied. The software packages will be added to the lpp_source.
Specify the SPOT resource that you want mounted by the diskless or dataless client as a /usr file system.
Specify the root resource that is the parent directory for the diskless or dataless client system's / (root) directory.
Specify the dump resource that is the parent directory for the diskless or dataless client's dump files.
Specify the paging resource that is the parent directory for the diskless or dataless client's paging files.
Specify the home resource that is the parent directory for the diskless or dataless client's /home directories.
Specify the shared_home resource that diskless and dataless clients will share for their /home directories.
Specify the tmp resource that is the parent directory for the diskless or dataless client's /tmp directory.
Initializes the resources for a diskless client. After the resources are initialized, you must boot the client from the SPOT server.
Initializes the resources for a dataless client. After the resources are initialized, you must boot the client from the SPOT server.
Deallocates the resources used by a diskless or dataless machine from the client. This option removes all of the client's configuration and user data.
Attention: Because this option destroys the client's configuration and user data, use this option only when the client's data has been backed up or is no longer needed.
Reinstalls the Base Operating System on this machine. Resources in the NIM environment are used to support this operation. The NIM resources that you want used must not reside on this machine.
Display the contents of a RESOLV_CONF resource.
Display the file sets installed in a SPOT resource.
Specify the name of the resolv_conf you want displayed.
Specify the name of the spot you want displayed. The file sets installed in the spot are shown.
If the system backup image already exists, enter the name of the file where the image resides. If you are creating the system backup image as part of this operation, enter the name of the file where you want the image placed after it is created.
When set to yes, increases the size of the /tmp file system on the machine being backed up if there is not sufficient space in /tmp to perform the backup.
Enter the name of the NIM network to which the interface being defined will be connected. Each interface of each machine in the NIM environment must be associated with a NIM network. Definition of this machine interface will create a NIM network using the name you specify.
Specifies the type of NIM network that will be defined as a result of adding this interface to the NIM environment. If you want to change the network type, use the Cancel function to return to the previous screen.
Displays the NIM Cstate and Mstate for machine group members and Rstate for resource group members. If members of the NIM group being displayed have any error or additional information listed in info, err_info or missing attributes, that information is also displayed. Continue to the next level of SMIT to specify the groups whose members you wish to display.
Specify the name of the resource group you want to select or deselect as the default resource group.
Enter the NIM type for the machine being defined. Use the List function to display a list of supported types.
Enter the platform for the machine being defined. Use the List function to display a list of supported platform types. Note that all SPOTs in the NIM environment will be queried to determine the currently supported platforms. If no SPOTs are defined, a list of default platforms is displayed.
Each NIM network is used to represent one logical network that exists in the NIM environment. When the network is defined, the type of interface used in the network must be supplied. Usually, a network is composed of only one type. However, a bridge can be used to connect different physical networks in the same logical network. In this situation, NIM needs to know about the other network interface.
Specify any additional network type that composes this network.
Set this field to Yes to have NIM remove permissions to use all resources currently allocated to the specified machine or machine group.
Specify a unique name for a custom task that is to be added to the NIM environment. Do not use any special characters, such as $, &, \, *, in this name. The maximum number of characters is 38.
Specify the unique name given to a custom task that has been added to the NIM environment.
Specify the number of diskless and dataless root directories that should be synchronized in parallel. Diskless and dataless machine configurations use a remote directory (a SPOT) as their /usr file system. When an installp operation is performed on the SPOT, the corresponding operation must be performed on the root directories to keep the root and usr parts of the software products synchronized. This operation is called a "root sync," and NIM automatically performs it whenever a SPOT is used. By default, NIM performs 5 root sync operations at the same time. You can specify a different value to change the number of times the root sync operation is performed in parallel.
Set this field to Yes to display the NIM characteristics of the specified machine or machine group.
Set this field to Yes to display the software installation history for the specified object.
Set this field to Yes to display the fix installation status for the specified object.
Set this field to Yes to display the diskless and dataless clients served by the selected SPOT.
Set this field to Yes to display all of the software associated with the selected LPP_source.
Set this field to Yes to display all of the software fixes for the selected LPP_source.
Set this field to Yes to display all of the supplemental file set information for the selected LPP_source.
Set this field to Yes to enable the low-level kernel debugger when building the network boot images. Enabling the kernel debugger helps you to diagnose network boot failures. Refer to the troubleshooting section of the Network Installation Management Guide and Reference for more information on diagnosing network boot failures.
Specifies a machine or machine group name in the NIM environment.
Lists menus for modifying the behavior of NIM for certain operations.
Specifies whether or not machines may register themselves as NIM clients. By default, machines may register themselves as clients of a NIM master by running the niminit command and specifying the hostname of the master machine. If this capability is disabled, then only the NIM master can add machines to the NIM environment.
Lists menus for controlling the ability of clients to allocate resources.
Specifies whether or not NIM clients may allocate resources to themselves. If this capability is disabled, clients will then be unable to initiate NIM operations. All NIM operations would have to be initiated by the NIM master.
Specifies whether or not a particular NIM client may allocate resources to itself. If this capability is disabled, the client will then be unable to initiate NIM operations. All NIM operations for that client would have to be initiated by the NIM master.
Specifies whether or not NIM clients may allocate a particular resource to themselves. If this capability is disabled, clients will then be unable to use that resource for NIM operations. All NIM operations involving that resource would have to be initiated by the NIM master.
By default, NIM validates client requests by verifying that the CPU ID of the requester matches the CPU ID that was originally registered for the client. This validation can be disabled to allow requests to be handled for machines that have had their hardware changed.
By default, NIM uses Network File System (NFS) to export files and directories to individual client machines when resources are allocated to them. This may result in very long /etc/exports and /etc/xtab files, causing file limit and performance problems. Enabling global exports of NIM resources allows an administrator to export NIM resources once to all clients instead of repeatedly to each client individually. When a resource is exported globally, it is accessible to any machine in the network. The resource remains globally exported until it is deallocated from all clients.
Enablement and disablement of global exports should only be performed when no NIM operations are running and no resources are currently allocated. Otherwise, resources could be left globally exported unintentionally.
Lists menus for limiting the creation of network boot images to defined interfaces.
Prior to AIX Version 4.3, NIM created network boot images for all possible combinations of machines and networks that could be supported by a SPOT. This resulted in the creation of many unnecessary boot images. In AIX Version 4.3, the default behavior of NIM has been changed to only create boot images to support the machines and networks that are defined in the environment. NIM can be configured to follow either behavior.
A change in NIM's boot-image creation behavior will not take effect until the next time that boot images are created for a SPOT.
If machines and networks are added and removed from the NIM environment, down-level information may exist for what machine and network combinations should be supported. You can use this option to rebuild the list of required boot images. The new set of boot images will be created the next time that boot images are built for a SPOT.
Copy the rootvg or install a mksysb onto an alternate disk of a running machine.
Use a mksysb as the source for installing an alternate disk.
Copy the rootvg of a machine to an alternate disk.
Select Standard if machines connect to this network using a Standard Ethernet interface (en). Select IEEE 802.3 if machines connect to this network using an IEEE 802.3 Ethernet interface (et).
Displays the type of Ethernet interface machines use to connect to this network and allows you to make changes. Standard is displayed or selected if machines connect to this network using a Standard Ethernet interface (en). IEEE 802.3 is displayed or selected if machines connect to this network using an IEEE 802.3 Ethernet interface (et).
The maximum number of machines from the selected group that should be installing at any time. You can specify this value when you are installing a machine group and you want to control the impact of the installation on network traffic.
If you leave the value blank, NIM initiates the installation on all machines in the selected group. If you specify the value, NIM monitors the progress of all machines in the group and attempts to keep installing no more or no less than the number specified until all machines in the group are installed.
If you want to stop the installation after a given period of time has elapsed, type the time limit in hours.
Specify the maximum number of hours in which to complete the installation of all machines in the selected group.
You can specify this value only when you are limiting the number of concurrent operations on a group of machines. The value tells NIM the number of hours that should elapse before NIM stops initiating the installation of additional members of the selected machine group.
If the installation of all machines in the group is not initiated within the specified time limit, the command should be reissued at a convenient time. This allows the operation to continue on the remaining machines in the group.
Specifies the machine or target group to perform the alternate disk installation.
Specifies the target disk (or disks) that will be used to create the alternate disk rootvg. If a group is selected, all of the disk names must be the same. The disks cannot have any volume group associated with them, unless it is altinst_rootvg and Phase 2 and/or Phase 3 is being executed.
Specifies the alternate disk installation phase to run. Alternate disk installation is broken down into three phases. You can perform Phase 1 once, Phase 2 multiple times, and Phase 3 once. The default is to perform all three phases in the same invocation.
Specifies the image.data file to use when cloning the rootvg to the alternate disk. The default is to create a new image.data file on the target system with the mkszfile command.
Specifies the exclude list that the alt_disk_install command should use to designate which mounted files and/or directories should not be backed up and copied to the new alternate rootvg disk.
Specifies the bundle to install into the alternate rootvg disk after the clone. A bundle is a file containing a list of file sets or packages to send to the installp command. You must include an lpp_source if a bundle is used. Additional installs are performed in Phase 2.
Specifies a list of file sets to install into the alternate rootvg disk after the clone. You must include an lpp_source if a list of file sets is given. Additional installs are performed in Phase 2.
Specifies a file containing a list of APARs to install into the alternate rootvg disk. You must include an lpp_source if a FIX_BUNDLE is specified. Additional installs are performed in Phase 2.
Specifies a list of APARs to install into the alternate rootvg disk. You must include an lpp_source if a list of APARs is specified. Additional installs are performed in Phase 2.
Specifies an lpp_source to use to install additional file sets or fixes into the alternate rootvg disk.
Specifies an executable to run after the rootvg disk has been cloned. The customization script is run in Phase 2.
Specifies whether the target system should reboot when the alternate disk installation has completed. This reboot is done in Phase 3.
Specifies whether the line-by-line output from the alt_disk_install command should be made available. The output, used for debugging, will be sent to the /var/adm/ras/nim.alt_disk_install file on the client system.
Specifies the mksysb resource to use for restoring to the alternate disk. This image must have all file sets for device support for the target system, as well as the appropriate kernel and 64-bit support, if necessary. The mksysb image must be Version 4.3 of the operating system or later.
Specifies that the client should remain a NIM client after the alternate disk installation. If YES is specified, the /.rhosts and the /etc/niminfo files are copied to the alternate rootvg disk.
Specify an existing resource to be replicated when a new resource is defined. This value should be specified when replicating one resource to create another of the same type. The file pointed to by the source resource will be copied to the new location and a new NIM resource will be defined.
For large installation environments, you can scale NIM to support installing more or less clients simultaneously. To do this, you must define installation resources on different NIM machines throughout the environment and use this option to tune the number of simultaneous requests from installing clients that the NIM master can handle.
The NIM master processes client requests (to update status and initiate installation) via a multi-threaded daemon (nimesis). The number of threads you assign to this daemon determines how many simultaneous NIM client requests can be handled in the NIM environment.
Select "enable" to support large installation environments (20 or more simultaneous NIM client commands). In this mode, NIM utilizes the multi-threaded daemon (nimesis).
Select "disable" to support smaller installation environments (20 or less NIM client requests at one time). In this mode, NIM utilizes the single-threaded daemon (nimesis).
Specify the number of threads, within the range of 20 to 150, to assign to the multi-threaded daemon (nimesis). The number of threads assigned to this daemon is the maximum number of simultaneous NIM client requests that the NIM environment can handle. This option is valid only if "Client Request Tuning" is set to "enable".
The architecture type of the source images to copy over when you create the LPP source. If you do not specify an architecture, the system attempts to determine the architecture.
The target client for this nimadm operation. You can type the NIM name of a client or select one from the list. Press the F4 key to display a list of choices. The client should be a registered standalone NIM client. Information in this field is required.
The NIM lpp_source resource that will be used for this nimadm operation. Type or select a NIM defined lpp_source resource. The lpp_source should be local to the master and will be the source of migration images. The lpp_source should match the operating system level you are migrating to and be at the same level or lower then the master. Information in this field is required.
The NIM SPOT resource that will be used for this operation. Type or select a NIM SPOT resource. All nimadm and alt_disk_install utilities that will be used by the client are installed in this resource. The level of alt_disk_install utilities installed in the spot should match the level of utilities installed on the NIM master. Information in this field is required.
Type the name of the target disks that will host altinst_rootvg on the client. The specified disks should contain no other volume groups and be large enough to host rootvg. Information in this field is required.
NOTE: The disks in question are local to the client (part of the client's hardware).
The image_data resource that is used by alt_disk_install in nimadm phase 1 and 11. Type or select a NIM defined image_data resource. NIM will allocate and mount this resource on the client before calling alt_disk_install.
The NIM BOSINST_DATA resource that will be used for this nimadm operation. Type or select a NIM defined bosinst_data resource. This NIM resource specifies various install settings that can be used by nimadm.
The NIM EXCLUDE_FILES resource that will be used for this nimadm operation. Type or select a NIM defined EXCLUDE_FILES resource. This NIM resource excludes specified files from being copied during nimadm phase 1. NIM will allocate and mount this resource on the client before calling alt_disk_install in nimadm phase 1. See the alt_disk_install man page for a complete explanation of this resource.
The NIM script resource that will be executed before any migration changes are made (in nimadm phase 4). Type or select a NIM defined SCRIPT resource.
The NIM script resource that will be executed after most migration changes are made (in nimadm phase 7). Type or select a NIM defined SCRIPT resource.
The NIM INSTALLP_BUNDLE resource that will be used for this nimadm operation. This resource contains the names of additional installp file sets that are to be installed by this nimadm process. Type or select a NIM defined INSTALLP_BUNDLE resource.
The phase or phases to execute during this invocation of nimadm. If there is more then one phase, separate the phases with commas or spaces. Valid phases are 1 through 12. Type or select phases.
Type the arguments that will be passed to the mount command that mounts client resources on the master. These arguments can be used to tune nimadm related NFS performance.
To set the client's boot list to the altinst_rootvg boot disk at the end of the nimadm migration (phase 11), select "yes". The default is "yes". To assume control of the client boot list, select "no".
To reboot the client if nimadm migration completes successfully, select "yes". To not reboot the client at the end of nimadm operation, select "no". The default is "no".
NOTE: Successful nimadm migration does not mean that everything has been successfully migrated. It only means that the nimadm process accomplished all of its tasks. Always check the nimadm migration log for details.
To turn nimadm verbose output on, select "yes". This displays information about each file set or key word associated with this action. To turn nimadmn verbose output off, select "no". The default is "no".
Select "yes" to run nimadm in debug mode. Select "no" to not run nimadm in debug mode. The default is "no".
To run the nimadm migration debugger if one of the phases encounters a serious failure, select "yes". To call cleanup, select "no". The default is "no".
Select "yes" to accept all license agreements and proceed with the installation. Select "no" to reject the license agreement and cancel the installation.
To have the nimadm operation unlock the client, select "yes". Normally, nimadm locks a client to perform various operations. While the client is locked, other nimadm or NIM operations cannot be performed. Use this option ONLY in the unusual condition that a client is incorrectly locked. (This can happen if, for some reason, nimadm could not call cleanup after a failure). Use this option with caution. The default is "no".
Lists NIM resources that can be verified for validity or content. Selecting a resource displays a verification menu for the selected resource.
The name of the resource selected to be verified for validity or content.
To use the current file sizes and checksum values in the SPOT to update the SWVPD database for the SPOT, select "yes". The default is "no".
To provide a source for install images to use to recover the SIMAGES attribute for the selected lpp_source resource, select "yes". The default is "no".
Type the name of a device, directory, or NIM lpp_source resource name to use as the source for the install images to recover the SIMAGES attribute for the selected lpp_source resource.
Type the alternate flags to be passed to the lsmksysb command. If you leave this field empty, the "-L" flag is used.
Executes the specified or selected script file on the first boot of the machine. This allows you to customize a machine after an installation. You can type the name of a new script file or select a script file from a menu list.
Provides options for removing from an lpp_source duplicate software images and software images that are not needed. You can remove duplicate software, superseded updates, language software that is no longer needed, and software that are not SIMAGES.
Select the operation to be run on this lpp_source.
To list only the software images that will be removed by this operation, select "yes". The default is "yes".
To remove duplicate base and update images from the specified lpp_source, select "yes". The default is "yes".
To remove superseded file sets from the specified lpp_source, select "yes". This action applies only to update images. The default is "yes".
To remove language and locale file sets that are not needed on your system, select "yes". This action removes all language and locale file sets from the specified lpp_source except the language specified in the "PRESERVE language" field. The default is "yes".
Choose which language to preserve in the specified lpp_source. All language and locale software that is NOT of the language you specify in this field will be removed. The default system value, "$LANG", will be used to determine the language to preserve if you do not specify another language.
To remove all file sets that are not needed for the lpp_source to have the "simages" attribute, which is required for the lpp_source to be used for rte BOS installations, select "yes". If you want only the minimum support needed for a BOS installation, select "yes". The default is "no".
To save all removed files to the directory specified below, select "yes". This moves the images to the specified directory instead of removing them from the hard drive. The default is "no".
Type the name of the directory where the removed files are being saved. Information is required in this field only if you selected "yes" in the "Save removed files" field.
Allows the system to extend file systems when you save removed files during specified operations and more space is required during processing.
"Yes" instructs the system to extend file systems as necessary. Once file system size is extended, it cannot be reduced. You must remove the entire file system. If you have plenty of hard disk space, choose "yes".
"No" instructs the system to NOT extend file systems. If you have limited hard disk space, choose "no". If you choose "no" and the system runs out of disk space during processing, a system message displays.
This menu provides options for you to add or remove software to or from an lpp_source.
To add software to the TARGET lpp_source, select "add". To remove software from the TARGET lpp_source, select "remove".
This menu allows you to select the specific software to remove from the TARGET lpp_source.
To remove software packages from the lpp_source, you can select the software package from the list or type the name of the package. To display the list, press the F4 key. If you type the package name, the format must be acceptable for the gencopy command.
Choose a NIM installp_bundle object that lists the software you want to remove from the TARGET lpp_source. To display the list, press the F4 key.
This menu allows you to select the source of the software. NIM will add the software selected for the source to the lpp_source.
Select a device, directory, or NIM lpp_source containing the software you want to copy into the TARGET lpp_source. When you specify a directory, you must provide the full path.
This menu allows you to select the specific software to add to the TARGET lpp_source.
Select the source media, directory, or lpp_source that contains the software to add to the TARGET lpp_source.
There are three ways you can specify software:
Type "all" to copy all software from the specified input device into your lpp_source.
Select F4 to display a list of software packages, then select the packages you want copied.
Type the name of the package. Your input must be acceptable by the gencopy command.
Choose a NIM installp_bundle object that lists the software you want to add to the lpp_source. To display the list, press the F4 key.
Select the flags to use when NIM invokes the gencopy command during an operation.
Provides options for specifying the settings for an Ethernet interface.
Sets the speed setting for the Ethernet adapter during NIM BOS installations. If you do not specify a value, the adapter's default value is used. You can specify the following settings: auto, 10, 100, and 1000. The default is 100.
Sets the duplex setting for the Ethernet adapter during NIM BOS installations. If you do not specify a value, the adapter's default value is used. You can specify the following settings: auto, half, and full. The default is "full".
Provides menus and options that guide you through the NIM operations that configure a NIM Master or NIM Client machine.
Provides menus and options for configuring a machine as a NIM master.
Provides menus and options for configuring a machine as a NIM client.
Provides options for configuring a system as a NIM master. You can select the software source to configure from, select the volume group to use for the NIM resources, and select the file system to use for the NIM resources. When the NIM master environment is configured, the basic NIM resources, lpp_source, spot, bosinst.data, and resolv.conf, are created.
Provides options for updating an installation of a specified set of fixes onto the default SPOT resource. A second SPOT resource containing the newly installed fixes is created by this operation.
Allows you to define and configure a machine as a NIM client and add it to the NIM environment.
Allows you to perform an update_all operation on a selected client or clients using an lpp_source resource.
Allows you to create a system backup image of a selected client and store the backup image on the NIM master.
Performs a mksysb restore or native (rte) installation on selected clients. You can select a system backup image to restore or use existing License Product Packages (lpp_source) for native installations and decide whether to reboot and install the client now.
Performs a reset operation on selected clients. This option resets the state of a client or clients in the NIM environment. Use this option after NIM operation has failed, and you want to return the client to the ready state.
Displays a list of the members of the EZ NIM environment, which include the master, clients, and resources, and their current state. For example, whether they are currently running, ready for a NIM operation, ready to use, or unavailable. Default resource group members are indicated with an asterisk.
Provides a list of the resource types available for checking, which includes: SPOT, mksysb, and lpp_source. If any of these resources exist in the NIM environment, they are in the list and you can select them to be verified.
If you select a mksysb type to verify, NIM runs the lsmksysb command on the resource and prints a list of file sets installed in the mksysb image. Flags are given for changing the output based on lsmksysb flags.
If you select a SPOT to verify, NIM runs the lppchk command to make sure the SPOT does not have inconsistent file set levels. This also verifies the checksum values contained in the SWVPD database and corrects anything that is different from what is expected.
If you select an lpp_source to verify, NIM runs an update operation on the resource to determine if it contains the default set of packages needed for an rte install. If not found, you can supply an option to NIM for adding the missing packages to the lpp_source.
Removes the NIM database without backing it up. Resources that reside in clients are not removed nor is the /etc/niminfo file from each client machine.
You can type the software source name or Press the F4 key to display a list of choices and select it from the list. The default is "cd0". Initializing the environment creates the following resources: lpp_source, spot, bosinst.data, and resolv.conf.
You can type the volume group name or Press the F4 key to display a list of choices and select it from the list. The default is "rootvg".
You can type the filesystem name or Press the F4 key to display a list of choices and select it from the list. The default is "export/eznim".
You can type the software source name or Press the F4 key to display a list of choices and select it from the list. The default is "cd0".
To update all the NIM clients in the current NIM environment, select "yes". This action perform an update_all operation on all the clients using an lpp_source resource.
You can type the names of the NIM client machines that you want to update or Press the F4 key to display a list and select them from the list.
You can type the name of the machine you want to back up or Press the F4 key to display a list and select it from the list. The machine can be the master or any of its clients.
Type the location of the existing backup. The format of the default location is /export/nim/<client>_sysbk.
Press the F4 key to display a list of machines you can select to reinstall. You can reinstall one or more clients at the same time. Clients will remain clients after the install is completed. The boot operation will initiate immediately and the client's boot list will be changed so that it boots from the network. Any mandatory software licenses will be automatically accepted.
Press the F4 key to display a list of backup resources you can use to reinstall the clients.
Press the F4 key to display a list of machines you can select to reset. This returns the client to the ready state. A machine must be in the ready state before operations can be run on it.
Defines the client machine in the NIM environment.
Allows you to perform an update_all operation on your clients using an lpp_source resource.
Performs a mksysb restore or native (rte) installation on the client. You can select a system backup image to restore or use existing License Product Packages (lpp_source) for native installations and decide whether to reboot and install the client now.
Resets the state of the client in the NIM environment. Use this option after a failed NIM operation to return the client to the ready state. NIM requires that a machine be in the ready state before operations can be run on it. While an operation is being performed, the state of the machine reflects the current operation. After the operation completes, the machine returns to the ready state. If an operation on a machine is interrupted, however, the machine state may continue to reflect the operation and the machine must be reset to the ready state before it can perform any more operations.
Specify whether the system backup image should be created when the savevg resource is being defined. The default is "no".
Select "yes" if the the system backup image to be associated with this savevg resource should be created as part of this operation. Select "no" if the system backup image to be associated with this savevg resource already exists.
The NIM name of the client that contains the volume group that you are backing up. You can specify a name only when you are creating a system backup image.
The name of the volume group that you are backing up. You can specify a name only when you are creating a system backup image.
Specify whether the space requirements for the system backup image should be displayed. The default is "no".
Select "yes" to display the maximum space required for the backup, along with the space available. The savevg resource is not defined and the system backup image is not created. Select "no" if you do not want to display the space requirements for the system backup image.
The name of the NIM VG_DATA resource that you want to add to the resource group definition. You can add only one resource of this type to a resource group. Information in this field is optional.
The name of the NIM SAVEVG resource that you want to add to the resource group definition. You can add only one resource of this type to a resource group. Information in this field is optional.
Type the name of one or more existing installp_bundle resources to remove from the group. Separate each name with a space. The resources are disassociated from the group after you finish adding any new installp_bundle resources to the group.
Select "yes" to accept the license agreement and install the software.
Select "no" to reject the license agreement and cancel the installation. Only clients and resources running AIX Version 5 and later can choose this option. Using it with earlier versions can cause the installation to fail with a usage error.
Multiple volumes will only be processed if the TARGET is local to the master and the SOURCE is a CD-ROM. Choose this option if you want to enable multi-volume CDs to be processed.
Processing software from CD-ROM source may require filesets stored on other CD volumes. Select "yes" to allow filesets on other CD volumes to be processed during the same session. If you select "no", even multi-volume CDs are seen as a single standalone CD and filesets on other CD volumes cannot be accessed.
Provides options for managing a NIM environment with alternate masters, including registering, synchronizing, and taking over control of the NIM environment.
Registers this machine as an alternate_master with an existing NIM master. This gives the existing NIM master remote access to this machine and allows the existing NIM master to run alternate master operations on this machine.
Defines an alternate master machine. The alternate master machine must initialize itself using the niminit command before this machine can run operations with the alternate master as the target.
Backs up the local NIM database, restores it onto the target alternate master, and checks the database for consistency.
Attempts to assume control of objects in the NIM environment from an alternate master that is currently in control of the NIM environment.
Removes an alternate master from the environment and removes its remote accesses permissions.
The NIM network interface on this machine that will be used to communicate with the alternate master.
The protocol this machine will use to communicate with the NIM master. Press the F4 key to display a list of supported communication protocols that you can select.
The NIM name of the alternate master. Press the F4 key to display a list of available alternate masters that you can select.
Overwrites the database if the target alternate master has an existing NIM database configured. A backup of the database is created before it is overwritten.
Provides options for managing secondary adapter definition files. You can perform the following tasks:
Adds a secondary adapter definition file of the specified client to the adapter definition resource.
Removes a client secondary definition files from an adapter definition resource.
Displays the contents of the specified client adapter definition file.
The name of the resource you are adding secondary definition files to.
The name of the NIM client that has a valid secondary adapter definition.
Specifying the machine type as secondary clearly distinguishes the nimadapters input from nimdef input. If a secondary adapter's file is mistakenly passed to the nimdef command, the error can be easily detected.
The network address for the secondary adapter.
The type of network interface, which can be one of the following: en, et, sn, or ml.
The subnet mask used by the secondary adapter.
Specify interface attributes and values, separated by blank spaces. For example, Attribute1=Value1 Attribute2=Value2. To see the list of attributes that can be set for the requested interface, run the command lsattr -E -l InterfaceName.
The cable type. This is optional if the network type is en or et.
Provide one or more comments to include in the secondary adapter definition.
The name of the network interface for the secondary adapter, for example, en1, sn0, ml0. Do not specify both a location and an interface name.
Note: The interface name must be consistent with the network type.
The physical location of the adapter corresponding to this network interface. Do not specify both a location and an interface name.
Note: Except for the multi-link pseudo-device, using "Location" is highly recommended. If the location is not specified and you add multiple adapters or add an adapter at the same time that the operating system is reinstalled, the adapter and network interface names might be reassigned by the operating system in unexpected ways.
The media speed. This is optional if the network type is en or et.
Host name to save in the /etc/hosts file with the netaddr attribute. This host name will not be set using the hostname command or uname -S command.
Specify adapter attributes and values, separated by blank spaces. For example, Attribute1=Value1 Attribute2=Value2. To see the list of attributes that can be set for the requested adapter, run the command lsattr -E -l AdapterName.
Specify a list of physical locations, separated by spaces, to specify the multiple physical location codes for an Etherchannel adapter an
d Virtual IP Address (VIPA).
Example: U0.1-P2-I6/E1 U0.2-P1-I5/E1
Specify the command tunchange to change the value of tuning parameters during BOS installation. The BOS Pre-Configuration value allows us
ers to change tunable parameters for a client that have otherwise been set by the /usr/lpp/bos.sysmgt/nim/methods/c_cfgadptrs script with
default values.
The format for this field would be in the form:
tunchange -f nextboot -t <Stanza> [ -o tunable=value ... ]
Specify the command vmo to change the value of tuning parameters during NIM customization. The Customization Pre-Configuration value allo
ws users to change tunable parameters that have otherwise been set by the /usr/lpp/bos.sysmgt/nim/methods/c_cfgadptrs script with default
values.
The format for this field would be in the form:
vmo -r [ -o tunable=value ... ]
Specify the route value to be added into the client's network routing table. The route attribute will accept three values which are:
The name of the adapter definition resource selected to be removed.
The name of the secondary definition file that contains secondary adapter definition for a NIM client. The client definition file resides in the location of the adapter definition resource.
Removes only the client definition file or all definition files from the adapter definition resource.
The name of the adapter definition resource selected to be viewed.
The name of the secondary definition file that contains secondary adapter definition for a NIM client. The client definition file resides in the location of the adapter definition resource.
Select "yes" to display information about the lpp source being created as the operation is taking place. Select "no" if you do not want to show the progress of the operation. The default is "yes".
Provides options for changing the primary interface of the NIM master and all its network attributes such as host name, IP address, subnet mask, network address, network adapter, and gateway to other NIM defined networks.
The host name of this new NIM master.
The type of Ethernet cable for this new NIM host. You can select the following cable types: bnc, dix, tp, and N/A.
The current host name of the NIM master being changed.
The type of network being defined. You can select one of the following: atm, tok, ent, fddi, and generic.
The NIM name of this new network.
The new IP address of the network being defined.
The subnet mask for the new NIM network.
The host name of the gateway used to communicate with other defined NIM networks.
Provides options for installing and configuring cryptographic software. After the software is installed, you can select nimsh as the communication protocol used by the client. Any incoming NIM Master service requests are authenticated through SSL socket connections.
To configure an existing standalone client to use NIM service handler communication protocol with SSL enabled, select "enable". This allows authentication based on key encryption. The default is "disable".
To install SSL, select "yes". This is required to use SSL encrypted certificates for authenticating the connecting NIM master. The default is "no".
If you are installing SSL from an RPM package, specify the absolute path for the RPM package. The default is /dev/cd0.
If you are installing SSL from an lpp_source, specify the resource that contains the SSL RPM package.
To display information about each file set or key word associated with this action, select "yes". The default is "no".
Select the communication protocol to be used by the client. Use the F4 key to display the list of options. You can select:
Specify the port number to be used by the secondary port.
Specify any range of ports to cycle through during nimsh operations. If you are changing the secondary port, choose a range of ports outside of the range used for system services, for example, 49152 through 65535.
For firewalls, you can open a specific range on the firewall, then for each machine on the internal network, ensure that the port range on the machine is within the open range on the firewall.
Provides options for installing and configuring cryptographic software. After the software is configured, participating NIM clients can request cryptographic authentication during service requests from the NIM master.
Provides options for installing and configuring cryptographic software. After the software is installed, you can select nimsh as the communication protocol used by the client. Any incoming NIM Master service requests are authenticated through SSL socket connections.
Provides options for managing the installation and cleanup of a client using the Virtual I/O DVD. These options enable you to perform the following tasks:
Use this option to create the necessary resources from the Virtual I/O DVD and to initiate an install on a client.
Use this option to remove the resources created from the Virtual I/O DVD and to return the NIM master to its original state.
Specifies the input device that is the source for the Virtual I/O software you are installing. You can type the software source name or press the F4 key to display a list of choices. The default value is cd0.
Type the IP address of the machine on which you will be installing the software.
Type the subnetmask (dotted decimal value) of the machine on which you will be installing the software.
Type the host name or IP address (dotted decimal value) of the default gateway (or router) used by the machine on which you will be installing the software.
Select the language environment that will be installed on the machine from a list of predetermined available languages for Vitual I/O and Integrated Virtualization Manager installation. The list is not generated from the installation source so certain selected languages may not be valid or supported from the installation source.
To force a reset and deallocation of resources on the client machine on which you are installing the software, type 'Yes'. This also removes all resources created for the installation of the Virtual I/O Server. Default value is 'No'.
To unconfigure the NIM master by removing the NIM daemons and all configuration informaton from the NIM database and to uninstall the NIM master fileset, type 'Yes'. Default value is 'No'.
Specifies the location to the NIM master fileset. Sets up the client as a NIM master so that NIM resources can be created for installing a Virtual I/O Server from the Virtual I/O DVD.
Allows you to configure the client as a NIM master for installing a Virtual I/O Server from the Virtual I/O DVD.
Executes the nimquery command to query a remote machine for system information. You can use this information to define a new client object in the NIM environment. System information is provided from the remote machines using the NIM Service Handler (nimsh).
Type either a NIM standalone client or a NIM machine group. The client(s) must be reachable via the network from the NIM master and must allow the NIM master to execute commands on them. If you specify a NIM machine group, they must all reside in the same NIM network. The client(s) are the target machine(s) that will be migrated onto equivalent LPARs on a POWER5 server.
Type the IP address that the new migrated client should be configured with after the client is installed onto the POWER5 server. If you specified a NIM machine group in the 'Existing NIM Client or Machine Group' field, you must supply a sufficient range of IP addresses to cover the number of clients you intend to migrate.
Type the subnet mask that the client(s) are to be configured with after the migration to the POWER5 server.
Type the IP address of the default gateway that the client(s) are to be configured with after the migration to the POWER5 server.
Type the hostname or IP address of the HMC or Logical Partition Manager that is used for hardware control of the POWER5 server to be used by the nim_move_up application.
Type the name of the managed system corresponding to the POWER5 server as tracked by the HMC or Logical Partition Manager.
Type the path to the source of the installation images to be used to create the NIM resources needed to perform the migration and installation. This path can be a device (such as dev/cd0 if using AIX product media) or a path to a location on the file system containing the installation images. The level of AIX present in the installation images must be 5.2 ML4 or above or AIX 5.3 or above.
Type the path to a location on the file system that will contain any new NIM resources created by the nim_move_up application. This location should have enough space to accommodate an lpp_source and a spot unless existing resources were provided through the 'Source of Install Images' and 'SPOT Name' fields.
Type the LPAR name of a Virtual I/O Server residing on the POWER5 server indicated in the 'Managed System Name' field.
Selecting 'Yes' forces the use of physical network adapters instead of shared ethernet adapters in creating the new LPAR on the POWER5 server when a virtual I/O server LPAR name has been provided.
Selecting 'Yes' forces the use of physical storage controllers instead of virtual SCSI adapters in creating the new LPAR on the POWER5 server when a virtual I/O server LPAR name has been provided.
Selecting 'Yes' means you accept all license agreements for any software installed automatically by the nim_move_up application during the migration process. Selecting 'No' means you will have to accept or deny each license agreement as it comes up during the migration process. Failing to accept a license agreement will stop the migration process.
Type the name of an existing lpp_source NIM resource to whose AIX level the target client(s) are to be migrated. If you do not provide an lpp_source name, the nim_move_up application will attempt to create a new lpp_source from the installation image source typed in the 'Source of Install Images' field.
Type the name of an existing spot NIM resource to be used in the migration and installation of the client(s). If you do not provide a spot name, a new spot will be created from the provided lpp_source NIM resource.
Type the name of an existing bosinst_data NIM resource to be used by the nim_move_up application to install the new clients onto the POWER5 LPARs. If you do not provide a bosinst_data NIM resource, the nim_move_up application will generate one with default unattended installation values.
Type the name of an existing exclude_files NIM resource that the nim_move_up application can use when creating a backup of the operating system of the original client(s). If you do not provide an exclude_files NIM resource, the nim_move_up application will generate one that excludes the contents of /tmp from the backup.
Type the name of an existing script NIM resource that the nim_move_up application can execute during the post-installation customization phase of the migration on all of the newly-migrated LPARs.
Type the name of an existing installp_bundle NIM resource whose software can be installed on each of the newly-migrated LPARs during the post-installation customization phase of the migration.
Type the name of an existing fix_bundle NIM resource whose APARs can be installed on each of the newly-migrated LPARs during the post-installation customization phase of the migration.
Type the name of the volume group to be used by the nimadm command for data caching. Default value is 'rootvg'.
Type the number of times to execute system analysis tools on the target NIM client(s) in analyzing its resource utilization. The final resource utilization data will be the average of the values obtained from each loop and will be taken into account when determining the equivalent POWER5 resources from which the migrated LPAR will be derived. Default value is one loop.
Type the number of seconds each loop run. Default value is ten seconds.
Selecting No executes only the next phase of the migration process. The nim_move_up application exits when the phase completes or fails. Selecting Yes means the nim_move_up application will not exit until all the subsequent phases are executed or one of the phases fails.
Selecting Yes configures the nim_move_up application to run in quiet mode. The terminal displays no output and all information is written to the logs. This option has no effect if you choose to let the nim_move_up application run in the background.
Selecting Yes configures the nim_move_up application to run in the background and returns control of the terminal to the caller. You can track the progress of the migration by selecting the 'Display the Current Status of nim_move_up' menu item.
Type the hostname or IP address of the HMC or Logical Partition Manager to be used for hardware control of the POWER5 server that is to be used by the nim_move_up application.
Selecting Yes unconfigures the environment and removes all NIM resources created by the nim_move_up application.
Displays NIM tasks for configuring and installing POWER5 LPARs.
Type the hostname or internet address of the Hardware Management Console (HMC) for the managed system in the 'Managed System Name' field.
Type the name of the managed system from which the client was partitioned.
Type the name of the partition, as it is defined on the Hardware Management Console (HMC), for the client machine being installed.
Type the name of the profile that contains the hardware configuration when activating the partition, for the client machine being installed.
If you do not want to configure the client's network after installation, type 'No' . Default value is 'Yes'.
To accept the Virtual I/O server license agreement, type 'Yes'; to accept the license agreement after the installation of the client machine, type 'No'. Default value is 'No'.
Displays the status of the execution of the next phase to be executed. All saved values are displayed as well. nim_move_up exits immediately after displaying the information.
Allows you to configure all required and optional input for the nim_move_up application. All values entered into the fields are saved and remembered through subsequent executions of the application and through subsequent invocations of this SMIT screen. This screen can also be used at any time to modify saved values after phases have been executed.
Allows you to execute nim_move_up phases, either one at a time, or all at once.
Allows you to set up SSH keys on the remote control host (Hardware Management Console or Logical Partition Manager) to allow the unattended remote execution of commands from th NIM master without password prompts, which is needed in order to cleanly execute all the phases (some of which remotely execute commands on this system).
Allows you to unconfigure the nim_move_up application's environment, removing all state information, including what phase to execute next, saved data files generated as a result of the execution of some phases, and all saved input values. Optionally, all NIM resources created through the nim_move_up application may be removed as well.
Provides an interface for running the nim_move_up application, which assists in migrating a back-level AIX system onto an LPAR residing on a POWER5 server.
Indicates whether to replicate the resources of a master onto an alternate master. Resources that are already present in the alternate master will not be replicated from the master. The default option is 'no'.
Indicates whether nim_move_up should transport to the new p5 Logical Partition all of the user-defined volume groups located on the physical machine. The default option is 'no'.
Manual configuration file(s) have to be given with a colon as a seperator between files. These file(s) are used in phase4 while creating the target LPAR. The values provided in these files would be used instead of the nim_move_up's automatically generated values.
Indicates whether the new LPAR(s) created as part of the nim_move_up migration should be removed, as well as any associated resources. The default option is 'no'.
Allows you to work with the installation inventory of NIM objects.
Type a comma-separated list of NIM objects that you want to inventory. If the NIM object is a physical machine, hardware inventory will be included.
Type the path to the directory to save the data. If the directory does not exist, it will be created. The data will be saved as inventory.<target_object>.<timestamp>. If the directory is not specified, all data will be displayed on the screen.
Type the path to the directory to save the data. If the directory does not exist, it will be created. The data will be saved as conglomerate.<target_object1:target_object2...>.<timestamp>. If the directory is not specified, all data will be displayed on the screen.
Determines whether colon-seperated output will be produced.
Name of the NIM object to use as the comparison base. If the NIM object is a physical machine, hardware inventory will be included. The comparison base acts as an exclusive list to compare against. If comparison against any installation inventory in the targets is required, use the keyword "any".
Type the path to the directory to save the data. If the directory does not exist, it will be created. The data will be saved as comparison.<base_object>.<target_object1:target_object2...>.<timestamp>. If the directory is not specified, all data will be displayed on the screen.
The name of the lpp_source to use as a filter for SUMA. If no 'Save Directory' or 'NEW lpp_source name' is specified and the 'Download Fixes' attribute is set to 'Yes', this lpp_source will be used as the save directory.
If 'Download Fixes' is set to 'Yes', this is the directory where the downloaded fixes will be stored. Use of this field requires use of the 'NEW lpp_source name' field. If this field is empty, fixes will be downloaded to the path listed in the 'Filter lpp_source' field.
The name of the new lpp_source to be created at the location listed in the 'Save Directory' field. The name must be unique and not already taken by an object in the NIM environment. The use of this field requires use of the 'Save Directory' field.
Indicates whether to download or preview fixes. See help messages for Filter lpp_source and Save Directory for details on where the fixes will be downloaded.
Identifies the ID of the Virtual Logical Area Network (VLAN) for VLAN tagging. The ID identifies the VLAN that the Ethernet frame belongs to. Using the ID, the network administrator can organize the client's communication logically rather than to the subnet. This value is consumed by NIM to network boot a client using the specified VLAN tag. The configuration of the VLAN tag communication must be done outside of NIM before using this value.
To configure an existing standalone client to use NIM service handler communication protocol with SSL as the desired form of communication with an alternate master, select an alternate master to exchange the SSL key.
Indicates whether to rebuild the /etc/niminfo for clients that are added before an alternate master. The option runs other NIM methods from the NIM master to configure the clients to work with the alternate master more efficiently.
To configure an existing alternate master to use NIM service handler communication protocol with SSL enabled, select "enable". This allows authentication based on key encryption. The default value is "disabled".