• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 497
  • Last Modified:

Wiring ESX Hosts SAN and Network

Wiring ESX Hosts SAN and Network

we have 4 ESX servers in production.
we purchased 2 more ESX servers.
I would like to know the procedure( the conventional way) to wire the new ESX servers to SAN Storage and Network.

if someone can give me a topolgy-like on how all the pieces get connected , that will really be appreciated.

Thank you
0
jskfan
Asked:
jskfan
  • 4
  • 3
  • 2
4 Solutions
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Best Practice assuming iSCSI (you do not mention which SAN)

1. Dedicated Storage Network consisting of at least two physical switches. (in a stack)

2. At least two network interfaces on your ESXi servers, connected to each physical switch.

3. Jumbo Frames enabled. (MTU=9000) -as per my EE Article

HOW TO: Enable Jumbo Frames on a VMware vSphere Hypervisor (ESXi 5.0) host server using the VMware vSphere Client

4. Two iSCSI VMKernel Interfaces arranged as per my EE Article

HOW TO: Add an iSCSI Software Adaptor and Create an iSCSI Multipath Network in VMware vSphere Hypervisor ESXi 5.0

5. other specialist tweaks, are stated by SAN Vendor.
0
 
jskfanAuthor Commented:
It is Fiber Andrew, forgot to mention that.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Then in fact that's a little easier.

You connect two HBAs with fibre to two physical switches, to create two paths.
0
SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

 
SouljaCommented:
On the network side (Production data) , create LACP Port Channels with  802.1q tagging on the switch(s) that the ESX server hosts connect to.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
@Soulja It's Fibre Channel! (and LACP is not supported on ESXi 5.1/5.5 for standard switches)
0
 
SouljaCommented:
@Hancock

I am not referring the Fiber Channel (Backend). I am referring to the front end. If LACP isn't supported then static port channels (LAGS) will suit just fine.

The author states
I would like to know the procedure( the conventional way) to wire the new ESX servers to SAN Storage and Network.
0
 
jskfanAuthor Commented:
So the standard way is :

Connect one HBA to Network switch 1 and connect another HBA to Network Switch2
Connect one HBA to Storage Switch 1 and connect another HBA to Storage Switch 2
Connect one Cat5 to iDRAC.

I am assuming HBA adapter can be used for both Network switch as well as Storage switch

in our environment I have seen 3  other Cat5 cables connected to ESXi, I wonder what would these be used for…
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes, that's correct.

Without more detailed screenshots of your hardware and networking, it's difficult to tell, what the other 3 Cat5 cables are doing!
0
 
jskfanAuthor Commented:
Thank You Guys!
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

  • 4
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now