Highlighted
JDSConsult
1 Copper

NX4 Failover - iSCSI Connectivity Lost

I have (2) NX4's (one active, one passive), I've exposed a LUN via iSCSI to a Clustered Hyper-V virtualization environment. When we fail the NX4 over to the 2nd one, our Hyper-V workloads hang and don't come back. [I believe this is probably expected behavior]

My main questions, prefaced with: We only configured iSCSI to see the 1st NX4 as we didn't get the 2nd one in until later.

  1. How does the NX4 handle the iSCSI connection transfer between them during failover? My understanding is the IP address is assumed by the 2nd NX4, so I want to know if iSCSI is handled the same way.
  2. Does the iSCSI Target Identifier remain the same when the NX4 fails, or do I have to configure and add the Target ID for the 2nd NX4 to my iSCSI Target.
0 Kudos
2 Replies
8 Krypton

Re: NX4 Failover - iSCSI Connectivity Lost

Hi, This looks like a question for the Support Forums.  I'm going to move this discussion there so someone can address it for you. -Stephanie

0 Kudos
8 Krypton

Re: NX4 Failover - iSCSI Connectivity Lost

Hi,

I've moved your question to the Celerra support forum where it should be addressed. Thanks!

0 Kudos