Cisco UBR904 Troubleshooting Guide - Page 34

Example 3

Get Cisco UBR904 - Router - EN PDF manuals and user guides View all Cisco UBR904 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 34 highlights

Command Reference Example 3 If the DHCP server could not be reached, the error would look like this in the MAC error display: uBR904# show controllers cable-modem 0 mac errors 497989.804 D01.0 Discover sent no Offer received. 498024.046 D01.0 Discover sent no Offer received. 498058.284 D01.0 Discover sent no Offer received. No available DHCP Server. No available DHCP Server. No available DHCP Server. The show controllers cable-modem 0 mac resets command shows only the entries in the MAC log that begin with the field CMAC_LOG_RESET. Collectively presenting these fields provides you with a summary of the most recent reasons why the cable interface was reset. Reset messages and brief explanations are included in the following examples and in Table 6; however, the reset messages in Table 6 do not commonly occur. In the following example, the configuration file downloaded from the TFTP server could not be read. The file might not exist, or the file might have incorrect permissions. uBR904# show controllers cable-modem 0 mac resets 62526.114 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED 62564.368 CMAC_LOG_RESET_T4_EXPIRED 62677.178 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED 62717.462 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED 62757.746 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED 62796.000 CMAC_LOG_RESET_T4_EXPIRED 62908.808 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED 62949.092 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED 62989.380 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED 63029.662 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED 63069.944 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED 63110.228 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED 63148.484 CMAC_LOG_RESET_T4_EXPIRED 63261.296 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED The following example shows that the DHCP server could not be reached. The DHCP server took too long to respond. uBR904# show controllers cable-modem 0 mac resets 497989.804 CMAC_LOG_RESET_DHCP_WATCHDOG_EXPIRED 498024.046 CMAC_LOG_RESET_DHCP_WATCHDOG_EXPIRED 498058.284 CMAC_LOG_RESET_DHCP_WATCHDOG_EXPIRED 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. uBR904# 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 34 Cisco IOS Release 12.0(3)T

  • 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
Command Reference
34
Cisco IOS Release 12.0(3)T
If the DHCP server could not be reached, the error would look like this in the MAC error display:
uBR904#
show controllers cable-modem 0 mac errors
497989.804 D01.0
Discover sent no Offer received.
No available DHCP Server.
498024.046 D01.0
Discover sent no Offer received.
No available DHCP Server.
498058.284 D01.0
Discover sent no Offer received.
No available DHCP Server.
Example 3
The
show controllers cable-modem 0 mac resets
command shows only the entries in the MAC log
that begin with the field
CMAC_LOG_RESET
. Collectively presenting these fields provides you with a
summary of the most recent reasons why the cable interface was reset.
Reset messages and brief explanations are included in the following examples and in Table 6;
however, the reset messages in Table 6 do not commonly occur.
In the following example, the configuration file downloaded from the TFTP server could not be read.
The file might not exist, or the file might have incorrect permissions.
uBR904#
show controllers cable-modem 0 mac resets
62526.114 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
62564.368 CMAC_LOG_RESET_T4_EXPIRED
62677.178 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
62717.462 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
62757.746 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
62796.000 CMAC_LOG_RESET_T4_EXPIRED
62908.808 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
62949.092 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
62989.380 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
63029.662 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
63069.944 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
63110.228 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
63148.484 CMAC_LOG_RESET_T4_EXPIRED
63261.296 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
The following example shows that the DHCP server could not be reached. The DHCP server took
too long to respond.
uBR904#
show controllers cable-modem 0 mac resets
497989.804 CMAC_LOG_RESET_DHCP_WATCHDOG_EXPIRED
498024.046 CMAC_LOG_RESET_DHCP_WATCHDOG_EXPIRED
498058.284 CMAC_LOG_RESET_DHCP_WATCHDOG_EXPIRED
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.
uBR904#
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