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 />
Field Description<br />
$ HELLO Xmt err (HELLO<br />
transmission error)<br />
Indicates how many times a message transmission failure has ‘‘dropped’’ a<br />
PEDRIVER HELLO datagram message. (The Channel Control [CC] level<br />
description in Section F.1 briefly describes the purpose of HELLO datagram<br />
messages.) If many HELLO transmission errors occur, PEDRIVER on other<br />
nodes probably is timing out a channel, which could eventually result in<br />
closure of the virtual circuit.<br />
The 1623 HELLO transmission failures shown in Example F–3 contributed<br />
to the high number of transmission errors (15896). Note that it is impossible<br />
to have a low number of transmission errors and a high number of HELLO<br />
transmission errors.<br />
F.3.5 Monitoring LAN Adapters<br />
Use the SDA command SHOW LAN/COUNT to display information about<br />
the LAN adapters as maintained by the LAN device driver (the command<br />
shows counters for all protocols, not just PEDRIVER [SCA] related counters).<br />
Example F–4 shows a sample display from the SHOW LAN/COUNT command.<br />
Example F–4<br />
$ ANALYZE/SYSTEM<br />
SDA Command SHOW LAN/COUNTERS Display<br />
SDA> SHOW LAN/COUNTERS<br />
LAN Data Structures<br />
-------------------<br />
-- EXA Counters Information 22-JAN-1994 11:21:19 --<br />
Seconds since zeroed<br />
Octets received<br />
PDUs received<br />
Mcast octets received<br />
Mcast PDUs received<br />
Unrec indiv dest PDUs<br />
Unrec mcast dest PDUs<br />
Data overruns<br />
3953329<br />
13962888501<br />
121899287<br />
7494809802<br />
58046934<br />
0<br />
0<br />
2<br />
Station failures<br />
Octets sent<br />
PDUs sent<br />
Mcast octets sent<br />
Mcast PDUs sent<br />
PDUs sent, deferred<br />
PDUs sent, one coll<br />
PDUs sent, mul coll<br />
0<br />
11978817384<br />
76872280<br />
183142023<br />
1658028<br />
4608431<br />
3099649<br />
2439257<br />
Unavail station buffs!<br />
Unavail user buffers<br />
Frame check errors<br />
Alignment errors<br />
Frames too long<br />
Rcv data length error<br />
802E PDUs received<br />
802 PDUs received<br />
Eth PDUs received<br />
LAN Data Structures<br />
0<br />
0<br />
483<br />
10215<br />
142<br />
0<br />
28546<br />
0<br />
122691742<br />
Excessive collisions"<br />
Carrier check failure<br />
Short circuit failure<br />
Open circuit failure<br />
Transmits too long<br />
Late collisions<br />
Coll detect chk fail<br />
Send data length err<br />
Frame size errors<br />
5059<br />
0<br />
0<br />
0<br />
0<br />
14931<br />
0<br />
0<br />
0<br />
-------------------<br />
-- EXA Internal Counters Information 22-JAN-1994 11:22:28 --<br />
Internal counters address<br />
Number of ports<br />
No work transmits<br />
Bad PTE transmits<br />
80C58257<br />
0<br />
3303771<br />
0<br />
Internal counters size<br />
Global page transmits<br />
SVAPTE/BOFF transmits<br />
Buffer_Adr transmits<br />
24<br />
0<br />
0<br />
0<br />
Fatal error count<br />
Transmit timeouts<br />
Restart failures<br />
Power failures<br />
Hardware errors<br />
Control timeouts<br />
0<br />
0<br />
0<br />
0<br />
0<br />
0<br />
RDL errors<br />
Last fatal error<br />
Prev fatal error<br />
Last error CSR<br />
Fatal error code<br />
Prev fatal error<br />
0<br />
None<br />
None<br />
00000000<br />
None<br />
None<br />
Loopback sent<br />
System ID sent<br />
ReqCounters sent<br />
0<br />
0<br />
0<br />
Loopback failures<br />
System ID failures<br />
ReqCounters failures<br />
0<br />
0<br />
0<br />
F–14 Troubleshooting the NISCA Protocol<br />
(continued on next page)
Change language