Unconfigured MetroCluster IP node waiting for reservations to clear
Applies to
- MetroCluster IP node configuration
- ONTAP 9
Issue
This issue can be noticed:
- Before configuring the MetroCluster IP nodes, a takeover is performed and the node taken over gets stuck
waiting for reservations to clear
- Unexpected node reboot (with partner takeover) when "Creating a mirrored data aggregate on each node" at Configuring the clusters into a MetroCluster configuration (netapp.com). Example:
Surviving node reporting:
[node_name-1: cf_main: cf.fsm.takeover.postFailed:debug]: Failover monitor: takeover attempted after partner POST failed
Impaired node reporting:
[node_name-1: mgwd: mgmtgwd.jobmgr.jobcomplete.failure:info]: Job "Aggr Create" [id 739] (Create data_aggr) completed unsuccessfully: Failed to create aggregate "data_aggr" on "node_name-2". Reason: ZSM - failed, status code = 571, extra = Timeout: Operation "ksmfRawZapi_iterator::get_imp()" took longer than 110 seconds to complete [from mgwd on node "node_name-1" (VSID: -3) to kernel at 169.254.204.144], took 109.998s, max 110s [169.254.204.144:9. (1).