Cisco UBR904 Troubleshooting Guide - Page 33

Example 2

Page 33 highlights

show controllers cable-modem mac *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar 7 01:43:15: 528317.958 CMAC_LOG_RNG_RSP_MSG_RCVD 7 01:43:15: 528317.960 CMAC_LOG_ADJUST_TX_POWER 7 01:43:15: 528317.962 CMAC_LOG_POWER_LEVEL_IS 7 01:43:15: 528317.964 CMAC_LOG_RANGING_CONTINUE 7 01:43:16: 528318.968 CMAC_LOG_RNG_REQ_TRANSMITTED 7 01:43:16: 528318.970 CMAC_LOG_RNG_RSP_MSG_RCVD 7 01:43:16: 528318.974 CMAC_LOG_RANGING_SUCCESS 7 01:43:16: 528318.976 CMAC_LOG_STATE_CHANGE 7 01:43:16: 528318.978 DHCP_COMPLETE 7 01:43:16: 528318.980 CMAC_LOG_STATE_CHANGE 7 01:43:16: 528318.982 CMAC_LOG_TOD_COMPLETE 7 01:43:16: 528318.984 CMAC_LOG_STATE_CHANGE 7 01:43:16: 528318.986 CMAC_LOG_SECURITY_BYPASSED 7 01:43:16: 528318.988 CMAC_LOG_STATE_CHANGE 7 01:43:16: 528318.992 CMAC_LOG_CONFIG_FILE_PROCESS_COMPLETE 7 01:43:16: 528319.028 CMAC_LOG_STATE_CHANGE 7 01:43:16: 528319.030 CMAC_LOG_REG_REQ_MSG_QUEUED 7 01:43:16: 528319.036 CMAC_LOG_REG_REQ_TRANSMITTED 7 01:43:16: 528319.038 CMAC_LOG_REG_RSP_MSG_RCVD 7 01:43:16: 528319.040 CMAC_LOG_COS_ASSIGNED_SID 7 01:43:16: 528319.044 CMAC_LOG_RNG_REQ_QUEUED 7 01:43:16: 528319.046 CMAC_LOG_REGISTRATION_OK 7 01:43:16: 528319.048 CMAC_LOG_STATE_CHANGE 7 01:43:16: 528319.052 CMAC_LOG_STATE_CHANGE 14 34.0 dBmV (commanded) dhcp_state establish_tod_state security_association_state configuration_file_state registration_state 1/4 4 establish_privacy_state maintenance_state If the DHCP server could not be reached, the error would look like this in the MAC log: 497959.800 CMAC_LOG_STATE_CHANGE 497969.864 CMAC_LOG_RNG_REQ_TRANSMITTED 497969.866 CMAC_LOG_RNG_RSP_MSG_RCVD 497979.936 CMAC_LOG_RNG_REQ_TRANSMITTED 497979.938 CMAC_LOG_RNG_RSP_MSG_RCVD 497989.802 CMAC_LOG_WATCHDOG_TIMER 497989.804 CMAC_LOG_RESET_DHCP_WATCHDOG_EXPIRED 497989.804 CMAC_LOG_STATE_CHANGE 497989.806 CMAC_LOG_DHCP_PROCESS_KILLED dhcp_state reset_interface_state The fields in this display are explained in the "Step 4-Interpret the MAC Log File and Take Action" section on page 10. Example 2 MAC error log information is displayed in the following example, which is also reported via SNMP: uBR904# show controllers cable-modem 0 mac errors 74373.574 R02.0 No Ranging Response received. T3 time-out. 74374.660 R02.0 No Ranging Response received. T3 time-out. 74375.508 R02.0 No Ranging Response received. T3 time-out. 74375.748 R02.0 No Ranging Response received. T3 time-out. 74375.748 R03.0 Ranging Request Retries exhausted. 74376.112 R02.0 No Ranging Response received. T3 time-out. 74376.354 R02.0 No Ranging Response received. T3 time-out. 74376.778 R02.0 No Ranging Response received. T3 time-out. 74377.442 R02.0 No Ranging Response received. T3 time-out. This output indicates that the cable modem acquired a downstream lock, successfully read a UCD, and successfully read a MAP. However, it was unable to communicate with the CMTS after ranging through all upstream transmit power levels (from 8 dBmv to 61 dBmv). The cable modem tried to communicate with the CMTS 16 times without success, after which it reset the cable interface to try to find a better downstream frequency. Troubleshooting Tips for the Cisco uBR904 Cable Modem 33

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62

show controllers cable-modem mac
Troubleshooting Tips for the Cisco uBR904 Cable Modem
33
*Mar
7 01:43:15: 528317.958 CMAC_LOG_RNG_RSP_MSG_RCVD
*Mar
7 01:43:15: 528317.960 CMAC_LOG_ADJUST_TX_POWER
14
*Mar
7 01:43:15: 528317.962 CMAC_LOG_POWER_LEVEL_IS
34.0
dBmV (commanded)
*Mar
7 01:43:15: 528317.964 CMAC_LOG_RANGING_CONTINUE
*Mar
7 01:43:16: 528318.968 CMAC_LOG_RNG_REQ_TRANSMITTED
*Mar
7 01:43:16: 528318.970 CMAC_LOG_RNG_RSP_MSG_RCVD
*Mar
7 01:43:16: 528318.974 CMAC_LOG_RANGING_SUCCESS
*Mar
7 01:43:16: 528318.976 CMAC_LOG_STATE_CHANGE
dhcp_state
*Mar
7 01:43:16: 528318.978 DHCP_COMPLETE
*Mar
7 01:43:16: 528318.980 CMAC_LOG_STATE_CHANGE
establish_tod_state
*Mar
7 01:43:16: 528318.982 CMAC_LOG_TOD_COMPLETE
*Mar
7 01:43:16: 528318.984 CMAC_LOG_STATE_CHANGE
security_association_state
*Mar
7 01:43:16: 528318.986 CMAC_LOG_SECURITY_BYPASSED
*Mar
7 01:43:16: 528318.988 CMAC_LOG_STATE_CHANGE
configuration_file_state
*Mar
7 01:43:16: 528318.992 CMAC_LOG_CONFIG_FILE_PROCESS_COMPLETE
*Mar
7 01:43:16: 528319.028 CMAC_LOG_STATE_CHANGE
registration_state
*Mar
7 01:43:16: 528319.030 CMAC_LOG_REG_REQ_MSG_QUEUED
*Mar
7 01:43:16: 528319.036 CMAC_LOG_REG_REQ_TRANSMITTED
*Mar
7 01:43:16: 528319.038 CMAC_LOG_REG_RSP_MSG_RCVD
*Mar
7 01:43:16: 528319.040 CMAC_LOG_COS_ASSIGNED_SID
1/4
*Mar
7 01:43:16: 528319.044 CMAC_LOG_RNG_REQ_QUEUED
4
*Mar
7 01:43:16: 528319.046 CMAC_LOG_REGISTRATION_OK
*Mar
7 01:43:16: 528319.048 CMAC_LOG_STATE_CHANGE
establish_privacy_state
*Mar
7 01:43:16: 528319.052 CMAC_LOG_STATE_CHANGE
maintenance_state
If the DHCP server could not be reached, the error would look like this in the MAC log:
497959.800 CMAC_LOG_STATE_CHANGE
dhcp_state
497969.864 CMAC_LOG_RNG_REQ_TRANSMITTED
497969.866 CMAC_LOG_RNG_RSP_MSG_RCVD
497979.936 CMAC_LOG_RNG_REQ_TRANSMITTED
497979.938 CMAC_LOG_RNG_RSP_MSG_RCVD
497989.802 CMAC_LOG_WATCHDOG_TIMER
497989.804 CMAC_LOG_RESET_DHCP_WATCHDOG_EXPIRED
497989.804 CMAC_LOG_STATE_CHANGE
reset_interface_state
497989.806 CMAC_LOG_DHCP_PROCESS_KILLED
The fields in this display are explained in the “Step 4—Interpret the MAC Log File and Take Action”
section on page 10.
Example 2
MAC error log information is displayed in the following example, which is also reported via SNMP:
uBR904#
show controllers cable-modem 0 mac errors
74373.574 R02.0
No Ranging Response received.
T3 time-out.
74374.660 R02.0
No Ranging Response received.
T3 time-out.
74375.508 R02.0
No Ranging Response received.
T3 time-out.
74375.748 R02.0
No Ranging Response received.
T3 time-out.
74375.748 R03.0
Ranging Request Retries exhausted.
74376.112 R02.0
No Ranging Response received.
T3 time-out.
74376.354 R02.0
No Ranging Response received.
T3 time-out.
74376.778 R02.0
No Ranging Response received.
T3 time-out.
74377.442 R02.0
No Ranging Response received.
T3 time-out.
This output indicates that the cable modem acquired a downstream lock, successfully read a UCD,
and successfully read a MAP. However, it was unable to communicate with the CMTS after ranging
through all upstream transmit power levels (from 8 dBmv to 61 dBmv). The cable modem tried to
communicate with the CMTS 16 times without success, after which it reset the cable interface to try
to find a better downstream frequency.