This chapter provides hints and tips to help you when working with AIX in a partitioned environment.
Each partition, including the Full System Partition, must have a unique host name that can be resolved. Host names cannot be reused between the Full System Partition and the logical partitions.
If the host name of the partition must be changed, before changing the host name of the partition, do the following:
/usr/sbin/rsct/bin/runact -c IBM.ManagementServer SetRTASPollingInterval Seconds=0
/usr/sbin/rsct/bin/lsrsrc IBM.ManagementServer HostnameIf the partition is managed by multiple HMCs, multiple entries might exist, because each HMC has its own entry. The output will be similar to the following:
resource 1: Hostname = "hmc1.mydomain.mycompany.com"
/usr/sbin/rsct/bin/rmrsrc -s 'Hostname = "hmc1.mydomain.mycompany.com"' IBM.ManagementServerYou can verify that all entries have been removed by running Step 2 again.
/usr/sbin/rsct/bin/rmcctrl -z
/usr/sbin/rsct/bin/rmcctrl -AFor information on updating the partition information on the HMC, see the IBM IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590.
After a partition has been started, it uses the network adapter to communicate with the HMC. Both the HMC and the partition must be configured so they can use the network adapters to communicate with each other. The partition must be configured to identify the HMC (or HMCs) on the network. It is recommended that the network be configured using a Domain Name Service (DNS) server.
You can use either fully qualified host names or short host names to identify partitions and HMCs. However, it is recommended that each partition and HMC be identified using a fully qualified host name, as this identification ensures unique naming of all the partitions and the HMC in the network. Fully qualified host names cannot be more than 100 bytes in length.
The HMC and partitions can also be configured using a short host name, where the domain name is not defined. This is typically done in a private or test network. If the HMC is defined using a short host name, you must perform extra network configuration steps to ensure correct communications between the partitions and the HMC. If you use short host names rather than fully qualified host names, make sure that the short host names are unique and that the mappings to IP addresses are properly specified.
The search order between the local /etc/hosts file and the DNS can be specified using the /etc/netsvc.conf file or /etc/irs.conf file.
The following examples illustrate the scenarios supported:
root@partition_1 -> cat /etc/hosts 127.0.0.1 loopback localhost 9.3.3.151 partition_1 9.3.3.152 hmc123
root@partition_1.mydomain.mycompany.com -> cat /etc/hosts 127.0.0.1 loopback localhost 9.3.3.151 partition_1.mydomain.mycompany.com 9.3.3.152 hmc123.mydomain.mycompany.com
root@partition_1 -> cat /etc/hosts 127.0.0.1 loopback localhost 9.3.3.151 partition_1 9.3.3.152 hmc123
root@partition_1.mydomain.mycompany.com -> cat /etc/hosts 127.0.0.1 loopback localhost 9.3.3.151 partition_1.mydomain.mycompany.com 9.3.3.152 hmc123 hmc123.mydomain.mycompany.com
This section provides information about how to shut down a partition by using the HMC and by using AIX.
When a partition is up, it is in the Running state. To use AIX to shut down a partition, do the following:
The partition eventually changes to the Starting state, and the operator panel values display, which indicates AIX is now rebooting.
The partition will eventually change to the Ready state. You have now shut down AIX and its partition.
To start AIX, on the HMC, select Activate. When you select Activate, the HMC uses the boot mode selection in the partition profile.
To use the HMC to shut down a partition, do the following:
To activate the partition, select the partition and press the right mouse button. Select Activate. When you select Activate, the HMC uses the boot mode selection in the partition profile.
Closing a vterm window does not shut down a partition. However, closing the window logs you off that session and kills any processes that you are running from that vterm window.