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
Hi,So what you have to do is the following:Default switchport configuration for all APs isAdministrative Mode: AccessAccess: Vlan 50 (though i would suggest you to change this VLAN to another VLAN since Students use this VLAN).On the controller you have to configure VLAN2,50,XYZ (XYZ - VLANID for the Guest).Then you go on each SSID Profiles and configure each VLAN on the SSID Part.Staff SSID: VLAN 2Student SSID: VLAN 50Guest SSID: VLAN XYZDepending which ArubaOS you are using (if Aruba OS6.x or Aruba OS8.x) there are different paths/ways to configure the SSID having VLANs.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.