Wanted to post this in case anyone else has a similar issue.. took us a week of troubleshooting.
After upgrading from 17.3.5b to 17.9.3, clients are failing to join wireless if they leave one policy profile and join later on another one.
shown in lo...
The 2nd Gen Intel procs, namely, most of the 6000 series "R" SKUs have inlet temp requirements. The B200 M5 spec sheet says the 6248R proc is limited to 77F ambient temp if in slot 1-7. What happens when this is exceeded? It wouldn't be by much, but...
Sure thing! We had 3 HA pairs registered to the FMC1000. We kept the IP of our old and new FMC the same.
If you want to migrate one or a few FTDs at a time to the new FMCv, your new FMCv will need a unique IP address of course, and I believe you will...
We did not experience any downtime. When shutting down the old FMC and turning up the "newly restored" FMC, it acted like it normally would-- it needed to do a full deploy to the firewalls, but no impact was noticed since the configs were the same be...
For what its worth (and to help you save any hairs remaining)...
17.9.3 with all SMUs and APSP6 applied has been our most rock solid deployment of 9800 wireless, to-date. No crashes, no random HA failovers. ~1500 APs consisting of 3800/9120/9130/9136...
We still have many access-sessions on our trunk links. The device-tracking database is empty for the trunk links as expected, but does anyone know how to prevent the MACs of devices attached to other switches from appearing in the session table on Ca...
Likewise. Can confirm, adding 100GB to the FMC from VMware, then booting the Gparted Live CD worked. Grew sda3 (the extended FS) then grew sda7, committed. Detached gparted and booted FMC with the new free space-- recognized in FMC from running "df -...
