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.

Troubleshooting the NISCA Protocol<br />

F.8 Using a LAN Protocol Analysis Program<br />

F.8.2 Multiple LAN Segments<br />

To troubleshoot multiple LAN segments, LAN analyzers must be able to capture<br />

the multicast packets and dynamically enable the trigger function of the LAN<br />

analyzer, as follows:<br />

Step Action<br />

1 Start capturing the data according to the rules specific to your LAN analyzer. Compaq<br />

recommends that only one LAN analyzer transmit a distributed enable multicast packet<br />

on the LAN. The packet must be transmitted according to the media access-control rules.<br />

2 Wait for the distributed enable multicast packet. When the packet is received, enable the<br />

distributed combination trigger function. Prior to receiving the distributed enable packet,<br />

all LAN analyzers must be able to ignore the trigger condition. This feature is required<br />

in order to set up multiple LAN analyzers capable of capturing the same event. Note that<br />

the LAN analyzer transmitting the distributed enable should not wait to receive it.<br />

3 Wait for an explicit (user-defined) trigger event or a distributed trigger packet. When the<br />

LAN analyzer receives either of these triggers, the LAN analyzer should stop the data<br />

capture.<br />

Prior to receiving either trigger, the LAN analyzer should continue to capture the<br />

requested data. This feature is required in order to allow multiple LAN analyzers to<br />

capture the same event.<br />

4 Once triggered, the LAN analyzer completes the distributed trigger function to stop the<br />

other LAN analyzers from capturing data related to the event that has already occurred.<br />

The <strong>HP</strong> 4972A LAN Protocol Analyzer, available from the Hewlett-Packard<br />

Company, is one example of a network failure analysis tool that provides the<br />

required functions described in this section.<br />

Reference: Section F.10 provides examples that use the <strong>HP</strong> 4972A LAN Protocol<br />

Analyzer.<br />

F.9 Data Isolation Techniques<br />

The following sections describe the types of data you should isolate when you use<br />

a LAN analysis tool to capture <strong>OpenVMS</strong> <strong>Cluster</strong> data between nodes and LAN<br />

adapters.<br />

F.9.1 All <strong>OpenVMS</strong> <strong>Cluster</strong> Traffic<br />

To isolate all <strong>OpenVMS</strong> <strong>Cluster</strong> traffic on a specific LAN segment, capture all the<br />

packets whose LAN header contains the protocol type 60–07.<br />

Reference: See also Section F.7.2 for a description of the LAN headers.<br />

F.9.2 Specific <strong>OpenVMS</strong> <strong>Cluster</strong> Traffic<br />

To isolate <strong>OpenVMS</strong> <strong>Cluster</strong> traffic for a specific cluster on a specific LAN<br />

segment, capture packets in which:<br />

• The LAN header contains the the protocol type 60–07.<br />

• The DX header contains the cluster group number specific to that <strong>OpenVMS</strong><br />

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

Reference: See Sections F.7.2 and F.7.5 for descriptions of the LAN and DX<br />

headers.<br />

F–26 Troubleshooting the NISCA Protocol

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

Saved successfully!

Ooh no, something went wrong!