Cruz cannot analyze the sFlow data from my S5232 and S5248

Hi,

I spoke to one of the network support co-worker and he mentioned this might due to incomplete configuration of sFlow. Also, he said not to use management VRF, try using non-default VRF.

Try completing all the sFlow configurations listed in this user guide: https://dell.to/3RvH390

Dear Joey C.
With the same success, can you advise me not to use the "sflow enable all-interfaces" setting.
Are your VRFs on DellOS10 limited? Are they not working properly?
Ping from VRF "management" goes to my collector and returns to the back (I provide a screenshot), what other mechanisms are there to check its operation?
Should I not use the VRF that is created from the beginning?
Why is it even possible to use VRF in a sFlow setup?
I advise you to use the guide that I will attach in this message, and you will see that my settings are correct.

Let's clarify one more point, what do you think there is a misconfiguration? This is when I don't receive packets of collector information?
I am now getting corrupted sFlow data packets.
It seems to me that with the wrong configuration I should not receive data at all!

Please correct me if I'm wrong.

Guid 
From page 1901 on the documentation below you will be able to check the Sflow configuration
https://mega.nz/file/BKtmUagC#nFT8NmrNKXA5ncVsO_rZmssVIfOcbolQb_ywmlfC7cQ

Screenshot


I am waiting for feedback on collectors for sFlow who uses which. Let's share)

Hi,

I'm not doubting your expertise on the configuration. Unfortunately, the company doesnot allow downloads from https://dell.to/3xii4PN. But if you need an analysis of any misses on your configurations, I would suggest contacting the network support to raise a case. We do not have any capability for configuration checking. 

Here are some simple steps for sFlow configuration, could you clear all configuration on sFlow and follow the steps? The steps are copied from an article requested from the network engineer that I sought advice from. 

Step01, Enable sFlow 

You can enable sFlow either on all interfaces (not recommended) globally or on a specific set of interfaces(better choice). 
sFlow® is disabled globally by default. 

Enable sFlow globally on all interfaces in CONFIGURATION mode.
OS10(config)# sflow enable ? 
  all-interfaces  Enables sflow globally for all interfaces
  <cr>    Enables sflow globally, but not specify interfaces
OS10(config)# sflow enable all-interfaces      ------// Don't set this, it's not best practice !!!! 

Suggest to make below setting : 
OS10(config)# sflow enable      ------// enable sflow feature globally, then set it to specific set of interfaces later ! 
 

Step02, Enable sFlow on interfaces 

OS10(config)# interface ethernet 1/1/1      ------// enable sflow on one specific single interface, 
OS10(conf-if-eth1/1/1)# sflow ? 
  enable  Enables ingress sflow in specific interface
OS10(conf-if-eth1/1/1)# sflow enable
OS10(conf-if-eth1/1/1)# 

OS10(config)# interface range ethernet 1/1/13-1/1/16      ------// enable sflow on one specific range interfaces, 
OS10(conf-range-eth1/1/10-1/1/16)# sflow enable
OS10(conf-range-eth1/1/10-1/1/16)#

OS10(config)# interface port-channel 10      ------// enable sflow on port-channel, 
OS10(conf-if-po-10)# sflow enable
OS10(conf-if-po-10)# 

 
 Step03, Set Max-header Size 

Set the packet maximum size in CONFIGURATION mode, from 64 to 256. 
The default is 128 bytes which is enough in most situation, you can set larger number if required. 

OS10(config)# sflow max-header-size ? 
  <64-256>  Header size (Default value = 128)      ------// value range 64-256, default is 128 seconds, 
OS10(config)# sflow max-header-size 256
OS10(config)#
 

Step04, Collector Configuration 

Configure the IPv4 or IPv6 address for the sFlow® collector. When you configure the collector, 
enter a valid and reachable IPv4 or IPv6 address. You can configure a maximum of two sFlow® collectors. 
If you specify two collectors, samples are sent to both. The agent IP address must be the same for both the collectors. 
If you configure a collector for a nondefault VRF, create the VRF first. 
If you do not specify the VRF instance, the system configures the collector for the default VRF instance. 

OS10(config)# sflow collector 172.16.100.1 agent-addr 192.168.100.1 ? 
  <1-65535>          Collector port number (Default port = 6343)
  max-datagram-size  Maximum datagram size
  vrf                VRF Instance
  <cr>
OS10(config)# sflow collector 172.16.100.1 agent-addr 192.168.100.1
 

Step05, Set sFlow Source Interface 

Do ping(collector) test as below : 
OS10# ping 172.16.100.1      ------// from switch ping collector, 
PING 172.16.100.1 (172.16.100.1) 56(84) bytes of data.
64 bytes from 172.16.100.1: icmp_seq=1 ttl=64 time=0.288 ms
64 bytes from 172.16.100.1: icmp_seq=2 ttl=64 time=0.292 ms
64 bytes from 172.16.100.1: icmp_seq=3 ttl=64 time=0.248 ms
^C
--- 172.16.100.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2009ms
rtt min/avg/max/mdev = 0.248/0.276/0.292/0.019 ms
OS10#

OS10# show lldp neighbors
Loc PortID          Rem Host Name        Rem Port Id                    Rem Chassis Id
--------------------------------------------------------------------------------------
ethernet1/1/54:1    Collector            ethernet1/1/54:1              3c:2c:30:22:87:80
OS10#

Collector# ping 192.168.100.1      ------// from collector ping switch, 
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data.
64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=0.293 ms
64 bytes from 192.168.100.1: icmp_seq=2 ttl=64 time=0.290 ms
64 bytes from 192.168.100.1: icmp_seq=3 ttl=64 time=0.285 ms
^C
--- 192.168.100.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2028ms
rtt min/avg/max/mdev = 0.285/0.289/0.293/0.014 ms
Collector#

OS10(config)# sflow source-interface ? 
  ethernet                 Ethernet interface type
  loopback                 Loopback interface type      ------// for best practice, should set loopback interface as the source, 
  port-channel             Port-channel interface type
  vlan                     Vlan interface type
OS10(config)# sflow source-interface loopback 0      ------// set local interface loopback 0 as the agent source, 

Notes : 
If you set physical interface as source, will lost the connection if physical interface down. 
If you set port-channel interface as source, will lost the connection if all member interfaces down. 
If you set vlan interface as source, will lost the connection if no active switchport in the vlan (down). 
But for loopback interface, it's always in "UP" status as long as you don't shutdown it manually. 
 

Step06, Set sFlow Polling-interval 

The polling interval for an interface is the number of seconds between successive samples of counters sent to the collector. You can configure the duration for polled interface statistics. Unless there is a specific deployment need to configure a lower polling interval value, configure the polling interval to the maximum value. 

OS10(config)# sflow polling-interval ? 
  <10-300>  Counter poll interval (Default value = 30)       ------// value range 10-300, default is 30 seconds, 
OS10(config)# sflow polling-interval 100
OS10(config)# 
 

Step07, Set sFlow Sample-rate 

Sampling rate is the number of packets skipped before the sample is taken. 
If the sampling rate is 4096, one sample generates for every 4096 packets observed. 

OS10(config)# sflow sample-rate ? 
  <4096-65535>  Sampling rate (Default value = 32768)
       ------// value range 4096-65535, default is 32768(means will take one packet from 32768 packets), 
OS10(config)# sflow sample-rate 4096
OS10(config)#