I'm planning an sflow agent implementation, and ran across this
question: should a link aggregation interface be a data source? E.g.,
ifIndex 1 and ifIndex 2 are in a link aggregate, which has ifIndex 50.
Would people to expect to configure sflow on interface 1 and
interface 2 seperately, or is i
Bill,
We have seen both approaches (one datasource for the LAG, or
separate datasources for each component link). You could even offer
both: it's OK for the same packet-sample to be sent on behalf of a
component link datsource and also on behalf of the LAG datasource.
There are trade
