IPU-POD128 build and test guide
user: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether f4:02:70:b9:18:3e brd ff:ff:ff:ff:ff:ff
inet 10.1.7.150/16 brd 10.1.255.255 scope global eno1
valid_lft forever preferred_lft forever
inet 10.2.7.150/16 brd 10.2.255.255 scope global eno1
valid_lft forever preferred_lft forever
inet 10.3.7.150/16 brd 10.3.255.255 scope global eno1
valid_lft forever preferred_lft forever
....
8.4 Merging IPU-POD
64
racks to create IPU-POD
128
8.4.1 Networking pre-requisites
1. Make sure that the lrack1 and lrack2 1GbE management switches are trunked together on a site-specific
switch that takes VLAN 13 uplinks from each rack’s management switch and connects VLAN13 across both
IPU-POD
64
racks as one L2 broadcast domain.
Warning:
These trunks must be disabled for VLAN13 traffic forwarding during the phased
merge to a single IPU-POD
128
since the migration steps require the IPU-POD
64
racks to be
fully isolated during the upgrade to the new IP address scheme.
If your IPU-POD
64
1GbE switches have the VLAN13 ports named as VLAN-14 or VLAN14 then
you should correct them.
2. Make sure the DHCP files in both the lrack1 and lrack2 management servers are named vlan-13.conf not
vlan-14.conf:
$
sudo find . -name vlan-14.conf
/etc/dhcp/dhcpd.d/vlan-14.conf
If you do have to correct this then any references to these files should also be fixed in
/etc/dhcp/
dhcpd.conf
.
3. Turn off V-IPU services and DHCP services
To turn off the V-IPU services and DHCP services, use these commands:
sudo systemctl stop vipu-server.service
sudo systemctl stop isc-dhcp-server.service
8.4.2 Phase 1: Edit configuration files
A user with sudo rights needs to edit the configuration files first.
Warning:
It is important that you do NOT apply the new configuration until you have carried out all the steps
in this section and are ready to embark on
Section 8.4.3, Phase 2: Activate new configuration
Version: latest (2021-11-25)
90