- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Comware Based
- >
- Re: In-line Hybrid VoiceVLAN Registration Problems
Comware Based
1753481
Members
4069
Online
108794
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО03-10-2009 05:10 PM
тАО03-10-2009 05:10 PM
In-line Hybrid VoiceVLAN Registration Problems
I'm trying to program my 3COM 4500G switches to automatically put my VoIP phones on VLAN 22; while putting the PC (connected via the same Ethernet cable; in-line) on VLAN 1.
What I've tried:
1) Configuring 'voice vlan 22 enable' globally and on the interface.
2) Putting phone on Access VLAN 22 and then moving the phone to a hybrid port.
3) Enabling GVRP (trunking all vlans)
Here is my consolidated config:
voice vlan 22 enable
voice vlan mac-address 0004-f200-0000 mask ffff-ff00-0000 description Avaya01
voice vlan mac-address 001b-4f00-0000 mask ffff-ff00-0000 description Avaya Phone 01
#
gvrp
#
vlan 1
igmp-snooping enable
#
vlan 22
#
interface Vlan-interface1
ip address 192.168.0.240 255.255.255.0
#
interface GigabitEthernet1/0/1
port link-type hybrid
port hybrid vlan 22 tagged
port hybrid vlan 1 untagged
broadcast-suppression pps 3000
undo jumboframe enable
poe enable
stp edged-port enable
#
interface GigabitEthernet1/0/47
port link-type trunk
port trunk permit vlan all
broadcast-suppression pps 3000
undo jumboframe enable
description Uplink to Server Switch
stp edged-port enable
gvrp
#
ip route-static 0.0.0.0 0.0.0.0 192.168.0.1
What I've tried:
1) Configuring 'voice vlan 22 enable' globally and on the interface.
2) Putting phone on Access VLAN 22 and then moving the phone to a hybrid port.
3) Enabling GVRP (trunking all vlans)
Here is my consolidated config:
voice vlan 22 enable
voice vlan mac-address 0004-f200-0000 mask ffff-ff00-0000 description Avaya01
voice vlan mac-address 001b-4f00-0000 mask ffff-ff00-0000 description Avaya Phone 01
#
gvrp
#
vlan 1
igmp-snooping enable
#
vlan 22
#
interface Vlan-interface1
ip address 192.168.0.240 255.255.255.0
#
interface GigabitEthernet1/0/1
port link-type hybrid
port hybrid vlan 22 tagged
port hybrid vlan 1 untagged
broadcast-suppression pps 3000
undo jumboframe enable
poe enable
stp edged-port enable
#
interface GigabitEthernet1/0/47
port link-type trunk
port trunk permit vlan all
broadcast-suppression pps 3000
undo jumboframe enable
description Uplink to Server Switch
stp edged-port enable
gvrp
#
ip route-static 0.0.0.0 0.0.0.0 192.168.0.1
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-10-2009 05:16 PM
тАО03-10-2009 05:16 PM
Re: In-line Hybrid VoiceVLAN Registration Problems
UPDATE:
Here is a manual workaround I've discovered. (But it's unpractical):
-Manually configured Port 1 as an Access Port on VLAN 22.
-Let the phone re-boot, and detect the VoIP server.
-Must make a phone call on the new VLAN.
-In-line PC get's an IP address from VLAN 22's DHCP (this is unacceptable.)
-Manually change the port from Access to Hybrid, PVID 1, 1 untagged, 22 tagged.
-Finally, Reboot the PC and it get's an IP address from VLAN 1.
-This configuration works, until the trunk carrying the GVRP trunk information get's severed; afterwhich all ports 'forget' and manual configuration steps need to be repeated per port.
(We also have some 'Dell PowerConnect 3324' - they picked up the hybrid config without a hitch. Only my new 4500G's have given me troubles.)
Here is a manual workaround I've discovered. (But it's unpractical):
-Manually configured Port 1 as an Access Port on VLAN 22.
-Let the phone re-boot, and detect the VoIP server.
-Must make a phone call on the new VLAN.
-In-line PC get's an IP address from VLAN 22's DHCP (this is unacceptable.)
-Manually change the port from Access to Hybrid, PVID 1, 1 untagged, 22 tagged.
-Finally, Reboot the PC and it get's an IP address from VLAN 1.
-This configuration works, until the trunk carrying the GVRP trunk information get's severed; afterwhich all ports 'forget' and manual configuration steps need to be repeated per port.
(We also have some 'Dell PowerConnect 3324' - they picked up the hybrid config without a hitch. Only my new 4500G's have given me troubles.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2009 09:11 AM
тАО03-14-2009 09:11 AM
Re: In-line Hybrid VoiceVLAN Registration Problems
Why are you using gvrp? It is not a must and not at all required for your voice config to work.
Also, it will only work on trunk port and only for passing vlans on these ports.
Also, unless the pc behind he phone is using authentication such as dot1x anyone just can bring a PC and connect it into his desk phone. That is not probably what you want!
VLAN 22
voice vlan 22 enable
voice vlan mac-address 0004-f200-0000 mask ffff-ff00-0000 description Avaya01
voice vlan mac-address 001b-4f00-0000 mask ffff-ff00-0000 description Avaya Phone 01
# Define the IP address of DHCP server
dhcp-server 1 ip xx.xx.xx.xx
# Define a vlan interface for vlan 22
interface Vlan-interface22
# Configure an ip address for interface vlan 22
ip address ip_address sub_net
# Configure a dhcp relay(udp ports 67 and 68) for the interface vlan 22 if there is no DHCP server in this VLAN
dhcp-server 1
interface GigabitEthernet1/0/1
# Setup for Hybrid ports
port link-type hybrid
# Setup for voice vlan
voice vlan enable
Because you are using your Data vlan as VID1 that is all what you require because VID1 is per defalt the PVID.
This message was edited by Shirin on 3-15-09 @ 2:28 AM
Also, it will only work on trunk port and only for passing vlans on these ports.
Also, unless the pc behind he phone is using authentication such as dot1x anyone just can bring a PC and connect it into his desk phone. That is not probably what you want!
VLAN 22
voice vlan 22 enable
voice vlan mac-address 0004-f200-0000 mask ffff-ff00-0000 description Avaya01
voice vlan mac-address 001b-4f00-0000 mask ffff-ff00-0000 description Avaya Phone 01
# Define the IP address of DHCP server
dhcp-server 1 ip xx.xx.xx.xx
# Define a vlan interface for vlan 22
interface Vlan-interface22
# Configure an ip address for interface vlan 22
ip address ip_address sub_net
# Configure a dhcp relay(udp ports 67 and 68) for the interface vlan 22 if there is no DHCP server in this VLAN
dhcp-server 1
interface GigabitEthernet1/0/1
# Setup for Hybrid ports
port link-type hybrid
# Setup for voice vlan
voice vlan enable
Because you are using your Data vlan as VID1 that is all what you require because VID1 is per defalt the PVID.
This message was edited by Shirin on 3-15-09 @ 2:28 AM
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP