This post is more than 5 years old
14 Posts
0
41809
April 24th, 2015 06:00
Interface PC8024 with existing voice VLAN (100) on HP 2910 switches
We've added our first Dell PowerConnect 8024 switch to an existing network consisting of HP 2910 switches. We have only 2 VLANS configured: the default (1) and voice (100). On the HP switches all ports in the default VLAN are set to "untagged" and all ports in the voice VLAN are set to "tagged".
I need to configure the PC8024 to coexist with the existing network so that the Mitel phones can communicate. We are not familiar with the PC8024 switch, are evaluating it as a potential solution for upgrading our backbone and DR subnet from 1Gb to 10Gb. For the backbone we need the voice traffic to be handled properly, so we need to configure the 8024 to work with the existing voice VLAN.
What VLAN configuration settings do we need on the PC8024 to coexist with the existing network configuration for the voice (100) VLAN on the HP switches?
DELL-Josh Cr
Community Manager
•
9.6K Posts
•
43K Points
0
April 24th, 2015 12:00
Voice VLAN allows you to specify what the VLANs are, so you should be able to use VLAN 1, but if you are using VLAN 1 and 100 you probably could just create VLAN 100 and not bother with the voice vlan stuff. What port mode is the port that you are trying to set to tagged in? Access mode can only do untagged. If it was general mode you could set it to tagged of 100 and a PVID of 1 which would put untagged traffic on vlan 1.
TLeBlanc22
14 Posts
0
April 24th, 2015 11:00
Excellent, will check it out.
The key for us is that we're not using existing Dell/Foundry, Cisco or similar technology. We're using HP switches, a Mitel 5000 phone switch and various Mitel phones, connecting via DHCP options to a separate IP subnet and VLAN, using common switches & ports with the default VLAN network.
I need to "match" the existing network.
Thanks, Josh.
--Terry
DELL-Josh Cr
Community Manager
•
9.6K Posts
•
43K Points
0
April 24th, 2015 11:00
The GUI instructions are on page 587 http://downloads.dell.com/Manuals/Common/PowerConnect_8024-and-f-UG_en-us.pdf
TLeBlanc22
14 Posts
0
April 24th, 2015 11:00
Thanks for the links, Josh. I'll check 'em out...to see if they get me where I need to go.
Stay tuned...
DELL-Josh Cr
Community Manager
•
9.6K Posts
•
43K Points
0
April 24th, 2015 11:00
Hi,
You can use the voice vlan command to setup a tagged vlan for voice and the untagged vlan for data. Page 830 http://downloads.dell.com/Manuals/Common/PowerConnect_8024-and-F-CLIRef_en-us.pdf
This is for another switch, but the concepts are the same http://en.community.dell.com/techcenter/networking/w/wiki/configuring-dell-powerconnect-55xx-series-switch-voice-vlan
http://www.dell.com/downloads/global/products/pwcnt/en/pwcnt_voice_vlan_support.pdf
TLeBlanc22
14 Posts
0
April 24th, 2015 11:00
Ah, this is using the CLI... You network guys are all the same...
Can it be done in the GUI? Trying to translate...don't mind using the CLI, but like to understand the concepts in both, since this is a new switch architecture here.
Thanks!
--Terry
DELL-Josh Cr
Community Manager
•
9.6K Posts
•
43K Points
0
April 24th, 2015 12:00
VLANs should work between the various hardware, we are not doing anything that is not standard with the VLAN usage. So I would not expect you to have any issues with getting it to work.
DELL-Josh Cr
Community Manager
•
9.6K Posts
•
43K Points
0
April 24th, 2015 12:00
Right, voice vlan has 1 tagged VLAN and 1 untagged VLAN and designed for VoIP. You could probably use normal VLANs too, but voice VLAN usually is easier to get working. Double VLAN is for having two layers of tags, usually for a WAN environment where there would be a normal tag and then an ISP tag between sites.
TLeBlanc22
14 Posts
0
April 24th, 2015 12:00
Understood...but different vendors do things...differently...
In this instance, on the PC8024, there is a "standard" VLAN configuration, a "double" VLAN configuratino, and a "voice" VLAN configuration. Based on your feedback, it's the "voice" VLAN configuration I should be working with on the PC8024 to "match" the existing voice VLAN on the HP switches.
Sound about right?
Thanks for the rapid response and focused feedback!
--Terry
TLeBlanc22
14 Posts
0
April 24th, 2015 12:00
Currently, on the HP switches, I have just 2 VLANs: the "default" (1) for all traffic but VoIP, and "voice" (100) for the Mitel phone traffic.
Sounds like the PC8024 has a "default" VLAN (1), plus 2 VLANs for "voice", one tagged and one untagged...is that right? Or am I reading more into it. I was just trying to add a "regular" VLAN, which I can do...but could not set the ports to "tagged", wouldn't let me...only offered F or U. I was able to set the "default" VLAN ports to "U", though I don't know if that was needed...appeared to be defaulting to "F".
TLeBlanc22
14 Posts
0
April 27th, 2015 06:00
So, if I understand what you're saying...the reason I can't set the ports on the VLAN 100 that I added is because the port mode for that VLAN is set to "Access" mode, which prohibits "tagged"...so I need to change to "General" mode. How do I set that up, from the beginning?
I've added the second VLAN, 100, named "voice". Where is access mode set?
Doesn't matter to me how we do this...whether it's by adding a 2nd VLAN or by using the
Voice VLAN, as long as it works and is compatible with the existing configuration on the HP switches so that the voice traffic is handled properly thru the PC8024.
Sounds like we're getting closer...
TLeBlanc22
14 Posts
0
April 27th, 2015 06:00
That worked, Josh. I was able to connect a phone to port 19 after changing the ports from "access" to "general" and it was able to communicate on the network and get a DHCP address and talk to the phone switch. Need to do some testing...but the phone is able to communicate on the network.
I can see where this is probably a lot easier in the CLI, where multiple ports can be manipulated with a single command using ranges.
TLeBlanc22
14 Posts
0
April 27th, 2015 06:00
Mode is set in port settings...have to set each port individually? All ports would have to be set to "general" instead of the default "access" to be able to have the ports "tagged" for the voice VLAN and "untagged" for the default?
TLeBlanc22
14 Posts
0
April 27th, 2015 06:00
Changed all 24 ports from "access" to "general". Then changed all ports to "tagged" in VLAN 100 (voice). Some of the ports will be "links" to the HP switches if we use the PC8024 as 10GbE backbone switches. Will that work with the ports set to "general" or will they need to changed to "trunk"? Voice traffic will need to flow between switches.