01-31-2023 03:58 PM
Have a client that has a 9800 auto-anchoring a quest network for several locations. The 9800 Auto-Anchor is at a site where they now want to host an AP and a local SSID. It has been my understanding that the auto-anchor should be used only for an anchor, and not control local APs or host local SSID. An associate told me it's possible to control local APs and host local SSID so long as the SSID isn't the same one that's exported for foreign controllers using it for guest traffic.
Anyone setup an Auto-Anchor with local SSID and supporting local APs?
02-01-2023 01:59 AM
>...An associate told me it's possible to control local APs and host local SSID so long as the SSID isn't the same one that's exported for foreign controllers using it for guest traffic.
- I doubt it because foreign WLC will use the anchor's Wireless Management IP and also everything will revert to Central Switching (to the Anchor) , you could attempt it and use WirelessAnalyzer which will quickly point out fatal configuring errors for that use the CLI command : show tech wireless , have the output analyzed by https://cway.cisco.com/
M.
02-01-2023 06:59 AM
You can have the same SSID as long as the profile name is unique. Basically you have your SSID that is used only for anchor and then you have another SSID profile that is used for local. Of course you will need different tags and policies for the site that requires local SSID.
02-01-2024 07:14 AM - edited 02-01-2024 07:53 AM
HI
Just on the back of this one, this helped me out, ith one anchor. We advertise 4 organisations in our hospital, and they in return advertise our SSID around the county in their buildings.
I can get above working just for one organisation, but when clone and change the profile name, I get the ususal
%CLIENT_ORCH_LOG-4-ANCHOR_VAP_SECURITY_MISMATCH: Chassis 1 R0/0: wncd: Export anchor required but local and remote security/profile configuration is not matching for: Wlan-Profile: billybob, Policy-Profile: billybob
But from I can see what it is asking for is correct. I've put them in seperate TAG, same TAG
Is there something I'm missing? cheers
foreign | ||||||
9800 wlan profile | 9800 wlan ssid | 9800 policy profile name | 5520 wlan profile name | 5520 wlan SSID | works | |
myssid | myssid | myssid | myssid | myssid | yes | |
billybob | myssid | billybob | billybob | myssid | no | |
02-01-2024 08:03 AM
- FYI : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwd76693
M.
m.
02-02-2024 12:33 AM
hi
So only way going to get this to work, is to get all the organisations to change their naming conventions for their WLAN Profile that points back to our wlcs, so the wlan profile, ssid name and policy are all the same?
cheers
02-02-2024 01:19 AM - edited 02-02-2024 01:19 AM
What version of software are you using?
CSCwd76693 is fixed in 17.9.4a which is the current TAC recommended release.
Not clear from your table which row is the local and which row is the anchor?
02-02-2024 01:40 AM
I'm on 17.9.4a
i'll log a call
cheers
02-02-2024 02:51 AM
> i'll log a call
That's probably best
But still not clear which ROW (horizontal line) is local and which is foreign.
In other words which SSID profile is the one you're using locally?
02-02-2024 03:02 AM
06-06-2024 01:43 PM
Scott, what you were saying works. I had to duplicate two components from the existing setup: a wireless policy and a WLAN. For instance, we have a Guest_Network under the company's Wireless profile policy. I duplicated it and renamed it Guest_Wireless_Anchor. In this setup, I enabled the anchor configuration. You need to have nearly identical configurations on both anchor and foreign controllers, with just a few minor adjustments. For example, you can ignore the VLAN on the wireless profile policy in the foreign controller since you're not supposed to have a local IP address assignment. It's working!!! Thanks
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