
IPU-POD128 build and test guide
Step 1: For lrack1 and lrack2
1a)
Copy
rack_config.json
to
rack_config.json_pod128
in the same directory:
cp /home/ipuuser/.rack_tool/rack_config.json /home/ipuuser/.rack_tool/rack_config.json_pod128
You then need to rewrite the
rack_config.json_pod128
config file to match the IPU-POD
128
IP addresses as
shown in
Section 8.7.3, Lrack1: rack_config.json file
Doing this means that you will be able to run
rack_tool
commands from the lrack1 management server for all the
IPU-M2000s, in both IPU-POD
64
racks (32 IPU-M2000s). Upgrading IPU-M2000 software for all 32 IPU-M2000s
can then be run as a single operation.
1b)
RNIC entries in lrack1 and lrack2
rack_tool.json
files
System fully connected with spine switches
If your IPU-POD
128
is using spine switches then you need to keep all the entries for the RNIC interfaces on both
lrack1 and lrack2
rnic_ip
in the lrack1
rack_tool.json
file. This file will also contain all the IPU-Gateway and
BMC interfaces for both lrack1 and lrack2. The lrack2
rack_tool.json
file is not required as lrack1 will be used
for all
rack_tool
operations.
System NOT fully connected with spine switches
If you are not using spine switches then you need to keep the entries for all the IPU-Gateway and BMC interfaces
for both lrack1 and lrack2 in the lrack1
rack_tool.json
file, but only the lrack1 RNIC interfaces
rnic_ip
. You
need to list the lrack2 RNIC interfaces
rnic_ip
in the lrack2
rack_tool.json
file instead.
Note:
There is no inter-rack RDMA connectivity (data plane) between the two IPU-POD
64
racks unless there is a
RoCE spine switch that brings the leaf switches together. This means that, on the data plane, the lrack1 server(s)
cannot access the lrack2 IPU-M2000s, and the lrack2 server(s) cannot access the lrack1 IPU-M2000s. The lrack1
server(s) can reach the lrack2 IPU-M2000s using the management network (control plane) for software updates.
Note:
Kubernetes will not be supported on the IPU-POD
128
unless there are spine switches providing inter-rack
RDMA connectivity.
Step 2: DHCP config files for lrack1 and lrack2
The DHCP config file
vlan-13.conf
contains the ports for the IPU-M2000 IPU-Gateway and BMC ports. You
need to add a copy of this file into a directory called
/etc/dhcp/dhcpd.d/lrack#
, where # denotes the rack (so 7
or 8 in our example). You also need to copy over the
vlan-11.conf
file.
2a) Lrack1
sudo mkdir /etc/dhcp/dhcpd.d/lrack1
sudo mkdir /etc/dhcp/dhcpd.d/lrack2
sudo cp /etc/dhcp/dhcpd.d/vlan-13.conf /etc/dhcp/dhcpd.d/lrack1
sudo cp /etc/dhcp/dhcpd.dvlan-11.conf /etc/dhcp/dhcpd.d/lrack1
2b) Lrack2
sudo mkdir /etc/dhcp/dhcpd.d/lrack2
sudo cp /etc/dhcp/dhcpd.d/vlan-11.conf /etc/dhcp/dhcpd.d/lrack2
sudo scp /etc/dhcp/dhcpd.d/vlan-13.conf ipuuser@pod7:/etc/dhcp/dhcpd.d/lrack2
2c) Lrack1 (required for spine switches)
You will need to run the following command if you have spine switches. If you don’t have spine switches then it is
not necessary, however, if you might add spine switches in the future then it is a good idea to run it now so that
lrack1 is prepared.
Version: latest (2021-11-25)
91