MetroCluster SAN Host IO timeout due to power outage

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

Views:: 188

Visibility:: Public

Votes:: 0

Category:: metrocluster

Specialty:: san

Last Updated:

Applies to

ONTAP MetroCluster
Hyper-V

Issue

During site power outage UPS batteries fully discharged causing DR automatic switchover (AUSO) within for stretched two-node MetroCluster with SAN SVM
Hyper-V Host experienced IO timeout ( > 120 seconds) though switchover was within SLA
CIFS share access interrupted

pmcsas_admin_0: sas.port.down:debug]: SAS port "0b" went down.

pmcsas_admin_0: sas.port.down:debug]: SAS port "2a" went down.

pmcsas_asyncd_2: sas.adapter.online:info]: SAS adapter 2a is now online.

pmcsas_asyncd_0: sas.adapter.online:info]: SAS adapter 0b is now online.

fmmbx_instanceWorker: fmmb.instStat.change:info]: normal mailbox instance on DR Partner side.

stackmon_thread: stackmon.workqueue.emptied:debug]: One or more shelves have been reconciled successfully.

monitor: monitor.globalStatus.ok:notice]: The system's global status is normal.

DR_heartbeat_thread: mcc.config.auso.stDisabled:error]: The state of Automatic Unplanned Switchover capability has been disabled.

DR_heartbeat_thread: cf.fmns.readSparecore:debug]: UID of the partners sparecore disk that is being read from the partner's mailbox is 0

DR_heartbeat_thread: mcc.auso.triggered:notice]: The node has triggered an Automatic Unplanned Switchover of the DR partner. Reason: DR partner Hearbeat Lost. If Automatic Unplanned Switchover was triggered because of heartbeat loss, any ongoing dump on the partner may be aborted