Skip to main content
NetApp Knowledge Base

Version Firmware Mismatch After Failed Takeover on Upgrade

Views:
6
Visibility:
Internal
Votes:
0
Category:
not set
Specialty:
not set
Last Updated:

Applies to

  • * ONTAP 9

Issue

Primary Problem:
node-1::> cluster image show-update-progress


Estimated Elapsed
Update Phase Status Duration Duration
-------------------- ----------------- --------------- ---------------
Pre-update checks completed 00:10:00 00:01:08
ONTAP updates paused-on-error 01:32:00 01:03:25
Details:
Node name Status Status Description
-------------------- ----------------- --------------------------------------
Node-01 failed Error: Takeover failed.
Action: Use the "storage failover
show-takeover" command to view the
cause of takeover failure and the
suggested corrective actions. When
all issues are resolved, use the
"cluster image resume-update" command
to trigger takeover.
Node-02 completed
7 entries were displayed.
Paused - An error occurred in "ONTAP updates" phase. The update cannot continue
until the error has been resolved. Resolve all issues, then use the cluster
image resume-update command to resume the update.


Takeover was vetoed by raid with error:


::> storage failover show-takeover


Node Node Status Aggregate Takeover Status
---------- --------------------- -------------- -------------------------------
Node-01
Optimized takeover
by partner aborted.
aggr_1
Failed: Operation was vetoed
by raid.
Node-02
Optimized takeover
of partner aborted.
Run the command
"storage failover
show-takeover -node
Node-01" to
display the
relocation status of
the partner.
- -
3 entries were displayed.


On EMS


ERROR ses.mismatch.fw.version: The disk shelf modules on disk shelf 0b.10 are
running two different firmware versions. Disk shelf module A is running 0130,
and disk shelf module B is running 0140.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

This is an internal KB article and its content should not be copy/pasted and shared with people outside of NetApp. Always seek Duty Manager authentication of caller for password reset requests. If you need further assistance post a question in Knowledge Xchange