Loading...
Loading...
A Nexus 5K or 6K switch may experience a HAP reset due to a crash on the "fex" process if one of the FEX modules is down and one of the following commands is issued: - "show fex" - "show fex detail" - "show fex # transceiver" %KERN-0-SYSTEM_MSG: writing reset reason 16, fex hap reset - kernel
This is only seen if one of the FEX modules is offline when the "show fex" command is issued. The most common cause for the FEX to be offline is when the parent switch chassis is running an incompatible NX-OS version.
Bring the FEX into an online state or else detach it it if isn't in use. If the FEX is offline due to an NX-OS incompatibility, upgrade the parent switch to a version that supports the FEX.
Versions of NX-OS with the fix for this issue will now present the following error message instead of crashing: "Fex # is not online"
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.