10.03.2013 Views

Sniffer Adaptive Application Analyzer: Adaptive Mode ... - NetScout

Sniffer Adaptive Application Analyzer: Adaptive Mode ... - NetScout

Sniffer Adaptive Application Analyzer: Adaptive Mode ... - NetScout

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

EARLY FIELD TRIAL Chapter 9<br />

224 <strong>Sniffer</strong> <strong>Adaptive</strong> <strong>Application</strong> <strong>Analyzer</strong><br />

The Expert also provides concise explanations for each symptom and<br />

diagnosis generated. To display a detailed explanation of a symptom or<br />

diagnosis, click the question mark (?) to the right of the symptom/<br />

diagnosis description in the Expert Detail pane. (You may have to scroll<br />

to the right of the pane to see the ?.)<br />

Postcapture Expert/Decode Statistics and CRCs<br />

Postcapture Decode and Expert statistics for raw packets do not take<br />

into account the CRC bytes attached to frames. This is by design, as the<br />

CRC bytes are not a part of the frame. Because of this, the Expert will<br />

show average frame sizes that are smaller than those reported by other<br />

views that do include the CRC – for example, the Statistics tab in the<br />

postcapture display, and all displays in the Quick Select window. For<br />

Ethernet, the difference will be 4 bytes; for WAN PPP, either 2 or 4 bytes,<br />

depending on how the network implements the CRC field.<br />

Extra Characters in Expert Displays for High Counts?<br />

Occasionally, you may see counts in the Expert displays followed by the<br />

letters M, G, or T. These letters stand for Million, Giga, and Tera,<br />

respectively.<br />

Saving Expert Objects with Trace Files<br />

During capture, the Expert creates Expert objects based on the frames<br />

it sees. Over a long capture, some of the frames which the Expert used<br />

to create these objects will most likely pass out of the capture buffer to<br />

make room for new ones. However, the Expert objects themselves will<br />

still be in the database.<br />

You can make sure that all the Expert objects created during a capture<br />

session are saved along with your trace file by enabling the Save Expert<br />

Objects checkbox in the Save As dialog box. When this option is<br />

enabled, all of the Expert objects in the database are written to the end<br />

of the saved trace file. Then, when you open a trace with saved Expert<br />

objects, make sure to enable the Load Expert Objects checkbox in the<br />

Open dialog box. This way, when you reopen a saved trace file, you can<br />

make sure you see all the Expert objects created during a capture<br />

session instead of just the ones the Expert creates based on the frames<br />

still in the file.<br />

Notes on the Save/Load Expert Objects Feature<br />

If you enable the Load Expert Objects option when opening a<br />

trace file that has no saved Expert objects, no error will occur. The<br />

saved file will simply be loaded normally.

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

Saved successfully!

Ooh no, something went wrong!