A national retailer is about to upgrade NX-OS on a production leaf and wants to know whether that upgrade will reload the switch before anyone starts it. Which check reports the impact?
Select an answer to reveal the explanation.
Short Explanation
You would not start a kitchen remodel without asking whether the crew has to shut the water off. You run the install impact check so you learn whether this system image reloads the leaf before anyone begins the upgrade. A checkpoint only compares configuration, and it does not speak for the image.
Full Explanation
On NX-OS, the install impact check evaluates a system image against the running switch and reports whether the upgrade is disruptive, including which parts of the switch must reload. That is the report this retailer needs before a production change window starts. A configuration checkpoint captures the running configuration so it can be compared or restored. It has nothing to say about whether a new system image reloads the box. SPAN copies frames to an analyzer. It can show traffic stopping after a reload has already happened, and it is not a preview of the upgrade. An EPLD update programs hardware logic devices and is a separate operation from the system image. Listing an EPLD image does not preview the hit of an NX-OS upgrade. Caveat: the impact result is specific to the image and the chassis you asked about, so a clean result on a lab switch does not automatically describe this production leaf. Operational check: run the impact check against the intended image, read whether a reload is required, and only then schedule the upgrade in a window that matches that result.