- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Setup and Networking
- >
- Re: VMware dvSwitch Design Question
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-29-2014 02:51 PM
тАО08-29-2014 02:51 PM
Hi,
I am a future (proud !) owner of a CS210, and I plan to refresh my vSphere design at the same time by switching to dvSwitch.
So, here is my question concerning dvSwitch and LACP:
I have 3 esxi with 8 gigabit cards each and a stack of 4 Cisco 3750G.
I'll use iSCSI (prod) and NFS (backup) as storage protocols.
I'll also plan to use 2 dvSwitch:
- 1 with 4 uplinks using LACP for VM traffic, VM management, NFS, and vMotion,
- 1 with 4 uplinks using iSCSI bindings for iSCSI (of course)
Is there any тАЬbetterтАЭ/more optimized designs (like only 1 dvSwitch with 8 uplinks and overriding failover order for iSCSI) ?
Note: 10 gigabits network cards are not an affordable solutions for the moment.
Thanks for any advice.
Jeremy
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-02-2014 03:36 AM
тАО09-02-2014 03:36 AM
SolutionJeremy,
May be worth having a read of the following article (non-Nimble) about dvSwithes first:
http://www.yellow-bricks.com/2009/09/24/dvswitch/
Some discussion on pros/cons.
Can't say I've seen anything specifically about dvSwitches with Nimble.
Given some of the comments in the post I'd probably avoid using 1 dvSwitch with 8 uplinks and overriding failover order for iSCSI and have some (if only logical) seperation between iSCSI traffic and other traffic.
Have you read the Nimble VMWare integration guide on InfoSight:
This gives 2 optons with standard vSwitches, using one vSwitch for all iSCSI with multiple vmnics (and overriding failover order) OR using multiple vSwitches (one vmnic per switch, no overriding failover order required).
If you are using dvswitches then I assume you are running Enterprise Edn of ESX, so also have a look at the Nimble Connection Manager (NCM) where you can use a Nimble PSP, full details in the document link above.
Regards
Phil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-02-2014 03:48 AM
тАО09-02-2014 03:48 AM
Re: VMware dvSwitch design question
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2014 12:48 PM
тАО09-15-2014 12:48 PM
Re: VMware dvSwitch Design Question
Hi Jeremy,
While there are a number of design criteria to consider for your question, I'll mention just a couple for now. Be aware that VMware recommends putting standard 1500 byte frames on a separate switch than jumbo frames (if you're using jumbo frames). I can't find my reference for this at the moment, but I'm fairly sure that goes for versions of ESXi below v5.5. It will work with both frame sizes on one switch, it's just that it is possible to have problems. Also be aware that the 3750G ASIC, which is the hardware-level switching that happens before the IOS software gets to examine the traffic, has a surprisingly low throughput capability and you may have microburst problems that cause the ASIC to drop packets (as observed in commands such as "sh platform port-asic stats drop gigabitEthernet x/x/x") before QoS gets to see it.
Ray