[ovs-dev] ovs-vsctl for sFlow config
Neil McKee
neil.mckee at inmon.com
Wed May 5 22:24:18 UTC 2010
Works now. Good. And I was able to add additional collector targets like this:
ovs-vsctl add sFlow br0 targets \"10.0.0.72:6343\"
Below is a bash script to turn on sFlow on all bridges with the same settings. Does this look right? Is there a better way to get the list of bridge names?
#!/bin/bash
COLLECTOR_IP="10.0.0.72:6343"
AGENT_IP=eth0
HEADER_BYTES=128
SAMPLING_N=256
POLLING_SECS=30
SFLOWUUID=`ovs-vsctl create sFlow agent=\"${AGENT_IP}\" target=\"${COLLECTOR_IP}\" header=${HEADER_BYTES} sampling=${SAMPLING_N} polling=${POLLING_SECS}`
for BRIDGE in `ovs-vsctl list br | awk -- '/^name/ { print $3; }'` ; do
echo "configuring sFlow for $BRIDGE"
ovs-vsctl set bridge br0 sflow=$SFLOWUUID ;
done
On May 5, 2010, at 1:30 PM, Ben Pfaff wrote:
> On Wed, May 05, 2010 at 12:55:15PM -0700, Neil McKee wrote:
>> 2. It seems that the patch I sent on Jan 21st did not make it into
>> the trunk, so sFlow is not working properly. It looks like the same
>> patch can be used again since the only other changes to
>> ofproto-sflow.c that have happened since then are cosmetic. I attach
>> it below, and here were the comments that went with it at the time:
>
> It's embarrassing that I dropped the ball like that. Sorry. I pushed
> your fixes to "master".
>
> I tried looking back through my inbox for other patches that I might
> have missed. I didn't see any obvious ones. Please do let me know if
> you notice anything else that's "gone missing".
More information about the dev
mailing list