While the VNXe does not run DART, it does act similarly to DART and shares a lot of functionality with Celerra/DART.  For network HA the VNXe acts a bit differently from Celerra though. Since Celerra used an Active/Passive model, you would build network redundancy within each datamover to handle network failures, and then duplicate the config on the passive datamover in the event of datamover failure. In Celerra configurations, this usually ended up employing the FailSafe Network and resulted in some ports being designated as passive which reduced overall bandwidth available to the datamover. VNXe is different due to its Active/Active model.  “For network high-availability features to work, the cable on each SP needs to have the same connectivity. If Port 0 on SPA is plugged in to Subnet X, Port 0 on SPB must also be plugged in to Subnet X. This is necessary for both server and network failover. If a VNXe server is configured to use a port that is not connected on the peer SP, an alert is generated. Unisphere does not verify if they are plugged in to the same subnet, but they should be, for proper failover. If you configure a server on a port that has no cable or connectivity, the traffic is routed over an SP interconnect path to the same port on the peer SP (just a single network connection to the entire system is not recommended).” --Page 30, EMC VNXe Series Storage Systems, A Detailed Review  “Network paths – The VNXe supports network pass-through to provide network path redundancy. If a network path becomes unavailable due to a failed NIC, switch port, or bad cable, network traffic is re-routed through the peer SP using an inter-SP network, and all the network connections remain active.” --Page 31, EMC VNXe Series Storage Systems, A Detailed Review  With this in mind, I personally would create an LACP group of all ports on SPA connected to one switch and an LACP group of all ports on SPB connected to a different switch. That way you get the benefit of ALL ports for traffic, network switch redundancy, and SP redundancy.  Description of SP Active/Active failover…  “When an SP experiences hardware or software failure, reboots, or a user places it in Service Mode, a failover occurs. Storage servers that use the out-of-service SP fail over to the other SP if it is available, with minimal disruption between the VNXe system and connected hosts. … After the SP is available again, the storage servers fail back to the original SP. The failback policy can be configured through Unisphere.”  Richard J Anderson
WRT VNXe 3100 configuration, and link failover and such, here’s what I don’t quite understand:  The docs refer to the two storage processors on the system as SP’s.  This is terminology held over from CLARiiON, and strongly implies to me that the SP’s run active/active.  But I also know that there is something analogous to  DART under the covers, allocating iSCSI LUNs and NAS shares/exports.  So, how does this work?  Is this DART-like code running on just one SP at a time?  Both?  If both, then what?  What does that mean from a networking and storage access perspective?  All LUNs and NAS shares/exports available on all configured network ports?  I don't understand, and I haven't found a document that explains it.  Thanks, Eric
VNXe Networking Questions