|
|
September 5, 2000
Part Number: OL-0384-04
These release notes for the Cisco uBR900 series cable access router support Cisco IOS Release 12.1, up to and including Cisco IOS Release 12.1(4). These release notes are updated as needed to describe new features, memory requirements, hardware support, software deferrals, and changes to the microcode and related documents.
For a list of software caveats that apply to Release 12.1(4), see the "Caveats" section and Caveats for Cisco IOS Release 12.1. The caveats document is updated for every maintenance release and is located on CCO and the Documentation CD-ROM.
Use these release notes with Cross-Platform Release Notes for Cisco IOS Release 12.1 located on Cisco Connection Online (CCO) and the Documentation CD-ROM.
![]() |
Note You can find the most current Cisco IOS documentation on Cisco Connection Online (CCO). These electronic documents may contain updates and modifications made after this document was published. |
These release notes describe the following topics:
The DOCSIS-based Cisco uBR900 series cable access routersCisco uBR924 and Cisco uBR904give residential or small office/home office (SOHO) subscribers high-speed Internet or Intranet access. The Cisco uBR924 cable access router also supports both data traffic and packet telephone and fax services using a shared two-way cable system and IP backbone network. The Cisco uBR900 series cable access router connects computers and other customer premises devices at a subscriber site to the service provider's cable, hybrid fiber-coaxial (HFC), and IP backbone network.
The Cisco uBR900 series cable access router is based on Data-over-Cable Service Interface Specifications (DOCSIS) and interoperates with any bidirectional, DOCSIS-qualified cable modem termination system (CMTS). The Cisco uBR900 series cable access router ships from the Cisco factory with a Cisco IOS software image stored in nonvolatile Flash memory that supports DOCSIS-compliant bridging data operations. The Cisco uBR900 series cable access router functions as a cable modema modulator/demodulator at the subscriber site that conveys data communications on the cable television system.
![]() |
Note For information on new features and Cisco IOS commands supported by Release 12.1, see the "New and Changed Information" section and the "Related Documentation" section. |
Based on the feature licenses your company purchased, other Cisco IOS images can be downloaded from CCO. Special operating modes, based on your service offering and the practices in place for your network, can be supported for the Cisco uBR900 series router, based on the images available in Cisco IOS Release 12.1(4). The Cisco uBR900 series cable access router can also function as an advanced router, providing wide-area network (WAN) data connectivity in a variety of configurations.
![]() |
Note All Cisco IOS images for the Cisco uBR900 series cable access router images support DOCSIS Baseline Privacy Interface (BPI) encryption. BPI is subject to export restrictions. |
The Cisco uBR924 cable access router features a single F-connector interface to the cable system, four RJ-45 (10BaseT Ethernet) hub ports, two RJ-11 Foreign Exchange Station (FXS) voice ports, one RJ-11 port for an optional backup analog telephone line connection, and one RJ-45 console port to connect to a laptop computer/console terminal for local Cisco IOS configuration. The Cisco uBR924 cable access router supports voice and data Cisco IOS software images; available feature sets include Cisco IOS Firewall, Easy IP, L2TP, and 56-bit and 168-bit IP security (IPSec) encryption.
The Cisco uBR904 cable access router features a single F-connector interface to the cable system, four RJ-45 (10BaseT Ethernet) hub ports, and one RJ-45 console port to connect to a laptop computer/console terminal for local Cisco IOS configuration. The Cisco uBR904 cable access router supports data-only Cisco IOS software images; available feature sets include Firewall (Phase I), Easy IP, and 56-bit IPSec.
![]() |
Note The Cisco uBR904 cable access router is an end-of-life (EOL) product, and is no longer available for orders as of October 1999. Software images for the Cisco uBR904 router will continue to be available until November 2000 but will not contain any new feature sets. However, software images for the Cisco uBR904 router do include current caveat fixes. |
This section describes the system requirements for Cisco IOS Releases 12.1(4):
Table 1 lists the memory recommendations for the Cisco IOS Release 12.1 image sets for the Cisco uBR924 cable access router. Table 2 lists the memory recommendations for the Cisco IOS Release 12.1 image sets for the Cisco uBR904 cable access router.
The image subset legend for Table 1 and Table 2 is as follows:
| Feature Set Matrix Term | Image Name | Minimum Flash Memory | Minimum DRAM Memory | Runs From |
|---|---|---|---|---|
Home Office with VoiceBase image with Easy IP and Voice | ubr920-k1v4y5-mz | 4 MB Flash | 16 MB DRAM | RAM |
Value TelecommuterEasy IP, Voice, L2TP, and IPSec 56 | ubr920-k1sv4y556i-mz | 4 MB Flash | 16 MB DRAM | RAM |
Performance Telecommuter Easy IP, Voice, L2TP, and IPSec 3DES | ubr920-k1k2sv4y5-mz | 4 MB Flash | 16 MB DRAM | RAM |
Value Small OfficeEasy IP, Voice, FW1, L2TP, and IPSec 56 | ubr920-k1o3sv4y556i-mz | 4 MB Flash | 16 MB DRAM | RAM |
Performance Small and Branch OfficeEasy IP, Voice, FW1, L2TP, and IPSec 3DES | ubr920-k1k2o3sv4y5-mz | 4 MB Flash | 16 MB DRAM | RAM |
| 1FWCisco IOS Firewall |
![]() |
Note Cisco IOS Release 12.1 supports fewer software images (five separate images) for the Cisco uBR924 cable access router than previous releases (which supported 14 separate images). The new simplified set of software images are a superset of the images supported in the previous releases, allowing for an easy upgrade path from Release 12.0 to Release 12.1. All of the images shown in Table 1 support both the Easy IP and Voice feature sets; the IPSec, L2TP, and Firewall feature sets are supported as shown. |
| Feature Set Matrix Term | Image Name | Minimum Flash Memory | Minimum DRAM Memory | Runs From |
|---|---|---|---|---|
Home Office | ubr900-k1y5-mz | 4 MB Flash | 8 MB RAM | RAM |
Small Office/FW1 | ubr900-k1oy5-mz | 4 MB Flash | 8 MB RAM | RAM |
Small Office+/FW1/IPSec 56 | ubr900-k1oy556i-mz | 4 MB Flash | 8 MB RAM | RAM |
Telecommuter/IPSec 56 | ubr900-k1y556i-mz | 4 MB Flash | 8 MB RAM | RAM |
| 1FWCisco IOS Firewall |
When using Cisco IOS Release 12.1(1) or greater, the Cisco uBR924 cable access router automatically supports the Cisco Cable Clock Card feature for voice traffic when the CMTS is a Cisco uBR7246 VXR universal broadband router with the Cisco Cable Clock Card feature. The Cisco uBR904 cable access router does not support this feature.
To use IPSec encryption, both the Cisco uBR900 series cable access router and the destination endpoint must support IPSec encryption and be configured for the same encryption policy. The endpoint is typically an IPSec gateway such as a peer router, PIX firewall, or other device that can be configured for IPSec. (The CMTS does not need to support IPSec encryption unless it is acting as an IPSec gateway.)
![]() |
Note The IPSec feature set encrypts traffic sent between endpoints, such as between two Cisco uBR900 series cable access routers, to protect traffic sent across the Internet and other unprotected networks. The DOCSIS BPI feature encrypts traffic on the cable interface, between the Cisco uBR900 series cable access router and the CMTS. To use BPI encryption, both the Cisco uBR900 series cable access router and the CMTS must support and enable BPI encryption. |
When using a Cisco IOS Release 12.1 image, the Cisco uBR924 cable access router can packetize and transport voice in compliance with the H.323 protocol. H.323v2 is integrated in Cisco gatekeeper/gateway products, such as the Cisco 2600 series and Cisco 3600 series, using Cisco IOS Release 12.0(5)T or higher images. The gatekeeper must be running Cisco IOS Release 12.0(5)T or higher in order to support registration of the full E.164 address for each Cisco uBR924 cable access router voice port.
The Cisco uBR924 cable access router also supports the Simple Gateway Control Protocol (SGCP) when using Cisco IOS Release 12.1(4) images. SGCP is an alternative to the H.323 protocol that provides signaling and feature negotiation using a remote call agent (CA). SGCP eliminates the need for a dial-plan mapper. It also eliminates the need for static configuration on the router to map IP addresses to telephone numbers because this function is provided by the remote call agent.
The Cisco uBR924 cable access router contains:
The Cisco uBR904 cable access router contains:
To determine the version of Cisco IOS software running on your Cisco uBR900 series cable access router, log in to the Cisco uBR900 series cable access router and enter the show version EXEC command.
For the Cisco uBR924 cable access router:
router# show version Cisco Internetwork Operating System Software IOS (tm) 920 Software (ubr920-k1v4y5-mz), Version 12.1(4), RELEASE SOFTWARE
For the Cisco uBR904 cable access router:
router# show version Cisco Internetwork Operating System Software IOS (tm) 900 Software (ubr900-k1y5-mz), Version 12.1(4), RELEASE SOFTWARE
For technical information about upgrading to a new software release, see Cisco IOS Upgrade Ordering Instructions on CCO located at:
http://www.cisco.com/warp/public/620/6.html
For other information about upgrading to Cisco IOS Release 12.1, see the product bulletin Cisco IOS Software Release 12.1 Upgrade Paths and Packaging Simplification on CCO at:
Service & Support: Software Center: Cisco IOS Software: Product Bulletins: Software
Under Cisco IOS 12.1, click Cisco IOS Software Release 12.1 Ordering Procedures and Platform Support
Cisco IOS software is packaged in feature sets consisting of software imagesdepending on the platform. Each feature set contains a specific set of Cisco IOS features.
![]() |
Caution Cisco IOS images with strong encryption (including, but not limited to 168-bit [3DES] data encryption feature sets) are subject to United States government export controls and have limited distribution. Strong encryption images to be installed outside the United States are likely to require an export license. Customer orders may be denied or subject to delay due to United States government regulations. When applicable, purchaser/user must obtain local import and use authorizations for all encryption strengths. Please contact your sales representative or distributor for more information, or send an e-mail to export@cisco.com. |
Table 3 lists the voice and data software images by feature sets for the Cisco uBR924 cable access router. Table 4 lists the data-only software images by feature sets for the Cisco uBR904 cable access router. These tables use the following conventions:
![]() |
Note These feature set tables might contain a selected list of features. These tables might not be cumulativenor do they list all the features in each image. |
| Software Images by Feature Set Matrix Term | |||||
|---|---|---|---|---|---|
| Features | Base Image with Voice | Value Telecommuter | Performance Telecommuter | Value Small Office | Performance Small and Branch Office |
Baseline Privacy Interface (BPI) Encryption | Yes | Yes | Yes | Yes | Yes |
Baseline Privacy Interface (BPI) MIB1 | Yes | Yes | Yes | Yes | Yes |
Cable Device MIB | Yes | Yes | Yes | Yes | Yes |
Cisco IOS Firewall | No | No | No | Yes | Yes |
Cisco Standard MIBs | Yes | Yes | Yes | Yes | Yes |
Cisco Voice MIBs | Yes | Yes | Yes | Yes | Yes |
DOCSIS-Compliant Bridging | Yes | Yes | Yes | Yes | Yes |
Easy IP | Yes | Yes | Yes | Yes | Yes |
H.323 Protocol | Yes | Yes | Yes | Yes | Yes |
IPSec Encryption 56-bit DES | No | Yes | Yes | Yes | Yes |
IPSec Encryption Triple DES (3DES) | No | No | Yes | No | Yes |
Layer 2 Tunneling Protocol (L2TP) | No | Yes | Yes | Yes | Yes |
Radio Frequency Interface MIB | Yes | Yes | Yes | Yes | Yes |
Routing (RIP V2) | Yes | Yes | Yes | Yes | Yes |
Simple Gateway Control Protocol (SGCP) | Yes | Yes | Yes | Yes | Yes |
SGCP MIB | Yes | Yes | Yes | Yes | Yes |
| 1MIB = Management Information Base |
| Software Images by Feature Set Matrix Term | ||||
|---|---|---|---|---|
| Features | Home Office | Small Office/ FW | Small Office+/ FW/IPSec 56 | Telecommuter/ IPSec 56 |
Baseline Privacy Interface (BPI) Encryption | Yes | Yes | Yes | Yes |
Baseline Privacy Interface (BPI) MIB | Yes | Yes | Yes | Yes |
Cable Device MIB | Yes | Yes | Yes | Yes |
Cisco IOS Firewall | No | Yes | Yes | No |
Cisco Standard MIBs | Yes | Yes | Yes | Yes |
DOCSIS-Compliant Bridging | Yes | Yes | Yes | Yes |
Easy IP | Yes | Yes | Yes | Yes |
IPSec Encryption 56-bit DES | No | No | Yes | Yes |
Radio Frequency Interface MIB | Yes | Yes | Yes | Yes |
Routing (RIP V2) | Yes | Yes | Yes | Yes |
This section lists the new hardware and software features supported by the Cisco uBR900 series cable access router.
Cisco IOS Release 12.1(4) does not contain any new hardware features for the Cisco uBR900 series cable access router.
Cisco IOS Release 12.1(4) does not contain any new software features for the Cisco uBR900 series cable access router.
Cisco IOS Release 12.1(3) does not contain any new hardware features for the Cisco uBR900 series cable access router.
Cisco IOS Release 12.1(3) does not contain any new software features for the Cisco uBR900 series cable access router.
Cisco IOS Release 12.1(2) does not contain any new hardware features for the Cisco uBR900 series cable access router.
Cisco IOS Release 12.1(2) does not contain any new software features for the Cisco uBR900 series cable access router.
The following hardware feature is supported by the Cisco uBR924 router for Release 12.1(1):
The following software features are supported by the Cisco uBR900 series cable access router for Release 12.1(1). For more information on these features, see the documentation listed in the "Related Documentation" section.
This section describes warnings and cautions about using Cisco IOS Release 12.1(4) software.
Access lists 100 and 101 are reserved for DOCSIS use only and should not be configured for use with IPsec encryption or any other purpose. Access lists that use any other numbers can be used without restriction.
The Cisco uBR900 series cable access router interoperates with DOCSIS cable networks. Cisco IOS Release 12.1 does not support bridging traffic across a non-DOCSIS cable network.
All debug commands should be used only when needed for troubleshooting and testing, and then turned off when no longer needed. Each debug display consumes system resources; turning on too many debug commands can negatively affect system performance.
Generic routing encapsulation (GRE) IP tunnels cannot be built between two Cisco uBR900 series cable access routers because GRE IP tunnels are not supported in any Cisco IOS image for the Cisco uBR900 series cable access routers. IPSec tunnels, however, are supported when using Cisco IOS images that support IPSec encryption.
The "MAX CPE" parameter in a Cisco uBR900 series cable access router's DOCSIS configuration file determines how many PCs (or other customer premises equipment [CPE] devices) are supported by the Cisco uBR900 series cable access router when operating in bridging mode. The default value for the MAX CPE parameter is 1, which means only one PC can be connected to the Cisco uBR900 series cable access router when operating in bridging mode.
The DOCSIS 1.0 specification states that a CMTS cannot age-out Media Access Control (MAC) addresses for CPE devices, so the first PC that is connected to the Cisco uBR900 series cable access router is normally the only one that the CMTS recognizes as valid. If a subscriber replaces an existing PC or changes 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. A similar thing would happen if a user decides to move a PC from one Cisco uBR900 series cable access router to another.
To allow a subscriber to replace an existing PC or NIC, the following workarounds are possible:
The reset switch on the back panel of the Cisco uBR900 series cable access router is recessed to prevent accidental resets of the router. To depress the switch, use a blunt object, such as a pen or pencil point; do not use a sharp object, such as a knife or awl, because this could damage the switch and the router's circuitry.
This section contains important information about using Cisco IOS Release 12.1(4) software.
The Cisco uBR904 cable access router is an end-of-life (EOL) product, and is no longer available for orders as of October 1999. Software images for the Cisco uBR904 router will continue to be available until November 2000 but will not contain any new feature sets. However, the software images for the Cisco uBR904 router do include the current caveat fixes.
By default, the Cisco uBR900 series cable access router enables its onboard TCP/IP "finger" server to allow remote users to query the number and identities of any users who are logged in to the router. Unless your network operations center (NOC) requires this service, it should be disabled to prevent denial-of-service attacks that access the finger server's well-known port (TCP port 79). To disable the finger server, include the no service finger command in the Cisco IOS configuration file that the router downloads at initial power-on.
Troubleshooting Tips for the Cisco uBR924 Cable Access Router, page 15, indicates:
The correction should read:
![]() |
Note For the most current information about the Cisco uBR924 cable access router, see the documents listed in the "Related Documentation" section. |
Troubleshooting Tips for the Cisco uBR904 Cable Modem, page 11, indicates:
The correction should read:
The following is updated information to the Cisco uBR904 Cable Modem Installation and Configuration Guide.
Data transmitted to a Cisco uBR904 cable access router from the CMTS shares a 26- or 27-Mbps, 6-MHz data channel in the 88- to 860-MHz range. The Cisco uBR904 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 End-to-end throughput varies based on the design and loading of network components, the mix of traffic, the processing speed and interface of the host servers, the processing speed and local Ethernet performance of the subscriber's computer, and other parameters. |
The Cisco uBR904 cable access router supports 64 or 256 quadrature amplitude modulation (QAM) downstream, and Quadrature Phase-Shift Keying (QPSK) or 16 QAM upstream transmission.
Table 5 lists the upstream and downstream data specifications for the Cisco uBR904 cable access router.
| Description | Downstream Values | Upstream Values | |
|---|---|---|---|
Frequency Range | 88 to 860 MHz | 5 to 42 MHz | |
Modulation | 64 QAM 256 QAM | QPSK 16 QAM | |
Data Rate | 30 Mbps/64 QAM 42.8 Mbps/256 QAM | QPSK320 Kbit/sec to 5 Mbit/sec 16 QAM640 Kbit/sec to 10 Mbit/sec | |
Bandwidth | 6 MHz | 200K, 400K, 800K, 1.6M, 3.2 MHz | |
FEC | RS (122, 128) Trellis | Reed Solomon | |
One Channel | Receive level of digital signal | QPSK +8 to +58 dBmV 16 QAM +8 to +55 dBmV | |
| |||
Security | DES decryption: DOCSIS Baseline Privacy (BPI), 40-bit- and 56-bit-encryption, as controlled by the headend and configuration files. | DES encryption. | |
| |||
Signal-to-Noise Ratio (SNR)1 | 64 QAM: 256 QAM*: | QPSK:2 16 QAM: | |
DOCSIS configuration files typically are created at the headend by using a configuration file editor of your choice. Using the FastStep utility at a subscriber site to locally configure the unit is not supported.
The DOCSIS configuration file defines the Cisco uBR904 cable access router's operating mode, such as the provisioned downstream and upstream service assignments, including assigned frequencies, data rates, modulation schemes, class of service (CoS), type of services to support, and other parameters.
![]() |
Note An incorrect configuration file can cause the Cisco uBR904 cable access router to constantly cycle offline. Such errors include: wrong downstream frequency, wrong Upstream Channel Descriptor (UCD), wrong downstream Channel ID, invalid CoS, and incorrect BPI privacy configurations or shared secret strings. |
The Cisco uBR904 cable access router supports the following service classes:
![]() |
Note The CMTS system administrator must define the supported upstream traffic priority levels and include the traffic priority fields in the DOCSIS configuration file downloaded to the Cisco uBR904 router. |
To change the operating mode of the Cisco uBR904 cable access router from its default bridging state, complete the following procedure:
| Command | Purpose | |
|---|---|---|
Step 1 | ubr904(config)#int c 0 | Enter interface configuration mode for the cable interface. |
Step 2 | ubr904(config-if)# no cable-modem compliant bridge | Disable DOCSIS-compliant bridging. |
Step 3 | ubr904(config-if)# no bridge group number | Remove the bridge group. |
Step 4 | ubr904(config-if)# ip address ip-address subnet-mask | Enter the cable interface's IP address and subnet mask. |
Step 5 | ubr904(config-if)# exit | Return to global configuration mode. |
Step 6 | ubr904(config)#int e 0 | Enter interface configuration mode for Ethernet 0. |
Step 7 | ubr904(config-if)# no bridge group number | Remove the bridge group. |
Step 8 | ubr904(config-if)# ip address ip-address subnet-mask | Enter the Ethernet interface's IP address and subnet mask. |
Step 9 | ubr904(config-if)# exit | Return to global configuration mode. |
Step 10 | ubr904(config)# ip routing | Enable IP routing for the router. |
Step 11 | To use RIPv2: ubr904(config)#router rip ubr904(config-router)# version 2 ubr904(config-router)# network cable-network-number ubr904(config-router)# network Ethernet-network-number ubr904(config-router)# exit | Enter router configuration mode. Enable RIP version 2 routing. Enable routing on the cable interface's IP network. Enable routing on the Ethernet interface's IP network. Return to global configuration mode. |
Step 12 | ubr904(config)# no cdp run | (Optional) Disable the Cisco Discovery Protocol (CDP) on the router. (CDP is a proprietary protocol for the discovery of Cisco routers running protocols other than TCP/IP; because DOCSIS cable data networks are primarily TCP/IP networks, CDP is not necessary on the Cisco uBR904 router.) |
Step 13 | ubr904(config)# ip default-gateway ip-address | Set the default gateway for routing (typically, this is the CMTS). |
Step 14 | ubr904(config)# ip classless | (Optional) Enable the forwarding of packets that are destined for unrecognized subnets to the best supernet route. |
Step 15 | ubr904(config)# ip route 0.0.0.0 0.0.0.0 ip-address | (Optional) Establish a static route so that all packets without an established route are forwarded to the default gateway (typically the ip-address should be the IP address for the CMTS), regardless of any routing metrics. |
Step 16 | ubr904(config-if)# Ctrl-z | Return to privileged EXEC mode. |
Step 17 | ubr904# copy running-config startup-config | Save the configuration to nonvolatile memory so that it will not be lost in the event of a reset, power cycle, or power outage. |
Step 18 | ubr904# show startup-config | Display the configuration file that was just created. |
The CMTS system administrator can download an updated Cisco IOS image to a Cisco uBR904 router installed in the field by specifying the updated image filename in the router's DOCSIS configuration file. The Cisco uBR904 router automatically downloads the DOCSIS configuration file during initialization. If the software upgrade option is present in the DOCSIS configuration file and if the name of the Cisco IOS image in the DOCSIS configuration file differs from the image that is currently running on the Cisco uBR904 router, the router automatically downloads the new Cisco IOS image from the Trivial File Transfer Protocol (TFTP) server and reboots.
The image filename must be entered as the fully qualified file and path name for the file, as it exists on a TFTP server. For example, if the ubr900-k1y5-mz software image is available on the TFTP server in the 12.1 directory, enter the following as the filename:
![]() |
Note If using the DOCSIS CPE Configurator tool, v2.0 or greater, you can enter the software filename and the TFTP server's IP address in the Software Upgrade fields. |
The vendor-specific information field in the DOCSIS configuration file supports a vendor-defined attribute (type = 43) that lets the system administrator define the name of a Cisco IOS configuration file to download to a remote Cisco uBR904 cable access router. This requires a unique DHCP policy for the Cisco uBR904 cable access router, a unique DOCSIS configuration file to be sent by the DOCSIS process, and a unique Cisco IOS configuration filenamesuch as "ios.cfg" filelocated in the same TFTP server directory supported by the DOCSIS process.
The Cisco uBR904 router automatically downloads the DOCSIS configuration file during initialization. If the DOCSIS configuration file contains the name of a Cisco IOS configuration file, the router automatically downloads that file and processes its Cisco IOS commands. This also automatically disables the router's console port to prevent remote configuration of the router.
Use the following procedure to enter the filename for a Cisco IOS configuration file in the router's DOCSIS configuration file:
![]() |
Note The following steps can be accomplished through the Cisco DOCSIS CPE Configurator, which is available on CCO at http://www.cisco.com/support/toolkit/CableModem. |
Step 2 Give the file a short filename such as "ios.cfg" and place that file in the appropriate directory on the TFTP server used by the Cisco uBR904 router.
Step 3 Ensure that file permissions allow the file to be sent by TFTP.
![]() |
Note On a standard UNIX workstation, put the IOS configuration file in the /tftpboot directory. Enter the following command: chmod 775 filename, where filename is the image filename. |
Step 4 Using a DOCSIS configuration editor, such as the Cisco DOCSIS CPE Configurator, create a DOCSIS configuration file and populate the file with the correct provisioning values. (If using version 2.0 of the DOCSIS CPE Configurator, you can simply enter the Cisco IOS configuration filename when prompted for it.)
![]() |
Note DOCSIS configuration files work on the "TLV" basismeaning Type, Length, Value. However, the Cisco DOCSIS CPE Configuration tool allows you to enter just the desired value, such as the filename; the tool then calculates the appropriate type and length fields. |
If using another DOCSIS configuration file editor, enter the following information in the Vendor Specific Information Field (the following uses a file named "ios.cfg"replace this value with the actual filename being used):
a. For Cisco products, specify "00C" as the Vendor ID field.
b. The option for downloading a Cisco IOS configuration file is "128"this downloads the configuration file to the Cisco uBR904 router and disables the console port to prevent further configuration of the router at the remote site.
c. Convert the Cisco IOS configuration filename to the decimal equivalent of the filename's ASCII characters. Use the following ASCII-to-decimal conversion chart as needed. See the sample below:
Decimal - Character
| 0 NUL| 1 SOH| 2 STX| 3 ETX| 4 EOT| 5 ENQ| 6 ACK| 7 BEL|
| 8 BS | 9 HT | 10 NL | 11 VT | 12 NP | 13 CR | 14 SO | 15 SI |
| 16 DLE| 17 DC1| 18 DC2| 19 DC3| 20 DC4| 21 NAK| 22 SYN| 23 ETB|
| 24 CAN| 25 EM | 26 SUB| 27 ESC| 28 FS | 29 GS | 30 RS | 31 US |
| 32 SP | 33 ! | 34 " | 35 # | 36 $ | 37 % | 38 & | 39 ' |
| 40 ( | 41 ) | 42 * | 43 + | 44 , | 45 - | 46 . | 47 / |
| 48 0 | 49 1 | 50 2 | 51 3 | 52 4 | 53 5 | 54 6 | 55 7 |
| 56 8 | 57 9 | 58 :| 59 ; | 60 < | 61 = | 62 > | 63 ? |
| 64 @ | 65 A | 66 B | 67 C | 68 D | 69 E | 70 F | 71 G |
| 72 H | 73 I | 74 J | 75 K | 76 L | 77 M | 78 N | 79 O |
| 80 P | 81 Q | 82 R | 83 S | 84 T | 85 U | 86 V | 87 W |
| 88 X | 89 Y | 90 Z | 91 [ | 92 \ | 93 ] | 94 ^ | 95 _ |
| 96 \Q | 97 a | 98 b | 99 c |100 d |101 e |102 f |103 g |
|104 h |105 i |106 j |107 k |108 l |109 m |110 n |111 o |
|112 p |113 q |114 r |115 s |116 t |117 u |118 v |119 w |
|120 x |121 y |122 z |123 { |124 | |125 } |126 ~ |127 DEL|
i o s . c f g 105 111 115 46 99 102 103
d. Enter the Type, Length, and Value fields into the DOCSIS configuration file. For example, the filename "ios.cfg" would require the following values:
128.6.105.111.115.46.99.102.103 \
e. Save your changes using the configuration file editor.
Step 5 After you have saved the DOCSIS configuration file, save both the DOCSIS configuration file and the Cisco IOS configuration file on the TFTP file server in the appropriate directory (such as /tftpboot or the equivalent).
Step 6 Ensure that the configuration files have the proper permissions to allow TFTP to download the files to the Cisco uBR904 router. For example, on a UNIX workstation, give the following commands:
chmod 775 filename1
chmod 775 filename2
Step 7 If necessary, reconfigure your DHCP server so that it downloads the new DOCSIS configuration file. (Cisco supplies a number of products, such as Cisco Network Register [CNR], to configure DHCP servers.)
Step 8 Reset the Cisco uBR904 router to force it to reinitialize. If using a Cisco uBR7200 series router as the CMTS, you can give the following command on the Cisco uBR7200 series command-line console:
clear cable modem x.x.x.x reset
The Cisco uBR904 cable access router reregisters with the CMTS. When it processes the new DOCSIS configuration file, it downloads the new Cisco IOS configuration file from the TFTP server.
The console port of the Cisco uBR904 cable access router is completely disabled.
The Cisco uBR900 series cable access router supports the following categories of Management Information Bases (MIBs):
For the Cisco uBR900 series cable access router, the Cable Device MIB is supported. The Cable Device MIB is for DOCSIS-compliant cable modems and CMTS. The Cable Device MIB records statistics related to the configuration and status of the cable modem. Statistics include an events log and device status. The following list details the components of the Cable Device MIB:
The Cable Device MIB is very similar to the RFI MIB in that both allow access to statistics. However, the Cable Device MIB reports statistics on the cable modem, while the RFI MIB reports statistics on the radio frequency transmissions over the cable television line.
For the Cisco uBR900 series cable access router, the Cisco Standard MIBs are supported. The Cisco Standard MIBs consist of the following components:
![]() |
Note The Cisco Management Information Base (MIB) User Quick Reference publication is no longer published. For the latest list of MIBs supported by Cisco, see the Cisco Network Management Toolkit on Cisco Connection Online (CCO). From the CCO home page, click on this path: Service & Support: Software Center: Network Mgmt Products: Cisco Network Management Toolkit: Cisco MIB |
The Cisco Voice MIBs are supported only on the Cisco uBR924 cable access router. The Cisco Voice MIBs consist of the following components:
For the Cisco uBR900 series cable access router, the Radio Frequency Interface (RFI) MIB is supported. The RFI MIB module is for DOCSIS-compliant radio frequency interfaces in cable modems and CMTS. On the cable modem, RFI MIB entries provide:
The RFI MIB includes tables describing both the CMTS and the cable modem side of the cable interface. All cable modem tables are implemented.
With IPSec, data can be transmitted across a public network without fear of observation, modification, or spoofing. This enables applications such as VPNs, extranets, and remote user access.
IPSec services are similar to those provided by Cisco Encryption Technology, a proprietary Cisco security solution. However, IPSec provides a more robust security solution, and is standards based.
The Simple Gateway Control Protocol (SGCP) Management Information Bases (MIBs) are supported only on the Cisco uBR924 cable access router. The SGCP MIBs support configuration, performance, and fault management of the SGCP interface. The SGCP MIBs components are as follows:
Table 6 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 functionalearlier releases might have had unsupported prototype versions of the MIB; later releases might have added new attributes and functionality.
![]() |
Note The names given in Table 6 are the filenames for the MIBs as they exist on Cisco's FTP site (ftp://ftp.cisco.com/pub/mibs/ or http://www.cisco.com/public/mibs). Most MIBs are available in both SNMPv1 and SNMPv2 versions; the SNMPv1 versions have V1SMI as part of their filenames. Also see the Cisco MIBs home at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml. |
| MIB Filename | Description | Release | ||
|---|---|---|---|---|
This module specifies the Structure of Management Information (SMI) for SNMPv2, as defined in RFC 1902. | 12.0(4) XI | |||
This module defines the textual conventions as specified in pages 4, and 10-11 of RFC 854. | 12.0(4) XI | |||
This module specifies the Structure of Management Information (SMI) for Cisco's enterprise MIBs. | 12.0(4) XI | |||
This module defines the textual conventions used in Cisco's enterprise MIBs. | 12.0(4) XI | |||
This module describes generic objects for the Layer 3 network interface sublayers. This MIB is an updated version of MIB-II's if table, and incorporates the extensions defined in RFC 1229. | 12.0(4) XI | |||
This module describes the spectrum management flap list attributes. | 12.0(5) T1 | |||
This module describes the DOCSIS-compliant Radio Frequency (RF) interfaces in cable modems and cable modem termination systems. | 12.0(4) XI | |||
This module describes the attributes for the DOCSIS-specified Baseline Privacy Interface (BPI) on cable modems and the CMTS. | 12.0(5) T | |||
This module extends the DOCSIS standard RFI MIB (DOCS-IF-MIB) with Cisco-specific extensions, such as QoS attributes and connection status and other information regarding the cable modems and CPE devices supported by the CMTS.
| partial support: full support: | |||
This module was previously known as the CABLE-DEVICE-MIB and contains cable-related objects for DOCSIS-compliant cable modems. | 12.0(4) XI |
![]() |
Note Because of interdependencies, the MIBs must be loaded in the order given in Table 6. |
A number of Cisco-provided MIBs have been replaced with more scalable, standardized MIBs; these MIBs have filenames that start with "OLD" and first appeared in Cisco IOS Release 10.2. The functionality of these MIBs has already been incorporated into replacement MIBs, but the old MIBs are still present to support existing Cisco IOS products or Network Management System (NMS) applications. However, because the deprecated MIBs will be removed from support in the future, you should update your network management applications and scripts to refer to the table names and attributes that are found in the replacement MIBs.
Table 7 shows the deprecated MIBs and their replacements. In most cases, SNMPv1 and SNMPv2 replacements are available, but some MIBs are available only in one version. A few of the deprecated MIBs do not have replacement MIBs; support for these MIBs will be discontinued in a future release of Cisco IOS software.
| Deprecated MIB | Replacement MIBs | |
|---|---|---|
| SNMPv1 MIB | SNMPv2 MIB | |
| ||
| ||
| | |
| | |
| ||
(Compilation of other OLD* MIBS) | ||
| | |
| | |
![]() |
Note Some of the MIBs listed in Table 7 represent feature sets that are not supported on the Cisco uBR900 series cable access router. |
Caveats describe unexpected behavior in Cisco IOS software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious.
This section contains open and resolved caveats for Cisco IOS Release 12.1(4). All caveats in Release 12.1 are also in Release 12.1(4).
For information on caveats in Cisco IOS Release 12.1, see Caveats for Cisco IOS Release 12.1, which lists severity 1 and 2 caveats, and is located on CCO and the Documentation CD-ROM.
![]() |
Note If you have an account with CCO, you can use Bug Navigator II to find caveats of any severity for any release. To reach Bug Navigator II, go to CCO and press Login. Then go to Software Center: Cisco IOS Software: Cisco Bugtool Navigator II. Another option is to go to http://www.cisco.com/support/bugtools (you must have an account on CCO to access this site). |
All the caveats listed in this section are open in Release 12.1(4).
All the caveats listed in this section are closed or resolved in Release 12.1(4).
![]() |
Note All debug commands should be used only when needed for troubleshooting and testing, and then turned off when no longer needed. Each debug display consumes system resources; turning on too many debug commands can negatively affect system performance. |
no ip http server
![]() |
Note Although CSCdr36952 has been resolved in Release 12.1(2), Cisco recommends that the Cisco web server be disabled on any Cisco uBR900 series router installed in a subscriber environment using the no ip http server command. |
The following sections describe the documentation available for the Cisco uBR900 series cable access router. These documents consist of hardware and software installation guides, Cisco IOS configuration and command references, system error messages, feature modules, and other documents.
Most documentation is available as printed manuals or electronic documents, except for feature modules and select manuals, which are available online on CCO and the Documentation CD-ROM.
Use these release notes with these documents:
The following documents are specific to Release 12.1 and are located on CCO and the Documentation CD-ROM:
![]() |
Note If you have an account with CCO, you can use Bug Navigator II to find caveats of any severity for any release. To reach Bug Navigator II, go to CCO and press Login. Then go to Software Center: Cisco IOS Software: Cisco Bugtool Navigator II. Another option is to go to http://www.cisco.com/support/bugtools (you must have an account on CCO to access this site). |
These documents are available for the Cisco uBR924 cable access router on CCO and the Documentation DC-ROM:
On CCO at:
Technical Documents: Documentation Home Page: Cisco Product Documentation: Broadband/Cable Solutions: Cisco uBR900 Series Cable Access Routers
On the Documentation CD-ROM at:
Cisco Product Documentation: Broadband/Cable Solutions: Cisco uBR900 Series Cable Access Routers
![]() |
Note The Cisco uBR924 Cable Access Router Installation and Configuration Guide is still available but has been superseded by the separate hardware and software guides listed above. |
These documents are available for the Cisco uBR904 cable access router on CCO and the Documentation CD-ROM:
On CCO at:
Technical Documents: Documentation Home Page: Cisco Product Documentation: Broadband/Cable Solutions: Cisco uBR900 Series Cable Access Routers
On the Documentation CD-ROM at:
Cisco Product Documentation: Broadband/Cable Solutions: Cisco uBR900 Series Cable Access Routers
Feature modules describe new features supported by Release 12.1, and are updates to the Cisco IOS documentation set. A feature module consists of a brief overview of the feature, benefits, configuration tasks, and a command reference. As updates, the feature modules are available online only. Feature module information is incorporated in the next printing of the Cisco IOS documentation set.
On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: New Feature Documentation
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: New Feature Documentation
The Cisco IOS software documentation set consists of the Cisco IOS configuration guides, Cisco IOS command references, and several other supporting documents that are available in electronic form on the Documentation CD-ROM and CCO, as well as separately orderable in printed versions.
Each module in the Cisco IOS documentation set consists of two books: a configuration guide and a corresponding command reference. Chapters in a configuration guide describe protocols, configuration tasks, and Cisco IOS software functionality, and contain comprehensive configuration examples. Chapters in a command reference provide complete command syntax information. Use each configuration guide with its corresponding command reference.
On CCO and the Documentation CD-ROM, two master hot-linked documents provide information for the Cisco IOS software documentation set.
On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
Table 8 describes the contents of the Cisco IOS Release 12.1 software documentation set, which is available in electronic form and in printed form upon request.
![]() |
Note You can find the most current Cisco IOS documentation on CCO and the Documentation CD-ROM. These electronic documents may contain updates and modifications made after the hard-copy documents were printed. |
On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1
| Books | Major Topics |
|---|---|
| Configuration Fundamentals Overview |
| Transparent Bridging |
| Preparing for Dial Access |
| Interface Configuration Overview |
| IP Overview |
| AppleTalk and Novell IPX Overview |
| Overview |
| Multiservice Applications Overview |
| Quality of Service Overview |
| Security Overview |
| Cisco IOS Switching Services Overview |
| Introduction: Wide-Area Networking Overview |
|
|
![]() |
Note Cisco Management Information Base (MIB) User Quick Reference is no longer published. If you have an account with CCO, you can find latest list of MIBs supported by Cisco. To reach the Cisco Network Management Toolkit, press Login at CCO and go to Software Center: Network Mgmt Products: Cisco Network Management Toolkit: Cisco MIB. |
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com. Translated documentation can be accessed at http://www.cisco.com/public/countries_languages.shtml.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.
Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed documents, or by sending mail to Cisco.
Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access CCO in the following ways:
You can e-mail questions about using CCO to cco-team@cisco.com.
The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.
To contact by e-mail, use one of the following:
Language | E-mail Address |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
If you have a CCO login account, you can access the following URL, which contains links and tips on configuring your Cisco products:
http://www.cisco.com/kobayashi/technotes/serv_tips.shtml
This URL is subject to change without notice. If it changes, point your Web browser to CCO , press Login, and click on this path: Technical Assistance Center: Technical Tips.
The following sections are provided from the Technical Tips page:
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate and value your comments.
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Tue Sep 5 14:51:51 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.