Unsolved
This post is more than 5 years old
11 Posts
0
2093
Configure sflow on s60 switch!!
We've configured sflow on s60 switch but somehow its dropping all of the traffic Here is the guide we used to configure it :
http://blog.sflow.com/2009/07/configuring-force10-switches.html
Here is the screenshot of sflow configuration on sw :
- The agent ip is the one configured on management port.
- The collector server is configured on nfsen/nfdump using 6343 udp port.
If anyone can point us to right direction that'd be very helpful. Here is the URL to access nfsen :
Thanks!!
shahzaibcb
11 Posts
0
May 3rd, 2016 09:00
Thanks for the response. Yes it looks like switch is dropping all the packets and they are unable to reach the collector, so yes collector is not receiving any traffic at all. Here you can see the 'udp packets drop' value keeps on increase after each polling interval.
http://prntscr.com/azsy75
FTOS version : http://prntscr.com/azsz3z
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
May 3rd, 2016 09:00
The internal filters we have are preventing me from accessing those URLs. Can you please copy and paste the config here on the forums. You can click "use rick format" to be able to upload media to the forum.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
May 3rd, 2016 09:00
What FTOS version is the switch on? This may change some of the available commands.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
May 3rd, 2016 09:00
I am not able to view that config. Can you please paste the config here on the forums? What do you mean by it is dropping all traffic? The collecting server is not receiving any traffic at all? Or the collecting server is receiving all traffic and not just the sample packets? From the graphs it doesn't look like it is receiving any packets at all.
What does the output from # show sflow, look like?
shahzaibcb
11 Posts
0
May 3rd, 2016 10:00
Oh sorry for misunderstanding. I am attaching output here.
1 Attachment
sflow.txt
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
May 3rd, 2016 11:00
Thanks for getting that to us. It looks like the UDP packets are not being exported, and are instead being dropped.
0 UDP packets exported
956794 UDP packets dropped
Can you please get the running config posted up, or even the # show tech, which would provide us with even more information to look through. Feel free to redact any sensitive information. Along with info on what port the collector is plugged into? Hopefully we can help look through things and offer some suggestions.
shahzaibcb
11 Posts
0
May 4th, 2016 00:00
Thanks for help Daniel. Could you please let me know if there's some 'redirect output to file' supported in switch? As the #show tech contains really long output which looks difficult to copy / paste on external media.
>> Along with info on what port the collector is plugged into?
Actually, we've total of two switches SW1 and SW2. Some of the servers are connected behind SW1 and some of behind SW2. In our case, we're exporting sflow data of SW2 and the collector is physically connected behind SW1 but both agent / collector are able to ping each other. Should this work ? Or we must connect collector to SW2 to fetch sflow data ?
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
May 4th, 2016 06:00
Easiest method is to have the session output saved to a log.
http://bit.ly/1Oe1IVp
The collector should be fine on a different switch. The collector responds to pings from switch 1, right? It would not hurt to test plugging the collector into switch 1.
shahzaibcb
11 Posts
0
May 5th, 2016 01:00
Thanks for great suggestion.
1 Attachment
tech.log
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
May 5th, 2016 13:00
Nothing in the config is jumping out at me. Were you able to move the collector tot he same switch as the source?
shahzaibcb
11 Posts
0
May 13th, 2016 01:00
Sorry for late response! Still everything is in dropped state. Should i move collector to same switch then ?
shahzaibcb
11 Posts
0
May 13th, 2016 04:00
I've configured collector on same switch but error still persists. :-(