Purview Integration Wireless Controller 9.21

[Michael_Kirchne]

Hi community,

has anyone integrated the wireless solution V 9.21 into Purview? I get the TopN Mirror up and running but I don't get netflow packets.

Netflow is configured in the section "VNS->Global->NetflowMirrorN"
There I configured the Mgmt IP of my Purview instance and choose esa1 as my L2 Mirror Port.

Any idea?

Best Regards
Michael

[Luis_Mendes]

Yes

I choose plug controller direct to the VM (C5210). If you call "tcpdump" the traffic exist and statitisc of purview appears. I have the same scenario but with traffic untagged and purivew show the traffic and informations. But with Tagged, no show

any Idea?

[Ronald_Dvorak]

- is the link to the VM server a trunk and all VLANs are allowed ?
- is the VM vswitch set to promiscuous mode and VLAN ID set to "all" so all VLANs are forwarded ?

I've choosen the "easy" way and use a dedicated NIC on my VM which I've directly connected to my WLAN controller mirror port which works great.

[Luis_Mendes]

Hi

When i use TAGGED on any ESA the traffic don´t appear on Purview, if the interface outside configured was untagged the purview show the connections, if tagged packets the purview count but not appear on dashboard. Any idea??

[Paulo_Francisco]

Hi Ron,

It depends on the direction of the traffic:

1) Traffic to the MU (NET to MU) if carrying a VLAN tag when received at the Appliance/AP will be mirrored as is (With VLAN tag)

Traffic from the MU (MU to NET) will always be mirrored as received from the wireless (post 802.3) which does not include the VLAN tag.

2) It depends on the topology configuration. For Bridged@Controller topologies all traffic is relayed back to the controller for N-Mirroring filtering and NetFlow metrics. Note: if mirroring applicable (Rule, Role or Service) the AP will still mirror back all traffic that is 'denied' by a Filtering@AP (controller will discard from the VLAN any such traffic, but will still mirror on Purview)

For Bridged@AP topologies, the AP will mirror only up to the first N-frames of a flow. Note2: AP will mirror up to N-Frames of any flow even if "Denied' by filtering at AP (so that Purview has complete view of all traffic intended to/by the user)

Paulo

[Paulo_Francisco]

Hi Ron,

The definition in the WLAN Service will work as the catch-all policy. Policy has precedence.

So in your example, if you want to capture all the traffic on the service except specific roles, simply set the service to 'Enable' - both directions recommended to get by-directional view of the traffic.

For any Roles you want to exclude, simply set their default action Traffic Mirror to 'Prohibited'.

If you have both Role and Service set to Enable, then there's no discrepancy and any traffic from that role on that service is N-Mirrored.

Paulo