Sflow data on prtg is not correct

[TsadikuBahiru78025]

We configured sflow on our nexus switch and applyed it on one of the interface but the information it sends to our monitoring system prtg is not correct. I mean it is the same information that we get from our edge router. Please help on this

[balaji.bandi]

what nexus model and what nexus os running ?

can you post sample configuration here and let us know what is not working as expected ? what you expecting to work ?

you need to bear in mind nexus and routers are not same - so there will some information not going to match all.

refer below document for reference :

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/93x/system-management/b-cisco-nexus-9000-series-nx-os-system-management-configuration-guide-93x/b-cisco-nexus-9000-series-nx-os-system-management-configuration-guide-93x_chapter_0...

[TsadikuBahiru78025]

Dear Balaji,

Thanks for the response here is the information.

cisco Nexus9000 C9372PX

sflow sampling-rate : 4096
sflow max-sampled-size : 128
sflow counter-poll-interval : 20
sflow max-datagram-size : 1400
sflow collector-ip : 10.1.39.24 , vrf : default
sflow collector-port : 7000
sflow agent-ip : 10.3.1.8
sflow data-source interface Ethernet1/27

The architecture is like this

You see I want to get the sflow information on the link which is green but the information that I get is the same as the one which I get from the red one which is the edge router.

[Georg Pauwen]

Hello,

do you have another sFlow configured for the router ? Can you post that part of the configuration as well ?

[TsadikuBahiru78025]

This is the conf for the edge router

!
multilink bundle-name authenticated
!
flow record hhh-Flow-Record-in
description record to monitor network traffic
match ipv4 source address
match ipv4 destination address
match ipv4 protocol
match interface input
match transport source-port
match transport destination-port
match ipv4 tos
collect interface output
collect counter packets long
collect counter bytes long
!
!
flow record hhh-Flow-Record-out
match ipv4 source address
match ipv4 destination address
match ipv4 protocol
match transport source-port
match transport destination-port
match ipv4 tos
match interface output
collect interface input
collect counter packets long
collect counter bytes long
!

!
flow exporter hhh-Flow-Export
destination 10.1.19.71
source Port-channel1.4
transport udp 9997
template data timeout 60
option interface-table
option sampler-table
option application-table
option c3pl-class-table
option c3pl-policy-table
option application-attributes
!

!
flow monitor hhh-Flow-Monitor-in
exporter boa-Flow-Export
cache timeout inactive 20
cache timeout active 180
record boa-Flow-Record-in
!
!
flow monitor hhh-Flow-Monitor-out
exporter boa-Flow-Export
cache timeout inactive 20
cache timeout active 180
record boa-Flow-Record-out

!

sampler PRTG-SAMPLER
mode random 1 out-of 32
!
!
interface Port-channel1.4
description Conn-To-Internet-WebSprix
encapsulation dot1Q 4
ip flow monitor hhh-Flow-Monitor-in input
ip flow monitor hhh-Flow-Monitor-out output
ip address 4.4.4.4 255.255.255.0
no ip redirects
no ip unreachables
no ip proxy-arp
ip access-group Block-Bogon-IP's in
!

[balaji.bandi]

what is the nexus os version running ?

which box is nexus 9K switch ?

what is the distribution switch ?

just want to check the VRF :

vrf management – You must use this option if the sFlow data collector is on the network connected to the management port.
vrf default – You must use this option if the sFlow data collector is on the network connected to the front-panel ports.

why you want to use sflow only - is there any way you can use NetFlow for your use case ?

[TsadikuBahiru78025]

the distribution switch is the nexus 9k switch.

the os version is 7.0(3)I6(1)

the data collector is found at the default vrf