SK Halt occurs when performing Takeover/Giveback

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 144

Visibility:: Public

Votes:: 0

Category:: ontap-9

Specialty:: hw

Last Updated:

Applies to

ONTAP 9
AFF/FAS/ASA

Issue

SK halt was initiated:

[?] Sun Sep 29 04:24:05 -0500 [Nodeb: kltp: callhome.clam.node.ooq:EMERGENCY]: Call home for NODE(S) OUT OF CLUSTER QUORUM. [?] Sun Sep 29 04:24:05 -0500 [Nodeb: kltp: clam.node.ooq:EMERGENCY]: Node (name=Nodeb, ID=1001) is out of "CLAM quorum" (reason=quorum update). [?] Sun Sep 29 04:24:05 -0500 [Nodeb: kltp: clam.node.avail.change:debug]: The availability status of node (name=Nodeb, ID=1001) changed from Available to Unavailable. [?] Sun Sep 29 04:24:05 -0500 [Nodeb: cf_main: cf.fsm.takeoverOfPartnerDisabled:error]: Failover monitor: takeover of Nodea disabled (partner is attempting takeover). [?] Sun Sep 29 04:24:07 -0500 [Nodeb: disk_server_1: ha.resvConflictHalt:notice]: A disk reservation conflict was detected on disk 0a.00.2P3 at %-20s. Typically, this only occurs when the node was taken over by its partner. [?] Sun Sep 29 04:24:07 -0500 [Nodeb: disk_server_1: kern.shutdown.initiator:debug]: SK reboot was initiated by "maytag.ko::fm_handleReserved+763".