Downloads |
Table Of Contents
Release Notes for Cisco uBR924 Cable Access Router for Cisco IOS Release 12.1(5)T
Cisco uBR924 Cable Access Router
Cisco Cable Clock Card Support
Determining the Software Version
Upgrading to a New Software Release
No New Hardware Features in Release 12.1(5)T
New Software Features in Release 12.1(5)T
NAT—Support for NetMeeting Directory (Internet Locator Service—ILS)
No New Hardware Features in Release 12.1(3a)T1
New Software Features in Release 12.1(3a)T1
HSRP Support for ICMP Redirects (CSCdp37610)
Media Gateway Control Protocol Residential Gateway Support
Secure Shell Version 1 Client Support
No New Hardware Features in Release 12.1(2)T
New Software Features in Release 12.1(2)T
Ecosystem Gatekeeper Interoperability Enhancements, Phase 2
H.323 Support for Virtual Interfaces
No New Hardware Features in Release 12.1(1)T
New Software Features in Release 12.1(1)T
Cable Monitor Web Diagnostics Tool
Cisco Cable Clock Card Support
Dynamic Host Configuration Protocol Proxy Support
Ecosystem Gatekeeper Interoperability Enhancements
New Hardware Features in Release 12.1(1)
New Software Features in Release 12.1(1)
Management Information Base (MIB) Features
DOCSIS CLI Commands Are Removed
GRE IP Tunnels Are Not Supported
Upgrading Software Images Using BPI
Using Access Lists with IPSec Images
Using Multiple PCs with the Cisco uBR924 Cable Access Router
Last Maintenance Release of Cisco IOS Release 12.1 T
Supplemental and Corrected Text for the Online Feature Module
Radio Frequency Interface MIBs
Troubleshooting uBR Cable Modems Not Coming Online
Closed or Resolved Caveats—Release 12.1(5)T and Earlier Releases
Cisco IOS Software Documentation Set
Release 12.1 Documentation Set
Obtaining Technical Assistance
Software Configuration Tips on the Cisco Technical Assistance Center Home Page
Release Notes for Cisco uBR924 Cable Access Router for Cisco IOS Release 12.1(5)T
November 27, 2000
Part Number: OL-0385-04 Rev.B0
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 for the Cisco uBR924 Cable Access Router describe the enhancements provided in Cisco IOS Release 12.1(5)T. These release notes are updated as needed to describe new features, memory requirements, hardware support, software platform deferrals, and changes to the microcode or modem code and related documents.
For a list of software caveats that apply to Release 12.1(5)T, see the "Caveats" section and Caveats for Cisco IOS Release 12.1 T. The caveats document is updated for every maintenance release and is located on Cisco Connection Online (CCO) and the Documentation CD-ROM.
Use these release notes with Cross-Platform Release Notes for Cisco IOS Release 12.1 T, located on CCO and the Documentation CD-ROM.
Note
Contents
These release notes describe the following topics:
•
Introduction
The DOCSIS-based Cisco uBR924 Cable Access Router gives residential or small office/home office (SOHO) subscribers high-speed Internet or Intranet access. The Cisco uBR924 Cable Access Router supports both data traffic and packet voice and fax traffic via a shared two-way cable system and Internet Protocol (IP) backbone network. The Cisco uBR924 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 uBR924 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 uBR924 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 uBR924 Cable Access Router functions as a cable modem at the subscriber site to convey data communications on the cable television system.
Note
Based on the feature licenses your company purchased, other Cisco IOS images can be downloaded from Cisco Connection Online (CCO). Special operating modes, based on your service offering and the practices in place for your network, can be supported for the Cisco uBR924 router, based on the available images in Cisco IOS Release 12.1(5)T. The Cisco uBR924 Cable Access Router can also function as an advanced router, providing wide-area network (WAN) data connectivity in a variety of configurations.
Note
Cisco uBR924 Cable Access Router
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 Easy IP, Firewall Phase II (Cisco Secure Integrated Software), and IP security (IPSec).
Early Deployment Releases
These release notes describe the Cisco uBR924 Cable Access Router for Cisco IOS Release 12.1(5)T, which is an early deployment (ED) release based on Cisco IOS Release 12.1. Early deployment releases contain fixes for software caveats and support for new Cisco hardware and software features.
Table 1 shows recent early deployment releases of the Cisco uBR924 Cable Access Router:
Table 1 Early Deployment Releases for the Cisco uBR924 Cable Access Router
(5)
•
•
Now
(3a)
•
•
•
•
Now
(2)
•
•
•
•
Now
(1)
•
•
•
•
•
•
•
•
Note
Now
(7)
•
•
•
•
•
Now
(7)
•
Note
Now
(7)
•
•
•
•
Now
(5)
•
•
–
–
–
–
–
•
•
Now
(4)
•
•
•
•
Now
1 NAT = Network Address Translation
2 HSRP = Hot Standby Router Protocol
3 ICMP = Internet Control Message Protocol
4 XGCP is meant to represent both Simple Gateway Control Protocol and Media Gateway Control Protocol.
5 MIB = Management Information Base
6 SGCP = Simple Gateway Control Protocol
7 SID = Service ID
8 SNMP = Simple Network Management Protocol
9 VPN = Virtual Private Network
10 DES = Data Encryption Standard
11 VoIP = Voice over Internet Protocol
12 NAT = Network Address Translation
13 PAT = Port Address Translation
14 RIP V2 = Routing Information Protocol version 2
System Requirements
This section describes the system requirements for Cisco IOS Releases 12.1(5)T:
•
•
Memory Recommendations
Table 2 lists the memory recommendations for each of the feature sets available for the Cisco uBR924 Cable Access Router in Cisco IOS Release 12.1(5)T. The image subset legend for Table 2Table 2 is as follows:
•
•
•
•
•
•
Table 2 Memory Recommendations for the Cisco uBR924 Cable Access Router,
Release 12.1(5)T Feature Sets
Flash
Memory
DRAM
Memory
FromHome Office with Voice—Base image with Easy IP and Voice
ubr920-k1v4y5-mz
4 MB Flash
16 MB DRAM
RAM
Value Telecommuter—Easy IP, Voice, and IPSec 56
ubr920-k1v4y556i-mz
4 MB Flash
16 MB DRAM
RAM
Performance Telecommuter— Easy IP, Voice, and IPSec 3DES
ubr920-k1k2v4y5-mz
4 MB Flash
16 MB DRAM
RAM
Value Small Office—Easy IP, Voice, FW2 , and IPSec 56
ubr920-k1o3v4y556i-mz
4 MB Flash
16 MB DRAM
RAM
Performance Small Office— Easy IP, Voice, FW2, and IPSec 3DES
ubr920-k1k2o3v4y5-mz
4 MB Flash
16 MB DRAM
RAM
1 L2TP is not supported in any Cisco IOS Release 12.1(5)T images for the Cisco uBR924 Cable Access Router.
2 FW—Firewall (Cisco Secure Integrated Software)
Note
Headend Interoperability
Cisco Cable Clock Card Support
When using Cisco IOS Release 12.1(1)T 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 uBR7200 series universal broadband router with the Cisco Cable Clock Card feature.
DOCSIS Concatenation
If using DOCSIS concatenation with a 16-QAM (quadrature amplitude modulation) symbol rate, the CMTS must be configured for Unique Word 16 in the preamble for both short and long data burst profiles. On the Cisco uBR7200 series universal broadband routers, use the cable modulation-profile global configuration command and specify "uw16" for both the long and short modulation profiles. See caveats CSCdp76415 and CSCdp92139 on page 31 for more detail.
DOCSIS 1.0+ Extensions
Cisco IOS Release 12.1 T images support the Cisco DOCSIS 1.0+ Extensions, which include dynamic multi-SID assignment and concatenation. To use the dynamic multi-SID and concatenation features, both the Cisco uBR924 router and the CMTS router must support them. If you are using the Cisco uBR7200 series headend equipment as the CMTS router, Cisco IOS Release 12.0(7)XR, Release 12.1(1)T, or greater is required on both the Cisco uBR924 Cable Access Router and the CMTS router to ensure that these features are activated.
To configure the Cisco uBR924 Cable Access Router to support multiple classes of service, use either the Cisco Subscriber Registration Center (CSRC) tool or the configuration file editor of your choice. DOCSIS configuration files can contain multiple classes of service (CoS) to support voice. The first CoS is used for data (and voice if no other CoS is defined), and up to three additional classes of service can be defined to give higher priority for voice traffic.
IPSec Encryption Support
To use IPSec encryption, both the Cisco uBR924 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 desired that the CMTS act as an IPSec gateway.)
Note
Voice Protocol Support
When using a voice-enabled 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. The gatekeeper must be running Cisco IOS Release 12.0(5)T or greater 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 voice-enabled Cisco IOS Release 12.1 images. SGCP is an alternative to the H.323 protocol that provides signaling and feature negotiation via a remote Call Agent. 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.
Hardware Supported
The Cisco uBR924 Cable Access Router contains the following interfaces:
•
•
–
Note
–
•
•
•
Determining the Software Version
To determine the version of Cisco IOS software running on your Cisco uBR924 Cable Access Router, log into the Cisco uBR924 Cable Access Router and enter the show version EXEC command:
For the Cisco uBR924 Cable Access Router:
router# show versionCisco Internetwork Operating System SoftwareIOS (tm) 920 Software (ubr920-k1v4y5-mz), Version 12.1(5)T, RELEASE SOFTWAREUpgrading to a New Software Release
For technical information about upgrading to a new software release, see Cisco IOS Upgrade Ordering Instructions on CCO 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
Feature Set Tables
Cisco IOS software is packaged in feature sets consisting of software images, depending on the platform. Each feature set contains a specific set of Cisco IOS features.
Caution
Table 3 lists the voice and data software images by feature sets for the Cisco uBR924 Cable Access Router. This table uses the following conventions:
•
•
Note
Table 3 Feature List by Feature Set for the Cisco uBR924 Cable Access Router—Voice and Data
Baseline Privacy Interface (BPI) Encryption
Yes
Yes
Yes
Yes
Yes
Baseline Privacy Interface (BPI) MIB
Yes
Yes
Yes
Yes
Yes
Cable Device MIB (RFC 2669)
Yes
Yes
Yes
Yes
Yes
Cable Monitor
Yes
Yes
Yes
Yes
Yes
Firewall (Cisco Secure Integrated Software)
No
No
No
Yes
Yes
Cisco Standard MIBs
Yes
Yes
Yes
Yes
Yes
Cisco Voice MIBs
Yes
Yes
Yes
Yes
Yes
Configurable H.225 Timers
Yes
Yes
Yes
Yes
Yes
DHCP Proxy Support
Yes
Yes
Yes
Yes
Yes
DOCSIS 1.0+ Extensions (Dynamic multi-SID assignment and concatenation)
Yes
Yes
Yes
Yes
Yes
DOCSIS-Compliant Bridging
Yes
Yes
Yes
Yes
Yes
Easy IP
Yes
Yes
Yes
Yes
Yes
Ecosystem Gatekeeper Interoperability Enhancements
Yes
Yes
Yes
Yes
Yes
HSRP Support for ICMP Redirect
Yes
Yes
Yes
Yes
Yes
H.323v2 Protocol
Yes
Yes
Yes
Yes
Yes
H.323 Support for Virtual Interfaces
Yes
Yes
Yes
Yes
Yes
IPSec Encryption with 56-bit DES
No
Yes
Yes
Yes
Yes
IPSec Encryption with Triple DES (3DES)
No
No
Yes
No
Yes
Layer 2 Tunneling Protocol (L2TP)1
No
No
No
No
No
Media Gateway Control Protocol (MGCP) Residential Gateway Support
Yes
Yes
Yes
Yes
Yes
NAT—Support for NetMeeting Directory (Internet Locator Service—ILS)
Yes
Yes
Yes
Yes
Yes
Parser Cache
Yes
Yes
Yes
Yes
Yes
RFC 2233 Support
Yes
Yes
Yes
Yes
Yes
Radio Frequency Interface MIB (RFC 2670)
Yes
Yes
Yes
Yes
Yes
Routing (RIP V2)
Yes
Yes
Yes
Yes
Yes
Secure Shell (SSH)—56-bit encryption
Yes
Yes
Yes
Yes
Yes
Secure Shell (SSH)—3DES encryption
No
No
Yes
No
Yes
Simple Gateway Control Protocol (SGCP)
Yes
Yes
Yes
Yes
Yes
XGCP MIB
Yes
Yes
Yes
Yes
Yes
1 The L2TP feature set is not supported in any Cisco IOS Release 12.1(3a)T1 images for the Cisco uBR924 Cable Access Router.
New and Changed Information
The following sections list the new hardware and software features supported by the Cisco uBR924 Cable Access Router.
No New Hardware Features in Release 12.1(5)T
Cisco IOS Release 12.1(5)T does not contain any new hardware features for the Cisco uBR924 Cable Access Router.
New Software Features in Release 12.1(5)T
The following new software features are supported by the Cisco uBR924 Cable Access Router for Cisco IOS Release 12.1(5)T.
NAT—Support for NetMeeting Directory (Internet Locator Service—ILS)
Microsoft NetMeeting is a Windows-based application that enables multiuser interaction and collaboration from a user's PC over the Internet or an intranet. Support for the NetMeeting Directory (ILS) allows connections by name from the directory built into the NetMeeting application. Destination IP addresses do not need to be known in order for a connection to be made.
Parser Cache
The Parser Cache feature optimizes the parsing (translation) of Cisco IOS software configuration command lines by remembering how to parse recently encountered command lines. This feature was developed to improve the scalability of the Cisco IOS software command-line interface (CLI) parser when processing large configuration files. This improvement is especially useful for those cases in which thousands of virtual circuits must be configured for interfaces, or hundreds of access control lists (ACLs) are required. The parser chain cache can rapidly recognize and translate configuration lines that differ slightly from previously used configuration lines (for example, pvc 0/100, pvc 0/101, and so on). Testing indicates an improvement to load time of between 30% and 36% for large configuration files when using the parser cache.
The parser cache is enabled by default on all platforms using Cisco IOS Release 12.1(5)T or later. A new global configuration command, [no] parser cache, allows the disabling or reenabling of this feature.
No New Hardware Features in Release 12.1(3a)T1
Cisco IOS Release 12.1(3a)T1 does not contain any new hardware features for the Cisco uBR924 Cable Access Router.
New Software Features in Release 12.1(3a)T1
The following new software features are supported by the Cisco uBR924 Cable Access Router for Cisco IOS Release 12.1(3a)T1.
IP Address Negotiation
Cisco IOS Release 12.1(3a)T1 for Cisco uBR900 series Cable Access Routers adds support for the ip address dhcp command on the cable interface. Previous releases used the ip address negotiated command for this purpose, but this command is now reserved for serial interfaces. This change is cosmetic only and does not change how the router obtains its IP address. See the "IP Address Negotiation" section for additional information.
HSRP Support for ICMP Redirects (CSCdp37610)
The HSRP Support for ICMP Redirects feature enables Internet Control Message Protocol (ICMP) redirection on interfaces configured with the Hot Standby Router Protocol (HSRP).
When running HSRP, it is important to prevent hosts from discovering the interface (or real) Media Access Control (MAC) addresses of routers in the HSRP group. If a host is redirected by ICMP to the real MAC address of a router, and that router later fails, then packets from the host will be lost. Previously, ICMP redirect messages were automatically disabled on interfaces configured with HSRP.
This feature now enables ICMP redirects on interfaces configured with HSRP. This functionality works by filtering outgoing ICMP redirect messages through HSRP, where the next-hop IP address may be changed to an HSRP virtual IP address.
Media Gateway Control Protocol Residential Gateway Support
Cisco IOS Release 12.1(3a)T1 for the Cisco uBR924 Cable Access Router supports version 0.1 of the Media Gateway Control Protocol (MGCP), a proposed IETF voice control protocol that is intended to eventually supersede the existing SCGP 1.1 protocol. The MGCP 0.1 and SGCP 1.1 protocols have been merged on the Cisco uBR924 router so that the router can respond efficiently to either protocol.
The Cisco uBR924 Cable Access Router functions as a Residential Gateway, providing an interface between analog FXS phone or fax systems and the Voice over IP (VoIP) network. The Residential Gateway uses a Trunking Gateway to contact the call agent, which in turn provides access to the public telephone switched network (PTSN).
The Cisco uBR924 Cable Access Router supports both call waiting and caller ID when using either MGCP or SGCP for call control. Each of the two voice ports on the Cisco uBR924 router can be configured with the IP address for a default call agent. SNMP management of both the MGCP and SNMP protocols is provided by a single MIB (XGCP-MIB).
Note
Secure Shell Version 1 Client Support
Cisco IOS Release 12.1(3a)T1 enhances the router's support for the Secure Shell (SSH) protocol, which was introduced in Cisco IOS Release 12.1(1)T (see the "Secure Shell Server Support" section). SSH connections use encryption and user authentication to establish a secure communications channel over an insecure network, such as the Internet.
In Cisco IOS Release 12.1(3a)T1, SSH support now includes the following features:
•
•
•
•
Note
Note
No New Hardware Features in Release 12.1(2)T
Cisco IOS Release 12.1(2)T does not contain any new hardware features for the Cisco uBR924 Cable Access Router.
New Software Features in Release 12.1(2)T
The following new software features are supported by the Cisco uBR924 Cable Access Router for Cisco IOS Release 12.1(2)T. For more information on these features, see the documentation listed in the "Related Documentation" section.
Configurable H.225 Timer
In previous Cisco IOS releases, the H.225 Transmission Control Protocol (TCP) connection timeout timer was fixed at 15 seconds. Cisco IOS Release 12.1(2)T adds the ability to configure this timer to a value between 1-30 seconds, or to disable it entirely.
Note
Ecosystem Gatekeeper Interoperability Enhancements, Phase 2
This feature enhances the existing Ecosystem Gatekeeper Interoperability Enhancements feature to improve the ability of voice gateways to move between gatekeepers upon a failure or an outage. In addition to the existing features, phase 2 adds support for the alternate gatekeeper field (altGKInfo) to the admission rejection message. This allows a gateway to move between gatekeepers during the admission request phase.
Phase 2 of this feature is introduced in Cisco IOS Release 12.1(2)T.
Note
H.323 Support for Virtual Interfaces
Cisco IOS Release 12.1(2)T for the Cisco uBR924 Cable Access Router introduces a new interface command to control the IP address used for outgoing H.323 VoIP traffic:
h323-gateway voip bind srcaddr ip address
The h323-gateway voip bind command can be used with any interface, but its primary use is with the Cisco uBR924 router's Ethernet interface when configuring a Virtual Private Network (VPN). In this configuration, the h323-gateway voip bind command configures the router so that VoIP traffic is sent and received using the IP address of the Ethernet interface (as opposed to the default behavior, which is to use the IP address of the default outgoing interface, which is the cable interface).
The h323-gateway voip bind command allows the enterprise network to maintain the H.323 gatekeeper and gateway in the enterprise network's address space. Without the h323-gateway voip bind command, outgoing voice traffic uses the IP address of the cable interface. This requires that the H.323 gatekeeper and gateway be maintained in the cable service provider's address space, which is not desirable if the enterprise needs to control the voice network and VPN configuration.
Note
This feature was tracked as caveat CSCdp11931, and is introduced in Cisco IOS Release 12.1(2)T.
RFC 2233 Support
Cisco IOS Release 12.1(2)T updates the IF-MIB MIB with support for RFC 2233, which makes the previous RFC 1573 obsolete. This change adds the "ifCounterDiscontinuityTime" attribute and changes the "ifTableLastChange attribute".
In addition, this feature adds support for RFC 2233-compliant link-up and link-down traps. By default, link-up and link-down traps are implemented as given in the CISCO-IF-CAPABILITY.my MIB. To generate link-up and link-down traps as defined by RFC 2233, use the snmp-server trap link ietf global configuration command.
This feature was tracked as caveats CSCdp41317 and CSCdp55546, and is introduced in Cisco IOS Release 12.1(2)T.
No New Hardware Features in Release 12.1(1)T
Cisco IOS Release 12.1(1)T does not contain any new hardware features for the Cisco uBR924 Cable Access Router.
New Software Features in Release 12.1(1)T
The following new software features are supported by the Cisco uBR924 Cable Access Router for Cisco IOS Release 12.1(1)T. For more information on these features, see the documentation listed in the "Related Documentation" section.
Cable Monitor Web Diagnostics Tool
The Cable Monitor is a web-based diagnostic tool to display the current status and configuration of the Cisco uBR924 router. The Cable Monitor can also be used when the cable network is down, providing an easy way for subscribers to provide necessary information to service technicians and troubleshooters.
The Cable Monitor is introduced in Cisco IOS Release 12.1(1)T.
Cisco Cable Clock Card Support
When using Cisco IOS Release 12.1(1)T 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 uBR7200 series universal broadband router with the Cisco Cable Clock Card feature. This feature can enhance reliability in a voice network and reduce delay and jitter in the voice traffic.
DOCSIS 1.0+ Extensions
In addition to the other quality-of-service (QoS) features, DOCSIS 1.1 supports a number of features that are required for the delivery of high-quality voice traffic. To use these features before the DOCSIS 1.1 specification is finalized, Cisco has created the DOCSIS 1.0+ extensions that contain the most important of these features:
•
•
To avoid potentially wasting bandwidth in this manner, the DOCSIS 1.0+ extensions support the dynamic creation of multiple SIDs. New MAC messages dynamically add, delete, and modify SIDs when needed. When a phone connected to the router is taken off-hook, the Cisco uBR924 router creates a SID that has the QoS parameters needed for that particular voice call. When the call terminates, the router deletes the SID, releasing its bandwidth for use elsewhere.
The DOCSIS 1.0+ features are introduced in Cisco IOS Software Release 12.0(7)XR and 12.1(1)T.
Note
Dynamic Host Configuration Protocol Proxy Support
The Dynamic Host Configuration Protocol (DHCP) Proxy Support feature helps to automate the configuration of the Cisco uBR924 Cable Access Router in two situations:
•
•
When configured for DHCP Proxy Support, during startup the Cisco uBR924 Cable Access Router sends a proxy DHCP request to the DHCP server using the Ethernet interface's MAC address. The DHCP server replies with a second IP address that the router assigns to either the Ethernet interface or to the NAT pool, depending on which option was specified.
Ecosystem Gatekeeper Interoperability Enhancements
The Ecosystem Gatekeeper Interoperability Enhancements feature improves the ability of voice gateways to move between gatekeepers upon a failure or an outage. Currently, gateways can be configured to switch from their primary gatekeeper to an alternate gatekeeper if a failure or outage occurs.
However, moving gateways from one gatekeeper to another can create an imbalance in the number of gateways registered to each gatekeeper. The Ecosystem Gatekeeper Interoperability Enhancements feature helps to restore the balance by moving some of the gateways back to their proper gatekeepers after the outage has been corrected.
This feature adds support for the alternate gatekeeper field (altGKInfo) to the gatekeeper rejection and registration rejection messages. This allows a gateway to move between gatekeepers during the gatekeeper request and registration request phases.
This feature is introduced in Cisco IOS Release 12.1(1)T.
Note
H.323 Enhancements
Cisco IOS Release 12.1(1)T adds a number of H.323v2 features for voice support:
•
•
–
–
This feature is introduced in Cisco IOS Release 12.0(7)XR and Release 12.1(1)T.
Note
Secure Shell Server Support
The Cisco uBR924 router supports the Secure Shell (SSH) Version 1 protocol, which allows network administrators to make a secure Telnet connection with the router. SSH provides for authentication and encryption at the application layer, providing a secure connection even when BPI or IPSec authentication and encryption are not used at the network layer.
By default, the SSH feature uses 56-bit DES encryption. Higher security 168-bit 3DES encryption is available when using Cisco IOS images that support 3DES IPSec encryption. (The SSH client must also support the same level of encryption.)
SSH client server is introduced in Cisco IOS Release 12.1(1)T.
SNMP Enhancements
Cisco IOS Release 12.1(1)T adds support for RFC 2669 and RFC 2670 to the DOCS-CABLE-DEVICE-MIB and DOCS-IF-MIB MIBs, respectively.
New Hardware Features in Release 12.1(1)
The following new hardware features are supported by the Cisco uBR924 Cable Access Router for Cisco IOS Release 12.1(1): FXS VoIP ports—V1+2 and V2—for uBR924 Cable Access Router only.
New Software Features in Release 12.1(1)
The following new software and MIB features are supported by the Cisco uBR924 Cable Access Router for Cisco IOS Release 12.1(1).
Software Features
•
•
•
•
•
•
•
•
•
•
•
•
•
Management Information Base (MIB) Features
•
•
•
•
•
•
Limitations and Restrictions
This section describes warnings and cautions about using Cisco IOS Release 12.1(5)T software.
Bridging Support
The Cisco uBR924 Cable Access Router interoperates with DOCSIS cable networks. Cisco IOS Release 12.1 T does not support bridging traffic across a non-DOCSIS cable network.
DOCSIS CLI Commands Are Removed
To comply with DOCSIS requirements that restrict access to commands that change DOCSIS parameters, Cisco IOS Release 12.1(2)T has removed a number of commands from the CLI. These commands are now reserved exclusively for DOCSIS use. See the description of caveat CSCdr32984, for more details.
GRE IP Tunnels Are Not Supported
Generic routing encapsulation (GRE) IP tunnels cannot be built between two Cisco uBR924 Cable Access Routers because GRE IP tunnels are not supported in any Cisco IOS image for the Cisco uBR924 Cable Access Routers. IPSec tunnels, however, are supported when using Cisco IOS images that support IPSec encryption.
IP Address Negotiation
The DOCSIS specifications require that a cable modem obtain its IP address at power-on or reset from a DHCP server that is available through the cable interface. For this reason, the Cisco uBR924 Cable Access Router defaults to a configuration that uses the ip address dhcp command for the cable interface. It is not possible to override this setting by specifying a specific static IP address; to assign a static IP address to the Cisco uBR924 router, configure the DHCP server so that it assigns the desired IP address on the basis of the unit's MAC address. However, service providers should warn subscribers that changes in the cable network's topology—due to traffic levels, growth, or changes to the cable plant and other hardware—might still require changing the subnets and IP addresses assigned to a particular cable modem.
Note
Upgrading Software Images Using BPI
To enable BPI encryption, the Cisco uBR924 Cable Access Router must use a Cisco IOS image that supports BPI encryption. If the router's current software image does not support BPI encryption (or if the current software image is corrupted), you must disable BPI encryption in the DOCSIS configuration file and reset the router before you will be able to download a new software image.
Using Access Lists with IPSec Images
Access lists 100 and 101 should never be manually configured on the Cisco uBR924 Cable Access Router. Configuring these access lists with Cisco IOS Release 12.1 T images that support any form of IPSec encryption can crash the router. Use any access lists 102 through 199 instead. See the description of caveats CSCdr45850 and CSCdr46128 on page 28 for more information.
Using Multiple PCs with the Cisco uBR924 Cable Access Router
The "MAX CPE" parameter in a Cisco uBR924 Cable Access Router's DOCSIS configuration file determines how many PCs (or other customer premises equipment [CPE] devices) are supported by the Cisco uBR924 Cable Access Router. The default value for the "MAX CPE" parameter is 1, which means only one PC can be connected to the Cisco uBR924 Cable Access Router.
The DOCSIS 1.0 specification states that a CMTS cannot age out MAC addresses for CPE devices, so the first PC that is connected to the Cisco uBR924 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 uBR924 router to another.
To allow a subscriber to replace an existing PC or NIC, the following workarounds are possible:
•
•
Using the Reset Switch
The reset switch on the back panel of the Cisco uBR924 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.
Important Notes
This section contains important information about using Cisco IOS Release 12.1(5)T software.
CPE Device Filtering
In Cisco IOS Release 12.1(2)T and above, the "docsDevCpeIpMax" attribute defaults to -1 instead of the previous default of 1. This attribute controls the maximum number of CPE devices that can pass traffic through the router from its Ethernet interface as follows:
•
•
•
CPE IP address filtering is done as part of the following process:
1.
2.
3.
4.
See the DOCS-CABLE-DEVICE-MIB.my MIB for more information on the attributes and tables listed above.
Disabling the Finger Server
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.
Last Maintenance Release of Cisco IOS Release 12.1 T
The last maintenance release of the 12.1 T release train is 12.1(5)T. The migration path for customers who need bug fixes for the 12.1 T features is the 12.2 mainline release. The 12.2 mainline release has the complete feature content of 12.1 T and will eventually reach general deployment (GD).
The last maintenance release was renamed from 12.1(4)T to 12.1(5)T to synchronize with its parent software base, the 12.1(5) mainline release, and to reflect that 12.1(5)T has all the bug fixes of the 12.1(5) mainline release. The 12.1 T release train is a superset of the 12.1 mainline release; hence any defect fixed in the 12.1 mainline is also fixed in 12.1 T. The set of features for 12.1(4)T is the same as that for 12.1(5)T. There was no change in the feature content of the release. The release was renamed so that the releases would be consistent with the Cisco release process.
Supplemental and Corrected Text for the Online Feature Module
Troubleshooting Tips for the uBR924 Cable Access Router, page 15, indicates:
"Some CATV systems use alternative frequency plans such as the IRC (Incrementally Related Carrier) and HRC (Harmonically Related Carrier) plans. Most of the IRC channel slots overlap the EIA plan. The HRC plan is not supported by Cisco's cable access routers since so few cable plants are using this plan."
The correction should read:
"For the Cisco uBR924 Cable Access Router, both the IRC (Incrementally Related Carrier) and HRC (Harmonically Related Carrier) plans are supported. Most of the IRC channel slots overlap the EIA plan. For the Cisco uBR924 Cable Access Router, both the IRC and HRC plans are supported.
"The list of downstream search bands added for HRC have appropriate center frequencies and step values for an HRC channel plan. The expanded search band list may increase the amount of time required by the Cisco uBR924 Cable Access Router to acquire the downstream signal on the HRC channel plan, which can add to the total time for complete registration of the modem the very first time it is added to the cable system."
Supported MIBs
The Cisco uBR924 Cable Access Router supports the following categories of MIBs:
•
•
•
•
•
•
•
Cable Device MIBs
The Cisco uBR924 Cable Access Router supports the Cable Device MIB, which is defined by RFC 2669 and describes 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:
•
•
•
•
•
