Not sure what route to take

I am in the middle of re doing the network and Firewall (I am a former cisco guy) but due to the difference in price I was unable to use Cisco.

procurveee  29XX and 1XXD Fortnet. having a difficult time making a decision and probably over thinking this but this is the first time I dont have a team to help plan things out. This would be much  easier in a brand new environment

Network Details
middle of a complete Network overhaul- Trying not to interrupt normal production at the same time but  I know there will some.

I already re wired the engineers with CAT6A Shielded. Previously IT admin didn't use a patch panel and has random home grade switches spanned across 60k sqft with no backbone cabling and 3 24 port smb unmanaged switches as the core. You cannot tell where any wires are going its a complete mess.. Ill upload a pic later today.

My Ideal -- Overall Ideal
To keep production flowing re wire one department at a time it worked for migration to new domain etc ! 1 CAT6A cable for data and future 10G speeds  and 1 CAT6 for VOIP ( keeps cost down. VOIP is not yet implemented that is a future project). create VLANS as I Go and keep the original LAN as management network once everything is said and done.

First Implantation-
Move Designers from old switch to new and setup a VLAN for them. Install New Firewall and use a router. Connect old switches to new firewall to keep everyone working\

VLAN10 -- These guys can Talk to everyone but office.
VLAN20 SHOP Need to see main directory same as engineers but cannot talk to Office -IT Management - or Managers
VLAN30 Office/Managers Can see everything but Management network
VLAN40 Management Segregated to admins only--Firewalls-Motion-etc...Exchange,DC Etc
VLAN60 Printers- Everyone can see them
VLAN70 Machines- Need to see shop
VLAN80 Guest
Now my question is do I need to put the file server and DC and all the servers on the on the management network and trunk the ones who can see it or have access? or whats the best way to do this

We have few I P  address and what I wanted to do since we have 3 WAN ports on gateway and 3 useable address I wanted to separate traffic guest/employees use .89 Exchange uses/web server uses .88 Is this a bad ideal? Create multiple pipes out.

Data Center

The messed up part of the Data Center since I had to do System's upgrade before the network. So I had no choice since the cables were not marked etc and recovery from disaster right before new hardware arrived ... 3 "core switches" unmanaged that connect everyone. I have Also Attached Pics if this is all garbled up

Just to many ways of doing this and only one person to think this over.

The question is WWEED * what would experts exchange Do*....How would my fellow engineers go about this or any flaws in this design ?
Chuck FinlyAsked:
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.

Don JohnstonInstructorCommented:
The question is WWEED * what would experts exchange Do*....How would my fellow engineers go about this or any flaws in this design ?
I think that you're going to need to be a little more specific.  

Now my question is do I need to put the file server and DC and all the servers on the on the management network and trunk the ones who can see it or have access?
You can go either way.  Personally, I like putting the servers on a "server network" if possible.  Makes it easier to manage access.

On the vendor selection, I'm a Cisco guy (been a CCSI since 1999). But I run into everything when consulting.  And if you can't go Cisco, I would go with HP.  You can't beat unlimited support.  And the CLI is close enough to Cisco that it's relatively easy to pick up.  There are a couple of diversions ("trunking" for example), but not impossible to overcome.
I love HP switches because they are cheap, have unlimited free support and lifetime (free) warranty.  Can't beat that. They work in the worst environments which is what I need.  We only do cisco routers but all Procurve switches.  Here is a great guide on Cisco and HP terminology and CLI reference.  like if I do it this way on a cisco what are the commands on the procurve.  

OMG, you're using Dell switches.  You'll be THRILLED with Procurve then.

If I was replacing all switches I would program new switches with my static addresses and all the vlans, program them and attach them to the old ones in series (uplink). test VLANs and routes then I would slowly migrate people over, moving the patch cables.  When the Dell's are empty, just move the uplink from the new switch to the router.  Then I would work on the router.  If it was just me doing all this work i would just do it step by step starting with the easiest which IMHO is the switches.

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
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.

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.