Finally, hard work paid off.
I was troubleshooting with wireshark and could observe receiving NetFlow
data (cflow) on the collector VM. Also, observed that the port 2055 was
giving "destination unreachable (port unreachable)" error.
I changed the NetFlow port to 2100 on openvswitch but then didn'
Yes, that's how UDP works.
On Fri, May 20, 2016 at 05:40:34PM +0200, Syed Faraz Ali wrote:
> The connection is established even when the other machine is offline. Is it
> still normal?
>
> # netstat -an | grep 2055
> udp0 0 192.168.56.104:49403192.168.56.103:2055
> ESTABLISHED
>
The connection is established even when the other machine is offline. Is it
still normal?
# netstat -an | grep 2055
udp0 0 192.168.56.104:49403192.168.56.103:2055
ESTABLISHED
# ping 192.168.56.103
PING 192.168.56.103 (192.168.56.103) 56(84) bytes of data.
>From 192.168.56.104 icm
It seems OK.
When I use a similar configuration, I see an appropriate line in
"netstat -an" output:
udp0 0 192.168.42.143:52897192.168.56.103:2055 ESTABLISHED
Do you get anything like that?
On Fri, May 20, 2016 at 05:11:07PM +0200, Syed Faraz Ali wrote:
> >OVS isn't even op
On Fri, May 20, 2016 at 12:50:13PM +0200, Syed Faraz Ali wrote:
> > It's probably easier to debug if you only enable NetFlow for now.
>
> Only NetFlow has been enabled.
>
> > Next, I'd use "strace" to see whether ovs-vswitchd is really trying to
> > send data to the collector. It would be using
Please don't drop the mailing list.
On Thu, May 19, 2016 at 09:02:41PM +0200, Syed Faraz Ali wrote:
> The packets are being collected on the sFlow port 6343 at the same time,
> but giving unreachable error for NetFlow. This looks pretty awkward!
> Do you have some suggestions to further look into
I setup two fresh VMs assuming that something might be blocking, but still
I'm getting the same logs.
I'm also not getting any output on tcpdump for NetFlow port 2055. I've
tried with changing the port as well.
Please suggest how to proceed?
2016-05-19T19:51:13.874Z|00263|sflow|INFO|creating sFlo
Hello Ben,
Thanks for the prompt responses!
The packets are being collected on the sFlow port 6343 at the same time,
but giving unreachable error for NetFlow. This looks pretty awkward!
Do you have some suggestions to further look into this matter?
To tell you more about the setup, I'm using POX
On Thu, May 19, 2016 at 06:17:45PM +0200, Syed Faraz Ali wrote:
> Hello Ben,
>
> Thanks for the prompt response.
>
> Please have the output from the logs. Below are the logs related to
> collector, I'm not sure if its related to NetFlow collector or used in some
> other context. Kindly suggest fu
Hello Ben,
Thanks for the prompt response.
Please have the output from the logs. Below are the logs related to
collector, I'm not sure if its related to NetFlow collector or used in some
other context. Kindly suggest further.
*cat /var/log/openvswitch/ovs-vswitchd.log | grep collector*
2016-05-1
On Thu, May 19, 2016 at 05:08:40PM +0200, Syed Faraz Ali wrote:
> I've configured NetFlow on the openvswitch, but I'm not getting any output
> on the collector machine. I've checked using tcpdump and Wireshark on the
> collector machine but couldn't observe any NetFlow related traffic.
>
> *Enable
Hello Support,
I've configured NetFlow on the openvswitch, but I'm not getting any output
on the collector machine. I've checked using tcpdump and Wireshark on the
collector machine but couldn't observe any NetFlow related traffic.
*Enabled NetFlow*
sudo ovs-vsctl -- set Bridge s1 netflow=@nf --
12 matches
Mail list logo
