DR Mirrors not operational on FAS8200/AFF A300 after brief connectivity loss
Applies to
- MetroCluster IP
- FAS8200 / AFF A300
- Interconnect
Description
Following the loss and recovery of MetroCluster IP connectivity, the HA, DR or AUX interconnect connectivity can be lost even though the physical connectivity is present and healthy.
The Mirror status will report as disabled and offline, even while the iWARP connections are up in metrocluster interconnect show:
Cluster1::> metrocluster interconnect show
(metrocluster interconnect show)
Mirror Mirror
Partner Admin Oper
Node Partner Name Type Status Status Adapter Type Status
---- ------------ ------- -------- ------- ------- ------ ------
Node1A Node2A HA enabled online
e1a iWARP Up
e1b iWARP Up
Node1B DR disabled offline
e1a iWARP Up
e1b iWARP Up
Node2B AUX disabled offline
e1a iWARP Up
e1b iWARP Up
Node2A Node1A HA enabled online
e1a iWARP Up
e1b iWARP Up
Node2B DR disabled offline
e1a iWARP Up
e1b iWARP Up
Node1B AUX disabled offline
e1a iWARP Up
e1b iWARP Up
It is also possible that the Local HA will be offline because of the loss of NVRAM synchronization. The eligibility to failover can be observed in storage failover show:
Cluster1::> storage failover show
Takeover
Node Partner Possible State Description
-------------- -------------- -------- -------------------------------------
Node1
node2 false Connected to node2,
Takeover is not possible: NVRAM log
not synchronized
Node2
Node1 false Connected to node1,
Takeover is not possible: NVRAM log
not synchronized
If AutoSupports available, check the METROCLUSTER-TCP-SYSCTL-MCC
section in a full Autosupport and look for these errors:
name=wafl qp_id=0 state=DISCONNECTED rhp=0xfffff806190ed800 refcnt=0 last_err=12 sq=0 rq=0 tid=0 cq=0 client
p_name=wafl state=WAIT_FOR_CONN rhp=0 refcnt=0 last_err=-12
name=wafl qp_id=0 state=CONNECTING rhp=0xfffff8086ce41800 refcnt=0 last_err=12 sq=0 rq=0 tid=0 cq=0 client
p_name=wafl state=WAIT_FOR_CONN rhp=0 refcnt=0 last_err=-12
name=raid qp_id=0 state=CONNECTING rhp=0xfffff8029f887000 refcnt=0 last_err=12 sq=0 rq=0 tid=0 cq=0 client
p_name=raid state=WAIT_FOR_CONN rhp=0 refcnt=0 last_err=-12
name=raid qp_id=0 state=DISCONNECTED rhp=0xfffff80287209000 refcnt=0 last_err=12 sq=0 rq=0 tid=0 cq=0 client
p_name=raid state=WAIT_FOR_CONN rhp=0 refcnt=0 last_err=-12
name=misc qp_id=0 state=CONNECTING rhp=0xfffff8087fa03000 refcnt=0 last_err=12 sq=0 rq=0 tid=0 cq=0 client
p_name=misc state=WAIT_FOR_CONN rhp=0 refcnt=0 last_err=-12
name=misc qp_id=0 state=CONNECTING rhp=0xfffff80844c73800 refcnt=0 last_err=12 sq=0 rq=0 tid=0 cq=0 client
If the WAIT_FOR_CONN rhp=0 refcnt=0 last_err=-12
errors are present then then the issue is confirmed as Bug 1307431.