If you have the additional 4 port I/O module, you can create 2 LACP port groups per SP – one port group using the onboard module, and one port group using the I/O module.
It sounds like your primary focus here is creating an LACP port group for CIFS, and a separate LACP port group for iSCSI. With your current setup, this can be done. We recommend cabling each SP identical, for failover reasons.
For detailed information regarding VNXe HA and specific examples, please see the “EMC VNXe High Availability” White Paper located on support.emc.com.
Right, I understand that and have read the document. It does a good job of giving an overview of the concepts but doesn't really get into specific scenarios.
What I wasn't planning on doing is allocating 4 ports for CIFS because it isn't necessary for our usage. What I was asking is if there may be a better way to configure this if, say, I wanted 2 ports in an LACP group for CIFS and wanted to use the other 6 ports for iSCSI (besides having 2 single ports left over only serving traffic individually).
Is this something I can accomplish by using MPIO on my Hyper-V servers? I'm fairly new to that concept and have some more reading/testing to do before I build the cluster and re-do our virtualization properly (I inherited a bit of a mess).
You are only going to be able to create 1 LACP port group per onboard NIC or I/O module, so if you create a 2 port LACP group, the other two ports that are not in use can not be used in an LACP port group.
You have the ability to assign 2 interfaces to an iSCSI storage server, so depending on your requirements, the other 2 ports could be used in this type of configuration. However, you still cannot use these 2 individual ports in an LACP port group.
eerreer
2 Intern
•
130 Posts
0
January 10th, 2012 06:00
Hello,
If you have the additional 4 port I/O module, you can create 2 LACP port groups per SP – one port group using the onboard module, and one port group using the I/O module.
It sounds like your primary focus here is creating an LACP port group for CIFS, and a separate LACP port group for iSCSI. With your current setup, this can be done. We recommend cabling each SP identical, for failover reasons.
For detailed information regarding VNXe HA and specific examples, please see the “EMC VNXe High Availability” White Paper located on support.emc.com.
KyleSTI
2 Posts
0
January 11th, 2012 09:00
Right, I understand that and have read the document. It does a good job of giving an overview of the concepts but doesn't really get into specific scenarios.
What I wasn't planning on doing is allocating 4 ports for CIFS because it isn't necessary for our usage. What I was asking is if there may be a better way to configure this if, say, I wanted 2 ports in an LACP group for CIFS and wanted to use the other 6 ports for iSCSI (besides having 2 single ports left over only serving traffic individually).
Is this something I can accomplish by using MPIO on my Hyper-V servers? I'm fairly new to that concept and have some more reading/testing to do before I build the cluster and re-do our virtualization properly (I inherited a bit of a mess).
eerreer
2 Intern
•
130 Posts
1
January 11th, 2012 10:00
You are only going to be able to create 1 LACP port group per onboard NIC or I/O module, so if you create a 2 port LACP group, the other two ports that are not in use can not be used in an LACP port group.
You have the ability to assign 2 interfaces to an iSCSI storage server, so depending on your requirements, the other 2 ports could be used in this type of configuration. However, you still cannot use these 2 individual ports in an LACP port group.