Network Guru: Info/Advice on VLAN with Data & Voice setup.

h2009

h2009

h2009

Associate
Joined
6 Jan 2008
Posts
316
Hi there,
The time has come where the my network needs to be split up, into VLAN's as there is too much broadcast traffic for my Voice and Data to live together.

At the moment my current setup is as follows: Very basic, all using dynamic IPs (without an expiring lease) - Voice and Data all on the same IP address 192.168.0.X

standardb.jpg


Now I'm thinking about going with the following setup.

Black line = Data traffic (IP 192.168.2.X)
Red Line = Voice (IP 192.168.1.X)
Blue = Virtual Link between the two (IP 192.168.0.X)

changedq.jpg



The hardware I current have is:

D-Link router DIR 655
Netgear Pro GS724AT (layer 2 advanced)
Netgear Pro GS716T (layer 2 smart)

All VLAN's need access to the internet, and the "Server" for the VOIP needs to be in DMZ).
And I need to a static connection so that a computer can be connected all VLANs at the same time so that I can change settings/etc when needed.

I'm planning to separate the Voice and Data onto different VLANs, but what I'm not sure about is how to go about connecting to switches, whilst maintaining the VLANS across them both.
I have 3 CAT5e cables running between the two switches (currently only one connected), so should I just use one cable for each VLAN'd port or will this cause IP conflicts?

Also to complicate matters, on the GS716T - there is a branch off which isn't shown where by there are computers and VOIP phones on the on the same switch (which doesn't have layering tech). So I'm thinking to set this port on the GS716T switch to 'general' and trying "tagging" the Voice data so get over this issue?

Due to the nature of this problem - I can't just change the switch as there will still be some computers which are connected to a VOIP phone (secondary LAN port).


If anyone can think of a better way of doing this I'd like your input.

(sorry for the crappy photoshop layouts!)
 
Why do you want to use 1 cable between the switces for each VLAN? why not simply create a trunk between the switches that allows traffic from all VLANs and prioritize the voice VLAN.
 
Its actually a lot bigger than, what is shown - that was just a simple setup.
Its actually 30 Voip extensions, 30 pc's and file servers.
 
It won't use three cables anyway unless you use an aggregated link. STP will block two cables. Just trunk one cable and put the server on 1 VLAN, PCs on another and voice on a third, fourth for management, fifth for native/wireless then just use whatever QoS mechanism you have to prioritise the voice traffic. Issue you will possibly have is the router as i doubt it will support multiple subnets and I also doubt the interface can be trunked. etc. etc. etc.

- Pea0n
 
Last edited:
Pea0n said:
It won't use three cables anyway unless you use an aggregated link. STP will block two cables. Just trunk one cable and put the server on 1 VLAN, PCs on another and voice on a third, fourth for management, fifth for native/wireless then just use whatever QoS mechanism you have to prioritise the voice traffic. Issue you will possibly have is the router as i doubt it will support multiple subnets and I also doubt the interface can be trunked. etc. etc. etc.

- Pea0n
Click to expand...

Ah ok - thanks for that.

Yes the router from what i can see doesn't support trucks, but it does support multicast IGMP members if that helps? Would the DrayTek Vigor 2930VN be any good?

Also is there any way that I can have dynamic IP address assigned - as its currently controlled by the router. There is an option for the switches to do it, but will that work across all the Vlans?
 
You don't want to use three cables with one for each VLAN. It can actually cause issues with some switches.

I'll be honest with you I can't actually work out what you're trying to do so I can't give you much advice.
 
BEst thing you could so is invest in a router that supports trunking on GBE/FA interfaces with the DSL WAN module. I.e. a Cisco model as it can also function as the DHCP server if need be with multiple subnets, provide trunk support, QoS and the WAN element :)

- Pea0n
 
You must log in or register to reply here.
Back
Top Bottom