• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 830
  • Last Modified:

CISCO IP Telephone sets are taking IP from data Vlan.

We have just finished with CISCO IPT installation. We configured Data and Voice Vlans on HP Procurve switches and DHCP on windows 2003 server with option 150 is configured accordigly. Now, when we connect a phone to a network it is taking an ip address from data vlan.

If we configure VLan ID manually on the phone set 7911 than it is taking an ip from the correct voice Vlan.
I dont know if any string value needs to be add at DHCP scope etc. we can't go to each phone and configure vlan ids.

I need help, rescue me plz.
regards
0
aassal
Asked:
aassal
  • 7
  • 7
  • 2
1 Solution
 
aassalAuthor Commented:
DHCP was configured as explained in the above links.







0
 
Darrell_MilamCommented:
Do you have other vlans setup or just the two?
0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

 
Darrell_MilamCommented:
the problem seems more with the vlan setup and ip address helper than the dhcp.
could you send the l3 switch config and the ip addresses of the dhcp server
0
 
aassalAuthor Commented:
We are having more than one Vlans. For now we are using Vlan ID 106 & 107 only, Other floors are not yet activated.

find below HP Switch configurations.
ProCurve J8698A Switch 5412zl
Software revision K.15.02.0005

 Running configuration:

; J8698A Configuration Editor; Created on release #K.15.02.0005

hostname "Core-Switch1"
module 1 type J8705A
module 2 type J9154A
module 3 type J8702A
module 4 type J8702A
module 5 type J8702A
module 6 type J8702A
module 7 type J8702A
module 8 type J8702A
module 9 type J8702A
module 10 type J8702A
module 11 type J8702A
module 12 type J8702A
ip routing
vlan 1
   name "DEFAULT_VLAN"
   untagged A1-A24,B1-B2,C1-C18,C20,C22,C24,D1-D24,E1-E24,F1-F24,G1-G24,H1-H24,I
1-I24,J1-J24,K1-K24,L1-L24
-- MORE --, next page: Space, next line: Enter, quit: Control-C

   no untagged C19,C21,C23
   exit
vlan 106
   name "6th_Floor_Voice_Vlan"
   untagged C19,C21,C23
   ip helper-address 10.14.4.3
   ip address 10.14.86.1 255.255.255.0
   tagged A1-A14,A16,A18-A24,C1-C18,C20,C22,C24,D1-D24,E1-E24,F1-F24,G1-G24
   exit
vlan 105
   name "5th_Floor_Voice_Vlan"
   ip helper-address 10.14.4.3
   ip address 10.14.85.1 255.255.255.0
   exit
vlan 104
   name "4th_Floor_Voice_Vlan"
   ip helper-address 10.14.4.3
   ip address 10.14.84.1 255.255.255.0
   exit
vlan 107
   name "7th_Floor_Voice_Vlan"
   ip helper-address 10.14.4.3
   ip address 10.14.87.1 255.255.255.0
   tagged A15,A17
   exit
vlan 14
   name "4th_Floor_Data_Vlan"
   ip helper-address 10.14.4.3
   ip address 10.14.74.1 255.255.255.0
   exit
vlan 15
   name "5th_Floor_Data_Vlan"
   ip helper-address 10.14.4.3
   ip address 10.14.75.1 255.255.255.0
   exit
vlan 16
   name "6th_Floor_Data_Vlan"
   ip helper-address 10.14.4.3
   ip address 10.14.76.1 255.255.255.0
   tagged A16
   exit
vlan 17
   name "7th_Floor_Data_Vlan"
   ip helper-address 10.14.4.3
   ip address 10.14.77.1 255.255.255.0
   tagged A15,A17
   exit
ip route 0.0.0.0 0.0.0.0 10.14.4.1
snmp-server location "6thFloor"
spanning-tree


0
 
aassalAuthor Commented:
Sorry i forgot to add DHCP server ip address.
10.14.4.3 is our DHCP server.
0
 
Darrell_MilamCommented:
which is the vlan in question?
is the phone's on there own port or are you trying to use one data port for the phone and pc.

are the phones connected to this?



0
 
aassalAuthor Commented:
Vlan 106 is for voice. Phones should take an IPs from Vlan-106 (10.14.86.x/24).
We are using one data port for phone and PC. Phones are connected yes.
0
 
cordeosCommented:
Using the phone's onboard mini Switch port for the PC, with one PORT connected to the LAN will only work in automated VLAN selection mode with Cisco switches which support CDP communication.  This is how the phone queries the switch to ask what VLAN to use for voice, which to use for DATA.

If you are not using a CDP (Cisco) switch, you will need to manually configure each phone with the correct VLAN settings for the two ports.  This can be found from the phone's "Settings" button - "Network Settings" and "Operational VLAN" and "PC VLAN".

Hope this helps.
0
 
Darrell_MilamCommented:
if possible use use one port with only the voice vlan for the phones and different port for the data pc
0
 
Darrell_MilamCommented:
history
0
 
aassalAuthor Commented:
I have mentinoed in my question that with manul Vlan ID settings it's working fine but its not pricticle, we have hundreds of extensions and many voice vlans. How can we have CDP sort of functionality on HP switches?
0
 
Darrell_MilamCommented:
from what I understand of CDP it is a Cisco proprietary protocol and HP procurve switches will only pass the information,

0
 
cordeosCommented:
There is absolutely no way to have CDP funcationality set on an HP switch.  None.

One thing you might be able to do is (if you Voice VLAN with the CallManager server is default) is setup a phone batch config/setup which sets the correct manual VLANs on each phone when they are plugged in and receive the initial config from CUCM.  Unfortunately this would mean config reset on each phone.

Its a little unusual that with 100s of phones and VLANs that this issue was not addressed or handled during deployment.

Currently, your only realistic options are, as noted already:
a) manually set the VLAN on each phone
b) use seperate LAN cable for voice and PC then set the VLAN assignment at the switch level

No other way around it.
0
 
aassalAuthor Commented:
I found a way...
I configured LLDP on HP switch and now its taking an ip address from voice vlan without any manual intervention.

Thank you all for your comments.

regards
0
 
aassalAuthor Commented:
I found solution by my self from other sources.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 7
  • 7
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now