Solved

Basic Network VLAN and Subnet Architecture Advice, Please

Posted on 2014-10-29
3
437 Views
Last Modified: 2014-11-01
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 - 172.16.100.0/22
Desktops, laptops, smartphones, end user devices, etc.

VLAN 110 - 172.16.110.0/23
VDI machines

VLAN 120 - 172.16.120.0/24
VoIP Phones

VLAN 130 - 172.16.130.0/24
VM Servers, ESXi hosts, SANs

VLAN 140 - 172.16.140.0/24
Network devices, switches, routers, etc.

VLAN 150 - 172.16.150.0/24
Printers


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.
0
Comment
Question by:Paul Wagner
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 37

Assisted Solution

by:Neil Russell
Neil Russell earned 150 total points
ID: 40411966
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.
0
 
LVL 5

Author Comment

by:Paul Wagner
ID: 40412012
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.
0
 
LVL 18

Accepted Solution

by:
Akinsd earned 350 total points
ID: 40412571
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
0

Featured Post

Webinar: MariaDB® Server 10.2: The Complete Guide

Join Percona’s Chief Evangelist, Colin Charles as he presents MariaDB Server 10.2: The Complete Guide on Tuesday, June 27, 2017 at 7:00 am PDT / 10:00 am EDT (UTC-7).

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Network ports are the threads that hold network communication together. They are an essential part of networking that can be easily ignore or misunderstood, my goals is to show those who don't have a strong network foundation how network ports opera…
Outsource Your Fax Infrastructure to the Cloud (And come out looking like an IT Hero!) Relative to the many demands on today’s IT teams, spending capital, time and resources to maintain physical fax servers and infrastructure is not a high priority.
In this video we outline the Physical Segments view of NetCrunch network monitor. By following this brief how-to video, you will be able to learn how NetCrunch visualizes your network, how granular is the information collected, as well as where to f…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

691 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