Appendix A. Appendix

Table of Contents

A.1. Configuring switches to send sFlow
A.1.1. Using SNMP to configure the switch to send sFlow
A.1.1.1. Configuring ProCurve switches to allow sFlow configuration via SNMP
A.1.2. Using the switch CLI to configure sFlow
A.1.2.1. Alcatel-Lucent OmniSwitch
A.1.2.2. Extreme Networks
A.1.2.3. Force10 Networks
A.1.2.4. Foundry Networks
A.1.2.5. ProCurve Networking by HP
A.2. Recommended sampling rates

A.1. Configuring switches to send sFlow

Your switches must be configured to send sFlow to sFlowTrend-Pro. There are two methods for configuring sFlow: telling sFlowTrend-Pro to configure the switch using SNMP or using the command line interface (CLI) on the switch.

A.1.1. Using SNMP to configure the switch to send sFlow

sFlowTrend-Pro can configure a switch to send sFlow using SNMP. You will need to make sure that the switch is configured to allow SNMP read/write access from sFlowTrend-Pro. You will also need to know the SNMP read/write community string. See Section 6.1.1, “Adding a switch that is to be configured using SNMP” for details on how to set up sFlowTrend-Pro so that it uses SNMP to configure a switch to send sFlow.

Alcatel-Lucent and ProCurve Networking by HP switches support SNMP configuration of sFlow.

A.1.1.1. Configuring ProCurve switches to allow sFlow configuration via SNMP

You can use SNMP to configure ProCurve switches (except the 9300 and 9400 series) to send sFlow. For this to be possible you must ensure that sFlowTrend-Pro uses an SNMP community that is configured on the switch with unrestricted write access and that the IP address of the host running sFlowTrend-Pro is included in the list of authorised managers configured on the switch.

Assuming that sFlowTrend-Pro is running on host with IP address 10.1.2.5 and is using the read/write SNMP community snmprw, access the command line interface on the ProCurve switch and take the following steps to set up the switch so that it will allow sFlowTrend-Pro to configure sFlow via SNMP:

  1. Configure the SNMP community so that it will allow any MIB variable that has read/write access to be set:

    (config)# snmp-server community snmprw manager unrestricted
                                    

    Then verify this setting with:

    (config)# show snmp-server
                                   

    The result should be something like:

     SNMP Communities
    
      Community Name   MIB View Write Access
      ---------------- -------- ------------
      snmprw           Manager  Unrestricted
                                   

  2. Configure the IP authorized managers to include the IP address of the host running sFlowTrend-Pro:

    (config)# ip authorized-managers 10.1.2.5
                                    

    Then verify this setting with:

    (config)# show ip authorized-managers
                                    

    The result should be something like:

     IP Managers
    
      Authorized Manager IP  IP Mask                Access Level
      ---------------------- ---------------------- -------------
      10.1.2.5               255.255.255.255        Manager
                                   

A.1.2. Using the switch CLI to configure sFlow

Using this method you must access the switch using its web interface, ssh, or telnet and manually configure the switch to send sFlow to the IP address and UDP port that sFlowTrend-Pro is using to receive sFlow (see Section 6.2.3, “Configuring advanced options” for information on determining and configuring the IP address and UDP port). You should enable sFlow on 1 or more interfaces on the switch and set a sampling rate and configure a counter polling interval. The counter polling interval controls how frequently the interface counters will be exported as part of the sFlow data. We recommend a counter polling interval of 30 seconds. We recommend that you enable sFlow on all interfaces. You should also determine the SNMP read community string for the switch so that you can configure sFlowTrend-Pro with this community string. This will allow sFlowTrend-Pro to query the switch for interface and system names.

Some example CLI configurations for enabling sFlow globally are given in the following sections. The configurations are for sFlowTrend-Pro running on a system with IP address 10.1.2.5 and receiving sFlow data on UDP port 6343, with the sFlow agent address which uniquely identifies the switch explicitly set to 10.10.10.1 (where possible).

Many switches support a command to show the current sFlow configuration and to indicate whether data has been exported:

show sflow
                

See your switch documentation for more details.

A.1.2.1. Alcatel-Lucent OmniSwitch

-> ip interface loopback0 10.10.10.1
-> sflow receiver 1 name sFlowTrend address 10.1.2.5 udp-port 6343
-> sflow sampler 1 1/1-24 receiver 1 rate 128
-> sflow poller 1 1/1-24 receiver 1 interval 30
                
[Note] Note

The OmniSwitches also support the configuration of sFlow using SNMP.

A.1.2.2. Extreme Networks

enable sflow
configure sflow-agent 10.10.10.1
configure sflow-collector 10.1.2.5 port 6343
configure sflow sample-rate 128
configure sflow poll-interval 30
configure sflow backoff-threshold 50
enable sflow backoff-threshold
enable sflow ports all        
            

A.1.2.3. Force10 Networks

Force10(conf)# sflow enable
Force10(conf)# sflow collector 10.1.2.5 agent-addr 10.10.10.1 6343
Force10(conf)# sflow sample-rate 128
Force10(conf)# sflow polling-interval 30
            

A.1.2.4. Foundry Networks

config> int e 1/1 to 4/48 
interface> sflow forwarding 
config> sflow destination 10.1.2.5 6343
config> sflow sample 128 
config> sflow polling-interval 30 
config> sflow enable
            

A.1.2.5. ProCurve Networking by HP

All ProCurve switches that support sFlow (except the 9300 and 9400 series) can be configured using SNMP. In addition, the ProCurve 3500 and 5400 series switches can be configured to send sFlow using the CLI.

(config)# sflow 1 destination 10.1.2.5 6343
(config)# sflow 1 sampling ethernet A1-A24 128
(config)# sflow 1 polling ethernet A1-A24 30
            
[Note] Note

ProCurve 9300 and 9400 switches must be configured using the CLI using the syntax given for Foundry switches. All other ProCurve switches can also be configured using SNMP to send sFlow;