Voice VLAN with HP V1910 switches
After Hurricane Sandy my organization lost all copper based phone service and Internet access. We currently are connecting via a FIOS line (I know it's not ideal but, at the moment, we don't have many options)
Since we are stuck without phones we have decided to use Broadview VoIP to at least get some kind of phone service. (When we can get Broadview service again we will get a dedicated line for the phones)
The problem I have is that I am not experienced with VLAN's and I am having a hard time getting the traffic separated.
The computers are connected to the phones since we only have one network port in each office.
What we are trying to do is to have the phones receive IP addresses from the voice VLAN from a Sonicwall firewall DHCP and the computers will receive addresses from DHCP on a Windows server.
Can someone help to point me in the right direction to get all of this set up correctly?
Thanks
Since we are stuck without phones we have decided to use Broadview VoIP to at least get some kind of phone service. (When we can get Broadview service again we will get a dedicated line for the phones)
The problem I have is that I am not experienced with VLAN's and I am having a hard time getting the traffic separated.
The computers are connected to the phones since we only have one network port in each office.
What we are trying to do is to have the phones receive IP addresses from the voice VLAN from a Sonicwall firewall DHCP and the computers will receive addresses from DHCP on a Windows server.
Can someone help to point me in the right direction to get all of this set up correctly?
Thanks
Jody Lemoine
It's going to depend largely on what kind of phones you have. Got a make/model for me? Also, how many phones do you have?
ASKER
Thanks for your response.
We have about 100 Mitel 5330 phones.
We have about 100 Mitel 5330 phones.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I ran through those steps and it's still not working. Swapped in a Fortinet for the Sonicwall, and connected my phone directly to the firewall. The phone gets an IP on the voice VLAN, but is stuck at "Contacting Server."
When I connect to the switch, the phone sees the DHCP server, then releases its address and looks for one on the voice VLAN. I can't get an IP on the voice VLAN, so something is missing on that side as well.
When I connect to the switch, the phone sees the DHCP server, then releases its address and looks for one on the voice VLAN. I can't get an IP on the voice VLAN, so something is missing on that side as well.
Is the firewall handing out all of the required options in its DHCP scope? If it isn't, the phone isn't going to know how to connect.
ASKER
Sorry for the delay guys but here is the quick version regarding how we got everything to work:
The main fix for the phones was removing all switchports from the built-in "Voice VLAN" option on the switch. I did a little research and that option doesn't actually tag the traffic, it just listens on that VLAN, and was apparently conflicting with the VLAN we created for the phones. I found a posting somewhere that said removing the built-in voice VLAN fixed someone's problem, and sure enough it was the fix here as well.
Otherwise we had everything set up correctly. I created a VLAN 200 on the switches, and tagged all ports for that VLAN, leaving all ports untagged on VLAN 1. (The tag/untag nomenclature is a conversation for another time, HP does things different than Cisco and other vendors, but just know that it works now.) I then created VLAN 200 on the SonicWall, as a sub-interface to the X0 (LAN) port. Next I added the Mitel-specific string to the existing DHCP scope on the network server, and also created a DHCP scope on the SonicWall for the VLAN 200 interface with the same settings.
When the phones are plugged in, they don't have a VLAN. They find the network server as the DHCP server, which tells the phones to go find a DHCP server on VLAN 200, along with a few other Mitel/Broadview settings. The phones then search on VLAN 200, where they find the SonicWall giving out IPs, with the Mitel/Broadview settings again. They get an IP on VLAN 200 and contact the Broadview servers for the rest of their settings. The traffic on VLAN 1 and VLAN 200 is separated so the voice and data traffic won't cause collisions on the switches.
Thank you for all of the help leading us in the right direction.
The main fix for the phones was removing all switchports from the built-in "Voice VLAN" option on the switch. I did a little research and that option doesn't actually tag the traffic, it just listens on that VLAN, and was apparently conflicting with the VLAN we created for the phones. I found a posting somewhere that said removing the built-in voice VLAN fixed someone's problem, and sure enough it was the fix here as well.
Otherwise we had everything set up correctly. I created a VLAN 200 on the switches, and tagged all ports for that VLAN, leaving all ports untagged on VLAN 1. (The tag/untag nomenclature is a conversation for another time, HP does things different than Cisco and other vendors, but just know that it works now.) I then created VLAN 200 on the SonicWall, as a sub-interface to the X0 (LAN) port. Next I added the Mitel-specific string to the existing DHCP scope on the network server, and also created a DHCP scope on the SonicWall for the VLAN 200 interface with the same settings.
When the phones are plugged in, they don't have a VLAN. They find the network server as the DHCP server, which tells the phones to go find a DHCP server on VLAN 200, along with a few other Mitel/Broadview settings. The phones then search on VLAN 200, where they find the SonicWall giving out IPs, with the Mitel/Broadview settings again. They get an IP on VLAN 200 and contact the Broadview servers for the rest of their settings. The traffic on VLAN 1 and VLAN 200 is separated so the voice and data traffic won't cause collisions on the switches.
Thank you for all of the help leading us in the right direction.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If the information provided was useful but was not a complete solution and required further research, this warrants accepting the comment with a B or C grade and not just a 0-point closure.
Not a problem. It's an easy mistake to make. I'm glad you managed to get everything working.
ASKER
I'm sorry about the poor grading-it was an oversight that was done quickly without enough thought