09-22-2018 09:17 AM - edited 07-05-2021 09:12 AM
Hello. I'm having a little problem configuring/discovering 12 ap's 1815i with mobility express. The scenario is the following: the controller ap has an ip for management and a single ssid that is on a different network and vlan from the management network . Vlan 13 (management) is native on the controller ap and the ssid/service vlan 10 is tagged. No guest vlan. All switch ports that connect to ap's are configured with: switchport mode trunk switchport trunk native vlan 13 switchport trunk allowed vlan 10, 13 There is no dhcp server for vlan 13. But there is an external dhcp server for vlan 10. I can connect to the ssid on the controller ap and have internet, but the other ap's don't connect/provision to the controller ap. My question is: since there is no dhcp server for the network on vlan13 (all switches and router have static management vlan 13 ip's configured) is it mandatory to have a dhcp server for the management network, or is there any other way for the other ap's to connect/provision with the controller ap? And if the management network dhcp server is a must for this to work do you advise it to be configured on the controller ap or on another network node (for instance the router)? all ap's have correct mobility express firmware. Thanks.
09-22-2018 11:35 AM
In my humble opinion, If you have 12 APs, you can config static IP for them.( no mandatory to set up DHCP server )
You should check both the Wired network setting and Wireless setting. (for example: config "int vlan 13", ping test to controller & dhcp, Mobility Express software for your AP.... )
By the way, setting native for management vlan is not a good idea.
Hope this help.
09-22-2018 02:04 PM
09-22-2018 07:39 PM
09-23-2018 01:01 AM - edited 09-23-2018 01:02 AM
I'm using mobility express. thanks for your help but i already have taken a look at these documents. And it didn't helped much.
honestly, i'm a little disappointed with these solution. i think ubiquiti has a much affordable and better solution for these kind of market segment. also the support is much better; you have tons of videos with several different configs. the videos and tutorials for the ME that are on the internet are all for the same kind of scenario: management network is the same network as the employee ssid. and always showing just the controller wizard part (airprovision). desapointing. thanks anyway.
09-23-2018 02:17 AM
09-23-2018 03:43 AM - edited 09-23-2018 03:59 AM
hello, again. and thanks for your patience and availability.
my main problem is with the provisioning and discovery of the subordinated ap's, since i don't have a dhcp server for the management vlan (and unfortunately i'm not supposed to have one!) how can the ap's be discovered? it's enough to have them be discovered on the wlan1/vlan 10 network? they don't have to be discovered on the management network/vlan 13, because only the controller function from ME has to be on management network/vlan 13??
As i said the switch ports are configured this way:
switchport mode trunk
switchport trunk native vlan 13
switchport trunk allowed vlan 10, 13
The Controller ap was configured with:
management ip 126.96.36.199/27 (since the router is 188.8.131.52; switch #1 184.108.40.206; switch #2 220.127.116.11; switch #3 18.104.22.168 - all with static ip (no dhcp pool));
(employee) wlan 1 with vlan 10 tagged;
Now, how can i put static ip adresses (from the management network 22.214.171.124/27) on the ap's if they don't get provisioned on the controller (since they dont gain ip on vlan 13 because there's no dhcp available).
i only see 2 options:
either i configure a dhcp server for management network/vlan 13, on the controller or on the router;
or the ap's will be provisioned on a different network from the management ( wlan 1 network 192.168.1.0 - vlan 10) ???
I think option 2 will work since only the controller function will be on management vlan/network!?!? all the ap's will be on wlan 1 network/vlan10, and get provisioned on it; but would't there be a problem if the controller ap get's "broken" and another one as to assume the controller role?
can you tell me if option 2 will work? unfortunately can only test tomorrow. can you help me?? thanks again
09-23-2018 06:10 AM
09-23-2018 06:38 AM
09-23-2018 07:27 AM - edited 09-23-2018 07:43 AM
Hi. but if the gateway for the 2 different vlan/networks (126.96.36.199 and 192.168.1.0) is the same node/router, and this router has in it's routing table a directly connected route, one for each network. shouldn't there be an entry on it's arp table for the controller on subnet 188.8.131.52 and shoudn't ap's on network 192.168.1.0 be able to reach the controller thanks to it's gateway that has the 2 networks directly connected??
the ap's are all running mobility express image, will the lwapp commands will also apply to this image?
if so, since all ap´s are on the same vlan i just need to connect via console port to each one and:
AP# lwapp ap ip address <IP address> <subnet mask>
AP# lwapp ip default-gateway IP-address
this way i will setup a static ip address for each one of them enabling them to be on the same subnet as the controller and to provision to the controller ap?
09-23-2018 08:22 AM
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: