Table of Contents
Advertisement
show controllers cable-modem mac
The following example indicates that an event in the cable interface driver caused the interface to
reset. This often occurs because a shut or clear command is currently being issued on the interface.
uBR924# show controllers cable-modem 0 mac resets
527986.444 CMAC_LOG_RESET_FROM_DRIVER
528302.042 CMAC_LOG_RESET_FROM_DRIVER
528346.600 CMAC_LOG_RESET_FROM_DRIVER
528444.494 CMAC_LOG_RESET_FROM_DRIVER
Table 6
Message
CMAC_LOG_RESET_CONFIG_FILE_PARSE_FAILED
CMAC_LOG_RESET_LOSS_OF_SYNC
CMAC_LOG_RESET_T4_EXPIRED
CMAC_LOG_RESET_DHCP_WATCHDOG_EXPIRED
CMAC_LOG_RESET_TOD_WATCHDOG_EXPIRED
CMAC_LOG_RESET_PRIVACY_WATCHDOG_EXPIRED
CMAC_LOG_RESET_CHANGE_US_WATCHDOG_EXPIRED
CMAC_LOG_RESET_SECURITY_WATCHDOG_EXPIRED
CMAC_LOG_RESET_CONFIG_FILE_WATCHDOG_EXPIRED
CMAC_LOG_RESET_ALL_FREQUENCIES_SEARCHED
CMAC_LOG_RESET_T2_EXPIRED
CMAC_LOG_RESET_T3_RETRIES_EXHAUSTED
CMAC_LOG_RESET_RANGING_ABORTED
CMAC_LOG_RESET_NO_MEMORY
CMAC_LOG_RESET_CANT_START_PROCESS
CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
CMAC_LOG_RESET_AUTHENTICATION_FAILURE
42
Cisco IOS Release 12.0(5)T
Possible but Uncommon Cable Interface Reset Causes
Description
The format of the DOCSIS configuration file acquired
from the TFTP server is not acceptable.
Synchronization with the CMTS has been lost (SYNC
messages are not being received).
Maintenance ranging opportunities for this
Cisco uBR924 are not being received from the CMTS.
The DHCP server took too long to respond.
The Time Of Day server took too long to respond.
The baseline privacy exchange with the CMTS took too
long.
The Cisco uBR924 was unable to transmit a response to a
UCC-REQ message.
The "full security" exchange with the CMTS took too
long.
The TFTP server took too long to respond.
All downstream frequencies to be searched have been
searched.
Note
This message indicates that downstream
frequencies were found, but the Cisco uBR924 failed to
acquire a downstream lock.
Initial ranging opportunities are not being received.
The CMTS failed too many times to respond to a
RNG-REQ message.
After 16 T3 timeouts, the Cisco uBR924 will reset
Note
the cable interface.
The CMTS commanded the Cisco uBR924 to abort the
ranging process.
The Cisco uBR924 has run out of memory.
The Cisco uBR924 was unable to start an internal process
necessary to complete ranging and registration.
The reading of the configuration file from the TFTP
server failed.
The file might not exist, or it might have incorrect
Note
permissions.
The Cisco uBR924 failed authentication as indicated in a
REG-RSP message from the CMTS.
Advertisement
Table of Contents
