HP OpenVMS Systems Documentation

HP OpenVMS System Management Utilities Reference Manual

Contents

Index

SHOW PORT

Displays information about selected SCA ports.

Format

SHOW PORT portname

Parameter

portname[,...]
Displays information about specific SCA ports, which you can use wildcards to specify. If no portname is specified, all ports on the node are displayed.

Qualifiers

/EXCLUDE=(portname[,...])
Excludes specific port names from the display. You cannot use wildcards to specify port names.
/OUTPUT=filespec
Creates the specified file and directs the output of the command to this file.

Example


SCACP> SHOW PORT

The command in this example produces output similar to the following:

  Port data for CLUIO2 at 06-DEC 15:01:25.82

    Port   Mgt       Msgs       Msgs     Dgrams     Dgrams
    Name   Prio      Sent       Rcvd       Sent       Rcvd
    ------ ---- ---------- ---------- ---------- ----------
    PEA0     0      64582      92237          0          0
    PIB0     0      95276     148937          0          0
    PIA0     0          0          0          0          0
    PIC0     0      62030     115148          0          0

SHOW TRACE

Displays PEDRIVER tracing data and parameters.

Note

This command is reserved for use by HP Services and OpenVMS Engineering only. Trace commands and output are subject to change from release to release.

Format

SHOW TRACE nodename

Parameter

nodename[,...]
Includes channels to specific nodes, which you can use wildcards to specify.
Each node name can be accompanied by optional qualifiers to specify local and remote device names. If no local or remote device name is specified, all channels associated with the specified node are included.
Use the SHOW CHANNEL command to display node names and local and remote device names.

Qualifiers

/CONTEXT
Displays only PEDRIVER trace settings and the event definition. If this qualifier is not included, trace event data is displayed.
/EVENT=(event1[,...])
Enables tracing on specific events, which you can use wildcards to specify. The default is all of the events that are in the trace buffer.
Use the SHOW TRACE/CONTEXT command to display event names.
/EXCLUDE[=(nodename[,...])
Excludes channels to specific nodes, which you can use wildcards to specify. Each node name can be accompanied by optional qualifiers to specify local and remote device names.
If no local or remote device name is specified, all channels associated with the specified node are included.
/GLOBAL (default when no nodes are specified)

/NOGLOBAL (default when nodes are specified)
Specifies whether global trace data is to be returned.
/INPUT=filename
Reads trace data from the specified file and displays it.
/LOCAL_DEVICE=(landevicename[,...])
Includes specific LAN devices that identify the local end of the channel. You can use wildcards to specify LAN devices.
Use the SHOW LAN_DEVICE command to display device names.
/OUTPUT=filename
Creates the specified file and directs output to it. If the filename extension is .DMP, the trace data is written to a dump file so that you can use the /INPUT qualifier to display it later.
/REMOTE_DEVICE=(landevicename[,...])
Includes specific LAN devices which identify the remote end of the channel, which you can use wildcards to specify.
Use the SHOW LAN_DEVICE command to display device names.
/SORT

/NOSORT (default)
Returns trace data sorted across channels, VCs, and the global trace buffer by sequence number. The default is trace data returned for channels and VCs one at a time, in order, for the channel or VC, but not across channels and VCs.

Examples

#1
SCACP> SHOW TRACE/CONTEXT

The command in this example displays trace settings and definition.

#2
SCACP> SHOW TRACE/OUTPUT=NODE10.TRC

The command in this example displays trace data and writes it to the specified file.

An example of the screen output of a SHOW TRACE/CONTEXT command follows.

SYS999 Trace Context 31-JAN-2001 10:59:28.25:

  Trace buffer size requested 2048 bytes
  Trace buffer total allocated 92160 bytes
  Trace buffer allocations 45 successful
  Trace buffer allocations 0 failed
  Current trace sequence number 812286047
  System cycle counter 404196 cps
  Stop tracing 0 events after stop event

  Trace  Stop  Default  Event
  -----  ----  -------  -----
  Active          Y     Error
  Active                Penalize_ch
  Active                Timer
  Active                Listen_timr
  Active                Handsh_timr
  Active                Size_probe
  Active                Delay_msmt
  Active                Verf_vack
  Active          Y     CC_event
  Active          Y     CC_state
  Active          Y     Path_state
  Active          Y     ECS_state
  Active                ACK_process
  Active          Y     Chan_update
  Active                Rcvd_CC_msg
  Active                Rcvd_TR_msg
  Active                Send_TR_msg
  Active                Xmt_failed
  Active          Y     VC_state
  Active                ACK_timeout
  Active          Y     TMO_listen
                  Y     No_path

    Channel Selection:
    Local Dev  Remote Dev  Remote Node Name    Selection
    ---------  ----------  ----------------    ---------
    All channels and VCs selected

SHOW VC

Displays PEDRIVER virtual circuit data. Each VC is an SCACP communications path between the local system and a remote system comprised of a set of channels.
Use the SHOW CHANNEL or SHOW VC commands to display node names, which are simply the names of the remote nodes.

Format

SHOW VC nodename

Parameter

nodename[,...]
Includes specific nodes, which you can use wildcards to specify.

Qualifiers

/ALL
Includes all VC data.
/COUNTERS
Includes VC counter data.
/EXCLUDE=(nodename[,...])
Excludes specific nodes, which you can use wildcards to specify.
Use the SHOW CHANNEL or SHOW VC commands to display VC names, which are simply the names of the remote nodes.
/INTERVAL
For the /COUNTERS display, displays the changes to counters since the last SHOW command.
/n
Displays the nth page. To select a particular page of a multipage display, specify the number of the page you want to display.
/OUTPUT=filespec
Creates the specified file and directs output to it.
/SDA
Includes VC data displayed in SDA format.
/SUMMARY
Includes VC summary data. This is the default if /ALL, /COUNTERS, and /SDA qualifiers are not specified.

Examples

#1
SCACP> SHOW VC/COUNTERS NODE10

The command in this example displays VC counters for all VCs whose name (that is, remote node name) starts with NODE10.

#2
SCACP> SHOW VC/COUNTERS/INTERVAL SCACP> SPAWN WAIT 0:0:10 SCACP> SHOW VC/COUNTERS/INTERVAL

The first command in this example displays VC counters since the last SHOW command. The SPAWN command tells the DCL WAIT command to insert a 10-second delay. The second SHOW VC command displays counters after the 10-second period.

SPAWN

Creates a subprocess of the current process. The SPAWN command copies the context of the subprocess from the current process.

Format

SPAWN [command-string]

Parameter

command-string
A string of commands to be executed in the context of the created subprocess. After the command string is executed, control returns to SCACP.

Qualifiers

None.

Example


SCACP> SPAWN SHOW TIME 24-AUG-2002 15:22:39 SCACP>

The command in this example creates a subprocess of the current process and displays the time.

START LAN_DEVICE

Directs PEDRIVER to start using the specified LAN device. The original (and still supported) way to start PEDRIVER on a LAN device is SYS$EXAMPLES:LAVC$START_BUS.

Format

START LAN_DEVICE landevicename

Parameter

landevicename[,...]
Includes specific LAN devices, which you can use wildcards to specify.
Use the /EXCLUDE qualifier to exclude LAN devices.
Use the SHOW LAN_DEVICE command to display device names.

Qualifiers

/EXCLUDE=(landevicename[,...])
Excludes specific LAN devices, which you can use wildcards to specify.
Use the SHOW LAN_DEVICE command to display device names.

Example


SCACP> START LAN_DEVICE EWA

This command starts PEDRIVER on the LAN device EWA.

START TRACE

Starts or resumes PEDRIVER tracing, optionally setting tracing options.

Note

This command is reserved for use by HP Services and OpenVMS Engineering only. Trace commands, their qualifiers, and output are subject to change from release to release.

Format

START TRACE nodename

Parameter

nodename[,...]
Includes information about communications with specific nodes, which you can use wildcards to specify. Each node name can be accompanied by optional qualifiers to specify local and remote device names.
If no local or remote device name is specified, the VC and all channels associated with the specified node are included.
Use the SHOW CHANNEL command to display node names and local and remote device names.

Qualifiers

/AFTER=n
After the trace stop condition has been satisfied, continues tracing for n events, and then stops. If you do not specify /AFTER, tracing does not continue after the trace stop event. n can be any value between 0 and FFFFFFF.
/DEFAULT
Sets the trace context back to the default settings, which are:
channelname=* /AFTER=0 /EVENT=default settings /STOP /SIZE=512
/EVENT=(event1[,...])
Enables tracing on specific events, which you can use wildcards to specify. The default is a subset of the events, which includes most errors and state changes.
Use the SHOW TRACE/CONTEXT command to display event names.
/EXCLUDE=(landevicename[,...])
Excludes specific LAN devices, which you can use wildcards to specify.
Use the SHOW LAN_DEVICE command to display device names.
/LOCAL_DEVICE=(landevicename[,...])
Includes specific LAN devices that identify the local end of the channel. You can use wildcards to specify LAN devices.
Use the SHOW LAN_DEVICE command to display device names.
/REMOTE_DEVICE=(landevicename[,...])
Includes specific LAN devices that identify the remote end of the channel. You can use wildcards to specify LAN devices.
Use the SHOW LAN_DEVICE command to display device names.
/STOP=(event[,...])
Stops tracing on specific events, which you can use wildcards to specify. The default is to stop no events.
Use the SHOW TRACE/CONTEXT command to display event names.
/SIZE=n
Specifies a trace buffer size of n bytes to be used by PEDRIVER for each trace buffer: one for global PEDRIVER use, one for each selected channel, and one for each selected VC. n can be any value between 0 and FFFFFFF.

Examples

#1
SCACP> START TRACE/EVENT=CC_STATE/SIZE=2000

The command in this example changes the Trace Channel Control layer state with a 2000-byte trace buffer.

#2
SCACP> START TRACE/EVENT=ALL NODE10,NODE20

The command in this example traces all events but only for the NODE10 and NODE20 channels.

STOP LAN_DEVICE

Directs PEDRIVER to stop using the specified LAN device. The original (and still supported) way to stop PEDRIVER on a LAN device is SYS$EXAMPLES:LAVC$STOP_BUS.

Caution
If you use either STOP LAN_DEVICE or SYS$EXAMPLES:LAVC$STOP_BUS to stop the only connection you have to a cluster, you will cause the system to CLUEXIT.

Format

STOP LAN_DEVICE landevicename

Parameter

landevicename[,...]
Includes specific LAN devices, which you can use wildcards to specify.
Use the /EXCLUDE qualifier to exclude LAN devices.
Use the SHOW LAN_DEVICE command to display device names.

Qualifier

/EXCLUDE=(landevicename[,...])
Excludes specific LAN devices, which you can use wildcards to specify.

Example


SCACP> STOP LAN_DEVICE EWA

This command stops PEDRIVER on the LAN device EWA.

STOP TRACE

Stops PEDRIVER tracing. You can read the trace data recorded so far with a SHOW TRACE command.
To revert trace behavior to initial settings, enter the command SET TRACE/DEFAULT.

Note

This command is reserved for use by HP Services and OpenVMS Engineering only. Trace commands and output are subject to change from release to release.

Format

STOP TRACE

Parameters

None.

Qualifiers

None.

Example


SCACP> STOP TRACE

The command in this example stops PEDRIVER tracing.

Chapter 19
Show Cluster Utility

19.1 SHOW CLUSTER Description

The OpenVMS Show Cluster utility (SHOW CLUSTER) monitors nodes in an OpenVMS Cluster and displays information about cluster-specific activity and performance. SHOW CLUSTER collects information from the System Communications Services (SCS) database, the connection management database, and the port database.

Table 19-1 shows the classes of data output by SHOW CLUSTER.

**Table 19-1 Classes of SHOW CLUSTER Information**
Class	Description
CIRCUITS	Describes information about the virtual circuits on a system, such as the local port name, the remote port type and number, the number of connections on the circuit, and the circuit state.
CLUSTER	Displays general OpenVMS Cluster information, such as the time the cluster was formed, the last time a system joined or left the cluster, and the cluster quorum.
CONNECTIONS	Describes connections established over a virtual circuit, such as the names of the local and remote processes, and the state of the connection.
COUNTERS	Displays accumulated statistics on connection traffic, such as the number of application datagrams, and the number of application messages that have been sent or received.
CREDITS	Displays the send and receive credits for each connection.
ERRORS	Displays a count of errors that have occurred on each port, along with information related to reinitializing those ports.
LOCAL_PORTS	Describes the local system interface to the OpenVMS Cluster, such as the name, number, and status of each port, and the number of entries in the queues associated with each port.
MEMBERS	Contains node-specific information, such as each node's identification numbers, quorum status, and connection status.
SYSTEMS	Lists information about all systems in the OpenVMS Cluster, such as the node identification numbers, node names, hardware types, and software versions.

Each class contains a number of fields of data. Table 19-2 through Table 19-10 list the fields of data in each class.

Table 19-2 CIRCUITS Class Fields

Field Name

Description

CABLE_STATUS

Status of the CI circuit paths A and B. Crossed cables are also noted. The field applies only to the CI. Possible displays are as follows:

-	Paths A and B are bad.
A-	Path A is good.
-B	Path B is good.
A-B	Paths A and B are good.
CROSSED	Cables are crossed.

CIR_STATE

State of the virtual circuit. Possible displays are as follows:

CLOSED	Circuit is closed.
OPEN	Circuit is open.
ST_REC	Circuit has a start received.
ST_SENT	Circuit has a start sent.
VC_FAIL	Virtual circuit failure is in progress.

LD_CLASS

The circuit's current capacity rating.

LPORT_NAME

Device name of the local port associated with the circuit (PAA0, PAB0, PEA0).

MGT_PRIORITY

Priority value assigned to the circuit by management action.

NUM_CONNECTIONS

Number of connections on the circuit between the local and remote systems.

PRIORITY

Circuit's current priority, which is the sum of the management priorities assigned to the circuit and the associated local port.

REM_STATE

State of the remote port. Possible displays are as follows:

DISAB	Remote port is disabled.
ENAB	Remote port is enabled.
M_DISAB	Remote port is in maintenance mode and is disabled.
M_ENAB	Remote port is in maintenance mode and is enabled.
M_UNINIT	Remote port is in maintenance mode and has not been initialized.
UNINIT	Remote port has not been initialized.

RP_FUNCTIONS

Function mask of the remote port.

RPORT_NUM

Port number of the remote port associated with the circuit. The field applies only to CI.

RP_OWNER

Port number of the remote port owner.

RP_REVISION

Hardware or microcode revision number of the remote port.

RP_TYPE

Type of remote port associated with the circuit. Examples of some possible types might include: CIMNA, KFMSA, SHAC, SII, BVPSSP (a BVP storage systems port), CI780, CI750, CIBCA-A and CIBCA-B, RF and TF devices (for example RF73 or TF85), HSC devices (for example, HSC65 or HSC90), Ethernet, PASSTH (port is in passthrough mode), and so on.

SCS_WAITERS

Number of connections waiting to send SCS control messages on the virtual circuit.

**Table 19-3 CLUSTER Class Fields**
Field Name	Description
CL_EXPECTED_VOTES	The number of votes the cluster has ever seen -- or could see, as determined by the connection manager. The value is based on the maximum value of CL_EXPECTED_VOTES, the value for EXPECTED_VOTES that is specified by each node, and the sum of the cluster votes (CL_VOTES). CL_QUORUM is derived from CL_EXPECTED_VOTES.
CL_MEMBERS	Number of processors participating in the cluster.
CL_QDVOTES	Number of votes contributed by the quorum disk.
CL_QUORUM	The number of votes that must be present for the cluster to function and permit user activity. CL_QUORUM is equal to (CL_EXPECTED_VOTES + 2) divided by 2.
CL_VOTES	Total number of votes contributed by all members of the cluster at any point in time.
FORMED	Time at which the cluster was formed, expressed as dd-mmm-yy hh:mm.
LAST_TRANSITION	Last time at which a system left or joined the cluster, expressed as dd-mmm-yy hh:mm.
MEMSEQ	Membership state sequence number, which changes whenever a node joins or leaves the cluster.
QD_NAME	Full device name of the quorum disk.
QF_VOTE	Indicates whether or not the quorum disk is contributing any votes towards the cluster quorum.

Table 19-4 CONNECTIONS Class Fields

Field Name

Description

CON_STATE

The state of the connection. Possible displays are as follows:

ACCP_SENT	Accept request has been sent.
CLOSED	Connection is closed.
CON_ACK	Connect request has been sent and acknowledged.
CON_REC	Connect request has been received.
CON_SENT	Connect request has been sent.
DISC_ACK	Disconnect request is acknowledged.
DISC_MTCH	Disconnect request is matched.
DISC_REC	Disconnect request has been received.
DISC_SENT	Disconnect request has been sent.
LISTEN	Connection is in the listen state.
OPEN	Connection is open.
REJ_SENT	Reject has been sent.
VC_FAIL	Virtual circuit has failed.

LOC_CONID

Identification number of the local side of the connection.

LOC_PROC_NAME

Name of the local process associated with the connection.

REM_CONID

Identification number of the remote side of the connection. This information does not apply for connections in the listen state.

REM_PROC_NAME

Name of the remote process associated with the connection. This information does not apply for connections in the listen state.

SCS_STATE

SCS send blocked state. If the connection is waiting to send an SCS control block message, the SCS send blocked state indicates what kind of message it is waiting to send. Possible displays are as follows:

ACCP_PEND	Waiting to send an accept request.
CLEAR	Not blocked.
CON_PEND	Waiting to send a connection request.
CR_PEND	Waiting to send credit.
DCR_PEND	Waiting to send credit in preparation for a disconnect.
DISC_PEND	Waiting to send a disconnect request.
REJ_PEND	Waiting to send a reject request.

Contents

Index