IPU-POD128 build and test guide
Step 15: Test access to V-IPU agents
Use the V-IPU
test
command to test access to V-IPU agents for both lrack1 and lrack2. For example:
vipu-admin test cluster cl128
For more details on how to use this command refer to the V-IPU guides (
and
Step 16: Create partitions on lrack1
Use the
IPUOF_VIPU_API
environment variables to create user specific partitions on lrack1 with the new IP address
setup. These environment variables are:
•
IPUOF_VIPU_API_HOST
: The IP address of the server running the V-IPU controller. Required.
•
IPUOF_VIPU_API_PORT
: The port to connect to the V-IPU controller. Optional. The default is 8090.
•
IPUOF_VIPU_API_PARTITION_ID
: The name of the partition to use. Required.
•
IPUOF_VIPU_API_GCD_ID
: The ID of the GCD you want to use. Required for multi-GCD systems.
•
IPUOF_VIPU_API_TIMEOUT
: Set the time-out for client calls in seconds. Optional. Default 200.
More details about how to use these environment variables are given in the
Use
gc-info
on the management server to check that the IPUs in the partition are visible. More details about how
to use
gc-info
are given
Step 17: lrack1 RNIC addresses
Run
netplan apply
on all lrack1 servers so that they get new RNIC IP addresses. Then use
gc-info
to check that
they have access to the partition setup and that all lrack1 servers can reach all the IPU-M2000s they should have
access to.
Step 18: lrack2 RNIC addresses
Run
netplan apply
on all lrack2 servers so that they get new RNIC IP addresses. Then use
gc-info
to check that
they have access to the partition setup and that all lrack2 servers can reach all the IPU-M2000s they should have
access to.
Step 19: rsyslog.d
Edit
/home/ipuuser/.rack_tool/root-overlay/etc/rsyslog.d
to point to lrack1 IP (10.2.7.150).
Step 20: chrony.conf
Edit
/home/ipuuser/.rack_tool/root-overlay/etc/chrony/chrony.conf
to point to lrack1 IP (10.2.7.150).
Version: latest (2021-11-25)
96