Specifications

Chapter 2. Architecture and technical overview 103
For the HMC to communicate properly with the managed server, eth0 of the HMC must be
connected to either the HMC1 or HMC2 ports of the managed server, although other network
configurations are possible. You can attach a second HMC to HMC Port 2 of the server for
redundancy (or vice versa). These must be addressed by two separate subnets. Figure 2-36
shows a simple network configuration to enable the connection from HMC to server and to
enable Dynamic LPAR operations. For more details about HMC and the possible network
connections, see Hardware Management Console V7 Handbook, SG24-7491.
Figure 2-36 HMC to service processor and LPARs network connection
The default mechanism for allocation of the IP addresses for the service processor HMC
ports is dynamic. The HMC can be configured as a DHCP server, providing the IP address at
the time the managed server is powered on. In this case, the FSPs are allocated IP address
from a set of address ranges predefined in the HMC software. These predefined ranges are
identical for Version 710 of the HMC code and for previous versions.
If the service processor of the managed server does not receive a DHCP reply before time
out, predefined IP addresses will be set up on both ports. Static IP address allocation is also
an option. You can configure the IP address of the service processor ports with a static IP
address by using the Advanced System Management Interface (ASMI) menus.
Power System
LPAR
n
LPAR
...
LPAR
2
LPAR
1
entxentxentxent1
Service
Processor
HMC 2
eth0
HMC 1
eth1
Management LAN