Table Of Contents
Configuring the Cisco uBR900 Series Cable Access Routers
Cisco IOS Software Feature Sets
Downstream and Upstream Data Transfer
Triple Data Encryption Standard
NetRanger Support—IOS Intrusion Detection
Related Features and Technologies
Configuring a Host Name and Password
Verifying the Host Name and Password
Configuration, Verification, and Troubleshooting Tips
Configuring Ethernet and Cable Access Router Interfaces
Verifying IP Address Configuration
Configuration, Verification, and Troubleshooting Tips
Reestablishing DOCSIS-Compliant Bridging
Verifying DOCSIS-Compliant Bridging
Customizing the Cable Access Router Interface
Using Multiple PCs with the Cable Access Router
Basic Internet Access Bridging Configuration
Basic Internet Access Routing Configuration
Multicast-Enabled Routing Configuration
VoIP Bridging Configuration Using H.323v2
VoIP Routing Configuration Using H.323v2
VoIP Bridging Configuration Using SGCP
cable-modem downstream saved channel
cable-modem upstream preamble qpsk
show controllers cable-modem bpkm
show controllers cable-modem des
show controllers cable-modem filters
show controllers cable-modem lookup-table
show controllers cable-modem mac
show controllers cable-modem phy
show controllers cable-modem tuner
Configuring the Cisco uBR900 Series Cable Access Routers
This document addresses the following topics:
•
VoIP Bridging Configuration Using SGCP
Feature Overview
Cisco uBR900 series cable access routers are fully-functional Cisco IOS routers and standards-based bidirectional cable modems that give a residential or small office/home office (SOHO) subscriber high-speed Internet or Intranet access and packet telephone services via a shared two-way cable system and IP backbone network. Cisco uBR900 series cable access routers are based on the current Data-Over-Cable Service Interface Specifications (DOCSIS) standards, and interoperate with any bidirectional, DOCSIS-qualified headend cable modem termination system (CMTS).
Cisco uBR900 series routers connect computers, telephone equipment, and other customer premises devices at a subscriber site to the service provider's Hybrid/Fiber Coax (HFC) and IP backbone network. Functioning as cable modems, the Cisco uBR900 series routers transport data and voice traffic on the same cable system that delivers broadcast TV signals.
Cisco uBR900 series cable access routers typically ship from the Cisco factory with a Cisco Internetwork Operating System (IOS) software image stored in nonvolatile memory (NVRAM). The standard Cisco IOS software image supports DOCSIS-compliant bridging operation for data as the default.
Based on the feature licenses purchased, other Cisco IOS images can be downloaded from Cisco Connection Online (CCO). Each Cisco uBR900 series router in your network can then be configured to support Voice over IP (VoIP) and/or other special operating modes based on your service offering and the practices in place for your network. A Cisco uBR900 series device can function as an advanced router, providing wide area network (WAN) data connectivity in a variety of configurations.
Cisco IOS Software Feature Sets
This section briefly describes the common feature sets supported by the Cisco uBR900 series cable access routers. Each feature set contains a number of features that provide a specific functionality such as Voice over IP (VoIP) or virtual private network (VPN) access.
The following feature set categories are currently available:
•
•
The data and voice feature sets add Voice over IP (VoIP) support to the same base features contained in the data only feature sets. Telephones that are connected to the uBR924 cable access router can make voice calls over the Internet using either the H.323 (Gateway/Gatekeeper) voice control protocol or Simple Gateway Control Protocol (SGCP). (For more information on these protocols, refer to H.323 Protocol Stack and SGCP Protocol Stack in this document.)
Because voice calls are real-time traffic, the Cisco uBR924 cable access router supports the DOCSIS Quality of Service (QoS) enhancements to give higher priority to IP packets containing voice traffic.
Note
Note
The following feature sets are available in data and voice versions as well as in data only versions:
•
•
•
•
These feature sets are described in the following sections.
Base IP Bridging
Base IP Bridging includes full and DOCSIS-compliant bridging and DOCSIS Baseline Privacy. The Base IP Bridging feature set allows the Cisco uBR900 series cable access router to function as a DOCSIS 1.0 cable modem and to interoperate with any DOCSIS 1.0-qualified CMTS. It provides basic high-speed Internet connectivity for users who want to connect only one computer to the cable network.
DOCSIS-compliant bridging (also referred to as "plug-and-play" bridging) is the default configuration for Cisco uBR900 series cable access routers. While in plug-and-play bridging mode, the router locates a downstream and upstream channel; finds ToD, TFTP, and DHCP servers; obtains an IP address; downloads a DOCSIS configuration file; and obtains DHCP parameters to work in bridging mode.
Note
In DOCSIS-compliant bridging mode, the Cisco uBR900 series cable access router acts as a transparent bridge for the following device combinations:
•
•
Note
Home Office (Easy IP)
The Home Office feature set provides high-speed Internet connectivity for customers who have a small home network (typically 2-4 computers). In addition to full DOCSIS 1.0 support and all of the functionality of the Base IP Bridging feature set, the Home Office feature set (also known as Easy IP) supports intelligent Dynamic Host Configuration Protocol (DHCP) server functions, including DHCP Relay Agent and DHCP Client functionality. It also supports Easy IP (NAT/PAT).
This feature set allows the Cisco uBR900 series cable access router great flexibility in administering IP addresses for the PCs and other customer premises equipment it is connecting to the cable network. The DHCP functionality allows intelligent use of the IP addresses that allow customer premises computers and other equipment to connect to the Internet. The NAT/PAT functionality allows you to use private IP addresses on the local network, while still maintaining connectivity to the Internet.
Small Office
In addition to full DOCSIS 1.0 support and all of the functionality of the Easy IP feature set, the Small Office feature set supports the Cisco IOS firewall feature set which provides a wide range of security features for Cisco uBR900 series cable access routers. Using the firewall feature set, Cisco uBR900 series cable access routers act as buffers between the customer's private enterprise network and the Internet and other connected public networks.
In firewall mode, the Cisco uBR900 series cable access router provides a high-speed Internet connection for an office's local network while protecting the computers on the office network from common attacks such as denial of service attacks and destructive Java applets, as well as real-time alerts of such attacks.
The Small Office feature set can be optionally extended with support for IPSec encryption to ensure that the traffic passed over the Internet cannot be intercepted. You can select either standard 56-bit IPSec Network Security encryption or high-security 168-bit Triple Data Encryption Standard (DES) encryption.
Telecommuter
In addition to full DOCSIS 1.0 support and all of the functionality of the Easy IP feature set, the Telecommuter feature set supports IPSec encryption and the Layer 2 Tunneling Protocol (L2TP), which can establish secure high-speed Internet connections between employees' homes and the office local network.
IPSec is an IP security feature that provides robust authentications and encryption of IP packets for the secure transmission of sensitive information over unprotected networks such as the Internet. You can select either standard 56-bit IPSec Network Security encryption or high-security 168-bit Triple Data Encryption Standard (DES) encryption.
L2TP is an extension of the Point-to-Point Protocol (PPP) that allows computers on different physical networks to interoperate as if they were on the same local area network (LAN). These features are important components for Virtual Private Networks (VPNs).
Note
Data Operations
illustrates a typical broadband data cable system. Data transmitted to a Cisco uBR900 series cable access router from the service provider's CMTS shares a 27 or 26 Mbps, 6 MHz data channel in the 88 to 860 MHz range. The Cisco uBR900 series cable access router shares an upstream data rate of up to 10 Mbps on a 200 kHz-wide to 3.2 MHz-wide channel in the 5 to 42 MHz range.
Note
Figure 1 Typical Cisco Broadband Data Cable System
Operating Modes
The broadband data cable system uses multiple types of access control to ensure efficient use of bandwidth over a wide range of loading conditions. Advanced queuing techniques and service algorithms are used to define the acquisition and release of channels.
Cisco uBR900 series cable access routers support 64 or 256 Quadrature Amplitude Modulation (QAM) downstream, and Quadrature Phase Shift Keying (QPSK) or 16 QAM upstream transmission. This allows the CMTS system administrator to set the preferred modulation scheme based on the quality of the cable plant.
Note
The system uses Transmission Control Protocol/Internet Protocol (TCP/IP) to transmit data. TCP/IP transmits data in segments encased in IP datagrams, along with checksums to detect data corruption and sequence numbers to ensure an ordered byte stream on the TCP connection between the Cisco cable access router and the CMTS.
Cisco cable access routers also support multicast services—data streams sent to groups of subscribers. These applications utilize the User Datagram Protocol (UDP) instead of TCP. Since UDP does not mandate upstream acknowledgments, these applications can be very efficient in the network. Additionally, restricting upstream throughput will have no effect on downstream UDP streaming throughput.
Note
Data Specifications
Service Assignments
Each Cisco uBR900 series cable access router on the network is configured to receive data on a particular downstream channel. A downstream channel contains upstream segment(s). Each upstream segment typically serves more than one fiber node.
Partitioning the upstream plant into smaller segments significantly reduces the number of potential ingress sources and failure points. The CMTS divides the cable plant into downstream channels and upstream segments or clusters of nodes.
Downstream and Upstream Data Transfer
When operating normally, the Cisco uBR900 series cable access router receives data addressed to it from the CMTS. The router reads the address in the header of the message, filters the message and forwards it to the appropriate device at the subscriber site.
Note
For upstream data transfer, the Cisco cable access router uses a request/grant mechanism to obtain upstream bandwidth. The CMTS configures, via MAC messages, upstream parameters associated with transmissions from all Cisco cable access routers on the system. Service class registration is granted based on class assignment and load provisioning. Upstream channels are time slotted and divided into basic scheduling time units.
The CMTS informs the Cisco cable access router of minislot structures on the upstream channel. Some minislots are marked as contention-based—shared by routers to make bandwidth (timeslot) requests with the CMTS. Others are grouped together into unicast grants for specific routers to send their data bursts. Yet others are grouped together into maintenance slots for "keep alive" messages from routers to the CMTS.
Bridging Applications
In bridging applications, the Cisco uBR900 series cable access router acts as a transparent bridge for up to 254 devices depending on the version of Cisco IOS software you are using. Older versions of software allow a maximum of 3 CPE devices to be bridged. The cable access router is connected to the Internet through the coaxial cable interface. All four 10BaseT Ethernet ports are treated as one Ethernet interface by the Cisco IOS software. The IP addresses for the CPE devices and the coaxial cable interface are typically in the same subnet, although this is not a requirement.
The Cisco uBR900 series complies with the DOCSIS standards for interoperable cable access routers; it supports full transparent bridging as well as DOCSIS-compliant transparent bridging.
Note
Figure 2 Cisco uBR900 Series Cable Access Router in a Bridging Configuration
DOCSIS-compliant transparent bridging is the factory default configuration of the Cisco uBR900 series cable access router. If your cable service provider is using a DHCP server, all you need to do is connect the cables and power on the cable access router; your service provider's configuration program will automatically configure both the coaxial cable interface and the bridging functionality. You do not need to set up IP addresses for the attached PCs or enter any Command Line Interface (CLI) configuration commands. This type of operation is called plug-and-play bridging.
In DOCSIS-compliant bridging mode, the cable access router is able to locate a downstream and upstream channel; find the TOD, TFTP, and DHCP server(s); obtain an IP address; download a DOCSIS configuration file; and obtain DHCP parameters to work in a bridging mode.
You can configure a customized bridging application on the Cisco uBR900 series using a downloadable configuration file or the CLI. See the sections "Configuring Bridging" on page 41 and "Customizing the Cable Access Router Interface" on page 44 for details.
Routing Applications
The Cisco uBR900 series cable access router can be configured to act as a router to preserve IP address space and limit broadcasts that can impact the performance of the network. A typical use would be if you are connecting the cable access router to an internal Ethernet hub that is connected to an existing PC network. The Cisco uBR900 series supports Routing Information Protocol Version 2 (RIP V2) for this application.
When configured in routing mode, the Cisco uBR900 series is automatically configured to use the headend's IP address as its IP default gateway. This allows the cable access router to send packets not intended for the Ethernet interface to the headend when IP host-routing is configured.
RIP V2 routing is useful for small internetworks in that it enables optimization of Network Interface Center (NIC)-assigned IP addresses by defining variable-length subnet masks (VLSMs) for network addresses, and it allows classless interdomain routing (CIDR) addressing schema.
Figure 3 Cisco uBR900 Series Cable Access Router in a Routing Configuration with a Hub
Layer 2 Tunneling Protocol
Layer 2 Tunneling Protocol (L2TP) is an emerging Internet Engineering Task Force (IETF) standard that combines the best features of two existing tunneling protocols: Cisco's Layer 2 Forwarding (L2F) and Microsoft's Point-to-Point Tunneling Protocol (PPTP). L2TP is an extension of the Point-to-Point Protocol (PPP), which is an important component for Access Virtual Private Networks (VPNs).
Traditional dial-up networking services only supported registered IP addresses, which limited the types of applications that could be implemented over VPNs. L2TP supports multiple protocols and unregistered and privately administered IP addresses over the Internet. This allows the existing access infrastructure such as the Internet, modems, access servers, and ISDN terminal adapters (TAs) to be used.
L2TP can be initiated wherever PPTP or L2F is currently deployed, and can be operated as a client initiated tunnel such as PPTP, or a network access server (NAS) initiated tunnel such as L2F.
The current implementation of L2TP in Cisco IOS software is dependent on a PPP connection supported on one of the directly attached interfaces. A dial-up PPP connection is required in order to initiate an L2TP Tunnel connection. This is a requirement of the L2TP Access Concentrator (LAC). Currently the Cisco uBR900 series cable access router cannot function as the LAC; it can only function as the L2TP Network Server (LNS), which terminates a tunnel created elsewhere in the network.
Easy IP
Dynamic Host Configuration Protocol (DHCP) Server
Cisco uBR900 series cable access routers support Intelligent DHCP Relay and DHCP Client functionality. A DHCP Relay Agent is any host that forwards DHCP packets between clients and servers. A DHCP Relay Agent enables the client and server to reside on separate subnets. If the Cisco IOS DHCP server cannot satisfy a DHCP request from its own database, it can forward the DHCP request to one or more secondary DHCP servers defined by the network administrator using standard Cisco IOS IP helper-address functionality.
Network Address Translation and Port Address Translation (NAT/PAT)
Network Address Translation (NAT) reduces the need for globally unique IP addresses. NAT allows an organization with addresses that are not globally unique to connect to the Internet by translating those addresses into globally routable address space.
Port Address Translation (PAT) is a similar mechanism that enables all internal hosts to share a single registered IP address (many-to-one translation). NAT/PAT:
•
•
•
•
•
•
Routing protocols will run on the Ethernet interface instead of the cable interface, and all packets received are translated to the correct private network IP address and routed out the Ethernet interface. This eliminates the need to run RIP on the cable interface.
To implement NAT on the Cisco uBR900 series, the Ethernet interface is configured with an "inside" address and the cable interface is configured with an "outside" address. The Cisco uBR900 series also supports configuration of static connections, dynamic connections, and address pools.
Voice Over IP Operations
Note
The Cisco uBR924 cable access router uses packets to transmit and receive digitized voice over an IP network. Voice signals are packetized and transported in compliance with H.323 or Simple Gateway Control Protocol (SGCP). H.323 is an International Telecommunications Union (ITU) standard that specifies call signaling and control protocols for a shared IP data network. SGCP is a Cisco/Bellcore-developed, out-of-band signaling protocol under review by the Internet Engineering Task Force (IETF).
illustrates a broadband cable system that supports VoIP transmission. Quality of Service (QoS) and prioritization schemes are used to enable real-time (voice) and non-real-time traffic to coexist on the same channel. The CMTS routes IP telephony calls intermixed with other data traffic.
Figure 4 Simplified VoIP Over Cable Network
Your company can then deploy IP telephony as a local-loop bypass service where voice packets are transferred from the CMTS to:
•
•
The gatekeeper or call agents manage voice calls. The gateway interconnects the IP network to the public switched telephone network (PSTN).
Voice calls are digitized, encoded, compressed, and packetized in the originating gateway, then decompressed, decoded, and reassembled in the destination gateway. A server maintains subscriber profiles and policy information.
You can place and receive calls without using the local exchange carrier. Two simultaneous voice and fax calls are supported to and from each subscriber site. Multiple telephones and fax devices can be connected to each of the two VoIP telephone lines at a subscriber site, providing the 5 REN limit is adhered to for each telephone line.
Note the following requirements and characteristics of VoIP applications using the Cisco uBR924 cable access router:
•
•
•
•
•
Contact your network management, provisioning, or operations team to determine what your network supports.
Voice Handling
The Cisco uBR924 cable access router supports the following compression and decompression algorithms (CODECs):
•
•
•
•
•
•
•
•
•
•
CautionBecause voice transmission is delay-sensitive, a well-engineered network is critical. Fine-tuning your network to adequately support VoIP typically involves a series of protocols and features geared to support Quality of Service (QoS).
To achieve acceptable voice quality and reduce network bandwidth usage, several voice processing techniques and services are employed, including echo cancellation, voice compression, Voice Activity Detection (VAD) or silence compression, and Dual Tone Multi- Frequency (DTMF) tone detection and generation.
The Cisco uBR924 cable access router supports multiple QoS service IDs (SIDs), enabling multiple classes of service on the cable interface. This enables VoIP and data traffic to be treated separately, with all data assigned to a default class of service, while VoIP traffic is assigned to a different class of service. Thus, voice traffic from the Cisco uBR924's telephone ports can take precedence over the data traffic coming from the Ethernet interfaces.
Note
If the Cisco uBR924 interoperates with a DOCSIS 1.0 CMTS that does not support multiple CoS per router, voice traffic will be transmitted on a "best effort" basis along with data traffic. This may cause poorer voice quality and lower data throughput when calls are being made from the router's telephone ports.The Cisco uBR924 cable access router supports the following service classes:
•
This service class results in the assignment of a primary SID for the router. In addition to being used as a data SID, the router uses this SID for all MAC message exchanges with the CMTS. Any SNMP management traffic from the network to the Cisco uBR924 will also use this SID.
While this class is strictly "best effort," data traffic within this class can be prioritized into eight different priority levels. The CMTS system administrator, however, must define the supported upstream traffic priority levels and include the traffic priority fields in the configuration file downloaded to the Cisco uBR924.
•
The multiple SID-per-router feature enables the Cisco uBR924 to use multiple SID queues for differentiated services. The Cisco uBR924 diverts voice call traffic to the higher QoS secondary SID, while forwarding "best effort" data from the Ethernet interface and MAC messages on the primary SID.
H.323 Protocol Stack
H.323 is an International Telecommunications Union (ITU) standard that specifies call signaling and control protocols for a shared IP data network. The Cisco uBR924 cable access router acts as an H.323 gateway. In architectures using the VoIP H.323 protocol stack, the session application manages two call legs for each call: (1) a telephony leg managed by the voice telephony service provider; (2) the VoIP leg managed by the cable system operator—the VoIP service provider. Use of the H.323 protocol typically requires a dial plan and mapper at the headend or other server location to map IP addresses to telephone numbers.
When both legs of the call have been set up, the session application creates a conference between them. The opposite leg's transmit routine for voice packets is given to each provider. The CMTS router passes data to the gateway and gatekeeper. The H.323 stack provides signalling via H.225 and feature negotiation via H.245.
To make and receive H.323 calls, the Cisco uBR924 cable access router must know:
•
•
Note
SGCP Protocol Stack
The Cisco uBR924 cable access router supports Simple Gateway Control Protocol (SGCP), an out-of-band signaling protocol that interacts with an external call agent (CA) to provide call setup and teardown for VoIP calls made through the Internet or a local intranet. Using the call control agent, SGCP communicates with the voice gateways, allowing you to create a distributed system that enhances performance, reliability, and scalability while still appearing as a single VoIP gateway to external clients. SGCP eliminates the need for a dial plan mapper and static configuration on the router to map IP addresses to telephone numbers because this function is provided by the external call agent.
In architectures using the SGCP protocol stack, the session application implements the gateway functionality defined to support both trunk and residential gateways. The Cisco uBR924 functions in this mode as a residential gateway with two endpoints.
SGCP can preserve Signaling System 7 (SS7) style call control information as well as additional network information such as routing information and authentication, authorization, and accounting (AAA) security information. SGCP allows voice calls to originate and terminate on the Internet, as well as allowing one end to terminate on the Internet and the other to terminate on a telephone or PBX on the PSTN.
Note
Voice Specifications
Backup POTS Connection
The Cisco uBR924 cable access router provides an RJ-11 port (Line) that connects to a standard analog telephone wall jack. In the event of a building power failure or a Cisco uBR924 power problem, the cutover port lets you dial out using the backup PSTN line. If the Cisco uBR924 loses power while VoIP calls are in progress, you can reestablish one of the two connections—dialing out over the PSTN.
Note
Security Features
Cisco uBR900 series cable access routers support the security features described in the paragraphs below.
DOCSIS Baseline Privacy
Support for DOCSIS Baseline Privacy in the Cisco uBR900 series is based on the DOCSIS Baseline Privacy Interface Specification (SP-BPI-I01-970922). It provides data privacy across the HFC network by encrypting traffic flows between the cable access router and the CMTS.
Baseline Privacy security services are defined as a set of extended services within the DOCSIS MAC sublayer. Two new MAC management message types, BPKM-REQ and BPKM-RSP, are employed to support the Baseline Privacy Key Management (BPKM) protocol.
The BPKM protocol does not use authentication mechanisms such as passwords or digital signatures; it provides basic protection of service by ensuring that a cable modem, uniquely identified by its 48-bit IEEE MAC address, can only obtain keying material for services it is authorized to access. The Cisco uBR900 series cable access router is able to obtain two types of keys from the CMTS: the Traffic Exchange Key (TEK), which is used to encrypt and decrypt data packets, and the Key Exchange Key (KEK), which is used to decrypt the TEK.
IPSec Network Security
IPSec Network Security (IPSec) is an IP security feature that provides robust authentication and encryption of IP packets. IPSec is a framework of open standards developed by the Internet Engineering Task Force (IETF) providing security for transmission of sensitive information over unprotected networks such as the Internet. IPSec acts at the network layer (Layer 3), protecting and authenticating IP packets between participating IPSec devices ("peers") such as the Cisco uBR900 series cable access router.
IPSec provides the following network security services:
•
•
•
•
Triple Data Encryption Standard
The Data Encryption Standard (DES) is a standard cryptographic algorithm developed by the United States National Bureau of Standards. The Triple DES (3DES) Cisco IOS Software Release images increase the security from the standard 56-bit IPSec encryption to 168-bit encryption, which is used for highly sensitive and confidential information such as financial transactions and medical records.
Firewall
Cisco uBR900 series cable access routers act as buffers between any connected public and private networks. In firewall mode, Cisco cable access routers use access lists and other methods to ensure the security of the private network.
Cisco IOS firewall-specific security features include:
•
•
•
•
•
•
•
•
For additional information, see the description of the Cisco IOS Firewall Feature Set in the Cisco Product Catalog, or refer to the sections on Traffic Filtering and Firewalls in the Security Configuration Guide and Security Command Reference available on Cisco Connection Online (CCO) and the Documentation CD-ROM.
NetRanger Support—IOS Intrusion Detection
NetRanger is an Intrusion Detection System (IDS) composed of three parts:
•
•
•
Configuration Options
The Cisco uBR900 series cable access router typically ships from the factory ready to work in the Base IP Bridging (DOCSIS-compliant bridging) data-only mode. The cable access router is configured automatically at startup by one or more configuration files generated by the cable service provider and downloaded to the router; no configuration or setup is required other than to connect the router to the cable system. The CMTS provides a path from the cable access router to the DHCP server for PC address assignment.
The PCs connected to the Cisco uBR900 series must be configured for Internet Protocol (IP). Using DHCP, the CMTS assigns an IP subnet address to the cable access router each time it connects to the network. The IP addresses of the cable access router and the individual PCs attached to it enable the CMTS to route data to and from the PCs.
Note
The configuration file or files downloaded to the Cisco uBR900 series by the CMTS at the headend are dependent on the services purchased by the individual cable service subscriber. The cable access router is provisioned in the following manner:
•
•
•
Note
To ensure that you obtain the exact services that you have ordered, the Cisco uBR900 series arrives from the factory with a unique identifier (UID) that consists of a serial number and MAC address. These factory-assigned values are on a label at the bottom of the cable access router; for convenience, these values are also in a barcode label that can be easily scanned for entry into the service provider's provisioning and billing system.
Using the MAC address of the cable access router as the key, the CMTS downloads the DOCSIS configuration file and Cisco IOS image that will provide the services that you have purchased. Service technicians at the headend typically create a number of standard configuration files to match the range of services offered by the provider; these configuration files can be created manually or with tools provided for this purpose by Cisco Systems.
The following sections describe the initial power-on and provisioning sequences in more detail, as well as the requirements that must be met by both the cable access router and the CMTS before provisioning can be successful.
Initial Power-On Sequence
When connected and first powered on, the Cisco uBR900 series cable access router performs the following boot procedures:
•
•
Next, the Cisco uBR900 series performs a series of DOCSIS-mandated procedures for automatic installation and configuration. These procedures are summarized in and in .
.
At this point the router is online and operational in the basic DOCSIS bridging ("plug and play") mode. If the DOCSIS configuration file specifies that the router must download a Cisco IOS image and a Cisco IOS configuration file, the router uses TFTP to download the image and configuration file into its local memory. It then installs the new IOS image and runs the configuration file.
Downloading a DOCSIS configuration file to a Cisco uBR900 series cable access router automatically:
•
•
•
Telnet access to the router from the headend is still allowed, but only if the Cisco IOS configuration file includes enable and line vty passwords; if the configuration file does not include enable and line vty commands to specify these passwords, Telnet access and console access are both disabled.
The sequence numbers shown in are also shown in below. The Cisco uBR900 series cable access router will complete all the steps shown in the table and flowchart each time it needs to reregister with the CMTS.
Figure 5 Cable Modem Initialization Flowchart
illustrates the traffic flow during the initialization process.
Figure 6
Cisco uBR900 Series Cable Access Router Provisioning Overview
Note
After the Cisco uBR900 series cable access router goes online, it begins transferring data between the attached CPE devices and the network (internet, intranet, VoIP). The cable service provider typically uses DHCP to assign IP addresses to the CPE devices. The number of IP addresses each subscriber can obtain depends on the services purchased from the provider.
Basic Troubleshooting
A MAC-layer circular log file is stored inside the Cisco uBR900 series cable access router. This file contains a history of the log messages such as state event activities and timestamps. This is the most valuable information for troubleshooting the cable interface.
The MAC log file is displayed by entering the show controllers cable-modem 0 mac log command from privileged EXEC mode.
The most useful display fields in this output are the reported state changes. These fields are preceded by the message CMAC_LOG_STATE_CHANGE. These fields show how the Cisco uBR900 series progresses through the various processes involved in establishing communication and registration with the CMTS. The normal operational state is maintenance_state ; the normal state when the interface is shut down is wait_for_link_up_state.
Note
The following is the normal progression of states as the Cisco uBR900 series registers with the CMTS:
wait_for_link_up_stateds_channel_scanning_statewait_ucd_statewait_map_stateranging_1_stateranging_2_statedhcp_stateestablish_tod_statesecurity_association_stateconfiguration_file_stateregistration_stateestablish_privacy_statemaintenance_stateFollowing is an example of a MAC log file for a cable access router that has successfully registered with the headend CMTS. The output that is displayed is directly related to the messages that are exchanged between the Cisco uBR900 series and the CMTS.
uBR924# show controllers cable-modem 0 mac log508144.340 CMAC_LOG_DRIVER_INIT_IDB_RESET 0x08098FEA508144.342 CMAC_LOG_LINK_DOWN508144.344 CMAC_LOG_LINK_UP508144.348 CMAC_LOG_STATE_CHANGE ds_channel_scanning_state508144.350 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 88/453000000/855000000/6000000508144.354 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 89/93000000/105000000/6000000508144.356 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 90/111250000/117250000/6000000508144.360 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 91/231012500/327012500/6000000508144.362 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 92/333015000/333015000/6000000508144.366 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 93/339012500/399012500/6000000508144.370 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 94/405000000/447000000/6000000508144.372 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 95/123015000/129015000/6000000508144.376 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 96/135012500/135012500/6000000508144.380 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 97/141000000/171000000/6000000508144.382 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 98/219000000/225000000/6000000508144.386 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 99/177000000/213000000/6000000508144.390 CMAC_LOG_WILL_SEARCH_SAVED_DS_FREQUENCY 699000000508145.540 CMAC_LOG_UCD_MSG_RCVD 3508146.120 CMAC_LOG_DS_64QAM_LOCK_ACQUIRED 699000000508146.122 CMAC_LOG_DS_CHANNEL_SCAN_COMPLETED508146.124 CMAC_LOG_STATE_CHANGE wait_ucd_state508147.554 CMAC_LOG_UCD_MSG_RCVD 3508147.558 CMAC_LOG_UCD_NEW_US_FREQUENCY 20000000508147.558 CMAC_LOG_SLOT_SIZE_CHANGED 8508147.622 CMAC_LOG_FOUND_US_CHANNEL 1508147.624 CMAC_LOG_STATE_CHANGE wait_map_state508148.058 CMAC_LOG_MAP_MSG_RCVD508148.060 CMAC_LOG_INITIAL_RANGING_MINISLOTS 40508148.062 CMAC_LOG_STATE_CHANGE ranging_1_state508148.064 CMAC_LOG_RANGING_OFFSET_SET_TO 9610508148.066 CMAC_LOG_POWER_LEVEL_IS 28.0 dBmV (commanded)508148.068 CMAC_LOG_STARTING_RANGING508148.070 CMAC_LOG_RANGING_BACKOFF_SET 0508148.072 CMAC_LOG_RNG_REQ_QUEUED 0508148.562 CMAC_LOG_RNG_REQ_TRANSMITTED508148.566 CMAC_LOG_RNG_RSP_MSG_RCVD508148.568 CMAC_LOG_RNG_RSP_SID_ASSIGNED 2508148.570 CMAC_LOG_ADJUST_RANGING_OFFSET 2408508148.572 CMAC_LOG_RANGING_OFFSET_SET_TO 12018508148.574 CMAC_LOG_ADJUST_TX_POWER 20508148.576 CMAC_LOG_POWER_LEVEL_IS 33.0 dBmV (commanded)508148.578 CMAC_LOG_STATE_CHANGE ranging_2_state508148.580 CMAC_LOG_RNG_REQ_QUEUED 2508155.820 CMAC_LOG_RNG_REQ_TRANSMITTED508155.824 CMAC_LOG_RNG_RSP_MSG_RCVD508155.826 CMAC_LOG_ADJUST_RANGING_OFFSET -64508155.826 CMAC_LOG_RANGING_OFFSET_SET_TO 11954508155.828 CMAC_LOG_RANGING_CONTINUE508165.892 CMAC_LOG_RNG_REQ_TRANSMITTED508165.894 CMAC_LOG_RNG_RSP_MSG_RCVD508165.896 CMAC_LOG_ADJUST_TX_POWER -9508165.898 CMAC_LOG_POWER_LEVEL_IS 31.0 dBmV (commanded)508165.900 CMAC_LOG_RANGING_CONTINUE508175.962 CMAC_LOG_RNG_REQ_TRANSMITTED508175.964 CMAC_LOG_RNG_RSP_MSG_RCVD508175.966 CMAC_LOG_RANGING_SUCCESS508175.968 CMAC_LOG_STATE_CHANGE dhcp_state508176.982 CMAC_LOG_DHCP_ASSIGNED_IP_ADDRESS 188.188.1.62508176.984 CMAC_LOG_DHCP_TFTP_SERVER_ADDRESS 4.0.0.1508176.986 CMAC_LOG_DHCP_TOD_SERVER_ADDRESS 4.0.0.32508176.988 CMAC_LOG_DHCP_SET_GATEWAY_ADDRESS508176.988 CMAC_LOG_DHCP_TZ_OFFSET 360508176.990 CMAC_LOG_DHCP_CONFIG_FILE_NAME platinum.cm508176.992 CMAC_LOG_DHCP_ERROR_ACQUIRING_SEC_SVR_ADDR508176.996 CMAC_LOG_DHCP_COMPLETE508177.120 CMAC_LOG_STATE_CHANGE establish_tod_state508177.126 CMAC_LOG_TOD_REQUEST_SENT508177.154 CMAC_LOG_TOD_REPLY_RECEIVED 3107617539508177.158 CMAC_LOG_TOD_COMPLETE508177.160 CMAC_LOG_STATE_CHANGE security_association_state508177.162 CMAC_LOG_SECURITY_BYPASSED508177.164 CMAC_LOG_STATE_CHANGE configuration_file_state508177.166 CMAC_LOG_LOADING_CONFIG_FILE platinum.cm508178.280 CMAC_LOG_CONFIG_FILE_PROCESS_COMPLETE508178.300 CMAC_LOG_STATE_CHANGE registration_state508178.302 CMAC_LOG_REG_REQ_MSG_QUEUED508178.306 CMAC_LOG_REG_REQ_TRANSMITTED508178.310 CMAC_LOG_REG_RSP_MSG_RCVD508178.312 CMAC_LOG_COS_ASSIGNED_SID 5/19508178.314 CMAC_LOG_COS_ASSIGNED_SID 6/20508178.316 CMAC_LOG_COS_ASSIGNED_SID 7/21508178.318 CMAC_LOG_RNG_REQ_QUEUED 19508178.320 CMAC_LOG_REGISTRATION_OK508178.322 CMAC_LOG_REG_RSP_ACK_MSG_QUEUED 0508178.324 CMAC_LOG_STATE_CHANGE establish_privacy_state508178.326 CMAC_LOG_NO_PRIVACY508178.328 CMAC_LOG_STATE_CHANGE maintenance_stateYou can display other aspects of the MAC layer by adding the following keywords to the show controllers cable-modem 0 mac command:
uBR924# show controllers cable-modem 0 mac ?errors Mac Error Log datahardware All CM Mac Hardware registerslog Mac log dataresets Resets of the MACstate Current MAC stateFor examples and descriptions of how to use these keywords, see the show controllers cable-modem mac command reference page.
The MAC log file gives a detailed history of initialization events that occur in the Cisco uBR900 series cable access router. All pertinent troubleshooting information is stored here.
In the following paragraphs, a sample log file is broken down into the chronological sequence of events listed below. Sample comments are also included in the log file.
•
•
•
•
•
•
•
•
•
Event 1—Wait for the Link to Come Up
When the Cisco uBR900 series cable access router is powered on and begins initialization, the MAC layer first informs the cable access router drivers that it needs to reset. The LINK_DOWN and LINK_UP fields are similar to the shut and no shut conditions on a standard Cisco interface.
uBR924# show controllers cable-modem 0 mac log528302.040 CMAC_LOG_LINK_DOWN528302.042 CMAC_LOG_RESET_FROM_DRIVER528302.044 CMAC_LOG_STATE_CHANGE wait_for_link_up_state528302.046 CMAC_LOG_DRIVER_INIT_IDB_SHUTDOWN 0x08098D02528302.048 CMAC_LOG_LINK_DOWN528308.428 CMAC_LOG_DRIVER_INIT_IDB_RESET 0x08098E5E528308.432 CMAC_LOG_LINK_DOWN528308.434 CMAC_LOG_LINK_UPEvent 2—Scan for a Downstream Channel, then Synchronize
Different geographical regions and different cable plants use different RF frequency bands. A frequency band is a group of adjacent 6 MHz-wide channels. These bands are numbered from 88 to 99. Each band has starting and ending digital carrier frequencies and a 6 MHz step size. For example, a search of EIA channels 95-97 is specified using band 89. The starting frequency of band 89 is 93 MHz; the ending frequency is 105 MHz.
The Cisco uBR900 series' default frequency bands correspond to the North American EIA CATV channel plan for 6 MHz channel slots between 90 and 858 MHz. For example, EIA channel 95 occupies the 90-96 MHz slot. The digital carrier frequency is specified as the center frequency of the slot, which is 93 MHz. Channel 95 is usually specified using the analog video carrier frequency of 91.25 MHz, which lies 1.75 MHz below the center of the slot.
Some CATV systems use alternative frequency plans such as the IRC (Incrementally Related Carrier) plan and HRC (Harmonically Related Carrier) plan. Cisco uBR900 series cable access routers support both of these plans. Most of the IRC channel slots overlap the EIA plan.
The Cisco uBR900 series uses a built-in default frequency scanning feature to find and lock onto a downstream channel. After the cable access router successfully finds a downstream frequency channel, it saves the channel to NVRAM. The router recalls this value the next time it needs to synchronize its frequency.
The downstream frequency search table is arranged so that the first frequencies that are scanned are above 450 MHz. Because many CATV systems have been upgraded from 450 MHz to 750 MHz coaxial cable, digital channels have a high chance of being assigned in the new spectrum. The search table omits channels below 90 MHz and above 860 MHz since the DOCSIS specification does not mandate their coverage.
The CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND field tells you what frequencies the cable access router will scan. The CMAC_LOG_WILL_SEARCH_SAVED_DS_FREQUENCY field tells you the frequency the router locked onto and saved to NVRAM for future recall. The CMAC_LOG_DS_64QAM_LOCK_ACQUIRED field communicates the same information. The CMAC_LOG_DS_CHANNEL_SCAN_COMPLETED field indicates that the scanning and synchronization was successful.
508144.348 CMAC_LOG_STATE_CHANGE ds_channel_scanning_state508144.350 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 88/453000000/855000000/6000000508144.354 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 89/93000000/105000000/6000000508144.356 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 90/111250000/117250000/6000000508144.360 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 91/231012500/327012500/6000000508144.362 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 92/333015000/333015000/6000000508144.366 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 93/339012500/399012500/6000000508144.370 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 94/405000000/447000000/6000000508144.372 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 95/123015000/129015000/6000000508144.376 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 96/135012500/135012500/6000000508144.380 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 97/141000000/171000000/6000000508144.382 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 98/219000000/225000000/6000000508144.386 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 99/177000000/213000000/6000000508144.390 CMAC_LOG_WILL_SEARCH_SAVED_DS_FREQUENCY 699000000508145.540 CMAC_LOG_UCD_MSG_RCVD 3508146.120 CMAC_LOG_DS_64QAM_LOCK_ACQUIRED 699000000508146.122 CMAC_LOG_DS_CHANNEL_SCAN_COMPLETEDEvent 3—Obtain Upstream Parameters
The Cisco uBR900 series waits for an upstream channel descriptor (UCD) message from the CMTS. The UCD provides transmission parameters for the upstream channel.
508146.124 CMAC_LOG_STATE_CHANGE wait_ucd_state508147.554 CMAC_LOG_UCD_MSG_RCVD 3508147.558 CMAC_LOG_UCD_NEW_US_FREQUENCY 20000000508147.558 CMAC_LOG_SLOT_SIZE_CHANGED 8508147.622 CMAC_LOG_FOUND_US_CHANNEL 1508147.624 CMAC_LOG_STATE_CHANGE wait_map_state508148.058 CMAC_LOG_MAP_MSG_RCVD508148.060 CMAC_LOG_INITIAL_RANGING_MINISLOTS 40Event 4—Start Ranging for Power Adjustments
The ranging process adjusts the transmit power of the cable access router. Ranging is performed in two stages: ranging state 1 and ranging state 2.
The CMAC_LOG_POWER_LEVEL_IS field is the power level that the CMTS told the Cisco uBR900 series to adjust to. The CMAC_LOG_RANGING_SUCCESS field indicates that the ranging adjustment was successful.
508148.062 CMAC_LOG_STATE_CHANGE ranging_1_state508148.064 CMAC_LOG_RANGING_OFFSET_SET_TO 9610508148.066 CMAC_LOG_POWER_LEVEL_IS 28.0 dBmV (commanded)508148.068 CMAC_LOG_STARTING_RANGING508148.070 CMAC_LOG_RANGING_BACKOFF_SET 0508148.072 CMAC_LOG_RNG_REQ_QUEUED 0508148.562 CMAC_LOG_RNG_REQ_TRANSMITTED508148.566 CMAC_LOG_RNG_RSP_MSG_RCVD508148.568 CMAC_LOG_RNG_RSP_SID_ASSIGNED 2508148.570 CMAC_LOG_ADJUST_RANGING_OFFSET 2408508148.572 CMAC_LOG_RANGING_OFFSET_SET_TO 12018508148.574 CMAC_LOG_ADJUST_TX_POWER 20508148.576 CMAC_LOG_POWER_LEVEL_IS 33.0 dBmV (commanded)508148.578 CMAC_LOG_STATE_CHANGE ranging_2_state508148.580 CMAC_LOG_RNG_REQ_QUEUED 2508155.820 CMAC_LOG_RNG_REQ_TRANSMITTED508155.824 CMAC_LOG_RNG_RSP_MSG_RCVD508155.826 CMAC_LOG_ADJUST_RANGING_OFFSET -64508155.826 CMAC_LOG_RANGING_OFFSET_SET_TO 11954508155.828 CMAC_LOG_RANGING_CONTINUE508165.892 CMAC_LOG_RNG_REQ_TRANSMITTED508165.894 CMAC_LOG_RNG_RSP_MSG_RCVD508165.896 CMAC_LOG_ADJUST_TX_POWER -9508165.898 CMAC_LOG_POWER_LEVEL_IS 31.0 dBmV (commanded)508165.900 CMAC_LOG_RANGING_CONTINUE508175.962 CMAC_LOG_RNG_REQ_TRANSMITTED508175.964 CMAC_LOG_RNG_RSP_MSG_RCVD508175.966 CMAC_LOG_RANGING_SUCCESSEvent 5—Establish IP Connectivity
After ranging is complete, the cable interface on the cable access router is UP. Now the cable access router accesses a remote DHCP server to get an IP address. The DHCP server sends a response containing the router's IP address plus the TFTP server's address, the Time of Day (TOD) server's address, and the name of a configuration file containing additional configuration parameters. The CMAC_LOG_DHCP_COMPLETE field shows that the IP connectivity was successful.
508175.968 CMAC_LOG_STATE_CHANGE dhcp_state508176.982 CMAC_LOG_DHCP_ASSIGNED_IP_ADDRESS 188.188.1.62508176.984 CMAC_LOG_DHCP_TFTP_SERVER_ADDRESS 4.0.0.1508176.986 CMAC_LOG_DHCP_TOD_SERVER_ADDRESS 4.0.0.32508176.988 CMAC_LOG_DHCP_SET_GATEWAY_ADDRESS508176.988 CMAC_LOG_DHCP_TZ_OFFSET 360508176.990 CMAC_LOG_DHCP_CONFIG_FILE_NAME platinum.cm508176.992 CMAC_LOG_DHCP_ERROR_ACQUIRING_SEC_SVR_ADDR508176.996 CMAC_LOG_DHCP_COMPLETEEvent 6—Establish the Time of Day
The Cisco uBR900 series accesses the Time of Day server for the current date and time, which is used to create time stamps for logged events. The CMAC_LOG_TOD_COMPLETE field indicates a successful time of day sequence.
508177.120 CMAC_LOG_STATE_CHANGE establish_tod_state508177.126 CMAC_LOG_TOD_REQUEST_SENT508177.154 CMAC_LOG_TOD_REPLY_RECEIVED 3107617539508177.158 CMAC_LOG_TOD_COMPLETEEvent 7—Establish Security
This event is currently bypassed by the Cisco uBR900 series because "full security" has not been fully defined by DOCSIS and is therefore not yet supported.
508177.160 CMAC_LOG_STATE_CHANGE security_association_state508177.162 CMAC_LOG_SECURITY_BYPASSED
Note
Event 8—Transfer Operational Parameters
After completing the DHCP and security operations, the Cisco uBR900 series downloads operational parameters by downloading a configuration file located on the TFTP server. The CMAC_LOG_DHCP_CONFIG_FILE_NAME field shows the filename containing the transmission parameters.
508177.164 CMAC_LOG_STATE_CHANGE configuration_file_state508177.166 CMAC_LOG_LOADING_CONFIG_FILE platinum.cm508178.280 CMAC_LOG_CONFIG_FILE_PROCESS_COMPLETEEvent 9—Perform Registration
After the Cisco uBR900 series is initialized, authenticated, and configured, it requests to be registered with the headend CMTS. The CMAC_LOG_COS_ASSIGNED_SID field assigns a class of service (CoS) number and a service ID (SID). Multiple CoS entries in the configuration file imply that multiple SIDs are supported by the cable access router. If several cable access routers use the same configuration file, they will have the same CoS numbers but will be assigned different SIDs.
A successful registration is indicated by the CMAC_LOG_REGISTRATION_OK field.
508178.300 CMAC_LOG_STATE_CHANGE registration_state508178.302 CMAC_LOG_REG_REQ_MSG_QUEUED508178.306 CMAC_LOG_REG_REQ_TRANSMITTED508178.310 CMAC_LOG_REG_RSP_MSG_RCVD508178.312 CMAC_LOG_COS_ASSIGNED_SID 5/19508178.314 CMAC_LOG_COS_ASSIGNED_SID 6/20508178.316 CMAC_LOG_COS_ASSIGNED_SID 7/21508178.318 CMAC_LOG_RNG_REQ_QUEUED 19508178.320 CMAC_LOG_REGISTRATION_OKEvent 10—Comply with Baseline Privacy
During this event, keys for baseline privacy are exchanged between the Cisco uBR900 series and the headend CMTS. A link level encryption is performed so that your data cannot be "sniffed" by anyone else on the cable network.
Following is a trace showing baseline privacy enabled. The key management protocol is responsible for exchanging two types of keys: KEKs and TEKs. The KEK (key exchange key, also referred to as the authorization key) is used by the CMTS to encrypt the TEKs (traffic encryption keys) it sends to the Cisco uBR900 series. The TEKs are used to encrypt/decrypt the data. There is a TEK for each SID that is configured to use privacy.
851.088 CMAC_LOG_STATE_CHANGE establish_privacy_state851.094 CMAC_LOG_PRIVACY_FSM_STATE_CHANGE machine: KEK, event/state:EVENT_1_PROVISIONED/STATE_A_START, new state: STATE_B_AUTH_WAIT851.102 CMAC_LOG_BPKM_REQ_TRANSMITTED851.116 CMAC_LOG_BPKM_RSP_MSG_RCVD851.120 CMAC_LOG_PRIVACY_FSM_STATE_CHANGE machine: KEK, event/state:EVENT_3_AUTH_REPLY/STATE_B_AUTH_WAIT, new state: STATE_C_AUTHORIZED856.208 CMAC_LOG_PRIVACY_FSM_STATE_CHANGE machine: TEK, event/state:EVENT_2_AUTHORIZED/STATE_A_START, new state: STATE_B_OP_WAIT856.220 CMAC_LOG_BPKM_REQ_TRANSMITTED856.224 CMAC_LOG_BPKM_RSP_MSG_RCVD856.230 CMAC_LOG_PRIVACY_FSM_STATE_CHANGE machine: TEK, event/state:EVENT_8_KEY_REPLY/STATE_B_OP_WAIT, new state: STATE_D_OPERATIONAL856.326 CMAC_LOG_PRIVACY_INSTALLED_KEY_FOR_SID 2856.330 CMAC_LOG_PRIVACY_ESTABLISHED
Note
Event 11—Enter the Maintenance State
As soon as the Cisco uBR900 series has successfully completed the above events, it enters the operational maintenance state and is authorized to forward traffic into the cable network.
508178.322 CMAC_LOG_STATE_CHANGE maintenance_stateBenefits
The Cisco uBR900 series cable access router provides the following benefits for data-over-cable applications:
•
•
•
•
Restrictions
When using the Cisco uBR900 series cable access router, keep the following restrictions and limitations in mind:
•
•
Note
CautionBefore attempting to reconfigure a Cisco uBR900 series cable access router at a subscriber site, contact your network administrator, provisioning manager, or billing system administrator to ensure remote configuration is allowed. If remote configuration is disabled, settings you make and save at the local site will not remain in effect after the cable access router is powered off and back on. Instead, settings will return to the previous configuration.
Related Features and Technologies
The Cisco uBR900 series cable access router is intended to be used in conjunction with a Cisco uBR7246 or a Cisco uBR7223 universal broadband router located at the cable service provider's headend facility. Other compatible headend devices may also be used with the Cisco uBR900 series.
Related Documents
For related information on the Cisco uBR900 series cable access router, refer to the following documents:
· Quick Start Guide - Cisco uBR924 Cable Access Router Subscriber Setup· Quick Start Guide - Cisco uBR924 Cable Access Router Installation and Startup•
· Regulatory Compliance and Safety Information for the Cisco uBR924 Cable Access Router•
•
•
•
•
•
Supported Platforms
The Cisco uBR900 series cable access router is a standalone device; it works in conjunction with the Cisco uBR7246 and the Cisco uBR7223 universal broadband routers.
Prerequisites
In order to use the Cisco uBR900 series cable access router for data-over-cable or voice-over-cable (VoIP) applications, the following tasks must be completed:
•
•
•
•
Note
•
•
•
Note
Note
•
•
•
Note
In order to use the Cisco uBR900 series cable access router for VoIP-over-cable applications, the following additional conditions must be met:
•
Supported MIBs and RFCs
The Cisco uBR900 series cable access router supports the following categories of MIBs:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Cable-Specific MIBs
shows the cable-specific MIBs that are supported on the Cisco uBR900 series cable access router. This table also provides a brief description of each MIB's contents and the Cisco IOS software release in which the MIB was initially functional—earlier releases might have had unsupported prototype versions of the MIB; later releases might have added new attributes and functionality. Because of interdependencies, the MIBs must be loaded in the order given in the table.
Note
The Cisco uBR900 series cable access router also supports the following:
•
•
•
Products & Ordering: Cisco Products: Network Management: CiscoWorks•
Cisco Product Documentation: Network Management: CiscoWorks•
•
•
•
•
•
•
•
•
•
•
•
•
•
For descriptions of supported MIBs and how to use MIBs, see Cisco's MIB web site on CCO at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
Configuration Tasks
The Cisco uBR900 series cable access router typically is configured automatically on power-up using a configuration file generated by the cable service provider and delivered via the CMTS installed at the cable headend. All of the configuration tasks listed below are optional.
•
•
•
•
•
CautionBefore attempting to reconfigure a Cisco uBR900 series cable access router at a subscriber site, contact your network administrator, provisioning manager, or billing system administrator to ensure remote configuration is allowed. If remote configuration is disabled, settings you make and save at the local site will not remain in effect after the cable access router is powered off and back on. Instead, settings will return to the previous configuration.
Note
Configuring a Host Name and Password
One of the first configuration tasks you might want to perform is to configure a host name and set an encrypted password. Configuring a host name allows you to distinguish multiple Cisco uBR900 series cable access routers from each other. Setting an encrypted password allows you to prevent unauthorized configuration changes.
Note
To configure a host name and an encrypted password for a Cisco uBR900 series cable access router, perform the following tasks, starting in global configuration mode:
Verifying the Host Name and Password
To verify that you configured the correct host name and password, enter the show running-config command from global configuration mode:
cisco(config)# show running-configUsing 1888 out of 126968 bytes!version XX.X..!hostname cisco!enable secret 5 $1$60L4$X2JYOwoDc0.kqa1loO/w8/•
•
cisco# exitcisco con0 is now availablePress RETURN to get started.cisco> enablePassword: guessmecisco#Configuration, Verification, and Troubleshooting Tips
If you are having trouble:
•
•
Configuring Ethernet and Cable Access Router Interfaces
To assign an IP address to the Ethernet or cable access router interface so that it can be recognized as a device on the Ethernet LAN, perform the following tasks, starting in global configuration mode:
Verifying IP Address Configuration
To verify that you have assigned the correct IP address, enter the show arp command:
uBR924# show arpProtocol Address Age (min) Hardware Addr Type InterfaceInternet 172.16.1.1 - 0009.0613.6030 ARPA cable-modem0Internet 4.0.0.28 - 00e0.1ed7.524d ARPA Ethernet0Configuration, Verification, and Troubleshooting Tips
If you are having trouble:
•
•
Configuring Routing
DOCSIS-compliant transparent bridging is the factory default configuration of the Cisco uBR900 series cable access router. To change the configuration of your cable access router from bridging to routing using the CLI, perform the following tasks, starting in global configuration mode:
Verifying Routing
To verify that bridging is not configured, routing is enabled, and that Routing Information Protocol is configured on the interfaces, enter the show startup-config command:
uBR924# show startup-configBuilding configuration...Current configuration:!version 12.0no service padno service password-encryptionservice udp-small-serversservice tcp-small-servers!hostname uBR924!!clock timezone - 4ip subnet-zero!!!voice-port 0!voice-port 1!!interface Ethernet0ip address 10.1.0.33 255.255.0.0no ip directed-broadcastip rip send version 2ip rip receive version 2no keepalive!interface cable-modem0ip address 172.16.1.42 255.255.0.0no ip directed-broadcastip rip send version 2ip rip receive version 2no keepalivecable-modem downstream saved channel 699000000 39no cable-modem compliant bridge!router ripnetwork 4.0.0.0network 172.16.0.0!ip classlessno ip http server!line con 0transport input noneline vty 0 4!endConfiguring Bridging
The Cisco uBR900 series cable access router is configured for DOCSIS-compliant transparent bridging by default. If it becomes necessary to reconfigure the unit for bridging after it has been configured for routing, you can erase the routing configuration and return the unit to factory default configuration settings, or you can reconfigure the unit manually using the CLI. To return the cable access router to factory default settings, see the section "Reestablishing DOCSIS-Compliant Bridging" on page 43 for details. To reconfigure the cable access router manually, perform the following tasks, starting in global configuration mode:
When the cable interface comes up, the IP address and downstream channel are configured automatically.
Note
Verifying Bridging
To verify that routing has been disabled on all interfaces and that bridging has been reenabled, enter the show startup-config command from privileged EXEC mode:
uBR924# show startup-configBuilding configuration...Current configuration:!version 12.0service configno service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname uBR924!clock timezone - 4ip subnet-zerono ip routing!!voice-port 0!!voice-port 1!!interface Ethernet0no ip addressno ip directed-broadcastno ip route-cachebridge-group 59bridge-group 59 spanning-disabled!interface cable-modem0no ip addressno ip directed-broadcastno ip route-cacheno keepalivecable-modem downstream saved channel 699000000 36bridge-group 59bridge-group 59 spanning-disabled!ip classless!line con 0line vty 0 4login!endReestablishing DOCSIS-Compliant Bridging
To erase the current non-default cable access router configuration and return the unit to its factory default DOCSIS-compliant bridging configuration, perform the following task from privileged EXEC mode:
1
uBR924#erase startup config
Erase the current configuration (assuming the current running configuration has been saved to NVRAM).
After entering this command, perform a warm reset of the Cisco uBR900 series cable access router by pressing and holding down the Reset button for less than 10 seconds. For information on the location and operation of the Reset button, refer to the "Physical Description" section in the chapter "Installing the Cisco uBR924 Cable Access Router" in the Cisco uBR924 Cable Access Router Installation and Configuration Guide.
Verifying DOCSIS-Compliant Bridging
To verify that the cable access router is configured for DOCSIS-compliant bridging, enter the show startup-config command from privileged EXEC mode. The configuration should look like this:
uBR924# show startup-configBuilding configuration...Current configuration:!version 12.0service configno service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname uBR924!clock timezone - 4ip subnet-zerono ip routing!!!voice-port 0!!voice-port 1!!interface Ethernet0no ip addressno ip directed-broadcastno ip route-cachebridge-group 59bridge-group 59 spanning-disabled!interface cable-modem0no ip addressno ip directed-broadcastno ip route-cacheno keepalivecable-modem downstream saved channel 699000000 36bridge-group 59bridge-group 59 spanning-disabled!ip classlessno ip http server!line con 0transport input noneline vty 0 4login!endCustomizing the Cable Access Router Interface
Different geographical regions and different cable plants use different frequency bands. The Cisco uBR900 series cable access router uses a built-in default frequency scanning feature to address this issue. After the cable access router finds a successful downstream frequency channel, it saves the channel and power setting to NVRAM. The cable access router recalls this value the next time it needs to synchronize its frequency or register with the cable service provider's CMTS.
However, you can customize the cable access router's interface configuration if you need to deviate from the default setting that ships with the unit. For example, you might need to specify a different compliant mode, modify the saved downstream channel setting and upstream power value, or enable a faster downstream search algorithm.
Note
To customize the cable access router interface, perform the following tasks, starting in global configuration mode:
1
uBR924(config)#interface cable-modem 0Specify cable access router interface 0.
2
uBR924(config-if)#cable-modem compliant bridgeEnable DOCSIS-compliant bridging.
3
Modify the saved downstream channel setting and upstream power value. If you do this, you must specify an exact downstream frequency and a power value.1
4
uBR924(config-if)#cable-modem fast-searchEnable a faster downstream search algorithm.
1 Use the no cable-modem downstream saved channel ds-frequency us-power command to remove a saved frequency and power setting from NVRAM.
Using Multiple PCs with the Cable Access Router
The MAX CPE parameter in the DOCSIS configuration file determines how many PCs or other CPE devices are supported by a particular cable access router. The default value for the MAX CPE parameter is 1, which means only one PC can be connected to the cable access router unless this value is changed.
The DOCSIS 1.0 specification states that a CMTS cannot age-out MAC addresses for CPE devices. Thus, if MAX CPE = 1, the first PC that is connected to a cable access router is normally the only one that the CMTS recognizes as valid. If you wish to replace an existing PC or change its network interface card (NIC) to one that has a different MAC address, the CMTS will refuse to let the PC come online because this would exceed the maximum number of CPE devices specified by the MAX CPE parameter.
If you wish to replace an existing PC or NIC, use one of the following workarounds:
•
•
•
Configuration Examples
This section provides the following configuration examples:
•
•
•
•
•
•
Basic Internet Access Bridging Configuration
The following Cisco uBR900 series cable access router configuration supports a typical residential Internet-access, data only subscriber:
Current configuration:!version 12.0service configno service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname uBR924!clock timezone - 4ip subnet-zerono ip routing!voice-port 0!voice-port 1!interface Ethernet0ip address 172.16.1.40 255.255.0.0no ip directed-broadcastno ip route-cachebridge-group 59bridge-group 59 spanning-disabled!interface cable-modem0ip address 172.16.1.40 255.255.0.0no ip directed-broadcastno ip route-cachecable-modem downstream saved channel 699000000 36bridge-group 59bridge-group 59 spanning-disabled!ip classlessno ip http server!line con 0transport input noneline vty 0 4login!endBasic Internet Access Routing Configuration
The Cisco uBR900 series cable access router can be configured to act as a router to preserve IP address space and limit broadcasts that can impact the performance of the network. A sample configuration file follows.
Note
Current configuration:!version 12.0service configno service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname uBR924!clock timezone - 4ip subnet-zero!voice-port 0!voice-port 1!interface Ethernet0ip address 10.1.0.33 255.255.0.0no ip directed-broadcast!interface cable-modem0ip address 172.16.1.42 255.255.0.0no ip directed-broadcastcable-modem downstream saved channel 699000000 39no cable-modem compliant bridge!router ripnetwork 4.0.0.0network 172.16.0.0!ip classlessno ip http server!line con 0transport input noneline vty 0 4!endMulticast-Enabled Routing Configuration
The following configuration is for a Cisco uBR900 series that uses PIM sparse-dense mode and belongs to a specific multicast group. Other multicast routing protocols such as PIM sparse-mode or PIM dense-mode can be used.
Current configuration:!! Last configuration change at 23:16:44 - Thu Mar 18 1999!version 12.0service configno service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname uBR924!clock timezone - 4ip subnet-zero!ip multicast-routingip dvmrp route-limit 20000!voice-port 0!voice-port 1!interface Ethernet0ip address 24.1.0.1 255.255.0.0no ip directed-broadcastip pim sparse-dense-modeno ip route-cacheno ip mroute-cache!interface cable-modem0ip address 10.1.0.25 255.255.0.0no ip directed-broadcastip pim sparse-dense-modeno ip route-cacheno ip mroute-cachecable-modem downstream saved channel 477000000 56no cable-modem compliant bridge!!router ripversion 2network 24.0.0.0network 10.0.0.0!!ip classlessno ip http server!!line con 0transport input noneline vty 0 4!endVoIP Bridging Configuration Using H.323v2
In this example, the Cisco uBR900 series is configured for bridging, with an H.323v2 dial peer to another Cisco uBR900 series attached to the same downstream interface on the headend CMTS.
Current configuration:!! Last configuration change at 21:54:41 - Thu Apr 29 1999! NVRAM config last updated at 21:56:20 - Thu Apr 29 1999!version 12.0no service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname 2007!clock timezone - 3ip subnet-zerono ip routing!voice-port 0input gain -3!voice-port 1input gain -3!dial-peer voice 1 potsdestination-pattern 6501port 0!dial-peer voice 2 potsdestination-pattern 6502port 1!dial-peer voice 62 voipdestination-pattern 620.session target ipv4:10.1.71.62!interface Ethernet0ip address 10.1.71.65 255.255.255.0no ip directed-broadcastno ip route-cachebridge-group 59bridge-group 59 spanning-disabled!interface cable-modem0description DHCP Reserved Address 10.1.71.65ip address 10.1.71.65 255.255.255.0no ip directed-broadcastno ip route-cachecable-modem downstream saved channel 537000000 27bridge-group 59bridge-group 59 spanning-disabled!ip classlessno ip http server!line con 0exec-timeout 0 0transport input noneline vty 0 4loginendVoIP Routing Configuration Using H.323v2
In this example, the Cisco uBR900 series is configured for IP routing, with an H.323v2 dial peer to another Cisco uBR900 series attached to the same downstream interface on the headend CMTS.
Current configuration:!! No configuration change since last restart!version 12.0no service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname 2007!class-map class-defaultmatch any!clock timezone - 3ip subnet-zero!voice-port 0!voice-port 1!dial-peer voice 1 potsdestination-pattern 6101port 0!dial-peer voice 2 potsdestination-pattern 6102port 1!dial-peer voice 101 voipdestination-pattern 620*codec g711alawsession target ipv4:10.1.71.62!interface Ethernet0ip address 24.1.61.1 255.255.255.0no ip directed-broadcastno ip mroute-cache!interface cable-modem0ip address 10.1.71.61 255.255.255.0no ip directed-broadcastno ip mroute-cachecable-modem downstream saved channel 537000000 27no cable-modem compliant bridge!router ripversion 2network 10.0.0.0network 24.0.0.0no auto-summary <<==== Not necessary!no ip classlessip route 0.0.0.0 0.0.0.0 10.1.71.1no ip http server!line con 0exec-timeout 0 0transport input noneline vty 0 4login!!endNAT/PAT Configuration
Current configuration:!! No configuration change since last restart!version 12.0no service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname uBR924!!ip nat inside source list 1 interface cable-modem0 overloadclock timezone - -4!!interface Ethernet0ip address 10.1.1.1 255.255.255.0ip nat inside!interface cable-modem0ip address 24.3.90.20 255.255.255.0ip nat outsideno keepalivecable-modem downstream saved channel 627000000 54no cable-modem compliant bridge!ip default-gateway 24.3.90.2ip classlessip route 0.0.0.0 0.0.0.0 24.3.90.2access-list 1 permit any!line con 0line vty 0 4login!endVoIP Bridging Configuration Using SGCP
In this example, Cisco uBR924 is configured to support VoIP in bridging mode using SGCP. Note the following in the sample configuration file:
•
•
•
To configure this application via DHCP, the following fields must also be set:
•
•
•
•
Current configuration:!! Last configuration change at 16:30:00 - Thu Dec 16 1999!version 12.1no service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname art1!clock timezone - 0 6ip subnet-zerono ip routingip domain-name cisco.comip name-server 4.0.0.32!sgcp!xgcp snmp sgcp!!voice-port 0!voice-port 1!dial-peer voice 100 potsapplication SGCPAPPport 0!dial-peer voice 101 potsapplication SGCPAPPport 1!process-max-time 200!interface Ethernet0ip address 188.186.1.14 255.255.0.0no ip directed-broadcastno ip route-cacheno ip mroute-cachebridge-group 59bridge-group 59 spanning-disabled!interface cable-modem0ip address 188.186.1.14 255.255.0.0no ip directed-broadcastno ip route-cacheno ip mroute-cachecable-modem downstream saved channel 699000000 27bridge-group 59bridge-group 59 spanning-disabled!ip classlessno ip http server!!line con 0transport input noneline vty 0 4login!endIPSec Configuration
Note
Note
For detailed information on IP security, L2TP, and Firewall, refer to the Security Configuration Guide.Current configuration:!Last configuration change at 23:24:55 - Thu Dedc 16 1999!version 12.1no service padservice timestamps debug uptimeservice timestamps log uptime!hostname Router!clock timezone - 0 6ip subnet-zerono ip domain-lookup!crypto isakmp policy 1hash md5authentication pre-sharelifetime 5000crypto isakmp key 1111 address 30.1.1.1crypto isakmp identity hostname!crypto ipsec transform-set test-transform ah-md5-hmac esp-des esp-md5-hmac!crypto map test-ipsec local-address cable-modem0crypto map test-ipsec 10 ipsec-isakmpset peer 30.1.1.1set transform-set test-transformmatch address 100!interface Ethernet0ip address 24.1.0.1 255.255.0.0no ip directed-broadcast!interface cable-modem0ip address 10.1.0.25 255.255.0.0no ip directed-broadcastno keepalivecable-modem downstream saved channel 213000000 30no cable-modem compliant bridgecrypto map test-ipsecrouter ripversion 2network 10.0.0.0 network 24.0.0.0!ip classlessno ip http server!access-list 100 permit ip host 10.1.0.25 30.1.1.0 0.0.0.255!line con 0exec-timeout 0 0transport input noneline vty 0 4login!endL2TP Configuration
Note
Note
For detailed information on IP security, L2TP, and Firewall, refer to the Security Configuration Guide.Current configuration:!! Last configuration change at 20:24:59 - Thu Dec 23 1999! NVRAM config last updated at 20:34:52 - Thu Dec 23 1999!version 12.1no service padservice timestamps debug uptimeservice timestamps log uptime!hostname Router!class-map class-defaultmatch any!!clock timezone - 0 1ip subnet-zeroip tftp source-interface cable-modem0no ip domain-lookup!vpdn enable!vpdn-group 1accept dialin l2tp virtual-template 1 remote L2TP_LACno l2tp tunnel authentication!!interface Ethernet0ip address 80.1.1.1 255.255.255.0no ip directed-broadcast!interface Virtual-Template1ip unnumbered Ethernet0no ip directed-broadcastpeer default ip address pool dialupppp authentication chap!interface cable-modem0ip address 255.255.0.0no ip directed-broadcastcable-modem downstream saved channel 639000000 38no cable-modem compliant bridge!router ripversion 2network 10.0.0.0network 24.0.0.0!ip local pool dialup 24.1.0.100ip classlessno ip http server!line con 0transport input noneline vty 0 4login!endCommand Reference
This section describes the following cable-modem interface commands for the Cisco uBR900 series cable access router for Cisco IOS Release 12.0(7)T:
•
•
•
•
•
•
•
•
•
All commands relating to VoIP applications are documented in the Cisco IOS Release 12.0 command references, or in Voice over IP for the Cisco AS5300, which can be accessed online or on the Documentation CDROM by going to New Features in Cisco IOS Release 12.0(3)T.
All other commands used with this feature are documented in the Cisco IOS Release 12.0 command references.
In Cisco IOS Release 12.0(1)T or later, you can search and filter the output for show and more commands. This functionality is useful when you need to sort through large amounts of output, or if you want to exclude output that you do not need to see.
To use this functionality, enter a show or more command followed by the "pipe" character (|), one of the keywords begin, include, or exclude, and an expression that you want to search or filter on:
command | {begin | include | exclude} regular-expression
Following is an example of the show atm vc command in which you want the command output to begin with the first line where the expression "PeakRate" appears:
show atm vc | begin PeakRate
For more information on the search and filter functionality, refer to the Cisco IOS Release 12.0(1)T document, CLI String Search.
cable-modem compliant bridge
To enable DOCSIS-compliant transparent bridging for a cable access router interface at startup, use the cable-modem compliant command from interface configuration mode. Use the no form of this command to disable DOCSIS-compliant bridging for the interface.
cable-modem compliant bridge
no cable-modem compliant bridge
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Interface configuration
Command History
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. If you wish to do full transparent bridging rather than DOCSIS-compliant bridging, use the no form of the command, then configure full transparent bridging using CLI commands. See the "Configuring Bridging" section for instructions.
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:
uBR924(config)# interface cable-modem 0uBR924(config-if)# cable-modem compliant bridgeuBR924(config-if)#Related Commands
cable-modem downstream saved channel
To modify the saved downstream channel setting and upstream power value on a cable access router interface, enter the cable-modem downstream saved channel command from interface configuration mode. Use the no form of this command to remove the saved settings, which will be resaved at the next initialization cycle.
cable-modem downstream saved channel ds-frequency us-power
no cable-modem downstream saved channel ds-frequency us-power
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
Interface configuration
Command History
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 resaved at the next initialization cycle.
Cisco recommends that this command NOT be used by end users of the Cisco uBR900 series 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.
uBR924(config)# interface cable-modem 0uBR924(config-if)# no cable-modem downstream saved channel 91000000 33uBR924(config-if)#Related Commands
cable-modem fast-search
To enable a faster downstream search algorithm on a cable access router interface, use the cable-modem fast-search command from interface configuration mode. Use the no form of this command to disable the downstream fast-search feature.
cable-modem fast-search
no cable-modem fast-search
Syntax Description
There are no keywords or arguments for this command.
Defaults
Disabled
Command Modes
Interface configuration
Command History
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, starting from global configuration mode:
uBR924(config)# interface cable-modem 0uBR924(config-if)# cable-modem fast-searchuBR924(config-if)#Related Commands
cable-modem upstream preamble qpsk
To enable the QPSK modulation scheme in the upstream direction from the cable access router interface to the headend, enter the cable-modem upstream preamble qpsk command from interface configuration mode. Use the no form of this command to disable upstream modulation for the interface.
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
Usage Guidelines
Examples
The following example shows how to enter the cable-modem upstream preamble qpsk command for a cable access router interface, starting from global configuration mode:
uBR924(config)# interface cable-modem 0uBR924(config-if)# cable-modem upstream preamble qpskuBR924(config-if)#Related Commands
cable-modem voip best-effort
To allow voice calls to be sent upstream over the cable interface via best effort, use the cable-modem voip best-effort command from interface configuration mode. To disable best-effort voice calls, use the no form of this command.
cable-modem voip best-effort
no cable-modem voip best-effort
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command allows you to configure the voice traffic on a Cisco uBR900 series 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 uBR900 series cable interface, starting from global configuration mode:
uBR924(config)# interface cable-modem 0uBR924(config-if)# no cable-modem voip best-effortuBR924(config-if)#Related Commands
interface cable-modem
To specify the cable interface on a Cisco uBR900 series cable access router, enter the interface cable-modem command from global configuration mode.
interface cable-modem number
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
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 interfacedownstream Downstream channel characteristicsfast-search Enable/disable the DS fast searchupstream upstream channel characteristicsvoip Options for Voice over IP traffic over the cable interfaceuBR924(config-if)#Related Commands
show bridge cable-modem
To display bridging information for a Cisco uBR900 series cable access router, enter the show bridge cable-modem command from privileged EXEC mode.
show bridge cable-modem number
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
Following is a sample output for this command:
uBR924# show bridge cable-modem 0Total of 300 station blocks, 298 freeCodes: P - permanent, S - selfBridge Group 59:describes the significant fields shown in the display.
Related Commands
Displays the current DHCP settings on point-to-point interfaces.
Displays information about the cable interface on the Cisco uBR900 series cable access router.
show controllers cable-modem
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.
show controllers cable-modem number
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
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 0BCM Cable interface 0:BCM3300 unit 0, idb 0x200EB4, ds 0x82D4748, regaddr = 0x800000, reset_mask 0x80station address 0010.7b43.aa01 default station address 0010.7b43.aa01PLD VERSION: 32MAC State is ranging_2_state, Prev States = 7MAC mcfilter 01E02F00 data mcfilter 01000000DS: BCM 3116 Receiver: Chip id = 2US: BCM 3037 Transmitter: Chip id = 30B4Tuner: status=0x00Rx: tuner_freq 699000000, symbol_rate 5055849, local_freq 11520000snr_estimate 33406, ber_estimate 0, lock_threshold 26000QAM in lock, FEC in lock, qam_mode QAM_64Tx: tx_freq 20000000, power_level 0x3E, symbol_rate 1280000DHCP: TFTP server = 4.0.0.32, TOD server = 4.0.0.188Security server = 0.0.0.0, Timezone Offest = 0.0.4.32Config filename =buffer size 1600RX data PDU ring with 32 entries at 0x201D40rx_head = 0x201D78 (7), rx_p = 0x831BE04 (7)00 pak=0x8326318 buf=0x225626 status=0x80 pak_size=001 pak=0x83241A0 buf=0x21DE5A status=0x80 pak_size=002 pak=0x83239C0 buf=0x21C22A status=0x80 pak_size=003 pak=0x8328C70 buf=0x22EA22 status=0x80 pak_size=004 pak=0x8325F28 buf=0x22480E status=0x80 pak_size=005 pak=0x8327CB0 buf=0x22B1C2 status=0x80 pak_size=006 pak=0x8323BB8 buf=0x21C936 status=0x80 pak_size=0RX MAC message ring with 8 entries at 0x201E80rx_head_mac = 0x201E88 (1), rx_p_mac = 0x831BE80 (1)00 pak=0x8326120 buf=0x224F1A status=0x80 pak_size=001 pak=0x8324590 buf=0x21EC72 status=0x80 pak_size=002 pak=0x8323FA8 buf=0x21D74E status=0x80 pak_size=003 pak=0x8326EE8 buf=0x22806E status=0x80 pak_size=004 pak=0x8328E68 buf=0x22F12E status=0x80 pak_size=005 pak=0x8327AB8 buf=0x22AAB6 status=0x80 pak_size=006 pak=0x8328880 buf=0x22DC0A status=0x80 pak_size=007 pak=0x8326CF0 buf=0x227962 status=0xA0 pak_size=0TX BD ring with 8 entries at 0x201FB8, tx_count = 0tx_head = 0x201FD8 (4), head_txp = 0x831BF20 (4)tx_tail = 0x201FD8 (4), tail_txp = 0x831BF20 (4)00 pak=0x000000 buf=0x200000 status=0x00 pak_size=001 pak=0x000000 buf=0x200000 status=0x00 pak_size=002 pak=0x000000 buf=0x200000 status=0x00 pak_size=003 pak=0x000000 buf=0x200000 status=0x00 pak_size=004 pak=0x000000 buf=0x200000 status=0x00 pak_size=005 pak=0x000000 buf=0x200000 status=0x00 pak_size=006 pak=0x000000 buf=0x200000 status=0x00 pak_size=007 pak=0x000000 buf=0x200000 status=0x20 pak_size=0TX PD ring with 8 entries at 0x202038, tx_count = 0tx_head_pd = 0x202838 (4)tx_tail_pd = 0x202838 (4)00 status=0x00 bd_index=0x0000 len=0x0000 hdr_len=0x0000ehdr: 01 06 02 74 34 1101 status=0x00 bd_index=0x0001 len=0x0000 hdr_len=0x0000ehdr: 01 06 02 74 34 1102 status=0x00 bd_index=0x0002 len=0x0000 hdr_len=0x0000ehdr: 01 06 02 74 34 1103 status=0x00 bd_index=0x0003 len=0x0000 hdr_len=0x0000ehdr: 01 06 02 74 34 1104 status=0x00 bd_index=0x0004 len=0x0000 hdr_len=0x0000ehdr: 01 06 02 74 34 1105 status=0x00 bd_index=0x0005 len=0x0000 hdr_len=0x0000ehdr: 01 06 02 74 34 1106 status=0x00 bd_index=0x0006 len=0x0000 hdr_len=0x0000ehdr: 01 06 02 74 34 1107 status=0x20 bd_index=0x0007 len=0x0000 hdr_len=0x0000ehdr: 01 06 02 74 34 11MIB StatisticsDS fifo full = 0, Rerequests = 0DS mac msg overruns = 0, DS data overruns = 0Qualified maps = 348, Qualified syncs = 73CRC fails = 0, HDR chk fails = 0Data pdus = 0, Mac msgs = 423Valid hdrs = 423BCM3300 Registers:downstream dma:ds_data_bd_base=0x001D40, ds_mac_bd_base=0x001E80ds_data_dma_ctrl=0x98, ds_mac_dma_ctrl=0xD8ds_dma_data_index=0x0007, ds_dma_msg_index=0x0000upstream dma:us_bd_base=0x001FB8, us_pd_base=0x002038us_dma_ctrl=0x80, us_dma_tx_start=0x00Global control and status:global_ctrl_status=0x00interrupts:irq_pend=0x0008, irq_mask=0x00F7briefly describes some of the fields shown in the display. For more information, see the Broadcom documentation for the BCM3300 chip.
Related Commands
show controllers cable-modem bpkm
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.
show controllers cable-modem number bpkm
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
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 bpkmCM Baseline Privacy Key Managementconfiguration (in seconds):authorization wait time: 10reauthorization wait time: 10authorization grace time: 600operational wait time: 1rekey wait time: 1tek grace time: 600authorization rej wait time: 60kek state: STATE_B_AUTH_WAITsid 4:tek state: No resources assigneddescribes the fields shown in the display.
Related Commands
show controllers cable-modem des
To display information about the Data Encryption Standard (DES) engine registers, use the show controllers cable-modem des command in privileged EXEC mode.
show controllers cable-modem number des
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
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=0x0Cbriefly describes some of the fields shown in the display. For more information, see the Broadcom documentation for the BCM3300 chip.
Related Commands
show controllers cable-modem filters
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.
show controllers cable-modem number filters
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
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=0x00briefly describes some of the fields shown in the display. For more information, see the Broadcom documentation for the BCM3300 chip.
Related Commands
show controllers cable-modem lookup-table
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.
show controllers cable-modem number lookup-table
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
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-tableMax Burst Size (minislots) = 0x6Max Burst Length (bytes) = 0x4BPHY Overhead Lookup Table:000: 01 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06010: 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06020: 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06030: 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06040: 06 06 06 06 06 06 06 06 06 06 06 06 10 10 10 10050: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10060: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10070: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10080: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10090: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 100A0: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 100B0: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 100C0: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 100D0: 10 10 10 10 10 10 10 10 10 10 10 10 10 1F 1F 1F0E0: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F0F0: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F100: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F110: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F120: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F130: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F140: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F150: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F160: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F170: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F180: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F190: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F1A0: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F1B0: 1F 1F 1F 1F 1F 1F 1F 1F 1F 2D 2D 2D 2D 2D 2D 2D1C0: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D1D0: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D1E0: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D1F0: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D200: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D210: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D220: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D230: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D240: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D250: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D260: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D270: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D280: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D290: 2D 2D 2D 2D 2D 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C2A0: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C2B0: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C2C0: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C2D0: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C2E0: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C2F0: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C300: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C310: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C320: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C330: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C340: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C350: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C360: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C370: 3C 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B380: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B390: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B3A0: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B3B0: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B3C0: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B3D0: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B3E0: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B3F0: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B400: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B410: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B420: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B430: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B440: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 5A 5A 5A450: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A460: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A470: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A480: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A490: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A4A0: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A4B0: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A4C0: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A4D0: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A4E0: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A4F0: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A500: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A510: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A520: 5A 5A 5A 5A 5A 5A 5A 5A 5A 68 68 68 68 68 68 68530: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68540: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68550: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68560: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68570: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68580: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68590: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 685A0: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 685B0: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 685C0: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 685D0: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 685E0: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 685F0: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68600: 68 68 68 68 68 77 77 77 77 77 77 77 77 77 77 77610: 77 77 77 77 77 77 77 77 77 77 77 77 77 77 77 77620: 77 77 77 77 77 77 77 77 77 77 77 77 77 77 77 77630: 77 77 77 77 77 77 77 77 77 77 77 77 77 77 77 77PHY Reverse Lookup Table:00: 0000 0000 0000 0000 0000 0000 004B 000008: 0000 0000 0000 0000 0000 0000 0000 000010: 00DC 00DC 00DC 00DC 00DC 00DC 00DC 00DC18: 00DC 00DC 00DC 00DC 00DC 00DC 00DC 01B820: 01B8 01B8 01B8 01B8 01B8 01B8 01B8 01B828: 01B8 01B8 01B8 01B8 01B8 0294 0294 029430: 0294 0294 0294 0294 0294 0294 0294 029438: 0294 0294 0294 0294 0370 0370 0370 037040: 0370 0370 0370 0370 0370 0370 0370 037048: 0370 0370 0370 044C 044C 044C 044C 044C50: 044C 044C 044C 044C 044C 044C 044C 044C58: 044C 044C 0528 0528 0528 0528 0528 052860: 0528 0528 0528 0528 0528 0528 0528 052868: 0604 0604 0604 0604 0604 0604 0604 060470: 0604 0604 0604 0604 0604 0604 0604 06E078: 06E0 06E0 06E0 06E0 06E0 06E0 06E0 06E080: 06E0 06E0 06E0 06E0 06E0 06E0 07BC 07BC88: 07BC 07BC 07BC 07BC 07BC 07BC 07BC 07BC90: 07BC 07BC 07BC 07BC 07BC 0898 0898 089898: 0898 0898 0898 0898 0898 0898 0898 0898A0: 0898 0898 0898 0974 0974 0974 0974 0974A8: 0974 0974 0974 0974 0974 0974 0974 0974B0: 0974 0974 0A50 0A50 0A50 0A50 0A50 0A50B8: 0A50 0A50 0A50 0A50 0A50 0A50 0A50 0A50C0: 0A50 0B2C 0B2C 0B2C 0B2C 0B2C 0B2C 0B2CC8: 0B2C 0B2C 0B2C 0B2C 0B2C 0B2C 0B2C 0B2CD0: 0C08 0C08 0C08 0C08 0C08 0C08 0C08 0C08D8: 0C08 0C08 0C08 0C08 0C08 0C08 0CE4 0CE4E0: 0CE4 0CE4 0CE4 0CE4 0CE4 0CE4 0CE4 0CE4E8: 0CE4 0CE4 0CE4 0CE4 0CE4 0DC0 0DC0 0DC0F0: 0DC0 0DC0 0DC0 0DC0 0DC0 0DC0 0DC0 0DC0F8: 0DC0 0DC0 0DC0 0DC0 0E9C 0E9C 0E9C 0E9CRelated Commands
show controllers cable-modem mac
To display detailed MAC-layer information for a Cisco uBR900 series, use the show controllers cable-modem mac command in privileged EXEC mode.
show controllers cable-modem number mac [errors | hardware | log | resets | state]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
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 Example 1, Example 2, and Example 3.
Example 1
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 log00:14:24: 864.124 CMAC_LOG_DRIVER_INIT_IDB_RESET 0x080B743000:14:24: 864.128 CMAC_LOG_LINK_DOWN00:14:24: 864.132 CMAC_LOG_RESET_FROM_DRIVER00:14:24: 864.134 CMAC_LOG_STATE_CHANGE wait_for_link_up_state00:14:24: 864.138 CMAC_LOG_LINK_UP00:14:24: 864.142 CMAC_LOG_STATE_CHANGE ds_channel_scanning_state00:14:24: 864.270 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 81/453000000/855000000/600000000:14:24: 864.276 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 82/93000000/105000000/600000000:14:24: 864.280 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 83/111025000/117025000/600000000:14:24: 864.286 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 84/231012500/327012500/600000000:14:24: 864.290 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 85/333025000/333025000/600000000:14:24: 864.294 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 86/339012500/399012500/600000000:14:24: 864.300 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 87/405000000/447000000/600000000:14:24: 864.304 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 88/123012500/129012500/600000000:14:24: 864.310 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 89/135012500/135012500/600000000:14:24: 864.314 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 90/141000000/171000000/600000000:14:24: 864.320 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 91/219000000/225000000/600000000:14:24: 864.324 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 92/177000000/213000000/600000000:14:24: 864.330 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 93/55752700/67753300/600030000:14:24: 864.334 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 94/79753900/85754200/600030000:14:24: 864.340 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 95/175758700/211760500/600030000:14:24: 864.344 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 96/121756000/169758400/600030000:14:24: 864.348 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 97/217760800/397769800/600030000:14:24: 864.354 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 98/73753600/115755700/600030000:14:24: 864.358 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND 99/403770100/997799800/600030000:14:24: 864.364 CMAC_LOG_WILL_SEARCH_SAVED_DS_FREQUENCY 21300000000:14:25: 865.450 CMAC_LOG_UCD_MSG_RCVD 100:14:25: %LINK-3-UPDOWN: Interface cable-modem0, changed state to up00:14:26: 866.200 CMAC_LOG_DS_64QAM_LOCK_ACQUIRED 21300000000:14:26: 866.204 CMAC_LOG_DS_CHANNEL_SCAN_COMPLETED00:14:26: 866.206 CMAC_LOG_STATE_CHANGE wait_ucd_state00:14:26: %LINEPROTO-5-UPDOWN: Line protocol on Interface cable-modem0, changed state to down00:14:27: 867.456 CMAC_LOG_UCD_MSG_RCVD 100:14:29: 869.470 CMAC_LOG_UCD_MSG_RCVD 100:14:29: 869.472 CMAC_LOG_ALL_UCDS_FOUND00:14:29: 869.476 CMAC_LOG_STATE_CHANGE wait_map_state00:14:29: 869.480 CMAC_LOG_UCD_NEW_US_FREQUENCY 2000000000:14:29: 869.484 CMAC_LOG_SLOT_SIZE_CHANGED 800:14:29: 869.564 CMAC_LOG_FOUND_US_CHANNEL 100:14:31: 871.484 CMAC_LOG_UCD_MSG_RCVD 100:14:31: 871.692 CMAC_LOG_MAP_MSG_RCVD00:14:31: 871.694 CMAC_LOG_INITIAL_RANGING_MINISLOTS 4000:14:31: 871.696 CMAC_LOG_STATE_CHANGE ranging_1_state00:14:31: 871.700 CMAC_LOG_RANGING_OFFSET_SET_TO 961000:14:31: 871.704 CMAC_LOG_POWER_LEVEL_IS 32.0 dBmV (commanded)00:14:31: 871.708 CMAC_LOG_STARTING_RANGING00:14:31: 871.710 CMAC_LOG_RANGING_BACKOFF_SET 000:14:31: 871.714 CMAC_LOG_RNG_REQ_QUEUED 000:14:32: 872.208 CMAC_LOG_RNG_REQ_TRANSMITTED00:14:32: 872.216 CMAC_LOG_RNG_RSP_MSG_RCVD00:14:32: 872.218 CMAC_LOG_RNG_RSP_SID_ASSIGNED 1600:14:32: 872.222 CMAC_LOG_ADJUST_RANGING_OFFSET 285300:14:32: 872.224 CMAC_LOG_RANGING_OFFSET_SET_TO 1246300:14:32: 872.228 CMAC_LOG_ADJUST_TX_POWER 800:14:32: 872.230 CMAC_LOG_POWER_LEVEL_IS 34.0 dBmV (commanded)00:14:32: 872.234 CMAC_LOG_STATE_CHANGE ranging_2_state00:14:32: 872.238 CMAC_LOG_RNG_REQ_QUEUED 1600:14:32: 872.848 CMAC_LOG_RNG_REQ_TRANSMITTED00:14:32: 872.852 CMAC_LOG_RNG_RSP_MSG_RCVD00:14:32: 872.856 CMAC_LOG_RANGING_SUCCESS00:14:32: 872.874 CMAC_LOG_STATE_CHANGE dhcp_state00:14:33: 873.386 CMAC_LOG_DHCP_ASSIGNED_IP_ADDRESS 188.188.1.6200:14:33: 873.388 CMAC_LOG_DHCP_TFTP_SERVER_ADDRESS 4.0.0.3200:14:33: 873.392 CMAC_LOG_DHCP_TOD_SERVER_ADDRESS 4.0.0.3200:14:33: 873.396 CMAC_LOG_DHCP_SET_GATEWAY_ADDRESS00:14:33: 873.398 CMAC_LOG_DHCP_TZ_OFFSET 6000:14:33: 873.402 CMAC_LOG_DHCP_CONFIG_FILE_NAME platinum.cm00:14:33: 873.406 CMAC_LOG_DHCP_ERROR_ACQUIRING_SEC_SVR_ADDR00:14:33: 873.410 CMAC_LOG_DHCP_COMPLETE00:14:33: 873.536 CMAC_LOG_STATE_CHANGE establish_tod_state00:14:33: 873.546 CMAC_LOG_TOD_REQUEST_SENT00:14:33: 873.572 CMAC_LOG_TOD_REPLY_RECEIVED 314096199200:14:33: 873.578 CMAC_LOG_TOD_COMPLETE00:14:33: 873.582 CMAC_LOG_STATE_CHANGE security_association_state00:14:33: 873.584 CMAC_LOG_SECURITY_BYPASSED00:14:33: 873.588 CMAC_LOG_STATE_CHANGE configuration_file_state00:14:33: 873.592 CMAC_LOG_LOADING_CONFIG_FILE platinum.cm00:14:34: %LINEPROTO-5-UPDOWN: Line protocol on Interface cable-modem0, changed state to up00:14:34: 874.728 CMAC_LOG_CONFIG_FILE_PROCESS_COMPLETE00:14:34: 874.730 CMAC_LOG_STATE_CHANGE registration_state00:14:34: 874.734 CMAC_LOG_REG_REQ_MSG_QUEUED00:14:34: 874.744 CMAC_LOG_REG_REQ_TRANSMITTED00:14:34: 874.754 CMAC_LOG_REG_RSP_MSG_RCVD00:14:34: 874.756 CMAC_LOG_COS_ASSIGNED_SID 1/1600:14:34: 874.760 CMAC_LOG_RNG_REQ_QUEUED 1600:14:34: 874.768 CMAC_LOG_REGISTRATION_OK00:14:34: 874.770 CMAC_LOG_REG_RSP_ACK_MSG_QUEUED 000:14:34: 874.774 CMAC_LOG_STATE_CHANGE establish_privacy_state00:14:34: 874.778 CMAC_LOG_PRIVACY_NOT_CONFIGURED00:14:34: 874.780 CMAC_LOG_STATE_CHANGE maintenance_state00:14:34: 874.784 CMAC_LOG_REG_RSP_ACK_MESSAGE_EVENT00:14:34: 874.788 CMAC_LOG_REG_RSP_ACK_MSG_SENTIf 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_state00:14:33: 873.386 CMAC_LOG_RNG_REQ_TRANSMITTED00:14:33: 873.388 CMAC_LOG_RNG_RSP_MSG_RCVD00:14:33: 873.386 CMAC_LOG_RNG_REQ_TRANSMITTED00:14:33: 873.392 CMAC_LOG_RNG_RSP_MSG_RCVD00:14:33: 873.396 CMAC_LOG_WATCHDOG_TIMER00:14:33: 873.398 CMAC_LOG_RESET_DHCP_WATCHDOG_EXPIRED00:14:33: 873.402 CMAC_LOG_STATE_CHANGE reset_interface_state00:14:33: 873.406 CMAC_LOG_DHCP_PROCESS_KILLEDThe fields in this display are explained in the section "Basic Troubleshooting" on page 23.
Example 2
MAC error log information is displayed in the following example, which is also reported via SNMP:
uBR924# show controllers cable-modem 0 mac errors74373.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 errors497989.804 D01.0 Discover sent no Offer received. No available DHCP Server.498024.046 D01.0 Discover sent no Offer received. No available DHCP Server.498058.284 D01.0 Discover sent no Offer received. No available DHCP Server.Example 3
The show controllers cable-modem 0 mac resets command shows only the entries in the MAC log that begin with the field CMAC_LOG_RESET. Collectively presenting these fields provides you with a summary of the most recent reasons why the cable interface was reset.
Reset messages and brief explanations are included in the following examples and in ; however, the reset messages in 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 resets62526.114 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED62564.368 CMAC_LOG_RESET_T4_EXPIRED62677.178 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED62717.462 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED62757.746 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED62796.000 CMAC_LOG_RESET_T4_EXPIRED62908.808 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED62949.092 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED62989.380 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED63029.662 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED63069.944 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED63110.228 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED63148.484 CMAC_LOG_RESET_T4_EXPIRED63261.296 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILEDThe 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 resets497989.804 CMAC_LOG_RESET_DHCP_WATCHDOG_EXPIRED498024.046 CMAC_LOG_RESET_DHCP_WATCHDOG_EXPIRED498058.284 CMAC_LOG_RESET_DHCP_WATCHDOG_EXPIREDThe 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 resets527986.444 CMAC_LOG_RESET_FROM_DRIVER528302.042 CMAC_LOG_RESET_FROM_DRIVER528346.600 CMAC_LOG_RESET_FROM_DRIVER528444.494 CMAC_LOG_RESET_FROM_DRIVER
Example 4
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 hardwarePLD VERSION: 32BCM3300 unit 0, idb 0x200EB4, ds 0x82D4748, regaddr = 0x800000, reset_mask0x80station address 0010.7b43.aa01 default station address 0010.7b43.aa01MAC mcfilter 01E02F00 data mcfilter 01000000buffer size 1600RX data PDU ring with 32 entries at 0x201D40rx_head = 0x201D40 (0), rx_p = 0x82D4760 (0)00 pak=0x82DF844 buf=0x227F1A status=0x80 pak_size=001 pak=0x82E0BF4 buf=0x22C56A status=0x80 pak_size=002 pak=0x82DF454 buf=0x22710A status=0x80 pak_size=003 pak=0x82DF64C buf=0x227812 status=0x80 pak_size=004 pak=0x82E0024 buf=0x229B3A status=0x80 pak_size=005 pak=0x82DBF2C buf=0x21B332 status=0x80 pak_size=006 pak=0x82DFE2C buf=0x229432 status=0x80 pak_size=007 pak=0x82E0FE4 buf=0x22D37A status=0x80 pak_size=008 pak=0x82DF064 buf=0x2262FA status=0x80 pak_size=009 pak=0x82DEC74 buf=0x2254EA status=0x80 pak_size=010 pak=0x82DEA7C buf=0x224DE2 status=0x80 pak_size=011 pak=0x82DE884 buf=0x2246DA status=0x80 pak_size=012 pak=0x82DE68C buf=0x223FD2 status=0x80 pak_size=013 pak=0x82DE494 buf=0x2238CA status=0x80 pak_size=014 pak=0x82DE29C buf=0x2231C2 status=0x80 pak_size=015 pak=0x82DE0A4 buf=0x222ABA status=0x80 pak_size=016 pak=0x82DDEAC buf=0x2223B2 status=0x80 pak_size=017 pak=0x82DDCB4 buf=0x221CAA status=0x80 pak_size=018 pak=0x82DDABC buf=0x2215A2 status=0x80 pak_size=019 pak=0x82DD8C4 buf=0x220E9A status=0x80 pak_size=020 pak=0x82DD6CC buf=0x220792 status=0x80 pak_size=021 pak=0x82DD4D4 buf=0x22008A status=0x80 pak_size=022 pak=0x82DD2DC buf=0x21F982 status=0x80 pak_size=023 pak=0x82DD0E4 buf=0x21F27A status=0x80 pak_size=024 pak=0x82DCEEC buf=0x21EB72 status=0x80 pak_size=025 pak=0x82DCCF4 buf=0x21E46A status=0x80 pak_size=026 pak=0x82DCAFC buf=0x21DD62 status=0x80 pak_size=027 pak=0x82DC904 buf=0x21D65A status=0x80 pak_size=028 pak=0x82DC70C buf=0x21CF52 status=0x80 pak_size=029 pak=0x82DC514 buf=0x21C84A status=0x80 pak_size=030 pak=0x82DC31C buf=0x21C142 status=0x80 pak_size=031 pak=0x82DC124 buf=0x21BA3A status=0xA0 pak_size=0RX MAC message ring with 8 entries at 0x201E80rx_head_mac = 0x201EB0 (6), rx_p_mac = 0x82D480C (6)00 pak=0x82E0DEC buf=0x22CC72 status=0x80 pak_size=001 pak=0x82E021C buf=0x22A242 status=0x80 pak_size=002 pak=0x82E060C buf=0x22B052 status=0x80 pak_size=003 pak=0x82E11DC buf=0x22DA82 status=0x80 pak_size=004 pak=0x82DFC34 buf=0x228D2A status=0x80 pak_size=005 pak=0x82E09FC buf=0x22BE62 status=0x80 pak_size=006 pak=0x82DEE6C buf=0x225BF2 status=0x80 pak_size=007 pak=0x82DFA3C buf=0x228622 status=0xA0 pak_size=0TX BD ring with 8 entries at 0x201FB8, tx_count = 0tx_head = 0x201FB8 (0), head_txp = 0x82D4888 (0)tx_tail = 0x201FB8 (0), tail_txp = 0x82D4888 (0)00 pak=0x000000 buf=0x200000 status=0x00 pak_size=001 pak=0x000000 buf=0x200000 status=0x00 pak_size=002 pak=0x000000 buf=0x200000 status=0x00 pak_size=003 pak=0x000000 buf=0x200000 status=0x00 pak_size=004 pak=0x000000 buf=0x200000 status=0x00 pak_size=005 pak=0x000000 buf=0x200000 status=0x00 pak_size=006 pak=0x000000 buf=0x200000 status=0x00 pak_size=007 pak=0x000000 buf=0x200000 status=0x20 pak_size=0TX PD ring with 8 entries at 0x202038, tx_count = 0tx_head_pd = 0x202038 (0)tx_tail_pd = 0x202038 (0)00 status=0x00 bd_index=0x0000 len=0x0000 hdr_len=0x0000ehdr: 00 00 00 2E FF FF01 status=0x00 bd_index=0x0001 len=0x0000 hdr_len=0x0000ehdr: 00 00 00 2E FF FF02 status=0x00 bd_index=0x0002 len=0x0000 hdr_len=0x0000ehdr: 00 00 00 2E FF FF03 status=0x00 bd_index=0x0003 len=0x0000 hdr_len=0x0000ehdr: 00 00 00 2E FF FF04 status=0x00 bd_index=0x0004 len=0x0000 hdr_len=0x0000
Guest
