This section contains information about compatibility and limitations between AIX Version 4.1 and AIX Version 4.2 (and later).
The resolv_conf resource is not supported when allocated to a Version 4.1 machine target.
Resources served from an AIX Version 4.1 client cannot be used when performing operations on machine groups.
Creating a system backup image while defining a mksysb resource is not supported when using an AIX Version 4.1 client as the source of the backup.
Default routes cannot be used to install an AIX Version 4.1 machine from an AIX Version 4.2 (and later) master, unless APAR IX59393 is installed in the AIX Version 4.1 SPOT used for the installation.
An AIX Version 4.2 (and later) lpp_source cannot be served from an AIX Version 4.1 NIM master. An Authorized Program Analysis Report (APAR) may be applied to the AIX Version 4.1 NIM master to allow this function. Apply APAR IX59032 to the AIX Version 4.1 NIM master.
Due to kernel changes in AIX, a SPOT cannot be created at a level of AIX that is higher than the level of AIX installed on the server of the SPOT. For example, an AIX Version 4.1 NIM master cannot serve an AIX Version 4.2 (and later) SPOT. In order to have an AIX Version 4.2 (and later) SPOT in an environment where the NIM master is running AIX Version 4.1, a client may be installed with AIX Version 4.2 (and later), and it can serve the AIX Version 4.2 (and later) SPOT. For backwards compatibility, an AIX Version 4.2 (and later) master may serve AIX Version 4.1 lpp_source and spot resources.
Note: An older release cannot serve the lpp_source of a later release.
Machines must have at least 32 MB of memory in order to run AIX 4.3.
Remote dump is not supported over ISA ethernet. Therefore, an error will occur under either of these conditions:
This is the error message you will receive:
Cannot set primary dump device host:/location
Operation not supported on socket where host:/location is the remote location at which you are attempting to
set the dump device.
On clients using a LAN SCSI adapter to access a NIM server it is not possible to declare the client with the niminit command.
It is possible to work around this problem by creating the NIM object that describes the client machine on the NIM server. This is done using the following command:
nim -o define