Page 2 of 2

Re: NNA on AWS

Posted: Thu Aug 06, 2015 8:19 am
by eloyd
Use tcpdump on the client to see if it's actually sending data:

Code: Select all

tcpdump host <ip of NNA server>

Re: NNA on AWS

Posted: Thu Aug 06, 2015 11:25 am
by jdalrymple
It may also be worth your while to yum update the Cent7 box if you haven't already. There were some weird IPv6 --> IPv4 listener translation mumbo jumbos happening that didn't work properly in earlier versions of Cent7. Updating to the newest kernel fixes these in my experience.

Re: NNA on AWS

Posted: Tue Aug 11, 2015 5:50 pm
by pchua
Hi all,

Just to give an update.

After trying to update CentOS to latest version and trying to check other things, I finally figured out how to make it work. fprobe wasn't running at all before, and I needed to include -n option and choose the newest version instead of the default (5).

Code: Select all

fprobe -i eth0 -n7 10.0.0.44:49152
After doing this I was able to verify that fprobe was running under ps aux and after a few minutes I can finally see the graph.

Thanks a lot for everyone's suggestions! Took me a couple of days but finally got it to work.

Re: NNA on AWS

Posted: Tue Aug 11, 2015 7:06 pm
by eloyd
I've never seen that required before. Glad it's working though.

Re: NNA on AWS

Posted: Wed Aug 12, 2015 9:38 am
by hsmith
pchua wrote:Hi all,

Just to give an update.

After trying to update CentOS to latest version and trying to check other things, I finally figured out how to make it work. fprobe wasn't running at all before, and I needed to include -n option and choose the newest version instead of the default (5).

Code: Select all

fprobe -i eth0 -n7 10.0.0.44:49152
After doing this I was able to verify that fprobe was running under ps aux and after a few minutes I can finally see the graph.

Thanks a lot for everyone's suggestions! Took me a couple of days but finally got it to work.
Glad to hear it worked!

I'm going to close this topic, thanks for the update.