Technical data

FastIron Ethernet Switch Administration Guide 271
53-1002637-02
sFlow
11
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.
Brocade(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.
Brocade(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
NOTE
FastIron devices support sFlow version 5 by default.
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
• Combines sFlow samples into UDP packets and forwards them to the sFlow collectors for
analysis
• Forwards byte and packet count data, or counter samples, to sFlow collectors
sFlow is described in RFC 3176, “InMon Corporation's sFlow: A Method for Monitoring Traffic in
Switched and Routed Networks”.
On ICX and FCX Series devices, you can use QoS queue 1 for priority traffic, even when sFlow is
enabled on the port. This differs from FastIron X Series devices, which support seven priorities
instead of eight when sFlow is enabled. In this case, QoS queue 1 is reserved for sFlow and is not
used by other packets. Any non-sFlow packets assigned to QoS queue 1 will be directed to QoS
queue 0.