Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

"Starting DHCP" or Static IP on 1120 - no connectivity

Status
Not open for further replies.

agamolya

IS-IT--Management
Jul 1, 2008
3
UA
Hello All,
I have looked through the Internet experience base and tried some of suggestion which didn't help.

So we have there BCM400 4.0.2.03, 1120E IP phone and Cisco 3750 as switch and PoE supplier.
1120 was applied with the latest soft upgrades.

The problem:
When we plug the phone into the cisco port it gets power supply and starts loading. Then it stucks on "Starting DHCP..".
By the way there are other 30 (from 32 lisences) IP phones working OK. There is 100 IPs subnet to serve for BCMs DCHP.
Those 2 phones were not used before.

What we tried:
Plug in into different ports - the same.
Set static IP address - "Server unreachable" and can't reach that IP.
Deregister or switch off some working phones - nothing.
Suddenly after some plug-in-s it loaded with DHCP address!
We checked the port on the Cisco - both port and line are UP, plugged it out and plugged in back - Nothing! "Starting DHCP.. " and stucks. - Checked port on Cisco - it had port and line DOWN, or in the second case UP/DOWN switching by some reason. At the same time port is supplied with PoE.
Plugged in into that port a "normal" 1120 - worked OK - port and line are UP from the beginning and phone loaded OK.

So I can't find out what's the problem and where to dig it from.. It doesn't look like cisco problem - nothing special in alerts there.

Any Ideas?
Thanks in advance!
 
I have only seen this problem when the ip phone has an incorrect VLan configured
 
I agree with TLDuk. Are these sets using full DHCP or partial? If its partial,you need to manually set the VLAN config on the set. Is the BCM your DHCP server?

What doesn't kill you only makes you stronger.

If it's true that our species is alone in the universe, then I'd have to say that the universe aimed rather low and settled for very little.---George Carlin RIP
 
change patch cords? Plug the bad set into a known working location and see if it works. I think you may have done that if it works the set is good. It sounds to me from what you are describing like it is a cabling issue. Compare the port status of a working set to this one. If you see a status of up/down it is more than likely a cabling issue that is why I suggested changing patch cords, even the one on the phone. Take the phone back and plug directly into the switch.

Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.
 
Replying to all in a one..

I have tried to plug in from different working sets and ofcourse there were different cables.

I have tried to plug directly to working and free cisco ports.

I have changed configurations on the "bad" phone playing with DHCP mode, VLANs numbers, static IPs, etc.

BCM does DHCP function for it's phones while DHCP server just provide an address scope. For the 30 sets it works OK.
If I take let's say a "normal-working" 1120/1140 and copy it's configuration to "bad" 1120 - it results with nothing.

Moreover here we have the only one VLAN both for traffic and voice and proper QoS set (thanks to 1Gbps ports).

Port status of working phone is UP/UP from the second it's plugged in. For the "bad" phone there are 3 conditions: DOWN/DOWN - no connection (but "Starting DHCP"), UP/DOWN-UP/DOWN port/line switching - I gess why?, and UP/UP - it's connected!..
But how came I can get it connected approx. once per 10 pluggin-s...

A time ago it seemed like cabling issue - but using direct 3750 patch cods results with the same situation - the phone might stay in "Starting DHCP" or might get connected..
And who knows why..
No config changes.
 
Is it possible that you ran out of IP addresses?

What doesn't kill you only makes you stronger.

If it's true that our species is alone in the universe, then I'd have to say that the universe aimed rather low and settled for very little.---George Carlin RIP
 
I've run into this same thing before. On occasion it has taken 10 phone resets for the phone to suddenly wake up. I've also had issue where the phone gets stuck showing starting DHCP and when I move it to another system it works fine. I find a lot of weird unexplainable things happen w/ these sets. I even had a working get stuck w/ starting dhcp when I unplugged it briefly.
 
One out of 50 Ip phones will do it to me .
Point it to another system with different firmware usually fixed most of it . Some I had to RMA back.
 
Same w/ some of my sets but I never changed the f/w. My sets were upgraded from c1b to c4d once they connected to the system.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top