
Find the physical ID for node 12
smw#
xtnid2str 12
node id 0xc = 'r0s0c1n4'
Find the physical ID for nodes 0, 1, 2, and 3
smw#
xtnid2str 0 1 2 3
node id 0x0 = 'r0s0c0n0'
node id 0x1 = 'r0s0c0n1'
node id 0x2 = 'r0s0c0n2'
node id 0x3 = 'r0s0c0n3'
Find Node Information Using the
nid2nic
Command
The
nid2nic
command prints the
nid
-to-
nic
address mappings,
nic
-to-
nid
address mappings, and a specific
physical_location
-to-
nic
address and
nid
mappings.
For information about using the
nid2nic
command, see the
nid2nic(8)
man page.
3.4.17 Request and Display System Routing
Use the HSS
rtr
command to request routing for the HSN, to verify current route configuration, or to display
route information between nodes. Upon startup,
rtr
determines whether it is making a routing request or an
information request.
For more information, see the
rtr(8)
man page.
Display routing information
The
--system-map
option to
rtr
writes the current routing information to
stdout
or to a
specified file. This command can also be helpful for translating node IDs (NIDs) to physical ID
names.
crayadm@smw>
rtr --system-map
Route the entire system
The
rtr -R | --route-system
command sends a request to perform system routing. If no
components are specified, the entire configuration is routed as a single routing domain based on
the configuration information provided by the state manager. If a component list (
idlist
) is
provided, routing is limited to the listed components. The state manager configuration further
limits the routing domain to omit disabled blades, nodes, and links and empty blade slots.
crayadm@smw>
rtr --route-system
CAUTION: The
rtr -R
command should not be executed if the system nodes have already been booted
and are using the Aries network.
System Management
S3016
37