CONTAP-455926: ASA r2 cluster data and management LIF reverts back to home port automatically in waiting for giveback status
Issue
- ASA r2 in takeover status, the cluster management LIF in migration status:
cluster1::> storage failover show
Takeover
Node Partner Possible State Description
-------------- -------------- -------- -------------------------------------
cluster1-01 cluster1-02 - Kernel loaded <<<
cluster1-02 cluster1-01 false In takeover, Auto giveback will be
initiated in 438 seconds
2 entries were displayed.
cluster1::> network int show
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
----------- ---------- ---------- ------------------ ------------- ------- ----
Cluster
.......
cluster1
......
cluster_mgmt up/up x.x.x.x/24 cluster1-02 e0c false <<<
- When the node in "waiting for giveback" status:
cluster1::*> storage failover show
Takeover
Node Partner Possible State Description
-------------- -------------- -------- -------------------------------------
cluster1-01 cluster1-02 - Waiting for giveback <<<
cluster1-02 cluster1-01 false In takeover, Auto giveback will be
initiated in 369 seconds
- The cluster management LIF reverts back to home port automatically:
cluster1::*> network int show
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
----------- ---------- ---------- ------------------ ------------- ------- ----
Cluster
......
cluster1
......
cluster_mgmt up/up 192.168.0.101/24 cluster1-01 e0c true <<<
- Even the LIF is back to home port status, the LIF doesn't work before storage failover giveback completely.
- For data LIF sample:
- LIF is down and then up before giveback start, even without LIF migration.
cluster2::> storage failover takeover -ofnode cluster2-01
iSCSI-lif_n1_e1a up/- 192.168.164.10/24 cluster2-01 e1a true
iSCSI-lif_n1_e1b up/- 192.168.164.11/24 cluster2-01 e1b true
iSCSI-lif_n1_e1a up/down 192.168.164.10/24 cluster2-01 e1a true
iSCSI-lif_n1_e1b up/down 192.168.164.11/24 cluster2-01 e1b true
iSCSI-lif_n1_e1a up/up 192.168.164.10/24 cluster2-01 e1a true
iSCSI-lif_n1_e1b up/up 192.168.164.11/24 cluster2-01 e1b true
cluster2::> storage failover show
Takeover
Node Partner Possible State Description
-------------- -------------- -------- -------------------------------------
cluster2-01 cluster2-02 - Waiting for giveback
cluster2-02 cluster2-01 false In takeover, Auto giveback will be
initiated in 345 seconds
2 entries were displayed.
Jun 19 18:22:16 [cluster2-01:vifmgr.started:notice]: The Logical Interface Manager (VIFMgr) has started.
Jun 19 18:22:25 [cluster2-01:vifmgr.portdown:notice]: A link down event was received on node cluster2-01, port e1a.
Jun 19 18:22:25 [cluster2-01:vifmgr.portdown:notice]: A link down event was received on node cluster2-01, port e1b.
Jun 19 18:22:27 [cluster2-01:vifmgr.portup:notice]: A link up event was received on node cluster2-01, port e1a.
Jun 19 18:22:27 [cluster2-01:vifmgr.portup:notice]: A link up event was received on node cluster2-01, port e1b.
Jun 19 18:22:30 [cluster2-01:vifmgr.lifbeinghosted:notice]: LIF iSCSI-lif_n1_e1a (on virtual server 4), IP address 192.168.164.10, previously marked as down, is now up and serving data on node cluster2-01, port e1a.
Jun 19 18:22:30 [cluster2-01:vifmgr.lifsuccessfullymoved:notice]: LIF iSCSI-lif_n1_e1a (on virtual server 4), IP address 192.168.164.10, is now hosted on node cluster2-01, port e1a.
Jun 19 18:22:30 [cluster2-01:vifmgr.lifbeinghosted:notice]: LIF iSCSI-lif_n1_e1b (on virtual server 4), IP address 192.168.164.11, previously marked as down, is now up and serving data on node cluster2-01, port e1b.
Jun 19 18:22:30 [cluster2-01:vifmgr.lifsuccessfullymoved:notice]: LIF iSCSI-lif_n1_e1b (on virtual server 4), IP address 192.168.164.11, is now hosted on node cluster2-01, port e1b.
Waiting for giveback...(Press Ctrl-C to abort wait)
Jun 19 18:23:41 [cluster2-01:vifmgr.reach.ok:notice]: Network port e1a on node cluster2-01 can reach its expected broadcast domain Default:Default-1. No other broadcast domains appear to be reachable from this port.
Jun 19 18:23:41 [cluster2-01:vifmgr.reach.ok:notice]: Network port e1b on node cluster2-01 can reach its expected broadcast domain Default:Default-1. No other broadcast domains appear to be reachable from this port.
Continuing boot...