cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
952
Views
0
Helpful
5
Replies

Configure CAP_WAP1602 with dynamic vlan and multiple SSID on WLC 8.0.120

gerards
Level 1
Level 1

I am trying to get a CAp-WAP1602 configured with dynamic vlan on a WLC 8.0

The dynamic vlan is allocation is handled by a microsoft Network Policy server that is running Radius

 

Are there any manuals on how this should be accomplished (complete configuration of the WLC & AP )

 

Kind Regards

Gerard

5 Replies 5

My Radius server is configured in the same manner as in this procedure for the dynamic vlan feature (because it works with other equipement).

 

The adviced cisco procedure for the WLC i tried to follow leaves me with a cap-wap1602 that (after a factory reset) a clean config according to this procedure does not broadcast any SSID i configure.

Can you/anybody advise what i might do wrong?

The AP is in Local mode (not flex connect) because i understand this provides the 2 tunnels to the WLC i need for mgmt & userdata.

 

Kind Regards

Gerard

When an AP doesn’t broadcast WLANs that are defined in the controller is usually due to the AP’s being in the wrong AP Group. If using wlan id 1-16, then all the WLANs will be broadcasted in the default AP Group. If using wlan id 17+, then you need to create an AP Group, assign the WLANs you want in that group and add the AP’s to that group in order to have the SSID available to be used on the AP’s.
-Scott
*** Please rate helpful posts ***

Seems that the solution for the SSID is setting the AP in Flexconnect mode instead of LOcal mode, however when a client log's on to th AP ity doesn't get an ipaddress from the correct vlan.

 

Any idea's on which setting in the WLC i should check?

 

Kind Regards

Gerard

Well I think there are a few things or maybe I’m confused with what you are asking. If the SSID is defined to broadcast and devices don’t see that SSID, then it’s something with AP groups. If you are trying to assign a vlan from radius, and the vlan the device is being placed on is wrong, then it’s either the radius policy not defined to send the proper interface name or the device failed to auth.
-Scott
*** Please rate helpful posts ***
Review Cisco Networking for a $25 gift card