This chapter contains information about Network Installation Management (NIM) error and warning messages, with suggestions for resolving specific problems.
If an error condition is detected when a NIM command is executed, the command returns an error message. If a NIM command returns a warning message, this indicates that either a less severe problem was encountered by NIM, or a problem was encountered in a command called by NIM, and the severity of the problem cannot be readily determined by NIM. In the latter case, additional messages or output from the command often reveal the true nature of the problem.
All NIM error messages begin with 0042 and are followed by a three-digit error code. All NIM commands use this three-digit error code as their exit code when fatal errors are detected. Warnings are also identified by a three-digit code but do not affect exit codes and are preceded by the warning label.
Information about each message is organized in the following manner:
Notes:
- If you require usage information for a NIM command, type the command without any arguments or with a question mark as an argument (for example, nim -? ). Additional information can be obtained from the lsnim command, which provides several options to display NIM help and usage information. For more information, refer to the -q, -O, and -P options of the lsnim command. You can also use the lsnim -p -a command to display information for all NIM classes, subclasses, types, and attributes. For example, to determine the list of valid values for an attribute, enter:
- If a User Action for a given error or warning specifies using the lsnim command for recovery hints, and if you are operating from a NIM client, use nimclient -l lsnimOperations, substituting the suggested lsnim options as appropriate.
- In some cases, a nim or nimclient operation that is being blocked because an object is in a particular state may be permitted with the use of the force option (the -F flag). However, by using the force option, you may adversely affect part of the NIM environment by forcing an operation that should only proceed after other actions are complete. Use error messages that are displayed without using the force option to determine if the force operation is a reasonable action.
- If you believe that your problem is the result of a software defect, or if the User Actions provided here do not provide adequate resolution to a problem, contact your point of sale.
To go directly to a specific message, click on one of the following numbers:
0042-001 0042-002 0042-003 0042-004 0042-005 0042-006 0042-007 0042-008 0042-011 0042-012 0042-013 0042-014 0042-015 0042-016 0042-017 0042-018 0042-019 0042-020 0042-021 0042-022 0042-023 0042-024 0042-025 0042-027 0042-028 0042-029 0042-030 0042-031 0042-032 0042-033 0042-034 0042-035 0042-036 0042-037 0042-038 0042-039 0042-040 0042-041 0042-042 0042-043 0042-044 0042-045 0042-046 0042-047 0042-048 0042-049 0042-051 0042-052 0042-053 0042-055 0042-056 0042-058 0042-059 0042-060 0042-061 0042-062 0042-063 0042-064 0042-065 0042-066 0042-067 0042-069 0042-073 0042-074 0042-075 0042-076 0042-077 0042-078 0042-079 0042-081 0042-083 0042-084 0042-086 0042-093 0042-109 0042-111 0042-113 0042-118 0042-121 0042-124 0042-129 0042-130 0042-131 0042-132 0042-133 0042-134 0042-135 0042-136 0042-137 0042-138 0042-139 0042-140 0042-141 0042-142 0042-143 0042-144 0042-145 0042-146 0042-147 0042-148 0042-150 0042-151 0042-152 0042-153 0042-154 0042-155 0042-156 0042-157 0042-158 0042-159 0042-160 0042-161 0042-162 0042-163 0042-164 0042-165 0042-166 0042-167 0042-168 0042-169 0042-170 0042-171 0042-172 0042-173 0042-174 0042-175 0042-176 0042-177 0042-178 0042-179 0042-180 0042-181 0042-182 0042-183 0042-184 0042-185 0042-186 0042-187 0042-188 0042-189 0042-190 0042-191 0042-192 0042-193 0042-194 0042-195 0042-196 0042-197 0042-198 0042-199 0042-204 0042-205 0042-206 0042-207 0042-208 0042-209 0042-210 0042-211 0042-212 0042-213 0042-214 0042-215 0042-216 0042-217 0042-218 0042-219 0042-220 0042-221 0042-222 0042-223 0042-224 0042-225 0042-226 0042-227 0042-228 0042-229 0042-230 0042-231 0042-232 0042-233 0042-234 0042-235 0042-236 0042-237 0042-238 0042-239 0042-240 0042-241 0042-242 0042-243 0042-244 0042-245 0042-246 0042-247 0042-248 0042-249 0042-250 0042-251 0042-252 0042-253 0042-254 0042-255 0042-256 0042-257 0042-258 0042-259 0042-260 0042-261 0042-262 0042-263 0042-264 0042-265 0042-266 0042-267 0042-268 0042-269 0042-270 0042-271 0042-272 0042-273 0042-274 0042-275 0042-276 0042-277 0042-278 0042-279 0042-280 0042-281 0042-282 0042-283
| Message | 0042-001 |
| Explanation | An error was detected by an underlying NIM method (a subcommand). This message describes where the error occurred with respect to the NIM client or master and may be useful in troubleshooting the problem. The messages that are displayed subsequent to this error are normally the true source of the problem. |
| User Action | Read the additional information and error messages, and refer to their explanation and recovery hints as appropriate. |
| Message | 0042-002 |
| Explanation | An interrupt signal has been received, perhaps because the user entered Ctrl-C or used the kill command on a NIM process. |
| User Action | The NIM operation that was active has been interrupted. Perform the operation again.
Note: This error is expected if it occurs after the nimclient -o bos_inst operation is performed on a client. |
| Message | 0042-003 and 0042-004 |
| Explanation | An error has been returned from a system call. |
| User Action | Fix the condition that caused the system call to fail and perform the operation again. |
| Message | 0042-005 |
| Explanation | The Object Data Manager (ODM) has returned an error. |
| User Action | Refer to the AIX Version 4.3 Messages Guide and Reference for specific details of the error. Fix the ODM problem and perform the NIM operation again. |
| Message | 0042-006 |
| Explanation | Generic error message used for rarely occurring NIM errors. |
| User Action | Phrases contained in this error message are constructed from debug information and from messages returned by commands called by NIM. If the content of the message does not give insight into the true cause of failure, contact your point of sale. |
| Message | 0042-007 |
| Explanation | An internal NIM error has occurred. |
| User Action | Try the operation again. |
| Message | 0042-008 |
| Explanation | NIM has attempted to establish socket communications with a remote machine, and it has refused the connection. |
| User Action | If the failing operation occurred on the master, verify that the master has rsh permissions on the client and that inetd is active on the client; otherwise, verify that the nimesis daemon is active on the master. If the failing operation was the niminit command on the client, a possible cause of failure is that the master does not have a network object that corresponds to the client's network. A network object that represents the client's network needs to be added to the database on the master; then a route needs to be added from the master's network to the client's network.
If the failure occurs during operations initiated from a client, using the nimclient command, or during a NIM installation of the base operating system, the cpuid attribute on the client's machine definition may be obsolete (for example, if the machine's system planar was recently replaced). To guarantee that this is not the case, erase the cpuid from the machine definition by issuing the following from the master: nim -Fo change -a cpuid= ClientName |
| Message | 0042-011 |
| Explanation | The /etc/niminfo file is not accessible. |
| User Action | The niminfo file is required by all NIM commands and methods. This file is created when the bos.sysmgt.nim.master and bos.sysmgt.nim.client packages are configured. If this file is not available, this indicates that the NIM package has not been initialized or that this file has been deleted. To create the niminfo file, execute the nimconfig command on the master or the niminit command on the client. To recreate a deleted or corrupted niminfo file, enter from the master:
nimconfig -r niminit -aname=ClientName -amaster=MasterHostName \ -amaster_port=MasterPortValue |
| Message | 0042-012 |
| Explanation | The specified command may only be executed on the master. |
| User Action | Execute the desired operation on the NIM master. |
| Message | 0042-013 |
| Explanation | The global lock used for synchronized access to the NIM database could not be obtained. |
| User Action | Try the operation again. If the same error is returned, verify that there are no active NIM commands. If this is true, remove the /var/adm/nim/glock file and try the operation again. If the file does not exist and the error persists, contact your point of sale. |
| Message | 0042-014 |
| Explanation | An internal NIM error has occurred. |
| User Action | Perform the remove operation on the NIM object followed by the appropriate define operation. |
| Message | 0042-015 |
| Explanation | A syntax error has been detected. |
| User Action | Refer to the appropriate man page for the NIM command and try again using valid syntax. |
| Message | 0042-016 |
| Explanation | An invalid option has been specified. |
| User Action | Refer to the appropriate man page for the NIM command and try again using valid syntax. |
| Message | 0042-017 |
| Explanation | An invalid value was specified for an option argument. |
| User Action | Refer to the appropriate man page for the NIM command and try again using valid syntax. |
| Message | 0042-018 |
| Explanation | A required option was not supplied. |
| User Action | Refer to the appropriate man page for the NIM command and try again using valid syntax. |
| Message | 0042-019 |
| Explanation | An option that requires an argument was specified without its argument. |
| User Action | Refer to the appropriate man page for the NIM command and try again, specifying the missing argument. |
| Message | 0042-20 |
| Explanation | An operand was required but not supplied. Usually, the operand is the NIM object to which a given operation is being applied (that is, a NIM name for a network, machine or resource object that is the target of the NIM operation). |
| User Action | Refer to the appropriate man page for the NIM command and try again using valid syntax. If you do not know the name of an operand, and if the failing operation was targeted toward an existing NIM object, enter:
lsnim -l -t ObjectType lsnim -l |
| Message | 0042-021 |
| Explanation | A NIM attribute was required for the operation. |
| User Action | Specify the missing attribute. If the failing command is the nim or nimclient command, to obtain a list of attributes, enter from the master:
lsnim -q ObjectName lsnim -q -t ObjectType nimclient -l lsnimOptions For the other NIM commands, see the appropriate NIM man page. |
| Message | 0042-022 |
| Explanation | A value was specified that exceeds the bounds of acceptable values. |
| User Action | Supply a value within the acceptable bounds. |
| Message | 0042-023 |
| Explanation | The specified value is not valid. |
| User Action | Try the command again with a valid value. To determine the valid values for classes of objects and operations as they pertain to those objects, enter:
lsnim -Pc ObjectClass lsnim -POc ObjectClass where ObjectClass is one of machines, networks, or resources. |
| Message | 0042-024 |
| Explanation | An invalid NIM object type was specified. |
| User Action | Specify a valid NIM object type. See user actions for error 023 for lsnim options to determine a valid object type. |
| Message | 0042-025 |
| Explanation | The specified operation cannot be supplied to the specified NIM object. |
| User Action | Specify an operation that can be applied to the object. Enter lsnim -O ObjectName for a list of valid operations that can be applied to the object. |
| Message | 0042-027 |
| Explanation | The specified object is missing an attribute that is required to complete the specified operation. |
| User Action | Redefine the object that is missing an attribute by performing the remove operation followed by the define operation. |
| Message | 0042-028 and 0042-029 |
| Explanation | The specified information cannot be supplied in the current context. |
| User Action | Try the operation again without supplying the offending attribute. |
| Message | 0042-030 |
| Explanation | A sequence number was opened to an attribute that doesn't allow sequence numbers. |
| User Action | Try the operation again without a sequence number on the offending attribute. |
| Message | 0042-031 |
| Explanation | An internal NIM error has occurred. NIM is unable to generate a unique object ID. |
| User Action | Try the operation again. |
| Message | 0042-032 |
| Explanation | The specified value for the attribute is not unique and it must be. |
| User Action | Supply a unique value for the attribute. |
| Message | 0042-033 |
| Explanation | The specified value is not unique and it must be. An attribute with a sequence number requires a unique value. |
| User Action | Supply a unique value. |
| Message | 0042-034 |
| Explanation | The specified value is not unique and it must be. |
| User Action | Supply a unique value. |
| Message | 0042-035 |
| Explanation | NIM was attempting to access an attribute that had the specified characteristics, but the attribute doesn't exist. |
| User Action | Make sure the attribute exists and retry the operation. |
| Message | 0042-036 |
| Explanation | The define operation failed for a resource because the specified server does not have a standalone configuration. |
| User Action | Try the operation again using a NIM client that is a standalone machine. |
| Message | 0042-037 |
| Explanation | The NIM state of the specified object prevents the operation from succeeding. |
| User Action | NIM states are used to synchronize activity among NIM objects. To perform the desired operation, the state of the specified object must be changed. If the specified object is in an unexpected state, check the system to make sure another user or process is not manipulating the object. Use the reset operation to set the object to a known state and try the operation again. |
| Message | 0042-038 |
| Explanation | An object that NIM would operate on is already locked and thus cannot be operated on. |
| User Action | NIM object locks are used to synchronize activity among NIM objects. These locks are temporary, so try the operation again after some delay. The value of the lock is the process ID of a NIM process that is using the lock. If the lock persists and no NIM commands are active, reset all NIM locks by stopping the nimesis daemon, then restarting it. |
| Message | 0042-039 |
| Explanation | The operating system version or release level of the specified object is unacceptable. |
| User Action | Perform the desired operation on objects that have the appropriate operating system version and release levels. |
| Message | 0042-040 |
| Explanation | A NIM object could not be removed because it is being used by some other NIM object. |
| User Action | Remove all references to the object to be removed before the remove operation is specified. If NIM states are such that you cannot remove references to the object and you want to remove the object anyway, provide the -F flag to the remove operation. |
| Message | 0042-041 |
| Explanation | A specified value has already been defined to NIM. |
| User Action | Specify a value that isn't already known to NIM.
Note: If /etc/niminfo is the value and the NIM command producing this error is niminit, this means that niminit has already been performed. If you want to reinitialize your NIM master or client, deinstall the appropriate fileset, and then reinstall and reconfigure the NIM master or client fileset. |
| Message | 0042-042 |
| Explanation | The specified machine could not be reached with the ping command from the master. |
| User Action | If the operation you were attempting to perform requires that the target machine be running and that it can be reached, then verify that the machine is currently running. If not, turn it on; otherwise, perform network diagnostic procedures to determine why the master could not reach the target machine. |
| Message | 0042-043 |
| Explanation | The remove operation cannot be performed, because the target machine currently serves a NIM resource that has been allocated for use. Performing the operation at this time could lead to processing failures on clients that are attempting to use the served resources. |
| User Action | You need to deallocate all resources that the target serves before you can remove the machine. |
| Message | 0042-044 |
| Explanation | You have specified a NIM attribute without an accompanying value. Most NIM attributes can only be specified with a value assigned to them in the form of attr=value. |
| User Action | Retry the operation with a value assigned to the specified attribute. |
| Message | 0042-045 |
| Explanation | Some NIM attributes can be added to an object's definition more than once. In these cases, a sequence number is used to uniquely identify each attribute of that type. In this case, you have specified an attribute of this type without its required sequence number and, therefore, NIM is unable to determine which attribute you are attempting to specify. |
| User Action | Verify the sequence number and try the operation again. |
| Message | 0042-046 |
| Explanation | NIM was unable to perform an operation on the specified file. This may be due to the permissions on the file. The file usually needs read, write, and, in some cases, execute permissions for root. |
| User Action | Change the permissions of the specified file and try the operation again. |
| Message | 0042-047 |
| Explanation | Some types of NIM resources may only be used by specific machine types. In this case, you attempted to allocate a NIM resource to a type of machine that is not allowed to use that type of resource. |
| User Action | Specify a resource type that the machine is allowed to use when performing allocation for the target machine.
To determine the valid resource types, enter: lsnim -p -s ResourceSubclassForMachineType To view the subclasses that are available, enter: lsnim -p -S |
| Message | 0042-048 |
| Explanation | When resource allocation is requested, NIM verifies that the designated client has the potential to communicate with the server of the resource. NIM does this by checking the NIM routing between the network that the client's primary interface connects to and all the networks that the server connects to. In this case, a NIM route is missing between the client and the server. |
| User Action | Either establish a NIM route between the client and the server or choose a different resource to allocate. |
| Message | 0042-049 |
| Explanation | Only one resource of this type may be allocated to the client and one has already been allocated. |
| User Action | Choose the resource that you want to use and deallocate the currently allocated resource of this type if you want to use the new one. |
| Message | 0042-051 |
| Explanation | NIM was unable to resolve a host name to an IP address or the other way around. |
| User Action | All host names that are used in the NIM environment must be resolvable. Perform the appropriate network administration tasks to ensure that the specified host name is resolvable and try the operation again. |
| Message | 0042-052 |
| Explanation | One or more NIM resources are still allocated to the machine that you have requested to be removed from the NIM environment. To remove a machine, it cannot have any resources allocated to it. |
| User Action | Deallocate all resources that have been allocated to the target machine and try the operation again. |
| Message | 0042-053 |
| Explanation | You have specified the name of a NIM object that does not currently exist in the NIM environment. NIM can only operate on objects that have been defined to NIM. |
| User Action | Verify that you have spelled the name of the object correctly and that it has already been defined. The name of a target machine for a NIM operation must be the NIM name, not the host name. Enter:
lsnim -l -t ObjectType lsnim -l to obtain listings of currently defined objects in the NIM environment. If you need to define the object, use the define operation. |
| Message | 0042-055 |
| Explanation | Many NIM operations require a source for installable images. You have specified a source that cannot be used for this operation. Examples of valid sources for NIM operations are: |
| User Action | Try the operation again using a source that the operation can use. |
| Message | 0042-056 |
| Explanation | You have specified the same attribute assignment more than once. |
| User Action | Try the operation again using only one instance of the attribute assignment. |
| Message | 0042-058 |
| Explanation | You have attempted to allocate a SPOT to a client whose primary network interface type or platform is not supported by the SPOT. For a client to use a SPOT, the SPOT must support the network interface type and platform of the client's primary interface. |
| User Action | Install the appropriate device support into the SPOT, which will allow the SPOT to support the client's primary interface type and platform, or choose a different SPOT that supports the client's primary interface type and platform. |
| Message | 0042-059 |
| Explanation | In an attribute assignment (in the form of attr=value), the value you have specified represents a NIM object whose type conflicts with the object type of the specified attr. |
| User Action | Try the operation again using the attr that corresponds to the type of object that value represents. |
| Message | 0042-060 |
| Explanation | You have specified multiple attribute assignments for an attribute that may only be specified once. |
| User Action | Try the operation again, using only one instance of the attribute. |
| Message | 0042-061 |
| Explanation | You have requested an operation to be performed on a NIM resource object that is currently allocated for client use. NIM is not allowing this operation to be performed because it may interrupt the client's use of the resource. |
| User Action | Try the operation again when the resource is not allocated for client use. If necessary, try the force option (-F flag) to disregard the preventive check by NIM. In some cases, NIM will allow the operation to be performed. |
| Message | 0042-062 |
| Explanation | The NIM object that was operated on is missing something that is required for its definition to be complete. |
| User Action | List information about the object using the lsnim command. Each item that is missing from the object's definition will be represented by a missing attribute. Perform the appropriate NIM operation that will add the missing item to the object's definition. For a SPOT, if network boot images are missing, apply the check operation to the SPOT. If software filesets are missing from a SPOT, allocate an lpp_source that contains the required filesets and apply the cust operation to the SPOT. |
| Message | 0042-063 |
| Explanation | Some NIM operations require access to one or more NIM resources to complete successfully. This access is granted through the allocate operation. In this case, you have not allocated all the resources that are required for this operation. |
| User Action | Allocate all the required resources and try the operation again. For a list of required and optional resources for a given operation, enter:
lsnim -q Operation ObjectName or lsnim -q Operation -t ObjectType |
| Message | 0042-064 |
| Explanation | The machine that is the target of the requested operation currently serves a NIM resource that is allocated for client use. The requested operation cannot be performed until all resources that the target serves have been deallocated for use. |
| User Action | Deallocate all resources that the target serves and try the operation again. |
| Message | 0042-065 |
| Explanation | You have specified a name that is reserved for NIM internal use only. |
| User Action | Try the operation again using a different name. To determine what names are reserved, enter:
lsnim -a reserved |
| Message | 0042-066 |
| Explanation | You have specified one or more characters that are not allowed in NIM object names. NIM uses regular expressions to perform many of its operations, so any character that has special meaning for regular expressions cannot be used (for example, ^). Also, any character that has special meaning to the shell cannot be used (for example, /). |
| User Action | Try the operation again using valid characters. |
| Message | 0042-067 |
| Explanation | You have requested an operation to be performed on a NIM object that has been reserved for NIM internal use only. |
| User Action | Try the operation again, using a NIM object that is not reserved. To determine what objects are reserved, enter:
lsnim -a reserved |
| Message | 0042-069 |
| Explanation | The requested operation cannot be performed at this time because it conflicts with the current NIM state of the target. NIM uses states to synchronize NIM activity so that operations don't interfere with each other. |
| User Action | Try the operation again when the state changes or, if necessary, try using the force option (-F flag). In some cases, NIM will allow you to override this state checking.
If you encounter this error as a result of trying to remove, using the reset operation, the boot resource from a client that incorrectly has a state of "ready for a NIM operation", you can remove the boot resource from the NIM master by entering: /usr/lpp/bos.sysmgt/nim/methods/m_dealloc_boot client_name where client_name is the name of the NIM object for the client. |
| Message | 0042-073 |
| Explanation | To perform customization on a machine, NIM constructs a shell script that is executed on the target. To construct this script, some type of resource that can be used for customization must be used. In this case, NIM could not create the customization script because no resources have been allocated to the target that could be used for customization purposes. |
| User Action | Allocate one or more resources that can be used for customization and try the operation again. To display the subclass of resources that can be used for customization, enter:
lsnim -p -s cust_res |
| Message | 0042-074 |
| Explanation | You have specified an attribute assignment in which the value represents a relative path name. NIM only allows absolute path names (that is, path names that begin with /) to be used. |
| User Action | Try the operation again, using an absolute path name. |
| Message | 0042-075 |
| Explanation | The requested operation requires that a NIM resource be exported for a machine's use. In this case, NIM attempted to export the resource but an error was returned by an NFS utility. |
| User Action | Fix the error condition that the NFS utility reported and try the operation again. |
| Message | 0042-076 |
| Explanation | You have specified a port number that is already in use. |
| User Action | Try the operation again, using a port number that is currently not being used Check the /etc/services file.
Note: NIM uses both the specified port number and its successor. Therefore, ensure that the port number after the specified port number is also free. |
| Message | 0042-077 |
| Explanation | The niminit command is used to join the NIM environment. When executed, this command attempts to add routing information that the NIM master has determined the client needs to participate in the NIM environment. In this case, one or more of the required routes could not be added. |
| User Action | Perform the appropriate network diagnostic task to determine why the route could not be added. |
| Message | 0042-078 |
| Explanation | You have specified a change to a NIM routing attribute in which the destination network is different from its current value. This is not allowed because only the gateway field of the routing attribute may be changed. |
| User Action | If you are trying to change the connectivity between NIM networks, then you must remove the current NIM route by supplying a NULL value for the appropriate routing attribute. Otherwise, specify the same destination network when attempting to change the gateway field of the routing attribute. |
| Message | 0042-079 |
| Explanation | In the NIM environment, one resource may depend on another for information. In this case, an allocated resource has a dependency on the resource you have specified for deallocation. |
| User Action | Deallocate the resource that is dependent on the resource causing the error. |
| Message | 0042-081 |
| Explanation | NIM uses NFS to make remote resources available for client use. To avoid NFS export errors, NIM enforces some restrictions on where a resource can be defined. In general, a NIM resource cannot be defined within a directory that is already a NIM resource. Conversely, a NIM resource cannot be defined for a directory that already contains an existing NIM resource. |
| User Action | Move the resource to a location that adheres to NIM export rules and try the operation again. |
| Message | 0042-083 |
| Explanation | Each network communications adapter has an associated network hardware address that is unique. In this case, you attempted to define a NIM network interface using a network hardware address already being used by a NIM machine object. |
| User Action | Only one NIM interface attribute may be defined for each network communications adapter a client might have. If you are attempting to add another interface definition, then verify that the hardware address is correct. If so, then you must first change the interface attribute that is currently using that address. If not, try the operation again with the correct hardware address. |
| Message | 0042-084 |
| Explanation | The machine has already been configured to be a NIM master. |
| User Action | If you want to reconfigure the machine as a NIM master, enter nim -o unconfig master , then deinstall and reinstall the master fileset. You may then run the nimconfig command. |
| Message | 0042-086 |
| Explanation | You have attempted to add a NIM route between two NIM networks that already have a NIM route between them. Only one NIM route can be specified between any two NIM networks. |
| User Action | If you are attempting to change NIM routing, delete the existing NIM route and try the operation again. |
| Message | 0042-093 |
| Explanation | NIM attempted to create a directory, and the mkdir command returned an error. |
| User Action | Fix the error reported by the mkdir command and try the operation again. |
| Message | 0042-109 |
| Explanation | To complete the requested operation, NIM requires information about one or more file systems about which it was unable to obtain information. |
| User Action | Verify that the file systems exist. If not, either specify the correct path name when performing the NIM operation or redefine the NIM environment so that all the participating file systems exist. |
| Message | 0042-111 |
| Explanation | When a sequence number is specified for a NIM attribute, it must be within a specific range. You have specified a sequence number that falls outside of the acceptable bounds. |
| User Action | Try the operation again using a sequence number that is within the acceptable bounds. |
| Message | 0042-113 |
| Explanation | To complete the requested operation, NIM requires information about the size of one or more objects, which NIM was unable to determine. |
| User Action | If the object is a file or directory that does not exist, then create the file or directory and try the operation again. |
| Message | 0042-118 |
| Explanation | You have requested to change characteristics of a NIM network on which there is currently one or more active NIM operations. NIM is not allowing the change because changing the network characteristics at this time could result in failures in the active operations. |
| User Action | Wait until the NIM resources allocated to machines that use the network being changed have been deallocated and try the operation again. |
| Message | 0042-121 |
| Explanation | An invalid value has been specified. |
| User Action | Try the operation again, using a valid value. |
| Message | 0042-124 |
| Explanation | An NFS option was specified that is not supported. |
| User Action | Try the operation again using valid NFS options. Refer to NFS Problem Determination in AIX Version 4.3 System Management Guide: Communications and Networks. |
| Message | 0042-129 |
| Explanation | An invalid resource type was specified for this operation. |
| User Action | Use the lsnim -q Operation -t TargetType command to view a list of required and optional resources for Operation when applied to TargetType. |
| Message | 0042-130 |
| Explanation | You have specified an attribute that cannot be used for this requested operation. |
| User Action | Try the operation again, without using the attribute you specified. |
| Message | 0042-131 |
| Explanation | You have specified two or more attributes that conflict with each other. |
| User Action | Try the operation again, using only one of the attributes. |
| Message | 0042-132 |
| Explanation | You have specified a value for an attribute assignment that is invalid in the context in which the operation is being performed. |
| User Action | Try the operation again, using a different value for the attribute assignment. |
| Message | 0042-133 |
| Explanation | The physical entity that is represented by the NIM resource object you have requested to be deleted could not be deleted. |
| User Action | Delete the file or directory, using the rm command. |
| Message | 0042-134 |
| Explanation | The operation you requested requires the designated target to reboot using a network boot image. NIM has automatically initialized the environment to enable the target to do this; however, NIM was unable to force the target to load the network boot image. |
| User Action | Intervention at the target is required. Follow the procedures for initiating a BOOTP request. |
| Message | 0042-135 |
| Explanation | To synchronize NIM operations that can be initiated from a client or on the master, NIM keeps track of which machine (the client or the master) is used to allocate the first resource to the client; this machine is said to be in control. For example, if the first resource allocation occurs from the client, then the client is in control. Once a machine has control, it remains in control until all resources for that client have been deallocated. You have requested an operation to be performed from a machine that is currently not in control of the specified target. |
| User Action | Perform the desired operation from the machine that is in control of the target, or from the controlling machine deallocate the resources (to remove the control), or override this behavior by using the force (-F flag) option when performing the operation from the master. |
| Message | 0042-136 |
| Explanation | The requested operation cannot be performed because a NIM route does not exist between two machines that participate in this operation. |
| User Action | Establish a NIM route between the networks. |
| Message | 0042-137 |
| Explanation | The /etc/niminfo file contains information about the NIM environment that all NIM commands require. In this case, the /etc/niminfo file is missing some information that is required to continue, which indicates that the file has been corrupted. |
| User Action | Reinitialize the NIM environment. |
| Message | 0042-138 |
| Explanation | Unable to update the rhost file. |
| User Action | Edit the $HOME/.rhosts file for root on the client machine to add an entry for the host name of the NIM master. |
| Message | 0042-139 |
| Explanation | The process of installing a machine prevents any attached disks from being used as the source for installable images. You have allocated a resource to the target of the install operation that is served by the target itself. |
| User Action | Deallocate the resource, allocate another resource of this type that is served by another machine, and try the operation again. |
| Message | 0042-140 |
| Explanation | You have requested that a machine object be removed from the NIM environment and this has been done; however, NIM was unable to remove the /etc/niminfo file on the machine that has been removed from the NIM environment. |
| User Action | Remove the /etc/niminfo file from the machine that was removed from the NIM environment.
Note: Verify that the .rhost permissions for the master have been removed from the client. |
| Message | 0042-141 |
| Explanation | By specifying an attribute assignment with a NULL value, you have requested NIM to remove the specified attr. However, in this case, the specified attr is not currently part of the specified object's definition. |
| User Action | Try the operation again, using an attribute that is part of the object's definition. |
| Message | 0042-142 |
| Explanation | All attribute values must be unique. You have specified a value in an attribute assignment that already exists. |
| User Action | Try the operation again, using a unique value for the attribute. |
| Message | 0042-143 |
| Explanation | Some NIM attributes can only be added to an object's definition once. In this case, you have specified an attribute of this type when one already exists for the specified object. |
| User Action | Only one attribute of this type can be used in the object's definition. Perform the change operation on the object if you want to replace the current value with a new one. |
| Message | 0042-144 |
| Explanation | Some NIM attributes require a unique sequence number so that NIM can distinguish between multiple attributes of that type. In this case, you have specified a sequence number that is already being used. |
| User Action | Try the operation again, using a sequence number that is not currently being used. To display the sequence number that are being used, enter:
lsnim -a AttributeName ObjectName |
| Message | 0042-145 |
| Explanation | You have specified an attribute that does not exist in the NIM environment. |
| User Action | Try the operation again, using a valid NIM attribute. To display a list of valid attribute names, enter:
lsnim -p -s info_subclass |
| Message | 0042-146 |
| Explanation | You have specified an object type that does not exist in the NIM environment. |
| User Action | Try the operation again, using a valid NIM object type. On the NIM master, the lsnim command can be used to display the valid NIM object types. |
| Message | 0042-147 |
| Explanation | You have attempted to execute a NIM command on the NIM master that can only be executed on NIM clients. |
| User Action | Execute the command on a NIM client. |
| Message | 0042-148 |
| Explanation | The information contained in the specified attribute is no longer valid. |
| User Action | Change the information in the attribute to reflect valid information and try the operation again. |
| Message | 0042-150 |
| Explanation | Any directory used to store NIM resources must be local to the machine that serves those resources. This is required because NIM can only NFS export local directories. In this case, you have specified a directory that is not local to the designated server of the directory. NIM has obtained this information from the file system of the designated server and the vfstype listed corresponds to values in the /usr/include/sys/vmount.h file. |
| User Action | Either copy the desired resources onto the designated server and perform the operation again, or specify the correct server when performing the operation. |
| Message | 0042-151 |
| Explanation | For NIM to use a file, it must be of a specific type. In this case, you have specified a file whose type cannot be used by NIM. NIM has obtained this information from the file system of the designated server of the file and the file type corresponds to values in the /usr/include/sys/mode.h file. |
| User Action | Change the file type of the file and try the operation again. |
| Message | 0042-152 |
| Explanation | When an installp operation is performed on a SPOT, the root directories of all diskless and dataless clients that use that SPOT must be synchronized with the changes made within the SPOT. In this case, one or more errors occurred when performing the root sync operation on a root directory. |
| User Action | Investigate why some of the root syncs failed and perform the operation again. The nim.installp log for the client root is located in RootResourceParentDirectory/ClientName/var/adm/ras. |
| Message | 0042-153 |
| Explanation | For NIM to use a file, it must have specific file permissions. In this case, you have specified a file whose permissions conflict with those required by NIM. NIM has obtained this information from the file system of the designated server of the file, and the value of the file permissions comes from the /usr/include/sys/mode.h file. |
| User Action | Change the file permissions of the file and try the operation again. |
| Message | 0042-154 |
| Explanation | For NIM to use a file, it must exist. You have specified a file that does not exist. |
| User Action | Create the file and try the operation again. |
| Message | 0042-155 |
| Explanation | For NIM to keep diskless and dataless root directories in sync with their corresponding SPOTs, NIM requires that the client's root directory be served from the same machine as its SPOT. In this case, you have requested a resource to be allocated that violates that requirement. |
| User Action | Try the operation again using resources that do not violate the NIM requirement. |
| Message | 0042-156 |
| Explanation | You have requested an operation to be performed that involves a directory that does not exist. |
| User Action | Create the missing directory and try the operation again. |
| Message | 0042-157 |
| Explanation | The operation you have requested could not be performed because a required file could not be accessed. |
| User Action | Create the missing file and try the operation again. For example:
|
| Message | 0042-158 |
| Explanation | The operation you have requested requires NIM to modify a file that it was unable to modify successfully. |
| User Action | Check the file permissions on the file and try the operation again. |
| Message | 0042-159 |
| Explanation | Required software is missing which prevents the target machine from acting as a SPOT server. |
| User Action | Install the missing software and retry the operation. |
| Message | 0042-160 |
| Explanation | The operation you requested requires the construction of network boot images and NIM was unable to do that. |
| User Action | Fix the problem that prevented the network boot images from being constructed and try the operation again. |
| Message | 0042-161 |
| Explanation | There is insufficient free disk space to complete the requested operation. |
| User Action | Increase the amount of available space, as detailed in the error message. |
| Message | 0042-162 |
| Explanation | To perform the requested operation, NIM requires an lpp_source type resource object that has the simages attribute as part of its definition. This attribute is used to designate that an lpp_source contains the total set of optional packages that are required to support NIM install operations. In this case, you have not supplied an lpp_source that fulfills this requirement. |
| User Action | Try the operation again using an lpp_source that has the simages attribute in its definition. |
| Message | 0042-163 |
| Explanation | NIM coordinates access between a client and the server of the resource. To do this, NIM must identify a network interface that can be used by the client. This becomes a complex problem when the server has more than one network interface. NIM uses a connectivity algorithm to establish which network interface to use. This error message occurred because the connectivity algorithm detected a problem with the client's routing and the interface the algorithm has selected to use. NIM does not allow the interface on the server that the client uses as a gateway to be used to serve resources because the operation requiring the resource could fail. |
| User Action | If the server has other network interfaces that are not known to NIM, change the server machine object to add the interfaces.
Define a NIM route between the client's primary network and one of the other networks to which the server connects. |
| Message | 0042-164 |
| Explanation | Some NIM operations do not allow the source of installable images to be a CD-ROM. NIM is not always able to construct an environment that supports the use of a CD-ROM for the operation being performed. This is true for the operation you tried to perform. |
| User Action | Try the operation again using a different source for installable images. |
| Message | 0042-165 |
| Explanation | Some attributes can only be specified together; others are mutually exclusive. In this case, you specified one or more attributes that conflict. |
| User Action | Try the operation again, omitting the attribute that was in conflict. For example, the ring_speed and cable_type attributes cannot be used with the same if attribute; the one you should use depends on the type of network interface referenced by the corresponding if attribute. |
| Message | 0042-166 |
| Explanation | The if attribute specifies network interface information, which includes a reference to the network object that the interface connects to. In this case, you have omitted a required attribute which is associated with the if attribute. |
| User Action | Try the operation again, including the required attribute. For example, the ring_speed attribute corresponds with the Token-Ring network interface, and the cable_type attribute corresponds with the Ethernet network interface. |
| Message | 0042-167 |
| Explanation | The device which you have specified as the source for the IPL ROM emulation, does not contain a valid, bootable image of the IPL ROM emulation. |
| User Action | If the specified device has media in it, this media either does not contain the IPL ROM emulation, or the media has been corrupted. Remake the IPL ROM emulation, and try the operation again. If the specified device has no media in it, make the IPL ROM emulation, put it in the device, and try the operation again. |
| Message | 0042-168 |
| Explanation | You have specified that the originating and destination network are the same. Machines that are on the same network do not need routing to communicate; therefore, adding a route from a network to itself is not allowed. |
| User Action | Specify a different originating and destination network when adding a NIM route. |
| Message | 0042-169 |
| Explanation | You have allocated an lpp_source, but you have not specified which filesets are to be installed using that lpp_source. |
| User Action | Specify the filesets to install using the filesets attribute in the command, or by allocating an installp_bundle that contains a list of the filesets to install. |
| Message | 0042-170 |
| Explanation | You entered a platform type that is not known to NIM. |
| User Action | The valid platform types are rs6k, rs6ksmp, and rspc. Correct the platform type attribute and try the operation again. |
| Message | 0042-171 |
| Explanation | Not all platform types are supported on all configuration types. For example, the diskless configuration type is not supported on the platform type rs6ksmp. |
| User Action | Use the correct platform type and try the operation again. |
| Message | 0042-172 |
| Explanation | You have specified the incorrect name of the machine object for the NIM client machine. When the niminit command is used to rebuild the niminfo file, the master registration process checks the CPU ID of the machine with the value stored in the NIM database for the named machine. If the stored value does not match the value passed by niminit, this message is issued. |
| User Action | Use the correct name and try the command again. |
| Message | 0042-173 |
| Explanation | You specified that the installp command should expand file systems (using the -X flag) while specifying that NIM should not auto expand (using the auto_expand attribute). This is not an allowable combination for the command invoked. |
| User Action | Use either the -X flag or the auto_expand attribute, but not both. |
| Message | 0042-174 |
| Explanation | You specified an invalid value for an attribute whose only valid values are yes and no. |
| User Action | Retry the operation with a value of yes or no for the attribute indicated. |
| Message | 0042-175 |
| Explanation | An unexpected result has been returned from a command that NIM tried to execute. |
| User Action | Fix the problem that caused the executed command to fail and try the operation again.
If the command failed due to a shortage of space, its error messages indicating this should be displayed. Expand the indicated file system, (for most NIM operations use the auto_expand attribute) and retry the operation. If a space failure occurred during SPOT creation, and if the bosboot command failed to make boot images as a result, increase the free space and run the check operation. If the command listed by NIM in this message is the installp command, check the nim.installp log for failure and recovery information. (For standalone client operations, this is located in the /var/adm/ras directory of the client. For SPOT cust and maint operations, this is located in SPOTParentDirectory/SPOTName/usr/lpp/bos/inst_root/var/adm/ras on the SPOT. For diskless and dataless clients, this is located in RootResourceParentDirectory/ClientName/var/adm/ras. |
| Message | 0042-176 |
| Explanation | The resource cannot serve as a support image (simages) lpp_source. When an lpp_source serves as a support image resource, it contains a minimal set of software packages for facilitating installation and the use of the base operating system. |
| User Action | No action is necessary if this resource does not need to serve as a support images lpp_source. If the resource needs to be a support images lpp_source, add the missing software to the lpp_source. If the lpp_source is a directory, you can do this by copying the missing packages to the location of the lpp_source and running the check operation. |
| Message | 0042-177 |
| Explanation | The operation you requested could not be completed due to insufficient free space in one or more file systems. |
| User Action | Make more space available if possible, by extending the file system displayed. For most NIM operations, the auto_expand attribute is available to automatically expand file systems. |
| Message | 0042-178 |
| Explanation | The if attribute is made up of four fields. The fourth field is optional in most cases. In this case. the network object that you specified (in field one) has more than one type of network. In this case, NIM requires that the fourth field has a value that specifies the logical device name of the network adapter. |
| User Action | Add the appropriate value to the if attribute, and try the operation again. |
| Message | 0042-179 |
| Explanation | You are attempting to remove an if or other_net_type attribute on which one or more NIM clients have a dependency. |
| User Action | If this is not a mistake, remove the NIM clients that are dependent on the network, or remove the if attribute from the NIM client object definition. |
| Message | 0042-180 |
| Explanation | The address of the machine that is being defined is not connected to the network that is represented by the specified network object. |
| User Action | Define a network object that represents the physical network to which the machine is connected. Use this network object when defining the machine. |
| Message | 0042-181 |
| Explanation | The fix_query_flags attribute has an illegal value. Use lsnim -Pa fix_query_flags for a list of legal values. |
| User Action | Determine the correct flags and retry the operation. |
| Message | 0042-182 |
| Explanation | A resource of one type cannot be allocated for the current operation at the same time as a resource of another type. Allocate one or the other, but not both. |
| User Action | The resources specified are mutually exclusive. Determine which one is needed for the operation, and omit the other. |
| Message | 0042-183 |
| Explanation | An attribute cannot be specified for the current operation when a type of resource is allocated. Use one or the other, but not both. |
| User Action | The attribute and the resource specified are mutually exclusive. Determine which one is needed for the operation, and omit the other. |
| Message | 0042-184 |
| Explanation | The network address (net_addr) or subnet mask (snm) cannot be changed for the network, because NIM clients are currently defined as being connected to that network. Remove the client definitions before changing the network. |
| User Action | The nimdef command can be used to quickly redefine NIM clients after they have been removed to update the network definition. |
| Message | 0042-185 |
| Explanation | Failed to link or copy files. Check permissions and file system space. |
| User Action | Verify that space and inodes are available for the files and links specified in the error message. |
| Message | 0042-186 |
| Explanation | Failed to copy setup programs. Either start NFS on the client or free 1000 512-byte blocks in the file system. |
| User Action | Programs required to set up the operation could not be copied to the client system. Either start NFS on the client, or increase space in the file system specified in the error message. |
| Message | 0042-187 |
| Explanation | Failed to expand file system. |
| User Action | Attempt to manually expand the file system specified in the error message, then retry the operation. |
| Message | 0042-188 |
| Explanation | Failed to NFS mount. |
| User Action | Verify that NFS is running on both the resource server and the client specified in the error message. Retry the operation when the NFS problems have been resolved. |
| Message | 0042-189 |
| Explanation | Failed saving existing boot image. Check space in the file system. |
| User Action | Increase space in the file system specified by the error message, and retry the operation. |
| Message | 0042-190 |
| Explanation | The key is not in the NORMAL position. Unattended installation cannot complete unless the key is in the NORMAL position. |
| User Action | Turn the key on the client machine to the NORMAL position and retry the operation. |
| Message | 0042-191 |
| Explanation | Unable to write the IPLROM emulation. |
| User Action | The mkboot command failed to write the IPLROM emulation on the client. Boot the client manually over the network to begin the BOS installation. |
| Message | 0042-192 |
| Explanation | Unable to find boot logical volume. |
| User Action | Verify that a boot logical volume is defined for the machine. NIM attempts to use the lslv -l hd5 command to determine the boot logical volume. |
| Message | 0042-193 |
| Explanation | The client does not have an .rhosts entry for the master, or the client host ID is not resolvable. |
| User Action | Verify that the client host name is resolvable by the master. Then verify that an entry exists for the master in the $HOME/.rhosts file for root on the client machine. |
| Message | 0042-194 |
| Explanation | The client does not allow NIM push operations. Remove /etc/nimstop on %s if push operation is necessary. |
| User Action | On the client machine, run the nimclient -p command to re-enable master push permissions. |
| Message | 0042-195 |
| Explanation | Unable to order boot device list. |
| User Action | An error was returned by the bootlist command on the client. If a network boot must be performed for a bos_inst, diag, or maint_boot operation, manually set the boot list and reboot the client, or follow the normal procedure to boot the client over the network. |
| Message | 0042-196 |
| Explanation | The set_bootlist attribute is only valid when used in combination with the no_client_boot or boot_client attributes. |
| User Action | Only specify the set_bootlist attribute to the nim command when changing the default behavior with the no_client_boot or boot_client attributes. |
| Message | 0042-197 |
| Explanation | If the target machine has more than one interface for a given network type, the network adapter's logical device name must be specified in the if1 attribute of the target machine's NIM definition when using the force_push attribute. |
| User Action | Modify the client's if1 attribute using the NIM change operation. Change the if1 attribute to include one of the client's network adapter logical device names listed in the error message. |
| Message | 0042-198 |
| Explanation | When converting a machine's /usr file system to a SPOT, the bos image on the media (lpp_source) being used to create the SPOT must match the bos image that was used to install the machine. |
| User Action | When defining the /usr SPOT, use the same installation media that was used to install the machine originally. For example, if a machine was originally installed with AIX 4.1.3 and then updates were applied to bring the machine to AIX 4.1.4, the installation media that should be used when defining the /usr SPOT on the machine would still need to be the AIX 4.1.3 product media. |
| Message | 0042-199 |
| Explanation | The no_client_boot and boot_client attributes may not be specified together. |
| User Action | To avoid the possibility of giving conflicting instructions to the NIM command, do not supply both the no_client_boot and boot_client attributes in the same NIM operation. |
| Message | 0042-204 |
| Explanation | The mk_image and source attributes are only valid when specified together. |
| User Action | When creating a mksysb resource from a running client machine, use the mk_image=yes attribute to indicate that a mksysb should be created, and use the source=ClientName attribute to specify the name of the client that is to be backed up. |
| Message | 0042-205 |
| Explanation | The bos.sysmgt.sysbr fileset must be installed on the client to perform the system backup. You may install this fileset with the NIM cust operation. |
| User Action | Install the bos.sysmgt.sysbr fileset on the client machine before retrying the operation. |
| Message | 0042-206 |
| Explanation | There is already a resource allocated. |
| User Action | Only one resource of the type specified can be allocated to the client. Deallocate the first resource before attempting to allocate the other. |
| Message | 0042-207 |
| Explanation | Unable to allocate a resource to a client. |
| User Action | Look for other NIM error messages that may accompany this error and which may provide more information about the problem. Verify that the resource specified is NFS-exportable to the client. |
| Message | 0042-208 |
| Explanation | Unable to lock a client. This could mean that the client is already locked, or the name given does not refer to a valid NIM client. |
| User Action | If another NIM operation is being performed on the same client, wait for the process to complete before retrying the operation. If no other NIM operations are being performed, stop and restart the nimesis daemon to remove locks. |
| Message | 0042-209 |
| Explanation | The mksysb_flags attribute contains an illegal value. Use the lsnim -Pa mksysb_flags command to get a list of legal values. |
| User Action | Specify the correct values for the mksysb_flags attribute, and retry the operation. |
| Message | 0042-210 |
| Explanation | The maximum space required for the backup is greater than the amount of free space in the target file system. To ignore space requirements, use the -F flag when defining the mksysb resource. |
| User Action | Either increase the space of the target file system where the mksysb is to be created, or use the -F flag as specified in the error message. |
| Message | 0042-211 |
| Explanation | The member already exists in group. |
| User Action | No additional action is required, since the member is already added to the group. |
| Message | 0042-212 |
| Explanation | The member was not added to the group, because it is not a valid NIM name. |
| User Action | The name of a member to add to a group was invalid. Verify that the member was specified correctly. |
| Message | 0042-213 |
| Explanation | The group was not created, because it did not contain any valid members. |
| User Action | A group must contain at least one member. Redefine the group with valid members to add it to the NIM environment. |
| Message | 0042-214 |
| Explanation | Unable to add a member to a group. |
| User Action | Look for other NIM error messages that may accompany this error and which may provide more information about the problem. |
| Message | 0042-215 |
| Explanation | An invalid log type for the showlog operation was specified. |
| User Action | Specify one of the valid log types listed in the error message. |
| Message | 0042-216 |
| Explanation | An invalid log type for the showlog operation was specified for a SPOT. |
| User Action | Specify one of the valid log types listed in the error message. |
| Message | 0042-217 |
| Explanation | An invalid log type for the showlog operation was specified for a diskless or dataless machine. |
| User Action | Specify one of the valid log types listed in the error message. |
| Message | 0042-218 |
| Explanation | The log file is either empty or does not exist. |
| User Action | No information is available in the log file for the machine or SPOT specified. |
| Message | 0042-219 |
| Explanation | The object is incompatible with the group. |
| User Action | The object cannot be added to the group, because its type is not allowed in the group. Machine groups can only contain one type of NIM client, and that type is determined by the first member added. Resource groups can only contain members whose types are resources. |
| Message | 0042-220 |
| Explanation | You cannot have more than one resource of the specified type in a resource group. |
| User Action | You must remove the current member with the specified type from the resource group before the new member with the same type can be added. |
| Message | 0042-221 |
| Explanation | The group %s is being removed, because its single remaining member was removed during this operation. |
| User Action | A group cannot be empty. Redefine the group with at least one member if it should remain in the NIM environment. |
| Message | 0042-222 |
| Explanation | An unknown error occurred allocating resources to the machine. |
| User Action | Look for other NIM error messages that may accompany this error and which may provide more information about the problem. Verify that the resource specified is NFS-exportable to the client. |
| Message | 0042-223 |
| Explanation | Invalid input file. The file either cannot be read, is empty, or contains no valid entries. |
| User Action | Verify that the file specified in the error message is the correct file for the operation. |
| Message | 0042-224 |
| Explanation | The limit on the length of a line in an NFS exports file was exceeded. The export operation cannot be performed. |
| User Action | Manually edit the /etc/exports and /etc/xtab files to remove any obsolete entries. The number of hosts to which NIM can NFS-export a resource can also be increased by setting the restrict_nfs_exports attribute to no on the master by running the nim -o change -a restrict_nfs_exports=no master command. |
| Message | 0042-225 |
| Explanation | An error occurred while updating the exports file. Check for corruption in the file. |
| User Action | Manually edit the /etc/exports and /etc/xtab files to fix any file corruption problems. Attempt to determine why NIM was unable to successfully update the files. Check file and directory permissions, and verify that file systems are not full. |
| Message | 0042-226 |
| Explanation | A timeout occurred while attempting to initiate the operation on the client. The operation may not have started successfully. |
| User Action | If the operation that was performed was bos_inst, the client only needs to be rebooted manually over the network to begin the installation. For all other operations, the problem is most likely due to network communication problems between the master and the client. Verify that the client is reachable by the master and that rsh permission is still granted by the client to the master. |
| Message | 0042-227 |
| Explanation | The state of the machine indicates that it may not be ready for certain NIM operations. |
| User Action | Check to see if any NIM operations are still being performed on the machine. If not, reset the state of the machine with the nim -Fo reset MachineName command. This returns the machine to the ready state so NIM operations can be performed on it. The reset operation does not deallocate resources, so deallocate resources if necessary using the nim deallocate operation. |
| Message | 0042-228 |
| Explanation | Invalid release level. |
| User Action | The release level of the resource is incomplete, or incorrectly specified. The level of the resource can be obtained by running the lsnim -l ResourceName command and viewing the version, release, and mod attributes. To correct the problem, either recreate the resource, or modify the NIM database to contain the correct level using the command on the NIM master: /usr/lpp/bos.sysmgt/nim/methods/m_chattr -a Attribute=Value ResourceName, where Attribute is version, release, or mod; Value is the correct value; and ResourceName is the name of the resource with the incorrect level specification. |
| Message | 0042-229 |
| Explanation | When installing a system using a mksysb as the source for the installation, the level of the SPOT used for the installation must match the level of the mksysb image being installed. The release levels of the SPOT and the mksysb do not match. |
| User Action | Create a SPOT that matches the level of the mksysb being installed, and use that SPOT when performing a mksysb BOS installation. The level of mksysb and SPOT resources can be obtained by running the lsnim -l ResourceName command and viewing the version, release, and mod attributes. |
| Message | 0042-230 |
| Explanation | When installing a system using a mksysb as the source for the installation, the level of the SPOT used for the installation should match the level of the mksysb image being installed. If this convention is not followed, the installation may not complete successfully. |
| User Action | Create a SPOT that matches the level of the mksysb being installed, and use that SPOT when performing a mksysb BOS installation. The level of mksysb and SPOT resources can be obtained by running the lsnim -l ResourceName command and viewing the version, release, and mod attributes. |
| Message | 0042-231 |
| Explanation | A temporary list of software that should be installed is created and used for this operation. The list could not be created. |
| User Action | Check previous error messages to understand why the error occurred. Correct the problem and try the operation again. |
| Message | 0042-232 |
| Explanation | A temporary installp_bundle resource is created and used for this operation. The temporary resource could not be created. |
| User Action | Check previous error messages to understand why the creation of the resource failed. Correct the problem and try the operation again. |
| Message | 0042-233 |
| Explanation | The operation cannot be performed because the NIM Master is already initialized. |
| User Action | Unconfigure the NIM Master and try the operation again. |
| Message | 0042-234 |
| Explanation | You cannot restore a NIM database backup onto a machine that has an earlier level of the NIM master fileset installed. For example, a NIM database backup of a system with level 4.2.0.0 of the NIM master cannot be restored to a system that has a level of the NIM master lower than 4.2.0.0. |
| User Action | Install a level of the NIM master fileset that is at the same level or a later level than that from which the backup was created. Then attempt to restore the NIM database backup. |
| Message | 0042-235 |
| Explanation | An image source was not specified for creating the SPOT. |
| User Action | Specify a device containing installation images or specify an lpp_source with the simages attribute for creating the SPOT. |
| Message | 0042-236 |
| Explanation | A name for the lpp_source and/or a directory to contain the lpp_source was not specified for the lpp_source that will be created. |
| User Action | Specify a name and a directory for the lpp_source and try the operation again. |
| Message | 0042-237 |
| Explanation | A name for the SPOT and/or a directory to contain the SPOT was not specified for the SPOT that will be created. |
| User Action | Specify a name and a directory for the SPOT and try the operation again. |
| Message | 0042-238 |
| Explanation | A parent directory was not specified for the diskless and dataless machine resources that will be created. |
| User Action | Specify a directory for the diskless/dataless machine resources and try the operation again. |
| Message | 0042-239 |
| Explanation | A name for the resource and/or directory to contain the resource was not specified for the resource that will be created. |
| User Action | Specify a name and a directory for the resource and try the operation again. |
| Message | 0042-240 |
| Explanation | A parent directory was not specified for the diskless and dataless machine resources that will be created. |
| User Action | Specify a directory for the diskless/dataless machine resources and try the operation again. |
| Message | 0042-241 |
| Explanation | The size and/or volume group was not specified for the creation of a new file system to contain a NIM resource. |
| User Action | Specify both the size and volume group for the file system and try the operation again. |
| Message | 0042-242 |
| Explanation | The size and/or volume group was not specified for the creation of a new file system to contain diskless and dataless machine resources. |
| User Action | Specify both the size and volume group for the file system and try the operation again. |
| Message | 0042-243 |
| Explanation | An attempt was made to create the same file system twice: once for an lpp_source and once for a SPOT. |
| User Action | Specify a different directory for either the lpp_source or the SPOT. This will cause different file systems to be created for the resources. If a new file system really should be created to contain both resources, then only specify that the file system should be created for one of the resources, but specify the same directory for both resources. |
| Message | 0042-244 |
| Explanation | An attempt was made to create the same file system twice: once for an lpp_source and once for diskless/dataless machine resources. |
| User Action | Specify a different directory for either the lpp_source or the diskless/dataless resources. This will cause different file systems to be created for the resources. If a new file system really should be created to contain both sets of resources, then only specify that the file system should be created for one of the resources, but specify the same directory for both resources. |
| Message | 0042-245 |
| Explanation | An attempt was made to create the same file system twice: once for a SPOT and once for diskless/dataless machine resources. |
| User Action | Specify a different directory for either the SPOT or the diskless/dataless resources. This will cause different file systems to be created for the resources. If a new file system really should be created to contain both sets of resources, then only specify that the file system should be created for one of the resources, but specify the same directory for both resources. |
| Message | 0042-246 |
| Explanation | Not enough space on the volume group to create the specified file system |
| User Action | Specify a different volume group for the file system to be created and try the operation again. |
| Message | 0042-247 |
| Explanation | Creation of the file system failed. |
| User Action | Check the previous output for error messages to understand what caused the file system creation to fail. Correct the error and try the operation again. |
| Message | 0042-248 |
| Explanation | An error occurred during file system creation. |
| User Action | Check the previous output for error messages to understand what caused the file system creation to fail. Correct the error and try the operation again. |
| Message | 0042-249 |
| Explanation | NIM master initialization failed. |
| User Action | Check the previous output for error messages to understand what caused the configuration of the NIM master to fail. Correct the error and attempt to reinitialize the master. The most frequent cause of this failure is that the master is already initialized. The master can be unconfigured with the nim -o unconfig master command and reinitialized. However, this should be done with extreme caution, since unconfiguring the master will remove all definitions from the NIM database. |
| Message | 0042-250 |
| Explanation | Unable to continue with configuration. |
| User Action | Check the previous output for error messages to understand what caused the configuration to fail. Correct the error and attempt to configure the system again from the point of failure. |
| Message | 0042-251 |
| Explanation | A route cannot be added to the network, because a required default route is missing. Add a default route to the network, and try this operation again. |
| User Action | Add a default route to the network specified in the error message, and retry the operation. |
| Message | 0042-252 |
| Explanation | Unable to locate a matching network. |
| User Action | The find_net keyword was used in the if attribute of the machine. However, no matching network was found. Either define the network prior to defining the machine interface, or use the net_definition attribute in conjunction with the find_net keyword to define the network while the interface is being defined. |
| Message | 0042-253 |
| Explanation | You cannot use the net_definition attribute when the find_net keyword is not specified as the first field of the if attribute. |
| User Action | The net_definition attribute is invalid when using a known network in the if attribute. Specify the find_net keyword in the if attribute, or omit the net_definition attribute, and retry the operation. |
| Message | 0042-254 |
| Explanation | Invalid format for the specified value of net_definition. The value of the attribute should be as follows:
If you want to specify NetName and if Client_gwName or Master_gwName are not applicable, specify 0 in their place. If Client_gwName is 0, Master_gwName cannot be nonzero. |
| User Action | Correct the syntax error, and retry the operation. |
| Message | 0042-255 |
| Explanation | The master already has a default route, and the gateway you specified as being the default for the master is different from that which is already defined. Use the change operation if you want to modify the master's default gateway. |
| User Action | To change the default gateway for a network, use the following command:
nim -o change -a routingX="default GatewayName" \ NetworkName where X is the sequence number for the routing attribute; GatewayName is the default gateway to use; and NetworkName is the name of the master's network. |
| Message | 0042-256 |
| Explanation | A default route already exists for the network. You can modify the default gateway, but you cannot define more than one default route. |
| User Action | To change the default gateway for a network, use the following command:
nim -o change -a routingX="default GatewayName" \ NetworkName where X is the sequence number for the routing attribute; GatewayName is the default gateway to use; and NetworkName is the name of the network to modify. |
| Message | 0042-257 |
| Explanation | You cannot specify the net_definition attribute without specifying the if attribute when changing a machine definition. |
| User Action | The net_definition must reference a machine interface, so specify an if attribute when using the net_definition attribute. |
| Message | 0042-258 |
| Explanation | You cannot specify the net_definition attribute when creating or modifying more than one if attribute in the same change operation. Use two separate operations. |
| User Action | To avoid ambiguity, manipulate only one machine interface (if attribute) at a time when using the net_definition attribute. |
| Message | 0042-259 |
| Explanation | The value of default_res specified on the master's database definition is not a valid NIM resource group. |
| User Action | Specify a valid NIM resource group as the default resource. Obtain a list of resource groups by running the lsnim -t res_group command. |
| Message | 0042-260 |
| Explanation | The default attribute is only applicable when manipulating a resource group. |
| User Action | Setting the default=yes/no attribute on a resource group makes it the default set of resources to use in NIM operations. The default attribute is invalid when used as an attribute in other NIM operations. |
| Message | 0042-261 |
| Explanation | Illegal use of the async attribute. This attribute can only be specified for the lppchk operation when the target is a standalone machine or a group of standalone machines. |
| User Action | Omit the async attribute when performing the lppchk operation, unless the target is a standalone machine or a group of standalone machines. |
| Message | 0042-262 |
| Explanation | The file name of the client definition file is missing for this operation. |
| User Action | Specify the client definition file that should be used to add machines to the NIM environment. For more information, see Network Installation Commands. |
| Message | 0042-263 |
| Explanation | The netboot_kernel attribute can only be assigned a value of up or mp. |
| User Action | Correct the value specified for the netboot_kernel attribute. |
| Message | 0042-264 |
| Explanation | The image source that was used to define the lpp_source is missing one or more requested packages. |
| User Action | Installation images were not copied into the lpp_source directory. The source for installation images may not contain all of the filesets specified to populate the lpp_source. Copy the missing installation images to the lpp_source directory, and then perform the NIM check operation on the lpp_source. |
| Message | 0042-265 |
| Explanation | The image source that was used to define the lpp_source is missing one or more items from the list of default packages. |
| User Action | Installation images were not copied into the lpp_source directory. The source for installation images may not contain all of the default filesets used to populate the lpp_source. Copy the missing installation images to the lpp_source directory, and then perform the NIM check operation on the lpp_source. |
| Message | 0042-266 |
| Explanation | Requested packages are missing from the defined lpp_source. |
| User Action | Installation images were not copied into the lpp_source directory. The fileset names may have been specified incorrectly, or the source for installation images may not contain all of the specified filesets. Copy the missing installation images to the lpp_source directory, and then perform the NIM check operation on the lpp_source. |
| Message | 0042-267 |
| Explanation | The defined lpp_source does not have the simages attribute, because one or more packages are missing. |
| User Action | Copy the missing installation images to the lpp_source directory, and perform the NIM check operation on the lpp_source to add the simages attribute. |
| Message | 0042-268 |
| Explanation | The operation cannot be performed, because all members of the target group specified are currently excluded from operations on the group. You must unmark (or include) excluded group members before proceeding. |
| User Action | Perform the NIM select operation on the group to include members in further operations. |
| Message | 0042-269 |
| Explanation | Only one type of verification can be performed at a time when verifying installed filesets on a NIM client. |
| User Action | Disable or deselect all but one verification option and try the operation again. |
| Message | 0042-270 |
| Explanation | The operation is only supported on SPOTs and NIM clients installed with a version and release level of 4.2 or greater. |
| User Action | The NIM client fileset on the target is at an earlier level and does not support the attempted operation. The client software on the target must be upgraded before the operation can be performed. |
| Message | 0042-271 |
| Explanation | A resource matching the type is already allocated. You cannot allocate more than one resource of this type to a machine. |
| User Action | Deallocate the first resource before attempting to allocate the second. It may be necessary to reset the machine before the resource can be deallocated. |
| Message | 0042-272 |
| Explanation | A value specified is not a valid value for default_re, because it is not a valid NIM resource group. |
| User Action | Specify a different resource group for the default_res attribute, or correct the resource group in question. |
| Message | 0042-273 |
| Explanation | A value specified cannot be used as the location for the mksysb image because it is a directory. You must specify the filename where the mksysb image currently resides or will reside after creation. |
| User Action | Specify a file name instead of a directory for the location of the mksysb resource. |
| Message | 0042-274 |
| Explanation | The -e flag in the mksysb_flags attribute and the exclude_files attribute cannot be specified together. Specify the -e flag with the mksysb_flags attribute to exclude the files in /etc/exclude.rootvg from the backup, or specify an exclude_files attribute. |
| User Action | Do not specify both the -e mksysb flag and an exclude_files resource when performing this operation. |
| Message | 0042-275 |
| Explanation | Unable to obtain possession of a lock file. If no NIM operations are currently in progress, remove the file and repeat the operation. |
| User Action | Use the ps -ef | grep nim command to list the running NIM processes on the system. If any NIM processes other than the nimesis daemon are running, wait for them to finish and then remove the file specified by the error message. |
| Message | 0042-276 |
| Explanation | A fileset must be installed before this operation can be performed. |
| User Action | Install the fileset listed in the error message before retrying the operation. Generally, the fileset needs to be installed on the client system. However, depending on the operation being performed, the NIM master may also need to have the fileset installed before the operation will succeed. |
| Message | 0042-277 |
| Explanation | Diskless and dataless machines cannot be defined with a primary network install interface residing on a generic NIM network. It is presumed that a network adapter defined on a generic NIM network does not support network boot. |
| User Action | To define the systems as diskless or dataless clients, they must first be connected to a NIM network that is known to support network boot, such as ethernet, token-ring, or FDDI. |
| Message | 0042-278 |
| Explanation | The interface specified does not correspond to a network adapter that is known to support network boot. As a result, the NIM master has been defined on a generic NIM network. Network boot-dependent operations, such as base operating system installation, will not be possible on any NIM client whose primary network install interface is defined on the same network as the NIM master. |
| User Action | Operations that rely on network boot capability cannot be performed on clients on generic NIM networks. Such operations must be performed using local media on the system. |
| Message | 0042-279 |
| Explanation | The interface specified maps to a subnet which has been defined as a generic NIM network. It will not be possible to perform network boot-dependent operations, such as base operating system installation, on the machine definition created by this operation. |
| User Action | Operations that rely on network boot capability cannot be performed on clients on generic NIM networks. Such operations must be performed using local media on the system. |
| Message | 0042-280 |
| Explanation | Specify a complete date and time for the scheduled operation in the form: YYMMDDhhmm . |
| User Action | Use the format described in the error message to correctly schedule a date and time for the operation. |
| Message | 0042-281 |
| Explanation | The /usr file system on the specified server cannot be converted to a NIM SPOT. Either the RM_INST_ROOTS variable was set to yes in a bosinst.data file during initial installation of the machine or inurid -r was subsequently invoked. The only way to create a SPOT on this machine is to specify the location to be something other than /usr or reinstall the machine and then create a SPOT in /usr. |
| User Action | The system is unable to support the creation of a /usr SPOT. A non-/usr SPOT may be created on the system by specifying a different value for the location attribute. |
| Message | 0042-282 |
| Explanation | The BOS installation has been enabled but could not be initiated, because the following file was not found on the target. To start the installation, do one of the following: |
| User Action | The NIM client fileset is not properly installed and configured on the target system. Follow the directions specified in the error message to correct the problem. |
| Message | 0042-283 |
| Explanation | The existence of a file on the server indicates that a NIM SPOT may still be mounted in a subdirectory which will be removed by this operation. Before attempting the operation again, unmount the SPOT's directory along with any other directories that may be mounted beneath the directory being removed. FAILURE TO DO SO WILL RESULT IN LOSS OF DATA ON THE SPOT SERVER! |
| User Action | A SPOT operation failed, and NIM was unable to unmount all the directories mounted into the SPOT. Manually unmount the directories specified in the error message before retrying the operation. The mount command can be used to list the directories mounted on the system, and the unmount command can be used to unmount directories. Use the -f option with the unmount command if necessary to force the unmount. |