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.

Sample Programs for LAN Control<br />

D.5 Using the Network Failure Analysis Program<br />

Table D–2 (Cont.) Creating a Physical Description of the Network<br />

Step Action Comments<br />

4 Classify each component into one of the following<br />

categories:<br />

• Node: VAX or Alpha system in the <strong>OpenVMS</strong><br />

<strong>Cluster</strong> configuration.<br />

• Adapter: LAN adapter on the system that<br />

is normally used for <strong>OpenVMS</strong> <strong>Cluster</strong><br />

communications.<br />

• Component: Generic component in the network.<br />

Components in this category can usually be<br />

shown to be working if at least one path through<br />

them is working. Wiring concentrators, DELNI<br />

interconnects, DEMPR repeaters, LAN bridges,<br />

and LAN segments and rings typically fall into<br />

this category.<br />

• Cloud: Generic component in the network.<br />

Components in this category cannot be shown to<br />

be working even if one or more paths are shown<br />

to be working.<br />

5 Use the component labels from step 3 to describe<br />

each of the connections in the <strong>OpenVMS</strong> <strong>Cluster</strong><br />

communications network.<br />

6 Choose a node or group of nodes to run the network<br />

failure analysis program.<br />

D–6 Sample Programs for LAN Control<br />

The cloud component is necessary only when<br />

multiple paths exist between two points within the<br />

network, such as with redundant bridging between<br />

LAN segments. At a high level, multiple paths<br />

can exist; however, during operation, this bridge<br />

configuration allows only one path to exist at one<br />

time. In general, this bridge example is probably<br />

better handled by representing the active bridge<br />

in the description as a component and ignoring the<br />

standby bridge. (You can identify the active bridge<br />

with such network monitoring software as RBMS<br />

or DECelms.) With the default bridge parameters,<br />

failure of the active bridge will be called out.<br />

You should run the program only on a node that<br />

you included in the physical description when you<br />

edited LAVC$FAILURE_ANALYSIS.MAR. The<br />

network failure analysis program on one node<br />

operates independently from other systems in the<br />

<strong>OpenVMS</strong> <strong>Cluster</strong>. So, for executing the network<br />

failure analysis program, you should choose systems<br />

that are not normally shut down. Other good<br />

candidates for running the program are systems<br />

with the following characteristics:<br />

• Faster CPU speed<br />

• Larger amounts of memory<br />

• More LAN adapters (running the NISCA<br />

protocol)<br />

Note: The physical description is loaded into<br />

nonpaged pool, and all processing is performed at<br />

IPL 8. CPU use increases as the average number of<br />

network components in the network path increases.<br />

CPU use also increases as the total number of<br />

network paths increases.

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

Saved successfully!

Ooh no, something went wrong!