I can't seem to make 3rd Party AP work.

[Rahman_Duran1]

Hi,

We have 15 aruba IAP devices which I want to use them as 3. party AP on C5210 controller to utilize internal captive portal.

I hook up the esa1 port to the swich and set the vlan tagging. Then I created a wlan on aruba and set it to vlan 60 tagged. Configured all the switches to pass vlan 60 so it can reach controller. I also created a dhcp pool on our dhcp server and configured it so vlan 60 clients use EWC interface ip (10.100.60.2) as their gateway.

So, I tried to connect to aruba but I can't seem to get ip address and connect to wlan. So what is wrong with my setup? Any hint on this is mostly wellcome.

Thanks,

Rahman

[Rahman_Duran1]

So after trying lots of thing I can't even ping EWC 3. party interface ip. I changed topology to vlan 60 untagged. Then get a laptop, gave it 10.100.60.100/24 and plugged it directly to esa1. But I could not ping esa1 ip (10.100.60.2). I plugged laptor to the same switch with esa1, in a port of vlan 60 untagged, can't ping 10.100.60.2 either.

If any of you has a working setup, can you share screenshots of
Virtual Networks
WLAN Services
Roles
Topologies sections of 3rd party service?

Thanks,

Rahman

[Jason1]

Rahman,

This article should help with getting the captive portal to work with the 3rd party AP's. There needs to be a change to allow out-of-network traffic to bypass that rule.

https://gtacknowledge.extremenetworks.com/articles/Solution/IdentiFi-3rd-Party-VNS-not-working-with-...

Thanks,
Jason

[Rahman_Duran1]

Ronald,

EWC's default routing interface is on esa0 (192.168.10.122). So I need to write a static route like this; 10.100.60.0/24 192.168.10.122 ?

>BTW, why are the APs in network 172.16.64.x and not 10.100.60.x ?

Because these aruba devices also broadcast eduroam(802.1x) WLAN and it is on 172.xxx.xxx.xxx subnet. CP WLAN is tagged as vlan 60 so it is a seperate network even the ap's management network subnet is different.

[Ronald_Dvorak]

Correct, you add the route to the router in the 192.168.10.x network and then you should be able to ping from the DHCP server to 10.100.60.2 and vice versa.

[Andre_Brits_Kan]

What Ronald said 