Appendix E |
Appendix E
|
Subroutines for LAN Control
|
E.1
|
Introduction
|
E.1.1
|
Purpose of the Subroutines
|
E.2
|
Starting the NISCA Protocol
|
E.2.1
|
Status
|
E.2.2
|
Error Messages
|
E.3
|
Stopping the NISCA Protocol
|
E.3.1
|
Status
|
E.3.2
|
Error Messages
|
E.4
|
Creating a Representation of a Network Component
|
E.4.1
|
Status
|
E.4.2
|
Error Messages
|
E.5
|
Creating a Network Component List
|
E.5.1
|
Status
|
E.5.2
|
Error Messages
|
E.6
|
Starting Network Component Failure Analysis
|
E.6.1
|
Status
|
E.6.2
|
Error Messages
|
E.7
|
Stopping Network Component Failure Analysis
|
E.7.1
|
Status
|
E.7.2
|
Error Messages
|
Appendix F |
Appendix F
|
Troubleshooting the NISCA Protocol
|
F.1
|
How NISCA Fits into the SCA
|
F.1.1
|
SCA Protocols
|
F.1.2
|
Paths Used for Communication
|
F.1.3
|
PEDRIVER
|
F.2
|
Addressing LAN Communication Problems
|
F.2.1
|
Symptoms
|
F.2.2
|
Traffic Control
|
F.2.3
|
Excessive Packet Losses on LAN Paths
|
F.2.4
|
Preliminary Network Diagnosis
|
F.2.5
|
Tracing Intermittent Errors
|
F.2.6
|
Checking System Parameters
|
F.2.7
|
Channel Timeouts
|
F.3
|
Using SDA to Monitor LAN or IP Communications
|
F.3.1
|
Isolating Problem Areas
|
F.3.2
|
SDA Command SHOW PORT
|
F.3.3
|
Monitoring Virtual Circuits
|
F.3.4
|
Monitoring PEDRIVER for LAN devices
|
F.3.5
|
Monitoring PEDRIVER Buses for LAN Devices
|
F.3.6
|
Monitoring LAN Adapters
|
F.3.7
|
Monitoring PEDRIVER Buses for IP interfaces
|
F.3.8
|
Monitoring PEDRIVER Channels for IP Interfaces
|
F.4
|
Using SCACP to Monitor Cluster Communications
|
F.5
|
Troubleshooting NISCA Communications
|
F.5.1
|
Areas of Trouble
|
F.6
|
Channel Formation
|
F.6.1
|
How Channels Are Formed
|
F.6.2
|
Techniques for Troubleshooting
|
F.7
|
Retransmission Problems
|
F.7.1
|
Why Retransmissions Occur
|
F.7.2
|
Techniques for Troubleshooting
|
F.8
|
Understanding NISCA Datagrams
|
F.8.1
|
Packet Format
|
F.8.2
|
LAN Headers
|
F.8.3
|
Ethernet Header
|
F.8.4
|
Datagram Exchange (DX) Header
|
F.8.5
|
Channel Control (CC) Header
|
F.8.6
|
Transport (TR) Header
|
F.9
|
Using a LAN Protocol Analysis Program
|
F.9.1
|
Single or Multiple LAN Segments
|
F.9.2
|
Multiple LAN Segments
|
F.10
|
Data Isolation Techniques
|
F.10.1
|
All OpenVMS Cluster Traffic
|
F.10.2
|
Specific OpenVMS Cluster Traffic
|
F.10.3
|
Virtual Circuit (Node-to-Node) Traffic
|
F.10.4
|
Channel (LAN Adapter--to--LAN Adapter) Traffic
|
F.10.5
|
Channel Control Traffic
|
F.10.6
|
Transport Data
|
F.11
|
Setting Up an HP 4972A LAN Protocol Analyzer
|
F.11.1
|
Analyzing Channel Formation Problems
|
F.11.2
|
Analyzing Retransmission Problems
|
F.12
|
Filters
|
F.12.1
|
Capturing All LAN Retransmissions for a Specific OpenVMS Cluster
|
F.12.2
|
Capturing All LAN Packets for a Specific OpenVMS Cluster
|
F.12.3
|
Setting Up the Distributed Enable Filter
|
F.12.4
|
Setting Up the Distributed Trigger Filter
|
F.13
|
Messages
|
F.13.1
|
Distributed Enable Message
|
F.13.2
|
Distributed Trigger Message
|
F.14
|
Programs That Capture Retransmission Errors
|
F.14.1
|
Starter Program
|
F.14.2
|
Partner Program
|
F.14.3
|
Scribe Program
|
Appendix G |
Appendix G
|
NISCA Transport Protocol Congestion Control
|
G.1
|
NISCA Congestion Control
|
G.1.1
|
Congestion Caused by Retransmission
|
G.1.1.1
|
OpenVMS VAX Version 6.0 or OpenVMS AXP Version 1.5, or Later
|
G.1.2
|
HELLO Multicast Datagrams
|
G.1.3
|
HELLO IP Unicast and IP Multicast Datagrams
|