Mitel & Windows 2003 DHCP problem

[StilPhone]

Hi, need some help please. We have a 3300 Mitel MX controller running DHCP on the voice VLAN and a Dell Poweredge server also running DHCP on a Data VLAN, all was working fine until yesterday when the DHCP scope on the data side was deleted by accident... (Don't ask!) Now we have re-created the DHCP scope on another server but now when the phones boot up they are picking up an IP from the Data server and not releasing it, the phone goes through the normal boot sequence then gets to Option 128+ DHCP Discovery, Acknowledge then sticks with the data IP address, before it would release then pickup an IP from the Mitel using Option 125. We have checked the DHCP Scope options on the other sites which are set up the same way and we can't see what the problem is - does anyone have any suggestions?

Thanks in advance,

Phil

 

[nickcx]

Not sure how much this will help, but we have created and use a specific Vendor Class for our DHCP options, depending on what model your phones are they can use it. All info is contained in one option:

Mitel Vendor Class (Default User Class)
001 Mitel Option
id:ipphone.mitel.com;sw_tftp=172.17.0.6;call_srv=172.17.0.6;vlan=800;l2p=6

Otherwise, yous should check your options thoroughly. You should have 128, 129, 130, 132, 133

Is your switch configured and ports untagged?

 

[kwbMitel]

The only reason that the phone would release and re-request an IP is if you change the VLAN. If you do not change the VLAN the phone will accept any IP that comes with options 128, 129, and 130 (or equiv in 125)

*******************************************************
Hard work often pays off after time, but laziness always pays off now.

 

[slapin]

Make sure your ethernet switch doesn't negotiate trunking with mitel phones. If it does all or some of the VLANs are accessible for the phone.

 

[StilPhone]

Thanks for the replies, we kind of managed to get it fixed but I don´t think its 100%, our Dell support got a CCNA trainer to look at it and he fixed it by removing all the options from the DHCP scope on the server. That fixed the mojority of the problem but now we have a group of phones in one area that aren´t picking up an IP at all! The phones that work get Option 128+ Offer rejected and then they collect option 125 and a Mitel IP... The ones that don´t work just keep rejecting...

So far we´ve tried a differetn port on the same switch, a different port on a different switch, and going straight into the switch without the structured cabling and that is the only one that works, which would sugget there is a problem with the cabling between the patch and the port, however it has only just stopped working and the building was cabled 6 months ago....

And to add another twist, if I give the phone a static IP it works...

Thanks guys!

 

[kwbMitel]

the phones that do not work have not had the latest TFTP loaded and do not know how to use option 125.

I would suggest using static vlan settings if you want to avoid the customers DHCP, this would still allow some flexibility without consuming too much time.



*******************************************************
Hard work often pays off after time, but laziness always pays off now.

 

[StilPhone]

Thanks, kind of sorted it, there were some config issues on the HP switches.