Wow. That's great. Thanks. I will look at what else we should add to the
sFlow export. (e.g. QinQ, NAT, ...). Should be straighforward now that we
have the actions for each sample.
Neil
On Tuesday, July 21, 2015, Ben Pfaff wrote:
> On Fri, Jul 17, 2015 at 09:37:02PM -0700, Neil McKee wrote
Sure, I'll try to get to that tonight.
Neil
--
Neil McKee
InMon Corp.
http://www.inmon.com
On Fri, Jul 17, 2015 at 4:31 PM, Ben Pfaff wrote:
> On Thu, Jun 11, 2015 at 09:43:59AM -0700, Neil McKee wrote:
> > Packets are still sampled at ingress only, so the egress
> > tunnel and/or MPLS s
On Thu, Jun 11, 2015 at 09:43:59AM -0700, Neil McKee wrote:
> Packets are still sampled at ingress only, so the egress
> tunnel and/or MPLS structures are only included when there is just 1 output
> port. The actions are either provided by the datapath in the sample upcall
> or looked up in the us
Packets are still sampled at ingress only, so the egress
tunnel and/or MPLS structures are only included when there is just 1 output
port. The actions are either provided by the datapath in the sample upcall
or looked up in the userspace cache. The former is preferred because it is
more reliable
