Re: Cisco Nexus Odd sFlow Implementation

[Mike Hammett <nanog () ics-il net>]

But then I'm storing and processing twice as much data as I need. 




----- 
Mike Hammett 
Intelligent Computing Solutions 

Midwest Internet Exchange 

The Brothers WISP 

----- Original Message -----

From: "Raymond Burkholder" <ray () oneunified net> 
To: nanog () nanog org 
Sent: Monday, March 20, 2023 10:16:37 AM 
Subject: Re: Cisco Nexus Odd sFlow Implementation 



On 3/20/23 08:55, Mike Hammett wrote: 



Cisco is sending the in and out packets in their sFlow implementation on their Nexus switches. Obviously, this double 
counts the information. 


Are there solutions that process those flows and remove one of those directions? 



Wouldn't you just do that in your reporting? The report engine usually has options for interface, ingress/egress, 
prefix range, protocol, .... 

Then when you need to aggregate for a specific interface for additional troubleshooting, you have all the information 
for when you need it. 

Yes, your aggregate numbers for total packets transiting is double, but I generally have specific reports for specific 
traffic patterns I focus on anyway. 

Raymond Burkholder 
One Unified Net Limited 


<blockquote>






----- 
Mike Hammett 
Intelligent Computing Solutions 

Midwest Internet Exchange 

The Brothers WISP 


</blockquote>