This is the standard case. All managed systems are delivered with FSP or eBMC configured as a DHCP client. The HMC ports of the managed system must then each be connected to a private network of an HMC in which the HMC is configured as a DHCP server.

The networks in which an HMC is configured as a DHCP server can be determined using the “hmc lsnet” command:

$ hmc lsnet hmc01
INTER  IPV4           IPV4           IPV4  DHCP    DHCP                 JUMBO          
FACE   ADDR           NETMASK        DHCP  SERVER  SERVERRANGE          FRAME  SPEED  DUPLEX  TSO
eth0   172.16.143.19  255.255.255.0  off   off     -                    off    auto   auto    -
eth1   0.0.0.0        0.0.0.0        on    off     -                    off    auto   auto    -
eth2   0.0.0.0        0.0.0.0        on    off     -                    off    auto   auto    -
eth3   10.0.0.1       255.255.255.0  off   on      10.0.0.2,10.0.0.254  off    auto   auto    -
$

In the example output, a private network is connected to port eth3 of the HMC. The HMC is configured there as a DHCP server (column DHCP SERVER, value on). The HMC itself has the IP address 10.0.0.1 in this network and manages the range 10.0.0.2 to 10.0.0.254.

As soon as one of the two HMC ports of the managed system is connected to this network, DHCP requests from the service processor of the managed system are answered and the managed system is assigned an IP address. After a few minutes the managed system should be visible on the HMC:

$ hmc lssysconn hmc01
TYPE_MODEL_SERIAL_NUM  STATE                  RESOURCE_TYPE  IPADDR      ALT_IPADDR   SP       SP_PHYS_LOC
8202-E4D*17B13DU       Connected              sys            10.0.0.4    unavailable  primary  U78AA.001.WZRKU4X-P1
8284-22A*323431V       Connected              sys            10.0.0.12   unavailable  primary  U78CB.001.WZR1CEV-P1
...
8205-E6C*17E4E7S       Failed Authentication  sys            10.0.0.234  unavailable  primary  unavailable
...
8284-22A*67D416X       Connected              sys            10.0.0.23   unavailable  primary  U78CB.001.WZR1M5B-P1
$

The output shows the “new” managed system in the “Failed Authentication” state. The IP address 10.0.0.234 has been assigned. The HMC access password for the ASMI user access must be specified so that the state can change to “Connected”. This can be done with the command “hmc chsyspwd”:

$ hmc chsyspwd hmc01 10.0.0.234 XXXXXXXX
Shared connection to virt-hmc01 closed.
$

The specified password is saved on the HMC and is used for authentication with the service processor of the managed system.

The status of the managed system should then change to “Connected” after a few seconds:

$ hmc lssysconn hmc01
TYPE_MODEL_SERIAL_NUM  STATE      RESOURCE_TYPE  IPADDR      ALT_IPADDR   SP       SP_PHYS_LOC
8202-E4D*17B13DU       Connected  sys            10.0.0.4    unavailable  primary  U78AA.001.WZRKU4X-P1
8284-22A*323431V       Connected  sys            10.0.0.12   unavailable  primary  U78CB.001.WZR1CEV-P1
...
8205-E6C*17E4E7S       Connected  sys            10.0.0.234  unavailable  primary  U78AA.001.WZRIW2S-P1
...
8284-22A*67D416X       Connected  sys            10.0.0.23   unavailable  primary  U78CB.001.WZR1M5B-P1
$

The “hmc rescan” command should then be executed for the HMC in order to update the LPAR tool’s information about managed systems and LPARs.

$ hmc rescan hmc01
hmc01:
   ms25(971BA04)
…
$

If the managed system is to be connected to another HMC, the corresponding steps must be repeated on the second HMC.