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.

Packet Status Flags in the Summary Pane<br />

Displaying Captured Data<br />

For most network topologies, the Status column in the Summary pane<br />

is empty if the packet is normal with no errors, symptoms, or diagnoses<br />

associated with it. The exceptions to this rule are as follows:<br />

For data captured from a wireless LAN, the Status column<br />

indicates the wireless LAN channel from which the packet was<br />

captured inside brackets. For example, an entry of [1] in the<br />

Status column indicates that the corresponding packet was<br />

captured from wireless LAN channel number 1.<br />

Otherwise, Table 8-8 lists the flags used in the Status column of the<br />

Summary pane. Note that any of the flags associated with error frames<br />

(CRC, Jabber, Runt, and so on) require an enhanced driver for detection<br />

and reporting.<br />

Table 8-8. Status Flags<br />

M Packet is marked. Mark a packet to return quickly to a<br />

particular spot in a decoded set of frames.<br />

A Packet was captured from Port A on the pod or adapter<br />

card.<br />

B Packet was captured from Port B on the pod or adapter<br />

card.<br />

# Packet has a symptom or diagnosis associated with it.<br />

Trigger Packet is an event filter trigger<br />

CRC CRC error packet with normal packet size<br />

Jabber CRC error packet with oversize error<br />

Runt Packet size is less than 64 bytes (including the 4 CRC<br />

bytes) but with valid CRC<br />

Fragment Packet size is less than 64 bytes (including the 4 CRC<br />

bytes) with CRC error<br />

Oversize Packet size is more than 1518 (including the 4 CRC bytes)<br />

but with valid CRC<br />

Collision Packet was damaged by a collision<br />

Alignment Packet length is not an integer multiple of 8 bits.<br />

User’s <strong>Guide</strong> 185

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

Saved successfully!

Ooh no, something went wrong!