Utility programs are provided with Vantage to enable administrators or operators to trouble shoot problems or to gather statistical information.
The diag1 Program for an example and explanation of information contained in diag1 output.
Refer to The listawide Program for an explanation of what information is contained in listawide.
Refer to The listalog Program to learn about using the listalog program.
Refer to The whereisrc Program to locate on which node resources are connected.
The script diag1 is provided as a tool that can be used to show running Vantage processes. The program can be run from a terminal window by typing diag1.
A group or "stack" of programs enable Vantage to monitor resources. This stack consists of one Broker, one NED, and two RPC processes. The for each resource there is a Monitor, and up to three Multiplex processes for each resource
Each section of the diag1 output is described below. The output has been abbreviated and thus does not show process id numbers etc.
The resource name associated with each process is shown as part of the process information. The resource "a" was used for this example.
NED SECTION
Contains process information about the Non-Event Display. The NED process should be running if the broker is active. Process information is displayed as follows.
xned -name NED -xrm '*workspaceList: all ' -geometry -225+5
MULTIPLEX SECTION
This section shows the multiplexers. Three multiplex processes should be running for each resource being monitored. Two of the processes handle I/O and the other runs an hpterm.
/usr/vue/bin/hpterm -name V_multiplex -n a -xrm '*workspaceList
/opt/vantage/bin/V_multiplex -m a /opt/vantage/bin/viper
/opt/vantage/bin/V_multiplex -m a /opt/vantage/bin/viper
SHARED MULTIPLEX SECTION
Contains information if any shared copies of consoles have been started. This information will appear as follows:
/usr/vue/bin/hpterm -name V_connect -n a -title "a Shared
Console"
/opt/vantage/bin/V_connect /opt/vantage/bin/viper a
VANTAGE DIALOG SECTION
Shows Vantage dialogs that pertain to the monitoring of resources. A single xbroker and an xmonitor should be running for each resource being monitored.
xbroker -name XBroker
xmonitor a Admin^J
VANTAGE ADMIN SECTION
This section shows the Resource, Group and Event definition dialog programs.
xsystems -display predator:0.0
xaliass -display predator:0.0
xevents -display predator:0.0
VANTAGE RPC SECTION
The RPC section shows the RPC programs. The vanrpc_serv process is started by the Launch/Status Manager and should always be running. The vanrpc_disp process dispatches Message event responses to the Message Manager and should be running if the xbroker is running.
vanrpc_serv
vanrpc_disp
VANTAGE POLLING SECTION
This section will contain information only if the RPC link to a remote Vantage node is down. If the link is down the poll_vannode process is started to periodically attempt to re-establish the link. Once the link is re-established the process stops.
poll_vannode predator 10
LOCK INFO
This section shows process lock files. The Broker_Lock file should exist if the Broker is running. If the Broker_Lock file exists and the Broker is not running, the Broker will not start until this file is removed. The BrokerReady file exists for a very brief time and should never appear in the diag1 output. A Monitor_Lock file should exist for each resource actively being monitored. A RPC_Lock file exists if the RPC link to a remote Vantage host to which transfer of control has been established is down. Once the link is re-established the lock file is removed.
-rw-r----- 1 vanmgr v_mgr 0 Jan 25 08:10 Broker_Lock
BrokerReady not found
-rw-r----- 1 vanmgr v_mgr 0 Jan 25 08:10 ./a/Monitor_Lock
-rw-r----- 1 vanmgr v_mgr 0 Jan 25 08:06
RPC_Lock.predator
See also The listawide Program , The listalog Program , Trouble Shooting Vantage and Recovering Vantage Software
The listawide program reads and creates a of the broker's log files. These log files contain event detection and response execution information.
The listawide program can be used to determine if events are being detected and if event responses are being executed.
Listawide can be passed a log number as an argument. Broker log files can be found in the /opt/vantage/broker directory. To report on the contents of the log file log0000000505 type listawide 505. To report on the current log simply type listawide. The log files can be fairly large so it is recommended that the output be piped to more or tail, for example, listawide | tail will list the last few lines of the log file.
Output from this program can be directed to a file or to other programs such as grep, more, lp, tail, etc., by typing listawide | [program_name] or listawide > [file_name].
The listawide output is formatted so that it can be imported into a spread sheet, if desired. Each field contains specific information about events and event responses. Information reported is:
Date & Time
This is the date and time that the event was detected or that the event response was executed.
Resource
The resource upon which the event was detected.
Seq and Bseq
Internal sequence numbers.
ExeFlag
A 0 in this field means that the event will always be executed. A -1 means that the event was throttled.
Action
Action is the primitive action number of the event response.
1-Message event, 2-Voice, 3-Command event, 4-Command with File, 5-Report event, 6-Report File, 7-Message with Reply, 8-API Exec event, 1001-NED no Logging, 1002-NED with Logging, 1004-Transfer Control, 1005-Default Display Change, 1008-Multiple Line Message event, 1009-Multiple Line Message with Reply
Event
Event is the event that was detected.
Context
Is the line of output in which the event was detected.
See also The listalog Program , The diag1 Program , Trouble Shooting Vantage and Recovering Vantage Software
The listalog program reports from the same log file as listawide but formats the information in a different way. The following figure shows an individual record from the program.
origin host predator
destination host predator
broker sequence 512001
system_name loopback
monitor's ev_seq 800
ev_time Mon Jan 24 15:24:18 1994
start_pos 0
event_string Connected - loopback
event_type @
file_name FILENAME
execution_priority 0
throttle_cnt 0
throttle_dur 0
throttle_ord 0
initial_time_stamp Mon Jul 12 14:42:59 1993
modified_time_stamp Thu Nov 11 16:20:52 1993
primitive_action 3
command_line
alias_name loopback
Context is - Connected - loopback
See also Trouble Shooting Vantage and Recovering Vantage Software
This program can be used to determine to which Vantage node resources are connected as well as connectivity information for resources.
The whereisrc program can be used to search Vantage nodes to obtain the node name, connectivity information and machine type of Vantage-managed resources. The program will search the local node, the vanhosts.bin file or a file of your choice for resource information.
The program is run from a terminal window as vanmgr. The whereisrc program accepts up to three arguments:
whereisrc
Executing whereisrc with no arguments displays information for all resources configured on the node upon which the program is executed (the current node).
whereisrc [resource_name]
Executing with a resource name as the first argument displays information for resource_name on the current node and nodes contained in the vanhosts.bin file.
whereisrc -all
Executing with the -all argument will display all resources on the current node and on the nodes in vanhosts.bin.
whereisrc [resource_name] -n
Will display information for resource_name on the current node only.
whereisrc [resource_name] -f
Will display information for resource_name on the current node and on nodes in the vanhosts.bin file.
whereisrc [resource_name] -n [node_name]
Executing whereisrc with these arguments will display information for resource_name on node_name.
whereisrc [resource_name] -f [file_name]
Will display information for resource_name on nodes contained in /opt/vantage/data/[file_name].
whereisrc -all -n [node_name]
Displays information for all resources on node_name.
whereisrc -all -f [file_name]
Will display information for all resources on nodes contained in /opt/vantage/data/[file_name].
See also, Trouble Shooting Vantage and Recovering Vantage Software
