|Help : Configure : Example 5|
Suppose an sFlow probe is being used to monitor the network shown in Figure 1. The router is unable to generate traffic data, but the two switches attached to the router are able to mirror traffic to the probe.
Figure 1 Virtual Tap
The following configuration file shows how the probe can be configured to provide traffic data for the router using mirrored traffic from the switches:
[probe] host = probe.inmon.com ; change to result of "hostname" command softwareKey = 3BC37BEF3C13E76F0003FFFFA4E46D998B7D7C3949879FCD475158E1 collectorHost = traffic.inmon.com ; name of the sFlow collector ; some settings can have default values defined at the top level ; which are then overridden for specific agents below: samplingRate = 1000 community = private ; Required to get interface counters. ; Include scripts relevant to layer 2 switching script.getArpCache.interval = 3600 ; get MAC -> ifIndex mapping script.getVlanTable.interval = 3600 ; get ifIndex -> VLAN mapping script.getIfTable.interval = 3600 ; get ifIndex -> MAC mapping ; Include scripts relevant to layer 3 switching script.getRoutingTable.interval = 3600 ; get CIDR -> nextHop, protocol, ifIndex ; Switch 1 [agent] address = 10.0.0.1 [adaptor] deviceName = eth1 mirrorDirection = input ; input traffic is being mirrored ; Switch 2 [agent] address = 10.0.0.2 [adaptor] deviceName = eth2 mirrorDirection = input ; input traffic is being mirrored ; Router [agent] address = 10.0.0.254 ; Use iBGP to obtain routing information BGP_Peer = YES BGP_LocalAS = 65111 [virtual] agent = 10.0.0.1 port = 27 ; ifIndex of interface on Switch 1 connects to Router [virtual] agent = 10.0.0.2 MAC = 080009123456 ; Router interface with MAC address 080009123456 is connected to Switch 2
Note: The router (10.0.0.254) must be configured to allow BGP peering with the probe.