• November 26, 2020, 03:51:13 PM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: Active/Active Cluster, Captive Portal, Internal DHCP & Public DNS only  (Read 2766 times)

0 Members and 1 Guest are viewing this topic.

Offline mcat84

  • Rookie
  • **
  • Posts: 1
First time with all these RFS7000 and AP650 and very confused.....

My lab setup (before go live to production)...
1. RFS7000 x 2units running in active/active cluster (v5.4.4)
2. Internal DHCP (for wlan ABC)
3. (SSID ABC, multiple vlans) and (SSID XYZ, single vlan)
4. Internal Captive Portal/Radius (for wlan ABC)

My questions:
1. In active/active cluster, can we specify the AP adoption by controller ? i.e. AP1,2,3 go to controller A and AP4,5,6 go to controller B ..

2. In captive portal environment(active/active cluster), i notice that the wireless client ip gateway must be point to the controller (vlans) for the captive portal to intercept...is this the correct way to do it? (Since i have multiple VLAN for single SSID, that's mean i have to setup multiple VRRP ?????)

3. For Captive Portal "Centralized Controller" deployment which using "virtual hostname", since i have only public DNS, how to go about it ?  (currently i am using Centralized ip address method + VRRP)

If i setup a Internal DNS, how to resolve this "virtual hostname" ? which ip should i point to ? should i setup VRRP and point to the VRRP virtual ip ?

Final question,
For L2 AP adoption, is it important for the AP650 to have an IP address? All my AP650 don't have ip addresses assign ? what is the purposes to assign an ip address to the AP ?

Hope someone can help.. thanks in advance.

Offline Fido

  • Rookie
  • **
  • Posts: 20
Re: Active/Active Cluster, Captive Portal, Internal DHCP & Public DNS only
« Reply #1 on: October 05, 2013, 04:29:40 AM »
Here is my opinion (which might not be 100%), based on my understanding of your questions (which might not be 100%)

1. Since you are on L2 adoption, not really. You can put each controller in a "controller group" and then assign each AP to a "preferred controller group". This way the AP will prefer a controller, but is not guaranteed to be adopted by it.

2. No, wireless client gateway must point to the actual gateway. Gateway may or may not be your RFS. RFS or AP will intercept the http session as it is in line with the connection.

3. DNS should probably not be involved here. The controller name is configured under device config, then the name is referenced in the captive portal policy.

4. If you are using L2 adoption then you do not need IP addresses. The only reason you might want IP on the APs is if you want to monitor them via some kind of ICMP tool.

I hope this can help.