Thank you very much for your response.
This is informative. I do not know all of the details of how the VLANs are configured on the controller. This is my third month on the job and I am still trying to figure out how the network topology was constructed.
Here's what I can tell you.
We have a Staff Vlan: 10.0.0.0-Vlan 2
We have. Student Vlan 10.50.0.0-Vlan 50
We also have a guest VLan.
Default switchport configuration for all APs is
Administrative Mode: Trunk
Access: Vlan 2
Native Vlan Trunk: Vlan 50
All other APs are getting an IP from Vlan 50 on this configuration except the three that have gone down. All three are Aruba 205 APs.
For some reason, on the switchport, toggling administrative mode from trunk to access, assigning the access vlan to vlan 50 then toggling the settings back to trunk mode, and changing the access vlan back to vlan 2 brought two of the down APs back up. This has not worked on the remaining three down APs.
From what I understand, the APs should broadcast all three ssids regardless of the Vlan they receive an IP address from. We also have a guest Vlan and some of our APs are up on IPs from that VLAN!
I thought our management vlan was Vlan 2. I guess my question is why, all of the sudden, has the switchport configuration that works throughout the rest of our network (100+ APs) stopped working on just these three APs. Note: I have connected these APs to other switches and the issue still occurs.
Original Message:
Sent: Mar 20, 2021 05:24 AM
From: Shpat Berzati
Subject: 205 Access Points Not Receiving Proper IP Address from Trunk Port
As far as i get you right, what you have to do is the following:
1. Place the switch port where you connect the access point as Access and place the VLAN which you will use as "management" VLAN, lets say vlan 100, for the AP to communicatee with the Wireless Controller.
(usually you want to have this VLAN separated from the clients/subscribers VLAN who will want to use the Internet through the SSID)
2. Then you configure the SSID with multiple types of VLAN if you want (maybe each SSID have a different VLAN, or configure named VLAN where for a name, lets say staf-vlan you add vlan 10,20,30 and guest-vlan you add vlan 40,50,60)
(this works like QinQ)
So the Client will get IP Address from VLAN 10,20,30,40,50,60..... but the uplink will have only 1 vlan (VLAN 100).
------------------------------
Shpat
Original Message:
Sent: Mar 19, 2021 01:44 PM
From: Kevin Gulliver
Subject: 205 Access Points Not Receiving Proper IP Address from Trunk Port
I have a handful of 205 Access Points that suddenly stopped broadcasting on our default configuration. The devices power up and get an IP address, but it is not from the tagged or native vlan that has been set on the trunk port. If I place the port into access mode the AP comes online but does not broadcast all the vlans we need it too--only the access mode vlan.
When I plug my computer into the same cable, I receive an IP from the correct vlan.
When I connect the AP to the console and break the boot sequence and run dchp. The ap gets an ip from the correct vlan. But when I reboot the AP it reverts back to the IP from the vlan that will not bring the AP up.
Previously we ran APs on IPs from multiple vlans but all the down APs show on up one vlan and that is the vlan down APs are reverting to for an IP address.
Thought this might be a switchport issue but after this troubleshooting I'm inclined to think it is an issue happening with the APs.
APs come up on our 10.50 vlan (tunnel)
APs are not coming up on our 10.0 vlan (bridge)
Thanks for any thoughts