Purview Colector Wireless

[Luis_Mendes]

Purview colector doesn´t shows de comunication. But the servers receive the mirror of controller

[AG1]

We have worked with Luis Mendes on this issue and it have found that he will have to setup one of the available physical interfaces (esa0-3) to be used as the source interface for the netflow traffic. The end user has been using the admin interface which we have identified to be the root cause. The Admin interface, we have learned, does not show netflow traffic.

[Ronald_Dvorak]

I'd reboot Purview and if it still doesn't work call the GTAC for a remote session.

[Luis_Mendes]

Ronald

I read the article. I have an lab with V2110 and the same configuration. On my lab purview works fine. But on the customer not populate.

root@purview:~$ tcpdump -i eth0 udp port 2095 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
19:07:22.052542 IP 10.72.0.2.55843 > purview..2095: UDP, length 1372
19:07:22.052577 IP 10.72.0.2.55843 > purview..2095: UDP, length 1372
19:07:23.052569 IP 10.72.0.2.55843 > purview..2095: UDP, length 1368
19:07:24.052552 IP 10.72.0.2.55843 > purview..2095: UDP, length 1296
19:07:25.052544 IP 10.72.0.2.55843 > purview..2095: UDP, length 1296
19:07:25.052584 IP 10.72.0.2.55843 > purview..2095: UDP, length 1372

tcpdump -i eth1 (show traffic)
tcpdump -i lo udp port 9191 (show traffic)

root@purview:~$ appidctl status** Purview Version 6.3.0.162 **
process status restarts pid start time
appid start/running 0 31622 Mon Oct 5 17:32:52 2015
appidserver start/running 0 31618 Mon Oct 5 17:32:52 2015
root@purview:~$

[Ronald_Dvorak]

Yes, from the screenshot you've provided we'd see that Purview is receiving the mirror data BUT didn't get any Netflow data (as far as I unterstand that output).

What AP models are used ?
Could you ping the Purview IP 172.16.0.136 from the controller ?

[Luis_Mendes]

Yes.. All Aps are 3715i
The Netsight have a ip 172.16.0.138
Purview has 172.16.0.136 and Controller has 172.16.0.130

The interface esa1 has connect directly to another port of Purview appliance (eth1) And receive traffic