Brocade TurboIron 24X Series Configuration Guide - Manual (Page 275)

Brocade TurboIron 24X Series Configuration Guide 241
53-1003053-01
sFlow
You can modify the sampling interval and the bucket (number of entries saved before overwrite)
using the CLI. In the above example, owner refers to the RMON station that will request the
information.
NOTE
To review the control data entry for each port or interface, enter the show rmon history command.
Alarm (RMON group 3)
Alarm is designed to monitor configured thresholds for any SNMP integer, time tick, gauge or
counter MIB object. Using the CLI, you can define what MIB objects are monitored, the type of
thresholds that are monitored (falling, rising or both), the value of those thresholds, and the
sample type (absolute or delta).
An alarm event is reported each time that a threshold is exceeded. The alarm entry also indicates
the action (event) to be taken if the threshold be exceeded.
A sample CLI alarm entry and its syntax is shown below.
TurboIron(config)#rmon alarm 1 ifInOctets.6 10 delta rising-threshold 100 1
falling threshold 50 1 owner nyc02
Syntax: rmon alarm <entry-number> <MIB-object.interface-num> <sampling-time>
<sample-type> <threshold-type> <threshold-value> <event-number> <threshold-type>
<threshold-value> <event-number> owner <text-string>
Event (RMON group 9)
There are two elements to the Event Group—the event control table and the event log table.
The event control table defines the action to be taken when an alarm is reported. Defined events
can be found by entering the CLI command, show event. The Event Log Table collects and stores
reported events for retrieval by an RMON application.
A sample entry and syntax of the event control table is shown below.
TurboIron(config)#rmon event 1 description ‘testing a longer string’ log-and-trap
public owner nyc02
Syntax: rmon event <event-entry> description <text-string> log | trap | log-and-trap owner
<rmon-station>
sFlow
sFlow is a standards-based protocol that allows network traffic to be sampled at a user-defined rate
for the purpose of monitoring traffic flow patterns and identifying packet transfer rates on
user-specified interfaces.
When sFlow is enabled on a Layer 2 or Layer 3 switch, the system performs the following
sFlow-related tasks:
• Samples traffic flows by copying packet header information
• Identifies ingress and egress interfaces for the sampled flows