Downloads |
Table Of Contents
Release Notes for Cisco uBR924 Cable Access Router for Cisco IOS Release 12.1 XM
Cisco uBR924 Cable Access Router
Cisco Cable Clock Card Support
Determining the Software Version
Upgrading to a New Software Release
New Hardware Features in Release 12.1(5)XM7
New Software Features in Release 12.1(5)XM7
New Hardware Features in Release 12.1(5)XM4
New Software Features in Release 12.1(5)XM4
New Hardware Features in Release 12.1(5)XM3
New Software Features in Release 12.1(5)XM3
New Hardware Features in Release 12.1(5)XM2
New Software Features in Release 12.1(5)XM2
MGCP Basic CLASS and Operator Services
Hardware and Software Features Inherited From Release 12.1(5)T
Radio Frequency Interface MIBs
Deprecated and Replacement MIBs
GRE IP Tunnels Are Not Supported
Upgrading Software Images Using BPI
Using Multiple PCs with the Cisco uBR924 Cable Access Router
Supplemental and Corrected Text for the Online Feature Module
Open Caveats in Release 12.1(5)XM7
Closed or Resolved Caveats—Release 12.1(5)XM7
Open Caveats in Release 12.1(5)XM4
Closed or Resolved Caveats—Release 12.1(5)XM4
uBR Cable Modems Not Coming Online
Cisco IOS Software Documentation Set
Release 12.1 Documentation Set Contents
Obtaining Technical Assistance
Contacting TAC by Using the Cisco TAC Website
Release Notes for Cisco uBR924 Cable Access Router for Cisco IOS Release 12.1 XM
February 13, 2002
Note
You can find the most current Cisco IOS documentation on Cisco.com. This set of 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)XM7. 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)XM7, 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.com and the Documentation CD-ROM.
Use these release notes with Cross-Platform Release Notes for Cisco IOS Release 12.1 T, located on Cisco.com and the Documentation CD-ROM.
Contents
These release notes describe the following topics:
•
•
Introduction
For information on new features and Cisco IOS commands supported by Release 12.1 XM, see the "New and Changed Information" section and the "Related Documentation" section.
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.
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)XM7. 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 (10BASE-T 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 and voice.
Early Deployment Releases
These release notes describe the Cisco uBR924 cable access router for Cisco IOS Release 12.1(5)XM7, which is an early deployment (ED) release based on Cisco IOS Release 12.1(5)T. Early deployment releases contain fixes for software caveats and support for new Cisco hardware and software features.
In addition to the new features that are introduced in Cisco IOS Release 12.1(5)XM2 for the Cisco uBR924 cable access router, all features that are supported in Release 12.1(5)T are also supported in Release 12.1(5)XM7. Table 3Table 1 shows the new features supported in Release 12.1(5)XM2. Table 3 lists all features supported in Release 12.1(5)XM7.
Table 1 Early Deployment Releases for the Cisco uBR924 Cable Access Router
Software Features Inherited from Release 12.1(5)T
Release 12.1 XM3(5)
•
•
Now
Release 12.1 T(5)
•
•
•
Now
(3a)
•
•
•
•
•
Now
(2)
•
•
•
•
Now
(1)
•
•
•
•
•
•
•
•
Note
Now
1 MGCP = Media Gateway Control Protocol
2 CAS = Channel Associated Signaling
3 PBX = private branch exchange
4 AAL2 = ATM Adaptation Layer 2
5 PVC = Permanent Virtual Circuit
6 CLASS = Custom Local Area Subscriber Services
7 NAT = Network Address Translation
8 HSRP = Hot Standby Router Protocol
9 ICMP = Internet Control Message Protocol
10 XGCP is meant to represent both Simple Gateway Control Protocol and Media Gateway Control Protocol.
11 MIB = Management Information Base
12 SGCP = Simple Gateway Control Protocol
13 SID = Service ID
14 SNMP = Simple Network Management Protocol
System Requirements
This section describes the system requirements for Cisco IOS Releases 12.1(5)XM7 and includes the following sections:
•
•
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)XM7. The image subset legend for Table 2Table 2 is as follows:
•
•
•
Headend Interoperability
Cisco Cable Clock Card Support
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.
DOCSIS 1.0+ Extensions
Cisco IOS Release 12.1 XM 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 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.
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.
To support the MGCP CAS PBX and AAL2 PVC feature and the MGCP Basic CLASS and Operator Services feature, both the Cisco uBR924 cable access router and the Cisco gatekeeper/gateway products must be running Cisco IOS Release 12.1(5)XM7 or greater.
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.
Supported Hardware
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)XM7, RELEASE SOFTWAREUpgrading to a New Software Release
For technical information about upgrading to a new software release, see Cisco IOS Upgrade Ordering Instructions on Cisco.com 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 Cisco.com 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
Note
New and Changed Information
The following sections list the new hardware and software features supported by the Cisco uBR924 cable access router.
New Hardware Features in Release 12.1(5)XM7
There are no new hardware features in the Cisco uBR924 for Cisco IOS Release 12.1(5)XM7.
New Software Features in Release 12.1(5)XM7
There are no new software features in the Cisco uBR924 for Cisco IOS Release 12.1(5)XM7.
New Hardware Features in Release 12.1(5)XM4
There are no new hardware features in the Cisco uBR924 for Cisco IOS Release 12.1(5)XM4.
New Software Features in Release 12.1(5)XM4
There are no new software features in the Cisco uBR924 for Cisco IOS Release 12.1(5)XM4.
New Hardware Features in Release 12.1(5)XM3
There are no new hardware features in the Cisco uBR924 for Cisco IOS Release 12.1(5)XM3.
New Software Features in Release 12.1(5)XM3
There are no new software features in the Cisco uBR924 for Cisco IOS Release 12.1(5)XM3.
New Hardware Features in Release 12.1(5)XM2
Cisco IOS Release 12.1(5)XM2 does not contain any new hardware features for the Cisco uBR924 cable access router.
New Software Features in Release 12.1(5)XM2
The following new software features are supported by the Cisco uBR924 cable access router for Cisco IOS Release 12.1(5)XM2.
MGCP CAS PBX and AAL2 PVC
The Media Gateway Control Protocol (MGCP) Channel Associated Signaling (CAS) private branch exchange (PBX) and ATM Adaptation Layer 2 (AAL2) Permanent Virtual Circuit (PVC) feature set—referred to as the MGCP CAS PBX and AAL2 PVC feature set— extends the earlier Simple Gateway Control Protocol (SGCP) CAS and AAL2 support onto the merged SGCP/MGCP software base. These features enable various service provider solutions, including Integrated Access, IP PBX, Residential Cable Access, and Voice over DSL.
Note
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121limit/121x/121xm/121xm_5/ftmgcpba.htm.MGCP CAS PBX and AAL2 includes the following features:
CAS Termination and Translation to MGCP on BGWs and TGWs
Channel Associated Signaling termination and translation to MGCP is supported on Business Gateways (BGWs) and Trunking Gateways (TGWs).
Support for CAS PBX and Feature Group D CAS Functions
MGCP 0.1 has been expanded to support CAS packages that handle CAS PBX and Feature Group D CAS functions, including Barge-In/Busy-Line-Verify capabilities on the TGW.
Expanding MGCP 0.1 to Control AAL2 Voice Transport
The earlier version of the merged SGCP/MGCP stack supported only Voice over IP. The merged stack will now support both VoIP and VoAAL2. However, the Cisco uBR924 cable access router does not support this feature in Cisco IOS Release 12.1(5)XM2—only the Cisco MC3810 platform supports this feature in this release.
Addition of SGCP CAS PBX Support to the Existing Merged SGCP/MGCP Software Stack
The CAS PBX gateway features include CAS PBX trunks, digit maps, CAS events, and quarantine buffer software. These features were available in the existing standalone SGCP software; now they are supported using the SGCP protocol option in the merged stack:
•
–
–
–
–
This feature is supported for both Voice over IP and Voice Transport over ATM.
•
–
–
–
–
–
–
–
–
–
–
The essential difference for current SGCP users is that support for the SGCP application has been replaced with the MGCP application. The MGCP application supports both SGCP commands and MGCP commands, permitting access to a larger feature set than with the SGCP application alone. The MGCP CAS PBX and AAL2 PVC software assumes the MGCP mode as the default environment. This allows the gateway to recognize both MGCP and SGCP messages sent by the Call Agent. However, the user can specify SGCP mode for certain messages that will be sent by the gateway (by using the sgcp option as the service type in the mgcp call-agent command).
MGCP Basic CLASS and Operator Services
The MGCP Basic CLASS (Custom Local Area Subscriber Services) and Operator Services (BCOS) are a set of calling features, sometimes called "custom calling" features, that use MGCP to transmit voice, video, and data over the IP network. These features are usually found in circuit-based networks. MGCP BCOS brings them to the Cisco IOS gateways on packet-based networks.
The MGCP BCOS software is built on the MGCP CAS PBX and AAL2 software package (see the section above), and supports MGCP 0.1 and the earlier protocol versions SGCP 1.1 and 1.5.
The following MGCP BCOS features are available on Residential Gateways (RGWs):
•
•
•
•
•
•
•
•
•
•
The following two features can be run as RGW or trunking gateway (TGW) features:
•
This feature is supported in SGCP mode on Cisco uBR924, Cisco 3660, and Cisco AS5300 platforms and in MGCP mode on the Cisco 3660 and Cisco AS5300 TGW platforms and on the Cisco MC3810, Cisco 2600, and Cisco uBR924 RGW platforms.
•
This feature is supported on the Cisco 3660 and Cisco AS5300 TGW platforms and on the Cisco MC3810, Cisco 2600, and Cisco uBR924 RGW platforms. This feature cannot be supported on the G.728 and G.723 codecs.
Distinctive Power Ring
A telephone rings in a distinctive pattern when a call comes in from a pre-defined telephone number. Five patterns are available:
•
•
•
•
•
Visual Message Waiting Indicator
A light will go on when a message is waiting for the line.
Caller ID
The calling party's telephone number, date, and time of the call appear on the receiving telephone's display between the first and second rings. Up to 18 digits are shown. Private and unlisted numbers are displayed. If the called party answers the phone on the first ring, the calling party's number will not appear.
If the called party has an appropriate name display unit, the calling party's name appears on the display along with the telephone number. The name and number appear between the first and second rings.
If the calling party has blocked Caller ID from displaying the telephone number, the called party will see "P" for private or "Anonymous" on the display unit.
Caller ID with Call Waiting
If the called party has Caller ID and has enabled the Call Waiting feature, then the calling party's telephone number and name (if an appropriate display unit is available) appear while the called party is on the line with another call.
If the calling party has blocked Caller ID from displaying the telephone number and name, the called party will see "P" for private or "Anonymous" on the display unit.
Call Forwarding
Several scenarios are available:
•
•
•
•
911 Calls
The user can make a 911 call to an Emergency Service Bureau (ESB), and the call is maintained as long as the ESB does not hang up. If the user hangs up, the call is maintained. If the user hangs up then picks up the phone again, the call can resume. If the user hangs up and does not pick the phone up again, the ESB can ring the user and resume the call.
This feature is available in SGCP mode on the Cisco uBR924, Cisco 3660, and Cisco 5300 platforms and in MGCP mode on all five supported platforms.
Ring Splash
Also known as Reminder Ring, Ring Splash is activated when the user enables Call Forwarding on the telephone. The user hears Distinctive Power Ring R5 when the line is idle and a call has been forwarded. This serves as a reminder to the user that Call Forwarding is active.
Distinctive Call-Waiting Tone
The called party hears four audible tone patterns (waiting tones, or WTs) when a call is waiting on the called party's line. The tone patterns are heard in sequence as the incoming call continues to wait:
•
•
•
•
Message Waiting Tone
For users with an active voice mail system, a special dial tone is heard when the user goes off-hook and a message is waiting. The dial tone is a sequence of 10 short tones followed by a steady tone. If the user has a telephone with a visual message indicator, the indicator light goes on when a message is waiting.
Stutter Dial Tone
This tone is used in place of the dial tone to indicate that a message is waiting. When the user goes off-hook, a sequence of three short tones followed by a steady tone is heard.
Off-Hook Warning Tone
The user hears this tone when the telephone is off-hook. The tone is repeated bursts of sound of rising pitch.
Three-way Calling
The user can create a 3-way call by pressing the switchhook quickly to put the first call on hold, dialing a third party, and pressing the switchhook again quickly to join all parties to the call. This feature is supported on all five platforms.
Requirements and limitations for Three-way Calling (TWC):
•
•
•
•
•
•
•
Note
Hardware and Software Features Inherited From Release 12.1(5)T
For information on hardware and software features that have been inherited from Cisco IOS Release 12.1(5)T, see the Release Notes for Cisco uBR924 Cable Access Router for Cisco IOS
Release 12.1(5)T on Cisco.com at
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121relnt/ubr900/9001215t.htm.MIBS
Current MIBs
To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB website on Cisco.com at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
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:
•
•
•
•
•
•
The Cable Device MIB is very similar to the RFI MIB in that both allow access to statistics; they are different in that the Cable Device MIB reports statistics on the cable modem, and the RFI MIB reports statistics on the radio frequency transmissions over the cable television line.
Cisco Standard MIBs
The Cisco uBR924 cable access router supports the Cisco Standard MIBs, which consist of the following components:
•
•
•
•
•
•
Note
Cisco Voice MIBs
The Cisco uBR924 cable access router supports the Cisco Voice MIBs are supported, which consist of the following components:
•
•
•
•
•
•
•
Radio Frequency Interface MIBs
The Cisco uBR924 cable access router supports the Radio Frequency Interface (RFI) MIB. The RFI MIB module is defined in RFC 2670 and describes 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.
SGCP and MGCP MIBs
The Cisco uBR924 cable access router supports the Simple Gateway Control Protocol (SGCP) and Media Gateway Control Protocol (MGCP) through a single MIB (XGCP-MIB). This MIB supports configuration, performance, and fault management of the SGCP and MGCP interfaces.
The key attributes of this MIB are as follows:
•
•
•
•
•
•
•
•
•
•
•
•
Note
Cable-Specific MIBs
Table 4 shows the cable-specific MIBs that are supported on the Cisco uBR924 cable access router. This table also provides a brief description of each MIB's contents. Because of interdependencies, the MIBs must be loaded in the order given in the table.
Note
Note
Deprecated and Replacement MIBs
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 5 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.
Note
Limitations and Restrictions
This section describes warnings and cautions about using Cisco IOS Release 12.1(5)XM7 software.
Bridging Support
The Cisco uBR924 cable access router interoperates with DOCSIS cable networks. Cisco IOS Release 12.1 XM does not support bridging traffic across a non-DOCSIS cable network.
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 docsis 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 Media Access Controller (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
Avoid manually configuring access lists 100, 101, and 102 on the Cisco uBR924 cable access router. Configuring these access lists, either by using the CLI or an Cisco IOS configuration file, can cause the router to reload. Use access lists 103 through 109 instead for those configurations that require access lists.
This situation occurs when the DOCSIS "docsDevNmAccessEntry" table is filled at initial provisioning with the network management stations that are allowed SNMP access. The router automatically uses access lists 100, 101, and 102 for the cable, Ethernet, and USB interfaces to control this access.
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)XM7 software.
CPE Device Filtering
In Cisco IOS Release 12.1(5)XM7, the "docsDevCpeIpMax" attribute defaults to -1 instead of a default of 1, which was used in the past. 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.
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."
Caveats
Caveats describe unexpected behavior in Cisco IOS software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious. Severity 3 caveats are moderate caveats, and only select severity 3 caveats are included in the caveats document.
All caveats in Cisco IOS Release 12.1(5)T and earlier 12.1 T releases are also in Cisco IOS Release 12.1(5)XM7. For information on caveats in Cisco IOS Release 12.1 T, see the Caveats for Cisco IOS Release 12.1 T document.
All caveats in Cisco IOS Release 12.1 are also in Cisco IOS Release 12.1 T.
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 select severity 3 caveats and is located on Cisco.com and the Documentation CD-ROM.
Caveat numbers and brief descriptions are listed in Table 7 and Table 8. For details about a particular caveat, go to Bug Toolkit at:
http://www.cisco.com/kobayashi/bugs/bugs.html
To access this location, you must have an account on Cisco.com. For information about how to obtain an account, go to the "Feature Navigator" section.
Note
Open Caveats in Release 12.1(5)XM7
There are no open caveats specific to Cisco IOS Release 12.1(5)XM7 that require documentation in the release notes.
Closed or Resolved Caveats—Release 12.1(5)XM7
All the caveats listed in Table 6 are resolved in Cisco IOS Release 12.1(5)XM7. This table lists only severity 1 and 2 caveats and select severity 3 caveats.
Table 6 Closed and Resolved Caveats for Release 12.1(5) XM7
CSCdw65903
An error can occur with management protocol processing. Please use the following URL for further information:
http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCdw65903
Open Caveats in Release 12.1(5)XM4
All the caveats listed in Table 7 are open in Cisco IOS Release 12.1(5)XM4. This table lists only severity 1 and 2 caveats and select severity 3 caveats.
