Switches, Hubs, and Modems

ip-helper with Avaya phone system on 2650 switch

 
Mark Alderson_1
Occasional Advisor

Re: ip-helper with Avaya phone system on 2650 switch

According to the HP documentation no it should not be. The IP helper-address, when set correctly, is meant to be able to answer from an independent VLAN as long as IP routing is enabled, DHCP-relay is enabled etc ... Tagging port 48 causes DHCP-ACK errors on the phone which is documented as the VLAN being enabled when it shouldn't be. Tried it just to make sure. I'll hopefully have an answer tomorrow.
Pieter 't Hart
Honored Contributor

Re: ip-helper with Avaya phone system on 2650 switch

>>> with the pressure to virtualise I'd only want a single NIC doing the work <<<

There is no technical problem to bring multiple VLANS to the virtual DHCPserver each to a different virtualNIC.
Pieter 't Hart
Honored Contributor

Re: ip-helper with Avaya phone system on 2650 switch

apart from that,
>>>
Phone is on port 37
vlan 10
name "VOICE"
untagged 1,37
<<<

Normal configuration is to have the phone port untagged in data-vlan and tagged in voice vlan.

The first dhcp request is on the data vlan (untagged). then it must be recognized as phone either by lldp or by "dhcp option 82".
The voice vlan id is sent to the phone and
The phone sends a new "tagged" dhcp request on the voice vlan.

You'll need a dhcp relay for the second request configured on the voice vlan if you want the request forwarded to a dhcp server that's not on the voice vlan.

so you'll need (only phone port)
vlan 10
tagged 37
vlan 20
untagged 37

Mark Alderson_1
Occasional Advisor

Re: ip-helper with Avaya phone system on 2650 switch

http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1276094532639+28353475&threadId=1101812

Seems to be the nearest to an answer. Still waiting on the supplier unfortunately but this is nearest I've found to a reply. Couldn't find searching on HP site but found through Avaya site ?!?!
KSimpson
Frequent Advisor

Re: ip-helper with Avaya phone system on 2650 switch

Sorry, I have very little knowledge on VoIP so forgive me if I'm not making sense.

If a phone is voice, why does it need to be on a data vlan? I can understand if a computer will be plugged intoport 37 but it's not. Or will it? Will port 37 always be connected to a phone?

Why can't port 37 (phone) be untagged 10 and port 48 (dhcp) be tagged 10?

Does the phone need to be on the data (vlan 20) network at all? This will eliminate wrong network traffic.

KSimpson
Frequent Advisor

Re: ip-helper with Avaya phone system on 2650 switch

If both of rhese devices are connected to the same switch, why can't it be done this way.

vlan 1
name "DEFAULT_VLAN"
no ip address
no untagged 1-50
exit
vlan 10
name "VOICE"
untagged 1,37
tagged 48
ip address 10.40.10.1 255.255.255.0
ip helper-address 10.30.10.2
tagged 48-50
exit


vlan 20
name "DATA"
untagged 2-36,38-48
ip address 10.30.10.1 255.255.255.0
tagged 49-50
exit

Shadow13
Respected Contributor

Re: ip-helper with Avaya phone system on 2650 switch

In General if both a phone and a device will be connected to the same port then:

Untag the port on the DATA VLAN
Tag the port in the voice VLAN
the voice vlan should be configured with the "VOICE" command as below
#vlan 10
#voice
#write mem

this should work and also make sure that either to configure the voice vlan on the phones manually or check if the phone supports LLDP-MED, in this case the voice controller should do the vlan configuration for the phone.


please you can refer to the below document for more details:

http://h40060.www4.hp.com/procurve/uk/en/pdfs/application-notes/AN-C6_ProCurve-Avaya-phone-final-0904008.pdf


Follow as mentioned and it should work perfectly, also the document has the 802.1x configuration in case you want to add security to the ports.

The document is the office HP PorCurve interoperability with AVAYA phones.

Regards.
Mark Alderson_1
Occasional Advisor

Re: ip-helper with Avaya phone system on 2650 switch

The phone is the primary device, this connects to the switch directly BUT the phone does have a port for data hence the tagged port for voice and the untagged port for data.

My problem isn't with the config of the switch particularly, I can make the config work by adding plugging in the voice DHCP server directly, but I'm trying to get the voice VLAN to see the DHCP server on the data VLAN by using ip-helper. If I create a secondary data VLAN and setup a port untagged to that VLAN then I can use the ip-helper command to point at the one and only DHCP server and it works. My issue seems to be with tagged vlans connecting to the DHCP server. I've got stacks of examples from both the HP and Avaya site but all of them have a configuration that is very different. As soon as I find the answer it'll be posted here.
Shadow13
Respected Contributor

Re: ip-helper with Avaya phone system on 2650 switch

it should work normally, just make sure you define the voice vlan on the phone itself that way the phone will request IP from the correct subnet using that same server.

is the server connected to the same switch ?

Can you post ur latest configuration so i can check it.
Mark Alderson_1
Occasional Advisor

Re: ip-helper with Avaya phone system on 2650 switch

Current config with the test DATA VLAN

; J8165A Configuration Editor; Created on release #H.10.83

hostname "ProCurve Switch 2650-PWR"
qos dscp-map 010101 priority 2
qos dscp-map 101001 priority 4
qos dscp-map 101010 priority 4
qos dscp-map 101011 priority 4
qos dscp-map 101110 priority 5
interface 11
name "Secondary DATA VLAN for test"
exit
interface 37
name "VOIP phone for test"
exit
interface 48
name "DHCP Server"
exit
ip routing
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
no ip address
no untagged 1-50
exit
vlan 10
name "VOICE"
ip address 10.40.10.1 255.255.255.0
ip helper-address 10.30.10.2
tagged 1-47,49-50
exit
vlan 20
name "DATA"
untagged 1-10,12-48
ip address 10.30.10.1 255.255.255.0
tagged 49-50
exit
vlan 30
name "DATA2"
untagged 11
ip address 10.41.10.1 255.255.255.0
ip helper-address 10.30.10.2
exit
qos type-of-service diff-services
password manager

As requested