oview man page on IRIX

Man page or keyword search:  
man Server   31559 pages
apropos Keyword Search (all sections)
Output format
IRIX logo
[printable version]



NAME
     oview - visualize the performance of an Origin server

SYNOPSIS
     oview [-Vw] [pmview+ options | oview4sn0 options]

DESCRIPTION
     oview displays the topology of an Origin server with performance
     information about CPUs, nodes and routers. The display is updated with
     new values retrieved from the target host or archive every interval
     seconds (default is 2 seconds).

     oview behaves differently and produces different views for SGI 3000 and
     SGI 2000 systems. For SGI 3000 systems oview constructs the view
     configuration and launches pmview+. In the SGI 2000 case oview parses the
     command line and launches oview4sn0.

     The rest of this document discusses the the first case, i.e displaying
     information about SGI 3000 systems. See oview4sn0(1) for details about
     displaying data from SGI 2000 systems.

     oview generates a pmview+(1) configuration file, and passes most command
     line options to pmview+(1).  Therefore, the command line options -A, -a,
     -C, -h, -n, -O, -p, -S, -t, -T, -Z and -z, the X11-args and user
     interface are described in the pmview+(1) man page.

     oview can display the topology of SGI 3000 systems with up to eight
     routers, which covers systems with 1 to 128 CPUs. Configurations with
     metarouters and repeater routers are currently not supported.

COMMAND LINE OPTIONS
     There are two oview specific options.  If -V is present, the
     configuration file is printed on the standard output and pmview+ is not
     executed.	If -w is present and an SGI 3000 system is being monitored,
     then the ``wait'' time is included for each processor (the default is to
     display only the ``user'' and ``system'' components of the CPU time).
     All other options are passed either to pmview+(1) or to oview4sn0(1).

VISUALIZATION
     Routers are represented by oblong boxes with a colored indicator of the
     router's utilization on the top of the box. The color of the indicator
     has the following meaning:

     cyan insignificant router utilization
	  0 <= utilization < 1%

     light cyan
	  light router utilization
	  1% <= utilization < 5%

     yellow
	  medium router utilization
	  5% <= utilization < 20%

     orange
	  high router utilization
	  20% <= utilization < 40%

									Page 1
									     1

OVIEW(1)							      OVIEW(1)

     red  saturated router utilization
	  utilization >= 40%

     Nodes are represented by square boxes and CPUs are represented by a
     stacks of blue, red and cyan colored blocks to show the user, system and
     wait (if -w specified) utilization of each CPU, respectively. The CPU
     stacks are grouped to appear on the top of the node they are physically
     connected to.

     Router ports are represented by cylindrical stacks, connected to the
     sides of a router box. The topology of the connection depends on the
     configuration of a machine. The router port stack shows the receive
     bypass and the receive queued utilization on the per-port basis as violet
     and yellow bands, respectively, which grow away from the router box as
     utilization increase.  A grey cylinder adjacent to the colored bands, if
     visible, represents the unused bandwidth capacity.

     Unanimated ``pipes'' are used to join the endpoints for each router
     connection.

     To avoid cluttering the scene, especially for large configuration, CPUs
     and nodes may be omitted from the view. The -l option can be used to
     select the ``level of details'' as follows:

	 0    Show only routers.

	 1    Show routers and nodes.

	 2    Show all the routers, nodes and CPUs. This is the default.

FILES
     $PCP_VAR_DIR/config/pmlogger/config.oview
	       A pmlogger(1) configuration file for oview metrics.

PCP 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 ALSO
     oview4sn0(1), pmcd(1), pmchart(1), pmlogger(1), pmtime(1) and pmview+(1).

CAVEATS
     The algorithm for 3-D layout of SGI 3000 system components by oview is
     complex, and relies on heuristics.	 If you encounter a configuration that
     is not displayed as expected, please send e-mail to pcp-info@sgi.com
     including a description of the problem, and attaching the output from

									Page 2

OVIEW(1)							      OVIEW(1)

	       pminfo -f hinv

     There are may be problems when oview cannot guess the information about
     routers connectivity in the non-standard SGI 3000 configuration. In this
     case router ports would be displayed but no attempt is made to draw the
     links between them.

									Page 3

[top]

List of man pages available for IRIX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net