NAMEoview_layout - determine CrayLink interconnection topology of Origin
systems
SYNOPSIS
$PCP_BINADM_DIR/oview_layout [-a archive] [-h host] [-n pmnsfile]
DESCRIPTIONoview_layout attempts to determine the interconnection topology of Origin
2000 and Origin 200 systems. It is not normally run by users, but rather
invoked automatically from the Origin systems visualization program,
oview(1).
oview_layout contacts the PCP collection daemon pmcd(1) on the target
host (if -h is given) or accesses the PCP archive (if -a is given) to
obtain the Craylink interconnection inventory and uses this to resolve
the logical topology of the system.
oview_layout can currently resolve the topology of Origin systems with an
unlimited number of CrayLink routers with logical topologies represented
by an edge, star, plane or series of cubes and/or planes.
Planes are chosen from different modules linked to each other by having
their routers connected on the same slots. That is, module A is connected
to module B with routers on slot 1 connected together and routers on slot
2 connected together. Cubes are formed by connected planes. An edge and a
star are degenerate cases handled separately.
If oview_layout successfully resolves the topology of the target host or
archive, it prints it in the following format (identical to the input
format expected by oview(1)).
router:M.S X Y Z
link rport:M.S.P router:M.S
...
link rport:M.S.P node:M.S [cpu:M.S.N [cpu:M.S.N]]
...
Where M and S denote an Origin 2000 module and slot respectively (a
``slot'' may be either a router slot or a node slot, depending on the
context), P denotes a CrayLink router port number, N denotes a CPU number
(either a or b), and X, Y and Z are coordinates in a Cartesian space.
The keywords router, link, rport, node and cpu are literals.
In configurations with no router, the router and router port numbers are
negative to indicate their placeholder status.
CAVEATS
For systems which use metarouters (systems with 65 or more processors),
the metarouters are currently ignored, however, the other routers and
links for the system will be shown as normal, i.e. the system layout will
be a series of cubes but with no links between the cubes (these are the
meta-router links).
Page 1
1
OVIEW_LAYOUT(1)OVIEW_LAYOUT(1)
If the CrayLink interconnections have not been properly configured, then
oview_layout may become confused.
FILES
$PCP_VAR_DIR/pmns/*
default local PMNS specification files
$PCP_VAR_DIR/config/pmlogger/config.oview_layout
pmlogger(1) configuration file suitable for use with
oview_layoutPCP ENVIRONMENT
Environment variables with the prefix PCP_ are used to parameterize the
file and directory names used by PCP. On each installation, the file
/etc/pcp.conf contains the local values for these variables. The
$PCP_CONF variable may be used to specify an alternative configuration
file, as described in pcp.conf(4).
SEE ALSOdkvis(1), mpvis(1), nodevis(1), oview(1), pcp.conf(1), pcp.env(1),
PCPIntro(1), pmafm(1), pmcd(1), pmie(1), pminfo(1), pmlogger(1),
pmtime(1), pmval(1), pmview(1), routervis(1), X(1), environ(5) and
pmlaunch(5).
Page 2
