IPU-POD128 build and test guide
#
server RNIC addresses also
set
by the Pod7 management server’s DHCP server
#
ONLY:
if
rack has
4
servers
host lr8-server1mx { hardware ethernet 1c:36:da:4b:ea:ef; fixed-address 10.5.8.150; }
host lr8-server2mx { hardware ethernet 1c:36:da:4b:ea:ef; fixed-address 10.5.8.151; }
host lr8-Server3mx { hardware ethernet 0c:44:a1:20:7c:83; fixed-address 10.5.8.152; }
host lr8-Server4mx { hardware ethernet 0c:44:a1:20:80:a3; fixed-address 10.5.8.153; }
Or: 3)
Modify
/etc/dhcp/dhcpd.d/lrack2/vlan-11.conf
on lrack2 using the new network addresses.
Note:
This is only required if you do NOT have spine switches enabling full RDMA connectivity between the two
IPU-POD
64
racks.
#
server RNIC addresses also
set
by the Pod7 management server’s DHCP server
#
ONLY:
if
rack has
4
servers
#
lr8-server1mx is setup using netplan to
10
.5.8.150
host lr8-server2mx { hardware ethernet 1c:36:da:4b:ea:ef; fixed-address 10.5.8.151; }
host lr8-Server3mx { hardware ethernet 0c:44:a1:20:7c:83; fixed-address 10.5.8.152; }
host lr8-Server4mx { hardware ethernet 0c:44:a1:20:80:a3; fixed-address 10.5.8.153; }
Next section requires changing so it no longer describes a live migration , but should describe migration from a
reference POD64
8.4.3 Phase 2: Activate new configuration
This section describes how to activate the new configuration to combine the two IPU-POD
64
racks into an
IPU-POD
128
. While this is ongoing users will not be able to use either of the two IPU-POD
64
racks.
Warning:
It is important that you do NOT apply the new configuration in this phase until you have carried out
all the steps in
Section 8.4.2, Phase 1: Edit configuration files
Step 6: Inform users of down time
If the IPU-POD
64
rack(s) are in use you need to inform all users that they will be unavailable for use while they are
switched over to form a single IPU-POD
128
. This activiation of the new configuration will generally take a couple
of hours.
Warning:
You need to follow these instructions in the order they are given to avoid problems with the con-
figuration activation. Do NOT enable VLAN13 trunking between the lrack1 and lrack2 management switches
at this stage.
Step 7: lrack2 DHCP server
7a)
The local lrack2 DHCP server must not service requests from the 1GbE management interface
vlan-13.conf
.
You therefore need to disable
vlan-13.conf
by editing the current DHCP setup
ipum-dhcp.conf
and removing
the
vlan-13.conf
file, as shown in
Section 8.6.3, Lrack2: /etc/dhcp/dhcpd.d/ipum-dhcp.conf
Note:
The following is only required if you do NOT have spine switches enabling full RDMA connectivity between
the two IPU-POD
64
racks.
7b)
Use the DHCP setup and file location
/etc/dhcp/dhcpd.d/lrack2/
for
vlan-11.conf
to use the new IP address
scheme for lrack2. Then restart the DHCP server on lrack2 with this command:
Version: latest (2021-11-25)
93