Building one and two is internally routed with a L3 switch (6509) 10.2.0.0/16
Building three is routed with a L3 switch (4900) 10.3.0.0/16
Our VoIP network in building one and two is 10.2.11.0/24
Our VoIP network in building one and two is 10.3.111.0/24
Our wireless system is a Meraki-based system that we just implemented.
The issue is that the wireless completely drops when moving from one subnet to the other. So in effect, service is pretty good when going between building one and two (share the same core and subnet), but drops when going into building 3. Signal to AP is just fine.
What do I need to look at and/or do to get prevents drops when roaming between the two subnets (cores) ?
Do not have any knowledge about Meraki wireless system. But as per your problem discription mobility/roaming is not working in your network.
In a normal cisco WLC environment client will not change its IP when roaming, in order to provide smooth roaming experience. Traffic will tunnel back to original controller where they first associate to network.
You need to bring this to the people (hope this was not deploy by yourself) who deploy this and ask them to fix it
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...