10-10-2016 01:17 AM - edited 07-05-2021 05:56 AM
Hi , I am facing a problem with my cisco 2500 series WLC.
i have a ssid which named office-group on the wlc. and this ssid have 2 vlans on it, so i made a interface-group which contain vlan5 and vlan8.
and i have a DHCP server on C3750, and made some DHCP ip reserved on vlan5 pool.(some laptop address).
but sometime i can't get the correct IP address which i reserved. finnaly i found i connected on vlan8 which i did not make the reserved.
can / how i specific a laptop force it to connect vlan5 ?
can / how i set the interface priority on interface-group? (that make wireless device can connect vlan5 priority) ----maybe this is not a good idea....
can / how i set the DHCP IP reserved on WLC?
or do you have a better idea ???
so many thanks!!!!
Solved! Go to Solution.
10-10-2016 08:21 PM
I do not think you can, as long as you use interface group then there is possibility WLC decide that mac address need to go vlan 8 (or any other vlan in that group), in that case end device may not get vlan 5 IP even though you have reserved it.
If there is a feasibility to give static IP to end device and allow static IP on your WLAN, that may be an option for you.
HTH
Rasika
*** Pls rate all useful responses ***
10-10-2016 12:18 PM
If you use interface group, it will use round robing #algorithm to assign IP. So it is difficult to assign reserve IP when it use interface group.
Best solution would be increase your subnet size to cater the number of devices you got in wireless.
HTH
Rasika
*** Pls rate all useful responses ****
10-10-2016 06:24 PM
can i specific a MAC address and force it to connect vlan5 ?
10-10-2016 08:21 PM
I do not think you can, as long as you use interface group then there is possibility WLC decide that mac address need to go vlan 8 (or any other vlan in that group), in that case end device may not get vlan 5 IP even though you have reserved it.
If there is a feasibility to give static IP to end device and allow static IP on your WLAN, that may be an option for you.
HTH
Rasika
*** Pls rate all useful responses ***
10-13-2016 07:56 PM
Hi Rasika,
from the other thread on the AP Fail-over scenario example
AP's is
Primary - .25
Secondary -.24
Tertiary -.23
We have shutdown .25, AP's go to .24, Shutdown .24 AP's go to .23
after we power on the .24, AP remains on .23
once we power on .25, all the AP's go back to .25, but from .23. they dont move to .24
is there any theory behind this?
regards
10-13-2016 08:12 PM
That's expected behavior. APs usually check & see if primary WLC reachable,if it is, AP will fallback to primary WLC.
after we power on the .24, AP remains on .23
Since AP not checking a secondary WLC reachability, even that WLC is up, APs wont go there unless it lose current WLC. So AP will remain in .23
once we power on .25, all the AP's go back to .25, but from .23. they dont move to .24
Since .25 is primary WLC, once it come back AP will know it (since it periodically checking for primary WLC availability), as long as it is up AP will fall back to that.
This document explain it
HTH
Rasika
*** Pls rate all useful responses ***
10-13-2016 08:51 PM
10-13-2016 09:56 PM
Configuring LAG (Link Aggregation) is the recommended approach for any physical port failures of WLC.
What WLC model you got ?
Rasika
10-14-2016 12:27 AM
WLC 5508, i plan to use two ports port to CoreSW1 and port 2 on CoreSW2, will lag work on that scenario?
or i create port 1 AP Manager/Management port and create port 2 as back-up port of AP Manager
Regards,
10-16-2016 06:02 PM
hi Rasika,
any advise?
regards,
10-16-2016 07:16 PM
Unless SW1 and SW2 is a VSS pair, LAG won't work.
If it is a small deployment where 1Gbps throughput is more than enough, you can go with 2nd option.
Next time start a new thread as what we discussed here is not related to original thread posted. So very difficult to someone find this information by searching.
HTH
Rasika
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide