Solved

How to optimally configure a switch for use with servers?

Posted on 2013-05-24
3
264 Views
Last Modified: 2013-05-24
Hi,

I'm using an HP ProCurve 4204vl switch and our VMWare servers, our NAS and our workstations are all connected to it. I doubt though that this is the best way to do it ... shouldn't the traffic by the servers and the NAS be somewhat separated from the traffic by the workstations? Although, of course, all need to communicate with each other.

There are virtual servers on the NAS that run on the VMWare hosts: shouldn't they be connected somewhat more 'intimately' (VLANs?) ... ?

(the whole infrastructure is going to be upgraded though at some point soonish so that the VMs don't have to run on NAS anymore but on a SAN).

Thank you.
0
Comment
Question by:Xeronimo
  • 2
3 Comments
 
LVL 6

Expert Comment

by:BurundiLapp
ID: 39193755
Is it just your servers that require connection to your NAS?

If so then you would ideally put in a seperate switch to connect to the NAS on seperate NIC's on the VMWare Hosts.

If that isn't an option then you would VLAN off the connections to the NAS but ideally still have them on seperate NIC's to the LAN connections on the VMWare Hosts.

As for your workstations it would be best to have them on cheaper edge switches that plugging them into a core switch put of course it depends on the number of workstations you're talking about.
0
 

Author Comment

by:Xeronimo
ID: 39193770
> Is it just your servers that require connection to your NAS?

Yes, although there's one server that's located in another room that needs access to it as well as a backup store (via Veeam). So I guess that's like having a workstation needing to access the NAS?

> If so then you would ideally put in a separate switch to connect to the NAS on separate NIC's on the VMWare Hosts.

So if there were two NICs on the server I'd use one to connect to that separate switch and one to connect to the main switch?

The NICs would still all have our regular IP addresses or would I need to separate it on that level as well? And is this really worth all the trouble as far as speed and reliability are concerned?

> If that isn't an option then you would VLAN off the connections to the NAS but ideally still have them on seperate NIC's to the LAN connections on the VMWare Hosts.

Ok

> As for your workstations it would be best to have them on cheaper edge switches that plugging them into a core switch put of course it depends on the number of workstations you're talking about.

About 40 workstations. They connect via a patch panel to the ProCurve.
0
 
LVL 6

Accepted Solution

by:
BurundiLapp earned 500 total points
ID: 39193797
Yes, although there's one server that's located in another room that needs access to it as well as a backup store (via Veeam). So I guess that's like having a workstation needing to access the NAS?

I'd route it through the internal cabling to connect to the LAN & NAS switches if you have enough free ports to do this.

So if there were two NICs on the server I'd use one to connect to that separate switch and one to connect to the main switch?

Yes although the ideal scenario is at least two bonded NIC ports per connection type so you would need four NIC ports, two bonded together for the LAN and two bonded together for the NAS.  It's also good practice to have multiple switches for the core LAN and Core NAS/SAN connections for failover redundancy.

The NICs would still all have our regular IP addresses or would I need to separate it on that level as well? And is this really worth all the trouble as far as speed and reliability are concerned?

Put the LAN on one IP range and the NAS on a seperate IP range to aid in routing configuration on the hosts and VM's, if you are spending the money on a proper SAN it's recommended to seperate the LAN and NAS/SAN connections from each other, the data requirements are usually different, your NIC settings may need to be different to get the setup working optimally and it becomes a problem changing settings if you are using the NIC's for multiple roles.

About 40 workstations. They connect via a patch panel to the ProCurve.

Depending on your workstation requirements you could put in 100mb desktop switches with dual gigabit uplinks to the core switches, if you need gigabit to the workstations then get another of the core switches you have and stack them together using the HP stacking modules. (i've not checked if that switch can be stacked though) and your workstations can go into that stack.

Hope that helps.
0

Featured Post

Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

Join & Write a Comment

Suggested Solutions

Title # Comments Views Activity
Multiple Static IP addresses on Router 14 73
KVM switch 7 25
HSRP needed? 4 31
stacking switches 2 27
 One of the main issues with network wires is that you never have enough.  You run plenty and plan for the worst case but you still end up needing more.  What many people do not realize is with 10BaseT and 100BaseT (but not 1000BaseT) networks you …
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now