Cisco IQ | Resilient Infrastructure Services Series - Prepare

In this video, we will cover the prepare step in the software upgrade workflow needed to remediate security vulnerabilities. In the prepare step, we run some technical commands to ensure that we have a health check and snapshot of the device before we introduce a change.00:05Into it. There are five steps, each with suggestions around these commands.00:20Current configurations are confirmed by running the commands shown here. The console output that is returned should be copied and saved to the approved backup store. Once this is done, select the box to confirm. In step two, various readiness commands are performed that we suggest to help prevent you from.00:25Overlooking things that could cause problems with an upgrade.00:44For the sake of ease, the commands can be directly copied to the clipboard by selecting the blue copy button above each command. Here is what each step will have you perform. Step one, confirm reachability to the image or transfer server.00:48Step two, check flash or disk against the target image size. Step three, verify the config register is 0X21 oh two, so the asset auto boots the new image after reload.01:05Step four, validate RSA/TLS/crypto readiness. Note, upgrade will not execute for 17 point 14.1 plus if weak crypto is found.01:21Step five confirm IP domain name is configured. Note, required for crypto or cert operations. Step six, confirm the startup configuration is present to prevent configuration loss on reboot.01:36Step seven, Confirm license and support tier supports target image features. Step eight, confirm target image matches platform or supervisor minimum supported version. Step nine.01:53Validate stack before upgrade. Note, all stack members must be ready and on the same image for catalyst 9000 stacks. Check the box to acknowledge that all the commands shown have been run, all checks performed, and it looks ok.02:08Step three serves as open ended guidance for you to collect any additional show commands or health checks that you would like to run that might be domain specific or use case specific to your environment. This is largely a catch all for any other commands that haven't explicitly been disclosed in the prior step that you would want to collect.02:25Act.02:45Check the box to confirm that you have performed all necessary checks needed for your environment. In step four, instructions are shown to move the software image containing the fix over to the device being targeted for remediation. Once that is copied over and validated that the file is now in the flash, check the box to confirm the.02:46The image is staged and ready to execute.03:05Finally in step five we confirm the active version and install details and the install summary on this device. We get a snapshot of our interfaces and make sure that we have all of that captured before we trigger the software upgrade automation. Ensure you've saved the output from these commands alongside the change record before proceeding.03:08Once this is done, select the box to confirm. The next step of the software upgrade workflow is the execution step, which we will cover in another video in this series. Thanks for watching.03:27