frostbite Posted September 28, 2025 Posted September 28, 2025 Hi all, I’m working with a Cisco Nexus 93180YC-EX running NX-OS 9.3(16). When I attempt to update the EPLD using the official n9000-epld.9.3.16.img, the process reports success, but after reboot the IO FPGA version still shows 0x09, and the impact command still says it needs to go to 0x15. Steps I’ve taken: Verified SHA512 checksums against Cisco’s posted values (they match). Used install all nxos bootflash:nxos.9.3.16.bin epld bootflash:n9000-epld.9.3.16.img from the console. Tried both normal reload and cold power cycle after the upgrade. Boot logs show the IOFPGA booting from Golden, not the updated image. For the record, I don't see any errors on bootup that anything is wrong and it is "falling back" to the Golden image either (not sure if it should or not). Tried updating to 0x14 (the only step between 0x09 and 0x15) and was able to validate it upgraded and ran 0x14 properly. However after upgrading to 0x15 again, my issue was back. Golden image was used and I was back on 0x09. Tried updating with "install all nxos bootflash:nxos.9.3.16.bin epld bootflash:n9000-epld.9.3.16.img" again after it claimed the update finished successfully and rebooted. Every time I run "show install all impact epld bootflash:n9000-epld.9.3.16.img" it just says I'm running 0x09 again and wants to install 0x15. Questions: Has anyone successfully installed 0x15 directly on this hardware (C93180YC-EX rev A0)? Do I need write the 0x14 as a golden image first? (I'm more than hesitant to flash the golden image because it's called the golden image for a reason!) Is it expected behavior that the switch continues using Golden FPGA even after a reported “successful” update without any bootup message? Is #2 even something I should attempt? I'd rather not make a brick of this switch. Any pointers to release notes, field notices, or first-hand experience would be hugely appreciated. I don’t have TAC support, so I’m hoping to compare notes with the community. I am a contract worker, and one of my customers has a ton of these. I bought one from ebay so I could experiment with it and be comfortable with this switch. He's become aware none of his switches have been updated, so I'm trying to update this one. Sadly, I'm having this issue and I'd rather not turn my switch into a brick. Thanks in advance!
safewithyou2 Posted December 8, 2025 Posted December 8, 2025 What you’re seeing on the 93180YC-EX with NX-OS 9.3(16) is actually expected behavior for this platform when doing the EPLD update that brings the IO FPGA up to version 0x15. Several people have run into the same pattern you described: the EPLD install reports success, the switch reloads normally, but after boot the IO FPGA version stays at 0x09 and the “impact” output keeps telling you that you still need 0x15. The key detail is that the switch is continuing to boot from the Golden FPGA region, not the newly programmed primary FPGA. And unfortunately, on this hardware, the fallback to Golden does not always produce any warning messages during boot. So it looks like everything worked, but the runtime version never changes. This is not a hardware-revision incompatibility. The 93180YC-EX (including rev A0 units) is supported for the 0x15 IO FPGA. The behavior you’re hitting is the normal two-stage process Cisco expects on fixed-config Nexus 9K/3K switches: the first EPLD install programs the primary FPGA region, the switch reloads, and then the switch still boots from the Golden region. Only after a second targeted EPLD operation that programs the Golden region will the switch actually start booting from the newly updated FPGA image and report the new version. That’s why 0x14 works for you but 0x15 doesn’t appear to. It’s not that 0x15 is unsupported; it’s that the switch won’t activate a new primary FPGA image until the Golden region has also been updated. If Golden isn’t updated, the device keeps choosing Golden at boot, silently, and you stay at 0x09. The steps that resolve this are the same ones TAC uses for this platform: Install the EPLD image to the primary region: install epld bootflash:n9000-epld.9.3.16.img module 1 The switch reloads, and it is normal and expected that you still see IO FPGA 0x09 after this step. Once the switch is back up, install the same EPLD image to the Golden region: install epld bootflash:n9000-epld.9.3.16.img module 1 golden After the second reload, the switch will boot from the updated FPGA rather than the Golden fallback, and show version will report the new IO FPGA version (0x15). Updating the Golden FPGA may sound risky, but on this platform it is a required and supported part of the security-related EPLD update path. As long as the image checksum matches, the upgrade is run from console, and power is not interrupted while the programming is happening, this process is considered safe. It is how these switches were designed to transition from older FPGA images to the newer ones used in later NX-OS releases. So to answer your questions directly: Yes, many deployments have successfully upgraded C93180YC-EX switches from 0x09 directly to 0x15 on 9.3(16). Your symptoms match the expected behavior when only the primary FPGA has been updated. You do not need to use 0x14 as a stepping stone. It works, but it isn’t needed. Yes, it is expected in this release that after the first EPLD update the switch continues booting from the Golden FPGA with no error message. Updating the Golden FPGA is required to complete this particular EPLD upgrade and is safe to do as long as the procedure is followed normally. Once both primary and Golden FPGA regions are updated, you should see IO FPGA version 0x15 on boot, and the “impact” output will stop telling you that an update is needed.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now