over the weekend i had and issue where i was creating a 2 node fail over cluster for high availability hyper-v. the cluster creation wizard was barking because each node had 2 adapters configured on the same iscsi subnet
iscsi-1 - 172.16.25.1
iscsi-2 - 172.16.25.2
iscsi-1 - 172.16.25.3
iscsi-1 - 172.16.25.4
i was getting a lot of packet loss between these adapters. I ended up updating the nic drivers and then teaming the nics together and all packet loss went away.
the SAN is a Equallogic PS4100E, isn't the default configuration to configure it the way I had it WITHOUT teaming my NICs?
Any thoughts? I am worried that teaming my iSCSI NICs might cause issues with Hyper-V. Does anyone know?
When using iSCSI MPIO, you can't also have those NICs teamed. MS doesn't support that. It's in the MS iSCSI users guide.
I believe, the iSCSI subnet needs to be excluded from the cluster.
Social Media and Community Professional#IWork4DellGet Support on Twitter - @dellcarespro
so how would i address the packet loss? i called dell for technical support (powerconnect switch engineer) and this was the recomendation. he said there was nothing wrong with my switch config.
I would open a case with Dell / EQL support. Problem with teamed / ISCSI MPIO is that on a link failure there will be a disagreement between them and will bring the node down.
What version of FW are you running on the array? It needs to be 5.2.1.
Looks like it is running 5.2.0
Still upgrade to 5.2.1, it has a few fixes over 5.2.0. Still best to open a case with Dell/EQL and the array diags and switch configuration can be reviewed.
Are you using the default VLAN on the Power Connect switch? What model is it?
2 x 6224 stacked.
I have a VLAN for ISCSI. But I do have a few servers as well as the Equallogic MGMT NIC using the default VLAN.
I also have a 3rd VLAN for cluster heartbeat but I don't thin anything is connected to it at this time.
Dwilliams62 is correct in that iSCSI NICs shouldn't be teamed. One thing you may want to do prior to calling support would be to make sure you have that update done and install SAN HQ (SAN Head Quarters). The reason I say that is because the SAN HQ will allow tech support to gather info as far as what is causing the dropped packets and will also give them more as to if there is also some latency that could be causing the issue. You will want to go to www.support.equallogic.com and login with your equallogic username and password. From there go to downloads and then SAN Head Quarters. The recommended version is 2.2.0. When you click on that it will take you to the download section and will also have the documentation for it as well if you want to look over the install guide. Let me know if you have any further questions and I would be happy to assist you with this EQL issue.
Get Support on Twitter @DellCaresPro
Download the Dell Quick Resource Locator app today to access PowerEdge support content on your mobile device! (iOS, Android, Windows)
Create a new VLAN for the Mgmt traffic as well. What FW is on the 6224's?
With regards to SAN HQ. Would I install the server and the client or just the client?
Can I install it on one of my R2 nodes?
It can be installed on the Windows server with out an issue. The only requirements is it has to be a windows box and it needs to have access to the network the iSCSI traffic runs on. That way it can help find where the bottle neck is at.
Correct, then you can install the client anywhere that can access that Node. So you can monitor from your LAN side network.
When trying to Add a group I keep getting "SAN HQ server failed to connect to the group"
I am using the group IP address and am able to PING it successfully.
For SNMP I am using "SNMP-trap" which is defined under Group Config / SNMP
FW on the 6224s is 220.127.116.11
If you want to allow a SAN HeadQuarters Client computer to add groups to the monitoring list, configure e-mail notification, or change the SNMP community name for a group, the computer must have read-write access to the directory and any network resources. One thing you may want to do is download the install and user guide and go to pg 32 where it breaks down the process of adding a group for monitoring. I hope this helps.