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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

9620L Phones - Waiting on LLDP 4

Status
Not open for further replies.

robspwing

IS-IT--Management
Oct 29, 2008
232
US
Hi All,

Thanks in advance. We are running IPO 500 R7. We just purchased some 9620L phones and during the initial boot up the phone will hang at the Waiting on LLDP for about 60 seconds.

I did check out the the other post here that took me to this:

my current 96xxupgrade.txt is newer than the one in the link above so that did not help.

I also see in the tek-tips post that you should add string 242 in the DHCP options. However, we use the IPO to hand out the IP address instead of using a DHCP server.

I can press * to program and scroll to the VLAN ID and enter the correct VLAN ID and reboot the phone and it will work but I was trying to bypass doing that step.


one more thing-- on the 9620L phones that we do have working, I do not see a log off button..any idea where that is?

Thanks

Rob

Doc, we better back up. We don't have enough road to get up to 88.
 
If the phones boot in a different VLAN to the system then there is no way the system can issue an address. You need to statically assign the vlan id then the system can finish the job :)

ACSS (SME)
APSS (SME)


"I'm just off to Hartlepool to buy some exploding trousers
 
Thanks amriddle01

(we do have two VLANs one for voice and one for data)

on our 4610 phones the phones will boot up and obtain all of the information without assigning the VLAN id.

I assume the 4610 is a better phone?





Rob

Doc, we better back up. We don't have enough road to get up to 88.
 
set the TEST VLAN=0 on the phone and try again

ACSS - SME
General Geek

1832163.png
 
The handset(s) will boot in the native VLAN, if the system is not in the native VLAN (which in your case I guess it isn't) then it is in a totally different network and broadcast domain, there is no way it can issue an address to either model of handset. If the 4610's do get an address from the system then they have been set to the correct VLAN previously or a DHCP/file server is putting them into the correct VLAN and then the system is issuing an address etc :)

ACSS (SME)
APSS (SME)


"I'm just off to Hartlepool to buy some exploding trousers
 
Or setup your lldp capable switch to broadcast the correct vlan.

What kind of switches are you using?
 
the 46xx uses option 176 not 242. check your dhcp server. i bet it pushes the vlan out and then once the phone is in the correct vlan the ipo takes over

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries
 
thanks for all of the feedback!



DennyHeack = Cisco 2960 switches



kwing112000 - originally we used a DHCP server but we disabled DHCP for the voice VLAN because we are using the IPO 500 to assign the DHCP address.
In Avaya Manager - under System, LAN1, LAN settings, we have DHCP mode set to server.

Rob

Doc, we better back up. We don't have enough road to get up to 88.
 
what do you use for dhcp on the default vlan? have you checked to see if there are strings on it?

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries
 
Rob, the phones are not in the voice vlan on boot though, so they are looking at the DHCP server in the data VLAN, check that server for option 176, if it's there you may as well put the info into option 242 too :)

ACSS (SME)
APSS (SME)


"I'm just off to Hartlepool to buy some exploding trousers
 
Then your done:


I'm setting up a mix of 9608 & 9641 on a 2960 as we speak:

lldp timer 10
lldp holdtime 30
lldp reinit 5
lldp run

interface FastEthernet0/1
description --- IP Phone Ports ---
switchport access vlan 10
switchport voice vlan 100
spanning-tree portfast
end

In this case vlan 10 is data lan, vlan 100 is voice lan.

If a phone refuses to hop correctly, try clearing the phone.

 
kwing112000 - thanks
Our Voice VLAN is 300 and is disabled in Windows DHCP but our Data VLAN is 200 and I do see the following in the DHCP settings

MCIPADD=10.1.3.x,MCPORT=1719,TFTPSRVR=10.1.1.x,L2Q=1,L2QVLAN=300


Do I need this setting for the data VLAN?

Rob

Doc, we better back up. We don't have enough road to get up to 88.
 
I would add an option 242 string and put in L2Q=1,L2QVLAN=300

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries
 
You need to add option 242 and put that string in there with HTTPSRVR=10.1.1.x added after TFTPSRVR=10.1.1.x :)

ACSS (SME)
APSS (SME)


"I'm just off to Hartlepool to buy some exploding trousers
 
just happy for the responses...I am working on adding the option 242 now

Rob

Doc, we better back up. We don't have enough road to get up to 88.
 
What if we have two VLANs for voice, we have VLAN 300 and VLAN 350
can I add two of the L2QVLAN= options in DHCP?

Rob

Doc, we better back up. We don't have enough road to get up to 88.
 
The system and handsets can only be in one of the VLAN's, why would you want two voice VLAN's anyway?

ACSS (SME)
APSS (SME)


"I'm just off to Hartlepool to buy some exploding trousers
 
Well the system can be in two as it has two LAN ports, but you know what I mean :)

ACSS (SME)
APSS (SME)


"I'm just off to Hartlepool to buy some exploding trousers
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top