Lldp Troubleshooting; Proposed Solution - Avaya J169 Installing And Administering

Troubleshooting
Condition
The user reports that
personalized labels
cannot be placed on
the button module's
buttons,

LLDP Troubleshooting

If the Waiting for LLDP message appears for more than a few seconds, the message generally
indicates a problem with getting a value for the call server IP address. This error can occur due to
incorrect settings in script files or in the way the network is configured.
On booting, the phone must obtain a valid IP address for the call cerver. The phone can obtain the
value, known as MCIPADD, from several sources:
• A static or manually programmed address on the phone.
• The 46xxsettings.txt file MCIPADD setting.
• A DHCP offer using option 242 that includes the MCIPADD setting.
• Link Layer Discovery Protocol or LLDP.
If the phone cannot find MCIPADD through any of these means, it will fail to register with the Call
Server and will display the Waiting for LLDP message several times before rebooting. For
example, if the MCIPADD value was specified in the 46xxsetting file and the network file server
fails, the phone will not be able to read the MCIPADD value or any of the 46xxsettings file
parameters. Therefore, do not use this method of providing MCIPADD.

Proposed Solution

Procedure
1. A more robust way to provide this value is to use DHCP. You can administer the DHCP
server to provide MCIPADD using DHCP Option 242. You can also administer the
TLSSRVR, HTTPSRVR and L2QVLAN parameters using this option. phones using non-
static addressing automatically use the DHCP request method. Option 242 is the default
DHCP offer and may get MCIPADD and other addresses using this way.
2. The phone displays the Waiting for LLDP message when both the HTTP and HTTPS
Server IP address are not administered. To administer the HTTP and/or HTTPS server,
May 2018
AND the user has tried
using the Program AD
button feature.
AND the user has tried
using the Personalize
Labels option on the
phone.
Installing and Administering Avaya J169/J179 IP Phone H.323
Comments on this document? infodev@avaya.com
Cause/Resolution
RESOLUTION: Verify correct administration.
CAUSE: Improper administration on the call server.
RESOLUTION: Verify correct administration.
CAUSE: The user pressed the button module button
to indicate which button to relabel.
RESOLUTION: The user should use the list displayed
on the phone, scroll to highlight the desired button
label, and press either OK or the corresponding line
button.
196