Hi Bill,  The configuration you mentioned is valid and should work seamlessly.  The only concern is to keep VNXe3200 version software in latest code due to restriction of one IPv4 and one IPv6 address in older code (3.0.0.2960754).  This restriction has been removed in 3.0.1.3513260 code.  You may refer VNXe high availability document for network best configuration with iSCSI and NAS  Regards, Swapnil
Let's assume we have a VNXe 3200 and we want to use iSCSI, CIFS, and NFS, all with high availability.  I know we need to dedicate interfaces for iSCSI only.  So let's say we use Ethernet2 and Ethernet3 for iSCSI.  That leaves us with Ethernet4 and Ethernet5.  Can we put these interfaces into an LACP link aggregation group and use the LAG for both CIFS and NFS traffic?  CIFS would be on VLAN 10, for example, and NFS would be on VLAN 20, so we would specify the VLAN tag when creating the CIFS server and NFS server.  Any issue with this setup, having CIFS and NFS servers on the same interfaces?  Should they both be "owned" by the same SP, or could I have the CIFS server owned by SP A, and the NFS server owned by SP B, while still using the same physical interfaces?
Any issues with using the same interfaces for CIFS and NFS on VNXe 3200?