09.12.2012 Views

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

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.

management packets, MAC packets, soft ring errors, broadcasts, multicasts,<br />

data packets, and packet size statistics.<br />

• (Group 2) His<strong>to</strong>ry group—Provides his<strong>to</strong>rical "snapshot" views of summary<br />

data collected by statistics-group managed objects. Views and sampling<br />

intervals are user-definable.<br />

• (Group 3) Alarm group—Provides <strong>the</strong> ability <strong>to</strong> set operational thresholds<br />

based on any collected data counter. Alarm thresholds can be set for a<br />

functional range or absolute value. It is also possible <strong>to</strong> set different alarms<br />

for <strong>the</strong> same value based on different thresholds. Alarm value<br />

determinations are made based on <strong>the</strong> comparison statistical samples,<br />

which are made at regular intervals.<br />

• (Group 4) Host group—Collects traffic statistics on each host connected <strong>to</strong><br />

<strong>the</strong> segment. This includes packets sent, received, errors, broadcasts,<br />

multicasts, runts, jabbers, collisions, and <strong>the</strong> order that each host was<br />

discovered by <strong>the</strong> probe.<br />

• (Group 5) HostTopN group—Provides <strong>the</strong> ability <strong>to</strong> create a specialized list of<br />

hosts based on one or more statistics over a period of time. This provides <strong>the</strong><br />

ability <strong>to</strong> identify hosts that generate <strong>the</strong> highest traffic or most errors, and<br />

so on.<br />

• (Group 6) Matrix group—Provides <strong>the</strong> ability <strong>to</strong> moni<strong>to</strong>r activity between<br />

node pairs. Each pair is s<strong>to</strong>red and all consequent conversations are logged.<br />

This feature collects traffic and error statistics for each pair, which can <strong>the</strong>n<br />

be sorted by address. This provides <strong>the</strong> ability <strong>to</strong> see which node is accessing<br />

<strong>the</strong> server <strong>the</strong> most, and so on.<br />

• (Group 7) Filter group—Enables packet-filtering capabilities for <strong>the</strong><br />

packet-capture group. Filters can be defined based on packet type, <strong>network</strong><br />

event, and so on.<br />

• (Group 8) Packet-capture group—Allows you <strong>to</strong> perform captures of all<br />

packets on <strong>the</strong> segment. Multiple buffers can be used <strong>to</strong> s<strong>to</strong>re different<br />

packet types using filtering capabilities defined by <strong>the</strong> filter group.<br />

• (Group 9) Events group—Provides <strong>the</strong> ability <strong>to</strong> have local stations send<br />

standard SNMP MIB-2 Trap information <strong>to</strong> <strong>the</strong> RMON probe, which can <strong>the</strong>n<br />

relay <strong>the</strong>m <strong>to</strong> <strong>the</strong> management station. The events group also provides<br />

notification processing of <strong>the</strong> probe's threshold alarms <strong>to</strong> <strong>the</strong> management<br />

station and <strong>the</strong> packet-capture triggering based on traffic filter matches, and<br />

so on.<br />

• (Group 10) Token Ring extensions—Provides Token Ring specific moni<strong>to</strong>ring.<br />

The feature is essentially ring station moni<strong>to</strong>ring, which includes data<br />

collection on ring state, number of stations, Active Moni<strong>to</strong>r, source routing<br />

traffic, ring <strong>to</strong>pology, fault domains, station order, claim <strong>to</strong>kens, and so on.<br />

RMON II provides moni<strong>to</strong>ring and collection capabilities similar <strong>to</strong> those provided in<br />

RMON I. RMON II, however, provides <strong>the</strong>se collection services <strong>to</strong> OSI Layer 3 and<br />

above. This allows you <strong>to</strong> moni<strong>to</strong>r <strong>network</strong> traffic by <strong>network</strong> pro<strong>to</strong>col, transport

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

Saved successfully!

Ooh no, something went wrong!