How do I restructure my network and implement VLANS?
Hi all,
We currently have 7 sites connected to the 192.168.0.0 /24 network and we are running out of IP addresses - only 3 currently available in the DHCP range (100-254), and 12 left in the static range (1-99).
I would like to restructure the network so that each site is on its own subnet, and also implement VLANs for Voice and Data at each site, something like this:
SAN: 192.168.99.0 VLAN 99
VMOTION: 192.168.101.0 VLAN 101
MGMT: 192.168.0.0 VLAN 1
SITE 1
DATA: 192.168.10.0 VLAN 10
VOICE: 192.168.11.0 VLAN 11
SITE 2
DATA: 192.168.20.0 VLAN 20
VOICE: 192.168.21.0 VLAN 21
SITE 3
DATA: 192.168.30.0 VLAN 30
VOICE: 192.168.31.0 VLAN 31
ETC...
I know this is a broad question, but I am not sure where to start. What do I need to do to keep everything operational while I implement the changes? Would this layout work?
We have 13 servers, 90 desktops, 61 IP phones, 30 network printers, 18 managed switches, 1 firewall, and 42 other devices on the network like wireless access points, cameras, and energy panels. Around 40 users access the wireless network with their own devices in addition to their desktops (iPhones, tablets etc.)
The need to change is immediate, as very soon there will be no more IP addresses available.
Where should I start? Please help experts!
We currently have 7 sites connected to the 192.168.0.0 /24 network and we are running out of IP addresses - only 3 currently available in the DHCP range (100-254), and 12 left in the static range (1-99).
I would like to restructure the network so that each site is on its own subnet, and also implement VLANs for Voice and Data at each site, something like this:
SAN: 192.168.99.0 VLAN 99
VMOTION: 192.168.101.0 VLAN 101
MGMT: 192.168.0.0 VLAN 1
SITE 1
DATA: 192.168.10.0 VLAN 10
VOICE: 192.168.11.0 VLAN 11
SITE 2
DATA: 192.168.20.0 VLAN 20
VOICE: 192.168.21.0 VLAN 21
SITE 3
DATA: 192.168.30.0 VLAN 30
VOICE: 192.168.31.0 VLAN 31
ETC...
I know this is a broad question, but I am not sure where to start. What do I need to do to keep everything operational while I implement the changes? Would this layout work?
We have 13 servers, 90 desktops, 61 IP phones, 30 network printers, 18 managed switches, 1 firewall, and 42 other devices on the network like wireless access points, cameras, and energy panels. Around 40 users access the wireless network with their own devices in addition to their desktops (iPhones, tablets etc.)
The need to change is immediate, as very soon there will be no more IP addresses available.
Where should I start? Please help experts!
Last Comment
naderz
How are your sites connected at the moment? And, are they all part of 192.168.0.0/24?
ASKER
They are connected via TLS, and yes all are on 192.168.0.0 /24
Please elaborate on connectivity. Are there routers (what kind?) and switches (what kind?) at the sites? Are the TLS connections in a hub-and-spoke configuration, or else? Where is the DHCP/DNS server?
It is theoretically possible to create the new networks without touching the existing and then switch over during a scheduled change.
It is theoretically possible to create the new networks without touching the existing and then switch over during a scheduled change.
ASKER
Default Gateway is a Cisco PIX 515e firewall at Site 1 which connects to the ISP router
Sites 1-7 have at least 1 managed switch (Some are Dell, some HP, some Cisco) which connects to the TLS
The TLS is in a hub and spoke configuration
DHCP server is at Site 1
Two DNS servers are at Site 1, and another at Site 2
Sites 1-7 have at least 1 managed switch (Some are Dell, some HP, some Cisco) which connects to the TLS
The TLS is in a hub and spoke configuration
DHCP server is at Site 1
Two DNS servers are at Site 1, and another at Site 2
The changes you have to make are pretty elaborate. Do you have access to consultants in your area that can help out?
Sounds like what you have right now is a flat network spanning all sites. Your plan of VLANing is correct but would require configuring routing, VLANing, possibly trunking, etc. These are not extremely difficult, but nevertheless very challenging if you have not done them before.
The basic idea would be to create the VLANs at each site's switch, trunk them to the site router so that it can direct packets to Site1 (or site2). If you don't have enough ports on the site switches to create the necessary VLANs ahead of time, then they have to be created on the day (probably night) of the change. The switches have to be able to do VLAN, trunking (Cisco term); some manufacturers call this tagging, etc. Same idea. The site routers will need to be configured for routing: dynamic routing is preferred (EIGRP); but static could work.
Sounds like what you have right now is a flat network spanning all sites. Your plan of VLANing is correct but would require configuring routing, VLANing, possibly trunking, etc. These are not extremely difficult, but nevertheless very challenging if you have not done them before.
The basic idea would be to create the VLANs at each site's switch, trunk them to the site router so that it can direct packets to Site1 (or site2). If you don't have enough ports on the site switches to create the necessary VLANs ahead of time, then they have to be created on the day (probably night) of the change. The switches have to be able to do VLAN, trunking (Cisco term); some manufacturers call this tagging, etc. Same idea. The site routers will need to be configured for routing: dynamic routing is preferred (EIGRP); but static could work.
ASKER
I have done VLAN and trunking, it has just been a long time... lol - I could probably handle it. I'll do some research to refresh my memory. I am just in the planning stage now.
I will get a router for each site. I think that is necessary before I can begin, correct? That, or a single router with 7 LAN interfaces?
I will get a router for each site. I think that is necessary before I can begin, correct? That, or a single router with 7 LAN interfaces?
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
We do have layer 2 connectivity between the sites. I will see about getting additional ethernet ports installed in our hub router and start planning the network layout.
Our IP phones do have built-in switches (Mitel 5200 and 5300 series) but I need to learn how to set the DHCP scopes up for this to work with the VLANS and trunking.
naderz thanks for your help! I will be closing this question since it is very broad and could be quite extensive. I will ask a new question if necessary for each step of the project, but I will be spending some time going through existing posts looking for my answers first.
Thanks again
Our IP phones do have built-in switches (Mitel 5200 and 5300 series) but I need to learn how to set the DHCP scopes up for this to work with the VLANS and trunking.
naderz thanks for your help! I will be closing this question since it is very broad and could be quite extensive. I will ask a new question if necessary for each step of the project, but I will be spending some time going through existing posts looking for my answers first.
Thanks again
Networking
Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.
102K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
