Sniffer® Portable Professional User's Guide - NetScout
Sniffer® Portable Professional User's Guide - NetScout
Sniffer® Portable Professional User's Guide - NetScout
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Chapter 4<br />
Setting the App Threshold Tab Options<br />
52 Sniffer <strong>Portable</strong> <strong>Professional</strong><br />
Use the options in the Tools > Options > App Threshold tab to set<br />
thresholds for alarms generated by the ART application. Specify the<br />
threshold values in the Rsp Time column, then click OK.<br />
See ART Alarms on page 105 and Application Response Time (ART) on<br />
page 97 for details on using the options in this tab.<br />
Setting the Alarm Tab Options<br />
Use the Tools > Options > Alarm tab to:<br />
Enable alarm logging and set alarm severity levels. See The Alarm<br />
Log on page 257 and Setting Alarm Severity Levels on page 260.<br />
Set up and assign alarm notification actions. See Setting Alarm<br />
Notification on page 264.<br />
Setting the Protocols Tab Options<br />
Use the Tools > Options > Protocols tab to specify on what ports the<br />
Sniffer should expect various upper layer protocols running over TCP,<br />
UDP, or IPX (separate options are provided for each). The commonly<br />
established port for each upper layer protocol is provided by default. For<br />
most networks, the default port number for the listed upper layer<br />
protocols will be correct. However, If your network uses a proprietary<br />
implementation of a particular protocol, you can specify custom ports<br />
here. You can also rename existing protocols by overwriting the default<br />
name supplied in this tab.<br />
In addition, you can also add entirely custom protocols by clicking in a<br />
blank cell at the end of the list and supplying a protocol and port pair for<br />
a given transport. The Sniffer will provide traffic counts for the named<br />
protocol/port pair in its Monitor displays.<br />
NOTE: The Sniffer can only track protocol loads that are based on<br />
well known and fixed port numbers. If you have an application that<br />
assigns and uses TCP/UDP (or IPX) port numbers dynamically, they<br />
will be grouped into the Others category in Monitor views.<br />
Similarly, upper layer packets running over TCP, UDP, or IPX with<br />
port numbers not listed in the default protocol list are also grouped<br />
together and counted in the Others category.
Change language