03-29-2017 12:30 PM
I have been installing a IAP and I wasn't be able to reach the Instant UI. The scenario was like this:
When I changed the AP to another switch with the port in access mode and DHCP server enabled, then I was able to reach the Instant UI.
What was the problem with the first scenario as illustrated above?
03-29-2017 01:45 PM - edited 03-29-2017 01:47 PM
What is your native VLAN set to and is the IAP able to pick up a DHCP IP address in this VLAN? So for example, if you have VLAN's 10, 20 and 30. The IAP managment sits on VLAN 10, this would be your native VLAN (untagged) and VLAN's 20, 30 would be the tagged VLAN's on your trunk.
If my post addresses your query, give kudos:)
03-29-2017 01:57 PM
The IAP is new, I took it from the box. I wasn't be able to reach the GUI in my first scenario (with trunks). When I changed to a switchport in access mode and DHCP enabled, I got the GUI, then I saw its uplink management VLAN is 0. As I told you, the IAP is completely new with factory configuration. Then what was the problem with the first scenario to reach the GUI?
03-30-2017 08:14 AM
1. Uplink management vlan is 0 by default.
When you connected the IAP to trunk port, it will send untagged packets by default. So, we expect it to get an IP address on the native vlan defined on the trunk port.
As you have mentioned you were unable to access the IAP's UI i scenario 1, please provide the following information:
1. Was the IAP getting an IP address?
In case it was unable to get an IP address, probably there is no DHCP scope for native vlan.
2. Did you try connecting wireless client to the factory SSID "instant" & tried accessing the Web UI?
03-30-2017 08:34 AM - edited 03-30-2017 08:46 AM
The IAP didn't get an IAP address and I think because the native VLAN is not allowed on the trunk.
And I tried to connect a client to the SSID instant and access the WebUI but I couldn't.
Is this because the IAP needs a valid IP address (not 169.254 subnet) in order to have access to the WebUI?
03-30-2017 08:56 AM
Please share the firmware version running on the IAP.
Did your client get the IP address from 172.x.x.x scope when connected to instat ssid ?
Did you try accessing the WebUI from a device which was only connected to wireless ?
I can test it in lab tomorrow once I am in office.
03-30-2017 10:35 AM
I have just tested this issue at office. I factory reseted an IAP 305 with firmware 18.104.22.168-22.214.171.124. I have powered it up by a kit power, without connecting the Eth uplink port.
1 - The IAP boots and the power LED starts flashing, after a while the radio LED starts flashing and the instant SSID appears.
2 - Both LEDs keep flashing (no one steady), I can't connect to the instant SSID (it lasts a lot and finally is connected like "without internet"), if I try to reach the WebUI I can't.
3 - After a while, the radio LED turns off and the instant SSID dissapears.
4 - IAP starts again in step 1.
After this, I powered off the IAP and powered it up again, this time I connected the Eth uplink to a LAN with DHCP server enabled. After a while, the power LED is on (without flashing) and the radio LED flashes. I can connect to the instant SSID and I can reach the WebUI successfully.
So it seems when the IAP is not connected to a DHCP server it can't get a valid IP and then the instant SSID doesn't properly work (in fact, the IAP boots from step 1 to 4 again and again), then users can't reach the WebUI. It seems for things work properly, the IAP needs to get a valid IP address.
03-30-2017 10:52 AM
After I powered up the IAP with its uplink connected to the LAN with DCHP server enabled, I was able to reach the GUI as I told you. I have configured the IAP and I ran the command "AP version", I got this message:
It says that the last IAP reboot was because before the Eth uplink was down (when I powered up the IAP without connecting the Eth uplink at the beginning as I stated in my last post).
So it seems the IAP needs to have both the Eth uplink connected and to get a valid IP address to work properly.