IP PHONES ON Different VLAN then PC's 3

[FreightTrain]

I have a customer who has IP phones and PC's on the same network. They want to change it to 2 different VLAN's. My question is if they plug the network cable from the PC's to the back of the IP phone then will the PC's get there address for the IP phones's VLAN or will it pull it from the new dedicated PC's VLAN? sorry if this is a stupid question, and thanks for for helping.

"When all else fails call for backup

 

[Okkie26]

The pc will get there address from the native VLAN.

For the IP phones you need to setup a VOICE vlan.

 

[gwebster]

All of the above is true if the data network and phones are configured to work that way.

 

[kyle555]

More specifically, DHCP on the data vlan or LLDP tell the phones the voice vlan ID - L2QVLAN=10 for example.
The phone tags a DHCP request into the switch port on VLAN 10 in that case - it also gets a settings file that defines how to treat its port the PC plugs into, but the default is leave it alone and untagged.
Your data switch would be set for those ports to recognize traffic tagged as voice vlan as just that, and untagged traffic as belonging to the native vlan.

If you're using Avaya data switches, there's an auto config script to set that stuff up, otherwise, depending on what type of switch you're using, there's probably a config note on Avaya's support or DevConnect site to accomplish what you're trying to do.

 

[jayjr1105]

Here's the best way I found in separating the voice and data networks.

Setup option 242 and/or 176 on the Data network DHCP server with this string "L2Q=1,L2QVLAN=100,VLANTEST=0"

We'll assume data VLAN is 1 and Voice VLAN is 100. Then setup the LAN DHCP server on IP Office (make it a different subnet than the data network). The above string will tell the phones to look for a DHCP server on VLAN 100 when they naturally look to VLAN 1 for DHCP first. Any switches will need ports tagged 100 and untagged 1. Be sure to disable CDP and LLDP if your switch has it. We had a heck of a time with LLDP enabled on a Cisco switch.

You'll also need a route in your firewall allowing your data network to ping your voice network for IP office management.

Some people will just have their server or firewall do DHCP for data and voice but I found it easier to make that simple change to the DHCP server then just program IP office to hand out IP addresses to phones only. I also don't use the LAN2 (WAN) port on the IPO. I don't see a need to have 2 NIC's to worry about.

 

[FreightTrain]

Guys thanks for the fast response. This is very good info for me. I will let you know how it went, thanks again.

"When all else fails call for backup

 

[faqeel]

data vlan should be untagged and voicevlan should be tagged this will resolve your issues.

thanks,

 

[BTI09]

Has anyone setup a VPN tunnel between 2 Adtran Netvanta 3120 units? The customer has a Broadband connection in both locations and wants an IP phone off of their IPOffice at one location. Any insight is greatly appreciated, thank you!

 

[intrigrant]

@BTI09 it is not done to hijack a thread, start your own. Besides of that this is a Avaya IP Office forum and not a networking/VPN forum, you may have better luck in another forum

 

[intrigrant]

Basically it is a bad idea to join 2 VLAN's on one ethernet port and two separate DHCP servers is neither a good idea.
The question which remains is what the benefit is of using VLANs in this approach?

Using the two IP Office NIC's and one solid ( IP Office DHCP is considered as not solid ) DHCP server which serves both VLANs together with a good router ( not a layer 4 switch ) is the only and best way to deploy VLANs.

 

[Okkie26]

The benefit of VLANS?

eeh, voice prio ???

 

[intrigrant]

.... if that is not known the don't bother deploying VLANs and trow everything on the same network

 

[jayjr1105]

Using VLAN's helps separate voice and data traffic. It also helps if you have a class C network and you're already close to capacity. 50 phones will be a huge waste of IP addresses stolen from the data VLAN.

intrigtant, I don't see the Avaya DHCP server struggling with IP addressing for 20-50 phones to be honest. I don't see why joining 2 vlans on the same switch port is a bad idea either. We have done this for years. Phones are tagged 100 and data is untagged 1. You plug a phone in and it goes on 100 and the phones passthrough port still communicates on the data vlan. This is almost mandatory on some installs where the office's don't have two ethernet jacks. We have to use the phone's passthrough to hook up the workstations.

 

[jamie77]

VLANs are only any good if set to have the correct QoS settings. Without that, as Intrigrant said, just chuck it all together. Layer 3 switches should be able to handle DiffServ for priority. Comes setup in default on the ERS kit.

Only other reason would be down to subnet sizes.

Most of our customers keep the whole thing as separate network segments, with physically different voice and data switches. A handful have VLAN networks. The others, we just ask for or enable DiffServ our selves. Can't think of one customer with call quality issues due to the n/w.

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer

 

[jayjr1105]

You have to understand not everyone is going to be doing jobs for companies that can afford brand new switching just for their phone system. I work for SMB and 99% of our client base is SMB. We probably won't deploy a single IPO phone system with more than 50 users so it's unlikely that any of them will have separate networks for voice and data. Maybe some of you guys lean more towards medium/enterprise type of work where companies can afford to do it the "proper" way

 

[jamie77]

I've just done a 16 IP user primary school with a single ERS 3500 for the phones, so not quite true. (and a 9 user roofing company last week done the same)

Most of my companies work is SMB.

There is no "proper" way as a rule. Every site is different.

Above 30 users, it's quite often cheaper to provide ERS3500's and IP phones than DS30's as DS phones. Avaya offer good discounts for 20+ user IP sales at the moment, which I think includes the switches.

We still do quite a few Digi systems at the small end.

I'd love to do more medium enterprise than small, but those sales are much harder to come by. Yet to see a Server Edition, but hopefully this will change very soon with some new company focus.

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer