Why did both nodes in ClusterA reboot causing switchover
Applies to
- Fabric MetroCluster
- ONTAP 9
Answer
19Oct2023 15:33:20"n="ClusterA-N1" t="1697722555"id="1697722212/299" p="5" s="Ok"o="cf_main" vf="" type="0"seq="57628599" <cf_fsm_partnerNotResponding_1/></LR>
19Oct2023 15:33:20" n="ClusterA-N2" t="1697722555" id="1697722212/299" p="5" s="Ok" o="cf_main" vf="" type="0" seq="57628599" <cf_fsm_partnerNotResponding_1/> </LR>
Both nodes inititate takeover causing disk reservation conflicts and both nodes reboot:
19Oct2023 14:34:58" n="ClusterA-N1" t="1697718800" id="1690874500/945100" p="7" s="Ok" o="disk_server_0" vf="" type="0" seq="57628077"
disk_reservationConflict_key_1
diskName="Switch01:1-17.126L599" Shelf 32 Bay 8 104588 & 104609 17T0A17HF9ZZ
delay="0"
key="0x20023bee00000199"
cdb="0x8a:000000010b337200:00000299"
thread="raidio_thread"
type="DISK_WRITE_CHAIN"
19Oct2023 14:34:58" n="ClusterA-N1" t="1697718800" id="1690874500/945100" p="5" s="Ok" o="disk_server_0" vf="" type="0" seq="57628079"
ha_resvConflictHalt_1
disk_name="Switch01:1-17.126L599" Shelf 32 Bay 8 104588 & 104609 17T0A17HF9ZZ
time="19Oct2023 14:34:58"
last_update="32184"
A disk reservation was detected on disk Switch01:1-17.126L599 at 19Oct2023 14:34:58 Ordinarily, this will only occur if the partner node has taken over.
This node will be shutdown.
HALT: HA partner has taken over disk reservations
Uptime: 79d5h12m58s
System rebooting...