10.03.2013 Views

Sniffer® Portable Professional User's Guide - NetScout

Sniffer® Portable Professional User's Guide - NetScout

Sniffer® Portable Professional User's Guide - NetScout

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.

Chapter 7<br />

Limitations of the Expert Filter<br />

152 Sniffer <strong>Portable</strong> <strong>Professional</strong><br />

The Expert filter has the following limitations:<br />

Some symptoms and diagnoses, such as Broadcast storm, have<br />

no associated network object on which the analyzer can filter. In<br />

those cases, the Define Filter button will not appear at the upper<br />

left of the display, indicating that an Expert filter cannot be set.<br />

Expert filters are not supported on objects at the Multicast layer.<br />

Expert filters support a maximum of 10 objects. Make sure you<br />

have selected no more than 10 objects before using this feature.<br />

Occasionally you will see the message:<br />

No frames are eligible for display<br />

This message appears when one or more of the following conditions<br />

exist:<br />

The highlighted object has not sent or received a frame<br />

The highlighted object has been filtered out by a standard<br />

Display filter<br />

Other Notes About Expert Filters<br />

The Expert analyzer uses several algorithms to decide which frames are<br />

associated with a network object. Sometimes, these algorithms may<br />

eliminate frames you consider relevant.<br />

Certain maintenance frames may not be shown. For example, if<br />

you set an Expert filter on a Novell Netware connection-layer<br />

connection, the Expert analyzer would show all those related<br />

frames with NCP layers, but would not show certain connection<br />

maintenance frames it considers irrelevant.<br />

When you set a filter on a connection object, the frame that<br />

initiates the connection is not shown. This is because Expert does<br />

not create a connection object until the connection is completed.<br />

When you filter on an application object, TCP continuation frames<br />

are not shown.

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

Saved successfully!

Ooh no, something went wrong!