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

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

10.03.2013 Views

Table 1-3. Key Terms (2 of 3) Terms Definition Network Interface (Stream) Capture Buffer (Store) EARLY FIELD TRIAL Chapter 1 24 Sniffer Adaptive Application Analyzer A network interface is the local source of network traffic for Sniffer Adaptive Application Analyzer monitoring and capture. Sniffer Adaptive Application Analyzer supports a single network interface for monitoring/ capture – the Ethernet interface on the local PC. This interface is listed under the local laptop’s entry in the Navigation Panel at the left of the user interface, like this: local laptop/desktop network interface InfiniStream Console users may be accustomed to referring to the network interface as a “stream.” The basic idea is the same – it’s the console’s representation of a packet/data gathering interface. However, there are several key differences: • The Sniffer Adaptive Application Analyzer network interface is on the local PC; streams are on remote InfiniStream appliance. • Sniffer Adaptive Application Analyzer begins monitoring statistics on the network interface when it is opened in the Navigation Panel. Packets themselves are only gathered when capture is started manually. In contrast, packets/statistics are continuously gathered for active streams on InfiniStream appliances. • Sniffer Adaptive Application Analyzer only has a single network interface – the Ethernet interface on the local laptop (identified in the list using the loopback IP address of 127.0.0.1). In contrast, the InfiniStream Console works with multiple remote appliances, each with multiple network streams. Sniffer Adaptive Application Analyzer stores captured packet and metadata in an in-memory capture buffer on the local PC. Recorded data stored in the capture buffer can be saved to trace files for permanent storage. InfiniStream Console users may be accustomed to referring to the capture buffer as “the store.” The basic idea is the same – a place to keep capture packets/metadata. However, there are several key differences between the Sniffer Adaptive Application Analyzer capture buffer and the store on an InfiniStream appliance: • Capture buffer is on the local PC; the store is on a remote InfiniStream appliance. • Capture buffer is designed for short-term recording and is filled on demand when capture starts; the store is a persistent stream-todisk operation designed for long-term forensic storage and analysis. • Capture buffer is relatively small (up to 1GB) and can be saved to trace files; the store is massive, typically spanning multiple disks/ arrays. • Capture buffer is dynamic and is removed when the application shuts down; the store is persistent.

EARLY FIELD TRIAL Table 1-3. Key Terms (3 of 3) Terms Definition Sniffer Adaptive Application Analyzer Overview Statistical Data Statistical Data refers to the RMON network statistics tabulated and presented in the Statistics panel at the base of the Quick Select window. Statistical Data includes traditional packet/byte counts broken out by MAC address, IP address, application port, conversation, and so on. Sniffer Adaptive Application Analyzer begins monitoring statistical data when you double-click the local network interface in the Navigation Panel – the Graph Panel will begin to update and display traffic volume over time. However, Sniffer Adaptive Application Analyzer does not record packets until you manually start capture. You can use the color-coded Availability Meter at the base of the Graph Panel to determine where both packets and statistics are available and where only statistics are available. Refer to Availability Meter on page 56 for details. Time Selection After Sniffer Adaptive Application Analyzer begins capturing packets, you can select a segment of the available packets in the Graph Panel for analysis. That segment – a portion of the available packets with a beginning and end time – is called a time selection. You must make a time selection before you can analyze or mine the stream’s data. Data Mining Data mining, or mining, refers to your ability to retrieve some of the packets in the capture buffer using your own custom search criteria. Mining allows you to locate specific sets of packets and conversations within the available data. Mining Filter A mining filter is a user-configured set of packet criteria and Boolean logic you can use to sift through data in the capture buffer. Source Filter A source filter is a user-configured set of packet criteria and Boolean logic Sniffer Adaptive Application Analyzer uses to filter unwanted packets before they are used for RMON monitoring or recorded to the capture buffer. Use these with care, since those packets you filter out are irretrievable. User’s Guide 25

Table 1-3. Key Terms (2 of 3)<br />

Terms Definition<br />

Network Interface<br />

(Stream)<br />

Capture Buffer<br />

(Store)<br />

EARLY FIELD TRIAL Chapter 1<br />

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

A network interface is the local source of network traffic for <strong>Sniffer</strong><br />

<strong>Adaptive</strong> <strong>Application</strong> <strong>Analyzer</strong> monitoring and capture. <strong>Sniffer</strong> <strong>Adaptive</strong><br />

<strong>Application</strong> <strong>Analyzer</strong> supports a single network interface for monitoring/<br />

capture – the Ethernet interface on the local PC. This interface is listed<br />

under the local laptop’s entry in the Navigation Panel at the left of the<br />

user interface, like this:<br />

local laptop/desktop<br />

network interface<br />

InfiniStream Console users may be accustomed to referring to the<br />

network interface as a “stream.” The basic idea is the same – it’s the<br />

console’s representation of a packet/data gathering interface. However,<br />

there are several key differences:<br />

• The <strong>Sniffer</strong> <strong>Adaptive</strong> <strong>Application</strong> <strong>Analyzer</strong> network interface is on the<br />

local PC; streams are on remote InfiniStream appliance.<br />

• <strong>Sniffer</strong> <strong>Adaptive</strong> <strong>Application</strong> <strong>Analyzer</strong> begins monitoring statistics on<br />

the network interface when it is opened in the Navigation Panel.<br />

Packets themselves are only gathered when capture is started<br />

manually. In contrast, packets/statistics are continuously gathered<br />

for active streams on InfiniStream appliances.<br />

• <strong>Sniffer</strong> <strong>Adaptive</strong> <strong>Application</strong> <strong>Analyzer</strong> only has a single network<br />

interface – the Ethernet interface on the local laptop (identified in<br />

the list using the loopback IP address of 127.0.0.1). In contrast, the<br />

InfiniStream Console works with multiple remote appliances, each<br />

with multiple network streams.<br />

<strong>Sniffer</strong> <strong>Adaptive</strong> <strong>Application</strong> <strong>Analyzer</strong> stores captured packet and<br />

metadata in an in-memory capture buffer on the local PC. Recorded data<br />

stored in the capture buffer can be saved to trace files for permanent<br />

storage.<br />

InfiniStream Console users may be accustomed to referring to the<br />

capture buffer as “the store.” The basic idea is the same – a place to<br />

keep capture packets/metadata. However, there are several key<br />

differences between the <strong>Sniffer</strong> <strong>Adaptive</strong> <strong>Application</strong> <strong>Analyzer</strong> capture<br />

buffer and the store on an InfiniStream appliance:<br />

• Capture buffer is on the local PC; the store is on a remote<br />

InfiniStream appliance.<br />

• Capture buffer is designed for short-term recording and is filled on<br />

demand when capture starts; the store is a persistent stream-todisk<br />

operation designed for long-term forensic storage and analysis.<br />

• Capture buffer is relatively small (up to 1GB) and can be saved to<br />

trace files; the store is massive, typically spanning multiple disks/<br />

arrays.<br />

• Capture buffer is dynamic and is removed when the application<br />

shuts down; the store is persistent.

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

Saved successfully!

Ooh no, something went wrong!