Note: The RS64, POWER3™, and 604 processors, 32-bit kernel, 32-bit kernel extensions and 32-bit device drivers are not supported.

Location	Allocated (Used)
/	196 MB (181 MB)
/usr	1936 MB (1751 MB)
/var	380 MB (264 MB)
/tmp	128 MB (2 MB)
/admin	128 MB (1 MB)
/opt	384 MB (176 MB)
/var/adm/ras/livedump	256 MB (1 MB)

Note: If the /tmp file system has less than 64 MB, it is increased to 64 MB during a migration installation so that the AIX V7.1 boot image can be created successfully at the end of the migration. Starting with AIX V6.1 Technology Level 5, the boot logical volume is required to be 24 MB in size. The pre_migration script will check if the logical volume is the correct size. The script is located on your AIX V7.1 installation media or it can also be located in an AIX V7.1 NIM SPOT. If necessary, the boot logical volume, hd5, size will be increased. The logical partitions must be contiguous and within the first 4 GB of the disk. If the system does not have enough free space, a message is displayed stating there is insufficient space to extend the hd5 boot logical volume.

AIX V7.1 Feature	Express	Standard	Enterprise
Vertical Scalability	4 cores, 8 GB per core	256 cores, 1024 threads	256 cores, 1024 threads
Cluster Aware AIX	Only with PowerHA	Yes	Yes
AIX Profile Manager (requires IBM Systems Director)	Management target only	Yes	Yes
AIX 5.2 Versioned WPAR support (requires the AIX 5.2 WPAR for AIX 7 product)	Yes	Yes	Yes
Full exploitation of POWER7 features	Yes	Yes	Yes
Workload Partition support	Yes	Yes	Yes
WPAR Manager and Systems Director Enterprise Edition	No	No	Yes

Note: Because the pathid argument can be repeated, both syntax pathid=0,2 and pathid=0 pathid=2 are equivalent. The order of the pathid arguments is how bootlist will process the paths. For example, pathid=2,0,1 will be different from patid=0,1,2.

Note: The lspath command also gets a new flag, -t, which makes it possible to print information using the pathid field. -t displays the path ID in addition to the current default output. The -t flag cannot be used with the -F or the -A flags. # lspath -t Enabled hdisk0 vscsi0 0 Enabled hdisk1 fscsi0 0 Enabled hdisk2 fscsi0 0 Enabled hdisk3 fscsi0 0 Enabled hdisk4 fscsi0 0 In case there is only one pathid, lspath and lspath -i 0 get the same output. # lspath Enabled hdisk0 vscsi0 Enabled hdisk1 fscsi0 Enabled hdisk2 fscsi0 Enabled hdisk3 fscsi0 Enabled hdisk4 fscsi0

option	values (default bolded)
version	v3 or v4
security	sys or krb5

Note: In order to propagate the Kerberos configuration to NIM clients, the credentials must be valid for NFS access when strong security is enabled.

Object name	Meaning
ent6	Represents an Ethernet IPv6 network. IPv6 clients must be a member of this network.
if1 new semantic	The third field of if1 must contain the client’s link-local address instead of the MAC address, such as If1=“v6net myclient.company.com fe80:23d7::663:4”

Note: For IPv6 clients, BOOTP is not used but the boot image is downloaded directly through TFTP, which requires specification of a boot image file name. The convention being used is that the boot image file name is simply the hostname used by the client.

Note: The NFS server calls the rpc.mountd daemon to get the access rights of each client, so the daemon must be running on the server even if the server only exports file systems for NFS version 4 access.

Note: Because Kerberos is relying on time, a mechanism should be invoked to automatically synchronize time through the network. The NIM server must run the AIX timed daemon or an NTP daemon.

Note: We did not have to specify any scripts to run. The scripts are all defined and referenced in the XML template file itself.

Note: Image creation must be performed after Activation Engine has been enabled.

Note: A template can reference as many scripts as it wants, as long as all those scripts are present on the optical media.

Note: Each template can also link to other template files, which allows for further flexibility. For example, you can create one template to customize all network parameters on the system, another to create new file systems, and another to add new custom user accounts and groups. This allows for easier categorization of customized data. It also makes it easier to add new customized data to the image because you can create a new template and have one of the existing templates point to the newly created file.

Note: The ae -o check command only checks syntax of the XML file, not the content. It does not check the existence of the script files referenced in the XML file.

Note: Activation Engine checks all bootable optical media for virtual image templates and uses the first one found. If you are booting a VDI on a system with two (or more) optical discs and all discs have virtual image templates, then AE will use the first template it finds on any of the mounted discs.