Applies to Azure Cloud Volume ONTAP HA Network Interface Controller (NIC) Issue storage failover show command shows NVRAM is not synced after the node was brought down due to Microsoft Azure maintenan...Applies to Azure Cloud Volume ONTAP HA Network Interface Controller (NIC) Issue storage failover show command shows NVRAM is not synced after the node was brought down due to Microsoft Azure maintenance event. EMS reports cf_main: cf.fsm.takeoverByPartnerDisabled:error]: Failover monitor: takeover of node-02 by node-01 disabled (unsynchronized log) HA Status: Degraded -HA cluster is not highly available. Takeover by node node-01 is not possible because: ic_errorlog_unsync
Applies to ONTAP 9 Azure Issue A new SVM is created In testing node failover, a CVO node is powered down Takeover happens, but NFS clients are unable to read and write The LIF fails over to the partne...Applies to ONTAP 9 Azure Issue A new SVM is created In testing node failover, a CVO node is powered down Takeover happens, but NFS clients are unable to read and write The LIF fails over to the partner, but LIF is unreachable by client In testing the LIFs on the original deployed SVM work normally
Applies to Azure-HA Issue From ONTAP EMS: [Cluster-01: OscHighPriThreadPool: objstore.host.unresolvable:error]: Object-store server host name "rootxxxxxxxxxx.blob.core.windows.net" cannot be resolved ...Applies to Azure-HA Issue From ONTAP EMS: [Cluster-01: OscHighPriThreadPool: objstore.host.unresolvable:error]: Object-store server host name "rootxxxxxxxxxx.blob.core.windows.net" cannot be resolved to an IP address on node From Cloud Manager server.log: Failed getting device data for Cluster01. com.netapp.oncloud.simplicator.client.common.SimplicatorBadRequestException: rootxxxxxxxxxx.blob.core.windows.net: Name or service not known
