02.12.2012 Views

OpenVMS Cluster Systems - OpenVMS Systems - HP

OpenVMS Cluster Systems - OpenVMS Systems - HP

OpenVMS Cluster Systems - OpenVMS Systems - HP

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Cluster</strong> Troubleshooting<br />

C.9 Port Communications<br />

C.9.2 LAN Communications<br />

For clusters that include Ethernet or FDDI interconnects, a multicast scheme<br />

is used to locate computers on the LAN. Approximately every 3 seconds, the<br />

port emulator driver (PEDRIVER) sends a HELLO datagram message through<br />

each LAN adapter to a cluster-specific multicast address that is derived from the<br />

cluster group number. The driver also enables the reception of these messages<br />

from other computers. When the driver receives a HELLO datagram message<br />

from a computer with which it does not currently share an open virtual circuit,<br />

it attempts to create a circuit. HELLO datagram messages received from a<br />

computer with a currently open virtual circuit indicate that the remote computer<br />

is operational.<br />

A standard, three-message exchange handshake is used to create a virtual circuit.<br />

The handshake messages contain information about the transmitting computer<br />

and its record of the cluster password. These parameters are verified at the<br />

receiving computer, which continues the handshake only if its verification is<br />

successful. Thus, each computer authenticates the other. After the final message,<br />

the virtual circuit is opened for use by both computers.<br />

C.9.3 System Communications Services (SCS) Connections<br />

System services such as the disk class driver, connection manager, and the<br />

MSCP and TMSCP servers communicate between computers with a protocol<br />

called System Communications Services (SCS). SCS is responsible primarily for<br />

forming and breaking intersystem process connections and for controlling flow of<br />

message traffic over those connections. SCS is implemented in the port driver (for<br />

example, PADRIVER, PBDRIVER, PEDRIVER, PIDRIVER), and in a loadable<br />

piece of the operating system called SCSLOA.EXE (loaded automatically during<br />

system initialization).<br />

When a virtual circuit has been opened, a computer periodically probes a remote<br />

computer for system services that the remote computer may be offering. The<br />

SCS directory service, which makes known services that a computer is offering,<br />

is always present both on computers and HSC subsystems. As system services<br />

discover their counterparts on other computers and HSC subsystems, they<br />

establish SCS connections to each other. These connections are full duplex and<br />

are associated with a particular virtual circuit. Multiple connections are typically<br />

associated with a virtual circuit.<br />

C.10 Diagnosing Port Failures<br />

This section describes the hierarchy of communication paths and describes where<br />

failures can occur.<br />

C.10.1 Hierarchy of Communication Paths<br />

Taken together, SCS, the port drivers, and the port itself support a hierarchy of<br />

communication paths. Starting with the most fundamental level, these are as<br />

follows:<br />

• The physical wires. The Ethernet is a single coaxial cable. FDDI typically<br />

has a pair of fiber-optic cables for redundancy. The CI has two pairs of<br />

transmitting and receiving cables (path A transmit and receive and path B<br />

transmit and receive). For the CI, the operating system software normally<br />

sends traffic in automatic path-select mode. The port chooses the free path or,<br />

if both are free, an arbitrary path (implemented in the cables and star coupler<br />

and managed by the port).<br />

C–18 <strong>Cluster</strong> Troubleshooting

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!