Avaya 4600 Series Administrator's Manual page 65

Table 5-1. Some Error Conditions in Operation of 4600 Series IP Telephones —Continued
Condition
Power to the telephone
is interrupted while the
telephone is saving the
application file
The DHCP server
indicates the 4600
Telephone reports itself
as a Token Ring device,
and refuses to provide
the telephone an
address.
There are three areas where installers can troubleshoot problems before seeking assistance from
the system or LAN administrator:
1. Check the wiring (power and Ethernet) for the following:
Whether all components are plugged in correctly.
Check LAN connectivity in both directions to all servers (DHCP, TFTP, DEFINITY)
2. If you are using static addressing, do the following:
Use the View command to find the names of the files being used and verify that these
filenames match those on the TFTP server. Check on the Avaya website to verify whether
the correct files are being used.
Use the ADDR option to verify IP addresses.
Use the QOS option to verify QoS parameters.
Refer to Chapter 3 of the 4600 Series IP Telephone Installation Guide.
3. If the 4600 Series IP Telephone is not communicating with the system (DHCP, TFTP, or
DEFINITY), make a note of the last message that was displayed and consult the system
administrator.
and the TFTP
application hangs
Troubleshooting Guidelines
Cause/Resolution
CAUSE: The TFTP server hangs if
power is interrupted while a telephone is
saving the application file.
RESOLUTION: Restart the TFTP
server.
CAUSE: Early versions of the 4600
Series Telephones erroneously report
being a Token Ring device. With most
DHCP servers, this does not matter.
Some LINUX servers, however, will
refuse to issue addresses to Ethernet
devices reporting to be Token Ring
devices.
RESOLUTION: Administer the DHCP
server to delete all MAC and IP
addresses associated with Lucent
Technologies or Avaya, or allow the
associated DHCP leases to expire.
Error Conditions
5-5