Troubleshooting guide

7-18
Cisco Broadband Local Integrated Services Solution Troubleshooting Guide
OL-5169-01
Chapter 7 Troubleshooting the CMTS
Troubleshooting the Cisco uBR7246VXR
2d01h: 177960.616 CMAC_LOG_TOD_REQUEST_SENT 172.17.110.130
2d01h: 177960.712 CMAC_LOG_RNG_REQ_TRANSMITTED
2d01h: 177960.716 CMAC_LOG_RNG_RSP_MSG_RCVD
2d01h: 177961.716 CMAC_LOG_RNG_REQ_TRANSMITTED
131.CABLEMODEM.CISCO: 2d01h: %UBR900-3-TOD_FAILED_TIMER_EXPIRED:TOD failed, but Cable
Interface proceeding to operational state
2d01h: 177986.616 CMAC_LOG_TOD_WATCHDOG_EXPIRED
2d01h: 177986.616 CMAC_LOG_STATE_CHANGE security_association_state
2d01h: 177986.616 CMAC_LOG_SECURITY_BYPASSED
2d01h: 177986.616 CMAC_LOG_STATE_CHANGE configuration_file
2d01h: 177986.620 CMAC_LOG_LOADING_CONFIG_FILE platinum.cm
2d01h: 177986.644 CMAC_LOG_CONFIG_FILE_PROCESS_COMPLETE
2d01h: 177986.644 CMAC_LOG_STATE_CHANGE registration_state
2d01h: 177986.644 CMAC_LOG_REG_REQ_MSG_QUEUED
2d01h: 177986.648 CMAC_LOG_REG_REQ_TRANSMITTED
2d01h: 177986.652 CMAC_LOG_REG_RSP_MSG_RCVD
2d01h: 177986.652 CMAC_LOG_COS_ASSIGNED_SID 1/1
2d01h: 177986.656 CMAC_LOG_RNG_REQ_QUEUED 1
NOTE— Modem online:
2d01h: 177986.656 CMAC_LOG_REGISTRATION_OK
2d01h: 177986.656 CMAC_LOG_STATE_CHANGE establish_privacy_statee
2d01h: 177986.656 CMAC_LOG_PRIVACY_NOT_CONFIGURED
2d01h: 177986.656 CMAC_LOG_STATE_CHANGE maintenance_state
2d01h: 177988.716 CMAC_LOG_RNG_REQ_TRANSMITTED
Time of day errors almost always point to a DHCP misconfiguration. Possible misconfigurations that can
result in TOD errors include the following:
gateway address misconfigurations
wrong TOD server address
Make sure you can ping the time-server to rule out IP connectivity issues and to make sure the
time-server is available.
Option File Transfer Started-init(o) State
The main configuration and administration interface to the cable modem is the configuration file
downloaded from the provisioning server. This configuration file contains downstream channel and
upstream channel identification and characteristics as well as Class of Service settings, Baseline Privacy
settings, general operational settings, network management information, software upgrade fields, filters,
and vendor specific settings.
A cable modem stuck in init(o) state usually indicates that the cable modem has started or is ready to
start downloading the configuration file, but was unsuccessful due to the following possible reasons:
Incorrect, corrupt, or missing DOCSIS configuration file
Unable to reach the TFTP server, either is unavailable or no IP connectivity
Invalid or missing Configuration Parameters in DOCSIS file
Wrong file permissions on the TFTP server
Note that you may not always see init(o), instead you might see init(i) and then cycling through from
init(r1) to init(i). A more accurate state can be derived by displaying the output of show controller
cable-modem 0 mac state.
Following is an abbreviated display of that output:
#show controller cable-modem 0 mac state
MAC State: configuration_file_state
Ranging SID: 4