show controllers
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
Table 6 | Possible but Uncommon Cable Interface Reset Causes | |
|
|
|
Message |
| Description |
|
| |
CMAC_LOG_RESET_CONFIG_FILE_PARSE_FAILED | The format of the DOCSIS configuration file acquired | |
|
| from the TFTP server is not acceptable. |
|
| |
CMAC_LOG_RESET_LOSS_OF_SYNC | Synchronization with the CMTS has been lost (SYNC | |
|
| messages are not being received). |
|
| |
CMAC_LOG_RESET_T4_EXPIRED | Maintenance ranging opportunities for this | |
|
| Cisco uBR924 are not being received from the CMTS. |
|
| |
CMAC_LOG_RESET_DHCP_WATCHDOG_EXPIRED | The DHCP server took too long to respond. | |
|
| |
CMAC_LOG_RESET_TOD_WATCHDOG_EXPIRED | The Time Of Day server took too long to respond. | |
|
| |
CMAC_LOG_RESET_PRIVACY_WATCHDOG_EXPIRED | The baseline privacy exchange with the CMTS took too | |
|
| long. |
|
| |
CMAC_LOG_RESET_CHANGE_US_WATCHDOG_EXPIRED | The Cisco uBR924 was unable to transmit a response to a | |
|
| |
|
| |
CMAC_LOG_RESET_SECURITY_WATCHDOG_EXPIRED | The “full security” exchange with the CMTS took too | |
|
| long. |
|
| |
CMAC_LOG_RESET_CONFIG_FILE_WATCHDOG_EXPIRED | The TFTP server took too long to respond. | |
|
| |
CMAC_LOG_RESET_ALL_FREQUENCIES_SEARCHED | 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. |
|
| |
CMAC_LOG_RESET_T2_EXPIRED | Initial ranging opportunities are not being received. | |
|
| |
CMAC_LOG_RESET_T3_RETRIES_EXHAUSTED | The CMTS failed too many times to respond to a | |
|
| |
|
| Note After 16 T3 timeouts, the Cisco uBR924 will reset |
|
| the cable interface. |
|
| |
CMAC_LOG_RESET_RANGING_ABORTED | The CMTS commanded the Cisco uBR924 to abort the | |
|
| ranging process. |
|
| |
CMAC_LOG_RESET_NO_MEMORY | The Cisco uBR924 has run out of memory. | |
|
| |
CMAC_LOG_RESET_CANT_START_PROCESS | The Cisco uBR924 was unable to start an internal process | |
|
| necessary to complete ranging and registration. |
|
| |
CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED | The reading of the configuration file from the TFTP | |
|
| server failed. |
|
| Note The file might not exist, or it might have incorrect |
|
| permissions. |
|
| |
CMAC_LOG_RESET_AUTHENTICATION_FAILURE | The Cisco uBR924 failed authentication as indicated in a | |
|
| |
|
|
|