topic SD Access wireless migration in Wireless

SD Access wireless migration

KevinR99 — Mon, 17 Feb 2025 16:01:21 GMT

I am testing the conversion of a standard WLC deployment with the usual method of tunnelling the SSIDs back to the WLC and changing this to a fabric WLC with some SSIDs then changed to fabric mode.

I do the initial learn device config process and also provision the WLC. I then add the WLC to the fabric. During this process new SSIDs and Policy profiles are created. However, as expected my APs retain the same SSID to policy mapping and nothing changes for the client.

I now want to test converting one of my SSIDs to fabric mode. So I create a new network profile and add one of my SSIDs to it. I then define it as a fabric SSID, define a WLAN profiile name of SSID-Fabric-profile and I assign this profile to one of the areas managed by my WLC. After provisioning my WLC I can then go tot he fabric area - Wireless SSIDs and define an address pool to attach my SSID to. For good measure I re-provision the WLC and my test AP.

I now expect my AP to be advertising the same SSID but in fabric mode. However, I don't see any new profile created called SSID-fabric-profile and my AP stays configured with the SSID attached to an interface.

I think what I exopect here is a new Policy profile to be defined and in its advanced area I expect it to be attached to a fabric profile. In my policy tag area I then expect the tag that is applied to my AP tomap my SSID to a new fabric policy profile. That is not the case.

Perhaps I am doing the deployment in the wrong order? My requirement is to take a standard SSID and convert it, in only a selected area, to be a fabric SSID.

Anyone have any experience of this?

Thanks, Kev.

Re: SD Access wireless migration

KevinR99 — Mon, 17 Feb 2025 16:30:44 GMT

As a test I deleted all the SSIDs from my new profile and re-provisioned my WLC. The AP now got a policy tag that included no SSIDs. This is expected because I had deleted the SSIDs from my profile. I then recreated my profile and added an SSID to it in fabric mode. I also ensured in the Fabric site the SSID had an address pool attached to it. I re-provisioned the WLC and the single SSID I have defined in my profile was there. However, it was still working in standard mode, not fabric mode.

Re: SD Access wireless migration

KevinR99 — Mon, 17 Feb 2025 16:54:36 GMT

I think I see what's happening. When I did the learn config process Cat Center learned the Policy Profile my SSIDs attach to. In the Cat Center Network Profile area when I add an SSID I've defined a specific WLAN Profile name to make it easily identifiable in the WLC. I then expect this profile to be pushed to the WLC in the relevant mode, fabric or not. However, this profile is not pushed out. Instead the original learned policy profile is altered to be a fabric one. Not really what I expect. More testing around this process needed.