Duplicate IP causes iSCSI sessions to reconnect randomly
Applies to
Issue
- Constantly reconnecting back-end iSCSI sessions due to timeouts as seen in the ems/events:
 
[ClusterB-01:iscsi.session.stateChanged:notice]: iSCSI session state is changed to Reconnecting for the target iqn.2016-06.com.netapp:09868cf1-034a-11e7-8ac6-d039ea1d28c3 (type: dr_partner, address: 192.168.188.1:65200). Reason: session login timed out.
[ClusterB-01:iscsi.session.stateChanged:notice]: iSCSI session state is changed to Reconnecting for the target iqn.2016-06.com.netapp:76acc4e4-034b-11e7-b81d-d039ea1d63df (type: dr_auxiliary, address: 192.168.188.2:65200). Reason: session login timed out.
- Sessions to different nodes randomly going up/down
 
cluster01A::*> storage iscsi-initiator show -status-oper down
                                                                       Status
Node Type Label    Target Portal      Target Name                      Admin/Op
---- ---- -------- ------------------ -------------------------------- --------
cluster01A-01
     dr_auxiliary
          mccip-aux-a-initiator
                   10.1.1.4:65200     iqn.2016-02.com.netapp:abcd1234efgh5678ijkl91011mnop1213
                                                                         up/up
              Failure Reason:  Operation timed out
          mccip-aux-a-initiator2
                   10.1.1.4:65200     iqn.2016-03.com.netapp:abcd1234efgh5678ijkl91011mnop1214
                                                                         up/down
              Failure Reason:  Operation timed out
     dr_partner
          mccip-pri-a-initiator
                   10.1.1.3:65200     iqn.2016-04.com.netapp:abcd1234efgh5678ijkl91011mnop1215
                                                                         up/up
              Failure Reason:  Operation timed out
          mccip-pri-a-initiator2
                   10.1.1.3:65200     iqn.2016-05.com.netapp:abcd1234efgh5678ijkl91011mnop121316
                                                                         up/down
              Failure Reason:  Operation timed out
- No physical layer issues
 
