CFG TFTP Size Error
|
The configuration file is too large for file system.
|
Power cycle the device.
|
Checksum Error
|
Downloaded software file is corrupted.
|
Obtain a new copy of the device firmware and place it in the
TFTPPath directory. Copy files into this directory only when the TFTP server
software is shut down; otherwise, the files may be corrupted.
|
DHCP timeout
|
DHCP server did not respond.
|
- Network is busy -
The errors resolve themselves when the network load reduces.
- No network
connectivity between the DHCP server and
the device - Verify
the network connections.
- DHCP server is
down - Check configuration of DHCP server.
- Errors persist -
Consider assignment of a static IP address.
|
DNS timeout
|
DNS server did not respond.
|
- Network is busy -
The errors resolve themselves when the network load reduces.
- No network
connectivity between the DNS server and
the device - Verify
the network connections.
- DNS server is down
- Check configuration of DNS server.
|
DNS unknown host
|
DNS could not resolve the name of the TFTP server or Cisco Unified Communications Manager.
|
- Verify that the
hostnames of the TFTP server or
Cisco Unified Communications Manager are configured properly in DNS.
- Consider use of IP
addresses rather than hostnames.
|
Duplicate IP
|
Another device is using the IP address that is assigned to the device.
|
- If
the device has a
static IP address, verify that you have not assigned a duplicate IP address.
- If you are using
DHCP, check the DHCP server configuration.
|
Error update locale
|
One or more localization files could not be found in the
TFTPPath directory or were not valid. The locale was not changed.
|
From Cisco Unified Communications Manager,
check that the following files are located within subdirectories in TFTP
File Management:
|
File not found <Cfg File>
|
The name-based and default configuration file was not found on
the TFTP Server.
|
The configuration file is created when the device is added to the Cisco Unified Communications Manager database. If the device has not been added to the Cisco Unified Communications Manager database,
the TFTP server generates a
CFG File Not Found
response.
|
IP address released
|
The device is configured to release its IP
address.
|
The device remains idle until it is power cycled or until you reset
the DHCP address.
|
Load rejected HC
|
The application that was downloaded is not compatible with
the device.
|
Occurs if you were attempting to install a version of software
on this device that did not support hardware changes on this device.
Check the load ID assigned to the device (from Cisco Unified Communications Manager, choose
).
Reenter the load that is displayed on the device.
|
No default router
|
DHCP or static configuration did not specify a default router.
|
- If
the device has a
static IP address, verify that the default router has been configured.
- If you are using
DHCP, the DHCP server has not provided a default router. Check the DHCP server
configuration.
|
No DNS server IP
|
A name was specified but DHCP or static IP configuration did
not specify a DNS server address.
|
- If
the device has a
static IP address, verify that the DNS server has been configured.
- If you are using
DHCP, the DHCP server has not provided a DNS server. Check the DHCP server
configuration.
|
No Trust List installed
|
The CTL file or the ITL file is not installed on the device.
|
The Trust List is not configured on Cisco Unified Communications Manager, which does not support security by default.
For more information about the Trust List, see the
Cisco Unified Communications Manager Security Guide.
|
Restart requested by Cisco Unified Communications Manager
|
The device is restarting based on a request from Cisco Unified Communications Manager.
|
Configuration changes have likely been made to the device in
Cisco Unified Communications Manager, and
Apply has been pressed so that the
changes take effect.
|
TFTP access error
|
TFTP server is pointing to a directory that does not exist.
|
- If you are using
DHCP, verify that the DHCP server is pointing to the correct TFTP server.
- If you are using
static IP addresses, check configuration of TFTP server.
|
TFTP error
|
The device does not recognize an error code that the
TFTP server provided.
|
Contact Cisco Technical Assistance Center (TAC).
|
TFTP timeout
|
TFTP server did not respond.
|
- Network is busy -
The errors resolve themselves when the network load diminishes.
- No network
connectivity between the TFTP server and
the device - Verify
the network connections.
- TFTP server is
down - Check configuration of TFTP server.
|
Timed Out
|
Supplicant attempted 802.1X transaction but timed out due to the
absence of an authenticator.
|
Authentication typically times out if 802.1X is not configured
on the switch.
|
Trust List update failed, verification failure
|
Updating CTL and ITL files failed.
|
Message displayed in case of error.
|
Version error
|
The name of the load file is incorrect.
|
Make sure that the device load file has the correct name.
|
XmlDefault.cnf.xml, or .cnf.xml corresponding to the
device name
|
Name of the configuration file.
|
None. This configuration file provides an informational
message that indicates the name of the configuration file.
|