Cisco 8832 Administration Manual page 137

Ip conference phone
Hide thumbs Also See for 8832:
Table of Contents

Advertisement

Cisco IP Conference Phone Troubleshooting
Message
IPv6 DHCP Timeout
IPv4 DNS Timeout
IPv6 DNS Timeout
DNS unknown IPv4 Host
DNS unknown IPv6 Host
Description
IPv6 DHCP server did not respond.
IPv4 DNS server did not respond.
IPv6 DNS server did not respond.
IPv4 DNS could not resolve the name of
the TFTP server or Cisco Unified
Communications Manager.
IPv6 DNS could not resolve the name of
the TFTP server or Cisco Unified
Communications Manager.
Cisco IP Conference Phone 8832 Administration Guide for Cisco Unified Communications Manager
Status Messages Fields
Possible Explanation and Action
Network is busy - The errors should resolve
themselves when the network load reduces.
No network connectivity between the IPv6
DHCP server and the phone: Verify the
network connections.
IPv6 DHCP server is down: Check
configuration of IPv6 DHCP server.
Errors persist: Consider assigning a static
IPv6 address.
Network is busy: The errors should resolve
themselves when the network load reduces.
No network connectivity between the IPv4
DNS server and the phone: Verify the
network connections.
IPv4 DNS server is down: Check
configuration of the IPv4 DNS server.
Network is busy: The errors should resolve
themselves when the network load reduces.
No network connectivity between the IPv6
DNS server and the phone: Verify the
network connections.
IPv6 DNS server is down: Check
configuration of the IPv6 DNS server.
Verify that the host names of the TFTP
server or Cisco Unified Communications
Manager are configured properly in IPv4
DNS.
Consider using IPv4 addresses rather than
host names
Verify that the host names of the TFTP
server or Cisco Unified Communications
Manager are configured properly in IPv6
DNS.
Consider using IPv6 addresses rather than
host names
127

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents