Yes, you're already set up for L3 roaming. By configuring your controllers to be in the same mobility group, your clients will be able to roam from an AP on one controller and one subnet to an AP on another controller in a different subnet, all running the same SSID. The controllers do this by creating a mobility tunnel back to the other controller, so the original controller is still the point of presence for that client.
Just make sure that the SSID uses the same security on both controllers. If you use different WPA keys, for example, your clients won't be able to roam from one controller to the other.
With your setup, when a user roams, he or she will keep the ip address they have initially obtained. This is how mobility works and why you can roam smoothly. Even if you have AP Groups configured in which you have one ssid and maybe on different floors you have it assigned to different subnets, the user or device will keep its original ip address no matter if they are in an area which users or devices are on a different subnet. Release and renew will allow then to get the ip from that area, but then you don't have roaming.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...
I have created a Powershell script to automatically add a Wireless Guest
User on Cisco WLCs. (tested on 2500 Series) The script should be
completely self explanatory. Prerequisites: Powershell SNMP Module
(Install-Module -Name SNMP) SNMP Write Access to y...