- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- tagging or trunking for voice VLAN traffic?
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2015 12:48 PM
06-30-2015 12:48 PM
I have been tasked with setting up a VLAN for VoIP on our existing HP Procurve Switches.
The specifications call for:
- Customer will be responsible for programming QoS on all switchports and trunks that will support voice traffic.
- Customer will provide a trunk from their core switch in the MDF to connect to the IAD router
- Customer will program voice VLAN 444 on all switchports that will support voice traffic
- Customer will allow VLAN 444 on all trunks that will transport voice traffic.
The client PC and the Cisco IP phones will be sharing the same port.
I plan to continue using Default VLAN 1 for data and use Voice VLAN 444 for VoIP.
I have six ProCurve Switch 2520G-24-PoE (J9299A) named USERS1 through USERS6
And one ProCurve Switch 2810-24G (J9021A) named MASTER which all the 2520’s named USERSx are plugged into the MASTER switch on ports 1 through 6.
As I understand, thespecifications called for in 1. and 3. above are dealt with in my running configuration:
hostname "USERSx"
vlan 1
name "DEFAULT_VLAN"
untagged 1-28
ip address 172.16.1.27 255.255.0.0
exit
vlan 444
name "VOICE"
tagged 1-28
no ip address
qos priority 6
exit
I am unclear on the need for and implementation of trunking called for in specifications 2. And 4..
Do I need to actually set up a trunk to allow VLAN 444 traffic from switch to switch or can I just tag ports 1 through 6 on the MASTER switch for VLAN 444 and tag one additional port on the MASTER switch (let’s say port 10) also for VLAN 444 for the IAD router to connect to?
If so, would a correct running config for the MASTER switch look like this?
hostname "MASTER"
vlan1
name "DEFAULT_VLAN"
untagged 1-24
ip address 172.16.1.10 255.255.0.0
exit
vlan 444
name "VOICE"
tagged 1-6,10
no ip address
qos priority 6
exit
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2015 05:06 PM
06-30-2015 05:06 PM
SolutionThey are using the word "trunk" in a Cisco context.
For your HP switches, you just need to add the voice VLAN as a tagged VLAN to the inter-switch links.
As you have tagged 1-28, then this presumably includes the uplink ports and covers you for 4.
Your MASTER has
- voice VLAN tagged on uplink ports
- voice VLAN tagged on link to IAD router
I think you're OK.
You might also want to add
VLAN 444 voice
- this enables some QoS and also LLDP to advertise VOICE VLAN to the phones
And ask them if their phones can get their VOICE VLAN from LLDP.