IP Network Addressing - Design Phase

Hello all,

I'm looking to build a private network for training and development. I will be virtualizing my environment as much as possible and designing it for HA, FT, and best practices on all aspects as much as possible. I have included a network diagram to help put things into perspective on what I'm trying to accomplish. The diagram is not complete nor is it final.

My biggest problem is IP Addressing. I have a hard time wrapping my head around it. I've been able to plan out how I want to setup my ESXi Host boxes in terms of VLANS, my problem is the rest of the network.

This is what I have come up with so far:

VLAN 50 (native) - 145.21.1.x /16
   ESXi Host Management
VLAN 2933 - 145.21.10.x /16
   VMotion Traffic
VLAN 2934 - 145.21.11.x /16
   iSCSI Traffic
VLAN 2935 - 145.21.12.x /16
   Fault Tolerance in vSphere 4
VLAN 2936 - 145.21.13.x /16
   VM Server Traffic
VLAN 2937 - 145.21.14.x /16
   User Traffic
VLAN 2938 - 145.21.15.x /16 (When needed)
   VM Server Traffic
VLAN 2939 - 145.21.16.x /16 (When needed)

This VLAN configuration is based off a white paper I found for DR procedure in VMWare. It was suggested that I may have multiple VLANs and address ranges for my VM Servers which will depend on my server needs.

I want to prevent any regular user from changing or accessing anything directly on the network (telnet into a switch, remote console into a server, etc)...they can only log into a workstation to do work.

I want to logically separate my "management" servers from "production" servers from my "storage" server. Before I go further, here is what I think are management servers and production servers:

Management Servers

- vCenter Server
- DNS/DHCP/Active Directory
- HP OpenView
- HP SIM
- MS System Center
- ISA Server

Production Servers

- Exchange 2010
- Sharepoint 2007
- Office Project Server 2007
- SQL Server 2008

So to me, my management servers will go on VLAN 50, and production servers on VLAN 2937. I would then configure Private VLANS, Inter-VLAN Routing, ACLs, etc to shape the traffic accordingly. I would use my 8300 switch as my core, set all the vlans and set the default gateway for each vlan there. So VLAN 50 will have a default gateway of 145.21.1.254, and VLAN 2938 would have a default gateway of 145.21.15.254.

The user workstation would be 145.21.14.x /16 DNS: 145.21.1.x GW: 145.21.1.254

Does any of this sound right? Am I on the right track? I know design is based on the requirements on the network, I'm just trying to use "best practices" and be as secure as possible...regardless any suggestions, tips, thoughts are greatly appreciated!
potential-layout.jpg
LVL 2
BrassMonkey26Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

zwart072Commented:
watch out, your subnet mask prefix is not right in this way. You use /16 and i think it should be /24,
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
BrassMonkey26Author Commented:
i think the prefix is the least of my issues with this design...i'll be looking for another solution another time...thanks anyways.
0
BrassMonkey26Author Commented:
no contributions were provided.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Network Architecture

From novice to tech pro — start learning today.