"If you have 5508 at central location, then branch 3850 running as MC/MA should be able to anchor to 5508 for guest traffic."
For this case, is it a controller to controller link between the 3850 and 5508. We have tried to setup the anchor in this way, but failed. The reason we get after consulting Cisco is that the 5508 need to be upgraded to support new Mobility.
Do you know what is the difference between a new and old mobility anchor. My undestanding is that anchor uses EOIP and CAPWAP is used between AP and MA.
I tested the NME-AIR-WLC6-K9 (Software version 7.0.230) on a Cisco 2821 (I cannot find a spare Cisco SRE 300 ISM to test). It cannot connect to a Cisco 5508 (Software version 7.6.130) running New Mobility. I must turn off New Mobility on the Cisco 5508 before the anchor connection can be established.
If I turn on New Mobility, Cisco 3850 MC connection will fail.
NME-AIR-WLC6-K9 only support Old Mobility and Cisco 3850 only support New Mobility.
Just an observation, Cisco 3850 connection to Cisco 5508 (New Mobility) takes about 5 minutes to come up completely.
I tested the NME-AIR-WLC6-K9 (Software version 7.0.230) on a Cisco 2821 (I cannot find a spare Cisco SRE 300 ISM to test). It cannot connect to a Cisco 5508 (Software version 7.6.130) running New Mobility. I must turn off New Mobility on the Cisco 5508 before the anchor connection can be established
This is expected as 7.0.x only support EoIP based tunnel for inter-WLC data traffic. Once you enable new mobility on 5508, these inter-controller Data tunneling based on UDP (16667) instead of EoIP.
Unless both end configured for same tunneling method, it won't work. New mobility support in AireOS 7.6.x & 8.0.x as supported software version (it was supported 7.3.x & 7.5.x , but all those codes are deferred)
> 3850 as MA , 5508 at central location as MC for all the location and anchor also for guest traffic. Please remember here all the client information (clients connecting to 802.1x) would be shared with 5508 as it is an MC.
>Can I anchor the 3850 (running as MA/MC) back to a 5508 ? Do I need to convert all the 3850 to MA and deploy a 5760 as a MC in order to anchor back to the 5508 ? This is also possible. This is a standard solution like CUWN Guest Anchor where 5508 can be placed in DMZ , 5760 as MC and 3850 as MA.5760 talks to 5508 instead of 3850 MA directly.
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...