OpenVMS Cluster Systems - OpenVMS Systems - HP
OpenVMS Cluster Systems - OpenVMS Systems - HP
OpenVMS Cluster Systems - OpenVMS Systems - HP
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Troubleshooting the NISCA Protocol<br />
F.3 Using SDA to Monitor LAN Communications<br />
Example F–1 SDA Command SHOW PORT Display<br />
$ ANALYZE/SYSTEM<br />
SDA> SHOW PORT<br />
VAXcluster data structures<br />
--------------------------<br />
--- PDT Summary Page ---<br />
PDT Address Type Device Driver Name<br />
----------- ---- ------- -----------<br />
80C3DBA0 pa PAA0 PADRIVER<br />
80C6F7A0 pe PEA0 PEDRIVER<br />
F.3.3 Monitoring Virtual Circuits<br />
To examine information about the virtual circuit (VC) that carries messages<br />
between the local node (where you are running SDA) and another remote node,<br />
enter the SDA command SHOW PORT/VC=VC_remote-node-name. Example F–2<br />
shows how to examine information about the virtual channel running between a<br />
local node and the remote node, NODE11.<br />
Example F–2 SDA Command SHOW PORT/VC Display<br />
SDA> SHOW PORT/VC=VC_NODE11<br />
VAXcluster data structures<br />
--------------------------<br />
--- Virtual Circuit (VC) 98625380 ---<br />
Remote System Name: NODE11<br />
Local System ID: 217 (D9)<br />
(0:VAX) Remote SCSSYSTEMID: 19583<br />
Status: 0005 open,path<br />
------ Transmit ------- ----- VC Closures ----- ’--- Congestion Control ----<br />
Msg Xmt! 46193196 SeqMsg TMO 0 Pipe Quota/Slo/Max( 31/ 7/31<br />
Unsequence 3 CC DFQ Empty 0 Pipe Quota Reached) 213481<br />
Sequence 41973703 Topology Change% 0 Xmt C/T+> 0/1984<br />
ReXmt" 128/106<br />
Lone ACK 4219362<br />
Bytes Xmt 137312089<br />
------- Receive -------<br />
NPAGEDYN Low& 0<br />
- Messages Discarded -<br />
RndTrp uS+? 18540+7764<br />
UnAcked Msgs 0<br />
CMD Queue Len/Max 0/21<br />
----- Channel Selection -----<br />
Msg Rcv#<br />
Unsequence<br />
Sequence<br />
47612604<br />
3<br />
37877271<br />
No Xmt Chan<br />
Rcv Short Msg<br />
Illegal Seq Msg<br />
0<br />
0<br />
0<br />
Preferred Channel<br />
Delay Time<br />
Buffer Size<br />
9867F400<br />
FAAD63E0<br />
1424<br />
ReRcv$<br />
Lone ACK<br />
Cache<br />
13987<br />
9721030<br />
314<br />
Bad Checksum<br />
TR DFQ Empty<br />
TR MFQ Empty<br />
0<br />
0<br />
0<br />
Channel Count<br />
Channel Selections<br />
Protocol<br />
18<br />
32138<br />
1.3.0<br />
Ill ACK 0 CC MFQ Empty 0 Open+@ 8-FEB-1994 17:00:05.12<br />
Bytes Rcv 3821742649 Cache Miss 0 Cls+A 17-NOV-1858 00:00:00.00<br />
The SHOW PORT/VC=VC_remote-node-name command displays a number of<br />
performance statistics about the virtual circuit for the target node. The display<br />
groups the statistics into general categories that summarize such things as packet<br />
transmissions to the remote node, packets received from the remote node, and<br />
congestion control behavior. The statistics most useful for problem isolation are<br />
called out in Example F–2 and described in Table F–5.<br />
Note: The counters shown in Example F–2 are stored in fixed-size fields and are<br />
automatically reset to 0 when a field reaches its maximum value (or when the<br />
system is rebooted). Because fields have different maximum sizes and growth<br />
rates, the field counters are likely to reset at different times. Thus, for a system<br />
that has been running for a long time, some field values may seem illogical and<br />
appear to contradict others.<br />
F–10 Troubleshooting the NISCA Protocol
Change language