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

Basic Network VLAN and Subnet Architecture Advice, Please

We are looking at redesigning our network core with some new VLANs and subnets. (something much easier to manage than what we have now). I'm looking for some guidance, or at least a 'thumb's up' on what we're doing. Thanks!

Current Plan:

VLAN 100 -
Desktops, laptops, smartphones, end user devices, etc.

VLAN 110 -
VDI machines

VLAN 120 -
VoIP Phones

VLAN 130 -
VM Servers, ESXi hosts, SANs

VLAN 140 -
Network devices, switches, routers, etc.

VLAN 150 -

Note: This is a fiber channel network, so the hosts and SANs will have a couple FC and several gigabit NICs.

Is this a decent plan?
Do you think there is an issue with putting ESXi hosts and SANs in the same VLAN/subnet as VM servers?
Should printers and end user devices be split up?

Any other thoughts or advice are welcomed.
Paul Wagner
Paul Wagner
2 Solutions
Neil RussellTechnical Development LeadCommented:
Put your management networks separate. Have a VLAN for VM Servers and a seperate for HOSTS/SANs
What about VMOTION?
Why /22 and /23 Networks? /24's do just fine across the board.
Paul WagnerFriend To Robots and RocksAuthor Commented:
What is the benefit to separating the hosts/sans from the servers?

I do have one set aside for vmotion. Just didn't list it. Good eye, though.

/22 and /23 are because I will need more than 254 IP's for each respective subnet.
AkinsdNetwork AdministratorCommented:
Vlan or subnetting structure are design preferences per se.

The main considerations for subnetting are
1. Ease of Management (sales vlan, management vlan, managers vlan, server vlans, HR vlan etc) - apply rules per vlan
2. Security (eg finance vlan. executine vlan) - where you can allow access as desired
3. Performance (subnets with 510 or less hosts are generally recommended to reduce broadcast storm, congestion, collision, packet loss etc)

With that said, there is no general rule, but it is usually recommended to separate your server vlans from other vlans for the same reasons mentioned above. If none of the above will impact your topology, it is not a crime to lump everything together in one vlan. It is kind of similar to having Admin building or Admin floor separate from other staff buildings or floors. At the same time, there are companies that have both admin and general staff all in the same place.

Bottom line, it is simply based on informed design preference.

Your setup looks good if it serves the purpose intended.
You are doing architectural design and that must be focused on your goals.
Start by setting up goals for your network
Then design your network based on the goals set.
If your design meets or satisfies your goals, then you have a perfect topology. The other main point to always put into consideration is room for growth (put a real figure on projected growth and make room for it in your design) eg In 5 years, the comapany is expected to triple its size and expand by adding 3 branches or sites.

I believe you get the logic. Consult your Business Intelligence office, or CEO or any executive to have clear understanding on the business objective. This will help you set your goals which in turn will help you design a perfect topology
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

Featured Post

We Need Your Input!

WatchGuard is currently running a beta program for our new macOS Host Sensor for our Threat Detection and Response service. We're looking for more macOS users to help provide insight and feedback to help us make the product even better. Please sign up for our beta program today!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now