IPU-POD128 build and test guide
The IPU-M2000 Gateway upgrade itself is destructive in the sense that it will overwrite all executables and cor-
responding file systems for the standby image. The content of the overlay config files is maintained and stored
persistently on the management server. A single central management server can function as a central repository
for a site-wide setup of all IPU-M2000s.
5.4 Rack tool
rack_tool
is a utility that is supplied with the IPU-M2000 release bundle when installed onto a management
server. It is always found under the account that is performing IPU resource management (the default is the
ipuuser
account), as
~/IPU-M_releases/IPU-M_<release-version>/rack_tool.py
.
Information about
rack_tool
and how to use it can be found on the
A suggested naming scheme for IPU-M2000s is:
lr1_ipum<n> (logical rack 1, IPU-M2000 #n)
.
rack_tool
is used for the following:
1. Querying the version of all IPU-M2000s
2. Connectivity test performed on all IPU-M2000 RDMA data-plane ports, GW and BMC management-plane
ports across all IPU-M2000s that are listed in
rack_tool
’s default config file
3. Restarting IPU-M2000s GW and BMC in different ways (power cycling or OS reboot)
4. Control power on/off for the GW part of the IPU-M2000
5. Running commands on several IPU-M2000s for troubleshooting
6. Updating the “root overlay” files onto all IPU-M2000s if NTP or syslog server has changed
7. Running hardware and connectivity tests (see
for the built-in
test capabilities)
Note that supported options will evolve over time so please check the latest
documentation before
using it.
Version: latest (2021-11-25)
79