setup issue - no data available on switch (source)

This support forum board is for support questions relating to Nagios Network Analyzer, our network traffic and bandwidth analysis solution.
Locked
Vextor
Posts: 4
Joined: Thu Oct 31, 2013 12:16 pm

setup issue - no data available on switch (source)

Post by Vextor »

Greetings, my company just bought NA and XI.

And I am having a bit of trouble getting Nagios NA setup.
running Nagios Network Analyzer • 2014R1.1
system is in test mode running in a VMware player

I enabled sFlow on my dell switch using the instructions at the following link:
http://blog.sflow.com/2010/02/configuri ... tches.html

when i go to the switch on NA (under source) i see
status = running
Traffic last 30 minutes = no data
flow type = sFlow

any ideas?

Thanks
Alex
slansing
Posts: 7698
Joined: Mon Apr 23, 2012 4:28 pm
Location: Travelling through time and space...

Re: setup issue - no data available on switch (source)

Post by slansing »

Sure, lets start by tcpdumping all incoming connections from your switch's address, on the NNA server:

Code: Select all

tcpdump host <address of switch> and port <unique port that flow data is coming through>
Is traffic hitting NNA?
Vextor
Posts: 4
Joined: Thu Oct 31, 2013 12:16 pm

Re: setup issue - no data available on switch (source)

Post by Vextor »

maybe my 10 year gap of working with linux is showing but
it doesnt look like tcpdump is installed on the na box??

[root@nagios-na /]# whereis tcpdump
tcpdump:
slansing
Posts: 7698
Joined: Mon Apr 23, 2012 4:28 pm
Location: Travelling through time and space...

Re: setup issue - no data available on switch (source)

Post by slansing »

I do not believe so, it does not look like it. You will need to:

yum install tcpdump
Vextor
Posts: 4
Joined: Thu Oct 31, 2013 12:16 pm

Re: setup issue - no data available on switch (source)

Post by Vextor »

oops posted in the wrong forums HAHAHA (don't worry, i deleted it)

here you are
FYI 40.5 is the switch, and 40.107 is the NA VM

I am getting the following:

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
16:31:15.317581 IP 10.10.40.5.sflow > 10.10.40.107.9055: sFlowv5, IPv4 agent 10.10.40.5, agent-id 1, length 170
16:31:25.317747 IP 10.10.40.5.sflow > 10.10.40.107.9055: sFlowv5, IPv4 agent 10.10.40.5, agent-id 1, length 156
16:31:30.317944 IP 10.10.40.5.sflow > 10.10.40.107.9055: sFlowv5, IPv4 agent 10.10.40.5, agent-id 1, length 170
16:31:34.317908 IP 10.10.40.5.sflow > 10.10.40.107.9055: sFlowv5, IPv4 agent 10.10.40.5, agent-id 1, length 204
16:31:37.317803 IP 10.10.40.5.sflow > 10.10.40.107.9055: sFlowv5, IPv4 agent 10.10.40.5, agent-id 1, length 156
16:31:40.317812 IP 10.10.40.5.sflow > 10.10.40.107.9055: sFlowv5, IPv4 agent 10.10.40.5, agent-id 1, length 170
16:31:43.317834 IP 10.10.40.5.sflow > 10.10.40.107.9055: sFlowv5, IPv4 agent 10.10.40.5, agent-id 1, length 156
16:31:44.317917 IP 10.10.40.5.sflow > 10.10.40.107.9055: sFlowv5, IPv4 agent 10.10.40.5, agent-id 1, length 156
16:31:52.317933 IP 10.10.40.5.sflow > 10.10.40.107.9055: sFlowv5, IPv4 agent 10.10.40.5, agent-id 1, length 220
16:31:55.318085 IP 10.10.40.5.sflow > 10.10.40.107.9055: sFlowv5, IPv4 agent 10.10.40.5, agent-id 1, length 220
16:31:56.318038 IP 10.10.40.5.sflow > 10.10.40.107.9055: sFlowv5, IPv4 agent 10.10.40.5, agent-id 1, length 220
16:31:58.318002 IP 10.10.40.5.sflow > 10.10.40.107.9055: sFlowv5, IPv4 agent 10.10.40.5, agent-id 1, length 220
16:31:59.318122 IP 10.10.40.5.sflow > 10.10.40.107.9055: sFlowv5, IPv4 agent 10.10.40.5, agent-id 1, length 220
16:32:00.318105 IP 10.10.40.5.sflow > 10.10.40.107.9055: sFlowv5, IPv4 agent 10.10.40.5, agent-id 3, length 604
16:32:01.317996 IP 10.10.40.5.sflow > 10.10.40.107.9055: sFlowv5, IPv4 agent 10.10.40.5, agent-id 1, length 220
16:32:02.318044 IP 10.10.40.5.sflow > 10.10.40.107.9055: sFlowv5, IPv4 agent 10.10.40.5, agent-id 2, length 412
16:32:03.318125 IP 10.10.40.5.sflow > 10.10.40.107.9055: sFlowv5, IPv4 agent 10.10.40.5, agent-id 1, length 162
^C
17 packets captured
26 packets received by filter
0 packets dropped by kernel
slansing
Posts: 7698
Joined: Mon Apr 23, 2012 4:28 pm
Location: Travelling through time and space...

Re: setup issue - no data available on switch (source)

Post by slansing »

Hmm and that sflow traffic is coming from switch? Did you set the correct port on your source in NNA? Would you be willing to open a ticket? You can email nasupport@nagios.com :)
Vextor
Posts: 4
Joined: Thu Oct 31, 2013 12:16 pm

Re: setup issue - no data available on switch (source)

Post by Vextor »

yes 10.10.40.5, yes 9055 (i had 2055 before and it didnt work either), yes, and done.
slansing
Posts: 7698
Joined: Mon Apr 23, 2012 4:28 pm
Location: Travelling through time and space...

Re: setup issue - no data available on switch (source)

Post by slansing »

Lets move this to a ticket I sent you a PM with the address to email. Moving this to customer support section.
Locked