Yes, the VNX supports up to 8 virtual ports per 10Gbps or 1Gbps physical interface; just to mention it, on the CX4 (VLAN tagging was introduced in FLARE 29), it was up to 8 virtual ports per 10Gbps port and just 2 virtual ports per 1Gbps physical interface. 

Also, multiple VLAN's are supported on each physical interface which really is the only use case for virtual ports based on our iSCSI best practices where on each SP you should not have more than one interface sharing the same subnet.  Therefore, when a VLAN ID is provided, it should be unique; which is just another way of rewording the following supported configuration:

emc235739: "Changing configuration on one iSCSI port may cause I/O interruption to all iSCSI ports on this SP if using IP addresses from same subnet."

As for your proposed solutions, I am assuming the additional VLAN's are for host connectivity.  Therefore, I would like to note that the first proposal would not allow for the proper redundancy of each initiator having a path to both SP A and B.  Having VLAN 22 only on SP A would not allow an initiator on that same subnet to log into SP B (as it is only configured with a port on VLAN 24).  At a minimum, you should have a port on SP B configured also on VLAN 22.  Then, assuming you plan to have 2 iSCSI initiators per host (each initiator also on separate subnets), the latter proposal will support this configuration and allow you to keep one physical port dedicated to MirrorView traffic versus sharing with host connectivity.

I hope this makes sense.

Also, not sure if you saw the following often quoted KB article regarding iSCSI connectivity and best practices:

emc245445: "Facts, limitations, and recommended settings when using CLARiiON iSCSI"

You'll find reference to many things you need to consider such as (listing the main ones in regards to subnet assignment):

1) emc156408: "Problems with iSCSI hosts when iSCSI ports share the same subnet"

- Simply another KB article supporting what was mentioned in the response above

2) When assigning subnets, do *NOT* use the following:

a) 192.168.1.1 to 192.168.1.255

- subnet used for PPP connections to the SP's when needed

b) 128.221

- subnet used for internal routing with our Unified Platform (amongst CS's, DM's, and SP's)

- used also for the Service LAN ports on the SP's

- then again, this is a subnet owned by EMC and shouldn't be used anywhere else so it simply is making an honorable mention here

c) Same subnet as the out-of-band connections for both host and array which includes:

- mgmt subnet for host

- mgmt port for SPA, SPB, and CS(s)'s which themselves are required to be on the same subnet

etc...

Yes,

This makes sense, thank you for your reply Christopher. Your assumption is correct, the addtional VLANs and virtual ports are for host connectivity. It was our desire to keep an SP port isolated for Mirrorview if possible, and it sounds like we will be able to accomplish that.

Thanks again.