Avaya 4600 Series Administrator's Manual page 63

Table 5-1. Some Error Conditions in Operation of 4600 Series IP Telephones —Continued
Condition
The TFTP script file is ignored or not used by the
telephone.
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)
If the telephone is supposed to be powered from the LAN, ensure the LAN is properly
administered and is compliant with IEEE 802.3af.
and the TFTP
application hangs
Troubleshooting Guidelines
Cause/Resolution
CAUSE: The telephone expects lines of
the script file to terminate with a
<Carriage Return><Line Feed>. Some
UNIX applications only terminate lines
with <Line Feed>. Editing the script file
with a UNIX-based editor can strip
<Carriage Return>s from the file,
causing the entire file to be treated as a
comment, and thus be ignored
RESOLUTION: Edit the script file with a
Windows-based editor, or another editor
that does not strip out the <Carriage
Return>.
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