The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.
One of a set of tools we're offering as a way of saying thank you for being a part of the community.
Trunks on Dell 5424 iSCSi switches and VMware 4.1
Hi all,
We're trying to eliminate a storage iSCSI problem on the Dell MD3200i, 2x Dell 5424 switches, and 2x DELL R610 ESXi 4.1 hosts.
Dell's recommendation is to set different segment on each controller's port, but for that we'll have to use trunk since there are only 2 iSCSI ports which allocates on the R610 ports.
The question is, what is the best practice to set the trunk on the 5424 switches, and on the VMware, and if there are any other considerations when using LUN's over trunks in ESXi 4.1 environment.
Thank you very much in advance
We're trying to eliminate a storage iSCSI problem on the Dell MD3200i, 2x Dell 5424 switches, and 2x DELL R610 ESXi 4.1 hosts.
Dell's recommendation is to set different segment on each controller's port, but for that we'll have to use trunk since there are only 2 iSCSI ports which allocates on the R610 ports.
The question is, what is the best practice to set the trunk on the 5424 switches, and on the VMware, and if there are any other considerations when using LUN's over trunks in ESXi 4.1 environment.
Thank you very much in advance
Asked:
10-
10
1 Solution
Thanks for the swift reply.
Before start reading, what about the trunk and the physical NIC's limitation?
Before start reading, what about the trunk and the physical NIC's limitation?
Dear Andrew
the issue is that we have 4 port on each host but only two are available for the "trunk" purpose we need to configure to two port to connect with four network segments.
please see the Dell storage best practice config to do so.
Dell-Storage-Config.jpg
the issue is that we have 4 port on each host but only two are available for the "trunk" purpose we need to configure to two port to connect with four network segments.
please see the Dell storage best practice config to do so.
Dell-Storage-Config.jpg
hanccocka?
We will really appreciate your help here, since it's a production env, and backup's are keep failing due to a mis-configuration.
Thanks
We will really appreciate your help here, since it's a production env, and backup's are keep failing due to a mis-configuration.
Thanks
Man, trust me when I say - we're way over this (numerous tickets in Symantec and Dell).
We're at the point that both vendors demands to use the suggested best practice on the storage, in order that they'll keep supporting us.
Just to feed your curiosity - it's BackupExec 2010 R2, and they fail with many different reasons (at least 5 different errors).
Please assist with the configuration of the storage / switches (trunks) and the ESXi 4.1 u1 part.
Thanks
We're at the point that both vendors demands to use the suggested best practice on the storage, in order that they'll keep supporting us.
Just to feed your curiosity - it's BackupExec 2010 R2, and they fail with many different reasons (at least 5 different errors).
Please assist with the configuration of the storage / switches (trunks) and the ESXi 4.1 u1 part.
Thanks
I need to understand the failure of the Backup Software OR
If virtual machines are correctly working in your environment with SAN, I do not understand why the Vendors are stating it's a storage issue why Backup Software is failing.
Do you have any issues with your storage and vritual machines? (exclude the Backup Software at present)
Please post screenshots of networking, vSwitches for examination, but I at a loss here, because if Storage or Networking is not defined as Symantec or Dell recommend, and they not going to state it's incorrect??
If virtual machines are correctly working in your environment with SAN, I do not understand why the Vendors are stating it's a storage issue why Backup Software is failing.
Do you have any issues with your storage and vritual machines? (exclude the Backup Software at present)
Please post screenshots of networking, vSwitches for examination, but I at a loss here, because if Storage or Networking is not defined as Symantec or Dell recommend, and they not going to state it's incorrect??
Andrew Hi,
the Dell best practice is the picture that i Posted on 2012-03-19 at 10:29:15
the Symantec best practice is to backup directly to the virtual array, and not to "backup to disk folder"
as today.
we have a long history about it that include files and folder "lock"
at the filesystem level because of malfunction communication between the vmware hosts and the storage.
that's way we know for sure that the problem is with the storage config (we also double check that with Dell).
the storage is a SAN based storage with iScsi connection to the vmware hosts.
is it possible for us to make a phone call to better explain to you the history and the current state of the storage issue ?
thanks in advance.
the Dell best practice is the picture that i Posted on 2012-03-19 at 10:29:15
the Symantec best practice is to backup directly to the virtual array, and not to "backup to disk folder"
as today.
we have a long history about it that include files and folder "lock"
at the filesystem level because of malfunction communication between the vmware hosts and the storage.
that's way we know for sure that the problem is with the storage config (we also double check that with Dell).
the storage is a SAN based storage with iScsi connection to the vmware hosts.
is it possible for us to make a phone call to better explain to you the history and the current state of the storage issue ?
thanks in advance.
Im afraid all communication must be through the EE forum.
Im still at a real loss here, if you have setup as per Dell Best Practice, does Symantec agree this is Best Practice, Im surprised they would have the experience to know this.
Im still at a real loss here, if you have setup as per Dell Best Practice, does Symantec agree this is Best Practice, Im surprised they would have the experience to know this.
i'm posting her the screenshot of the storage event log and the network config of the vmware hosts ,and the V-center iscsi config.
the v-center is the pc that holds the mapping of the LUN's from the storage,
and functions as the Backup system PC.
first-host-config.JPG
Second-host-config.JPG
storage-event-log.JPG
v-center.JPG
the v-center is the pc that holds the mapping of the LUN's from the storage,
and functions as the Backup system PC.
first-host-config.JPG
Second-host-config.JPG
storage-event-log.JPG
v-center.JPG
have you considered setting up as per my best practice document, rather than a vSwitch per VMKernel Portgroup?
what you have implemented functions, but not considered best practice.
and why do Dell state you get those errors?
what you have implemented functions, but not considered best practice.
and why do Dell state you get those errors?
In situations like this where Vendors Dell and Symantec disagree over design and implementation, we often use VMware Professional services to check the implementation and sign off on it.
Once VMware have approved the configuration, we bounce back to Vendors to resolve.
Once VMware have approved the configuration, we bounce back to Vendors to resolve.
so you suggesting to see if the config is OK with vmware ?
and only then turn to the other vendors ?
and only then turn to the other vendors ?
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
HOW TO: Add an iSCSI Software Adaptor and Create an iSCSI Multipath Network in VMware vSphere Hypervisor ESXi 4.1
HOW TO: Add an iSCSI Software Adaptor and Create an iSCSI Multipath Network in VMware vSphere Hypervisor ESXi 5.0