>> "Each AP will create a connection to a primary local controller and *only one* standby controller, regardless of the number of
>> controllers in a fast failover group”
[mw] Yes, that is correct
>> While license count will not be decrementented for a standby AP session; CAP capacity *is* impacted. That is to say a controller
>> with a 512 CAP limit like the M3 could handle 512 Primary AP connections OR 512 Standby Connections OR 300 Active and 212
>> Standby Connections but NOT 300 Active connections and 300 Standby connections (88 standby connections would thusly be
>> denied)
[mw] This is correct
>> In v6.4 you mention standby-mode connection capacity to exceed the rated controller CAP limit. Will this be limited to specific
>> hardware like the 7200 or newer platforms?
[mw] Yes, there are some dependency on hardware platform. For 7200 series controller, it will allow 4x the platform limit for standby tunnel. The controller will only allow active tunnel up to platform limit. for M3/3600, the ratio is 2x.
>> In v6.4 is support for deterministic pathways supported? For example, on a college campus, I would typically terminate all APs
>> for a building to a specific controller. In a non-deterministic fast-failover; I could have a building where APs were now terminated
>> across different local controllers.
[mw] You can build predictability by making sure that the controller have enough capacity, where AP build active and standby tunnel to the same set of controllers.