Vlan Configuration
Hi experts....my first foray into Vlan's...how exciting ;)
Here's my scenario. Just looking for advice on how best to configure this to suit the needs of our business.
Subnet 1 - Is our main network environment containing SBS2011 & around 10 workstations..all functioning fine. Ip Range 192.168.0/24.
We have commissioned a 3rd party contractor to install a WIFI setup for a call system used in our environment. They have installed all of their own hardware which i will call Subnet 2.
Subnet 2 - The WIFI network. IP Range 192.168.1/24. Has a number of access points we would like to take advantage of, & apparently can. Their system is basically for their own internal usage, however as they require remote access for troubleshooting, their is a network cable running from a small router in their cabinet to our router (both netgears) which gives internet connection....now
To take advantage of this Wifi infrastructure, i would like to connect these 2 subnets in such a way that our staff can connect to the Wifi & be able to access the internet as well as our internal network on the 0/24 range.
I've purchased some new equipment (current is outdated), which consists of a Draytek 2830n Router and a HP 2620-24 PoE+ Switch (layer 3 i believe)
My idea is to put all the office staff computers etc + the SBS server in the default Vlan & connect their network cable to a dedicated port on the switch in a separate Vlan..This is where my experience, or lack of it, has me a little unsure. Do i need to switch on IP Routing?, any tagging or trunking?
I'm told their equipment supports Vlan & i don't believe the 2 subnets need to be locked down from each other to any great extent. We simply want to take advantage of the investment already made on the WIFI infrastructure.
I'm pretty sure this is not a huge job, but would really appreciate some advice for the experts in this area.
Thanks
Here's my scenario. Just looking for advice on how best to configure this to suit the needs of our business.
Subnet 1 - Is our main network environment containing SBS2011 & around 10 workstations..all functioning fine. Ip Range 192.168.0/24.
We have commissioned a 3rd party contractor to install a WIFI setup for a call system used in our environment. They have installed all of their own hardware which i will call Subnet 2.
Subnet 2 - The WIFI network. IP Range 192.168.1/24. Has a number of access points we would like to take advantage of, & apparently can. Their system is basically for their own internal usage, however as they require remote access for troubleshooting, their is a network cable running from a small router in their cabinet to our router (both netgears) which gives internet connection....now
To take advantage of this Wifi infrastructure, i would like to connect these 2 subnets in such a way that our staff can connect to the Wifi & be able to access the internet as well as our internal network on the 0/24 range.
I've purchased some new equipment (current is outdated), which consists of a Draytek 2830n Router and a HP 2620-24 PoE+ Switch (layer 3 i believe)
My idea is to put all the office staff computers etc + the SBS server in the default Vlan & connect their network cable to a dedicated port on the switch in a separate Vlan..This is where my experience, or lack of it, has me a little unsure. Do i need to switch on IP Routing?, any tagging or trunking?
I'm told their equipment supports Vlan & i don't believe the 2 subnets need to be locked down from each other to any great extent. We simply want to take advantage of the investment already made on the WIFI infrastructure.
I'm pretty sure this is not a huge job, but would really appreciate some advice for the experts in this area.
Thanks
ASKER
" I would guess that their router is already performing routing/NAT'ing."
Yes, they have a small router that we supplied to allow them to access the internet on our subnet. It's a direct router to router connection with static routes set in both. Their server is the only device currently using it. The server nic gateway is set to our router, 192.168.0.1.
"At a guess, their devices are all connected to their own switch, which is then connected to one port on their router?" - Correct, which is then connected to our router.
What we would like to be able to do is to remove the small router in their rack, migrate ours to the Draytek router, set up a separate Vlan for them with an ip on their range which will give any of their equipment access to the internet through our Draytek router.
Hope that makes sense.
Yes, they have a small router that we supplied to allow them to access the internet on our subnet. It's a direct router to router connection with static routes set in both. Their server is the only device currently using it. The server nic gateway is set to our router, 192.168.0.1.
"At a guess, their devices are all connected to their own switch, which is then connected to one port on their router?" - Correct, which is then connected to our router.
What we would like to be able to do is to remove the small router in their rack, migrate ours to the Draytek router, set up a separate Vlan for them with an ip on their range which will give any of their equipment access to the internet through our Draytek router.
Hope that makes sense.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Just so i am clear, if i remove the router they currently use, do i run the cable from their network from their switch into a port on our new L3 switch, configure a separate VLan and add that port + the port that connects the switch to the interface on the draytek?
Or is there another way to do it?
Or is there another way to do it?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thankyou
At a guess, their devices are all connected to their own switch, which is then connected to one port on their router?
If so, then the broadcast domains are already isolated from each other, and you don't need to worry about VLANs.