A retail bank upgraded the NX-OS system image on a Nexus switch. A later advisory says the programmable hardware logic on a module is still outdated. The system image on the switch is already the recommended release. What is the remaining upgrade?
Select an answer to reveal the explanation.
Short Explanation
The system image is the playbook. EPLD is the wiring inside the module, and you update that wiring with its own upgrade. You do not get a new EPLD just because the bank already installed the recommended NX-OS image.
Full Explanation
EPLD updates the programmable logic on a Nexus module. Cisco ships that update separately from the NX-OS system image, and installing the recommended image does not by itself refresh an outdated EPLD. The bank has finished the image step and still needs the EPLD upgrade named in the advisory. Copying the same system image again does not deliver hardware logic that the image does not contain. POAP is a day-0 configuration bootstrap. It does not program module EPLDs on each boot. SPAN copies frames to an analyzer. It does not write hardware logic. Caveat: EPLD upgrades are disruptive to the module being updated, so the bank should read the impact and take the hit in a maintenance window rather than treating the update as hitless. Operational check: compare the module's current EPLD versions with the advisory, schedule the EPLD upgrade, and confirm the module reports the new version after it returns. Record the before and after values in the change ticket so the next shift can see what changed.