You can ADD and REMOVE classes of information from the SHOW CLUSTER display. Each class consists of one or more fields. For example, the SYSTEMS class displays fields that list information about all systems in the cluster, such as their identification numbers, node names, hardware types, and software versions.
1 – CIRCUITS
The CIRCUITS class contains information about the virtual circuits on a system. This class includes fields such as local port name, remote port type and number, number of connections on the circuit, circuit state, etc.
1.1 – 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:
- 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.
1.2 – CIR_STATE
State of the virtual circuit. Possible displays are:
CLOSED Circuit is closed.
OPEN Circuit is open.
ST_REC Circuit has a start received.
ST_SENT Circuit has a start sent.
1.3 – LD_CLASS
The circuit's current capacity rating.
1.4 – LPORT_NAME
Device name of the local port associated with the circuit (PAA0, PAB0, PEA0).
1.5 – MGT_PRIORITY
Priority value assigned to the circuit by management action.
1.6 – NUM_CONNECTIONS
Number of connections on the circuit between the local and remote systems.
1.7 – PRIORITY
Circuit's current priority, which is the sum of the management priorities assigned to the circuit and the associated local port.
1.8 – REM_STATE
State of the remote port. Possible displays are:
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.
1.9 – RP_FUNCTIONS
Function mask of the remote port.
1.10 – RPORT_NUM
Port number of the remote port associated with the circuit. The field applies only to CI.
1.11 – RP_OWNER
Port number of the remote port owner.
1.12 – RP_REVISION
Hardware or microcode revision number of the remote port.
1.13 – 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.
1.14 – SCS_WAITERS
Number of connections waiting to send SCS control messages on the virtual circuit.
2 – CLUSTER
The CLUSTER class contains general information about the cluster. This class includes information such as the time the cluster was formed, the time of the last transition, and the cluster quorum.
2.1 – 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.
2.2 – CL_MEMBERS
Number of processors participating in the cluster.
2.3 – CL_QDVOTES
Number of votes contributed by the quorum disk.
2.4 – 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.
2.5 – CL_VOTES
Total number of votes contributed by all members of the cluster at any point in time.
2.6 – FORMED
Time at which the cluster was formed, expressed as dd-mmm-yy hh:mm.
2.7 – LAST_TRANSITION
Last time at which a system left or joined the cluster, expressed as dd-mmm-yy hh:mm.
2.8 – MEMSEQ
Membership state sequence number, which changes whenever a node joins or leaves the cluster.
2.9 – QD_NAME
Full device name of the quorum disk.
2.10 – QF_VOTE
Indicates whether or not the quorum disk is contributing any votes towards the cluster quorum.
3 – CONNECTIONS
The CONNECTIONS class contains information about the connection established over a virtual circuit. This class includes fields such as the names and ID numbers of the local and remote processes, and the state of the connection.
3.1 – CON_STATE
The state of the connection. Possible displays are:
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.
3.2 – LOC_CONID
Identification number of the local side of the connection.
3.3 – LOC_PROC_NAMR
Name of the local process associated with the connection.
3.4 – REM_CONID
Identification number of the remote side of the connection. This information does not apply for connections in the listen state.
3.5 – REM_PROC_NAME
Name of the remote process associated with the connection. This information does not apply for connections in the listen state.
3.6 – 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:
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.
4 – COUNTERS
The COUNTERS class displays the counts for the total accumulated traffic over a connection for the life of the connection. This class includes fields such as the number of application datagrams sent and received, the number of application messages sent and received, and the number of kilobytes sent and requested in block transfer mode.
4.1 – BDT_WAITS
Number of times this connection had to wait for a buffer descriptor.
4.2 – BLKS_REQ
Number of block-request data commands initiated to block transfer data from the remote system to the local system.
4.3 – BLKS_SENT
Number of block-send data commands initiated to block-transfer data from the local system to the remote system.
4.4 – CR_WAITS
Number of times this connection had to wait for send credit.
4.5 – DGS_DSCRD
Number of application datagrams discarded by the port driver.
4.6 – DGS_RCVD
Number of application datagrams received by the local system over the connection from the remote system and given to SYSAP.
4.7 – DGS_SENT
Number of application datagrams sent over the connection.
4.8 – KB_MAPPED
Number of kilobytes of data mapped for block transfer.
4.9 – KB_RCVD
Number of kilobytes of data received by the local system from the remote system through request-data commands.
4.10 – KB_SENT
Number of kilobytes of data sent from the local system to the remote system through send-data commands.
4.11 – MSGS_RCVD
Number of application datagram messages received over the connection.
4.12 – MSGS_SENT
Number of application datagram messages sent over the connection.
5 – CREDITS
The CREDITS class displays the send and receive credit counts for each connection. This class includes fields that indicate the minimum, current, and initial credit counts.
5.1 – INIT_REC
Initial receive credit extended to the remote system when the connection was made.
5.2 – MIN_REC
Minimum receive credit (minimum send credit required by the remote system).
5.3 – MIN_SEND
Minimum send credit.
5.4 – PEND_REC
Receive credit not yet extended to the remote system.
5.5 – RECEIVE
Receive credit (send credit held by the remote system).
5.6 – SEND
Current send credit.
6 – ERRORS
The ERRORS class displays a running count of the errors on each port along with the current number of reinitialization attempts remaining and the maximum number of times reinitialization can be attempted.
6.1 – ERT_COUNT
Number of port reinitialization attempts remaining.
6.2 – 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.
6.3 – 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.
7 – LOCAL_PORTS
The LOCAL_PORTS class displays information about the port interface on the local system. This class includes fields such as port name, port number, port status, and number of entries in the queues for each port.
7.1 – BUFF_DESCR
Number of buffer descriptors in use.
7.2 – CMDS_QUEUED
Total number of messages, datagrams, and port commands queued for transmission at all priorities by the port.
7.3 – COUNTER_OWNER
Name of the process currently using the port traffic counters.
7.4 – 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.
7.5 – DG_OVRHD_SIZE
Number of bytes of port header, SCS header, and DECnet header in a datagram.
7.6 – DGS_FREE
Number of free datagram buffers currently queued for receive commands.
7.7 – FORM_CIRCS
Number of formative circuits (circuits in the process of opening) from the port.
7.8 – FREE_BUFF
Number of CI buffer descriptors free for use.
7.9 – LB_STATUS
Loopback status of each cable from the port to the star coupler.
The field applies only to CI. Possible displays are:
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.
7.10 – 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.
7.11 – LP_LD_CLASS
Hard-coded capacity value of the port, based on the megabits/second rate of the interconnect of the port.
7.12 – LP_PRIORITY
Management priority assigned to the port.
7.13 – LP_STATUS
Status of the local port. The port is either online or offline.
7.14 – LP_TYPE
Device type of the port (CI780, CI750).
7.15 – MAX_PORT
Largest port number to which a virtual circuit open is attempted.
7.16 – MSGS_FREE
Number of free message buffers currently queued for receives commands.
7.17 – MSG_HDR_SIZE
Number of bytes of port header and SCS header in a message.
7.18 – NAME
Device name of the local port.
7.19 – OPEN_CIRCS
Number of virtual circuits open from the port.
7.20 – POOL_WAITERS
Number of processes waiting for nonpaged pool resources for message buffers.
7.21 – PORT_NUM
Port number assigned to the port.
7.22 – 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.
7.23 – RSPS_QUEUED
Total number of responses of all kinds received from the port but not yet processed.
8 – MEMBERS
The MEMBERS class contains information about the systems that are actively participating in the cluster. This class includes fields such as the system's clusterwide ID number and the system's membership status in the cluster.
8.1 – ACK_LM
Maximum number of OpenVMS Cluster messages the remote system can receive before sending an acknowledgment.
8.2 – ACKR_SQ
Sequence number of the last acknowledgment received over the cluster connection.
8.3 – CNX_STATE
State of the cluster connection. Possible displays are:
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.
8.4 – 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.
8.5 – DIR_WT
Lock manager distributed directory weight.
8.6 – 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 CLUSTER Class Fields.
8.7 – PROTOCOL
Protocol version number and ECO level of the connection management software.
8.8 – 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.
8.9 – QF_ACTIVE
Indicates whether the remote system's quorum file is accessible.
8.10 – QF_SAME
Indicates whether the local and remote systems agree about which disk is the quorum disk.
8.11 – 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.
8.12 – 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 CLUSTER Class Fields.
8.13 – RCVD_SQ
Sequence number of the last message received over the OpenVMS Cluster connection.
8.14 – 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.
8.15 – SEND_SQ
Sequence number of the next message to be sent over the OpenVMS Cluster connection.
8.16 – STATUS
Status of the node in the cluster. Possible displays are:
8.16.1 – blank
System is not being considered as a cluster member.
8.16.2 – BRK_MEM
System is a member of the cluster, but the connection manager has lost communication with it.
8.16.3 – BRK_NEW
System has just booted, but has not yet joined the cluster and the connection manager has lost communication with it.
8.16.4 – BRK_NON
Connection manager has lost communication with the system and the system is no longer a member of the cluster.
8.16.5 – BRK_REM
Connection manager has lost communication with the system, and the system has been removed from the cluster.
8.16.6 – 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.
8.16.7 – NON
System is not a member of the cluster.
8.16.8 – REMOVED
System has been removed from the cluster.
8.17 – SW_VERS
Indicator of the software version running on the node.
8.18 – TRANSITION_TIME
Time of the system's last change in membership status. (See the STATUS field.)
8.19 – UNACKED
Number of unacknowledged OpenVMS Cluster messages received by the remote system.
8.20 – VOTES
Number of votes the remote node contributes toward quorum. Normally, the cluster manager sets this number with the system parameter VOTES.
8.21 – WARMCDRPS
Number of CDRPs on the CDRP free queue.
9 – SYSTEMS
The SYSTEMS class contains information about the systems in the cluster. This class includes information such as the system ID, the node name, the type of system, the type of software, the software version, the number of virtual circuits, etc.
9.1 – DG_SIZE
Maximum number of bytes of application data in datagrams sent over the circuit.
9.2 – HW_TYPE
System hardware type (for example, VAXstation 3100 or HS70). (Enclose the system type between double quotation marks.)
9.3 – HW_VERS
Hardware configuration and revision levels of the remote system.
9.4 – INCARNATION
Unique 16-digit hexadecimal number established when the system is booted.
9.5 – INCN_TIME
Incarnation number expressed as a time (dd-mmm-yy hh:mm).
9.6 – MSG_SIZE
Maximum number of bytes of application data in messages sent over the circuit.
9.7 – 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.)
9.8 – NUM_CIRCUITS
Number of virtual circuits between the local system and remote systems.
9.9 – SOFTWARE
Name and version of the operating system currently running on the remote system.
9.10 – 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.