5340 Boot Problems 4

[Ratti3]

Hi,

I have 2 Mitel 5340 that are stuck at "DHCP: Discovery", I have a third 5340 that works fine. I have tried resetting the device manually, tried setting ip address manually and also tried a PING test and that fails.

I've got an MX Controller running 7.1.5.13, a POE switch with VLAN, the DHCP option on the Windows DC are as follows:
128: 192.168.203.33
129: 192.168.203.33
130: MITEL IP PHONE
132: 0x2
133: 0x6
The 3300 is configured to give out the IP addresses.

Is this a broken phone or is it not seeing the DHCP server because some option is missing?

Thanks

 

[jimboban]

Hiya

To be honest, if the rest of your handsets are working from the same ports, it is likely to be the handsets - we have seen more than a few with exactly the same problem...

 

[MitelInMyBlood]

Have you tried manually (within the phone) setting the ICP (the 3300's) address and TFTP server address (should be alike)?

Something else I've had some success doing with a difficult instrument is try hard-coding the phone's MAC address in the Multiline Set Config form.

Seems like once you finally get the phone to come up that you can dispense with all the special tricks and it will work fine thereafter.

We've not (yet) put in a lot of 5340s, but we're so far 20 for 20.

 

[Ratti3]

@jimboban: its useful to know that the same problem has occured with other people

@MitelInMyBlood: I have tried manually setting the IP on the phone and also doing a ping test which fails. I have not tried hard coding the MAC in the 3300 although I dont think that will make a difference as it needs to get an IP first, I'll give it a go first.

thanks

 

[paterson]

What static options are you putting into the set? Looks like you are using VLAN 2. Did you put that into the set? Have you tried connecting the set to a network port that has been proven to work, ie. remove a working set and place the trouble set there. What happens?

**************************************
Insert Witty Signature Here.

 

[TheMitelGuy]

I would highly recommend you reference the Technical Handbook that states you should be using Vendor Defined Scope Option 43 with a Windows Server.

Very easily overlooked, but I think it's page 93. It will probably solve your issues.

 

[TheMitelGuy]

Ps. Option 125 should not be used in a WinServ '03 environment, and 43 should be instead.

 

[paterson]

???

Option 125 should not be used in a WinServ '03 environment, and 43 should be instead.

I have never heard this. What are the problems?

**************************************
Insert Witty Signature Here.

 

[TheMitelGuy]

There are problems with WinServ hading out the VLAN incorrectly in binary (don't quote me, but I think I'm extremely close on that).

 

[Ratti3]

@Paterson: I used 192.168.203.33 and the correct VLAN ids, and it did not work, I tried the same port it didnt work. Still stuck at DHCP discovery.

@TheMitelGuy: Those windows DHCP options are the only ones, I don't have option 125 on windows.

These are options on the 3300 DHCP:
3: 192.168.203.1
66: 192.168.203.33
67: /sysro/E2T8260
125: id:ipphone.mitel.com;sw_tftp=192.168.203.33;call_srv=192.168.203.33;dscp=46
128: 192.168.203.33
129: 192.168.203.33
130: MITEL IP PHONE
134: 46

Are you saying I should turn them off on the 3300?

I tried setting option 43 on the WIndows DHCP and it made no difference, I set it like this:
id:ipphone.mitel.com;sw_tftp=192.168.203.33;call_srv=192.168.203.33;vlan=2;l2p=6=dscp=46

thanks

 

[TheMitelGuy]

You are missing 131 and 132 (VLAN and prio.) in you last example.

Is your switch programmed to provide the proper default VLAN to the ports that you are plugging the phones into?? For example, if you are sending those DHCP scope options out on VLAN 1, and your switch is setup to default those ports to VLAN 20, then your phone will never see those options.

 

[Ratti3]

I think VLAN tagging is all correct I'll double check it. All other phones work ok and are on VLAN 2, they first get the IP from the W2K3 server use option 128 then release the IP and then get the VLAN ID and get the IP from the Switch.

I did a test with another DHCP server with no options set, used a different phone and it discovers the dhcp server but rejects the ip. When I plug in the 5340 it does not discover the DHCP server.

Am I correct in saying that regardless of VLANs/ICPs being present or not these phones should at least communicate with a DHCP server.

Thanks