IPU-POD128 build and test guide
8.7 /etc/netplan files
8.7.1 1GbE management interface on lrack1 server
The 1GbE management interface is required to have the setup described in this section. The
eno1
interface has
three IP subnets for communicating with: BMC ports, IPU-Gateway ports, and between servers (for example
V-IPU CLI to V-IPU controller on the management server, and Poplar instance to V-IPU controller).
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether bc:97:e1:46:00:b6 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
inet6 fe80::be97:e1ff:fe46:b6/64 scope link
valid_lft forever preferred_lft forever
8.7.2 RNIC interfaces on the servers
The IPU-POD
128
contains two IPU-POD
64
racks, and each of the IPU-POD
64
racks can contain up to four servers.
Each of these servers has an RNIC interface which needs to be configured.
You need to setup the RNIC interfaces as described in this section. If there are multiple servers on lrack1 (up to
four), the management server (lrack1 server 1) will control the remaining servers (lrack1 servers 2, 3 and 4) with
DHCP. lrack1 server 1 will be running the v-ipu server and also a DHCP server to control the IP addressing for
the lrack1 IPU-M2000s and servers (lrack1 servers 2, 3 and 4). Server 1 on lrack2 only runs a DHCP server for
the lrack2 IPU-M2000s and servers (lrack2 servers 2, 3 and 4).
7: enp161s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 0c:42:a1:1e:79:27 brd ff:ff:ff:ff:ff:ff
inet 10.5.7.150/16 brd 10.5.255.255 scope global enp161s0f1
valid_lft forever preferred_lft forever
inet6 fe80::e42:a1ff:fe1e:7927/64 scope link
valid_lft forever preferred_lft forever
This can be achieved by setting up the
/etc/netplan/01-netcfg.yaml
file as follows:
network:
version: 2
renderer: networkd
ethernets:
eno1:
addresses:
- 10.1.7.150/16
- 10.2.7.150/16
- 10.3.7.150/16
eno2:
dhcp4: yes
enp161s0f0:
dhcp4: yes
enp161s0f1:
addresses:
- 10.5.7.150/16
If there are more servers in the lrack1 rack (up to four), each will require an
/etc/netplan/01-netcfg.yaml
file
with the
enp161s0f1
interface edited accordingly. For example. server 2 in the rack would have
/etc/netplan/
01-netcfg.yaml
as follows:
network:
version: 2
renderer: networkd
(continues on next page)
Version: latest (2021-11-25)
102