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 cause the system to CLUEXIT. Even when you have have another connection using a different cluster port, stopping all LAN devices results in excessive activity. When PEdriver loses access to all of its LAN devices, it makes an effort to restore cluster communications by completely re-initializing itself. After the last LAN device is stopped, the reinitilization produces an error message similar to the following: SCACP> STOP LAN * ;%PEA0, Port is Reinitializing ( 49 Retries Left). Check the Error Log. After the displayed retry count is exceeded, PEdriver permanently goes offline. To disable cluster use of all but 1 LAN device, enter the following command: SCACP> STOP LAN * /EXCLUDE=landevicename All LAN devices except the excluded device are stopped, and PEdriver does not need to be reset.

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.

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.

Format

STOP TRACE

Parameters

None.

Qualifiers

None.

Example

SCACP> STOP TRACE
      

The command in this example stops PEDRIVER tracing.

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 22-1 shows the classes of data output by SHOW CLUSTER.

Table 22-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 22-2 through Table 22-10 list the fields of data in each class.

Table 22-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 22-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 22-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.

Table 22-5 COUNTERS Class Fields

Field Name	Description
BDT_WAITS	Number of times this connection had to wait for a buffer descriptor.
BLKS_REQ	Number of block-request data commands initiated to block transfer data from the remote system to the local system.
BLKS_SENT	Number of block-send data commands initiated to block-transfer data from the local system to the remote system.
CR_WAITS	Number of times this connection had to wait for send credit.
DGS_DSCRD	Number of application datagrams discarded by the port driver.
DGS_RCVD	Number of application datagrams received by the local system over the connection from the remote system and given to SYSAP.
DGS_SENT	Number of application datagrams sent over the connection.
KB_MAPPED	Number of kilobytes of data mapped for block transfer.
KB_RCVD	Number of kilobytes of data received by the local system from the remote system through request-data commands.
KB_SENT	Number of kilobytes of data sent from the local system to the remote system through send-data commands.
MSGS_RCVD	Number of application datagram messages received over the connection.
MSGS_SENT	Number of application datagram messages sent over the connection.

Table 22-6 CREDITS Class Fields

Field Name	Description
INIT_REC	Initial receive credit extended to the remote system when the connection was made.
MIN_REC	Minimum receive credit (minimum send credit required by the remote system).
MIN_SEND	Minimum send credit.
PEND_REC	Receive credit not yet extended to the remote system.
RECEIVE	Receive credit (send credit held by the remote system).
SEND	Current send credit.

Table 22-7 ERRORS Class Fields

Field Name	Description
ERT_COUNT	Number of port reinitialization attempts remaining.
ERT_MAX	Total number of times a recovery from fatal port errors can be attempted by shutting down all virtual circuits and connections and reinitializing the port.
NUM_ERRORS	Number of errors that have been logged on the port since the system was booted. This number includes errors encountered in reinitialization attempts as well as recoverable errors, such as virtual circuit failure. This is the same error count as that displayed by the DCL command SHOW DEVICE.

Table 22-8 LOCAL_PORTS Class Fields

Field Name	Description
BUFF_DESCR	Number of buffer descriptors in use.
CMDS_QUEUED	Total number of messages, datagrams, and port commands queued for transmission at all priorities by the port.
COUNTER_OWNER	Name of the process currently using the port traffic counters.
DGI_MAP	A 16-bit bit map displayed as four hexadecimal digits. Each bit in the map represents a port in the cluster from which datagram reception has been disabled.
DG_OVRHD_SIZE	Number of bytes of port header, SCS header, and DECnet header in a datagram.
DGS_FREE	Number of free datagram buffers currently queued for receive commands.
FORM_CIRCS	Number of formative circuits (circuits in the process of opening) from the port.
FREE_BUFF	Number of CI buffer descriptors free for use.
LB_STATUS	Loopback status of each cable from the port to the star coupler. The field applies only to CI. Possible displays are as follows: A-B Loopback tests pass on paths A and B. A-# Loopback tests pass on path A. #-B Loopback tests pass on path B. #-# Loopback tests failed on paths A and B. N/A Loopback tests are not being done.
LOG_MAP	A 16-bit bit map displayed as four hexadecimal digits. Each bit in the map represents a port in the cluster for which an error was logged. Errors are logged when data provided by the configuration database on the local system conflicts with data provided by the remote system. When a conflict is discovered and an error is logged, virtual circuits to the remote system can no longer be established.
LP_LD_CLASS	Hard-coded capacity value of the port, based on the megabits/second rate of the interconnect of the port.
LP_PRIORITY	Management priority assigned to the port.
LP_STATUS	Status of the local port. The port is either on line or off line.
LP_TYPE	Device type of the port (CI780, CI750).
MAX_PORT	Largest port number to which a virtual circuit open is attempted.
MSGS_FREE	Number of free message buffers currently queued for receives commands.
MSG_HDR_SIZE	Number of bytes of port header and SCS header in a message.
NAME	Device name of the local port.
OPEN_CIRCS	Number of virtual circuits open from the port.
POOL_WAITERS	Number of processes waiting for nonpaged pool resources for message buffers.
PORT_NUM	Port number assigned to the port.
PRT_MAP	A 16-bit bit map displayed as three hexadecimal digits. Each bit in the map represents a port in the cluster that has been recognized by the host system.
RSPS_QUEUED	Total number of responses of all kinds received from the port but not yet processed.

Table 22-9 MEMBERS Class Fields

Field Name	Description
ACK_LM	Maximum number of OpenVMS Cluster messages the remote system can receive before sending an acknowledgment.
ACKR_SQ	Sequence number of the last acknowledgment received over the cluster connection.
CNX_STATE	State of the cluster connection. Possible displays are as follows: ACCEPT Initial connection is accepted. CLOSED Connection is closed. CONNECT Initial connection is being accepted. DEAD No connection is possible. DISCONNECT Disconnection is in progress. NEW No attempt to make a connection has been made yet. OPEN Connection is open. REACCEPT Connection is accepting the reconnect request. RECONNECT Connection is attempting to reconnect. WAIT Timeout is in progress.
CSID	Cluster system identification number. This number is unique over the life of the cluster. Unlike SYS_ID, this identification number may change when the system reboots.
DIR_WT	Lock manager distributed directory weight.
EXPECTED_VOTES	Maximum number of votes that an individual node can encounter. Used as an initial estimate for computing CL_EXPECTED_VOTES. The cluster manager sets this number using the EXPECTED_VOTES system parameter. It is possible for this field to display a number smaller than the EXPECTED_VOTES parameter setting if the REMOVE_NODE option was used to shut down a cluster member or the SET CLUSTER/EXPECTED_VOTES DCL command was used since this node was last rebooted. The dynamic value for EXPECTED_VOTES used clusterwide is the CL_EXPECTED_VOTES field, which is described in Table 22-3.
PROTOCOL	Protocol version number and ECO level of the connection management software.
QDVOTES	Number of votes the remote system recommends be contributed by the quorum disk. Normally, the cluster manager sets this number using the system parameter QDSKVOTES.
QF_ACTIVE	Indicates whether the remote system's quorum file is accessible.
QF_SAME	Indicates whether the local and remote systems agree about which disk is the quorum disk.
QF_WATCHER	Remote system has an active connection to the quorum disk and can verify its connection for members unable to access the disk directly.
QUORUM	Derived from EXPECTED_VOTES and calculated by the connection manager. It represents an initial value for the minimum number of votes that must be present for this node to function. The dynamic QUORUM value is the CL_QUORUM field, which is described in the CLUSTER class category in Table 22-3.
RCVD_SQ	Sequence number of the last message received over the OpenVMS Cluster connection.
RECNXINTERVAL	Displays the time (in seconds) that the connection manager will wait before timing out the corresponding connection. It is the maximum of the value contained in the system parameter RECNXINTERVAL on the local node and the amount of time it would take for the connection manager on the remote node to discover that the connection is broken.
SEND_SQ	Sequence number of the next message to be sent over the OpenVMS Cluster connection.
STATUS	Status of the node in the cluster. Possible displays are as follows: blank System is not being considered as a cluster member. BRK_MEM System is a member of the cluster, but the connection manager has lost communication with it. BRK_NEW System has just booted, but has not yet joined the cluster and the connection manager has lost communication with it. BRK_NON Connection manager has lost communication with the system and the system is no longer a member of the cluster. BRK_REM Connection manager has lost communication with the system, and the system has been removed from the cluster. MEMBER System is participating in the cluster. NEW System has just booted, but has not yet joined the cluster. If this system would normally be a member of the cluster and is displaying NEW in this field, you can expect that the display will eventually change to MEMBER. NON System is not a member of the cluster. REMOVED System has been removed from the cluster.
SW_VERS	Indicator of the software version running on the node.
TRANSITION_TIME	Time of the system's last change in membership status. (See the STATUS field.)
UNACKED	Number of unacknowledged OpenVMS Cluster messages received by the remote system.
VOTES	Number of votes the remote node contributes toward quorum. Normally, the cluster manager sets this number with the system parameter VOTES.
WARMCDRPS	Number of CDRPs on the CDRP free queue.

Table 22-10 SYSTEMS Class Fields

Field Name	Description
DG_SIZE	Maximum number of bytes of application data in datagrams sent over the circuit.
HW_TYPE	System hardware type (for example, VAXstation 3100 or HS70). (Enclose the system type between double quotation marks.)
HW_VERS	Hardware configuration and revision levels of the remote system.
INCARNATION	Unique 16-digit hexadecimal number established when the system is booted.
INCN_TIME	Incarnation number expressed as a time (dd-mmm-yy hh:mm).
MSG_SIZE	Maximum number of bytes of application data in messages sent over the circuit.
NODE	Node name of the remote system. Normally, the cluster manager sets the node name using the system parameter SCSNODE. The node name should be the same as the DECnet node name. (Note that SCSNODE cannot be more than six characters.)
NUM_CIRCUITS	Number of virtual circuits between the local system and remote systems.
SOFTWARE	Name and version of the operating system currently running on the remote system.
SYS_ID	Identification number of the remote system. Normally, the cluster manager sets this number using the system parameters SCSSYSTEMID and SCSSYSTEMIDH. This number should be the same as the DECnet node number.