Some phones not booting properly on Cisco Switches

[kwbMitel]

I have a customer with a lot of older phones that they deploy as needed.

They have an odd issue where some of the phones boot properly and some do not when connected to their Cisco Switch.

When they do not boot properly, nothing happens. Literally Nothing, not even the Mitel Startup screen.

Plugging a non-working phone into a POE injector will show the proper bootup sequence.

They have quite a number of phones that wont boot but specifically:
[pre]
5330 IP 50005070 Rev B.24 Works
5330 IP 50005804 Rev E.22(6) Not Working
[/pre]

The Cisco is a Cisco Catalyst 3650-48PS-S Switch

Does anyone have a clue as to what might be happening here?

 

[Billz66]

does it appear that they are getting DHCP properly but not connecting , or no dhcp either
- no DHCP might be a CDP LLDP issue - could try static IP and see if that connects

Also have they ever been used on the system?
if they have worked before has the system been upgraded since they worked ?
it might be a firmware issue
there was a KMS article 11-5191-00240 related to firmware problems




If I never did anything I'd never done before , I'd never do anything.....

 

[kwbMitel]

Thanks Billz66,

The boot sequence never starts on the phone, not even the Mitel Splash Screen when connected to the Cisco.
On an isolated POE injector the phone boot sequence is normal

That KMS article is ancient and wont be relevant in this case. It did make me remember an issue with 53xx phone firmware and release 9 however but alas, that does not look good either as that issue had the phones get stuck on Contacting server at the end of the boot sequence.

I'm investigating a possible POE Threshold issue at this point

 

[Valamagules]

Sounds like PoE issue to me.

Clever men learns what Wise men shares!

 

[kwbMitel]

The customer informed me that an update to the Cisco Switches resolved the issue

 

[Billz66]

might have been this one then

Mitel IP Phones get stuck at DHCP discovery Document ID SO3800
Symptoms
Phones will get stuck at DHCP Discovery and will not connect to the MiVB due to no Network connection
Environment
MiVB
Cause
A problem has been identified with Cisco equipment being used as a IP Helper that will cause the DHCP servers response to be dropped if option 125 is contained within the response.
Further details can been found in the Cisco article

https://quickview.cloudapps.cisco.com/quickview/bug/CSCvm29618

Resolution
Upgrade the Cisco equipment to the Cisco specified release or configure the DHCP server to use Option 43 to configure the IP Phones rather than using Option 125


If I never did anything I'd never done before , I'd never do anything.....

 

[kwbMitel]

Sorry Billz66, not that one either.

I can handle, and troubleshoot issues with DHCP.

I this case, the phone wasn't booting, period. Screen Dead for all intents and purposes but not dead if plugged into anything but the Cisco.

Some Phones worked with Identical power draw so POE wasn't the issue.

We'll probably never know.