looking for some network advice

[rickr2010]

Hello,

I would like to get someone’s opinion on the following changes I would like to make?

• Am I going in the right direction?
• Is this the correct direction 
• What would you do?

Just some Facts:

The current system is a mixture of old brocade and cisco switches and I would like to replace all with HPE switches. And setup VLANs, place DHCP on the network and the company has 1 location with approx. 175 users, 250 devices, and 85 servers mostly virtualized. All running on 3 VLANs.

I would like to get some feedback on the following changes I want to make during the 

Network cutover:

• Would like to change over the Main network subnet from 192.168.1.0/24 to 192.168.10.0/24 Change from 1.0 network to 10.0 network 
• change or move Server, Printers, and other equipment to their respective VLANs to simplify network traffic, this can be moved at another Time, not during the cutover
• Separate Desktop phones and computers to their own network ports to increase network port speed to the users’ devices (Currently all laptops and desktops are connected through the ShoreTel phone, which only allows the user to get 100MB network connection), this would increase user network connection to 1GB connection.
• Move the wireless to its own VLAN and separate the WIFI networks, Main and GuestMove the building lighting controls to its own VLAN to separate it from our main network
• Move the DHCP Service for each VLAN to the Network to improve network speed and offload this service from the Windows server. This will ensure if the Domain controller was ever down users could always connect to the network shares with cached user credentials and still be able to get to network shares and printers.
•  If the Server DHCP was ever down users could always connect to the network shares with cached user credentials and still be able to get to network shares and printers.

These also can be moved or separated at another time, just wanted to get some feedback on these items

[Ihaqueit]

As per your query,

Too much load better to go with.

1. HPE 8200 series for core switch( Main backbone of your network)

2. For end user side Aruba 2930 series best option

3. Connectivity from fiber to fiber

What you need all available, its depend how you configure the network.

[parnassus]

Hello @rickr2010, you wrote:

"The current system is a mixture of old brocade and cisco switches and I would like to replace all with HPE switches"

What do you mean with HPE Switches exactly?

Currently there are three different main groups of Ethernet switch series under the big HPE umbrella (HPE owns Aruba Networks so currently marketed Aruba Switches - such as the Aruba 2540 or the Aruba 5400R zl2 - are de-facto HPE...that's to say that if you generically write "HPE" then we should include HPE and HPE Aruba so Aruba).

• HPE FlexFabric/FlexNetwork switch series based on Comware OS.
• Aruba for edge and campus based on ArubaOS-Switch operating system (ArubaOS-Switch = AOS-S <- some of those are the development of legacy HP ProCurve that - years ago - run using the HP ProVision OS, just to say).
• Aruba for edge and campus based on ArubaOS-CX operating system (ArubaOS-CX = AOS-CX)

So it's important to understand what you're planning to deploy (at edge and/or core) because what you want to do can be done for sure but there are CLI differences among those series.

[DavidJP]

• Am I going in the right direction?
• It certainly seems like you are.
• Is this the correct direction 
• See above.
• Segregating the network, thinking of performance, providing gigabit to each endpoint
• What would you do?
• I would consider DNS to ease the cut over, so users go to printer1 instead of 192.168.1.23, this will probably mean you need to leave the server in place as a possible failure point, perhaps you could make a redundant pair if it is that critical.
• You haven't spoken about a firewall or ACLs in the switching. I would look into both of those. It sounds like you will have to spend some money here, adding a firewall may enable remote access, etc for users which they may see as a benefit to justify the effort and cost.

It sounds like you are going in the correct direction.

Segregating the network, considering performance.