96xx phones "waiting for LLDP" 1

[bdelmar]

IP500 V2 6.0(14) with 9620 and 9650 phones.

Lan port of the IPO is on the Data VLan of 1, Wan port is on the Voice VLan of 3. Set option 242 on the DHCP server on VLan 1. The IPO is acting as the DHCP server on VLan 3.

Plug a phone in, first displays "* to Program, VLan=0". A few seconds the screen goes blanks and comes back with "* to program, VLan=3" it counts for about 3 or 4 seconds, then immediately displays "Waiting for LLDP' and is stuck there.

I see in monitor the phone does get an address from the IPO on VLan 3.

The network switches are Brocade FastIron switches.

I know its something in the switch becase I put an unmanaged POE switch in place, hook the phones up to that, and they come up fine.

Ive tried disabling and enabling LLDP on the Brocade switch.

Any ideas?

 

[kwing112000]

This may help.

http://www.tek-tips.com/viewthread.cfm?qid=1623625&page=1

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries

 

[bdelmar]

Thanks Kevin, I just figured it out. The customer's data vendor did not enter in the entire string for the 242 option, he just did L2Q=1, L2QVLAN=3,VLANTEST=0.

He forget the rest of the settings. MCIPADD=xxx.xxx.xxx.xx, MCPORT=1719, TFTPSRVR=xxx.xxx.xxx.x

Once he entered thats stuff, they come up.

 

[Bas1234]

You should turn off LLDP or configure it the right way.

By adding MCIPADD=xxx.xxx.xxx.xx, MCPORT=1719, TFTPSRVR=xxx.xxx.xxx.x in the options 242 you'll have a 8 day lease in the DHCP reserved list.

I also would check is the extension are sitting in the right IP scope by doing this.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[bdelmar]

Kevin,

That doc you pointed me to that talks about a patch for the phones, if the phone got loaded with the bin files included in 6.0(14), which is the hb96xxua3_11.bin file, would I still need the load it with that patch they are talking about which gives it a new bin of hb96xxr3_171bS.bin?

 

[kwing112000]

I am not really sure. all i did to fix my issue was edit the test file to include the lines in that doc and it worked right away.

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries

 

[bdelmar]

Can I ask what lines you added to the 46xxsetttings. I added the bin files to the fileserver, and the 96xxupgrade file, the phone loads the new bin file, then just keeps reloading the 96xxupgrade file, and then the 46xxsettings file in a constant loop.

 

[bdelmar]

Kevin,

I got it working. That doc and those bin files did the job. Thanks a lot, you saved me big time!

 

[mikeg826]

Kevin -

do you know if you can re-upgrade these phones to Rel3.171b after downgrading them to Rel 3.10 ? I got hit by this bug last week, and had to static IP 20 9620 and doing this allowed the firmware to be completely "downgraded" to Rel 3.1, but now I'm thinking of upgrading back to Rel 3.171b and placing the phones back on DHCP.

>mike

ACE - IP Telephony