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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

G<br />

NISCA Transport Protocol Channel Selection<br />

and Congestion Control<br />

G.1 NISCA Transmit Channel Selection<br />

This appendix describes PEDRIVER running on <strong>OpenVMS</strong> Version 7.3 (Alpha<br />

and VAX) and PEDRIVER running on earliers versions of <strong>OpenVMS</strong> Alpha and<br />

VAX.<br />

G.1.1 Multiple-Channel Load Distribution on <strong>OpenVMS</strong> Version 7.3 (Alpha and<br />

VAX) or Later<br />

While all available channels with a node can be used to receive datagrams from<br />

that node, not all channels are necessarily used to transmit datagrams to that<br />

node. The NISCA protocol chooses a set of equally desirable channels to be used<br />

for datagram transmission, from the set of all available channels to a remote<br />

node. This set of transmit channels is called the equivalent channel set (ECS).<br />

Datagram transmissions are distributed in round-robin fashion across all the<br />

ECS members, thus maximizing internode cluster communications throughput.<br />

G.1.1.1 Equivalent Channel Set Selection<br />

When multiple node-to-node channels are available, the <strong>OpenVMS</strong> <strong>Cluster</strong><br />

software bases the choice of which set of channels to use on the following criteria,<br />

which are evaluated in strict precedence order:<br />

1. Packet loss history<br />

Channels that have recently been losing LAN packets at a high rate are<br />

termed lossy and will be excluded from consideration. Channels that have<br />

an acceptable loss history are termed tight and will be further considered for<br />

use.<br />

2. Capacity<br />

Next, capacity criteria for the current set of tight channels are evaluated. The<br />

capacity criteria are:<br />

a. Priority<br />

Management priority values can be assigned both to individual channels<br />

and to local LAN devices. A channel’s priority value is the sum of these<br />

management-assigned priority values. Only tight channels with a priority<br />

value equal to, or one less than, the highest priority value of any tight<br />

channel will be further considered for use.<br />

b. Packet size<br />

Tight, equivalent-priority channels whose maximum usable packet size is<br />

equivalent to that of the largest maximum usable packet size of any tight<br />

equivalent-priority channel will be further considered for use.<br />

NISCA Transport Protocol Channel Selection and Congestion Control G–1

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

Saved successfully!

Ooh no, something went wrong!