|
|
This section describes the cable-specific commands available to the family of Cisco cable customer premises equipment (CPE) devices. See the following sections for more information:
Table 28 lists the Cisco cable CPE platforms and Cisco IOS releases that support the commands listed in this section. Earlier Cisco IOS software releases might not support all the commands listed, or might support them on fewer platforms or with a limited functionality. See the description of each command for complete details.
| Platform | Cisco IOS Release |
|---|---|
Cisco uBR904 Cable Access Router | Release 12.1(3) |
Cisco uBR905 Cable Access Router | Release 12.1(3)XL |
Cisco uBR924 Cable Access Router | Release 12.1(3)T |
Cisco uBR914 Cable Data Service Unit | Release 12.1 (3)T |
![]() |
Note Not all platforms support all commands, and support for some commands depends on the specific Cisco IOS release. See the description for each command for a list of the supported platforms and required Cisco IOS releases. |
Many of the "related commands" mentioned in this section are not cable-specific commands and thus are not described in this section. Also, other platforms support some of these commands with additional options. For a description of these and other non-cable specific commands, see the command reference documentation for Cisco IOS Release 12.1, available on CCO and the Documentation CD-ROM.
This section describes the following cable-specific commands.
To configure the Cisco uBR924 cable access router so that it configures its Ethernet interface or Network Address Translation (NAT) address pool with an IP address supplied by the DHCP server, use the cable dhcp-proxy cable interface command. To disable this feature (so that you can then manually assign an IP address to the Ethernet interface or NAT address pool), use the no cable dhcp-proxy cable interface command.
Cisco uBR924 cable access router
cable dhcp-proxy {interface ethernet number | nat pool-name}
no cable dhcp-proxy {interface ethernet number | nat pool-name}
![]() |
Note This command cannot be used when the Cisco uBR924 cable access router is configured for DOCSIS bridging. |
Syntax Description
interface ethernet number The Ethernet interface to be assigned the static IP address from the DHCP server. (Because the Cisco uBR924 cable access router has only one Ethernet interface, the only allowable number is 0). nat pool-name The name of the NAT pool to be created using the IP address and subnet mask supplied by the DHCP server. (This is equivalent to giving the ip nat pool pool-name start-ip end-ip netmask subnet command, using the IP address and subnet mask supplied by the DHCP server.)

Note This option should be used only when the Cisco uBR924 cable access router is configured for routing mode.
Defaults
No default behavior or values.
Command Modes
Interface configuration (cable interface only)
Command History
12.1(1)T This command was introduced for the Cisco uBR924 cable access router.
Release
Modification
Usage Guidelines
This command is useful in two situations:
After configuring the Cisco uBR924 cable access router with the cable dhcp-proxy command, reboot the router. During the DOCSIS provisioning process, the router sends a DHCP client request to obtain an IP address for the cable interface.
The router then sends a proxy DHCP request to the DHCP server using the Ethernet interface's MAC address. The DHCP server replies with a second IP address that the router assigns to either the Ethernet interface or to the NAT pool, depending on which option was used in the cable dhcp-proxy command.
![]() |
Note When replying to the proxy request for the Ethernet interface, the DHCP server should assign an IP address on the same network as the CPE devices that are attached to the router's Ethernet interface. |
Examples
The following example configures the Cisco uBR924 cable access router so that it makes a proxy DHCP request to obtain an IP address for its Ethernet interface:
ubr924(config)# int c0 ubr924(config-if)# cable dhcp-proxy interface Ethernet 0
The following example creates a NAT address pool with the IP address assigned by the DHCP server; this IP address must be in the network attached to the Ethernet address (which in this case is 192.168.100.0).
ubr924(config)# ip nat inside source list 1 pool net-208 overload ubr924(config)# interface cable0 ubr924(config-if)# ip nat outside ubr924(config-if)# no cable compliant bridge ubr924(config-if)# cable dhcp-proxy nat net-208 ubr924(config-if)# exit ubr924(config)# interface ethernet0 ubr924(config-if)# ip address 192.168.100.94 255.255.255.0 ubr924(config-if)# ip nat inside ubr924(config-if)# exit ubr924(config)# access-list 1 permit 192.168.100.0 0.0.0.255 ubr924(config)#
Related Commands
None.
To enable DOCSIS-compliant bridging for a cable access router interface at startup, use the cable-modem compliant bridge command in cable interface configuration command. To disable DOCSIS-compliant bridging (which is required to enable routing mode), use the no form of this command.
Cisco uBR904, uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
cable-modem compliant bridge
no cable-modem compliant bridge
Syntax Description
This command has no arguments or keywords.
Defaults
DOCSIS-compliant bridging is enabled by default.
Command Modes
Cable interface configuration
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Usage Guidelines
It is normally not necessary to enter this command in data-over-cable bridging applications because DOCSIS-compliant bridging is enabled by default. However, to configure the router for full transparent bridging or for routing mode, use the no form of the command and then configure the router as desired using the appropriate CLI commands.
Examples
The following example shows how to enter the cable-modem compliant bridge command for a cable access router interface, starting from global configuration mode:
interface cable-modem 0 cable-modem compliant bridge
Related Commands
Modifies the saved downstream channel setting and upstream power value on a cable access router interface. Enables a faster downstream search algorithm on a cable access router interface. Enables the QPSK modulation scheme in the upstream direction from the cable modem interface to the headend. Allows voice calls to be sent upstream over the cable interface via best effort.
Command
Description
To modify the saved downstream channel setting and upstream power value on a cable access router interface, use the cable-modem downstream saved channel command in cable interface configuration mode. To remove the saved settings, which will be saved at the next initialization cycle, use the no form of this command.
Cisco uBR904, uBR924 cable access routers
cable-modem downstream saved channel ds-frequency us-power
no cable-modem downstream saved channel ds-frequency us-power
![]() |
Note Cisco IOS Release 12.1(2)T removed this command from the CLI for all platforms and reserved it for exclusive use by the DOCSIS provisioning process. |
Syntax Description
ds-frequency Downstream channel frequency in Hz, which can be from 91000000 to 860000000. us-power Upstream power level in decibels per millivolt (dBmV), which can be from 8 to 61.
Defaults
Enabled
Command Modes
Cable interface configuration
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(2)T This command was removed from the CLI for all platforms and reserved for exclusive use by the DOCSIS provisioning process.
Release
Modification
Usage Guidelines
This command is auto-generated by the operation of the cable MAC layer process. The DOCSIS RFI specification requires that cable modems remember the downstream frequency and upstream power of the last successfully ranged session. These parameters are called up as the first downstream frequency and upstream power to use the next time the cable modem is booted. This operation dramatically speeds up the channel search.
Use the no cable-modem downstream saved channel ds-frequency us-power command to remove the saved frequency and power setting from the running configuration, which will be saved at the next initialization cycle.
Cisco recommends that this command NOT be used by end users of the Cisco uBR924 cable access router.
Examples
The following example shows how to remove the downstream frequency of 91000000 Hz and the upstream power level of 33 dBmV from the running configuration of a cable-modem interface, starting from global configuration mode:
interface cable-modem 0 no cable-modem downstream saved channel 91000000 33
Related Commands
cable max-hosts Enables DOCSIS-compliant transparent bridging for a cable modem interface at startup. Enables a faster downstream search algorithm on a cable access router interface. Enables the QPSK modulation scheme in the upstream direction from the cable modem interface to the headend. Allows voice calls to be sent upstream over the cable interface via best effort.
Command
Description
To enable a faster downstream search algorithm on a cable access router interface, use the cable-modem fast-search command in cable interface configuration mode. To disable the downstream fast-search feature, use the no form of this command.
Cisco uBR904, uBR924 cable access routers
cable-modem fast-search
no cable-modem fast-search
![]() |
Note Cisco IOS Release 12.1(2)T removed this command from the CLI for all platforms and reserved it for exclusive use by the DOCSIS provisioning process. |
Syntax Description
There are no keywords or arguments for this command.
Defaults
Disabled
Command Modes
Cable interface configuration
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(2)T This command was removed from the CLI for all platforms and reserved for exclusive use by the DOCSIS provisioning process.
Release
Modification
Usage Guidelines
This feature speeds up the frequency search performed by the cable access router. Normally it takes the cable access router about 30 to 50 seconds to sample 30 to 50 frequencies. The cable-modem fast-search command can reduce this search time. However, there might be some cases where this fast-search algorithm might not perform as well as the default algorithm. Trial and error is the only way to discover how well this feature works for your environment.
Examples
The following example shows how to enter the cable-modem fast-search command, beginning in global configuration mode:
interface cable-modem 0 cable-modem fast-search
Related Commands
cable max-hosts Enables DOCSIS-compliant transparent bridging for a cable modem interface at startup. Modifies the saved downstream channel setting and upstream power value on a cable access router interface. Enables the QPSK modulation scheme in the upstream direction from the cable modem interface to the headend. Allows voice calls to be sent upstream over the cable interface via best effort.
Command
Description
To enable the QPSK modulation scheme in the upstream direction from the cable access router interface to the headend, use the cable-modem upstream preamble qpsk command in cable interface configuration mode. To disable upstream modulation for the interface, use the no form of this command.
Cisco uBR904, uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
cable-modem upstream preamble qpsk
no cable-modem upstream preamble qpsk
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Interface configuration
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Examples
The following example shows how to enter the cable-modem upstream preamble qpsk command for a cable access router interface, beginning in global configuration mode:
interface cable-modem 0 cable-modem upstream preamble qpsk
Related Commands
cable max-hosts Enables DOCSIS-compliant transparent bridging for a cable modem interface at startup. Modifies the saved downstream channel setting and upstream power value on a cable access router interface. Enables a faster downstream search algorithm on a cable access router interface. Allows voice calls to be sent upstream over the cable interface via best effort.
Command
Description
To allow voice calls to be sent upstream over the cable interface via best effort, use the cable-modem voip best-effort command in cable interface configuration mode. To disable best-effort voice calls, use the no form of this command.
Cisco uBR924 cable access router
cable-modem voip best-effort
no cable-modem voip best-effort
![]() |
Note Cisco IOS Release 12.1(2)T removed this command from the CLI for all platforms and reserved it for exclusive use by the DOCSIS provisioning process. |
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Cable interface configuration
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(2)T This command was removed from the CLI for all platforms and reserved for exclusive use by the DOCSIS provisioning process.
Release
Modification
Usage Guidelines
This command allows you to configure the voice traffic on a Cisco uBR924 to allow only calls having a high priority service identifier (SID) to be connected.
If the dynamic configuration of high priority queues for voice traffic fails, or if the far end cannot support the multiple SIDs and multiple classes of service required by high priority traffic, the flag set by this command will be checked. If enabled (the default setting), the call will be allowed to go through. If disabled, the call will fail.
Examples
The following example shows how to disable best-effort voice calls on a Cisco uBR924 cable interface beginning in global configuration mode:
interface cable-modem 0 no cable-modem voip best-effort
Related Commands
cable max-hosts Enables DOCSIS-compliant transparent bridging for a cable modem interface at startup. Modifies the saved downstream channel setting and upstream power value on a cable access router interface. Enables a faster downstream search algorithm on a cable access router interface. Enables the QPSK modulation scheme in the upstream direction from the cable modem interface to the headend.
Command
Description
To reset the Cisco uBR905 router's hardware accelerator's statistical and error counters, use the clear crypto engine accelerator counter privileged EXEC command.
Cisco uBR905 cable access router
clear crypto engine accelerator counter
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC.
Command History
12.1(3)XL This command was introduced for the Cisco uBR905 router.
Release
Modification
Usage Guidelines
This command resets the statistical and error counters for the Cisco uBR905 router's hardware accelerator to zero.
Examples
The following example clears the Cisco uBR905 router's statisticAL and error counters to zero:
uBR905# clear crypto engine accelerator counter uBR905#
Related Commands
crypto ca Defines the parameters for the certification authority used for a session. crypto cisco Defines the encryption algorithms and other parameters for a session. crypto dynamic-map Creates a dynamic map crypto configuration for a session. crypto ipsec Defines the IPsec security associations and transformation sets. crypto isakmp Enables and defines the IKE protocol and its parameters. crypto key Generates and exchanges keys for a cryptographic session. crypto map Creates and modifies a crypto map for a session. debug crypto engine accelerator control Prints each control command as it is given to the crypto engine. debug crypto engine accelerator packet Prints information about each packet sent for encryption and decryption. show crypto engine accelerator ring control Prints the contents of command ring, which queues the control commands that are being sent to the crypto engine. show crypto engine accelerator ring packet Prints the contents of the transmit packet ring, which contains the packets being sent to the crypto engine for encryption and decryption. show crypto engine accelerator sa-database Prints the active (in-use) entries in the crypto engine security association (SA) database. show crypto engine accelerator statistic Print out the current run-time statistics and error counters for the crypto engine. show crypto engine configuration Print out the version and configuration information for the crypto engine. show crypto engine brief Print out a summary of the configuration information for the crypto engine. show crypto engine connections Print out a list of the current connections maintained by the crypto engine.
Command
Description
To enable the use of the Cisco uBR905 router's onboard hardware accelerator for IPsec encryption, use the crypto engine accelerator global configuration command. To disable the use of the onboard hardware IPsec accelerator (and thereby perform IPsec encryption/decryption in software), use the no crypto engine accelerator global configuration command.
crypto engine acceleratorSyntax Description
This command has no keywords or arguments.
Defaults
The hardware accelerator for IPsec encryption is enabled by default.
Command Modes
Global configuration.
Command History
12.1(3)T This command was introduced for the Cisco 1700 series router and other Cisco routers that support hardware accelerators for IPsec encryption. 12.1(3)XL This command was introduced for the Cisco uBR905 router.
Release
Modification
Usage Guidelines
This command is not normally needed for typical operations because the Cisco uBR905 router's onboard hardware accelerator for IPsec encryption is enabled by default. The hardware accelerator should not be disabled except on instruction from Cisco TAC personnel.
Examples
The following example enables the Cisco uBR905 router's onboard hardware accelerator for IPsec encryption. This is normally needed only after the accelerator has been disabled for testing or debugging purposes.
uBR905# crypto engine accelerator uBR905#
The following example disables the Cisco uBR905 router's onboard hardware accelerator. If IPsec encryption is configured, all current connections are brought down. Future encryption will be performed by the Cisco IOS software, which has the same functionality as the hardware accelerator, but performance is significantly slower.
uBR905# no crypto engine accelerator Warning! all current connections will be torn down. Do you want to continue? [yes/no]: y ...Crypto accelerator in slot 0 disabled ...switching to SW IPsec crypto engine uBR905#
Related Commands
clear crypto engine accelerator counter Resets the statistical and error counters for the hardware accelerator crypto engine to zero. crypto ca Defines the parameters for the certification authority used for a session. crypto cisco Defines the encryption algorithms and other parameters for a session. crypto dynamic-map Creates a dynamic map crypto configuration for a session. crypto engine accelerator Enables or disables the onboard hardware accelerator crypto engine. crypto ipsec Defines the IPsec security associations and transformation sets. crypto isakmp Enables and defines the IKE protocol and its parameters. crypto key Generates and exchanges keys for a cryptographic session. crypto map Creates and modifies a crypto map for a session. debug crypto engine accelerator control Prints each control command as it is given to the crypto engine. debug crypto engine accelerator packet Prints information about each packet sent for encryption and decryption. show crypto engine accelerator ring control Prints the contents of command ring, which queues the control commands that are being sent to the crypto engine. show crypto engine accelerator ring packet Prints the contents of the transmit packet ring, which contains the packets being sent to the crypto engine for encryption and decryption. show crypto engine accelerator sa-database Prints the active (in-use) entries in the crypto engine security association (SA) database. show crypto engine accelerator statistic Print out the current run-time statistics and error counters for the crypto engine. show crypto engine configuration Print out the version and configuration information for the crypto engine. show crypto engine brief Print out a summary of the configuration information for the crypto engine. show crypto engine connections Print out a list of the current connections maintained by the crypto engine.
Command
Description
Cisco uBR924 cable access router
dtmf-relay [cisco-rtp] [h245-signal] [h245-alphanumeric]
no dtmf-relay
Syntax Description
cisco-rtp Forwards DTMF tones using the Real-Time Transport Protocol (RTP) with a Cisco proprietary payload type. h245-alphanumeric Forwards DTMF tones using the H.245 Alphanumeric User Input Indication method. This transmits each tone using a fixed duration of 500 milliseconds. Supports tones 0-9, *, #, and A-D. h245-signal Forwards DTMF tones using the H.245 Signal User Input Indication method. This transmits each tone using the original duration. Supports tones 0-9, *, #, and A-D.

Note RTP is a proprietary Cisco protocol that interoperates only between two Cisco access servers or routers running Cisco IOS images that support the RTP protocol. This typically requires Cisco IOS 12.0(5)T or later releases; see the router's release notes for complete information.
Defaults
By default, DTMF tones are transmitted inband, as part of the voice traffic.
Command Modes
Dial-peer voice configuration mode.
Command History
12.0(7)XR and 12.1(1)T Support was added for the Cisco uBR924 cable access router.
Release
Modification
Usage Guidelines
DTMF tones are generated when you press the keypad digits on a touch-tone phone. DTMF tones are most commonly used to dial calls, but they can also be used during a call to interact with an Interactive Voice Response (IVR) system, such as voicemail, automated banking services and so on. By default, DTMF tones are transmitted along with the regular voice traffic, but this can cause problems with some IVR systems.
In particular, IVR systems might not recognize DTMF tones when using highly compressed CODECs such as G.729a. These CODECs are highly optimized for voice frequencies, but they can distort DTMF tones, preventing IVR systems from recognizing the tones. To avoid this problem, use one or more of the following methods of transmitting DTMF tones in an out of band channel, separately from the voice traffic:
You can enable more than one DTMF relay option for a particular dial peer, to support multiple destinations that might use different methods. If you enable more than one option, and if the peer is capable of receiving DTMF in more than one of these formats, the router selects the DTMF format with the highest priority:
1. Cisco RTP (highest priority)
2. H.245 Signal
3. H.245 Alphanumeric
4. NoneDTMF is sent inband
Examples
The following example configures an outgoing dial peer so that DTMF tones to that destination are transmitted using the Cisco RTP protocol, if it is supported by the remote end; otherwise, the DTMF tones are transmitted using the H.245 signaling protocol.
ubr924(config)# dial-peer voice 100 voip ubr924(config-dial-peer)# destination-pattern 555-1212 ubr924(config-dial-peer)# session target ipv4:192.168.100.110 ubr924(config-dial-peer)# dtmf-relay cisco-rtp h245-signal ubr924(config-dial-peer)# exit ubr924(config)#
The following example reconfigures the above dial peer and disables out of band DTMF signaling, so that the DTMF tones are sent inband, as part of the voice traffic:
ubr924(config)# dial-peer voice 100 voip ubr924(config-dial-peer)# no dtmf-relay ubr924(config-dial-peer)# exit ubr924(config)#
Related Commands
codec Specifies the voice coder rate of speech for a dial peer. dial-peer Enters dial peer voice configuration mode.
Command
Description
Cisco BR924 cable access router
h323-gateway voip bind srcaddr ip-address
no h323-gateway voip bind srcaddr
Syntax Description
ip-address Specifies the IP address to be used for outgoing H.323 traffic, which includes H.225, H.245, and RAS messages. This typically is the IP address assigned to the Ethernet interface.
Defaults
No defaults assigned. By default, H.323 traffic is transmitted with the IP address assigned to the cable interface.
Command Modes
Interface configuration
Command History
12.1(2)T This command is introduced for the Cisco uBR924 cable access router.
Release
Modification
Usage Guidelines
The h323-gateway voip bind command can be used with any interface, but it is primarily used with the Cisco uBR924 cable access router's Ethernet interface when configuring a virtual private network (VPN). In this configuration, the h323-gateway voip bind command configures the router so that VoIP traffic is sent using the IP address of the Ethernet interface (as opposed to the default behavior, which is to use the IP address of the default outgoing interface, which is the cable interface).
The h323-gateway voip bind command allows the enterprise network to maintain the H.323 gatekeeper and gateway in the enterprise network's address space. Without the h323-gateway voip bind command, outgoing voice traffic uses the IP address of the cable interface. This requires that the H.323 gatekeeper and gateway be maintained in the cable service provider's address space, which is not desirable if the enterprise needs to control the voice network and VPN configuration.
![]() |
Note The h323-gateway voip bind command can be used only when the Cisco uBR924 cable access router is operating in routing mode. This command has no effect when the router is operating in DOCSIS bridging mode. |
Examples
The following example shows the Ethernet interface being configured with the IP address of 192.168.100.94, and that H.323 traffic will be transmitted using that IP address:
ubr924(config)# interface ethernet0 ubr924(config-if)# ip address 192.168.100.94 255.255.255.0 ubr924(config-if)# h323-gateway voip bind srcaddr 192.168.100.94 ubr924(config-if)#
The following example disables the H.323 binding, so that H.323 voice traffic is transmitted using the cable interface's IP address:
ubr924(config-if)# no h323-gateway voip bind srcaddr ubr924(config-if)#
Related Commands
h323-gateway voip h323-id Defines the H.323 name that identifies this Cisco uBR924 cable access router gateway to its associated gatekeeper. h323-gateway voip id Defines the name and IP address of the gatekeeper for this gateway. h323-gateway voip interface Configures the interface as an H.323 interface. h323-gateway voip tech-prefix Defines the technology prefix that the gateway uses to register with the gatekeeper.
Command
Description
To specify the cable interface on a Cisco uBR900 series cable access router, enter the interface cable-modem command from global configuration mode.
Cisco uBR904, uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
interface cable-modem number
Syntax Description
number The interface number of the cable interface on the rear panel of the cable access router.
Defaults
Disabled
Command Modes
Global configuration
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Usage Guidelines
When this command is entered, the Cisco uBR900 series cable access router switches from global configuration mode to interface configuration mode.
Examples
The following example brings up cable access router interface 0 and displays the available cable-modem interface configuration commands:
uBR924(config)#interface cable-modem 0uBR924(config-if)# cable-modem ? compliant Enter compliant modes for interface downstream Downstream channel characteristics fast-search Enable/disable the DS fast search upstream upstream channel characteristics voip Options for Voice over IP traffic over the cable interface uBR924(config-if)#
Related Commands
cable-modem compliant bridge Enables DOCSIS-compliant transparent bridging on the Cisco uBR900 series at startup. Modifies the saved downstream channel setting and upstream power value on the cable interface of a Cisco uBR900 series. Enables a faster downstream search algorithm on the cable interface of a Cisco uBR900 series. Enables the QPSK modulation scheme in the upstream direction from the Cisco uBR900 series to the CMTS. Allows voice traffic to be transmitted on the upstream via best effort rather than by assigning it a higher priority class of service.
Command
Description
Cisco uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
ip address docsis
no ip address docsis
Syntax Description
There are no key words or arguments for this command.
Defaults
The cable access router uses the DHCP protocol, as required by the DOCSIS specification, to assign an IP address to its cable interface during system power-on.
Command Modes
Global configuration
Command History
12.1(3)XL This command is introduced for the Cisco uBR905 cable access router. 12.1(4)T This command is introduced for the Cisco uBR924 cable access router and Cisco uBR914 cable DSU.
Release
Modification
Usage Guidelines
The ip address docsis command configures the cable access router so that it obtains its IP address from a DHCP server at system power-on, which is a requirement for DOCSIS operation. Using the no ip address docsis command prevents the cable access router from operating in DOCSIS networks and should be used only in lab or test networks.
If no ip address command is specified, the cable access router defaults to configuring its cable interface with the ip address docsis command. To change this behavior, this command must be saved to the startup configuration, or it should be included as part of a Cisco IOS configuration file that is downloaded to the cable access router.
![]() |
Note Earlier Cisco IOS software releases for the cable access routers used either the ip address negotiated and ip address dhcp commands to specify that the cable interface should obtain its IP address from a DHCP server. These commands should not be used on cable access routers except that the ip address negotiated command can be used for the serial interface on the Cisco uBR914 cable DSU. |
Examples
The following example configures the cable access router so that it obtains the IP address for its cable interface from a DHCP server:
ubr924(config)# ip address docsis ubr924(config)#
Related Commands
cable dhcp-proxy Specifies that DHCP should be used to assign an IP address to the Cisco uBR924 cable access router's Ethernet interface. ip http negotiated Specifies that a serial interface should use the PPP/IPCP (IP Control Protocol) to obtain an IP address at system power-on. (This command can be used only for the serial interface on the Cisco uBR914 cable DSU.) ip http dhcp Specifies the use of the DHCP protocol to obtain an IP address for any interface except the cable interface at system power-on.
Command
Description
Cisco uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
ip http cable-monitor {basic | advance} [URL-IP-address URL-mask]
no ip http cable-monitor
Syntax Description
basic Displays only the basic status and performance pages. advance Displays all status and diagnostic pages. URL-IP-address Specifies the IP address for the Cable Monitor. This parameter, along with the URL-mask parameter, also defines the network that provides the IP address pool used by the temporary DHCP server when the cable interface goes down. URL-mask Specifies the subnet mask for the Cable Monitor. This parameter, along with the URL-IP-address parameter, also defines the network that provides the IP address pool used by the temporary DHCP server when the cable interface goes down.

Note The Cable Monitor should not be used in advanced mode without first implementing a secure password strategy on the Cisco uBR924 cable access router. Enabling the Cable Monitor in advanced mode without setting an encrypted enabled password could provide information that would allow remote users to change the router's configuration.
Defaults
For URL-IP-address, 192.168.100.1
For URL-mask, 255.255.255.0
Command Modes
Global configuration
Command History
12.1(1)T This command is introduced for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Usage Guidelines
This command enables the Cable Monitor, an onboard web server that displays current status, troubleshooting, and performance information. The Cable Monitor can be accessed in two ways:
Enabling the Cable Monitor also enables the Cisco web server that is onboard the Cisco uBR924 cable access router (which is the equivalent to giving the ip http server command). However, when the Cable Monitor is enabled, all other access, including CLI access, to the onboard web server is automatically disabled.
Disabling the Cable Monitor using the no ip http cable-monitor command also automatically disables the Cisco web server (which is the equivalent of giving the no ip http server command).
The URL-IP-address and URL-mask parameters also specify that the class C private network 192.168.100.0 is the default address pool for the temporary DHCP server that activates when the cable interface goes down.
Examples
The following example enables the Cable Monitor for advanced mode, in which all status and diagnostic pages are displayed:
ubr924(config)# ip http cable-monitor advance ubr924(config)#
The following example disables both the Cable Monitor and the Cisco web server, preventing all web server access to the Cisco uBR924 cable access router:
ubr924(config)# no ip http cable-monitor ubr924(config)#
Related Commands
ip http port Configures the TCP port number for the router's HTTP web server (the default is the well-known web server port of 80). ip http server Enables and disables the router's HTTP web server.
Command
Description
![]() |
Note The ip http command also supports two options, access-class and authentication, that should not be used when the Cable Monitor is enabled. |
Cisco uBR904, uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
ping docsis{mac-addr | ip-addr}
Syntax Description
mac-addr MAC address. Specify the 48-bit hardware address of the cable modem. ip-addr IP address. Specify the IP address of the cable modem.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Examples
The following example confirms that the cable modem at 172.00.00.00 is connected to the network and is operational:
ping docsis 172.00.00.00 Queueing 5 MAC-layer station maintenance intervals, timeout is 25 msec: !!!!! Success rate is 100 percent (5/5)
Cisco uBR924 cable access router
port number
no port number
Syntax Description
For the Cisco uBR924 cable access router
:
number | Indicates the RJ-11 connectors installed in the Cisco uBR924. Valid entries are 0 (which corresponds to the RJ-11 connector labeled V1) and 1 (which corresponds to the RJ-11 connector labeled V2. |
Defaults
No port is configured.
Command Modes
Dial-peer configuration
Command History
12.0(4)T Support was added for the Cisco uBR924 cable access router.
Release
Modification
Usage Guidelines
This command is used for calls incoming from a telephony interface to select an incoming dial peer and for calls coming from the VoIP network to match a port with the selected outgoing dial peer.
This command applies only to POTS peers.
Examples
The following example associates a Cisco 3600 series router POTS dial peer 10 with voice port 1, which is located on subunit 0, and accessed through port 0:
dial-peer voice 10 pots port 1/0/0
The following example associates a Cisco MC3810 POTS dial peer 10 with voice port 0, which is located in slot 1:
dial-peer voice 10 pots port 1/0
The following example associates a Cisco AS5300 POTS dial peer 10 with voice port 0:D:
dial-peer voice 10 pots port 0:D
The following example associates a Cisco AS5800 POTS dial peer 10 with voice port 1/0/0:D (T1 card):
dial-peer voice 10 pots port 1/0/0:D
The following example associates a Cisco AS5800 POTS dial peer 10 with voice port 1/0/0:1:D (T3 card):
dial-peer voice 10 pots port 1/0/0:1:D
To display bridging information for a Cisco uBR900 series cable access router, enter the show bridge cable-modem command in privileged EXEC mode.
Cisco uBR904, uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
show bridge cable-modem number
Syntax Description
number The interface number of the cable interface on the rear panel of the Cisco uBR900 series.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Examples
The following example is sample output for this command:
uBR924#show bridge cable-modem 0Total of 300 station blocks, 298 freeCodes: P - permanent, S - selfBridge Group 59:
Table 29 describes the significant fields shown in the display.
| Field | Description |
|---|---|
Total of 300 station blocks | Total number of forwarding database elements in the system. The memory to hold bridge entries is allocated in blocks of memory sufficient to hold 300 individual entries. When the number of free entries falls below 25, another block of memory sufficient to hold another 300 entries is allocated. Thus, the total number of forwarding elements in the system is expanded dynamically, as needed, limited by the amount of free memory in the router. |
Bridge Group | The number of the bridge group to which this interface is assigned. |
Related Commands
show dhcp Displays the current DHCP settings on point-to-point interfaces. show interfaces cable-modem Displays information about the Cisco uBR900 series cable access router cable interface.
Command
Description
To display high-level controller information about a Cisco uBR900 series cable access router, use the show controllers cable-modem command in privileged EXEC mode.
Cisco uBR904, uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
show controllers cable-modem number
Syntax Description
number Controller number inside the Cisco uBR900 series.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Usage Guidelines
The show controllers cable-modem display begins with information from the first few registers of the Broadcom BCM3300 chip. Next is buffer information for the receive, receive MAC message, buffer descriptor, and packet descriptor rings. Then comes MIB statistics from the BCM3300 chip, DMA base registers to indicate where the rings start, global control and status information, and finally interrupts for the interrupt code.
When using this command, be sure to check the tx_count and the tx_head and tx_tail values for the buffer descriptor (TX BD) and packet descriptor (TX PD) rings. The tx_count should be greater than 0, and the tx_head and tx_tail values should not be equal. If these values do not change for a long period of time, it indicates there are packets stuck on the ring. This condition is often caused by the headend not giving grants.
Examples
Following is sample output for the show controllers cable-modem 0 command:
uBR924# show controllers cable-modem 0
BCM Cable interface 0:
BCM3300 unit 0, idb 0x200EB4, ds 0x82D4748, regaddr = 0x800000, reset_mask 0x80
station address 0010.7b43.aa01 default station address 0010.7b43.aa01
PLD VERSION: 32
MAC State is ranging_2_state, Prev States = 7
MAC mcfilter 01E02F00 data mcfilter 01000000
DS: BCM 3116 Receiver: Chip id = 2
US: BCM 3037 Transmitter: Chip id = 30B4
Tuner: status=0x00
Rx: tuner_freq 699000000, symbol_rate 5055849, local_freq 11520000
snr_estimate 33406, ber_estimate 0, lock_threshold 26000
QAM in lock, FEC in lock, qam_mode QAM_64
Tx: tx_freq 20000000, power_level 0x3E, symbol_rate 1280000
DHCP: TFTP server = 4.0.0.32, TOD server = 4.0.0.188
Security server = 0.0.0.0, Timezone Offset = 0.0.4.32
Config filename =
buffer size 1600
RX data PDU ring with 32 entries at 0x201D40
rx_head = 0x201D78 (7), rx_p = 0x831BE04 (7)
00 pak=0x8326318 buf=0x225626 status=0x80 pak_size=0
01 pak=0x83241A0 buf=0x21DE5A status=0x80 pak_size=0
02 pak=0x83239C0 buf=0x21C22A status=0x80 pak_size=0
03 pak=0x8328C70 buf=0x22EA22 status=0x80 pak_size=0
04 pak=0x8325F28 buf=0x22480E status=0x80 pak_size=0
05 pak=0x8327CB0 buf=0x22B1C2 status=0x80 pak_size=0
06 pak=0x8323BB8 buf=0x21C936 status=0x80 pak_size=0
RX MAC message ring with 8 entries at 0x201E80
rx_head_mac = 0x201E88 (1), rx_p_mac = 0x831BE80 (1)
00 pak=0x8326120 buf=0x224F1A status=0x80 pak_size=0
01 pak=0x8324590 buf=0x21EC72 status=0x80 pak_size=0
02 pak=0x8323FA8 buf=0x21D74E status=0x80 pak_size=0
03 pak=0x8326EE8 buf=0x22806E status=0x80 pak_size=0
04 pak=0x8328E68 buf=0x22F12E status=0x80 pak_size=0
05 pak=0x8327AB8 buf=0x22AAB6 status=0x80 pak_size=0
06 pak=0x8328880 buf=0x22DC0A status=0x80 pak_size=0
07 pak=0x8326CF0 buf=0x227962 status=0xA0 pak_size=0
TX BD ring with 8 entries at 0x201FB8, tx_count = 0
tx_head = 0x201FD8 (4), head_txp = 0x831BF20 (4)
tx_tail = 0x201FD8 (4), tail_txp = 0x831BF20 (4)
00 pak=0x000000 buf=0x200000 status=0x00 pak_size=0
01 pak=0x000000 buf=0x200000 status=0x00 pak_size=0
02 pak=0x000000 buf=0x200000 status=0x00 pak_size=0
03 pak=0x000000 buf=0x200000 status=0x00 pak_size=0
04 pak=0x000000 buf=0x200000 status=0x00 pak_size=0
05 pak=0x000000 buf=0x200000 status=0x00 pak_size=0
06 pak=0x000000 buf=0x200000 status=0x00 pak_size=0
07 pak=0x000000 buf=0x200000 status=0x20 pak_size=0
TX PD ring with 8 entries at 0x202038, tx_count = 0
tx_head_pd = 0x202838 (4)
tx_tail_pd = 0x202838 (4)
00 status=0x00 bd_index=0x0000 len=0x0000 hdr_len=0x0000
ehdr: 01 06 02 74 34 11
01 status=0x00 bd_index=0x0001 len=0x0000 hdr_len=0x0000
ehdr: 01 06 02 74 34 11
02 status=0x00 bd_index=0x0002 len=0x0000 hdr_len=0x0000
ehdr: 01 06 02 74 34 11
03 status=0x00 bd_index=0x0003 len=0x0000 hdr_len=0x0000
ehdr: 01 06 02 74 34 11
04 status=0x00 bd_index=0x0004 len=0x0000 hdr_len=0x0000
ehdr: 01 06 02 74 34 11
05 status=0x00 bd_index=0x0005 len=0x0000 hdr_len=0x0000
ehdr: 01 06 02 74 34 11
06 status=0x00 bd_index=0x0006 len=0x0000 hdr_len=0x0000
ehdr: 01 06 02 74 34 11
07 status=0x20 bd_index=0x0007 len=0x0000 hdr_len=0x0000
ehdr: 01 06 02 74 34 11
MIB Statistics
DS fifo full = 0, Rerequests = 0
DS mac msg overruns = 0, DS data overruns = 0
Qualified maps = 348, Qualified syncs = 73
CRC fails = 0, HDR chk fails = 0
Data pdus = 0, Mac msgs = 423
Valid hdrs = 423
BCM3300 Registers:
downstream dma:
ds_data_bd_base=0x001D40, ds_mac_bd_base=0x001E80
ds_data_dma_ctrl=0x98, ds_mac_dma_ctrl=0xD8
ds_dma_data_index=0x0007, ds_dma_msg_index=0x0000
upstream dma:
us_bd_base=0x001FB8, us_pd_base=0x002038
us_dma_ctrl=0x80, us_dma_tx_start=0x00
Global control and status:
global_ctrl_status=0x00
interrupts:
irq_pend=0x0008, irq_mask=0x00F7
Table 30 briefly describes some of the fields shown in the display. For more information, see the Broadcom documentation for the BCM3300 chip.
| Field | Description |
|---|---|
BCM3300 unit | The unit number of this BCM3300 chip. |
idb | Interface description block number. |
ds | Downstream channel. |
regaddr | Indicates the start of the BCM3300 registers. |
reset_mask | Indicates the bit to hit when resetting the chip. |
station address | MAC address of this Cisco uBR900 series cable access router interface. |
default station address | Default MAC address assigned by the factory for this Cisco uBR900 series cable access router. |
PLD VERSION | PLD version of the BCM3300 chip. |
MAC state | Current MAC state of the Cisco uBR900 series. |
Prev States | Number of states that have previously existed since initialization. |
MAC mcfilter | MAC control filter for MAC messages. |
data mcfilter | MAC control filter for data. |
DS | Downstream Broadcom receiver chip number and ID. |
US | Upstream Broadcom transmitter chip number and ID. |
Tuner: status | Current status of the tuner. |
Rx: tuner_freq | Downstream frequency (in Hz) that the Cisco uBR900 series searched for and found. |
symbol_rate | Downstream frequency in symbols per second. |
local_freq | Frequency on which the transmitter and the tuner communicate. |
snr_estimate | Estimate of signal-to-noise ratio (SNR) in Db X 1000. |
ber_estimate | Estimate of bit error rate (always 0). |
lock_threshold | Minimum signal-to-noise ratio (SNR) that the Cisco uBR900 series will accept as a valid lock. |
qam_mode | The modulation scheme used in the downstream direction. |
Tx: tx_freq | Upstream frequency sent to the Cisco uBR900 series by the CMTS in the UCD message. |
power_level | Transmit power level as set in the hardware, expressed as a hexadecimal value. The units are unique to the hardware used. Use the show controllers cable-modem 0 mac state command to see the power level in dBmV. |
symbol_rate | Upstream frequency in symbols per second. |
TFTP server | IP address of the TFTP server at the headend. |
TOD server | IP address of the time-of-day server at the headend. |
Security server | IP address of the security server at the headend. |
Timezone Offset | Correction received from the DHCP server to synchronize the Cisco uBR900 series time clock with the CMTS. |
Config filename | Name of the file stored on the cable company's TFTP server that contains operational parameters for the Cisco uBR900 series. |
buffer size | Size in bytes of the BCM3300 message buffers. |
RX data PDU ring: rx_p | Indicates the memory location of the beginning of buffer information for the receive data ring. Indicates current head buffer descriptor. Indicates current head packet descriptor. |
RX MAC message ring: rx_p_mac | Indicates the memory location of the beginning of buffer information for the receive MAC message ring. Indicates current head buffer descriptor. Indicates current head packet descriptor. |
TX BD ring: tx_head tx_tail tail_txp | Indicates the memory location of the beginning of buffer information for the transmit buffer descriptor ring. If tx_count is 0, or if tx_head and tx_tail are equal and there is no change for a period of time, it means there are packets stuck on the ring. This condition may be caused by the headend not giving grants. The next packet descriptor to get used, along with its index.
The next packet descriptor to get sent, along with its index. When head_txp and tail_txp are the same, the transmit queue is empty. |
TX PD ring: tx_tail_pd ehdr | Indicates the memory location of the beginning of buffer information for the transmit packet descriptor ring. Indicates current head packet descriptor. Indicates current tail packet descriptor. Extended MCNS header. |
MIB Statistics: |
|
DS fifo full | Number of times the downstream input first-in first-out (FIFO) buffer became full on the Cisco uBR900 series. |
rerequests | Number of times a bandwidth request generated by the Cisco uBR900 series was not responded to by the CMTS. |
DS mac msg overruns | Number of times the Cisco uBR900 series' DMA controller had a downstream MAC message and there were no free MAC message buffer descriptors to accept the message. |
DS data overruns | Number of times the Cisco uBR900 series' DMA controller had downstream data and there were no free data PDU buffer descriptors to accept the data. |
Qualified maps | Number of times a MAP message passed all filtering requirements and was received by the Cisco uBR900 series. |
Qualified syncs | Number of times a timestamp message was received by the Cisco uBR900 series. |
CRC fails | Number of times a MAC message failed a cyclic redundancy (CRC) check. |
HDR chk fails | Number of times a MAC header failed its 16-bit CRC check. The MAC header CRC is a 16-bit Header Check Sequence (HCS) field that ensures the integrity of the MAC header even in a collision environment. |
Data pdus | Total number of data PDUs (protocol data units) of all types received by the Cisco uBR900 series. |
Mac msgs | Number of MAC messages received by the Cisco uBR900 series. |
Valid hdrs | Number of valid headers received by the Cisco uBR900 series, including PDU headers, MAC headers, and headers only. |
Global control and status: | Used to reset the BCM3300 chip. |
interrupts: | Hexadecimal values of the pending IRQ interrupt and IRQ mask. |
Related Commands
Displays information about the baseline privacy key management exchange between the Cisco uBR900 series and the CMTS. Displays information about the Data Encryption Standard (DES) engine registers. Displays the registers in the MAC hardware that are used for filtering received frames. Displays the mini-slot lookup table inside a Cisco uBR900 series. Displays detailed MAC-layer information for a Cisco uBR900 series. Displays the contents of the registers used in the downstream physical hardware of the Cisco uBR900 series. Displays the settings for the upstream and downstream tuners used by a Cisco uBR900 series.
Command
Description
To display information about the baseline privacy key management exchange between the Cisco uBR900 series cable access router and the headend CMTS, use the show controllers cable-modem bpkm command in privileged EXEC mode.
Cisco uBR904, uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
show controllers cable-modem number bpkm
Syntax Description
number Controller number inside the Cisco uBR900 series cable access router.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Usage Guidelines
Baseline privacy key management exchanges take place only when both the Cisco uBR900 series and the CMTS are running code images that support baseline privacy, and the privacy class of service is enabled via the configuration file that is downloaded to the cable access router. Baseline privacy code images for the Cisco uBR900 series contain k1 in the code image name.
Examples
The following output is displayed when the headend CMTS does not have baseline privacy enabled:
uBR924# show controllers cable-modem 0 bpkm
CM Baseline Privacy Key Management
configuration (in seconds):
authorization wait time: 10
reauthorization wait time: 10
authorization grace time: 600
operational wait time: 1
rekey wait time: 1
tek grace time: 600
authorization rej wait time: 60
kek state: STATE_B_AUTH_WAIT
sid 4:
tek state: No resources assigned
Table 31 describes the fields shown in the display.
| Field | Description |
|---|---|
authorization wait time | The number of seconds the Cisco uBR900 series waits for a reply after sending the Authorization Request message to the CMTS. |
reauthorization wait time | The number of seconds the Cisco uBR900 series waits for a reply after it has sent an Authorization Request message to the CMTS in response to a reauthorization request or an Authorization Invalid message from the CMTS. |
authorization grace time | The number of seconds before the current authorization is set to expire that the grace timer begins, signaling the Cisco uBR900 series to begin the reauthorization process. |
operational wait time | The number of seconds the TEK state machine waits for a reply from the CMTS after sending its initial Key Request for its SID's keying material. |
rekey wait time | The number of seconds the TEK state machine waits for a replacement key for this SID after the TEK grace timer has expired and the request for a replacement key has been made. |
tek grace time | The number of seconds before the current TEK is set to expire that the TEK grace timer begins, signaling the TEK state machine to request a replacement key. |
authorization rej wait time | Number of seconds the Cisco uBR900 series waits before sending another Authorization Request message to the CMTS after it has received an Authorization Reject message. |
kek state | The current state of the key encryption key that the CMTS uses to encrypt the traffic encryption keys it sends to the Cisco uBR900 series. |
tek state | The current state of the traffic encryption key state machine for the specified SID. |
Related Commands
Displays high-level controller information about a Cisco uBR900 series cable access router. Displays information about the Data Encryption Standard (DES) engine registers. Displays the registers in the MAC hardware that are used for filtering received frames. Displays the mini-slot lookup table inside a Cisco uBR900 series. Displays detailed MAC-layer information for a Cisco uBR900 series. Displays the contents of the registers used in the downstream physical hardware of the Cisco uBR900 series. Displays the settings for the upstream and downstream tuners used by a Cisco uBR900 series.
Command
Description
To display information about the Data Encryption Standard (DES) engine registers, use the show controllers cable-modem des command in privileged EXEC mode.
Cisco uBR904, uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
show controllers cable-modem number des
Syntax Description
number Controller number inside the Cisco uBR900 series.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Examples
DES engine registers are displayed in the following example:
uBR924#show controllers cable-modem 0 desdownstream des:ds_des_key_table:key 0: even 0, odd 0key 1: even 0, odd 0key 2: even 0, odd 0key 3: even 0, odd 0ds_des_cbc_iv_table:iv 0: even 0, odd 0iv 1: even 0, odd 0iv 2: even 0, odd 0iv 3: even 0, odd 0ds_des_sid_table:sid_1=0x0000, sid_2=0x0000, sid_3=0x0000, sid_4=0x0000ds_des_sid_enable=0x80, ds_des_ctrl=0x2Eds_des_sv=0x0F00ds_unencrypted_length=0x0Cupstream des:us_des_key_table:key 0: even 0, odd 0key 1: even 0, odd 0key 2: even 0, odd 0key 3: even 0, odd 0us_des_cbc_iv_table:iv 0: even 0, odd 0iv 1: even 0, odd 0iv 2: even 0, odd 0iv 3: even 0, odd 0pb_req_bytes_to_minislots=0x10us_des_ctrl=0x00, us_des_sid_1= 0x1234ds_unencrypted_length=0x0C
Table 32 briefly describes some of the fields shown in the display. For more information, see the Broadcom documentation for the BCM3300 chip.
| Field | Description |
|---|---|
ds_des_key_table | Table showing downstream DES keys. |
ds_des_cbc_iv_table | Table of downstream DES Cipher Block Chaining mode information. |
ds_des_sid_table | Table showing the SID values to be enabled for DES encryption. |
ds_des_sid_enable | Controls which SID entries in the SID table are enabled for encryption. In the above example, none of the entries are enabled for encryption. |
ds_des_ctrl | Control register that controls the operating mode of the downstream DES engine. |
ds_des_sv | DES security version register; the range of the version field in the Baseline Privacy Interface (BPI) extended headers that will be accepted by the hardware. High byte is upper limit, low byte is lower limit. The Cisco uBR900 will accept versions 0 to 15. |
ds_unencrypted_length | Specifies the number of bytes that will be unencrypted at the beginning of the MAC frame. 0x0C means the first 12 bytes are not encrypted, which is what the DOCSIS Baseline Privacy specification calls for. |
us_des_key_table | Table showing upstream DES keys. |
us_des_cbc_iv_table | Table of upstream DES Cipher Block Chaining mode information. |
us_des_ctrl | Control register that controls the operating mode of the upstream DES engine. The value 0x24 means that the upstream is configured to enable decryption and to use CBC mode. |
Related Commands
Displays high-level controller information about a Cisco uBR900 series cable access router. Displays information about the baseline privacy key management exchange between the Cisco uBR900 series and the CMTS. Displays the registers in the MAC hardware that are used for filtering received frames. Displays the mini-slot lookup table inside a Cisco uBR900. Displays detailed MAC-layer information for a Cisco uBR900. Displays the contents of the registers used in the downstream physical hardware of the Cisco uBR900 series. Displays the settings for the upstream and downstream tuners used by a Cisco uBR900 series.
Command
Description
To display the registers in the MAC hardware that are used for filtering received frames, use the show controllers cable-modem filters command in privileged EXEC mode.
Cisco uBR904, uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
show controllers cable-modem number filters
Syntax Description
number Controller number inside the Cisco uBR900 series.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Usage Guidelines
Some of the filtering parameters are MAC hardware addresses, Service IDs (SIDs), and upstream channel IDs.
Examples
MAC and SID filter information is displayed in the following example:
uBR924#show controllers cable-modem 0 filtersdownstream mac message processing:ds_mac_da_filters:filter_1=0010.7b43.aa01, filter_2=0000.0000.0000filter_3=0000.0000.0000, filter_4=0000.0000.0000ds_mac_da_filter_ctrl=0x71, ds_mac_msg_sof=0x0000ds_mac_da_mc=01E02F00map_parser_sids:sid_1=0x0000, sid_2=0x0000, sid_3=0x0000, sid_4=0x0000ds_mac_filter_ctrl=0x00, us_channel_id=0x0000ds_pid=0x0000, mac_msg_proto_ver=FF 00reg_rang_req_sid=0x0000downstream data processing:ds_data_da_filter_table:filter_1 0010.7b43.aa01, filter_2 0000.0000.0000filter_3 0000.0000.0000, filter_4 0000.0000.0000ds_data_da_filter_ctrl=0x61, ds_pdu_sof=0xDEADds_data_da_mc=01000000upstream processing:us_ctrl_status=0x04, Minislots per request=0x01burst_maps:map[0]=0 map[1]=0 map[2]=0 map[3]=0bytes_per_minislot_exp=0x04us_map_parser_minislot_adv=0x03, ticks_per_minislot=0x08, maint_xmit=0x0001us_sid_table:sid_1=0x0000, sid_2=0x0000, sid_3=0x0000, sid_4=0x0000max_re_req=0x0010, rang_fifo=0x00
Table 33 briefly describes some of the fields shown in the display. For more information, see the Broadcom documentation for the BCM3300 chip.
| Field | Description |
|---|---|
ds_mac_da_filters | Shows the MAC address of the cable interface and the MAC address of any Ethernet MAC it is bridging. |
ds_mac_da_filter_ctrl | Downstream MAC filter control for data. |
ds_mac_msg_sof | Downstream MAC message start of frame. |
ds_mac_da_mc | Downstream MAC control filter for data. |
map_parser_sids | Service IDs used for upstream bandwidth allocation. |
ds_mac_filter_ctrl | Downstream MAC filter control for MAC messages. |
us_channel_id | Upstream channel ID. |
ds_pid | Downstream packet ID |
mac_msg_proto_ver | Version of the MAC management protocol in use. |
reg_rang_req_sid | Service ID (SID) field of the ranging request message. |
ds_data_da_filter_table | Downstream data processing filter table. |
ds_data_da_filter_ctrl | Downstream data processing filter control. |
ds_pdu_sof | Downstream PDU start of frame. |
ds_data_da_mc | Downstream data processing MAC control. |
us_ctrl_status | Upstream control status. |
Minislots per request | Length of each registration request in mini-slots. |
burst_maps | Maps the burst profiles saved in the BCM3037 registers to interval usage codes (IUCs). |
bytes_per_minislot_exp | Number of bytes per expansion mini-slot. |
ticks_per_minislot | Number of time ticks (6.25-microsecond intervals) in each upstream mini-slot. |
maint_xmit | Number of initial maintenance transmit opportunities. |
us_sid_table | Upstream service ID table. |
max_re_req | Maximum number of registration re-requests allowed. |
rang_fifo | Number of ranging requests that can be held in the first-in-first-out (FIFO) buffer. |
Related Commands
Displays high-level controller information about a Cisco uBR900 series cable access router. Displays information about the baseline privacy key management exchange between the Cisco uBR900 series and the CMTS. Displays information about the Data Encryption Standard (DES) engine registers. Displays the mini-slot lookup table inside a Cisco uBR900. Displays detailed MAC-layer information for a Cisco uBR900. Displays the contents of the registers used in the downstream physical hardware of the Cisco uBR900. Displays the settings for the upstream and downstream tuners used by a Cisco uBR900.
Command
Description
To display the mini-slot lookup table inside a Cisco uBR900 series, use the show controllers cable-modem lookup-table command in privileged EXEC mode.
Cisco uBR904, uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
show controllers cable-modem number lookup-table
Syntax Description
number Controller number inside the Cisco uBR900 series.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Usage Guidelines
This command displays the details of the lookup table. The driver uses this table to convert the size of the packets that the Cisco uBR900 series wants to transmit into a bandwidth request to the CMTS in mini-slots. The contents of this table are affected by the upstream symbol rate that is negotiated between the CMTS and the cable access router.
Use this table to look up the packet size and determine how many mini-slots will be needed.
Examples
The mini-slot lookup table is displayed in the following example:
uBR924# show controllers cable-modem 0 lookup-table
Max Burst Size (minislots) = 0x6
Max Burst Length (bytes) = 0x4B
PHY Overhead Lookup Table:
000: 01 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06
010: 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06
020: 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06
030: 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06
040: 06 06 06 06 06 06 06 06 06 06 06 06 10 10 10 10
050: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
060: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
070: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
080: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
090: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
0A0: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
0B0: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
0C0: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
0D0: 10 10 10 10 10 10 10 10 10 10 10 10 10 1F 1F 1F
0E0: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
0F0: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
100: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
110: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
120: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
130: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
140: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
150: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
160: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
170: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
180: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
190: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
1A0: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
1B0: 1F 1F 1F 1F 1F 1F 1F 1F 1F 2D 2D 2D 2D 2D 2D 2D
1C0: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
1D0: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
1E0: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
1F0: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
200: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
210: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
220: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
230: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
240: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
250: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
260: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
270: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
280: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
290: 2D 2D 2D 2D 2D 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
2A0: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
2B0: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
2C0: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
2D0: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
2E0: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
2F0: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
300: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
310: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
320: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
330: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
340: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
350: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
360: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
370: 3C 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
380: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
390: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
3A0: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
3B0: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
3C0: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
3D0: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
3E0: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
3F0: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
400: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
410: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
420: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
430: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
440: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 5A 5A 5A
450: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
460: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
470: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
480: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
490: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
4A0: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
4B0: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
4C0: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
4D0: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
4E0: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
4F0: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
500: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
510: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
520: 5A 5A 5A 5A 5A 5A 5A 5A 5A 68 68 68 68 68 68 68
530: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
540: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
550: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
560: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
570: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
580: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
590: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
5A0: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
5B0: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
5C0: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
5D0: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
5E0: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
5F0: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
600: 68 68 68 68 68 77 77 77 77 77 77 77 77 77 77 77
610: 77 77 77 77 77 77 77 77 77 77 77 77 77 77 77 77
620: 77 77 77 77 77 77 77 77 77 77 77 77 77 77 77 77
630: 77 77 77 77 77 77 77 77 77 77 77 77 77 77 77 77
PHY Reverse Lookup Table:
00: 0000 0000 0000 0000 0000 0000 004B 0000
08: 0000 0000 0000 0000 0000 0000 0000 0000
10: 00DC 00DC 00DC 00DC 00DC 00DC 00DC 00DC
18: 00DC 00DC 00DC 00DC 00DC 00DC 00DC 01B8
20: 01B8 01B8 01B8 01B8 01B8 01B8 01B8 01B8
28: 01B8 01B8 01B8 01B8 01B8 0294 0294 0294
30: 0294 0294 0294 0294 0294 0294 0294 0294
38: 0294 0294 0294 0294 0370 0370 0370 0370
40: 0370 0370 0370 0370 0370 0370 0370 0370
48: 0370 0370 0370 044C 044C 044C 044C 044C
50: 044C 044C 044C 044C 044C 044C 044C 044C
58: 044C 044C 0528 0528 0528 0528 0528 0528
60: 0528 0528 0528 0528 0528 0528 0528 0528
68: 0604 0604 0604 0604 0604 0604 0604 0604
70: 0604 0604 0604 0604 0604 0604 0604 06E0
78: 06E0 06E0 06E0 06E0 06E0 06E0 06E0 06E0
80: 06E0 06E0 06E0 06E0 06E0 06E0 07BC 07BC
88: 07BC 07BC 07BC 07BC 07BC 07BC 07BC 07BC
90: 07BC 07BC 07BC 07BC 07BC 0898 0898 0898
98: 0898 0898 0898 0898 0898 0898 0898 0898
A0: 0898 0898 0898 0974 0974 0974 0974 0974
A8: 0974 0974 0974 0974 0974 0974 0974 0974
B0: 0974 0974 0A50 0A50 0A50 0A50 0A50 0A50
B8: 0A50 0A50 0A50 0A50 0A50 0A50 0A50 0A50
C0: 0A50 0B2C 0B2C 0B2C 0B2C 0B2C 0B2C 0B2C
C8: 0B2C 0B2C 0B2C 0B2C 0B2C 0B2C 0B2C 0B2C
D0: 0C08 0C08 0C08 0C08 0C08 0C08 0C08 0C08
D8: 0C08 0C08 0C08 0C08 0C08 0C08 0CE4 0CE4
E0: 0CE4 0CE4 0CE4 0CE4 0CE4 0CE4 0CE4 0CE4
E8: 0CE4 0CE4 0CE4 0CE4 0CE4 0DC0 0DC0 0DC0
F0: 0DC0 0DC0 0DC0 0DC0 0DC0 0DC0 0DC0 0DC0
F8: 0DC0 0DC0 0DC0 0DC0 0E9C 0E9C 0E9C 0E9C
Related Commands
Displays high-level controller information about a Cisco BR900 series cable access router. Displays information about the baseline privacy key management exchange between the Cisco uBR900 series and the CMTS. Displays information about the Data Encryption Standard (DES) engine registers. .Displays the registers in the MAC hardware that are used for filtering received frames. Displays detailed MAC-layer information for a Cisco uBR900. Displays the contents of the registers used in the downstream physical hardware of the Cisco uBR900. Displays the settings for the upstream and downstream tuners used by a Cisco uBR900.
Command
Description
To display detailed MAC-layer information for a Cisco uBR900 series, use the show controllers cable-modem mac command in privileged EXEC mode.
Cisco uBR904, uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
show controllers cable-modem number mac [errors | hardware | log | resets | state]
Syntax Description
number Controller number inside the Cisco uBR900 series. errors (Optional) Displays a log of the error events that are reported to SNMP. This keyword enables you to look at the error events without accessing a MIB. hardware (Optional) Displays all MAC hardware registers. log (Optional) Displays a history of MAC log messages, up to 1023 entries. This is the same output that is displayed when using the debug cable-modem mac log command. resets (Optional) Extracts all of the reset causes out of the MAC log file and summarizes them in a mini report. state (Optional) Displays a summary of the MAC state.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Usage Guidelines
MAC log messages are written to a circular log file even when debugging is not turned on. These messages include timestamps, events, and information pertinent to these events. Use the show controllers cable-modem mac log command to view MAC log messages.
If the Cisco uBR900 series interface fails to come up or resets periodically, the MAC log will capture what happened. For example, if an address is not obtained from the DHCP server, an error is logged, initialization starts over, and the Cisco uBR900 series scans for a downstream frequency.
The most useful keywords for troubleshooting a Cisco uBR900 series are log, errors, and resets. See Examples 1 through 3.
Examples
The following sample display shows the MAC log file for a cable-modem interface that has successfully registered with the CMTS:
uBR924# show controllers cable-modem 0 mac log 00:14:24: 864.124 CMAC_LOG_DRIVER_INIT_IDB_RESET 0x080B7430 00:14:24: 864.128 CMAC_LOG_LINK_DOWN 00:14:24: 864.132 CMAC_LOG_RESET_FROM_DRIVER 00:14:24: 864.134 CMAC_LOG_STATE_CHANGE wait_for_link_up_state 00:14:24: 864.138 CMAC_LOG_LINK_UP 00:14:24: 864.142 CMAC_LOG_STATE_CHANGE ds_channel_scanning_state 00:14:24: 864.270 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 81/453000000/855000000/6000000 00:14:24: 864.276 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 82/93000000/105000000/6000000 00:14:24: 864.280 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 83/111025000/117025000/6000000 00:14:24: 864.286 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 84/231012500/327012500/6000000 00:14:24: 864.290 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 85/333025000/333025000/6000000 00:14:24: 864.294 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 86/339012500/399012500/6000000 00:14:24: 864.300 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 87/405000000/447000000/6000000 00:14:24: 864.304 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 88/123012500/129012500/6000000 00:14:24: 864.310 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 89/135012500/135012500/6000000 00:14:24: 864.314 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 90/141000000/171000000/6000000 00:14:24: 864.320 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 91/219000000/225000000/6000000 00:14:24: 864.324 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 92/177000000/213000000/6000000 00:14:24: 864.330 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 93/55752700/67753300/6000300 00:14:24: 864.334 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 94/79753900/85754200/6000300 00:14:24: 864.340 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 95/175758700/211760500/6000300 00:14:24: 864.344 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 96/121756000/169758400/6000300 00:14:24: 864.348 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 97/217760800/397769800/6000300 00:14:24: 864.354 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 98/73753600/115755700/6000300 00:14:24: 864.358 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 99/403770100/997799800/6000300 00:14:24: 864.364 CMAC_LOG_WILL_SEARCH_SAVED_DS_FREQUENCY 213000000 00:14:25: 865.450 CMAC_LOG_UCD_MSG_RCVD 1 00:14:25: %LINK-3-UPDOWN: Interface cable-modem0, changed state to up 00:14:26: 866.200 CMAC_LOG_DS_64QAM_LOCK_ACQUIRED 213000000 00:14:26: 866.204 CMAC_LOG_DS_CHANNEL_SCAN_COMPLETED 00:14:26: 866.206 CMAC_LOG_STATE_CHANGE wait_ucd_state 00:14:26: %LINEPROTO-5-UPDOWN: Line protocol on Interface cable-modem0, changed state to down 00:14:27: 867.456 CMAC_LOG_UCD_MSG_RCVD 1 00:14:29: 869.470 CMAC_LOG_UCD_MSG_RCVD 1 00:14:29: 869.472 CMAC_LOG_ALL_UCDS_FOUND 00:14:29: 869.476 CMAC_LOG_STATE_CHANGE wait_map_state 00:14:29: 869.480 CMAC_LOG_UCD_NEW_US_FREQUENCY 20000000 00:14:29: 869.484 CMAC_LOG_SLOT_SIZE_CHANGED 8 00:14:29: 869.564 CMAC_LOG_FOUND_US_CHANNEL 1 00:14:31: 871.484 CMAC_LOG_UCD_MSG_RCVD 1 00:14:31: 871.692 CMAC_LOG_MAP_MSG_RCVD 00:14:31: 871.694 CMAC_LOG_INITIAL_RANGING_MINISLOTS 40 00:14:31: 871.696 CMAC_LOG_STATE_CHANGE ranging_1_state 00:14:31: 871.700 CMAC_LOG_RANGING_OFFSET_SET_TO 9610 00:14:31: 871.704 CMAC_LOG_POWER_LEVEL_IS 32.0 dBmV (commanded) 00:14:31: 871.708 CMAC_LOG_STARTING_RANGING 00:14:31: 871.710 CMAC_LOG_RANGING_BACKOFF_SET 0 00:14:31: 871.714 CMAC_LOG_RNG_REQ_QUEUED 0 00:14:32: 872.208 CMAC_LOG_RNG_REQ_TRANSMITTED 00:14:32: 872.216 CMAC_LOG_RNG_RSP_MSG_RCVD 00:14:32: 872.218 CMAC_LOG_RNG_RSP_SID_ASSIGNED 16 00:14:32: 872.222 CMAC_LOG_ADJUST_RANGING_OFFSET 2853 00:14:32: 872.224 CMAC_LOG_RANGING_OFFSET_SET_TO 12463 00:14:32: 872.228 CMAC_LOG_ADJUST_TX_POWER 8 00:14:32: 872.230 CMAC_LOG_POWER_LEVEL_IS 34.0 dBmV (commanded) 00:14:32: 872.234 CMAC_LOG_STATE_CHANGE ranging_2_state 00:14:32: 872.238 CMAC_LOG_RNG_REQ_QUEUED 16 00:14:32: 872.848 CMAC_LOG_RNG_REQ_TRANSMITTED 00:14:32: 872.852 CMAC_LOG_RNG_RSP_MSG_RCVD 00:14:32: 872.856 CMAC_LOG_RANGING_SUCCESS 00:14:32: 872.874 CMAC_LOG_STATE_CHANGE dhcp_state 00:14:33: 873.386 CMAC_LOG_DHCP_ASSIGNED_IP_ADDRESS 188.188.1.62 00:14:33: 873.388 CMAC_LOG_DHCP_TFTP_SERVER_ADDRESS 4.0.0.32 00:14:33: 873.392 CMAC_LOG_DHCP_TOD_SERVER_ADDRESS 4.0.0.32 00:14:33: 873.396 CMAC_LOG_DHCP_SET_GATEWAY_ADDRESS 00:14:33: 873.398 CMAC_LOG_DHCP_TZ_OFFSET 60 00:14:33: 873.402 CMAC_LOG_DHCP_CONFIG_FILE_NAME platinum.cm 00:14:33: 873.406 CMAC_LOG_DHCP_ERROR_ACQUIRING_SEC_SVR_ADDR 00:14:33: 873.410 CMAC_LOG_DHCP_COMPLETE 00:14:33: 873.536 CMAC_LOG_STATE_CHANGE establish_tod_state 00:14:33: 873.546 CMAC_LOG_TOD_REQUEST_SENT 00:14:33: 873.572 CMAC_LOG_TOD_REPLY_RECEIVED 3140961992 00:14:33: 873.578 CMAC_LOG_TOD_COMPLETE 00:14:33: 873.582 CMAC_LOG_STATE_CHANGE security_association_state 00:14:33: 873.584 CMAC_LOG_SECURITY_BYPASSED 00:14:33: 873.588 CMAC_LOG_STATE_CHANGE configuration_file_state 00:14:33: 873.592 CMAC_LOG_LOADING_CONFIG_FILE platinum.cm 00:14:34: %LINEPROTO-5-UPDOWN: Line protocol on Interface cable-modem0, changed state to up 00:14:34: 874.728 CMAC_LOG_CONFIG_FILE_PROCESS_COMPLETE 00:14:34: 874.730 CMAC_LOG_STATE_CHANGE registration_state 00:14:34: 874.734 CMAC_LOG_REG_REQ_MSG_QUEUED 00:14:34: 874.744 CMAC_LOG_REG_REQ_TRANSMITTED 00:14:34: 874.754 CMAC_LOG_REG_RSP_MSG_RCVD 00:14:34: 874.756 CMAC_LOG_COS_ASSIGNED_SID 1/16 00:14:34: 874.760 CMAC_LOG_RNG_REQ_QUEUED 16 00:14:34: 874.768 CMAC_LOG_REGISTRATION_OK 00 :14:34: 874.770 CMAC_LOG_REG_RSP_ACK_MSG_QUEUED 0 00:14:34: 874.774 CMAC_LOG_STATE_CHANGE establish_privacy_state 00:14:34: 874.778 CMAC_LOG_PRIVACY_NOT_CONFIGURED 00:14:34: 874.780 CMAC_LOG_STATE_CHANGE maintenance_state 00:14:34: 874.784 CMAC_LOG_REG_RSP_ACK_MESSAGE_EVENT 00:14:34: 874.788 CMAC_LOG_REG_RSP_ACK_MSG_SENT If the DHCP server cannot not be reached, the error will look like this in the MAC log: 00:14:32: 872.874 CMAC_LOG_STATE_CHANGE dhcp_state 00:14:33: 873.386 CMAC_LOG_RNG_REQ_TRANSMITTED 00:14:33: 873.388 CMAC_LOG_RNG_RSP_MSG_RCVD 00:14:33: 873.386 CMAC_LOG_RNG_REQ_TRANSMITTED 00:14:33: 873.392 CMAC_LOG_RNG_RSP_MSG_RCVD 00:14:33: 873.396 CMAC_LOG_WATCHDOG_TIMER 00:14:33: 873.398 CMAC_LOG_RESET_DHCP_WATCHDOG_EXPIRED 00:14:33: 873.402 CMAC_LOG_STATE_CHANGE reset_interface_state 00:14:33: 873.406 CMAC_LOG_DHCP_PROCESS_KILLED
The following MAC error log information is displayed in the following example, which is also reported via SNMP:
uBR924# 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 Cisco uBR900 series 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. The Cisco uBR900 series 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.
If the DHCP server could not be reached, the error would look like this in the MAC error display:
uBR924# 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.
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; however, the reset messages 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.
uBR924# 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, or that it took too long to respond.
uBR924# 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.
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
| Message | 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 uBR900 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 uBR900 series 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.
| ||
| Initial ranging opportunities are not being received. | ||
| The CMTS failed too many times to respond to a RNG-REQ message.
| ||
| The CMTS commanded the Cisco uBR900 series to abort the ranging process. | ||
| The Cisco uBR900 series has run out of memory. | ||
| The Cisco uBR900 series 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 Cisco uBR900 series failed authentication as indicated in a REG-RSP message from the CMTS. | ||
| The CMTS has failed the Cisco uBR900 series' registration because a required or requested class of service is not available. | ||
| The CMTS failed too many times to respond to a REG-REQ message. | ||
| The Cisco uBR900 series MAC layer failed to detect a change in the interface driver. | ||
| The Network Access parameter is missing from the DOCSIS configuration file. | ||
| The Cisco uBR900 series was unable to set the Write Access Control for an SNMP parameter as specified by the DOCSIS configuration file. | ||
| The DHCP server did not respond with all the required values. The required values are: IP address, network mask, TFTP server IP address, TOD server IP address, DOCSIS configuration file name, and time zone offset. | ||
| The Cisco uBR900 series was unable to start the internal process used to manage the downstream tuner. | ||
| Downstream QAM/FEC lock has been lost too many times. | ||
| The Cisco uBR900 series MAC-layer process was unable to communicate with the downstream tuner management process. | ||
| The downstream tuner process failed to report its continuing operation for a long period of time. | ||
| The Cisco uBR900 series was unable to set an SNMP parameter as specified by the DOCSIS configuration file. | ||
| The internal MIB object took too long to process the entries in the DOCSIS configuration file. |
The following example display for the show controllers cable-modem 0 mac hardware command shows the detailed configuration of the interface driver and the MAC-layer hardware. The most interesting bit is the station address (hardware address). The MIB statistics reflect the MAC hardware counters for various events, but these counters are typically reset every few seconds, so their contents are not accurate in this display.
uBR924# show controllers cable-modem 0 mac hardware
PLD VERSION: 32
BCM3300 unit 0, idb 0x200EB4, ds 0x82D4748, regaddr = 0x800000, reset_mask
0x80
station address 0010.7b43.aa01 default station address 0010.7b43.aa01
MAC mcfilter 01E02F00 data mcfilter 01000000
buffer size 1600
RX data PDU ring with 32 entries at 0x201D40
rx_head = 0x201D40 (0), rx_p = 0x82D4760 (0)
00 pak=0x82DF844 buf=0x227F1A status=0x80 pak_size=0
01 pak=0x82E0BF4 buf=0x22C56A status=0x80 pak_size=0
02 pak=0x82DF454 buf=0x22710A status=0x80 pak_size=0
03 pak=0x82DF64C buf=0x227812 status=0x80 pak_size=0
04 pak=0x82E0024 buf=0x229B3A status=0x80 pak_size=0
05 pak=0x82DBF2C buf=0x21B332 status=0x80 pak_size=0
06 pak=0x82DFE2C buf=0x229432 status=0x80 pak_size=0
07 pak=0x82E0FE4 buf=0x22D37A status=0x80 pak_size=0
08 pak=0x82DF064 buf=0x2262FA status=0x80 pak_size=0
09 pak=0x82DEC74 buf=0x2254EA status=0x80 pak_size=0
10 pak=0x82DEA7C buf=0x224DE2 status=0x80 pak_size=0
11 pak=0x82DE884 buf=0x2246DA status=0x80 pak_size=0
12 pak=0x82DE68C buf=0x223FD2 status=0x80 pak_size=0
13 pak=0x82DE494 buf=0x2238CA status=0x80 pak_size=0
14 pak=0x82DE29C buf=0x2231C2 status=0x80 pak_size=0
15 pak=0x82DE0A4 buf=0x222ABA status=0x80 pak_size=0
16 pak=0x82DDEAC buf=0x2223B2 status=0x80 pak_size=0
17 pak=0x82DDCB4 buf=0x221CAA status=0x80 pak_size=0
18 pak=0x82DDABC buf=0x2215A2 status=0x80 pak_size=0
19 pak=0x82DD8C4 buf=0x220E9A status=0x80 pak_size=0
20 pak=0x82DD6CC buf=0x220792 status=0x80 pak_size=0
21 pak=0x82DD4D4 buf=0x22008A status=0x80 pak_size=0
22 pak=0x82DD2DC buf=0x21F982 status=0x80 pak_size=0
23 pak=0x82DD0E4 buf=0x21F27A status=0x80 pak_size=0
24 pak=0x82DCEEC buf=0x21EB72 status=0x80 pak_size=0
25 pak=0x82DCCF4 buf=0x21E46A status=0x80 pak_size=0
26 pak=0x82DCAFC buf=0x21DD62 status=0x80 pak_size=0
27 pak=0x82DC904 buf=0x21D65A status=0x80 pak_size=0
28 pak=0x82DC70C buf=0x21CF52 status=0x80 pak_size=0
29 pak=0x82DC514 buf=0x21C84A status=0x80 pak_size=0
30 pak=0x82DC31C buf=0x21C142 status=0x80 pak_size=0
31 pak=0x82DC124 buf=0x21BA3A status=0xA0 pak_size=0
RX MAC message ring with 8 entries at 0x201E80
rx_head_mac = 0x201EB0 (6), rx_p_mac = 0x82D480C (6)
00 pak=0x82E0DEC buf=0x22CC72 status=0x80 pak_size=0
01 pak=0x82E021C buf=0x22A242 status=0x80 pak_size=0
02 pak=0x82E060C buf=0x22B052 status=0x80 pak_size=0
03 pak=0x82E11DC buf=0x22DA82 status=0x80 pak_size=0
04 pak=0x82DFC34 buf=0x228D2A status=0x80 pak_size=0
05 pak=0x82E09FC buf=0x22BE62 status=0x80 pak_size=0
06 pak=0x82DEE6C buf=0x225BF2 status=0x80 pak_size=0
07 pak=0x82DFA3C buf=0x228622 status=0xA0 pak_size=0
TX BD ring with 8 entries at 0x201FB8, tx_count = 0
tx_head = 0x201FB8 (0), head_txp = 0x82D4888 (0)
tx_tail = 0x201FB8 (0), tail_txp = 0x82D4888 (0)
00 pak=0x000000 buf=0x200000 status=0x00 pak_size=0
01 pak=0x000000 buf=0x200000 status=0x00 pak_size=0
02 pak=0x000000 buf=0x200000 status=0x00 pak_size=0
03 pak=0x000000 buf=0x200000 status=0x00 pak_size=0
04 pak=0x000000 buf=0x200000 status=0x00 pak_size=0
05 pak=0x000000 buf=0x200000 status=0x00 pak_size=0
06 pak=0x000000 buf=0x200000 status=0x00 pak_size=0
07 pak=0x000000 buf=0x200000 status=0x20 pak_size=0
TX PD ring with 8 entries at 0x202038, tx_count = 0
tx_head_pd = 0x202038 (0)
tx_tail_pd = 0x202038 (0)
00 status=0x00 bd_index=0x0000 len=0x0000 hdr_len=0x0000
ehdr: 00 00 00 2E FF FF
01 status=0x00 bd_index=0x0001 len=0x0000 hdr_len=0x0000
ehdr: 00 00 00 2E FF FF
02 status=0x00 bd_index=0x0002 len=0x0000 hdr_len=0x0000
ehdr: 00 00 00 2E FF FF
03 status=0x00 bd_index=0x0003 len=0x0000 hdr_len=0x0000
ehdr: 00 00 00 2E FF FF
04 status=0x00 bd_index=0x0004 len=0x0000 hdr_len=0x0000
ehdr: 00 00 00 2E 00 00
05 status=0x00 bd_index=0x0005 len=0x0000 hdr_len=0x0000
ehdr: 00 00 00 2E 00 00
06 status=0x00 bd_index=0x0006 len=0x0000 hdr_len=0x0000
ehdr: 00 00 00 00 00 00
07 status=0x20 bd_index=0x0007 len=0x0000 hdr_len=0x0000
ehdr: 00 00 00 00 00 00
MIB Statistics
DS fifo full = 0, Rerequests = 0
DS mac msg overruns = 0, DS data overruns = 0
Qualified maps = 0, Qualified syncs = 0
CRC fails = 0, HDR chk fails = 0
Data pdus = 0, Mac msgs = 0
Valid hdrs = 0
BCM3300 Registers:
downstream dma:
ds_data_bd_base=0x001D40, ds_mac_bd_base=0x001E80
ds_data_dma_ctrl=0x98, ds_mac_dma_ctrl=0x98
ds_dma_data_index=0x0000, ds_dma_msg_index=0x0000
upstream dma:
us_bd_base=0x001FB8, us_pd_base=0x002038
us_dma_ctrl=0x00, us_dma_tx_start=0x00
global control and status:
global_ctrl_status=0x00
interrupts:
irq_pend=0x0018, irq_mask=0x00E7
timing recovery circuit:
loop_enable=0x00, minislot_divisor=0x00
K0_ctrl=0x06, K1_ctrl=0x07, acq_threshhold=0x01
err_threshhold=0x04, timeout_threshold=0xFF
nco_bias=0x4F7004F7, ranging_offset=0x00000000
ts_err=0x00, sync_valid=0x00, delta_F=0x00
timeout_err=0x00
spi:
dynamic_ctrl=0x09, static_ctr=0x9F, autonomous=0x01
irq_ack=0x00, spi_cmd=0x51, spi_addr=0x11
spi_data= FF/00/00/00/00/00/00
burst profiles:
profile 0:
01 19 1D 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
profile 1:
01 19 1D 03 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
profile 2:
01 19 1D 04 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
profile 3:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Most of the fields in this display are described in Table 47; Table 35 describes the MIB statistics shown in the display.
| Field | Description |
|---|---|
DS fifo full | Number of times the downstream receive buffer on the Cisco uBR900 series has become full. |
Rerequests | Number of registration requests sent by the Cisco uBR900 series to the CMTS. |
DS mac msg overruns | Number of times the DMA controller has had a downstream MAC message and there were no free MAC message buffer descriptors to accept the message. |
DS data overruns | Number of times the DMA controller has had downstream data and there were no free data PDU buffer descriptors to accept the data. |
Qualified maps | Number of valid MAP messages received by the Cisco uBR900 series. |
Qualified syncs | Number of times the Cisco uBR900 series has received synchronization with the downstream channel. |
CRC fails | Number of cyclic redundancy checksums generated by the far-end device that did not match the checksums calculated from the message portions of the packets received. |
HDR check fails | Number of cyclic redundancy checksums generated by the far-end device that did not match the checksums calculated from the MAC headers of the packets received. The MAC header CRC is a 16-bit Header Check Sequence (HCS) field that ensures the integrity of the MAC header even in a collision environment. |
Data pdus | Total number of data PDUs (protocol data units) of all types received by the cable interface. |
Mac msgs | Number of MAC messages received by the cable interface. |
Valid hdrs | Number of valid MAC headers received by the cable interface. |
Below the MIB statistics in the show controllers cable-modem 0 mac hardware display, the BCM3300 registers section shows the DMA locations of the indicated processing routines of the Broadcom 3220 MAC chip within the Cisco uBR900 series.
The following show controllers cable-modem mac state command summarizes the state of the cable MAC layer and provides a list of downstream search frequency bands and the order in which they are searched. If the cable MAC layer is in the wait_for_link_up_state, the information shown in the display corresponds to the last time the interface was up. This allows useful information to be acquired from this display even though the modem has not been able to range and register. The normal operational state of the interface is the maintenance_state.
uBR924# show controller cable-modem 0 mac state
MAC State: maintenance_state
Ranging SID: 5
Registered: TRUE
Privacy Established: TRUE
MIB Values:
Mac Resets: 0
Sync lost: 0
Invalid Maps: 0
Invalid UCDs: 0
Invalid Rng Rsp: 0
Invalid Reg Rsp: 0
T1 Timeouts: 0
T2 Timeouts: 0
T3 Timeouts: 4
T4 Timeouts: 0
Range Aborts: 0
DS ID: 1
DS Frequency: 663000000
DS Symbol Rate: 5056941
DS QAM Mode 64QAM
DS Search:
88 453000000 855000000 6000000
89 93000000 105000000 6000000
90 111250000 117250000 6000000
91 231012500 327012500 6000000
92 333015000 333015000 6000000
93 339012500 399012500 6000000
94 405000000 447000000 6000000
95 123015000 129015000 6000000
96 135012500 135012500 6000000
97 141000000 171000000 6000000
98 219000000 225000000 6000000
99 177000000 213000000 6000000
US ID: 1
US Frequency: 20000000
US Power Level: 34.0 (dBmV)
US Symbol Rate: 1280000
Ranging Offset: 12460
Mini-Slot Size: 8
Change Count: 4
Preamble Pattern: CC CC CC CC CC CC CC CC CC CC CC CC CC CC 0D 0D
A9 17 D9 C3 52 2F B3 86 A4 5F 67 0D 48 BE CE 1A
91 7D 9C 35 22 FB 38 6A 45 F6 70 D4 8B EC E1 A9
17 D9 C3 52 2F B3 86 A4 5F 67 0D 48 BE CE 1A 91
F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 F3
F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 33 F7 33 F7
88 84 04 4C C4 84 C0 0C 44 08 08 CC 8C 0C 80 48
88 40 44 CC 48 4C 00 C4 40 80 8C C8 C0 C8 04 88
Burst Descriptor 0:
Interval Usage Code: 1
Modulation Type: 1
Differential Encoding: 2
Preamble Length: 64
Preamble Value Offset: 56
FEC Error Correction: 0
FEC Codeword Info Bytes: 16
Scrambler Seed: 338
Maximum Burst Size: 1
Guard Time Size: 8
Last Codeword Length: 1
Scrambler on/off: 1
Burst Descriptor 1:
Interval Usage Code: 3
Modulation Type: 1
Differential Encoding: 2
Preamble Length: 128
Preamble Value Offset: 0
FEC Error Correction: 5
FEC Codeword Info Bytes: 34
Scrambler Seed: 338
Maximum Burst Size: 0
Guard Time Size: 48
Last Codeword Length: 1
Scrambler on/off: 1
Burst Descriptor 2:
Interval Usage Code: 4
Modulation Type: 1
Differential Encoding: 2
Preamble Length: 128
Preamble Value Offset: 0
FEC Error Correction: 5
FEC Codeword Info Bytes: 34
Scrambler Seed: 338
Maximum Burst Size: 0
Guard Time Size: 48
Last Codeword Length: 1
Scrambler on/off: 1
Burst Descriptor 3:
Interval Usage Code: 5
Modulation Type: 1
Differential Encoding: 2
Preamble Length: 72
Preamble Value Offset: 48
FEC Error Correction: 5
FEC Codeword Info Bytes: 75
Scrambler Seed: 338
Maximum Burst Size: 0
Guard Time Size: 8
Last Codeword Length: 1
Scrambler on/off: 1
Config File:
Network Access: TRUE
Vendor ID: 0.240.30
Baseline Privacy:
Auth. Wait Timeout: 10
Reauth. Wait Timeout: 10
Auth. Grace Time: 600
Op. Wait Timeout: 1
Retry Wait Timeout: 1
TEK Grace Time: 600
Auth. Reject Wait Time: 60
COS 1:
Assigned SID: 5
Max Downstream Rate: 4000000
Max Upstream Rate: 2000000
Upstream Priority: 7
Min Upstream Rate: 100000
Max Upstream Burst: 12
Privacy Enable: TRUE
Ranging Backoff Start: 0 (at initial ranging)
Ranging Backoff End: 4 (at initial ranging)
Data Backoff Start: 0 (at initial ranging)
Data Backoff End: 4 (at initial ranging)
IP Address: 0.0.0.0
Net Mask: 0.0.0.0
TFTP Server IP Address: 223.255.254.254
Time Server IP Address: 188.188.1.5
Config File Name: muck/ebuell/tftp/cm_conf
Time Zone Offset: -28800
Table 36 describes the fields shown in the display.
| Field | Description |
|---|---|
MAC State | Current operational state of the MAC layer of the Cisco uBR900 series. |
Ranging SID | Service ID used for ranging requests. |
Registered | Indicates whether or not the Cisco uBR900 is currently registered with the CMTS. |
Privacy Established | Indicates whether or not keys for baseline privacy have been exchanged between the Cisco uBR900 series and the CMTS, establishing privacy. |
Mac Resets | Number of times the Cisco uBR900 series reset or initialized this interface. |
Sync lost | Number of times the Cisco uBR900 series lost synchronization with the downstream channel. |
Invalid Maps | Number of times the Cisco uBR900 series received invalid MAP messages. |
Invalid UCDs | Number of times the Cisco uBR900 series received invalid UCD messages. |
Invalid Rng Rsp | Number of times the Cisco uBR900 series received invalid ranging response messages. |
Invalid Reg Rsp | Number of times the Cisco uBR900 series received invalid registration response messages. |
T1 Timeouts | Number of timeouts caused by the Cisco uBR900 series not receiving a valid upstream channel descriptor (UCD) from the CMTS within the specified time. |
T2 Timeouts | Number of timeouts caused by the Cisco uBR900 series not receiving a maintenance broadcast for ranging opportunities from the CMTS within a specified time. |
T3 Timeouts | Number of timeouts caused by the Cisco uBR900 series not receiving a response within a specified time from the CMTS to a RNG-REQ message during initial maintenance. |
T4 Timeouts | Number of timeouts caused by the Cisco uBR900 series not receiving a response within a specified time from the CMTS to a periodic maintenance request. |
Range Aborts | Number of times the ranging process was aborted by the CMTS. |
DS ID | Identifier of the downstream channel on which this MAC management message has been transmitted. This identifier is arbitrarily chosen by the CMTS and is only unique within the MAC-sublayer domain. |
DS Frequency | Downstream frequency acquired by the Cisco uBR900 series during its last initialization sequence. |
DS Symbol Rate | Downstream frequency in symbols per second. |
DS QAM Mode | Downstream modulation scheme being used by the Cisco uBR900 series. |
DS Search | Frequency bands scanned by the Cisco uBR900 series when searching for a downstream channel. The Cisco uBR900 series' default frequency bands correspond to the North American EIA CATV channel plan for 6 MHz channel slots between 90 MHz and 858 MHz. |
US ID | Identifier of the upstream channel to which this MAC management message refers. This identifier is arbitrarily chosen by the CMTS and is only unique within the MAC-sublayer domain. |
US Frequency | Transmission frequency used by the Cisco uBR900 series in the upstream direction. |
US Power Level | Transmit power level of the Cisco uBR900 series in the upstream direction. |
US Symbol Rate | Upstream frequency in symbols per second. |
Ranging Offset | Delay correction (in increments of 6.25 µs/64) applied by the Cisco uBR900 series to the CMTS upstream frame time derived at the Cisco uBR900 series. Used to synchronize the upstream transmissions in the time division multiple access (TDMA) scheme, this value is roughly equal to the round-trip delay of the Cisco uBR900 series from the CMTS. |
Mini-Slot Size | Size T of the mini-slot for this upstream channel in units of the timebase tick of 6.25 µs. Allowable values are 2, 4, 8, 16, 32, 64, or 128. |
Change Count | Incremented by 1 by the CMTS whenever any of the values of this channel descriptor change. If the value of this count in a subsequent upstream channel descriptor (UCD) remains the same, the Cisco uBR900 series can quickly decide that the remaining fields have not changed, and may be able to disregard the remainder of the message. |
Preamble Pattern | Byte pattern used for the preamble. |
Burst Descriptor: Interval Usage Code | A compound type/length/value (TLV) encoding that defines, for each type of upstream usage interval, the physical-layer characteristics that are to be used during that interval. Each burst descriptor is given an identifying number. Each upstream transmit burst belongs to a class which is given a number called the IUC (interval usage code). Bandwidth MAP messages are used by IUC codes to allocate upstream time slots. The following types are currently defined: 1. Request: bandwidth request slot 2. Request/Data: bandwidth request or data slot 3. Initial Maintenance: initial link registration contention slot 4. Station Maintenance: link keep-alive slot 5. Short Data Grant: short data burst slot 6. Long Data Grant: long data burst slot |
Modulation Type | Upstream modulation format. (1 = QPSK; 2 = 16QAM) |
Differential Encoding | Indicates whether or not differential encoding is used. (1 = yes; 2 = no) |
Preamble Length | Length of the preamble in bits. This value must be an integral number of symbolsa multiple of 2 for QPSK; a multiple of 4 for 16QAM. |
FEC Error Correction | Length of the forward error correction in bytes. The range is 0-10 bytes; a value of 0 implies no forward error correction. |
FEC Codeword Info Bytes | Number of information bytes in the FEC codeword. |
Scrambler Seed | 15-bit seed value loaded at the beginning of each burst after the register has been cleared. Not used if scrambler is off. |
Maximum Burst Size | Maximum number of mini-slots that can be transmitted during this burst type. When the interval type is Short Data Grant, this value must be greater than 0. If this value is 0, the burst size is limited elsewhere. |
Guard Time Size | Amount of time in symbols between the center of the last symbol of a burst and the center of the first symbol of the preamble of an immediately following burst in an upstream transmission from the Cisco uBR900 series to the CMTS. |
Last Codeword Length | Indicates whether or not the length of the last codeword is fixed or shortened. |
Scrambler on/off | Indicates whether or not a scrambler is enabled in the upstream modulator. |
Network Access | Indicates whether or not the Cisco uBR900 series has access to the HFC network. |
Vendor ID | Unique identifier specifying the cable modem manufacturer. |
Auth. Wait Timeout | Number of seconds the Cisco uBR900 series waits for a reply after sending the Authorization Request message to the CMTS. |
Reauth. Wait Timeout | Number of seconds the Cisco uBR900 series waits for a reply after it has sent an Authorization Request message to the CMTS in response to a reauthorization request or an Authorization Invalid message from the CMTS. |
Auth. Grace Time | Number of seconds before the current authorization is set to expire that the grace timer begins, signaling the Cisco uBR900 series to begin the reauthorization process. |
Op. Wait Timeout | Number of seconds the TEK state machine waits for a reply from the CMTS after sending its initial Key Request for its SID's keying material. |
Retry Wait Timeout | Number of seconds the TEK state machine waits for a replacement key for this SID after the TEK grace timer has expired and the request for a replacement key has been made. |
TEK Grace Time | Number of seconds before the current TEK is set to expire that the TEK grace timer begins, signaling the TEK state machine to request a replacement key. |
Auth. Reject Wait Time | Number of seconds the Cisco uBR900 series waits before sending another Authorization Request message to the CMTS after it has received an Authorization Reject message. |
Assigned SID | Service ID assigned by the CMTS for the corresponding service class. |
Max Downstream Rate | Maximum downstream rate in bits per second that the CMTS is permitted to forward to CPE unicast MAC addresses learned or configured as mapping to this Cisco uBR900. (This does not include MAC packets addressed to broadcast or multicast MAC addresses.) |
Max Upstream Rate | Maximum upstream rate in bits per second that the Cisco uBR900 series is permitted to forward to the RF network. This includes packet PDU data packets addressed to broadcast or multicast addresses. |
Upstream Priority | Relative priority assigned to this service class for data transmission in the upstream channel. Higher numbers indicate higher priority. |
Min Upstream Rate | Date rate in bits per second that will be guaranteed to this service class on the upstream channel. |
Max Upstream Burst | Maximum transmit burst in bytes allowed for this service class on the upstream channel. |
Privacy Enable | Indicates whether or not Baseline Privacy is enabled for this service class. |
Ranging Backoff Start | Initial back-off window for initial ranging contention, expressed as a power of 2. Valid values are from 0 to 15. |
Ranging Backoff End | Final back-off window for initial ranging contention, expressed as a power of 2. Valid values are from 0 to 15. |
Data Backoff Start | Initial back-off window for contention data and requests, expressed as a power of 2. Valid values are from 0 to 15. |
Data Backoff End | Final back-off window for contention data and requests, expressed as a power of 2. Valid values are from 0 to 15. |
IP Address | IP address of the cable interface. |
Net Mask | Subnet mask of the cable interface. |
TFTP Server IP Address | IP address of the CMTS TFTP server. |
Time Server IP Address | IP address of the CMTS Time of Day (TOD) server. |
Config File Name | Name of the configuration file that is downloaded from the TFTP server to provide the Cisco uBR900 series with operational parameters. |
Time Zone Offset | Correction received from the DHCP server to synchronize the Cisco uBR900 series time clock with the CMTS. |
Related Commands
Displays high-level controller information about a Cisco uBR900 series cable access router. Displays information about the baseline privacy key management exchange between the Cisco uBR900 series and the CMTS. Displays information about the Data Encryption Standard (DES) engine registers. .Displays the registers in the MAC hardware that are used for filtering received frames. Displays the mini-slot lookup table inside a Cisco uBR900 series. Displays the contents of the registers used in the downstream physical hardware of the Cisco uBR900 series. Displays the settings for the upstream and downstream tuners used by a Cisco uBR900 series.
Command
Description
To display the contents of the registers used in the downstream physical hardware of the Cisco uBR900 series cable access router, use the show controllers cable-modem phy command in privileged EXEC mode.
Cisco uBR904, uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
show controllers cable-modem phy {receive | transmit}
Syntax Description
receive Displays all receiver registers in the downstream physical hardware. transmit Displays all transmitter registers in the upstream physical hardware.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Usage Guidelines
To understand the output from this command, consult the Broadcom specifications for the BCM3116 and BCM3037 chips.
Examples
Physical receive registers are displayed in the following example:
uBR924#show controllers cable-modem 0 phy receiveBCM3116 Receiver Registers: Chip ID = C2C1rstctl= frzctl=20 qamctl=1B lmsctl=0B tpctl=00 fmtctl=24ffectl=3F irqsts=09 irqmask=00 stoscm=9E rstctr=00 frzctl2=46dvctl=30 idepth=55 eqlctl=00 tstctl=02 berctl=00 clkset=00tunset=00 tunctl=03FFC coefficient registers:F0=0067FFBC F1=FF880080 F2=00C1FEFB F3=FF75019DF4=00C5FD89 F5=FF6D0485 F6=FC95F690 F7=2D280000DFE coefficient registers:D00=0636031E D01=FBDD0314 D02=0077FD39 D03=001B00C6D04=0024FF74 D05=0015007E D06=000CFFC4 D07=FFC0004BD08=0044FFF6 D09=FFE00019 D10=00190005 D11=FFD3FFADD12=FFD3FFE0 D13=001A000A D14=FFF3FFED D15=0008FFFDD16=FFFC0024 D17=0023FFDF D18=0029FFFF D19=000D001ED20=00020017 D21=00250001 D22=0007FFF4 D23=FFF60014ldsft=B0EE ldsnre=0098AF ldif=0D004E ldbbi=00000000ldbbq=00000000 ldali=032E00 ldaii=E62AF2 ldbrfo=705A05ldbri=F9CDC200 lddrfo=007E7D lddri=007EF0FEC correctable error count: 0FEC uncorrectable error count: 0Bit Error Rate Count: 0
Physical transmit registers are displayed in the following example:
uBR924#show controllers cable-modem 0 phy transmitBCM3037 Transmitter Registers:part_id = 3037 rev_id = 01test_mode = 00 test_input = 00test_misc = 2009 rst = 00power = 0000 power_2 = 00port = 6F pll = F7map = 66 mod = 28tx_oen_bdly = 14 tx_oen_edly = C8prbs_cfg = 00C000 baud = 1A36E3burst = 0000 if_freq = 200000dac = 37 tx_config = 00burst config 0 : prbs_init = FFFFFF rs = 343Efec = 00 qam = 01pream_len = 0018 offset = 0000burst config 1 : prbs_init = FFFFFE rs = 033Bfec = 1C qam = 65pream_len = 0000 offset = 0000burst config 2 : prbs_init = FFFFFE rs = 033Bfec = 1D qam = 65pream_len = 0000 offset = 0000burst config 3 : prbs_init = FFFFFE rs = 033Bfec = 1E qam = 65burst config 4 : prbs_init = FFFFFE rs = 033Bfec = 1F qam = 65pream_len = 0000 offset = 0000burst config 5 : prbs_init = FFFFFE rs = 033Bfec = 0F qam = 66pream_len = 0000 offset = 0000Eq Coeff:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Preamble values:CC CC CC CC CC 0D 0D CC CC CC CC CC CC CC CC 0D04 25 01 01 01 01 02 01 02 03 02 00 40 04 02 0040 05 01 00 06 01 10 07 02 01 52 08 01 01 09 0108 0A 01 01 0B 01 02 04 25 03 01 01 01 02 01 0203 02 00 50 04 02 00 30 05 01 00 06 01 22 07 0201 52 08 01 00 09 01 30 0A 01 01 0B 01 02 04 2504 01 01 01 02 01 02 03 02 00 40 04 02 00 40 0501 00 06 01 22 07 02 01 52 08 01 00 09 01 30 0A
Related Commands
Displays high-level controller information about a Cisco uBR900 series cable access router. Displays information about the baseline privacy key management exchange between the Cisco uBR900 series and the CMTS. Displays information about the Data Encryption Standard (DES) engine registers. .Displays the registers in the MAC hardware that are used for filtering received frames. Displays the mini-slot lookup table inside a Cisco uBR900 series. Displays detailed MAC-layer information for a Cisco uBR900 series. Displays the settings for the upstream and downstream tuners used by a Cisco uBR900 series.
Command
Description
Cisco uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
show controllers cable-modem number qos
Syntax Description
number Cable interface number inside the Cisco uBR924 cable access router (should always be 0 to indicate the first and only cable interface).
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.0(7)XR and 12.1(1)T This command was introduced for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Usage Guidelines
This command displays the four possible stream queues, the SID associated with each queue (if the queue is currently in use), and whether the SID is the primary SID, a secondary (static) SID, or a dynamic (on demand) SID. The display also shows the packets and bytes that have been transmitted and received on each stream.
Examples
The following example displays the current QoS statistics for each of the router's four queues:
uBR924# show controllers cable-modem 0 qos
Queue SID SID SFID TX TX RX RX
Type Pkts Bytes Pkts Bytes
0 2 Primary 0 11377 2721985 12320 983969
1 52 Dynamic 52 116 13608 105 14300
2 0 NA 0 0 0 0 0
3 0 NA 0 0 0 0 0
ubr924#
Table 37 describes significant fields shown in this display.
| Field | Description |
|---|---|
Queue | One of the four possible service flow queues that exist in the Cisco uBR924 cable access router. |
SID | Service Identifier, a 14-bit integer assigned by the CMTS to each active upstream service flow. |
SID Type | The type of SID:
|
SFID | Service Flow Identifier, a 32-bit integer assigned by the CMTS to each service flow on the Cisco uBR924 cable access router. |
TX Pkts | The number of packets the Cisco uBR924 cable access router has transmitted on this service flow. |
TX Bytes | The number of bytes the Cisco uBR924 cable access router has transmitted on this service flow. |
RX Pkts | The number of packets the Cisco uBR924 cable access router has received on this service flow. |
RX Bytes | The number of bytes the Cisco uBR924 cable access router has received on this service flow. |
Related Commands
show controllers cable-modem number mac Displays MAC-layer statistics showing the MAC error log, the other MAC log data, the number of MAC-layer resets, and the current MAC state.
Command
Description
To display the settings for the upstream and downstream tuners used by a Cisco uBR900 series cable access router, use the show controllers cable-modem tuner command in privileged EXEC mode.
Cisco uBR904, uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
show controllers cable-modem tuner
Syntax Description
There are no key words or arguments for this command.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Examples
Typical Cisco uBR900 series tuner settings are displayed in the following example. See Table 38 for output field possibilities and descriptions.
uBR924#show controllers cable-modem 0 tunerTuner: status=0x00Rx: tuner_freq 507000000, symbol_rate 5360736, local_freq 11520000snr_estimate 17488, ber_estimate 0, lock_threshold 26000QAM not in lock, FEC not in lock, qam_mode QAM_64Tx: tx_freq 20000000, power_level 0x3E, symbol_rate 1280000
Field | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Related Commands
Displays high-level controller information about a Cisco uBR900 series cable access router. Displays information about the baseline privacy key management exchange between the Cisco uBR900 series and the CMTS. Displays information about the Data Encryption Standard (DES) engine registers. .Displays the registers in the MAC hardware that are used for filtering received frames. Displays the mini-slot lookup table inside a Cisco uBR900 series. Displays detailed MAC-layer information for a Cisco uBR900 series. Displays the contents of the registers used in the downstream physical hardware of the Cisco uBR900 series.
Command
Description
To display the contents and status of the control command, transmit packet, and receive packet rings used by the hardware accelerator crypto engine, use the show crypto engine accelerator ring Privileged EXEC command.
Cisco uBR905 cable access router
show crypto engine accelerator ring [ control | packet | pool ]
Syntax Description
control Prints out the number of control commands that are queued for execution by the hardware accelerator crypto engine. packet Prints out the contents and status information for the transmit packet rings that are used by the hardware accelerator crypto engine. pool Prints out the contents and status information for the receive packet rings that are used by the hardware accelerator crypto engine.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC.
Command History
12.1(3)XL This command was introduced and enhanced for the Cisco uBR905 router.
Release
Modification
Usage Guidelines
This command displays the version, current status, configuration, and run-time statistics for the hardware accelerator that performs IPsec encryption/decryption for the Cisco uBR905 router.
Examples
The following example displays the number of control commands that are waiting to be executed by the Cisco uBR905 router's hardware accelerator.
uBR905# show crypto engine accelerator ring control control commands queued = 1 uBR905#
The following truncated example displays typical contents of the transmit rings that are used by the Cisco uBR905 router's hardware accelerator.
uBR905# show crypto engine accelerator ring packet
Contents of the high priority transmit descriptor ring:
status id_no handle particle length pkt length
0: 0x00A0 0x0000 0x0011 0x05DC 0x0000
1: 0x00A0 0x0001 0x0012 0x05B5 0x8712
2: 0x00A0 0x0002 0x0011 0x05DC 0x0000
3: 0x00A0 0x0003 0x0012 0x05B6 0x8714
4: 0x00A0 0x0004 0x0011 0x05DC 0x0000
5: 0x00A0 0x0005 0x0012 0x05B7 0x8716
6: 0x00A0 0x0006 0x0011 0x05E4 0x0000
7: 0x00A0 0x0007 0x0012 0x05B8 0x8718
8: 0x00A0 0x0008 0x0011 0x05E4 0x0000
9: 0x00A0 0x0009 0x0012 0x05B9 0x871A
10: 0x00A0 0x000A 0x0011 0x05E4 0x0000
. . .
123: 0x00A0 0x007B 0x0012 0x05B2 0x870C
124: 0x00A0 0x007C 0x0011 0x05DC 0x0000
125: 0x00A0 0x007D 0x0012 0x05B3 0x870E
126: 0x00A0 0x007E 0x0011 0x05DC 0x0000
127: 0x00A0 0x007F 0x0012 0x05B4 0x8710
Head = 59 Tail = 59 Taken = 59
Address of descriptors and some contents of high priority tx shdw ring:
packet particle serial # handle
0: 0x80D6D844 0x00000000 0x0000 0x0011
1: 0x80D1FF24 0x00000000 0x0001 0x0012
2: 0x80D6A0F4 0x00000000 0x0002 0x0011
3: 0x80D1FF24 0x00000000 0x0003 0x0012
4: 0x80D6CD34 0x00000000 0x0004 0x0011
5: 0x80D1FF24 0x00000000 0x0005 0x0012
6: 0x80D22834 0x00000000 0x0006 0x0011
7: 0x80D1FF24 0x00000000 0x0007 0x0012
8: 0x80D22834 0x00000000 0x0008 0x0011
9: 0x80D1FF24 0x00000000 0x0009 0x0012
10: 0x80D22834 0x00000000 0x000A 0x0011
. . .
123: 0x80D1FF24 0x00000000 0x007B 0x0012
124: 0x80D68AD4 0x00000000 0x007C 0x0011
125: 0x80D1FF24 0x00000000 0x007D 0x0012
126: 0x80D69E30 0x00000000 0x007E 0x0011
127: 0x80D1FF24 0x00000000 0x007F 0x0012
Head = 59 Tail = 59 Taken = 59
uBR905#
The following example shows the command that displays the contents of the receive rings that are used by the Cisco uBR905 router's hardware accelerator.
uBR905# show crypto engine accelerator ring pool There are no receive pool and shadow rings uBR905#
Related Commands
clear crypto engine accelerator counter Resets the statistical and error counters for the hardware accelerator crypto engine to zero. crypto ca Defines the parameters for the certification authority used for a session. crypto cisco Defines the encryption algorithms and other parameters for a session. crypto dynamic-map Creates a dynamic map crypto configuration for a session. crypto engine accelerator Enables or disables the onboard hardware accelerator crypto engine. crypto ipsec Defines the IPsec security associations and transformation sets. crypto isakmp Enables and defines the IKE protocol and its parameters. crypto key Generates and exchanges keys for a cryptographic session. crypto map Creates and modifies a crypto map for a session. debug crypto engine accelerator control Prints each control command as it is given to the crypto engine. debug crypto engine accelerator packet Prints information about each packet sent for encryption and decryption. show crypto engine accelerator sa-database Prints the active (in-use) entries in the crypto engine security association (SA) database. show crypto engine accelerator statistic Print out the current run-time statistics and error counters for the crypto engine. show crypto engine brief Print out a summary of the configuration information for the crypto engine. show crypto engine configuration Print out the version and configuration information for the crypto engine. show crypto engine connections Print out a list of the current connections maintained by the crypto engine.
Command
Description
![]() |
Note For information about these additional commands, see the IP Security and Encryption section in the Cisco IOS Release 12.1 Security Command Reference . |
To display the current contents of the hardware accelerator's security association (SA) database, use the show crypto engine accelerator sa-database Privileged EXEC command.
Cisco uBR905 cable access router
show crypto engine accelerator sa-database
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC.
Command History
12.1(3)XL This command was introduced for the Cisco uBR905 router.
Release
Modification
Usage Guidelines
This command displays the contents of the database that contains the security associations used by the Cisco uBR905 cable access router.
Examples
The following example displays the security associations database for the Cisco uBR905 router's hardware accelerator.
uBR905# show crypto engine accelerator sa-database
Hornet14:2010#show cry eng acc sa-database
Flow Summary
Index Algorithms
001 transport inbound esp-des
002 transport outbound esp-des
003 transport inbound esp-md5-hmac esp-3des ah-md5-hmac
004 transport outbound esp-md5-hmac esp-3des ah-md5-hmac
005 transport inbound esp-md5-hmac esp-3des ah-md5-hmac
006 transport outbound esp-md5-hmac esp-3des ah-md5-hmac
007 transport inbound esp-md5-hmac esp-3des ah-md5-hmac
008 transport outbound esp-md5-hmac esp-3des ah-md5-hmac
009 transport inbound esp-md5-hmac esp-3des ah-md5-hmac
010 transport outbound esp-md5-hmac esp-3des ah-md5-hmac
011 tunnel inbound esp-3des
012 tunnel outbound esp-3des
013 tunnel inbound esp-3des ah-sha-hmac
014 tunnel outbound esp-3des ah-sha-hmac
015 tunnel inbound esp-des
016 tunnel outbound esp-des
017 tunnel inbound esp-des ah-md5-hmac
018 tunnel outbound esp-des ah-md5-hmac
019 tunnel inbound esp-des ah-md5-hmac
020 tunnel outbound esp-des ah-md5-hmac
036 tunnel inbound esp-des ah-sha-hmac
037 tunnel outbound esp-des ah-sha-hmac
038 tunnel inbound esp-md5-hmac esp-3des ah-md5-hmac
039 tunnel outbound esp-md5-hmac esp-3des ah-md5-hmac
SA Summary:
Index DH-Index Algorithms
001 007 DES SHA
002 001(deleted) DES SHA
003 001(deleted) DES SHA
004 001(deleted) DES SHA
012 001(deleted) DES SHA
016 001(deleted) DES SHA
017 004(deleted) DES SHA
018 002(deleted) DES SHA
019 009(deleted) DES SHA
DH Summary
Index Group Config
007 001 Shared Secret
uBR905#
Table 0-39 explains each field.
| Field | Description |
|---|---|
Flow Summary | |
Flow Index | Unique identifier for the flow. |
Flow Algorithm | The Flow Algorithm field displays the transformation set for each SA: Mode
Direction
Encapsulating Security Protocol (ESP) Transform
ESP Authentication Transform
Authentication Header (AH) Transform
|
SA Summary | |
SA Index | Unique identifier for the SA. |
SA DH-Index | Unique identifier for the Diffie-Hellman group used in this SA. If the connection is not currently active, the text "(deleted)" follows the index number. |
SA Algorithms | The transform al set for this SA:
|
DH Summary | |
DH Index | Unique DH index. |
DH Group | Identifies the DH group. |
DH Config | The type of keys:
|
Related Commands
clear crypto engine accelerator counter Resets the statistical and error counters for the hardware accelerator crypto engine to zero. crypto ca Defines the parameters for the certification authority used for a session. crypto cisco Defines the encryption algorithms and other parameters for a session. crypto dynamic-map Creates a dynamic map crypto configuration for a session. crypto engine accelerator Enables or disables the onboard hardware accelerator crypto engine. crypto ipsec Defines the IPsec security associations and transformation sets. crypto isakmp Enables and defines the IKE protocol and its parameters. crypto key Generates and exchanges keys for a cryptographic session. crypto map Creates and modifies a crypto map for a session. debug crypto engine accelerator control Prints each control command as it is given to the crypto engine. debug crypto engine accelerator packet Prints information about each packet sent for encryption and decryption. show crypto engine accelerator ring control Prints the contents of command ring, which queues the control commands that are being sent to the crypto engine. show crypto engine accelerator ring packet Prints the contents of the transmit packet ring, which contains the packets being sent to the crypto engine for encryption and decryption. show crypto engine accelerator statistic Print out the current run-time statistics and error counters for the crypto engine. show crypto engine brief Print out a summary of the configuration information for the crypto engine. show crypto engine configuration Print out the version and configuration information for the crypto engine. show crypto engine connections Print out a list of the current connections maintained by the crypto engine.
Command
Description
![]() |
Note For information about these additional commands, see the IP Security and Encryption section in the Cisco IOS Release 12.1 Security Command Reference . |
To display the statistics and error counters for the Cisco uBR905 router's onboard hardware accelerator for IPsec encryption, use the show crypto engine accelerator statistic Privileged EXEC command.
Cisco uBR905 cable access router
show crypto engine accelerator statistic
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC.
Command History
12.1(1)XC This command was introduced for the Cisco 1700 series router and other Cisco routers that support hardware accelerators for IPsec encryption. 12.1(3)XL This command was introduced for the Cisco uBR905 router.
Release
Modification
Usage Guidelines
This command displays the run-time statistics and error counters for the hardware accelerator engine that performs IPsec encryption/decryption for the Cisco uBR905 router.
Examples
The following example is a typical display of the current statistics and error counters for the Cisco uBR905 router's hardware accelerator.
uBR905# show crypto engine accelerator statistics
HIFN79xx:
ds: 0x80D92A64 idb:0x80D6F39C
Statistics for Virtual Private Network (VPN) Module:
1292 packets in 1292 packets out
2 paks/sec in 2 paks/sec out
6 Kbits/sec in 6 Kbits/sec out
rx_no_endp: 0 rx_hi_discards: 0 fw_failure: 0
invalid_sa: 0 invalid_flow: 0
fw_qs_filled: 0 fw_resource_lock:0 lotx_full_err: 0
null_ip_error: 0 pad_size_error: 0 out_bound_dh_acc: 0
esp_auth_fail: 0 ah_auth_failure: 0 crypto_pad_error: 0
ah_prot_absent: 0 ah_seq_failure: 0 ah_spi_failure: 0
esp_prot_absent:0 esp_seq_fail: 0 esp_spi_failure: 0
obound_sa_acc: 0 invalid_sa: 0 out_bound_sa_flow: 0
invalid_dh: 0 bad_keygroup: 0 out_of_memory: 0
no_sh_secret: 0 no_skeys: 0 invalid_cmd: 0
dsp_coproc_err: 0 comp_unsupported:0 pak_too_big: 0
pak_mp_length_spec_fault: 0
tx_lo_queue_size_max 2 cmd_unimplemented: 0
tx_lo_count 60
15124 seconds since last clear of counters
Interrupts: Notify = 0, Reflected = 1292, Spurious = 0
packet_loop_max: 2 packet_loop_limit: 512
uBR905#
Related Commands
clear crypto engine accelerator counter Resets the statistical and error counters for the hardware accelerator crypto engine to zero. crypto ca Defines the parameters for the certification authority used for a session. crypto cisco Defines the encryption algorithms and other parameters for a session. crypto dynamic-map Creates a dynamic map crypto configuration for a session. crypto engine accelerator Enables or disables the onboard hardware accelerator crypto engine. crypto ipsec Defines the IPsec security associations and transformation sets. crypto isakmp Enables and defines the IKE protocol and its parameters. crypto key Generates and exchanges keys for a cryptographic session. crypto map Creates and modifies a crypto map for a session. debug crypto engine accelerator control Prints each control command as it is given to the crypto engine. debug crypto engine accelerator packet Prints information about each packet sent for encryption and decryption. show crypto engine accelerator ring control Prints the contents of command ring, which queues the control commands that are being sent to the crypto engine. show crypto engine accelerator ring packet Prints the contents of the transmit packet ring, which contains the packets being sent to the crypto engine for encryption and decryption. show crypto engine accelerator sa-database Prints the active (in-use) entries in the crypto engine security association (SA) database. show crypto engine brief Print out a summary of the configuration information for the crypto engine. show crypto engine configuration Print out the version and configuration information for the crypto engine. show crypto engine connections Print out a list of the current connections maintained by the crypto engine.
Command
Description
![]() |
Note For information about these additional commands, see the IP Security and Encryption section in the Cisco IOS Release 12.1 Security Command Reference . |
To display the version, capabilities, and other information for the Cisco uBR905 router's onboard hardware accelerator engine, use the show crypto engine brief Privileged EXEC command.
Cisco uBR905 cable access router
show crypto engine brief
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privilege d EXEC.
Command History
11.2 This command was introduced for the Cisco 7200, RSP7000, and 7500 series routers. 12.1(3)XL This command was introduced for the Cisco uBR905 router.
Release
Modification
Usage Guidelines
This command displays the version, capabilities, and other information for the hardware accelerator engine that performs IPsec encryption/decryption for the Cisco uBR905 router.
Examples
The following example shows the typical display for the show crypto engine brief command:
uBR905# show crypto engine brief
crypto engine name: unknown
crypto engine type: ISA/ISM
hifn chip id: 8
hifn rev : 0
hifn api rev: 0.22.0
Compression: No
3 DES: Yes
Privileged Mode: 0x0000
Maximum buffer length: 4096
Maximum DH index: 0010
Maximum SA index: 0020
Maximum Flow index: 0040
Maximum RSA key size: 0256
crypto engine name: unknown
crypto engine type: software
serial number: 00000000
crypto engine state: installed
crypto engine in slot: N/A
uBR905#
Table 0-40 explains each field.
| Field | Description |
|---|---|
crypto engine name | Name of the crypto engine as assigned with the key-name argument in the crypto key generate dss command. If no name has been assigned, this field shows `unknown'. |
crypto engine type | The type of encryption engine running, always `ISA/ISM' and `software' for the Cisco uBR905 cable access router. |
hifn chip id, rev, and api rev | Identifies the hardware accelerator, the revision of its onboard firmware, and the revision of the software application layer. |
Compression | Identifies whether packets are compressed as well as encrypted. |
3DES | Identifies whether Triple DES (3DES) 168-bit encryption is supported. |
crypto engine state | The current run-time state of the crypto engine:
|
crypto firmware version | Version number of the crypto library running on the router. |
crypto engine in slot | The chassis slot number containing the crypto engine. This is always N/A for the Cisco uBR905 cable access router because the engine is not in a slot but is permanently onboard the router. |
Related Commands
clear crypto engine accelerator counter Resets the statistical and error counters for the hardware accelerator crypto engine to zero. crypto ca Defines the parameters for the certification authority used for a session. crypto cisco Defines the encryption algorithms and other parameters for a session. crypto dynamic-map Creates a dynamic map crypto configuration for a session. crypto engine accelerator Enables or disables the onboard hardware accelerator crypto engine. crypto ipsec Defines the IPsec security associations and transformation sets. crypto isakmp Enables and defines the IKE protocol and its parameters. crypto key Generates and exchanges keys for a cryptographic session. crypto map Creates and modifies a crypto map for a session. debug crypto engine accelerator control Prints each control command as it is given to the crypto engine. debug crypto engine accelerator packet Prints information about each packet sent for encryption and decryption. show crypto engine accelerator ring control Prints the contents of command ring, which queues the control commands that are being sent to the crypto engine. show crypto engine accelerator ring packet Prints the contents of the transmit packet ring, which contains the packets being sent to the crypto engine for encryption and decryption. show crypto engine accelerator sa-database Prints the active (in-use) entries in the crypto engine security association (SA) database. show crypto engine accelerator statistic Print out the current run-time statistics and error counters for the crypto engine. show crypto engine configuration Print out the version and configuration information for the crypto engine. show crypto engine connections Print out a list of the current connections maintained by the crypto engine.
Command
Description
![]() |
Note For information about these additional commands, see the IP Security and Encryption section in the Cisco IOS Release 12.1 Security Command Reference . |
To display the configuration information for the Cisco uBR905 router's onboard hardware accelerator engine, use the show crypto engine configuration Privileged EXEC command.
Cisco uBR905 cable access router
show crypto engine configuration
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC.
Command History
11.2 This command was introduced for the Cisco 7200, RSP7000, and 7500 series routers. 12.1(3)XL This command was introduced for the Cisco uBR905 router.
Release
Modification
Usage Guidelines
This command displays the version, capabilities, and other information for the hardware accelerator engine that performs IPsec encryption/decryption for the Cisco uBR905 router.
Examples
The following example shows the typical display for the show crypto engine configuration command:
uBR905# show crypto engine configuration
crypto engine name: unknown
crypto engine type: ISA/ISM
hifn chip id: 8
hifn rev : 0
hifn api rev: 0.22.0
Compression: No
3 DES: Yes
Privileged Mode: 0x0000
Maximum buffer length: 4096
Maximum DH index: 0010
Maximum SA index: 0020
Maximum Flow index: 0040
Maximum RSA key size: 0256
Crypto Adjacency Counts:
Lock Count: 0
Unlock Count: 0
uBR905#
Table 0-41 explains each field.
| Field | Description |
|---|---|
crypto engine name | Name of the crypto engine as assigned with the key-name argument in the crypto key generate dss command. If no name has been assigned, this field shows `unknown'. |
crypto engine type | Type of encryption engine running, always `ISA/ISM' and `software' for the Cisco uBR905 cable access router. |
hifn chip id, rev, and api rev | Identifies the hardware accelerator, the revision of its onboard firmware, and the revision of the software application layer. |
Compression | Identifies whether packets are compressed as well as encrypted. |
3DES | Identifies whether Triple DES (3DES) 168-bit encryption is supported. |
Maximum buffer length | Maximum size of the data buffer for each connection. |
Maximum DH index, SA index, and Flow index | Maximum size of each index that is supported per connection. |
Maximum RSA key size | Maximum size of the RSA encryption key that is supported. |
Lock Count | Number of connections that have requested access to the crypto engine and are waiting for processing time. |
Unlock Count | Number of connections that have finished encryption processing and are waiting to release the crypto engine. |
Related Commands
clear crypto engine accelerator counter Resets the statistical and error counters for the hardware accelerator crypto engine to zero. crypto ca Defines the parameters for the certification authority used for a session. crypto cisco Defines the encryption algorithms and other parameters for a session. crypto dynamic-map Creates a dynamic map crypto configuration for a session. crypto engine accelerator Enables or disables the onboard hardware accelerator crypto engine. crypto ipsec Defines the IPsec security associations and transformation sets. crypto isakmp Enables and defines the IKE protocol and its parameters. crypto key Generates and exchanges keys for a cryptographic session. crypto map Creates and modifies a crypto map for a session. debug crypto engine accelerator control Prints each control command as it is given to the crypto engine. debug crypto engine accelerator packet Prints information about each packet sent for encryption and decryption. show crypto engine accelerator ring control Prints the contents of command ring, which queues the control commands that are being sent to the crypto engine. show crypto engine accelerator ring packet Prints the contents of the transmit packet ring, which contains the packets being sent to the crypto engine for encryption and decryption. show crypto engine accelerator sa-database Prints the active (in-use) entries in the crypto engine security association (SA) database. show crypto engine accelerator statistic Print out the current run-time statistics and error counters for the crypto engine. show crypto engine brief Print out a summary of the configuration information for the crypto engine. show crypto engine connections Print out a list of the current connections maintained by the crypto engine.
Command
Description
![]() |
Note For information about these additional commands, see the IP Security and Encryption section in the Cisco IOS Release 12.1 Security Command Reference . |
To display the configuration information for the Cisco uBR905 router's onboard hardware accelerator engine, use the show crypto engine configuration privileged EXEC command.
Cisco uBR905 cable access router
show crypto engine connections [ active | dh | dropped-packet | flow ]
Syntax Description
active Prints out the configuration information for each active session. dh Prints out the Diffie-Hellman connection status. dropped-packet Prints out the number of packets that the crypto engine has dropped. flow Prints out the definition for each flow that has been defined.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC.
Command History
11.2 This command was introduced for the Cisco 7200, RSP7000, and 7500 series routers. 12.1(3)XL This command was introduced for the Cisco uBR905 router.
Release
Modification
Usage Guidelines
This command displays the version, capabilities, and other information for the hardware accelerator engine that performs IPsec encryption/decryption for the Cisco uBR905 router.
Examples
The following example shows the typical display for the show crypto engine connections active command:
uBR905# show crypto engine connections active
ID Interface IP-Address State Algorithm Encrypt Decrypt
1 <none> <none> set HMAC_MD5+DES_56_CB 0 0
2068 cable-modem0 192.168.100.9 set HMAC_MD5 0 2484
2069 cable-modem0 192.168.100.9 set HMAC_MD5 2618 0
2070 cable-modem0 192.168.100.9 set 3DES_56_CBC 0 2484
2071 cable-modem0 192.168.100.9 set 3DES_56_CBC 2618 0
2072 cable-modem0 192.168.100.9 set HMAC_MD5 0 232
2073 cable-modem0 192.168.100.9 set HMAC_MD5 94 0
2074 cable-modem0 192.168.100.9 set 3DES_56_CBC 0 232
2075 cable-modem0 192.168.100.9 set 3DES_56_CBC 94 0
ubr905#
Table 0-42 explains each field.
| Field | Description |
|---|---|
ID | Identifies the connection by its number. Each active encrypted session connection is identified by a positive number from 1 to 299. These connection numbers correspond to the table entry numbers. |
Interface | Interface involved in the encrypted session connection. |
IP-Address | IP address of the interface. |
State | Current state of the connection:
|
Algorithm | The encryption algorithms used for this connection. If this field says "NONE," this connection is still being allocated and has not yet requested an algorithm. |
Encrypt | Total number of encrypted outbound IP packets. |
Decrypt | Total number of encrypted outbound IP packets. |
The following example shows the typical display for the show crypto engine connections dh command:
uBR905# show crypto engine connections dh Conn ID Status 0 0 1 0 14 1 0 0 1 0 0 1 0 18 1 uBR905#
Table 0-43 explains each field.
| Field | Description |
|---|---|
Conn | Identifies the connection by its number. Each active encrypted session connection is identified by a positive number from 1 to 299. These connection numbers correspond to the table entry numbers. |
ID | Identifies the Diffie-Hellman group. |
Status | Identifies the Diffie-Hellman status: 1768-bit Diffie-Hellman prime modulus group 21024-bit Diffie-Hellman prime modulus group |
The following example shows the typical display for the show crypto engine connections dropped-packet command:
uBR905# show crypto engine connections dropped-packet Interface IP-Address Drop Count Ethernet0/0 192.168.100.165 4 uBR905#
Table 0-44 explains each field.
| Field | Description |
|---|---|
Interface | Interface involved in the encrypted session connection. |
IP-Address | IP address of the interface. |
Drop Count | Total number of dropped packets since the last reset of the Cisco uBR905 cable access router. |
The following example shows the typical display for the show crypto engine connections flow command:
uBR905# show crypto engine connections flow
flow_id ah_conn_id esp_conn_id comp_spi
3 0 0 0
4 0 0 0
7 0 0 0
8 0 0 0
9 0 0 0
10 0 0 0
11 0 0 0
12 0 0 0
13 0 0 0
14 0 0 0
36 0 0 0
37 0 0 0
38 0 0 0
39 0 0 0
uBR905#
Table 0-45 explains each field.
| Field | Description |
|---|---|
flow_id | Unique identifier for this flow. |
ah_conn_id | Unique identifier for the flow's Authentication Header. |
esp_conn_id | Unique Identifier for the flow's Encapsulating Security Protocol (ESP). |
comp_spi | Security Parameter Index (SPI)An arbitrary number that unique identifies the flow's security association. |
Related Commands
clear crypto engine accelerator counter Resets the statistical and error counters for the hardware accelerator crypto engine to zero. crypto ca Defines the parameters for the certification authority used for a session. crypto cisco Defines the encryption algorithms and other parameters for a session. crypto dynamic-map Creates a dynamic map crypto configuration for a session. crypto engine accelerator Enables or disables the onboard hardware accelerator crypto engine. crypto ipsec Defines the IPsec security associations and transformation sets. crypto isakmp Enables and defines the IKE protocol and its parameters. crypto key Generates and exchanges keys for a cryptographic session. crypto map Creates and modifies a crypto map for a session. debug crypto engine accelerator control Prints each control command as it is given to the crypto engine. debug crypto engine accelerator packet Prints information about each packet sent for encryption and decryption. show crypto engine accelerator ring control Prints the contents of command ring, which queues the control commands that are being sent to the crypto engine. show crypto engine accelerator ring packet Prints the contents of the transmit packet ring, which contains the packets being sent to the crypto engine for encryption and decryption. show crypto engine accelerator sa-database Prints the active (in-use) entries in the crypto engine security association (SA) database. show crypto engine accelerator statistic Print out the current run-time statistics and error counters for the crypto engine. show crypto engine brief Print out a summary of the configuration information for the crypto engine. show crypto engine configuration Print out the version and configuration information for the crypto engine.
Command
Description
![]() |
Note For information about these additional commands, see the IP Security and Encryption section in the Cisco IOS Release 12.1 Security Command Reference . |
To display the current Dynamic Host Configuration Protocol (DHCP) settings on point-to-point interfaces, use the show dhcp command in privileged EXEC mode.
Cisco uBR904, uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
show dhcp {lease | server}
Syntax Description
lease Displays DHCP addresses leased from a server. server Displays known DHCP servers.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Usage Guidelines
You can use this command on any point-to-point type of interface that uses DHCP for temporary IP address allocation.
Examples
The following is sample output for the show dhcp lease command:
uBR924#show dhcp leaseTemp IP addr: 188.188.1.40 for peer on Interface: cable-modem0Temp sub net mask: 0.0.0.0DHCP Lease server: 4.0.0.32, state: 3 BoundDHCP transaction id: 2431Lease: 3600 secs, Renewal: 1800 secs, Rebind: 3150 secsTemp default-gateway addr: 188.188.1.1Next timer fires after: 00:58:01Retry count: 0 Client-ID: 0010.7b43.aa01
Table 46 describes the significant fields shown in the display.
| Field | Description |
|---|---|
Temp IP addr | IP address leased from the DHCP server for the cable access router interface. |
Temp subnet mask | Temporary subnet mask assigned to the cable access router interface. |
DHCP Lease server | IP address of the DHCP server that assigned an IP address to this client. |
state | Current state of this client (the cable access router interface). Possible states are Bound, Renew, or Rebinding. For descriptions of these states, see RFC 2131. |
DHCP transaction id | Unique number established by the Cisco uBR924 before the first request message is sent to the DHCP server. The same transaction id is used as long as the lease keeps getting renewed and is valid. If a new "discover" message is sent, a new transaction ID is used. |
Lease | Time (in seconds) for which the leased IP address is valid; the duration of the lease. |
Renewal | Time interval (in seconds) from address assignment until the client transitions to the renewing state. When the renewal (T1) time expires, the client sends a unicast dhcprequest message to the server to extends its lease. The default value of this timer is 0.5 times the duration of the lease. |
Rebind | Time interval (in seconds) from address assignment until the client transitions to the rebinding state and sends a broadcast dhcprequest message to any DHCP server to extends its lease. The default value of this timer (T2) is 0.875 times the duration of the lease. |
Temp default-gateway addr | IP address of the router closest to this client on the network. |
Next timer fires after | Time in hours, minutes, and seconds until the next timer expires. |
Retry count | Number of times the client has sent any message to the DHCP servermost likely a request message to extend its lease. When the lease is renewed, the Retry count is reset to 0. |
Client-ID | MAC address (with optional media type code) that uniquely identifies the client on the subnet for binding lookups. |
The following is sample output for the show dhcp server command:
uBR924#show dhcp serverDHCP server: ANY (255.255.255.255)Leases: 1Offers: 1 Requests: 2 Acks: 1 Naks: 0Declines: 0 Releases: 0 Bad: 0TFTP Server Name: SOHOSERVERTIME0: 1.2.0.250, TIME1: 0.0.0.0 Subnet: 255.255.255.0
Table 47 describes the significant fields shown in the display.
| Field | Description |
|---|---|
DHCP server | MAC address used by the DHCP server. |
Leases | Number of current leased IP addresses. |
Offers | Number of offers for an IP address sent to a proxy client from the server. |
Requests | Number of requests for an IP address to the server. |
Acks | Number of acknowledge messages sent by the server to the proxy client. |
Naks | Number of not acknowledge messages sent by the server to the proxy client. |
Declines | Number of offers from the server that have been declined by the proxy client. |
Releases | Number of times IP addresses have been relinquished gracefully by the client. |
Bad | Number of bad packets received due to wrong length, wrong field type, or other causes. |
TFTP Server Name | Name (if any) configured for the server providing TFTP downloads to the cable modem. |
TIME0 | IP address of the primary Time of Day (ToD) server. |
TIME1 | IP address of the secondary Time of Day (ToD) server. |
Subnet | Subnet containing the DHCP server. |
Related Commands
cable-modem voip best-effort Allows voice calls to be sent upstream over the cable interface via best effort. show bridge cable-modem Displays bridging information for a cable modem. show interfaces cable-modem Displays information about the cable interface of the Cisco uBR900 series cable access router.
Command
Description
To display information about the Cisco uBR924 cable access router cable interface, use the show interfaces cable-modem command in either user EXEC mode or privileged EXEC mode.
Cisco uBR904, uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
show interfaces cable-modem number [accounting | counters | crb | irb | type]
Syntax Description
number Cable access router interface number. accounting (Optional) Displays the number of packets of each protocol type that has been sent through the cable access router interface. counters (Optional) Shows MIB counters on the cable interface. crb (Optional) Displays concurrent routing and bridging information for each interface that has been configured for routing or bridging. This option does not really apply to the Cisco uBR924; it is included because it is part of the subsystem that provides DOCSIS-compliant bridging. For more information, refer to the Bridging and IBM Networking Command Reference. irb (Optional) Displays integrated routing and bridging information for each interface that has been configured for routing or bridging. This option does not really apply to the Cisco uBR924; it is included because it is part of the subsystem that provides DOCSIS-compliant bridging. For more information, refer to the Bridging and IBM Networking Command Reference. type (Optional) Designed to display information about virtual LANs associated with the interface; however, this option is not supported on the Cisco uBR924.
Defaults
No default behavior or values.
Command Modes
User EXEC or privileged EXEC
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Usage Guidelines
When this command is entered without a keyword, general information about the cable interface is displayed.
Examples
Traffic passing through the cable access router interface is shown in the following example:
uBR924#show interfaces cable-modem 0cable-modem0 is up, line protocol is up Hardware is BCM3300, address is 0050.7366.2439 (bia 0050.7366.2439) Internet address is 5.2.0.11/16 MTU 1500 bytes, BW 27000 Kbit, DLY 1000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation DOCSIS, loopback not set Keepalive set (10 sec) ARP type:ARPA, ARP Timeout 04:00:00 Last input 00:00:00, output 00:00:00, output hang never Last clearing of "show interface" counters 00:08:40 Queueing strategy:fifo Output queue 40/40, 52787 drops; input queue 0/75, 0 drops 5 minute input rate 2000 bits/sec, 2 packets/sec 5 minute output rate 94000 bits/sec, 154 packets/sec 1074 packets input, 418472 bytes, 0 no buffer Received 19 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 78771 packets output, 6326786 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out
Table 48 describes the significant fields shown in the display.
| Field | Description |
|---|---|
cable-modem0 is up | Indicates that the interface is currently active. "Disabled" indicates the interface has received more than 5000 errors in one keepalive interval (10 seconds by default if keepalive is set); "administratively down" indicates the interface has been taken down by an administrator. |
line protocol is up | Indicates that the software processes that handle the line protocol believe the interface is usable. |
Hardware | Hardware type and MAC address. |
Internet address | Internet address followed by the shorthand notation for the subnet mask. |
MTU | Maximum Transmission Unit (equivalent of the maximum packet size) for the interface. |
BW | Bandwidth of the interface in kilobits per second. |
DLY | Delay of the interface in microseconds. |
reliability | Reliability of the interface, expressed as a fraction of 255, calculated as an exponential average over a 5-minute period. (255/255 equals 100% reliability.) |
tx load/rx load | Load on the interface caused by transmitting and receiving, expressed as a fraction of 255, calculated as an exponential average over a 5 minute period. |
Encapsulation/loopback/keepalive | Encapsulation method assigned to the interface. |
loopback | Indicates whether or not loopback is set. |
keepalive | Indicates whether or not keepalives are set. |
ARP type | Type of Address Resolution Protocol configured for the interface. |
ARP Timeout | Number of hours, minutes, and seconds an ARP cache entry will stay in the cache. |
Last input/output | Number of hours, minutes, and seconds since the last packet was successfully received/transmitted by the interface. |
output hang | Number of hours, minutes, and seconds since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "Last..." fields exceeds 24, the number of days and hours is displayed. If the field overflows, asterisks are printed. |
Last clearing of "show interface" counters | Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared. *** indicates the elapsed time is too large to be displayed. |
Queueing strategy | Type of queueing strategy in effect on the interface. |
Output queue/drops | Number of packets in the output queue followed by the size of the queue and the number of packets dropped due to a full queue. |
input queue/drops | Number of packets in the input queue followed by the size of the queue and the number of packets dropped due to a full queue. |
5 minute input rate | Average number of bits and packets received and transmitted per second in the last 5 minutes. If the interface is not in promiscuous mode, it senses network traffic it sends and receives (rather than all network traffic). The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period. |
packets input | Total number of error-free packets received by the system. |
bytes input | Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system. |
no buffer | Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events. |
Received broadcasts | Total number of broadcast or multicast packets received by the interface. |
runts | Number of packets discarded because they were smaller than the medium's minimum packet size. For example, any Ethernet packet less than 64 bytes is considered a runt. |
giants | Number of packets discarded because they were larger than the medium's maximum packet size. For example, any Ethernet packet larger than 1518 bytes is considered a giant. |
throttles | Number of times the receiver on the port was disabled, possibly due to buffer or processor overload. |
input errors | Includes runts, giants, no buffer, CRC, frame, overrun, and ignored counts. Other input-related errors can also cause the input errors count to be increased, and some datagrams may have more than one error; therefore, this sum may not balance with the sum of enumerated input error counts. |
CRC | Number of cyclic redundancy checksums generated by the originating LAN station or far-end device that do not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station sending bad data. |
frame | Number of packets received incorrectly, having a CRC error and a noninteger number of octets. On a LAN, this is usually the result of collisions or a malfunctioning Ethernet device. |
overrun | Number of times the receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data. |
ignored | Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different from the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be increased. |
abort | Number of packets whose receipt was aborted. |
packets output | Total number of messages sent by the system. |
bytes | Total number of bytes, including data and MAC encapsulation, sent by the system. |
underruns | Number of times the transmitter has been running faster than the router can handle. |
output errors | Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, as some datagrams might have more than one error, and others might have errors that do not fall into any of the specifically tabulated categories. |
collisions | Number of messages retransmitted due to an Ethernet collision. This is usually the result of an overextended LAN (Ethernet or transceiver cable too long, more than two repeaters between stations, or too many cascaded multiport transceivers). A packet that collides is counted only once in output packets. |
interface resets | Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down. |
output buffer failures | Number of times the output buffer has failed. |
output buffers swapped out | Number of times the output buffer has been swapped out. |
To display the number of packets and bytes of each protocol type passing through the cable access router interface, use the accounting option with the show interfaces cable-modem command:
uBR924#show interfaces cable-modem 0 accountingcable-modem0Protocol Pkts In Chars In Pkts Out Chars OutIP 545 185502 159 90240Trans. Bridge 3878 964995 12597 1611142ARP 73 3066 86 4128
Table 49 describes the significant fields shown in this display.
| Field | Description |
|---|---|
Protocol | List of protocols operating on the cable-modem interface. |
Pkts In | Number of packets of each protocol received on the interface. |
Chars In | Number of bytes of each protocol received on the interface. |
Pkts Out | Number of packets of each protocol sent on the interface. |
Chars Out | Number of bytes of cache protocol sent on the interface. |
MIB counters on the cable interface are displayed in the following example:
uBR924#show interfaces cable-modem 0 countersCable specific counters:Ranging requests sent : 50982Downstream FIFO full : 0Re-requests : 7277DS MAC Message Overruns: 0DS Data Overruns : 0Received MAPs : 254339485Received Syncs : 53059555Message CRC failures : 0Header CRC failures : 1394Data PDUs : 5853DS MAC messages : 307861745Valid Headers : 307869065Sync losses : 0Pulse losses : 1BW request failures : 6
Table 50 describes the counters shown in this display.
| Field | Description |
|---|---|
Ranging requests sent | Number of ranging requests sent by the Cisco uBR924 to the CMTS. |
Downstream FIFO full | Number of times the downstream input first-in first-out (FIFO) buffer became full on the Cisco uBR924. |
Re-requests | Number of times a bandwidth request generated by the Cisco uBR924 was not responded to by the CMTS. |
DS MAC Message Overruns | Number of times the Cisco uBR924 DMA controller had a downstream MAC message and there were no free MAC message buffer descriptors to accept the message. |
DS Data Overruns | Number of times the Cisco uBR924 DMA controller had downstream data and there were no free data PDU buffer descriptors to accept the data. |
Received MAPs | Number of times a MAP message passed all filtering requirements and was received by the Cisco uBR924. |
Received Syncs | Number of times a time-stamp message was received by the Cisco uBR924. |
Message CRC failures | Number of times a MAC message failed a cyclic redundancy (CRC) check. |
Header CRC failures | Number of times a MAC header failed its 16-bit CRC check. The MAC header CRC is a 16-bit Header Check Sequence (HCS) field that ensures the integrity of the MAC header even in a collision environment. |
Data PDUs | Total number of data PDUs (protocol data units) of all types received by the Cisco uBR924. |
DS MAC messages | Number of MAC messages received by the Cisco uBR924. |
Valid Headers | Number of valid headers received by the Cisco uBR924, including PDU headers, MAC headers, and headers only. |
Sync losses | Number of times the Cisco uBR924 lost timebase sync with the CMTS. |
Pulse losses | Number of times the Cisco uBR924 did not receive expected timestamp messages from the CMTS. |
BW request failures | Number of times the Cisco uBR924 sent the maximum number of re-requests for bandwidth allocation and the request was still not granted. |
Information about routing and bridging protocols and filtering on the cable access router interface is displayed in the following example:
uBR924#show interfaces cable-modem 0 crbcable-modem0Bridged protocols on cable-modem0:ipSoftware MAC address filter on cable-modem0Hash Len Address Matches Act Type0x00: 0 ffff.ffff.ffff 3877 RCV Physical broadcast0x2A: 0 0900.2b01.0001 0 RCV DEC spanning tree0x7A: 0 0010.7b43.aa01 573 RCV Interface MAC address0xC2: 0 0180.c200.0000 0 RCV IEEE spanning tree0xC2: 1 0180.c200.0000 0 RCV IBM spanning tree
Table 51 describes the software MAC address filter information for the cable access router interface.
| Field | Description |
|---|---|
Hash | Hash key/relative position in the keyed list for this MAC address filter. |
Len | Length of this entry to the beginning element of this hash chain. |
Address | Canonical (Ethernet ordered) MAC address of this filter. |
Matches | Number of received packets that match this MAC address. |
Act | Action to be taken when this address is looked up; choices are to receive or discard the packet. |
Type | MAC address type. |
Related Commands
show bridge cable-modem Displays bridging information for a cable modem.
Command
Description
Cisco uBR924 cable access router
show voice port number
Syntax Description
For the Cisco uBR924 cable access router
:
number | Indicates the RJ-11 connectors installed in the Cisco uBR924. Valid entries are 0 (which corresponds to the RJ-11 connector labeled V1) and 1 (which corresponds to the RJ-11 connector labeled V2. |
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.0(4)XL Support added for the Cisco uBR924.
Release
Modification
Usage Guidelines
This command applies to Voice over IP on the Cisco uBR924 cable access router.
Use the show voice port privileged EXEC command to display configuration and voice interface card-specific information about a specific port.
Examples
The following is sample output from the show voice port command for the Cisco uBR924 cable access router:
router# show voice port 0
Foreign Exchange Station 0
Type of VoicePort is FXS
Operation State is DORMANT
Administrative State is UP
No Interface Down Failure
Description is not set
Noise Regeneration is enabled
Non Linear Processing is enabled
Music On Hold Threshold is Set to -38 dBm
In Gain is Set to -2 dB
Out Attenuation is Set to 0 dB
Echo Cancellation is enabled
Echo Cancel Coverage is set to 8 ms
Connection Mode is normal
Connection Number is not set
Initial Time Out is set to 10 s
Interdigit Time Out is set to 10 s
Call-Disconnect Time Out is set to 60 s
Ringing Time Out is set to 180 s
Region Tone is set for US
Analog Info Follows:
Currently processing none
Maintenance Mode Set to None (not in mtc mode)
Number of signaling protocol errors are 0
Impedance is set to 600r Ohm
Voice card specific Info Follows:
Signal Type is loopStart
Ring Frequency is 25 Hz
Hook Status is On Hook
Ring Active Status is inactive
Ring Ground Status is inactive
Tip Ground Status is inactive
Digit Duration Timing is set to 100 ms
InterDigit Duration Timing is set to 100 ms
Table 52 explains the fields in the sample output.
| Field | Description |
|---|---|
Administrative State | Administrative state of the voice port. |
Alias | User-supplied alias for this voice port, if any. |
Coder Type | Voice compression mode used. |
Connection Mode | Connection mode of the interface. |
Connection Number | Full E.164 telephone number used to establish a connection with the trunk or PLAR mode. |
Currently Processing | Type of call currently being processed: none, voice, or fax. |
Description | Description of the voice port. |
Digit Duration Timing | DTMF digit duration in milliseconds. |
Echo Cancel Coverage | Echo cancel coverage for this port. |
Echo Cancellation | Whether or not echo cancellation is enabled for this port. |
Hook Flash Duration Timing | Maximum length of hook flash signal. |
Hook Status | Hook status of the FXO/FXS interface. |
Impedance | Configured terminating impedance for the E&M interface. |
In Gain | Amount of gain inserted at the receiver side of the interface. |
Initial Time Out | Amount of time the system waits for an initial input digit from the caller. |
InterDigit Duration Timing | DTMF interdigit duration in milliseconds. |
InterDigit Pulse Duration Timing | Pulse dialing interdigit timing in milliseconds. |
Interdigit Time Out | Amount of time the system waits for a subsequent input digit from the caller. |
Maintenance Mode | Maintenance mode of the voice port. |
Music On Hold Threshold | Configured music-on-hold threshold value for this interface. |
Noise Regeneration | Whether or not background noise should be played to fill silent gaps if VAD is activated. |
Non-Linear Processing | Whether or not nonlinear processing is enabled for this port. |
Number of signalling protocol errors | Number of signalling protocol errors. |
Operations State | Operation state of the port. |
Out Attenuation | Amount of attenuation inserted at the transmit side of the interface. |
Region Tone | Configured regional tone for this interface. |
Ring Active Status | Ring active indication. |
Ring Cadence | Configured ring cadence for this interface. |
Ring Frequency | Configured ring frequency for this interface. |
Ring Ground Status | Ring ground indication. |
Ringing Time Out | Ringing time out duration. |
Signal Type | Type of signalling for a voice port: loop-start, ground-start, wink-start, immediate, and delay-dial. |
Tip Ground Status | Tip ground indication. |
Type of VoicePort | Type of voice port: always FXS for the Cisco uBR924 cable access router. |
Related Commands
show call active voice Displays the contents of the active call table. show call history voice Displays the contents of the call history table. show dial-peer voice Displays configuration information and call statistics for dial peers. show voice port Displays configuration information about a specific voice port.
Command
Description
To enter the voice-port configuration mode, use the voice-port command in global configuration mode.
Cisco uBR924 cable access router
voice-port number
Syntax Description
For the Cisco uBR924 cable access router
:
number | Indicates the RJ-11 connectors installed in the Cisco uBR924. Valid entries are 0 (which corresponds to the RJ-11 connector labeled V1) and 1 (which corresponds to the RJ-11 connector labeled V2. |
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
12.0(4)XI1 Support for the Cisco uBR924 cable access router was added.
Release
Modification
Usage Guidelines
Use the voice-port global configuration command to switch to the voice-port configuration mode from the global configuration mode. Use the exit command to exit the voice-port configuration mode and return to the global configuration mode. See the Cisco IOS Release 12.1 Multiservice Applications Command Reference , available on CCO and the Documentation CD-ROM for a list of subcommands that are supported by the voice-port global configuration command.
Examples
The following example accesses the voice-port configuration mode for port 0, the first voice port (labeled "V1+V2") on the Cisco uBR924 cable access router.
ubr924# configure terminal ubr924(config)# voice-port 0
Related Commands
dial-peer voice Enters dial-peer configuration mode, defines the type of dial peer, and defines the tag number associated with a dial peer.
Command
Description
This section describes the following debug commands, which are not normally needed to install or configure the Cisco cable CPE devices. These commands are used to troubleshoot the device's installation or configuration.
Additional debug commands are documented in the Cisco IOS Release 12.1 Debug Command Reference , available on CCO and the Documentation CD-ROM.
![]() |
Caution The debug commands are primarily intended for use in controlled test and troubleshooting situations with a limited volume of traffic. You should use caution when enabling debug messages because sending these messages to the console consumes system resources. Turning on too many types of debug messages can adversely affect the router's network performance, depending on what messages are being displayed and the type of traffic that is occurring. |
To display Baseline Privacy Interface (BPI) information, use the debug cable-modem mac command in privileged EXEC mode. The no form of this command turns debugging messages off.
Cisco uBR904, uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
debug cable-modem bpkm {errors | events | packets}
no debug cable-modem bpkm {errors | events | packets}
Syntax Description :
errors Debugs cable modem privacy errors. events Debugs events related to cable baseline privacy. packets Debugs baseline privacy packets.
Defaults
The default is not to display any debugging messages.
Command Modes
Privileged EXEC
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Usage Guidelines
Baseline privacy key management exchanges take place only when both the Cisco uBR900 series and the CMTS are running code images that support baseline privacy, and the privacy class of service is enabled via the configuration file that is downloaded to the cable access router. Baseline privacy code images for the Cisco uBR900 series contain k1 in the code image name.
This command should be used only while debugging cable modem operation. Displaying debugging messages consumes system resources, and turning on too many messages could negatively affect system performance.
Examples
The following example shows typical debug output when the headend does not have privacy enabled:
uBR924# debug cable-modem bpkm errors cm_bpkm_fsm(): machine: KEK, event/state: EVENT_4_TIMEOUT/STATE_B_AUTH_WAIT, new state: STATE_B_AUTH_WAIT cm_bpkm_fsm(): machine: KEK, event/state: EVENT_4_TIMEOUT/STATE_B_AUTH_WAIT, new state: STATE_B_AUTH_WAIT %LINEPROTO-5-UPDOWN: Line protocol on Interface cable-modem0, changed state to down cm_bpkm_fsm(): machine: KEK, event/state: EVENT_1_PROVISIONED/STATE_A_START, new state: STATE_B_AUTH_WAIT %LINEPROTO-5-UPDOWN: Line protocol on Interface cable-modem0, changed state to up
Related Commands
Display bridge filter processing information. Display debugging messages for the cable interface driver. Display information about cable modem interrupts. Display information about the cable modem MAC layer. Display the timing of MAP and sync messages.
Command
Description
Use the debug cable-modem bridge command in privileged EXEC mode to display bridge filter processing information on a cable modem. The no form of this command turns debugging messages off.
Cisco uBR904, uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
debug cable-modem bridge
no debug cable-modem bridge
Syntax Description
This command has no keywords or arguments.
Defaults
The default is not to display any debugging messages.
Command Modes
Privileged EXEC
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Usage Guidelines
When the interface is down, all bridge table entries learned on the Ethernet interface are set to discard because traffic is not bridged until the cable interface has completed initialization. After the interface (the line protocol) is completely up, bridge table entries learned on the Ethernet interface program the cable's MAC data filters. The cable MAC hardware filters out any received packets whose addresses are not in the filters. In this way, the cable interface only receives packets addressed to its own MAC address or an address it has learned on the Ethernet interface.
This command should be used only while debugging cable modem operation. Displaying debugging messages consumes system resources, and turning on too many messages could negatively affect system performance.
Examples
The following shows sample display output for the debug cable-modem bridge command.
uBR924# debug cable-modem bridge %LINEPROTO-5-UPDOWN: Line protocol on Interface cable-modem0, changed state to downshut cm_tbridge_add_entry(): MAC not initialized, discarding entry: 00e0.fe7a.186fno shut cm_tbridge_add_entry(): MAC not initialized, discarding entry: 00e0.fe7a.186f %LINEPROTO-5-UPDOWN: Line protocol on Interface cable-modem0, changed state to up cm_tbridge_add_entry(): Adding entry 00e0.fe7a.186f to filter 2
Related Commands
Display Baseline Privacy Interface (BPI) information. Display debugging messages for the cable interface driver. Display information about cable modem interrupts. Display information about the cable modem MAC layer. Display the timing of MAP and sync messages.
Command
Description
Use the debug cable-modem error command in privileged EXEC mode to display debugging messages for the cable interface driver. The no form of this command turns debugging messages off.
Cisco uBR904, uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
debug cable-modem error
no debug cable-modem error
Syntax Description
This command has no keywords or arguments.
Defaults
The default is not to display any debugging messages.
Command Modes
Privileged EXEC
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Usage Guidelines
This command displays detailed output about the sanity checking of received frame formats, the acquisition of downstream QAM/FEC lock, the receipt or non-receipt of SYNC messages from the CMTS, reception errors, and bandwidth request failures.
This command should be used only while debugging cable modem operation. Displaying debugging messages consumes system resources, and turning on too many messages could negatively affect system performance.
Examples
The following shows sample display output for the debug cable-modem error command.
uBR924# debug cable-modem error *Mar 7 20:16:29: AcquireSync(): Update rate is 100 Hz *Mar 7 20:16:30: 1st Sync acquired after 1100 ms. *Mar 7 20:16:30: Recovery loop is locked (7/9) *Mar 7 20:16:30: 2nd Sync acquired after 100 ms. *Mar 7 20:16:30: Recovery loop is locked (10/15)
Related Commands
Display Baseline Privacy Interface (BPI) information. Display bridge filter processing information. Display information about cable modem interrupts. Display information about the cable modem MAC layer. Display the timing of MAP and sync messages.
Command
Description
Use the debug cable-modem interrupts command in privileged EXEC mode to display information about cable modem interrupts. The no form of this command turns debugging messages off.
Cisco uBR904, uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
debug cable-modem interrupts
no debug cable-modem interrupts
Syntax Description
This command has no keywords or arguments.
Defaults
The default is not to display any debugging messages.
Command Modes
Privileged EXEC
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Usage Guidelines
This command should be used only while debugging cable modem operation. Displaying debugging messages consumes system resources, and turning on too many messages could negatively affect system performance.
Examples
The following shows sample debug output for cable modem interrupts.
uBR924# debug cable-modem interrupts *** bcm3220_rx_mac_msg_interrupt *** *** bcm3220_rx_mac_msg_interrupt *** ### bcm3220_tx_interrupt ### *** bcm3220_rx_mac_msg_interrupt *** ### bcm3220_tx_interrupt ### *** bcm3220_rx_mac_msg_interrupt *** ### bcm3220_tx_interrupt ### ### bcm3220_tx_interrupt ### ### bcm3220_tx_interrupt ### ### bcm3220_tx_interrupt ###
Related Commands
Display Baseline Privacy Interface (BPI) information. Display bridge filter processing information. Display debugging messages for the cable interface driver. Display information about the cable modem MAC layer. Display the timing of MAP and sync messages.
Command
Description
Use the debug cable-modem mac command in privileged EXEC mode to display information about the cable modem MAC layer. The no form of this command turns debugging messages off.
Cisco uBR904, uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
debug cable-modem mac {log [verbose] | messages}
no debug cable-modem mac {log [verbose] | messages}
Syntax Description :
log Real time MAC log display. verbose Displays periodic MAC layer events, such as ranging. messages MAC layer management messages.
Defaults
The default is not to display any debugging messages.
Command Modes
Privileged EXEC
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Usage Guidelines
Of all the available debug cable modem commands, the most useful is debug cable-modem mac log.
Mac log messages are written to a circular log file even when debugging is not turned on. These messages include timestamps, events, and information pertinent to these events. Enter the debug cable-modem mac log command to view Mac log messages. If you want to view this information without entering debug mode, enter the show controllers cable-modem number mac log command. The same information is displayed by both commands.
If the Cisco uBR900 series interface fails to come up or resets periodically, the Mac log will show what happened. For example, if an address is not obtained from the DHCP server, an error is logged, initialization starts over, and the cable modem scans for a downstream frequency. The debug cable-modem mac log command displays the log from oldest entry to newest entry.
After initial ranging is successful (dhcp_state has been reached), further RNG-REQ/RNG-RSP messages and watchdog timer entries are suppressed from output unless the verbose keyword is used. Note that CMAC_LOG_WATCHDOG_TIMER entries while in the maintenance_state are normal when using the verbose keyword.
This command should be used only while debugging cable modem operation. Displaying debugging messages consumes system resources, and turning on too many messages could negatively affect system performance.
Examples
Example 1
This example shows sample display output from the debug cable-modem mac log command. The fields of the output are the time since bootup, the log message, and in some cases a parameter that gives more detail about the log entry.
uBR924# debug cable-modem mac log *Mar 7 01:42:59: 528302.040 CMAC_LOG_LINK_DOWN *Mar 7 01:42:59: 528302.042 CMAC_LOG_RESET_FROM_DRIVER *Mar 7 01:42:59: 528302.044 CMAC_LOG_STATE_CHANGE wait_for_link_up_state *Mar 7 01:42:59: 528302.046 CMAC_LOG_DRIVER_INIT_IDB_SHUTDOWN 0x08098D02 *Mar 7 01:42:59: 528302.048 CMAC_LOG_LINK_DOWN *Mar 7 01:43:05: 528308.428 CMAC_LOG_DRIVER_INIT_IDB_RESET 0x08098E5E *Mar 7 01:43:05: 528308.432 CMAC_LOG_LINK_DOWN *Mar 7 01:43:05: 528308.434 CMAC_LOG_LINK_UP *Mar 7 01:43:05: 528308.436 CMAC_LOG_STATE_CHANGE ds_channel_scanning_state *Mar 7 01:43:05: 528308.440 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 88/453000000/855000000/6000000 *Mar 7 01:43:05: 528308.444 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 89/93000000/105000000/6000000 *Mar 7 01:43:05: 528308.448 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 90/111250000/117250000/6000000 *Mar 7 01:43:05: 528308.452 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 91/231012500/327012500/6000000 *Mar 7 01:43:05: 528308.456 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 92/333015000/333015000/6000000 *Mar 7 01:43:05: 528308.460 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 93/339012500/399012500/6000000 *Mar 7 01:43:05: 528308.462 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 94/405000000/447000000/6000000 *Mar 7 01:43:05: 528308.466 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 95/123015000/129015000/6000000 *Mar 7 01:43:05: 528308.470 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 96/135012500/135012500/6000000 *Mar 7 01:43:05: 528308.474 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 97/141000000/171000000/6000000 *Mar 7 01:43:05: 528308.478 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 98/219000000/225000000/6000000 *Mar 7 01:43:05: 528308.482 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 99/177000000/213000000/6000000 *Mar 7 01:43:05: 528308.486 CMAC_LOG_WILL_SEARCH_SAVED_DS_FREQUENCY 663000000 *Mar 7 01:43:05: 528308.488 CMAC_LOG_WILL_SEARCH_USER_DS_FREQUENCY 663000000 *Mar 7 01:43:07: 528310.292 CMAC_LOG_DS_64QAM_LOCK_ACQUIRED 663000000 . . . 528383.992 CMAC_LOG_STATE_CHANGE registration_state 528384.044 CMAC_LOG_REG_REQ_MSG_QUEUED 528384.050 CMAC_LOG_REG_REQ_TRANSMITTED 528384.052 CMAC_LOG_REG_RSP_MSG_RCVD 528384.078 CMAC_LOG_COS_ASSIGNED_SID 1/4 528384.102 CMAC_LOG_RNG_REQ_QUEUED 4 528384.102 CMAC_LOG_REGISTRATION_OK 528384.102 CMAC_LOG_STATE_CHANGE establish_privacy_state 528384.102 CMAC_LOG_STATE_CHANGE maintenance_state 528388.444 CMAC_LOG_RNG_REQ_TRANSMITTED 528388.444 CMAC_LOG_RNG_RSP_MSG_RCVD 528398.514 CMAC_LOG_RNG_REQ_TRANSMITTED 528398.516 CMAC_LOG_RNG_RSP_MSG_RCVD 528408.584 CMAC_LOG_RNG_REQ_TRANSMITTED 528408.586 CMAC_LOG_RNG_RSP_MSG_RCVD 528414.102 CMAC_LOG_WATCHDOG_TIMER 528418.654 CMAC_LOG_RNG_REQ_TRANSMITTED 528418.656 CMAC_LOG_RNG_RSP_MSG_RCVD 528428.726 CMAC_LOG_RNG_REQ_TRANSMITTED 528428.728 CMAC_LOG_RNG_RSP_MSG_RCVD 528438.796 CMAC_LOG_RNG_REQ_TRANSMITTED 528438.798 CMAC_LOG_RNG_RSP_MSG_RCVD 528444.102 CMAC_LOG_WATCHDOG_TIMER 528444.492 CMAC_LOG_LINK_DOWN 528444.494 CMAC_LOG_RESET_FROM_DRIVER 528444.494 CMAC_LOG_STATE_CHANGE wait_for_link_up_state 528444.494 CMAC_LOG_DRIVER_INIT_IDB_SHUTDOWN 0x08098D02 528444.494 CMAC_LOG_LINK_DOWN 528474.494 CMAC_LOG_WATCHDOG_TIMER 528504.494 CMAC_LOG_WATCHDOG_TIMER 528534.494 CMAC_LOG_WATCHDOG_TIMER 0 events dropped due to lack of a chunk
![]() |
Note The line "0 events dropped due to lack of a chunk" at the end of the display indicates that no log entries were discarded due to a temporary lack of memory. This means the log is accurate and reliable. |
Example 2
The following example compares the output of the debug cable-modem mac log command with the debug cable-modem mac log verbose command. The verbose keyword displays periodic events such as ranging.
uBR924# debug cable mac log Cable Modem mac log debugging is on uBR924# uBR924# debug cable mac log verbose Cable Modem mac log debugging is on (verbose) uBR924# 574623.810 CMAC_LOG_RNG_REQ_TRANSMITTED 574623.812 CMAC_LOG_RNG_RSP_MSG_RCVD 574627.942 CMAC_LOG_WATCHDOG_TIMER 574633.880 CMAC_LOG_RNG_REQ_TRANSMITTED 574633.884 CMAC_LOG_RNG_RSP_MSG_RCVD 574643.950 CMAC_LOG_RNG_REQ_TRANSMITTED 574643.954 CMAC_LOG_RNG_RSP_MSG_RCVD 574654.022 CMAC_LOG_RNG_REQ_TRANSMITTED 574654.024 CMAC_LOG_RNG_RSP_MSG_RCVD 574657.978 CMAC_LOG_WATCHDOG_TIMER 574664.094 CMAC_LOG_RNG_REQ_TRANSMITTED 574664.096 CMAC_LOG_RNG_RSP_MSG_RCVD 574674.164 CMAC_LOG_RNG_REQ_TRANSMITTED 574674.166 CMAC_LOG_RNG_RSP_MSG_RCVD uBR924# no debug cable mac log verbose Cable Modem mac log debugging is off uBR924# 574684.234 CMAC_LOG_RNG_REQ_TRANSMITTED 574684.238 CMAC_LOG_RNG_RSP_MSG_RCVD
Example 3
The following example shows display output for the debug cable mac messages command. This command causes received cable MAC management messages to be displayed in a verbose format. The messages that are displayed are shown below:
uBR924# debug cable-modem mac messages ? dynsrv dynamic service mac messages map map messages received reg-req reg-req messages transmitted reg-rsp reg-rsp messages received rng-req rng-req messages transmitted rng-rsp rng-rsp messages received sync Sync messages received ucc-req ucc-req messages received ucc-rsp ucc-rsp messages transmitted ucd UCD messages received <cr>
The dynsrv keyword displays Dynamic Service Add or Dynamic Service Delete messages during the off-hook/on-hook transitions of a phone connected to the Cisco uBR900 series.
In addition, transmitted REG-REQs are displayed in hex dump format. The output from this command is very verbose and is usually not needed for normal interface debugging. The command is most useful when attempting to attach a Cisco uBR900 series cable access router to a CMTS that is not DOCSIS-qualified.
For a description of the displayed fields of each message, refer to the DOCSIS Radio Frequency Interface Specification, v1.0 (SP-RFI-I04-980724).
uBR924# debug cable mac messages *Mar 7 01:44:06: *Mar 7 01:44:06: UCD MESSAGE *Mar 7 01:44:06: ----------- *Mar 7 01:44:06: FRAME HEADER *Mar 7 01:44:06: FC - 0xC2 == MAC Management *Mar 7 01:44:06: MAC_PARM - 0x00 *Mar 7 01:44:06: LEN - 0xD3 *Mar 7 01:44:06: MAC MANAGEMENT MESSAGE HEADER *Mar 7 01:44:06: DA - 01E0.2F00.0001 *Mar 7 01:44:06: SA - 00E0.1EA5.BB60 *Mar 7 01:44:06: msg LEN - C1 *Mar 7 01:44:06: DSAP - 0 *Mar 7 01:44:06: SSAP - 0 *Mar 7 01:44:06: control - 03 *Mar 7 01:44:06: version - 01 *Mar 7 01:44:06: type - 02 == UCD *Mar 7 01:44:06: RSVD - 0 *Mar 7 01:44:06: US Channel ID - 1 *Mar 7 01:44:06: Configuration Change Count - 4 *Mar 7 01:44:06: Mini-Slot Size - 8 *Mar 7 01:44:06: DS Channel ID - 1 *Mar 7 01:44:06: Symbol Rate - 8 *Mar 7 01:44:06: Frequency - 20000000 *Mar 7 01:44:06: Preamble Pattern - CC CC CC CC CC CC CC CC CC CC CC 0D 0D *Mar 7 01:44:06: Burst Descriptor 0 *Mar 7 01:44:06: Interval Usage Code - 1 *Mar 7 01:44:06: Modulation Type - 1 == QPSK *Mar 7 01:44:06: Differential Encoding - 2 == OFF *Mar 7 01:44:06: Preamble Length - 64 *Mar 7 01:44:06: Preamble Value Offset - 56 *Mar 7 01:44:06: FEC Error Correction - 0 *Mar 7 01:44:06: FEC Codeword Info Bytes - 16 *Mar 7 01:44:06: Scrambler Seed - 0x0152 *Mar 7 01:44:06: Maximum Burst Size - 1 *Mar 7 01:44:06: Guard Time Size - 8 *Mar 7 01:44:06: Last Codeword Length - 1 == FIXED *Mar 7 01:44:06: Scrambler on/off - 1 == ON *Mar 7 01:44:06: Burst Descriptor 1 *Mar 7 01:44:06: Interval Usage Code - 3 *Mar 7 01:44:06: Modulation Type - 1 == QPSK *Mar 7 01:44:06: Differential Encoding - 2 == OFF *Mar 7 01:44:06: Preamble Length - 128 *Mar 7 01:44:06: Preamble Value Offset - 0 *Mar 7 01:44:06: FEC Error Correction - 5 *Mar 7 01:44:06: FEC Codeword Info Bytes - 34 *Mar 7 01:44:06: Scrambler Seed - 0x0152 *Mar 7 01:44:06: Maximum Burst Size - 0 *Mar 7 01:44:06: Guard Time Size - 48 *Mar 7 01:44:06: Last Codeword Length - 1 == FIXED *Mar 7 01:44:06: Scrambler on/off - 1 == ON *Mar 7 01:44:06: Burst Descriptor 2 *Mar 7 01:44:06: Interval Usage Code - 4 *Mar 7 01:44:06: Modulation Type - 1 == QPSK *Mar 7 01:44:06: Differential Encoding - 2 == OFF *Mar 7 01:44:06: Preamble Length - 128 *Mar 7 01:44:06: Preamble Value Offset - 0 *Mar 7 01:44:06: FEC Error Correction - 5 *Mar 7 01:44:06: FEC Codeword Info Bytes - 34 *Mar 7 01:44:06: Scrambler Seed - 0x0152 *Mar 7 01:44:06: Maximum Burst Size - 0 *Mar 7 01:44:06: Guard Time Size - 48 *Mar 7 01:44:06: Last Codeword Length - 1 == FIXED *Mar 7 01:44:06: Scrambler on/off - 1 == ON *Mar 7 01:44:06: Burst Descriptor 3 *Mar 7 01:44:06: Interval Usage Code - 5 *Mar 7 01:44:06: Modulation Type - 1 == QPSK *Mar 7 01:44:06: Differential Encoding - 2 == OFF *Mar 7 01:44:06: Preamble Length - 72 *Mar 7 01:44:06: Preamble Value Offset - 48 *Mar 7 01:44:06: FEC Error Correction - 5 *Mar 7 01:44:06: FEC Codeword Info Bytes - 75 *Mar 7 01:44:06: Scrambler Seed - 0x0152 *Mar 7 01:44:06: Maximum Burst Size - 0 *Mar 7 01:44:06: Guard Time Size - 8 *Mar 7 01:44:06: Last Codeword Length - 1 == FIXED *Mar 7 01:44:06: Scrambler on/off - 1 == ON *Mar 7 01:44:06: *Mar 7 01:44:06: *Mar 7 01:44:06: MAP MESSAGE *Mar 7 01:44:06: ----------- *Mar 7 01:44:06: FRAME HEADER *Mar 7 01:44:06: FC - 0xC3 == MAC Mement with Extended Header *Mar 7 01:44:06: MAC_PARM - 0x02 *Mar 7 01:44:06: LEN - 0x42 *Mar 7 01:44:06: EHDR - 0x00 0x00 *Mar 7 01:44:06: MAC MANAGEMENT MESSAGE HEADER *Mar 7 01:44:06: DA - 01E0.2F00.0001 . *Mar 7 01:44:17: RNG-RSP MESSAGE *Mar 7 01:44:17: --------------- *Mar 7 01:44:17: FRAME HEADER *Mar 7 01:44:17: FC - 0xC2 == MAC Management *Mar 7 01:44:17: MAC_PARM - 0x00 *Mar 7 01:44:17: LEN - 0x2B *Mar 7 01:44:17: MAC MANAGEMENT MESSAGE HEADER *Mar 7 01:44:17: DA - 00F0.1EB2.BB61 . *Mar 7 01:44:20: REG-REQ MESSAGE *Mar 7 01:44:20: --------------- *Mar 7 01:44:20: C20000A5 000000E0 1EA5BB60 00F01EB2 *Mar 7 01:44:20: BB610093 00000301 06000004 03010104 *Mar 7 01:44:20: 1F010101 0204003D 09000304 001E8480 *Mar 7 01:44:20: 04010705 04000186 A0060200 0C070101 *Mar 7 01:44:20: 080300F0 1E112A01 04000000 0A020400 *Mar 7 01:44:20: 00000A03 04000002 58040400 00000105 *Mar 7 01:44:20: 04000000 01060400 00025807 04000000 *Mar 7 01:44:20: 3C2B0563 6973636F 06105E4F C908C655 *Mar 7 01:44:20: 61086FD5 5C9D756F 7B730710 434D5453 *Mar 7 01:44:20: 204D4943 202D2D2D 2D2D2D2D 0C040000 *Mar 7 01:44:20: 00000503 010100 *Mar 7 01:44:20: *Mar 7 01:44:20: *Mar 7 01:44:20: REG-RSP MESSAGE *Mar 7 01:44:20: --------------- *Mar 7 01:44:20: FRAME HEADER *Mar 7 01:44:20: FC - 0xC2 == MAC Management *Mar 7 01:44:20: MAC_PARM - 0x00 *Mar 7 01:44:20: LEN - 0x29 *Mar 7 01:44:20: MAC MANAGEMENT MESSAGE HEADER *Mar 7 01:44:20: DA - 00F0.1EB2.BB61
Related Commands
Display Baseline Privacy Interface (BPI) information. Display bridge filter processing information. Display debugging messages for the cable interface driver. Display information about cable modem interrupts. Display the timing of MAP and sync messages.
Command
Description
Cisco uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
debug cable-modem mac messages dynsrv
no debug cable-modem mac messages dynsrv
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.0(7)XR and 12.1(1)T This command was introduced for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Usage Guidelines
This command begins the display of debug messages that show the dynamic service MAC messages that are generated when a voice call is made using the dynamic SID feature. Dynamic SIDs use the following DOCSIS MAC-layer messages to create a new SID when a voice call is made and to delete it when the call is over:
![]() |
Note Dynamic Services are described in the DOCSIS 1.1 specification (SP-RFIv1.1-I03-991105 or later revision). |
Examples
The following example enables the display of debug messages related to dynamic service operations:
ubr924# debug cable-modem mac messages dynsrv ubr924#
The following example turns off the display of debug messages related to dynamic service operations:
ubr924# no debug cable-modem mac messages dynsrv ubr924#
The following are examples of the types of debug messages that are displayed when a voice call is made. This example shows that dynamic SID 52 is created for this particular call.
DSA-REQ TLV's:
--------------
US Flow Scheduler(24):
Unsolicited Grant Size - 19:2:89
Nominal Grant Interval - 20:4:20000
Created New Dynamic Service State, Transaction_id = 3
DSA-REQ MESSAGE TLVS
--------------------
C2000026 00010010 07DF6854 00507366
23270014 00000301 0F000003 180A1302
00591404 00004E20
597.721 CMAC_LOG_DSA_REQ_MESSAGE_EVENT
DSA-REQ MESSAGE
---------------
FRAME HEADER
FC - 0xC2 == MAC Management
MAC_PARM - 0x00
LEN - 0x26
MAC MANAGEMENT MESSAGE HEADER
DA - 0010.abcd.ef00
SA - 0050.abcd.ef00
msg LEN - 14
DSAP - 0
SSAP - 0
control - 03
version - 01
type - 0F == DSA-REQ
RSVD - 0
Transaction ID - 3
597.725 CMAC_LOG_DSA_RSP_MSG_RCVD
DSA-RSP MESSAGE
---------------
FRAME HEADER
FC - 0xC2 == MAC Management
MAC_PARM - 0x00
LEN - 0x26
MAC MANAGEMENT MESSAGE HEADER
DA - 0050.abcd.ef00
SA - 0010.abcd.ef00
msg LEN - 14
DSAP - 0
SSAP - 0
control - 03
version - 01
type - 10 == DSA-RSP
RSVD - 0
Transaction ID - 3
Response - 0 == DSA-RSP-OK
SID - 52
Adding sid = 52 to sid_index = 1
597.729 CMAC_LOG_QOS_ADD_FLOW_SID 52
Related Commands
debug cable-modem mac messages Displays debug messages for other types of MAC-layer messages, including MAP messages, upstream request messages, and sync messages. show controllers cable-modem number qos Displays current statistics for each primary, secondary, and dynamic SIDs.
Command
Description
Use the debug cable-modem map command in privileged EXEC mode to display the timing from MAP messages to sync messages and the timing between MAP messages. The no form of this command disables debugging output.
Cisco uBR904, uBR905, uBR924 cable access routers, Cisco uBR914 cable DSU
debug cable-modem map
no debug cable-modem map
Syntax Description
This command has no keywords or arguments.
Defaults
The default is not to display any debugging messages.
Command Modes
Privileged EXEC
Command History
11.3(4)NA This command was introduced for the Cisco uBR904 cable access router. 12.0(4)XI1 Support was added for the Cisco uBR924 cable access router. 12.1(1)XD Support was added for the Cisco uBR914 cable DSU. 12.1(3)XL Support was added for the Cisco uBR905 cable access router.
Release
Modification
Usage Guidelines
This command should be used only while debugging cable modem operation. Displaying debugging messages consumes system resources, and turning on too many messages could negatively affect system performance.
Examples
The following shows display output for the debug cable map Privileged EXEC command.
uBR924# debug cable-modem map Cable Modem MAP debugging is on uBR924# *Mar 7 20:12:08: 595322.942: Min MAP to sync=72 *Mar 7 20:12:08: 595322.944: Max map to map time is 40 *Mar 7 20:12:08: 595322.982: Min MAP to sync=63 *Mar 7 20:12:08: 595323.110: Max map to map time is 41 *Mar 7 20:12:08: 595323.262: Min MAP to sync=59 *Mar 7 20:12:08: 595323.440: Max map to map time is 46 *Mar 7 20:12:09: 595323.872: Min MAP to sync=58
Related Commands
Display Baseline Privacy Interface (BPI) information. Display bridge filter processing information. Display debugging messages for the cable interface driver. Display information about cable modem interrupts. Display information about the cable modem MAC layer.
Command
Description
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Sun Oct 1 19:34:43 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.