Switches, Hubs, and Modems
cancel
Showing results for 
Search instead for 
Did you mean: 

HP Procurve and DHCP Cisco CallManager

Semlali_1
Advisor

HP Procurve and DHCP Cisco CallManager

Hi,
I have one Callmanager Cisco, it's work like dhcp and tftp server.
I have a hard phone Cisco 6921 and i wanna use it with dhcp CallManager
When i fixe address in the phone, in the vlan 506 thats work.
And when i try to let the phone in dynamic address, thats not work
the phone cant't have IP address dynimacly

Thats what i do my switch HP Procurve,

dhcp-relay
ip routing

vlan 505
name "Call manager"
untagged K21-K24
ip address 192.168.0.1 255.255.255.0
tagged H1-H8
exit


vlan 506
name "telephone_Cisco"
untagged K1
qos dscp 101110
ip helper-address 192.168.0.111
ip address 192.168.100.1 255.255.255.0
tagged A17,G13,H1,K24,L7
voice
exit

dhcp-snooping
dhcp-snooping authorized-server 172.22.3.111
dhcp-snooping authorized-server 172.22.3.113
dhcp-snooping trust K21-K24
dhcp-snooping trust L7

Spanning-tree
spanning-tree priority 1

Please help

Thanks


10 REPLIES
Jeff Carrell
Honored Contributor

Re: HP Procurve and DHCP Cisco CallManager

Quick question, what is the IP addr of the 6921?

And of course, the dhcp server does have a scope for subnet 192.168.100.0/24, yes?
--

Based on your config having a ip helper-addr of 192.168.0.111 and that same IP addr is not in your dhcp-snooping config, the dhcp-snooping may not be passing the dhcp reply from the dhcp server. You could see if this is the case by doing 'sh dhcp-s s' on the ProCurve switch before and after the you connect the phone and see if the dhcp-snooping status.

hth...Jeff
Semlali_1
Advisor

Re: HP Procurve and DHCP Cisco CallManager

Hi,

Sorry the dhcp server its :
dhcp-snooping authorized-server 192.168.0.111
dhcp-snooping authorized-server 192.168.0.113


The phone can't toke the ip address on then DHCP CallManager, it's always 0.0.0.0
And what is the scope for subnet 192.168.100.0/24 ?
when i fixe ip address in vlan 506,i can send icmp request between vlan 505 and vlan 506.
server DHCP : 192.168.0.111 is alive, time = 2 ms
Phone : 192.168.100.200

This is the result of : sh dhcp-s s
Packet type Action Reason Count
----------- ------- ---------------------------- ---------
server forward from trusted port 0
client forward to trusted port 0
server drop received on untrusted port 0
server drop unauthorized server 0
client drop destination on untrusted port 0
client drop untrusted option 82 field 0
client drop bad DHCP release request 0
client drop failed verify MAC check 0

Thanks jeff,

Kings regards
Jeff Carrell
Honored Contributor

Re: HP Procurve and DHCP Cisco CallManager

Hmm...nothing in the counters, something of course is not happy....

Make sure that the dhcp-snooping trust port definition includes the port where the dhcp server traffic comes in/out - usually you only trust the "uplink" port -or- if the dhcp server is connected to the same switch, you only trust that port. No other device ports should be trusted.

Another way to test and see if dhcp will work, disable dhcp-snooping 'no dhcp-snooping', all the dhcp-snooping config will stay, just stops its operation. That way if its the dhcp-snooping config causing problems, you isolate it.

You know routing between is working, so at least basic L2/L3 is good...just down to one more function, but you have 2 different config components to test through (dhcp relay/helper and dhcp-snooping).

hth...Jeff
John Gelten
Regular Advisor

Re: HP Procurve and DHCP Cisco CallManager

To agree with Jeff's suggestion... First try to get DHCP to work as basis as possible, so only use the IP-helper, and temporarily disable all other DHCP-relay and DHCP-snooping stuff on the switch.

And you were asking about scope...
When the phone is in the same supbnet as your DHCP-server, the server has to offer to the phone an address in the range of 192.168.0.0/24
Now, your phone is in another subnet; is your DHCP-server setup to offer addresses in the 192.168.100.0/24 subnet ? There should be a scope (or a pool or a network or whatever it is called) for the subnet of the phone.
Semlali_1
Advisor

Re: HP Procurve and DHCP Cisco CallManager

thats not work, the phone cant's see the spool of the dhcp CallManager Cisco.
i dont know if it's the spéciale configuration between Switch HP Procurve and DHCP Cisco Call Mnager
I activated lld and cdp, and upgraded the firmwear Switch, and that's not work.

Please help.
Jeff Carrell
Honored Contributor

Re: HP Procurve and DHCP Cisco CallManager

Semlali said "thats not work, the phone cant's see the spool of the dhcp CallManager Cisco.
i dont know if it's the spà ©ciale configuration between Switch HP Procurve and DHCP Cisco Call Mnager
I activated lld and cdp, and upgraded the firmwear Switch, and that's not work.

Please help."

Can the CCM ping the ProCurve switch on both 192.168.0.1 and 192.168.100.1?

Can the CCM ping a device in VLAN 506?

We need to see both your current ProCurve config and your current CCM's config as well.


...Jeff
Semlali_1
Advisor

Re: HP Procurve and DHCP Cisco CallManager

ping CMU => gateway vlan 192.168.100.1 ok
ping CMU => fixed ip address in the phone ok

i add this command to HP Procurve
int L7 poe-lldp-detect enabled

but the probléme it's the same
Jeff Carrell
Honored Contributor

Re: HP Procurve and DHCP Cisco CallManager

We need to see both your current ProCurve config and your current CCM's config.

Sanitize the config files as appropriate and post them.

Do not provide just some of the config, it will help to see it all.

Also, provide a 'show lldp i r' from ProCurve.
Semlali_1
Advisor

Re: HP Procurve and DHCP Cisco CallManager

Ther's a ptobléme with lldp in the switch or there's à spécial configuration to do with switch 5412 ?!
Jeff Carrell
Honored Contributor

Re: HP Procurve and DHCP Cisco CallManager

Semlali said: "Ther's a ptoblà ©me with lldp in the switch or there's à spà ©cial configuration to do with switch 5412 ?!"

LLDP = link layer discovery protocol, is enabled by default on ProVision switches. It is an industry standard, similar to Cisco's CDP.

I guess don't worry about that, it will just help us to help to you to see your configs.

Cheers...Jeff