Under Construction
Connecting a Managed Systems (eBMC) as a DHCP Client
In eBMC systems, just like in managed systems with FSP, DHCP is used by default to assign the IP address. The HMC ports of the managed system must then each be connected to a private network of an HMC in which the HMC acts as a DHCP server.
The command “hmc lsnet” can be used to determine in which connected networks an HMC is configured as a DHCP server:
LPAR-Tool
$ 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.127.255.1 255.255.255.0 off on 10.127.255.2,10.127.255.254 off auto auto -
$
HMC-CLI
hscroot@hmc01:~> lshmc -n
hmc01,domain=,description=,"ipaddr=172.16.143.19,0.0.0.0,0.0.0.0,10.127.255.1","networkmask=255.255.255.0,255.255.255.255,255.255.255.255,255.255.255.0",gateway=172.16.143.1,nameserver=,dns=enabled,domainsuffix=gdl.mex.ibm.com,slipipaddr=10.253.0.1,slipnetmask=255.255.0.0,"ipaddrlpar=172.16.143.19,10.127.255.1","networkmasklpar=255.255.255.0,255.255.255.0","clients=10.127.255.7,10.127.255.5,10.127.255.6,10.127.255.9,10.127.255.8,10.127.255.3,10.127.255.2",...
hscroot@hmc01:~>
In the example output, a private network is connected to the HMC’s eth3 port. The HMC is configured there as a DHCP server (DHCP SERVER column, value on). The HMC itself has the IP address 10.127.255.1 in this network and manages the range 10.127.255.2 to 10.127.255.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, which can be easily checked with the command “hmc lssysconn“:
LPAR-Tool
$ hmc lssysconn hmc01
MTMS STATE TYPE IPADDR ALT_IPADDR SP SP_TYPE SP_PHYS_LOC
…
0000-BMC*101272558 Pending Authentication - Password Updates Required sys 10.127.255.8 unavailable - ebmc -
…
$
HMC-CLI
hscroot@hmc01:~> lssysconn -r all
...
resource_type=sys,type_model_serial_num=9105-22B*89B34G2,sp_type=ebmc,ipaddr=10.127.255.8,user_name=admin,alt_ipaddr=unavailable,state=Pending Authentication - Password Updates Required
...
hscroot@hmc01:~>
For eBMC systems, instead of the correct machine type, model and serial number (MTMS), “0000” is displayed for the machine type, “BMC” for the model and instead of the serial number, the IP address obtained via DHCP without decimal points, which in the example above leads to “0000-BMC-101272558” in the first column. As soon as the managed system has a connection to the HMC, this is replaced by the correct machine type, model and serial number!
For a new managed system, the connection is then in the “Pending Authentication” state, since no password has been set for the eBMC user. The connected eBMC port has been given the IP address 10.127.255.8. The password for authentication can be set with the command “hmc chsyspwd“:
LPAR-Tool
$ hmc chsyspwd hmc01 10.127.255.8
Enter the new password: XXXXXXXXXX
Retype the new password: XXXXXXXXXX
Shared connection to hmc01 closed.
state of system connection is 'No Connection' waiting vor 'Connected' (17 trials remaining)
state of system connection is 'No Connection' waiting vor 'Connected' (16 trials remaining)
Server-9105-22B-89B34G2(89B34G2) - 'Power Off'
$
HMC-CLI
hscroot@hmc01:~> chsyspwd -u admin -m 0000-BMC*102552558
Enter the new password: XXXXXXXXXX
Retype the new password: XXXXXXXXXX
hscroot@hmc01:~>
Note: The managed system can be specified either by the MTMS (here 0000-BMC-101272558) or the IP address (here 10.127.255.8).
The specified password is set for the eBMC user on the eBMC and also saved on the HMC. The HMC can use this to authenticate itself with the service processor (eBMC) of the managed system at any time.
The status of the managed system should then change to “Connected” within a minute (but sometimes it takes a little longer):
LPAR-Tool
$ hmc lssysconn hmc01
RESOURCE
MTMS STATE TYPE IPADDR ALT_IPADDR SP SP_TYPE SP_PHYS_LOC
…
9105-22B*89B34G2 Connected sys 10.127.255.8 unavailable - ebmc -
…
$
HMC-CLI
hscroot@hmc01:~> lssysconn -r all
...
resource_type=sys,type_model_serial_num=9105-22B*89B34G2,sp_type=ebmc,ipaddr=10.127.255.8,user_name=admin,alt_ipaddr=unavailable,state=Connected
...
hscroot@hmc01:~>
Note: If the managed system is to be connected to a second HMC, the corresponding steps must be repeated on the second HMC.
The managed system should not be powered on yet. The eBMC Managed System has another component (Virtualization Management Interface) that must be correctly configured before powering on.
The managed system is automatically given a name of the form “Server-TTTT-MMM-SSSSSSS“, where “TTTT” is the machine type, “MMM” is the model and “SSSSSSS” is the serial number of the managed system:
LPAR-Tool
$ ms show hmc01
NAME SERIAL_NUM TYPE_MODEL HMCS MODEL_NAME
...
Server-9105-22B-89B34G2 89B34G2 9105-22B hmc01 IBM Power System S1022s
...
$
HMC-CLI
hscroot@hmc01:~> lssyscfg -r sys | grep 89B34G2
name=Server-9105-22B-89B34G2,type_model=9105-22B,serial_num=89B34G2,ipaddr=10.127.255.8,sp_type=ebmc,state=Operating,state_detail=,detailed_state=None,sys_time=11/11/2024 10:37:01,...
hscroot@hmc01:~>
First, the managed system should be given a shorter name. To do this, use the command “ms rename“:
LPAR-Tool
$ ms rename Server-9105-22B-89B34G2 ms12
$
HMC-CLI
hscroot@hmc01:~> chsyscfg -m Server-9105-22B-89B34G2 -r sys -i 'new_name=ms12'
hscroot@hmc01:~>
Managed systems with eBMC have a Virtualization Management Interface (VMI). This is also connected to the HMC via the eBMC and requires its own IP address. If DHCP is used for the eBMC, the VMI should also obtain the IP address via DHCP. The current configuration can be displayed using the command “ms lsvmi“:
LPAR-Tool
$ ms lsvmi ms12
NAME INTERFACE IPV4ADDR_ORIG IPV4ADDR NET_MASK GATEWAY
ms12 eth1 static 0.0.0.0 0.0.0.0 0.0.0.0
ms12 eth0 static 0.0.0.0 0.0.0.0 0.0.0.0
$
HMC-CLI
hscroot@hmc01:~> lssysconn -r vmi -m ms12
resource_type=vmi,type_model_serial_num=9105-22B-89B34G2,interface=eth1,ipv4addr=0.0.0.0,gateway=0.0.0.0,net_mask=0.0.0.0,ipv4addr_orig=static,ipv6addr=::/0,ipv6_gateway=::,ipv6addr_orig=dhcp
resource_type=vmi,type_model_serial_num=9105-22B-89B34G2,interface=eth0,ipv4addr=0.0.0.0,gateway=0.0.0.0,net_mask=0.0.0.0,ipv4addr_orig=static,ipv6addr=::/0,ipv6_gateway=::,ipv6addr_orig=dhcp
hscroot@hmc01:~>
Note: The VMI has interfaces on both HMC ports.
As the output shows, static IP addresses are expected by default. The configuration must therefore be reconfigured to use DHCP. The command “ms chvmi” can be used for this:
LPAR-Tool
$ ms chvmi ms12 eth0 ipv4dhcp
$ ms chvmi ms12 eth1 ipv4dhcp
$
HMC-CLI
hscroot@hmc01:~> chsysconn -r vmi -m ms12 -o set -i eth0 -t ipv4dhcp
hscroot@hmc01:~> chsysconn -r vmi -m ms12 -o set -i eth1 -t ipv4dhcp
hscroot@hmc01:~>
A quick check with “ms lsvmi” shows that the two VMI interfaces are switched to DHCP:
LPAR-Tool
$ ms lsvmi ms12
NAME INTERFACE IPV4ADDR_ORIG IPV4ADDR NET_MASK GATEWAY
ms12 eth1 dhcp 0.0.0.0 0.0.0.0 0.0.0.0
ms12 eth0 dhcp 0.0.0.0 0.0.0.0 0.0.0.0
$
HMC-CLI
hscroot@hmc01:~> lssysconn -r vmi -m ms12
resource_type=vmi,type_model_serial_num=9105-22B-89B34G2,interface=eth1,ipv4addr=0.0.0.0,gateway=0.0.0.0,net_mask=0.0.0.0,ipv4addr_orig=dhcp,ipv6addr=::/0,ipv6_gateway=::,ipv6addr_orig=dhcp
resource_type=vmi,type_model_serial_num=9105-22B-89B34G2,interface=eth0,ipv4addr=0.0.0.0,gateway=0.0.0.0,net_mask=0.0.0.0,ipv4addr_orig=dhcp,ipv6addr=::/0,ipv6_gateway=::,ipv6addr_orig=dhcp
hscroot@hmc01:~>
The VMI only becomes active when the managed system is powered on, so the IP address is still displayed as “0.0.0.0“.
After the VMI configuration is complete, the managed system can be turned on by using “ms poweron“:
LPAR-Tool
$ ms poweron ms12
HMC-CLI
hscroot@hmc01:~> chsysstate -m ms12 -r sys -o on
hscroot@hmc01:~>
The state of the managed system changes from “Power Off” to “Initializing” after a short time, as the output of “ms status” shows:
LPAR-Tool
$ ms status ms12
NAME STATE DETAILS IPADDR SECONDARY KEYLOCK SERVICE_LPAR_ID
ms12 Initializing None 10.127.255.8 - norm unavailable
$
HMC-CLI
hscroot@hmc01:~> lssyscfg -r sys | grep 89B34G2
name=Server-9105-22B-89B34G2,type_model=9105-22B,serial_num=89B34G2,ipaddr=10.127.255.8,sp_type=ebmc,state=Initializing,state_detail=,detailed_state=None,sys_time=11/11/2024 10:48:38,...
hscroot@hmc01:~>
Depending on the machine type, it takes different amounts of time until the initialization is completed. The state then changes to “Operating“:
LPAR-Tool
$ ms status ms12
NAME STATE DETAILS IPADDR SECONDARY KEYLOCK SERVICE_LPAR_ID
ms12 Operating None 10.127.255.8 - norm 1
$
HMC-CLI
hscroot@hmc01:~> lssyscfg -r sys | grep 89B34G2
name=Server-9105-22B-89B34G2,type_model=9105-22B,serial_num=89B34G2,ipaddr=10.127.255.8,sp_type=ebmc,state=Operating,state_detail=,detailed_state=None,sys_time=11/11/2024 10:51:13,...
hscroot@hmc01:~>
The VMI interfaces then also obtained an IP address via DHCP from the HMC(s):
LPAR-Tool
$ ms lsvmi ms12
NAME INTERFACE IPV4ADDR_ORIG IPV4ADDR NET_MASK GATEWAY
ms12 eth1 dhcp 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0
ms12 eth0 dhcp 10.0.0.159 255.255.128.0 0.0.0.0
$
HMC-CLI
hscroot@hmc01:~> lssysconn -r vmi -m ms12
resource_type=vmi,type_model_serial_num=9105-22B-89B34G2,interface=eth1,ipv4addr=0.0.0.0,gateway=0.0.0.0,net_mask=0.0.0.0,ipv4addr_orig=dhcp,ipv6addr=::/0,ipv6_gateway=::,ipv6addr_orig=dhcp
resource_type=vmi,type_model_serial_num=9105-22B-89B34G2,interface=eth0,ipv4addr=10.127.255.159,gateway=0.0.0.0,net_mask=255.255.255.0,ipv4addr_orig=dhcp,ipv6addr=::/128,ipv6_gateway=::,ipv6addr
hscroot@hmc01:~>
The managed system is now ready for use.
It is recommended to check the system firmware and possibly do a system firmware update (or upgrade).