Status Monitoring and Statistics
NOTE
On an Aspen 8810 switch, sFlow and mirroring are mutually exclusive. You can enable either sFlow, or mirroring,
but not both.
However, you should be aware of a few limitations in the current release. The current release supports:
Generic port statistics reported to the sFlow collector
●
Non-extended data
●
Only those packets that do not match an ACL rule are considered for sampling
●
Only port-based sampling
●
No MIB support
●
Configuring sFlow
ExtremeWare XOS allows you to collect sFlow statistics on a per port basis. An agent, residing locally
on the switch, sends data to a collector that resides on another machine. You configure the local agent,
the address of the remote collector, and the ports of interest for sFlow statistics gathering. You can also
modify default values for how frequently on average a sample is taken and the maximum number of
samples allowed before throttling the sample gathering.
To configure sFlow on a switch, you must do the following tasks:
Configure the local agent
●
Configure the addresses of the remote collectors
●
Enable sFlow globally on the switch
●
Enable sFlow on the desired ports
●
Optionally, you may also change the default values of the following items:
How often the statistics are collected
●
How frequently a sample is taken, globally or per port
●
How many samples per second can be sent to the CPU
●
Configuring the Local Agent
The local agent is responsible for collecting the data from the samplers and sending that data to the
remote collector as a series of UDP datagrams. The agent address is stored in the payload of the sFlow
data, and is used by the sFlow collector to identify each agent uniquely. By default, the agent uses the
management port IP address as it's IP address. You change the agent IP address by using the following
command:
configure sflow agent {ipaddress} <ip-address>
You unconfigure the agent using this command:
unconfigure sflow agent
ExtremeWare XOS 11.1 Concepts Guide
144