Issue is introduced by cluster node removal or manipulation on affected ONTAP releases and is not necessarily immediately obvious Scenarios that may manifest issue: HA takeover for Power failure, Over...Issue is introduced by cluster node removal or manipulation on affected ONTAP releases and is not necessarily immediately obvious Scenarios that may manifest issue: HA takeover for Power failure, Over temperature, update etc and result in Host server not able to access the FC (Fiber Channel) target correctly. H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. network interface show shows UUID (not node name) for the nodes that were removed from the cluster:
Mon Jan 04 12:09:45 EST [example: fpolicy: fpolicy.server.connectError:error]: Node failed to establish a connection with the FPolicy server '10.1.1.101' (reason: 'Connection to FPolicy server is brok...Mon Jan 04 12:09:45 EST [example: fpolicy: fpolicy.server.connectError:error]: Node failed to establish a connection with the FPolicy server '10.1.1.101' (reason: 'Connection to FPolicy server is broken(EPIPE) received.'). Mon Jan 04 12:09:45 EST [example: fpolicy: fpolicy.server.disconnect:warning]: Connection to the Fpolicy server '10.1.1.101' is broken ( reason: 'FPolicy server is removed from external engine.' ).
FAS and AFF systems in a 2 node HA configuration Running a 2 node HA configuration Attempts to configure cluster HA fail with the following error: cluster::*> cluster ha modify -configured true Warnin...FAS and AFF systems in a 2 node HA configuration Running a 2 node HA configuration Attempts to configure cluster HA fail with the following error: cluster::*> cluster ha modify -configured true Warning: High Availability (HA) configuration for cluster services requires that both SFO storage failover and SFO auto-giveback be enabled. Do you want to continue? {y|n}: y Error: command failed: RDB dblade agent: RDB HA configuration UUID does not match cluster UUID.
