Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Looking to upgrade and running deployment of CatC from 2.3.7.6 to 2.3.7.9. It's running in DR already. Trying to find the steps to do this upgrade. Not sure if I need to break/pause DR and upgrade the witness node first and then active and backup. I'...
I'm running into an issue trying to use the API to provision APs on version 2.3.7.7.
https://developer.cisco.com/docs/dna-center/2-3-7/ap-provision/
Per the documentation I need to send the below in the payload.
customApGroupName:string Custom AP gr...
I'm trying to write a template to push AutoConf templates to ports and I'm having issues when I bind the input to the source.
I have bound the $interface_range to the source, inventory, interface, portName
when I run the simulation it never replaces ...
Trying to find out what replaces the "magctl rbac external_auth_fallback enable" command on 2.3.7.0 and if it's still needed. Generally looking for any CLI information on 2.3.7 since it seems to have changed.
I was wondering if anyone knew what the maximum amount of traffic that can be passed over GRE tunnels for this sup. I seem to think that it is 35Mb, but not really sure. Also can I add an ASIC daughter card to improve this?
It's been a bit since I did the upgrade but it was 2 three node clusters. I think each cluster takes a few hours to complete. The witness VM was very fast. Then re-enabling DR was pretty fast as well. No SD-Access so no impact there. Hope that helps....
I'm not sure if you found the answer but I can tell one thing to check is the certificate for Catalyst Center. If you replaced it then make sure you have all the IP addresses in it. Especially the Enterprise VIP address. During certificate deployment...
I can tell you that if you are trying to use CatC to do this and are not on version 2.3.7.10 than this is a known bug specific to 9200s. I was working with a client on deploying a bunch, 300+, 9200s and uncovered this bug. We had developers on calls ...
