Table Of Contents
Release Notes for Cisco uBR7100 Series
for Cisco IOS Release 12.1 ECOverview of Cisco Universal Broadband Routers
Cisco uBR7100 Series Universal Broadband Routers
Cisco uBR7111 and Cisco uBR7111E Universal Broadband Routers
Cisco uBR7114 and Cisco uBR7114E Universal Broadband Routers
Universal Broadband Router Overview
Determining Your Software Release
Upgrading to a New Software Release
No New Hardware Features in Release 12.1(22)EC1
No New Software Features in Release 12.1(22)EC1
No New Hardware Features in Release 12.1(22)EC
No New Software Features in Release 12.1(22)EC
No New Hardware Features in Release 12.1(20)EC3
No New Software Features in Release 12.1(20)EC3
No New Hardware Features in Release 12.1(20)EC2
No New Software Features in Release 12.1(20)EC2
No New Hardware Features in Release 12.1(20)EC1
No New Software Features in Release 12.1(20)EC1
No New Hardware Features in Release 12.1(20)EC
No New Software Features in Release 12.1(20)EC
No New Hardware Features in Release 12.1(19)EC1
No New Software Features in Release 12.1(19)EC1
No New Hardware Features in Release 12.1(19)EC
No New Software Features in Release 12.1(19)EC
No New Hardware Features in Release 12.1(13)EC4
No New Software Features in Release 12.1(13)EC4
No New Hardware Features in Release 12.1(13)EC3
No New Software Features in Release 12.1(13)EC3
No New Hardware Features in Release 12.1(13)EC2
No New Software Features in Release 12.1(13)EC2
No New Hardware Features in Release 12.1(13)EC1
No New Software Features in Release 12.1(13)EC1
No New Hardware Features in Release 12.1(13)EC
New Software Features in Release 12.1(13)EC
cable source-verify leasetimer Command
Secondary IP Support for BPI Operations
No New Hardware Features in Release 12.1(12c)EC1
No New Software Features in Release 12.1(12c)EC1
No New Hardware Features in Release 12.1(12c)EC
New Software Features in Release 12.1(12c)EC
Adding Load Information and a Timestamp to Show Commands
No New Hardware Features in Release 12.1(11b)EC1
New Software Features in Release 12.1(11b)EC1
Support for the cable tftp-enforce Command
EXEC Commands in Configuration Mode
New Hardware Features in Release 12.1(11b)EC
New Software Features in Release 12.1(11b)EC
Cable Intercept Supports Multiple Hops
Show Cable Modem Summary Command Enhanced
Show Interface Cable Command Enhanced
No New Hardware Features in Release 12.1(10)EC1
No New Software Features in Release 12.1(10)EC1
New Hardware Features in Release 12.1(10)EC
PA-T3+ and PA-2T3+ Port Adapters
New Software Features in Release 12.1(10)EC
Cisco IOS Network-Based Application Recognition
Updates to the cable map-advance and show cable modem Commands
No New Hardware Features in Release 12.1(9)EC
New Software Features in Release 12.1(9)EC
New Hardware Features in Release 12.1(8)EC
New Software Features in Release 12.1(8)EC
Enhancements to CISCO-DOCS-EXT-MIB
New Hardware Features in Release 12.1(7)EC
New Software Features in Release 12.1(7)EC
No New Hardware Features in Release 12.1(6)EC
No New Software Features in Release 12.1(6)EC
New Hardware Features in Release 12.1(5)EC1
New Software Features in Release 12.1(5)EC1
Cable Downstream Frequency Override CLI
Cable Interface Setup Facility
"cdxCmtsCmOnOffTrapEnable" Enhancement
Configurable Alternate Termination System Information Messages
DOCSIS Ethernet MIB Objects Support (RFC 2665)
DOCSIS OSSI Objects Support (RFC 2233)
Enhanced Per-Modem Error Counter
Internal Modem Configuration File Editor
MPLS VPN Support for Subinterfaces and Interface Bundles
Link Up/Down Traps Support (RFC 2233)
Overlapping Subinterface IP Addresses
SNMP Objects for Clear Host, Clear Cable Modem, and Show Current CPEs
SNMP-Specific Trap CLI Enhancements
Using cable helper-address and ip helper-address Commands
Limitation on CPE IP Addressing in Bridging Mode
Limitation on Vendor-Specific Information in the DOCSIS Configuration File
Hot-Standby 1+1 Redundancy Not Supported
EIGRP, IS-IS, and OSPF Not Supported on Cable Interfaces
Configuring the Routing Protocol Causes a Reset of the Cable Modems
Cable Source-Verify and Routing Configurations
PA-MC-2T1 Port Adapter Not Supported in Release 12.1(7)EC
Open Caveats for Release 12.1(22)EC1
Closed and Resolved Caveats for Release 12.1(22)EC1
Open Caveats for Release 12.1(22)EC
Closed and Resolved Caveats for Release 12.1(22)EC
Open Caveats for Release 12.1(20)EC3
Closed or Resolved Caveats—Release 12.2(20)EC3
Open Caveats for Release 12.1(20)EC2
Closed and Resolved Caveats for Release 12.1(20)EC2
Open Caveats for Release 12.1(20)EC1
Closed and Resolved Caveats for Release 12.1(20)EC1
Open Caveats for Release 12.1(20)EC
Closed and Resolved Caveats for Release 12.1(20)EC
Open Caveats for Release 12.1(19)EC1
Closed and Resolved Caveats for Release 12.1(19)EC1
Open Caveats for Release 12.1(19)EC
Closed and Resolved Caveats for Release 12.1(19)EC
Open Caveats for Release 12.1(13)EC4
Closed and Resolved Caveats for Release 12.1(13)EC4
Open Caveats for Release 12.1(13)EC3
Closed and Resolved Caveats for Release 12.1(13)EC3
Open Caveats for Release 12.1(13)EC2
Closed and Resolved Caveats for Release 12.1(13)EC2
Open Caveats for Release 12.1(13)EC1
Closed and Resolved Caveats for Release 12.1(13)EC1
Open Caveats for Release 12.1(13)EC
Closed and Resolved Caveats for Release 12.1(13)EC
Open Caveats for Release 12.1(12c)EC1
Closed and Resolved Caveats for Release 12.1(12c)EC1
Open Caveats for Release 12.1(12c)EC
Closed and Resolved Caveats for Release 12.1(12c)EC
Open Caveats for Release 12.1(11b)EC1
Closed and Resolved Caveats for Release 12.1(11b)EC1
Open Caveats for Release 12.1(11b)EC
Closed and Resolved Caveats for Release 12.1(11b)EC
Open Caveats for Release 12.1(10)EC1
Closed and Resolved Caveats for Release 12.1(10)EC1
Open Caveats for Release 12.1(10)EC
Closed and Resolved Caveats for Release 12.1(10)EC
Open Caveats for Release 12.1(9)EC
Closed and Resolved Caveats for Release 12.1(9)EC
Open Caveats for Release 12.1(8)EC
Closed and Resolved Caveats for Release 12.1(8)EC
Open Caveats for Release 12.1(7)EC
Closed and Resolved Caveats for Release 12.1(7)EC
Open Caveats for Release 12.1(6)EC
Closed and Resolved Caveats for Release 12.1(6)EC
Open Caveats for Release 12.1(5)EC1
Closed and Resolved Caveats for Release 12.1(5)EC1
Open Caveats for (Deferred) Release 12.1(5)EC
Closed and Resolved Caveats for (Deferred) Release 12.1(5)EC
Cisco IOS Software Documentation Set
Release 12.1 Documentation Set Contents
Obtaining Technical Assistance
Release Notes for Cisco uBR7100 Series
for Cisco IOS Release 12.1 EC
May 12, 2005
Cisco IOS Release 12.1(22)EC1
OL-1563-15These release notes for the Cisco uBR7100 series universal broadband routers document the cable-specific, leading-edge Cisco IOS 12.1 EC release and describe the enhancements and caveats provided in Cisco IOS Release 12.1(22)EC1. These release notes are updated as needed to describe new memory requirements, new features, new hardware, related document changes, and any other important changes. For a list of the software caveats that apply to Cisco IOS Release 12.1(22)EC1, see the "Caveats" section.
The Cisco IOS 12.1 EC release is based on the Cisco IOS 12.1 E train, which is the first release train available for the Cisco uBR7100 series universal broadband routers.
Use these release notes in conjunction with the Cross-Platform Release Notes for Cisco IOS Release 12.1 located on Cisco.com and the Documentation CD-ROM.
Cisco recommends that you view the field notices for this release to see if your software or hardware platforms are affected. If you have an account on Cisco.com, you can find field notices at http://www.cisco.com/warp/public/tech_tips/index/fn.html. If you do not have a Cisco.com login account, you can find field notices at http://www.cisco.com/warp/public/tech_tips/index/fn.html.
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 initially published.
Contents
These release notes describe the following topics:
•
MIBs
•
Obtaining Technical Assistance
Introduction
For information on new features and the Cisco IOS documentation set supported by Cisco IOS Release 12.1(22)EC1, see the "New and Changed Information" section and the "Related Documentation" section.
Overview of Cisco Universal Broadband Routers
The Cisco uBR7100 series and Cisco uBR7200 series universal broadband routers are based on the Data-over-Cable Service Interface Specification (DOCSIS) standards and designed to be installed at small cable operators and multiple dwelling unit (MDU) operators to enable them to offer services such as e-mail, high-speed Internet access, voice, and digital video over a bidirectional cable television and IP backbone network. The universal broadband routers function as the cable modem termination system (CMTS) for subscriber-end devices such as Cisco uBR905, Cisco uBR924, and Cisco uBR925 cable access routers, and other DOCSIS-compliant cable modems (CMs) and set-top boxes (STBs).
Both the Cisco uBR7100 series and Cisco uBR7200 series universal broadband routers allow two-way transmission of digital data and Voice over IP (VoIP) traffic over a hybrid fiber-coaxial (HFC) network. For cable plants not fully upgraded to support two-way cable transmission, the routers support DOCSIS-compliant telco return, where the cable modem's return path to the CMTS is via a dial-up telephone line connection instead of an upstream channel over the coaxial cable. The telco-return delivery mechanism enables cable operators to accelerate deployment of high-speed data services before the cable systems are upgraded to two-way plants.
Cisco uBR7100 Series Universal Broadband Routers
The Cisco uBR7100 series routers provide a fixed set of WAN and LAN interfaces with a combination of fixed and modular interfaces, allowing both flexibility and simplicity in configuration. Each Cisco uBR7100 series router includes one modular single-width port adapter, one integrated cable interface with an internal upconverter, and two integrated Fast Ethernet ports. The cable interface is based on the Cisco uBR-MC14C cable interface line card and is not field-replaceable.
The Cisco uBR7100 series routers support IP routing through the following optional WAN and LAN port adapters: Ethernet, Fast Ethernet, serial, High-Speed Serial Interface (HSSI), Packet over SONET (POS) OC-3c, and Asynchronous Transfer Mode (ATM) media. For more information, see Table 4.
Depending on the model, the Cisco uBR7100 series routers support the following two standards:
•
Data Over Cable Service Interface Specifications (DOCSIS), which supports the 6 MHz North American channel plans using the ITU J.83 Annex B RF standard. The downstream uses a 6 MHz channel width in the 85 to 860 MHz frequency range, and the upstream supports the 5 to 42 MHz frequency range.
•
European Data Over Cable Service Interface Specifications (EuroDOCSIS), which supports the 8 MHz Phase Alternating Line (PAL) and Systeme Electronique Couleur Avec Memoire (SECAM) channel plans using the ITU J.112 Annex A RF standard. The downstream uses an 8 MHz channel width in the 85 to 860 MHz frequency range, and the upstream supports multiple channel widths in the 5 to 65 MHz frequency range.
The Cisco uBR7100 series offers the following models:
•
The Cisco uBR7111 and Cisco uBR7111E universal broadband routers provide a cable interface with one downstream port and one upstream port. The downstream port can be output either as an RF signal through the integrated upconverter or as an IF signal for processing by an external upconverter. The Cisco uBR7111 router supports DOCSIS cable plants, and the Cisco uBR7111E supports EuroDOCSIS cable plants.
•
The Cisco uBR7114 and Cisco uBR7114E universal broadband routers provide a cable interface with one downstream port and four upstream ports. The downstream port can be output either as an RF signal through the integrated upconverter or as an IF signal for processing by an external upconverter. The Cisco uBR7114 router supports DOCSIS cable plants, and the Cisco uBR7114E supports EuroDOCSIS cable plants.
Cisco uBR7111 and Cisco uBR7111E Universal Broadband Routers
The Cisco uBR7111 and Cisco uBR7111E provide the following major hardware features:
•
Integrated network processing engine
•
1 upstream cable modem interface
•
1 downstream cable modem interface
•
2 Fast Ethernet ports
•
1 port adapter slot
•
1 service adapter slot
•
1 AC power supply
•
1 Personal Computer Memory Card International Association (PCMCIA) slot that allows for software upgrades through the use of Flash memory cards
Cisco uBR7114 and Cisco uBR7114E Universal Broadband Routers
The Cisco uBR7114 and Cisco uBR7114E provide the following major hardware features:
•
Integrated network processing engine
•
1 downstream cable modem interface
•
4 upstream cable modem interfaces
•
2 Fast Ethernet ports
•
1 port adapter slot
•
1 service adapter slot
•
1 AC power supply
•
1 Personal Computer Memory Card International Association (PCMCIA) slot that allows for software upgrades through the use of Flash memory cards
Universal Broadband Router Overview
Table 1 provides a quick overview of the major hardware features of the two universal broadband routers.
Early Deployment Releases
These release notes describe the Cisco uBR7100 series universal broadband routers for Cisco IOS Release 12.1(22)EC1. Release 12.1 EC is an early deployment (ED) release based on Release 12.1 E, which serves as the train's starting point. Release 12.1 E, in turn, is based on Release 12.1 Mainline. Early deployment releases contain fixes to software caveats as well as support for new Cisco hardware and software features. Feature support is cumulative from release to release, unless otherwise noted.
Table 2 lists the features supported by the Cisco uBR7100 series in Cisco IOS Release 12.1(22)EC1.
Table 2 Early Deployment (ED) Releases for the Cisco uBR7100 Series
ED Release Additional Hardware
Features Hardware
AvailabilityCisco IOS
Release 12.1(22)EC1None
None
NA
Cisco IOS
Release 12.1(22)ECNone
None
NA
Cisco IOS
Release 12.1(20)EC3None
None
NA
Cisco IOS
Release 12.1(20)EC2None
None
NA
Cisco IOS
Release 12.1(20)EC1None
None
NA
Cisco IOS
Release 12.1(20)ECNone
None
NA
Cisco IOS
Release 12.1(19)EC1None
None
NA
Cisco IOS
Release 12.1(19)ECNone
None
NA
Cisco IOS
Release 12.1(13)EC4None
None
NA
Cisco IOS
Release 12.1(13)EC3None
None
NA
Cisco IOS
Release 12.1(13)EC2None
None
NA
Cisco IOS
Release 12.1(13)EC1None
None
NA
Cisco IOS
Release 12.1(13)EC•
Support for cable source-verify leasetimer <n> command to configure how often the timer checks for expired lease times for the IP addresses for known CPE devices.
•
Secondary IP Support for Baseline Privacy Interface (BPI) Operations where the secondary IP addresses are linked to the service IDs (SIDs) used by CMs and CPE devices.
None
NA
Cisco IOS
Release 12.1(12c)EC1None
None
NA
Cisco IOS
Release 12.1(12c)EC•
Support for exec prompt timestamp command to add load information and a timestamp to Show commands.
None
NA
Cisco IOS
Release 12.1(11b)EC1•
Support for cable tftp-enforce command
•
EXEC commands in configuration mode
None
NA
Cisco IOS
Release 12.1(11b)EC•
Secure Shell Support
•
Cable Intercept Supports Multiple Hops
•
Show Cable Modem Summary Command Enhanced
•
Show Interface Cable Command Enhanced
•
Support for the PA-A3-E3 port adapter
Now
Cisco IOS
Release 12.1(10)EC1None
None
NA
Cisco IOS
Release 12.1(10)EC•
Network-Based Application Recognition (NBAR)
•
Updates to the cable map-advance and show cable modem commands
•
Support for PA-T3+ and PA-2T3+ port adapters
12/2001
Cisco IOS
Release 12.1(9)ECNew in Release 12.1(9)EC:
•
Turbo Access Control Lists (Turbo ACL)
None
NA
Cisco IOS
Release 12.1(8)ECSNMP Enhancements to CISCO-DOCS-EXT-MIB
Support for the following new port adapters:
•
PA-2FE-TX
•
PA-2FE-FX
•
PA-MC-4T1
•
PA-MC-2T1
•
PA-A3-8T1/IMA
8/27/01
Cisco IOS
Release 12.1(7)ECMxU3 Bridging
New cable routers:
•
Cisco uBR7111E
•
Cisco uBR7114E
06/13/01
Cisco IOS
Release 12.1(6)ECNone
None
N/A
Cisco IOS
Release 12.1(5)EC1The following features have been inherited from 12.1(4)EC and earlier 12.1 EC releases:
•
Cable Downstream Frequency Override CLI4
•
Cable Interface Setup Facility
•
Cable Monitor
•
Configurable Alternate Termination System Information Messages
•
Dynamic Ranging Support
•
Dynamic Upstream Modulation
•
Enhanced Per-Modem Error Counter
•
Internal Modem Configuration File Editor
•
"MAX-CPE" CLI override
•
MPLS5 VPN6 Support for Subinterfaces and Interface Bundles
•
Overlapping Subinterface IP Addresses
•
SNMP7 Warm Start Trap
New cable routers:
•
Cisco uBR7111
•
Cisco uBR7114
03/09/2001
1 Only major features are listed.
2 MIB = Management Information Base
3 MxU = Multi-Dwelling Unit (MDU) and Multi-Tenant Unit (MTU)
4 CLI = command-line interface
5 MPLS = Multiprotocol Label Switching
6 VPN = Virtual Private Network
7 SNMP = Simple Network Management Protocol
System Requirements
This section describes the system requirements for Cisco IOS Release 12.1(22)EC1 and includes the following sections:
•
Determining Your Software Release
•
Upgrading to a New Software Release
Memory Recommendations
Table 3 displays the memory recommendations of the Cisco IOS feature sets for the Cisco uBR7100 series universal broadband routers for Cisco IOS Release 12.1(22)EC1. Cisco uBR7100 series universal broadband routers are available with a 16-MB or 20-MB Type II PCMCIA Flash memory card.
The image subset legend for Table 3 is as follows:
•
i = IP routing, MPLS-VPN support, and noncable interface bridging, including Network Address Translation (NAT)
•
k1 = DOCSIS Baseline Privacy and MPLS-VPN support
•
p = IP routing with Intermediate System-to-Intermediate System (IS-IS) and Border Gateway Protocol (BGP); MPLS-VPN support; no NAT
•
s = "Plus" features: NAT and Inter-Switch Link (ISL)
•
t = Telco-Return
Note
All images support all of the hardware listed in the "Supported Hardware" section, unless otherwise indicated.
System Interoperability
This section clarifies the operation of certain features in the Cisco uBR7100 series universal broadband routers.
•
DOCSIS 1.0 Baseline Privacy
DOCSIS baseline privacy interface (BPI) gives subscribers data privacy across the RF network, encrypting traffic flows between the CMTS and CM. BPI ensures that a CM, uniquely identified by its Media Access Control (MAC) address, can obtain keying material for only those services to which it has authorized access.
To enable BPI, choose software at both the CMTS and CM that support the mode of operation. For the Cisco uBR7100 series software, choose an image with "k1" in its file name or BPI in the feature set description.
The CM must also support BPI. CMs must have factory-installed RSA private/public key pairs to support internal algorithms to generate key pairs prior to first BPI establishment. BPI must be enabled using the DOCSIS configuration file.
Note
RSA stands for Rivest, Shamir, and Adelman, inventors of a public-key cryptographic system.
•
CM Interoperability
The Cisco uBR7100 series interoperates with the following cable modems:
–
DOCSIS-based (Cisco uBR7111 and Cisco uBR7114) or Euro-DOCSIS (Cisco uBR7111E and Cisco uBR7114E) two-way CMs that support basic Internet access, VoIP, or Virtual Private Networks (VPNs).
–
Telco-return CMs—To support telco return, use a Cisco uBR7100 series software image that contains "t" in its file name. The telco-return CM must be DOCSIS-based or compliant and must be configured to support telco return.
Note
Some third-party telco-return CMs cannot receive traffic over the same downstream channel as CMs operating on a two-way data system. In these instances, segment your cable plant to allow more than one downstream channel.
•
DOCSIS 1.0 Extensions
The Cisco uBR7100 series supports the following DOCSIS 1.0 quality of service (QoS) extensions:
–
Multi-Service ID (SID) support, allowing the definition of multiple SIDs on the upstream—Voice traffic can be designated on a higher QoS committed information rate (CIR) secondary SID, while data traffic can be forwarded on a best-effort basis on a primary SID. Secondary SIDs are higher QoS CIR-type classes that have a nonzero minimum reserved rate (CIR-type service). These SIDs receive preferential treatment at the CMTS for grants over any tiered best-effort type data SID of that upstream. Reliable operation with voice requires multiple SIDs—at least two per CM to separate voice from data. In DOCSIS 1.0, SIDs are set up statically. When supporting DOCSIS 1.0 extensions, SIDs can be set up statically or dynamically. Both the CMTS and CM must support this capability.
–
CM-initiated dynamic MAC messages—Dynamic Service Addition (DSA) and Dynamic Service Deletion (DSD). These messages allow dynamic SIDs to be created and deleted at run-time on a per-VoIP call basis.
–
Unsolicited grant service (constant bit rate [CBR] scheduling) on the upstream—This helps provide a higher-quality channel for upstream VoIP packets from an Integrated Telephony Cable Modem (ITCM) such as the Cisco uBR924 cable access router.
–
Ability to provide separate downstream rates for any given ITCM, based on the IP-precedence value in the packet—This helps separate voice signaling and data traffic that goes to the same ITCM to address rate-shaping purposes.
–
Concatenation—To increase the per-CM upstream throughput in certain releases of software, Cisco uBR7100 series software supports a concatenated burst of multiple MAC frames from a CM that supports concatenation.
Note
All DOCSIS 1.0 extensions are activated only when a CM or Cisco uBR924 that supports these extensions solicits services via dynamic MAC messages or the feature set. If the CMs in your network are pure DOCSIS 1.0-based, they will receive regular DOCSIS 1.0 treatment from the CMTS.
Supported Hardware
Cisco IOS Release 12.1(22)EC1 supports the following Cisco uBR7100 series universal broadband routers:
•
Cisco uBR7111
•
Cisco uBR7114
•
Cisco uBR7111E
•
Cisco uBR7114E
For detailed descriptions of the new hardware features, see the "New and Changed Information" section.
Port Adapter Cards
Table 4 lists and describes the port adapters supported by Cisco uBR7100 series routers in Cisco IOS Release 12.1(22)EC1.
.
Table 4 Cisco uBR7100 Series Port Adapter Releases
WAN Technology Product Number and Description Introduced in Release1Ethernet
PA-A3-E3 port single-width, single-port E3 ATM, PCI-based port adapter
12.1(11)EC
PA-4E—4-port Ethernet 10BASE-T port adapter
12.1(5)EC1
PA-8E—8-port Ethernet 10BASE-T port adapter
12.1(5)EC1
Fast Ethernet
PA-FE-TX—1-port 100BASE-TX Fast Ethernet port adapter
12.1(5)EC1
PA-FE-FX—1-port 100BASE-FX Fast Ethernet port adapter
12.1(5)EC1
PA-2FE-TX—2-port 100BASE-TX Fast Ethernet port adapter
12.1(8)EC
PA-2FE-FX—2-port 100BASE-FX Fast Ethernet port adapter
12.1(8)EC
Serial
PA-E3—1-port high-speed serial E3 interface port adapter
12.1(7)EC
PA-T3—1-port T3 serial interface port adapter
12.1(7)EC
PA-T3+—1-port T3 serial interface port adapter enhanced
12.1(10)EC
PA-2E3—2-port high-speed serial E3 interface port adapter
12.1(7)EC
PA-2T3—2-port T3 serial interface port adapter
12.1(7)EC
PA-2T3+—2-port T3 serial interface port adapter enhanced
12.1(10)EC
PA-4T+—4-port synchronous serial port adapter
12.1(5)EC1
PA-4E1G-75—4-port unbalanced (75-ohm) E1-G.703/G.704 synchronous serial port adapter
12.1(7)EC
PA-4E1G-120—4-port balanced (120-ohm) E1-G.703/G.704 synchronous serial port adapter
12.1(7)EC
PA-8T-232—8-port EIA/TIA-232 synchronous serial port adapter
12.1(5)EC1
PA-8T-V35—8-port V.35 synchronous serial port adapter
12.1(5)EC1
PA-8T-X21—8-port X.21 synchronous serial port adapter
12.1(5)EC1
PA-MC-2T1—2-port multichannel DS1 Integrated Services Digital Network (ISDN) Primary Rate Interface (PRI) single-wide port adapter
12.1(8)EC
PA-MC-4T1—4-port multichannel DS1 ISDN PRI single-wide port adapter
12.1(8)EC
HSSI
PA-H—1-port HSSI port adapter
12.1(5)EC1
PA-2H—2-port HSSI port adapter
12.1(5)EC1
ATM
PA-A3-OC3MM—1-port OC-3c ATM, PCI-based multimode port adapter
12.1(5)EC1
PA-A3-OC3SMI—1-port OC-3c ATM, PCI-based single-mode intermediate reach port adapter
12.1(5)EC1
PA-A3-OC3SML—1-port OC-3c ATM, PCI-based single-mode long reach port adapter
12.1(5)EC1
PA-A3-8T1/IMA—ATM inverse multiplexer over ATM port adapter with 8 T1 ports
12.1(8)EC
Packet over SONET
PA-POS-OC3SMI—1-port OC3 single-mode, intermediate reach port adapter
12.1(7)EC
1 The number in this column indicates the Cisco IOS release in which the interface was introduced. For example, 12.1(5)EC means that an interface was introduced in Cisco IOS Release 12.1(5)EC.
Determining Your Software Release
To determine the version of Cisco IOS software running on the Cisco uBR7100 series universal broadband router, log in to the router and enter the show version EXEC command:
Router> show versionCisco Internetwork Operating System SoftwareIOS (tm) 12.1 EC Software (ubr7100-k1p-mz), Version 12.1(22)EC1, RELEASE SOFTWAREUpgrading to a New Software Release
For general information about upgrading to a new software release, see Cisco IOS Upgrade Ordering Instructions located at http://www.cisco.com/warp/public/cc/pd/iosw/prodlit/957_pp.htm.
Feature Set Tables
The 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.
Table 5 lists the features and feature sets supported by the Cisco uBR7100 series in Cisco IOS Release 12.1(22)EC1 and uses the following conventions:
•
Yes—The feature is supported in the software image.
•
No—The feature is not supported in the software image.
•
In—The number in the "In" column indicates the Cisco IOS release in which the feature was introduced (excluding deferred images). Cisco IOS Release 12.1(5)EC1 was the base release; all features, unless otherwise noted, were introduced in this release.
Note
Table 5 might not be cumulative or list all the features in each image. You can find the most current Cisco IOS documentation on Cisco.com. These electronic documents may contain updates and modifications made after the hard-copy documents were printed. If you have a Cisco.com login account, you can find image and release information regarding features prior to Cisco IOS Release 12.1(22)EC1 by using the Feature Navigator tool at http://www.cisco.com/go/fn.
Table 5 Feature List by Feature Sets for Cisco uBR7100 Series Universal Broadband Routers
Feature Feature Set In1 DOCSIS Two-way with BPI DOCSIS Two-way
IP Plus
with BPI DOCSIS Telco-Return
IP Plus
with BPI IP RoutingDHCP2 Server
Yes
Yes
Yes
DRP3 Server Agent
Yes
Yes
Yes
Easy IP (Phase 1)
Yes
Yes
Yes
Hot-Standby 1+1 Redundancy
No
No
No
No
No
Yes
IP Type of Service and Precedence for GRE6 Tunnels
Yes
Yes
Yes
IP Enhanced IGRP7 Route Authentication
Yes
Yes
Yes
MxU Bridging
12.1(7)EC
Yes
Yes
Yes
Per-Modem Filters
Yes
Yes
Yes
ManagementCable Interface Setup Facility
Yes
Yes
Yes
Cable Monitor
Yes
Yes
Yes
Cisco Call History MIB Command Line Interface
Yes
Yes
Yes
Cisco IOS Internationalization
Yes
Yes
Yes
DOCSIS Ethernet MIB Objects Support (RFC 2665)
Yes
Yes
Yes
DOCSIS OSSI8 Objects Support (RFC 2233)
Yes
Yes
Yes
Dynamic Ranging Support
Yes
Yes
Yes
Enhanced Modem Status Display
Yes
Yes
Yes
Enhanced Per-Modem Error Counter
Yes
Yes
Yes
Entity MIB, Phase 1
Yes
Yes
Yes
Interface Command Enhancements
Yes
Yes
Yes
Internal Modem Configuration File Editor
Yes
Yes
Yes
MIB Enhancements
Yes
Yes
Yes
Multicast BPI MIB
Yes
Yes
Yes
LinkUp/Down Traps Support (RFC 2233)
Yes
Yes
Yes
RF Interface MIB
Yes
Yes
Yes
Yes
Yes
Yes
SNMP Cable Modem Remote Query
Yes
Yes
Yes
MultimediaBidirectional PIM11
Yes
Yes
Yes
IP Multicast Load Splitting Across Equal-Cost Paths
Yes
Yes
Yes
IP Multicast over ATM12 Point-to-Multipoint Virtual Circuits
Yes
Yes
Yes
IP Multicast over Token Ring LANs
Yes
Yes
Yes
Stub IP Multicast Routing
Yes
Yes
Yes
Quality of ServiceDynamic Upstream Modulation
Yes
Yes
Yes
DOCSIS 1.0+13 QoS Enhancements
Yes
Yes
Yes
Downstream QoS Handling
Yes
Yes
Yes
Downstream Traffic Shaping
Yes
Yes
Yes
Dynamic SID Support
Yes
Yes
Yes
Dynamic Map-Advance
Yes
Yes
Yes
Improved Upstream QoS
Yes
Yes
Yes
Multiple SID Support (static only)
Yes
Yes
Yes
Network-Based Application Recognition
12.1(10)EC
Yes
Yes
Yes
QoS Configuration
Yes
Yes
Yes
QoS Profile Enforcement
Yes
Yes
Yes
Read/Create Implementation of QoS
Yes
Yes
Yes
RTP14 Header Compression
Yes
Yes
Yes
Telco Return
No
No
Yes
Time of Day (ToD) Server
Yes
Yes
Yes
Upstream Address Verification
Yes
Yes
Yes
Upstream Traffic Shaping
Yes
Yes
Yes
SecurityAutomated Double Authentication
Yes
Yes
Yes
BPI Encryption
Yes
Yes
Yes
Cable Modem and Multicast Authentication using RADIUS15
Yes
Yes
Yes
Cisco IOS Firewall Enhancements
Yes
Yes
Yes
Dynamic Mobile Hosts
Yes
Yes
Yes
HTTP16 Security
Yes
Yes
Yes
Named Method Lists for AAA17 Authorization & Accounting
Yes
Yes
Yes
Per-Modem and Per-Host Access List Support
Yes
Yes
Yes
Per-User Configuration
Yes
Yes
Yes
Reflexive Access Lists
Yes
Yes
Yes
Secondary IP Support for BPI Operations
12.1(13)EC
Yes
Yes
Yes
Secure Shell
12.1(11b)EC
Yes
Yes
Yes
TFTP Enforce Support18
12.1(11b)EC1
Yes
Yes
Yes
Turbo Access Control Lists
Yes
Yes
Yes
Vendor-Proprietary RADIUS Attributes
Yes
Yes
Yes
SwitchingFast-Switched Policy Routing
Yes
Yes
Yes
VPNMPLS VPN Support for Subinterfaces and Interface Bundles
Yes
Yes
Yes
WAN OptimizationPAD19 Subaddressing
Yes
Yes
Yes
WAN ServicesBandwidth Allocation Control Protocol (BACP)
Yes
Yes
Yes
Enhanced Local Management Interface (ELMI)
Yes
Yes
Yes
Frame Relay Enhancements
Yes
Yes
Yes
Frame Relay MIB Extensions
Yes
Yes
Yes
Frame Relay Router ForeSight
Yes
Yes
Yes
ISDN20 Advice of Charge
Yes
Yes
Yes
ISDN Caller ID Callback
Yes
Yes
Yes
ISDN Multiple Switch Type
Yes
Yes
Yes
ISDN NFAS21
Yes
Yes
Yes
Microsoft Point-to-Point Compression (MPPC)
Yes
Yes
Yes
Yes
Yes
Yes
VPDN24 MIB and Syslog Facility
Yes
Yes
Yes
X.25 Enhancements
Yes
Yes
Yes
Yes
Yes
Yes
1 The number in the "In" column indicates the Cisco IOS release in which the feature was introduced. For example, 12.1(5)EC1 means that a feature was introduced in Cisco IOS Release 12.1(5)EC1. If a cell in this column is empty, the feature was included in the initial base release.
2 DHCP = Dynamic Host Configuration Protocol
3 DRP = Director Response Protocol
4 HSRP = Hot-Standby Routing Protocol
5 ISL = Inter-Switch Link
6 GRE = generic routing encapsulation
7 IGRP = Interior Gateway Routing Protocol
8 OSSI = Operations Support System Interface
9 SNMPv2 = Simple Network Management Protocol version 2
10 SNMPv3 = Simple Network Management Protocol version 3
11 PIM = Protocol Independent Multicast
12 ATM = Asynchronous Transfer Mode
13 The DOCSIS 1.0+ QoS Enhancements is a set of Cisco's Quality of Service extensions to DOCSIS 1.0 to enable basic VoIP service over the DOCSIS link before DOCSIS 1.1 becomes available. The main enhancements include support for dynamic creation and teardown of flows during voice calls, support for one new unsolicited grant service (UGS) slot scheduling mechanism for voice slots, and per IP-precedence rate shaping on the downstream.
14 RTP = Real-Time Transport Protocol
15 RADIUS = Remote Access Dial-In User Service
16 HTTP = Hypertext Transfer Protocol
17 AAA =authentication, authorization, and accounting
18 TFTP = Trivial File Transfer Protocol
19 PAD = packet assembler/disassembler
20 ISDN = Integrated Services Digital Network
21 NFAS = non-facility-associated signaling
22 BRI = Basic Rate Interface
23 PRI = Primary Rate Interface
24 VPDN = virtual private dial-up network
25 PVC = permanent virtual circuit
26 SVC = switched virtual circuit
New and Changed Information
The following sections list the new hardware and software features supported by the Cisco uBR7100 series routers for Cisco IOS Release 12.1 EC.
No New Hardware Features in Release 12.1(22)EC1
There are no new hardware features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(22)EC1.
No New Software Features in Release 12.1(22)EC1
There are no new software features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(22)EC1.
No New Hardware Features in Release 12.1(22)EC
There are no new hardware features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(22)EC.
No New Software Features in Release 12.1(22)EC
There are no new software features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(22)EC.
No New Hardware Features in Release 12.1(20)EC3
There are no new hardware features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(20)EC3.
No New Software Features in Release 12.1(20)EC3
There are no new software features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(20)EC3.
No New Hardware Features in Release 12.1(20)EC2
There are no new hardware features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(20)EC2.
No New Software Features in Release 12.1(20)EC2
There are no new software features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(20)EC2.
No New Hardware Features in Release 12.1(20)EC1
There are no new hardware features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(20)EC1.
No New Software Features in Release 12.1(20)EC1
There are no new software features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(20)EC1.
No New Hardware Features in Release 12.1(20)EC
There are no new hardware features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(20)EC.
No New Software Features in Release 12.1(20)EC
There are no new software features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(20)EC.
No New Hardware Features in Release 12.1(19)EC1
There are no new hardware features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(19)EC1.
No New Software Features in Release 12.1(19)EC1
There are no new software features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(19)EC1.
No New Hardware Features in Release 12.1(19)EC
There are no new hardware features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(19)EC.
No New Software Features in Release 12.1(19)EC
There are no new software features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(19)EC.
No New Hardware Features in Release 12.1(13)EC4
There are no new hardware features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(13)EC4.
No New Software Features in Release 12.1(13)EC4
There are no new software features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(13)EC4.
No New Hardware Features in Release 12.1(13)EC3
There are no new hardware features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(13)EC3.
No New Software Features in Release 12.1(13)EC3
There are no new software features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(13)EC3.
No New Hardware Features in Release 12.1(13)EC2
There are no new hardware features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(13)EC2.
No New Software Features in Release 12.1(13)EC2
There are no new software features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(13)EC2.
No New Hardware Features in Release 12.1(13)EC1
There are no new hardware features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(13)EC1.
No New Software Features in Release 12.1(13)EC1
There are no new software features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(13)EC1.
No New Hardware Features in Release 12.1(13)EC
There are no new hardware features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(13)EC.
New Software Features in Release 12.1(13)EC
Cisco IOS Release 12.1(13)EC supports the following new software feature for the Cisco uBR7100 series routers.
cable source-verify leasetimer Command
Cisco IOS Release 12.1(13)EC introduces the cable source-verify leasetimer <n> command.
The leasetimer option allows you to configure how often the timer checks the lease times, so as to specify the maximum amount of time a customer premises equipment (CPE) device can use an IP address that was previously assigned by the DHCP server but whose lease time has since expired. The time period can range from 1 minute to 240 minutes (4 hours), with a grace period of 2 minutes to allow a PC enough time to make a DHCP request to renew the IP address.
To turn off the timer, so that the CMTS no longer checks the lease times, issue the cable source-verify command without the dhcp option, or turn off the feature entirely with the no cable source-verify command. The leasetimer option takes effect only when the dhcp option is also used on an interface or subinterface.
The leasetimer option adds another level of verification by activating a timer that periodically examines the lease times for the IP addresses for known CPE devices. If the CMTS discovers that the DHCP lease for a CPE device has expired, it removes that IP address from its database, preventing the CPE device from communicating until it makes another DHCP request. This prevents users from treating DHCP-assigned addresses as static addresses, as well as from using IP addresses that were previously assigned to other devices.
Note
The leasetimer option for the cable source-verify command cannot be configured on subinterfaces. Instead, configure the command on the master interface, and the leasetimer will apply to all subinterfaces as well.
The following example shows how to enable the leasetimer feature so that every two hours, the CMTS checks the IP addresses in the CPE database for that particular interface for expired lease times:
router# configure terminalrouter#(config) interface c1/0router(config-if)# cable source-verify dhcprouter(config-if)# cable source-verify leasetimer 120For more information on the command, refer to the "Cisco Cable Modem Termination System Commands" chapter in the Cisco Broadband Cable Command Reference Guide at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/cable/bbccmref/bbcmts.htm
Secondary IP Support for BPI Operations
To support Baseline Privacy Interface (BPI) operations with cable modems (CMs) and customer premises equipment (CPE) devices that use secondary IP addresses, in Cisco IOS Release 12.1(13)EC, the Cisco CMTS maintains a database that links the known secondary IP addresses to the service IDs (SIDs) used by those devices. When the CMTS and CM need to renew their public keys, the CMTS uses this database to ensure that all IP addresses are sufficiently updated to allow proper routing and fast switching.
To manually clear the table of IP addresses for a particular SID, you can use the new clear cable secondary-ip command.
To display the list of known IP addresses per SID, you can use the new secondary-ip option for the show interface cable sid command.
For more information on the commands, refer to the "Cisco Cable Modem Termination System Commands" chapter in the Cisco Broadband Cable Command Reference Guide at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/cable/bbccmref/bbcmts.htm
No New Hardware Features in Release 12.1(12c)EC1
There are no new hardware features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(12c)EC1.
No New Software Features in Release 12.1(12c)EC1
There are no new software features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(12c)EC1.
No New Hardware Features in Release 12.1(12c)EC
There are no new hardware features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(12c)EC.
New Software Features in Release 12.1(12c)EC
Cisco IOS Release 12.1(12c)EC supports the following new software feature for the Cisco uBR7100 series routers.
Adding Load Information and a Timestamp to Show Commands
Cisco IOS Release 12.1(12c)EC adds a new command, exec prompt timestamp, that adds load information and a timestamp to all show commands. This can be useful for troubleshooting and system analysis.
The new command has the following syntax in line configuration mode:
Router(config-line)# [no] exec prompt timestampThe command has the following syntax in User EXEC mode, so that users who do not know the enable password can also timestamp their show commands:
Router> terminal [no] exec prompt timestampThe following example shows how to enable and disable the timestamp for the console connection:
Router# config tRouter(config)# line console 0Router(config-line)# exec prompt timestampRouter(config-line)# no exec prompt timestampThe following example shows how to enable and disable the timestamp for the first five telnet connections:
Router(config)# line vty 0 4Router(config-line)# exec prompt timestampRouter(config-line)# no exec prompt timestampThe following example shows how to enable and disable the timestamp when logged into User EXEC mode:
Router> terminal exec prompt timestampRouter> terminal no exec prompt timestampNo New Hardware Features in Release 12.1(11b)EC1
There are no new hardware features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(11b)EC1.
New Software Features in Release 12.1(11b)EC1
Cisco IOS Release 12.1(11b)EC1 supports the following new software feature for the Cisco uBR7100 series routers.
Support for the cable tftp-enforce Command
Cisco IOS Release 12.1(11b)EC1 adds support for the new cable tftp-enforce cable interface configuration command, which requires all cable modems on a cable interface to attempt a TFTP request for the DOCSIS configuration file through the cable interface with the Cisco uBR7100 series router before being allowed to register and come online. This can help prevent the following situations from occurring:
•
Users who attempt theft-of-service by reconfiguring their local networks to allow the downloading of an unauthorized DOCSIS configuration file from a local TFTP server. Typically, some users do this to obtain services that they have not paid for, such as higher guaranteed bandwidths or a higher priority Quality of Service (QoS) profile.
•
Some brands or models of cable modems might be running older software releases that cache the DOCSIS configuration file and use the cached version instead of downloading the actual file from a TFTP server during the registration process. Although this can marginally speed up the registration process, it also violates the DOCSIS requirements and could create a situation in which the cable modem is not using the proper DOCSIS configuration file. A user might then be mistakenly accused of theft-of-service, when in reality the problem is the non-DOCSIS-compliant cable modem.
The cable tftp-enforce command identifies these situations and can block these cable modems from registering and coming online. This command also has an option that allows these cable modems to come online, but it also identifies the cable modems so that the network administrators can investigate the situation further before taking any action.
Command Syntax
The new command has the following syntax:
cable tftp-enforce [mark-only]no cable tftp-enforce [mark-only]When the command is used without the mark-only option, cable modems that do not download a TFTP file are blocked from registering and coming online. The mark-only option allows the cable modems to come online, but it also prints a warning message and marks the cable modems in the show cable modem command.
Tips
Cisco recommends that you initially configure cable interfaces with the mark-only option, so that potential problems are identified without initially interfering with users' ability to come online. After you identify and resolve these initial problems, reconfigure the cable interfaces without the mark-only option to block problem cable modems that attempt to come online without downloading a valid DOCSIS configuration file through the cable interface.
The default behavior is not to require the TFTP download through the Cisco uBR7100 series router. You must configure this command on the cable interface to require the TFTP download.
Enforcing TFTP Downloads and Blocking Non-Compliant Cable Modems
The following example shows how to enforce TFTP downloads for all of the cable modems on cable interface 1/0. These cable modems must attempt a TFTP download of the DOCSIS configuration file through their cable interface with the Cisco uBR7100 series router. If they do not, they are not allowed to register or come online.
Router# configure terminalRouter(config)# interface cable 1/0Router(config-if)# cable tftp-enforceRouter(config-if)# exitRouter(config)#When the cable tftp-enforce command is configured, the following message is displayed on the console when a cable modem attempts to register without first attempting a TFTP download through the cable interface with the Cisco uBR7100 series router:
06:53:57: %UBR7100-4-REGISTRATION_BEFORE_TFTP: Registration request unexpected:Cable Modem did not attempt TFTP. Registration Rejected. CM Mac Addr <00ff.ff66.12fb>When a cable modem is rejected for not attempting a TFTP download, it is marked as having a Message Integrity Check (MIC) failure—reject(m)—in the show cable modems command.
Router# configure terminalRouter(config)# interface cable 1/0Router(config-if)# cable tftp-enforceRouter(config-if)# exitRouter(config)#Router# show cable modemsInterface Prim Online Timing Rec QoS CPE IP address MAC addressSid State Offset PowerCable1/0/U1 1 online(pt) 2734 0.50 5 0 10.1.1.38 00ff.fffa.0a35Cable1/0/U0 2 online(pt) 2729 0.25 5 0 10.1.1.50 00ff.ff07.382fCable1/0/U0 3 init(i) 2732 0.25 2 0 10.1.1.48 00ff.ff03.307dCable1/0/U1 4 online(pt) 2737 0.75 5 0 10.1.1.34 00ff.ff59.4477Cable1/0/U1 5 reject(m) 2215 0.25 2 0 10.1.1.47 00ff.ff66.12fbRouter#
Note
DOCSIS-compliant cable modems that are rejected with a MIC failure go into the offline state for a short period of time and then retry the registration process.
The debug cable registration command can be used to display additional information:
Router# debug cable interface c1/0 verboseRouter# debug cable registrationCMTS registration debugging is onJun 6 23:27:15.859: Registration request from 00ff.ff66.12fb, SID 7 on Cable1/0/U1Jun 6 23:27:15.859: Found a network access control parameter: OkJun 6 23:27:15.859: Found a class of service block: OkJun 6 23:27:15.859: Found Baseline Privacy config: OkJun 6 23:27:15.859: Found Max CPE: OkJun 6 23:27:15.859: Found CM MIC: OkJun 6 23:27:15.859: Found CMTS MIC: OkJun 6 23:27:15.859: Found modem ip: OkJun 6 23:27:15.859: Found modem capabilities: OkJun 6 23:27:15.859: Finished parsing REG RequestJun 6 23:27:15.859: Cable Modem sent Registration Request without attemptingrequired TFTP22:33:21 %UBR7100-4-REGISTRATION_BEFORE_TFTP: Registration request unexpected:Cable Modem did not attempt TFTP. Registration Rejected. CM Mac Addr <00ff.ff66.12fb>Registration failed for Cable Modem 00ff.ff66.12fb on interface Cable1/0/U0:CoS/Sflow/Cfr/PHS failed in REG-REQJun 6 23:27:15.859: REG-RSP Status : failure (2)Jun 6 23:27:15.859: Registration Response:Jun 6 23:27:15.859: 0x0000: C2 00 00 1B 00 00 00 50 73 4E B4 19 00 05 00 E0Jun 6 23:27:15.859: 0x0010: 56 AC 00 09 00 00 03 01 07 00 00 02 02Jun 6 23:27:15.859: Registration Response TransmittedIdentifying Non-Compliant Cable Modems But Allowing Them to Come Online
The mark-only option of the cable tftp-enforce command allows CMs that do not attempt a TFTP download through the cable interface to come online, but the Cisco uBR7100 series router displays a warning message on the console and marks the cable modem in the show cable modem command with a pound sign (#). This option allows network providers to identify potential problems and to investigate them before taking any corrective action.
When the mark-only option is configured, the following message is displayed on the console when a cable modem attempts to register without first attempting a TFTP download through the cable interface with the Cisco uBR7100 series router:
06:53:57: %UBR7100-4-REGISTRATION_BEFORE_TFTP: Registration request unexpected:Cable Modem did not attempt TFTP. Modem marked with #. CM Mac Addr <00ff.ff66.12fb>In addition, the cable modem is marked with a pound sign (#) in the show cable modems command:
Router# configure terminalRouter(config)# interface cable 1/0Router(config-if)# cable tftp-enforce mark-onlyRouter(config-if)# exitRouter(config)#Router# show cable modemsInterface Prim Online Timing Rec QoS CPE IP address MAC addressSid State Offset PowerCable1/0/U1 1 online(pt) 2734 0.50 5 0 10.1.1.38 00ff.fffa.0a35Cable1/0/U0 2 online(pt) 2729 0.25 5 0 10.1.1.50 00ff.ff07.382fCable1/0/U0 3 init(i) 2732 0.25 2 0 10.1.1.48 00ff.ff03.307dCable1/0/U1 4 online(pt) 2737 0.75 5 0 10.1.1.34 00ff.ff59.4477Cable1/0/U1 5 #online 2213 0.25 6 0 10.1.1.47 00ff.ff66.12fbRouter#The debug cable registration command can be used to display additional information:
Jun 6 23:27:15.859: Registration request from 00ff.ff66.12fb, SID 7 on Cable1/0/U1Jun 6 23:27:15.859: Found a network access control parameter: OkJun 6 23:27:15.859: Found a class of service block: OkJun 6 23:27:15.859: Found Baseline Privacy config: OkJun 6 23:27:15.859: Found Max CPE: OkJun 6 23:27:15.859: Found CM MIC: OkJun 6 23:27:15.859: Found CMTS MIC: OkJun 6 23:27:15.859: Found modem ip: OkJun 6 23:27:15.859: Found modem capabilities: OkJun 6 23:27:15.859: Finished parsing REG RequestJun 6 23:27:15.859: Cable Modem sent Registration Request without attemptingrequired TFTP23:27:15: %UBR7100-4-REGISTRATION_BEFORE_TFTP: Registration request unexpected:Cable Modem did not attempt TFTP. Modem marked with #. CM Mac Addr <00ff.ff66.12fb>Jun 6 23:27:15.859: Sec sids obtained for all requested classes of serviceJun 6 23:27:15.859: Performing connection admission control (CAC) for each SidJun 6 23:27:15.859: CAC Status for ClassID:1 is CAC_SUCCESSJun 6 23:27:15.859: Registration Status: ok (0)Jun 6 23:27:15.859: Registration Response TransmittedEXEC Commands in Configuration Mode
In Cisco IOS Release 12.1(11b)EC1, you can issue EXEC-level Cisco IOS commands (such as show, clear, and debug commands) from within global configuration mode or other configuration modes by issuing the do command followed by the EXEC command.
For example, you can display the run-time configuration file from within global configuration mode by issuing the following command:
Router(config)# do show running-config
Note
You cannot use the do command to execute the configure terminal EXEC command because issuing the configure terminal command changes the mode to configuration mode.
New Hardware Features in Release 12.1(11b)EC
Cisco IOS Release 12.1(11b)EC supports the following new hardware features in Cisco uBR7100 series routers.
PA-A3-E3 Port Adapter
The PA-A3-E3 is a single-width, single-port E3 ATM, PCI-based port adapter that uses an E3 interface with a coaxial cable BNC connector.
Note
For configuration information on the PA-A3-E3 port adapter, see the
PA-A3 Enhanced ATM Port Adapter Installation and Configuration guide, which is available on Cisco.com and the Customer Documentation CD-ROM.
New Software Features in Release 12.1(11b)EC
Cisco IOS Release 12.1(11b)EC supports the following new software features for the Cisco uBR7100 series routers.
Secure Shell Support
Secure Shell (SSH) allows network administrators to securely log in to the Cisco uBR7100 series router, using authentication and encryption at the application layer, providing a secure connection even when logging in over insecure networks such as the Internet. This allows an administrator to securely monitor and configure a router without having to be logged into the router's local console port or directly connected to the Ethernet port onboard the router's network processing engine.
To configure SSH on the Cisco uBR7100 router, use the following command in global configuration mode:
uBR7100(config)#crypto key generate rsa general-keys
Note
When you are asked the size of the key seed, enter a value of at least 1024.
To verify whether SSH is configured on the Cisco uBR7100 router, use the following command in Privileged EXEC mode:
uBR7100#show ip sshSSH Enabled - version 1.5Authentication timeout: 120 secs; Authentication retries: 3To verify whether the Cisco uBR7100 router has an SSH connection, use the following command in Privileged EXEC mode:
uBR7100#show sshConnection Version Encryption State Username1 1.5 DES Session started adminCable Intercept Supports Multiple Hops
In previous software releases, the data collection system that collects the output of the cable intercept command had to be within two hops of the Cable Modem Termination System (CMTS). Cisco IOS Release 12.1(11b)EC removes this limitation.
Show Cable Modem Summary Command Enhanced
In Cisco IOS Release 12.1(11b)EC, the show cable modem summary commands now display the Description that the user configured for the interface, if any.
The following shows typical output with the Description field:
Router# show cable modem summaryInterface Total Active Registered DescriptionModems Modems ModemsCable1/0/U0 165 141 141 Line 32/1Cable1/0/U1 209 172 170 Line 32/2Cable1/0/U2 262 207 203 Line 32/3Cable1/0/U3 256 194 188 Line 32/4Show Interface Cable Command Enhanced
In Cisco IOS Release 12.1(11b)EC, the show interface cable sid command now includes a new option, association, that displays the name of the virtual interface that has been configured for Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) operation.
The following shows typical output for the association option:
Router# show interface cable5/0 sid associationSid Prim Online IP Address MAC Address Interface VRF Name1 online 195.151.129.20 0003.e38f.e993 Ca1/0.50 green2 online 195.151.129.17 0003.e38f.e89d Ca1/0.50 green3 init(t) 195.151.129.12 00d0.baa2.fb93 Ca1/0.50 greenNo New Hardware Features in Release 12.1(10)EC1
There are no new hardware features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(10)EC1.
No New Software Features in Release 12.1(10)EC1
There are no new hardware features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(10)EC1.
New Hardware Features in Release 12.1(10)EC
The following are the new hardware features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(10)EC.
PA-T3+ and PA-2T3+ Port Adapters
The PA-T3+ and PA-2T3+ port adapters provide full-duplex operation at the T3 (45 Mbps) speed. They support both 16- and 32-bit cyclic redundancy checks (CRCs), with the default being 16-bit CRCs. The PA-T3+ port adapter provides one port, and the PA-2T3+ port adapter provides two ports.
Cisco IOS Release 12.1(10)EC supports the PA-T3+ and PA-2T3+ port adapters on the Cisco uBR7100 series universal broadband routers. These port adapters are replacements for the PA-T3 and PA-2T3 port adapters, which have reached their end-of-life.
Note
For configuration information on the PA-T3+ and PA-2T3+ port adapters, see the PA-T3+ Serial Port Adapter Installation and Configuration Guide, which is available on Cisco.com and the Customer Documentation CD-ROM.
New Software Features in Release 12.1(10)EC
The following new software features are supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(10)EC.
Cisco IOS Network-Based Application Recognition
Cisco IOS Release 12.1(10)EC adds support for Cisco IOS Network-Based Application Recognition (NBAR). The NBAR feature is a new classification engine that can recognize a wide variety of network applications, including Web-based applications, client/server applications, and other difficult-to-classify protocols that dynamically assign TCP or UDP port numbers.
NBAR enhances existing methods of application-recognition by adding several new classification features:
•
Classification of applications that use statically assigned TCP/UDP port numbers, that use dynamically assigned TCP/UDP port numbers, or that use protocols other than TCP and UDP
•
Classification of HTTP traffic by URL, host, or MIME type
•
Classification of Citrix ICA traffic by application name
•
Classification of application traffic using subport information
NBAR can also classify static port protocols. Although access control lists (ACLs) can also be used for this purpose, NBAR is easier to configure and can provide other options and classification statistics that are not available when using ACLs.
Tips
The Cisco IOS NBAR feature requires CPU resources to inspect, recognize, and process the packets coming through the router. In laboratory conditions, the use of NBAR can impact CPU performance by approximately 30 percent—the actual performance impact depends on the current CPU load, the number of packets processed, and the type of traffic being inspected. To limit the performance impact when using NBAR, activate the Turbo ACL feature to increase the performance of access list handling.
After NBAR recognizes an application, the Cisco uBR7100 series router can invoke specific services appropriate for that application. These services can provide QoS features such as:
•
Guaranteed bandwidth
•
Bandwidth limits
•
Traffic shaping
•
Packet coloring
The Cisco IOS NBAR feature can also be used to detect and respond to denial-of-service and other types of network attacks. Cisco IOS NBAR uses a protocol description language module (PDLM) to define the rules by which the NBAR processes recognize an application. New PDLM definitions can usually be loaded without the need for a Cisco IOS software upgrade or a router reboot, allowing for a rapid response to discovered attacks.
Note
For basic information on configuring and using the Cisco IOS NBAR feature, see the Network-Based Application Recognition documentation. For information on configuring NBAR for Quality of Service (QoS) control, see the Configuring Network-Based Application Recognition chapter in the Cisco IOS Release 12.2 Quality of Service Solutions Configuration Guide. These documents are available on Cisco.com and the Customer Documentation CD-ROM.
Tips
Cisco.com also contains a technical note, Using Network-Based Application Recognition and Access Control Lists for Blocking the Code Red Worm, that provides information on using NBAR to block denial-of-service attacks. This technical note is available at http://www.cisco.com/warp/public/63/nbar_acl_codered.shtml.
Updates to the cable map-advance and show cable modem Commands
Cisco IOS Release 12.1(10)EC updates the cable map-advance command with a new option, max-delay. The new command syntax is the following:
cable map-advance [dynamic [safety] | static] [max-delay]
The max-delay option specifies the maximum round trip delay between the cable plant and furthest cable modem in microseconds. The valid range is 100 to 2000 microseconds. The typical delay for a mile of coaxial cable is approximately 7 microseconds. The typical delay for a mile of fiber cable is approximately 8 microseconds.
A cable modem will not be allowed to exceed the maximum timing offset given by the max-delay value (in static mode) or given by the combination of the max-delay and safety values (in dynamic mode). If a cable modem reports a timing offset beyond the maximum value, the CMTS will reset its offset to the maximum value and put an exclamation point (!) next to its offset value in the show cable modem display.
In dynamic MAP operation, Cisco IOS 12.1(10)EC also implements a regular polling of the furthest CM, to determine if that CM is now offline. If the furthest CM has gone offline, the CMTS scans the currently online CMs to determine which is now the furthest offline and updates the dynamic MAP advance algorithm with the new value.
Tip
The show cable modem command displays the CM timing offset in DOCSIS ticks. Use the following method to convert microseconds to DOCSIS ticks: ticks = microseconds*64/6.25.
No New Hardware Features in Release 12.1(9)EC
There are no new hardware features supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(9)EC.
New Software Features in Release 12.1(9)EC
The following new software features are supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(9)EC.
Turbo Access Control Lists
Cisco IOS Release 12.1(9)EC adds support for Turbo Access Control Lists (Turbo ACL), which increases the performance of access lists by compiling them into a form that is more quickly accessed during packet processing. The access-list compiled command enables the Turbo ACL feature, and the show access-lists and show access-lists compiled commands provide status information about these access lists.
Complete information about the Turbo ACL feature is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/dttacl.htm. The related commands are also described in the Addressing and Services volume of the Cisco IOS Release 12.1 IP and IP Routing Command Reference. For complete information about access lists, see the Traffic Filtering and Firewall volume in the Cisco IOS Release 12.1 Security Configuration Guide.
Note
The Turbo ACL feature was introduced in Cisco IOS Release 12.1(9)EC but was unusable because of caveats CSCdv04414 and CSCdv69271. These caveats have been resolved in Cisco IOS Release 12.1(10)EC.
New Hardware Features in Release 12.1(8)EC
The following new hardware features are supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(8)EC:
Port Adapters
Cisco IOS Release 12.1(8)EC adds support for the following port adapters: PA-MC-2T1, PA-MC-4T1, PA-2FE-TX, PA-2FE-FX, and PA-A3-8T1/IMA.
New Software Features in Release 12.1(8)EC
The following new software features are supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(8)EC.
Enhancements to CISCO-DOCS-EXT-MIB
The new version of the CISCO-DOCS-EXT-MIB, dated 10/07/2001, has the following changes:
The following attributes are added to cdxCmtsCmStatusExtTable:
•
cdxIfCmtsCmStatusOnlineTimesNum—Specifies the number of times that the CM changes its connectivity state from 'offline' to 'online' over the time period from the modem's first ranging message received by CMTS until now. The value of this object is reset to 0 if the value in cdxIfCmtsCmStatusLastResetTime is changed. This attribute has a new syntax type, CdxResettableCounter32.
•
cdxIfCmtsCmStatusLastResetTime—Specifies the timestamp for the last time that the cable modem connectivity statistics were reset. If the value of this object is '0', then the cable modem connectivity statistics had not been reset.
•
The cdxDocsExtComplianceRev6 attribute has been replaced by cdxDocsExtComplianceRev7.
•
The cdxCmtsCmCpeGroupRev4 attribute has been replaced by cdxCmtsCmCpeGroupRev5.
SNMP Enhancements
The following attributes have been added to CISCO-DOCS-EXT-MIB to provide information about the Unsolicited Grant Service (UGS) allocation on the upstream interfaces:
•
"cdxIfUpChannelNumActiveUGS" returns the the number of active UGS flows currently allocated on the upstream.
•
"cdxIfUpChannelMaxUGSInLastOneHour" returns the maximum number of UGS flows allocated on the upstream in the last hour.
•
"cdxIfUpChannelMinUGSInLastOneHour" returns the minimum number of UGS flows allocated on the upstream in the last hour.
•
"cdxIfUpChannelAvgUGSInLastOneHour" returns the average number of UGS flows allocated on the upstream in the last hour.
•
"cdxIfUpChannelMaxUGSInLastFiveMins" returns the maximum number of UGS flows allocated on the upstream in the last five minutes.
•
"cdxIfUpChannelMinUGSInLastFiveMins" returns the minimum number of UGS flows allocated on the upstream in the last five minutes.
•
"cdxIfUpChannelAvgUGSInLastFiveMins" returns the average number of UGS flows allocated on the upstream in the last five minutes.
New Hardware Features in Release 12.1(7)EC
The following new hardware features are supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(7)EC.
EuroDOCSIS Models
Cisco IOS Release 12.1(7)EC adds support for the EuroDOCSIS models (Cisco uBR7111E and Cisco uBR7114E) of the Cisco uBR7100 series routers.
Port Adapters
Cisco IOS Release 12.1(7)EC adds support for the following port adapters: PA-E3, PA-T3, PA-2E3, PA-2T3, PA-4E1G-75, PA-4E1G-120, and PA-POS-OC3SMI.
New Software Features in Release 12.1(7)EC
The following new software features are supported by the Cisco uBR7100 series routers in Cisco IOS Release 12.1(7)EC.
MxU Bridging
The Multi-Dwelling Unit (MDU) and Multi-Tenant Unit (MTU) Bridging (MxU Bridging) feature supports transparent bridging and integrated routing and bridging (IRB) between the cable interfaces and the Fast Ethernet interfaces of a Cisco uBR7100 series routers.
Note
You cannot use Point-to-Point Protocol over Ethernet (PPPoE) sessions on the Cisco uBR7100 series router in MxU bridged mode. PPPoE is not supported in the Cisco IOS Release 12.1 EC train for the Cisco uBR7100 series routers.
Note
Bridging is not supported on a Telco return path, nor on a cable subinterface.
No New Hardware Features in Release 12.1(6)EC
There are no new hardware features introduced in Cisco IOS Release 12.1(6)EC.
No New Software Features in Release 12.1(6)EC
There are no new software features introduced in Cisco IOS Release 12.1(6)EC.
New Hardware Features in Release 12.1(5)EC1
Cisco IOS Release 12.1(5)EC1 supports model Cisco uBR7111 and model Cisco uBR7114 of the Cisco uBR7100 series universal broadband routers.
New Software Features in Release 12.1(5)EC1
The following software features have been inherited from Cisco IOS Release 12.1(4)EC and earlier 12.1 EC releases for the Cisco uBR7200 series routers and are supported by the Cisco uBR7100 series routers in Release 12.1(5)EC1.
Cable Downstream Frequency Override CLI
The following CLI command turns off the cable downstream frequency override on a per-interface basis:
[no] cable downstream override
The default configuration enables the cable downstream frequency override. Only the [no] cable downstream override command is displayed and allows the cable downstream frequency override to be turned off.
Cable Interface Setup Facility
The cable interface setup facility is an alternative mechanism to enable or configure Cisco uBR7100 series parameters. The setup facility supports automated configuration of upstream parameters.
In earlier releases, upstream ports were put in a default shut-down state after the setup facility was run. You had to use the CLI to configure a fixed frequency or create a spectrum group, assign an interface to it, and enable each upstream port on a cable interface line card. The setup facility now supports configuring and enabling upstream parameters.
In the following example for a Cisco uBR7100 series router, the upstream parameters for a cable interface line card in slot 1 are configured and enabled. Press Return to accept the default.
Do you want to configure Cable 1/0 interface? [no]: yes Downstream setting frequency: 531000000 For cable upstream [0] Shut down this upstream? [yes/no]: no Frequency: 33808000 Would you like to configure the DHCP server? [yes/no]: yes IP address for the DHCP server [X.X.X.X]: 10.0.0.2 Configure IP on this interface? [yes]: IP address for this interface [10.20.133.65]: Subnet mask for this interface [255.0.0.0]: 255.255.255.248 Class A network is 10.0.0.0, 29 subnet bits; mask is /29In this example, the previous input generates the following command interface script:
interface Cable 1/0 no shutdown cable downstream frequency 531000000 no shutdown cable downstream modulation 64qam cable downstream annex B cable downstream interleave-depth 32 no cable upstream 0 shutdown cable upstream 0 frequency 33808000 cable helper-address 10.0.0.2 ip address 10.20.133.65 255.255.255.248
Note
Cable modems or set-top boxes with integrated cable modems are brought online after the utility is run.
Note
For Dynamic Host Configuration Protocol (DHCP)/time of day (ToD)/Trivial File Transfer Protocol (TFTP), a static route must exist to the host.
Cable Monitor
The cable monitor feature allows administrators to filter a selection of MAC messages; map messages and data packets to access lists, MAC-address numbers, and upstream port numbers; enable time stamping of each packet; and permit the option of stripping away the DOCSIS header for data packets. This makes it easier to resolve interoperability issues, understand network issues that can affect application performance and functionality, and increase the ability to manage network variables.
The configuration CLI consists of the following sniffer commands (enter configuration commands, one per line, and end with CNTL-Z):
Router(config-if)# cable monitor [outbound | incoming] [timestamp] interface <interface> {access-list <name | number> | sid <n> | mac-addr <address> | upstream <n>}[packet-type {mac [type {map-req | map-grant | dsa | dsc | dsd ... }] | data packet-header {ethernet | docsis}}]
For more information on the command-line interface (CLI) and for syntax descriptions, see the Broadband Command Consolidation. The "Platform-Specific Documents" section provides details on how to access that document.
"cdxCmtsCmOnOffTrapEnable" Enhancement
The following new CLI commands are supported for the "cdxCmtsCmOnOffTrapEnable" object:
[no] cable enable-trap cmonoff-notification
[no] cable enable-trap cmonoff-interval <time 0 to 86400>These commands have the following default settings:
no cable enable-trap cmonoff-notification
no cable enable-trap cmonoff-intervalAfter the default setting has been changed and the new configuration has been saved, the new configuration will remain active after the CMTS reloads.
Syntax examples:
•
cable enable-trap cmonoff-notification—This command enables "cdxCmtsCmOnOffNotification" in the RF MAC interface. Alternatively, you can set the SNMP object "cdxCmtsCmOnOffTrapEnable" to true (1).
•
no cable enable-trap cmonoff-notification—This command disables "cdxCmtsCmOnOffNotification" in the RF MAC interface. Alternatively, you can set the SNMP object "cdxCmtsCmOnOffTrapEnable" to false (2).
•
cable enable-trap cmonoff-interval <time 0 to 86400>—This command sets the interval for "cdxCmtsCmOnOffNotification" sent by the CMTS for one online/offline CM state change when "cdxCmtsCmOnOffTrapEnable" is set to true (1). Alternatively, you can set the SNMP object "cdxCmtsCmOnOffTrapInterval" to the same time value.
•
no cable enable-trap cmonoff-interval—This command sets the interval "cdxCmtsCmOnOffNotification" to 0 so that "cdxCmtsCmOnOffNotification" will be sent for every online/offline CM state change when "cdxCmtsCmOnOffTrapEnable" is set to true (1). Alternatively, you can set the SNMP object "cdxCmtsCmOnOffTrapInterval" to 0.
Note
The default for "cdxCmtsCmOnOffTrapInterval" is 0.
Configurable Alternate Termination System Information Messages
The registration IP address that is included in Termination System Information messages is configurable for telco return. With the cable telco-return registration-ip command, you can configure an alternate IP address to which the cable telco-return modem can send its registration requests.
DOCS-EXT-MIB Enhancements
DOCS-EXT-MIB has been modified to include the capability of counting the number of cable modems on an upstream as well as on each line card:
•
"cdxIfUpChannelCmTotal", "cdxIfUpChannelCmActive", and "cdxIfUpChannelCmRegistered" have been added to "cdxIfUpstreamChannelExtTable" to report the total number of active, registered, cable modems connected on an upstream.
•
"cdxCmtsCmTotal", "cdxCmtsCmActive", and "cdxCmtsCmRegistered" have been added to "cdxCmtsMacExtTable" to report the total number of active, registered, cable modems on a cable MAC interface since boot-up.
DOCSIS Ethernet MIB Objects Support (RFC 2665)
Support for RFC 2665, the latest revision of the Ethernet MIB, is now mandatory for DOCSIS compliance.
The key changes are as follows:
•
Two new objects in "dot3StatsTable" of RFC 2665 are supported:
–
dot3StatsSymbolErrors
–
dot3StatsDuplexStatus
•
Two new tables in RFC 2665 are not supported:
–
dot3ControlTable
–
dot3PauseTable
•
Also, "dot3CollTable" is not supported
DOCSIS OSSI Objects Support (RFC 2233)
Cisco uBR7100 series routers support the required objects in RFC 2233 for DOCSIS Operations Support System Interface (OSSI) compliance.
•
IF-MIB.my is updated to match RFC 2233
•
The new object "ifCounterDiscontinuityTime" is now supported
Dynamic Map-Advance
The Dynamic Map-Advance feature improves the upstream throughput for a cable modem. This feature enables the map-advance to be dynamic and self-adjusting to propagation delay, even for the furthest cable modem in the plant.
Dynamic Mobile Hosts
This feature addresses a security hole that occurs when the Cisco uBR7100 series router supports mobile hosts. (Mobile hosts are hosts that can move from one modem to another modem.) Anyone who knows the MAC address of a mobile host can "fake" the mobile host, thereby causing denial of access for the real mobile host.
To avoid this security hole, the Dynamic Mobile Hosts feature pings the mobile host on the old SID to verify that the host has indeed been moved.
Dynamic Ranging Support
The functionality of the clear cable modem <mac-address> reset command is extended to send a "Ranging Abort" message instead of just removing the SID.
A new modem state—Reset (display: resetting)— has been introduced into the modem state list. A modem is deprovisioned when moving into this state as if going offline. Move the modem to the Continue Ranging list. If a ranging request is received from the modem, send a "Ranging Abort" message. Continue until an "Initial Ranging" message is received or until normal timeout (16 attempts). If the modem does not go back to initial ranging, set it to offline.
The Reset modem state may show as follows in the output of show cable modem:
Cable1/0/U1 80 resetting 3575 0.25 3 0 10.30.160.26 0050.7318.e965This is an intermediate state. A modem will not be in this state for more than a few seconds. If the modem does not respond, it may remain in this state for up to 30 seconds. The subsequent modem state is offline.
Dynamic Upstream Modulation
The Dynamic Upstream Modulation feature reduces the risks associated with transitioning to QAM16 modulation in the return path, and provides assurance that subscribers remain online and connected during periods of return-path impairments.
This new feature actively monitors the signal-to-noise-ratio (SNR) and forward error correction (FEC) counters in the active return path of each upstream port. The software tracks whether the current upstream channel signal quality can adequately support the higher modulation scheme configured, and proactively adjusts to the more robust quadrature phase-shift keying (QPSK) modulation scheme when necessary. When return-path spectrum conditions improve, the software proactively returns the upstream channel to the higher-modulation quadrature amplitude modulation (QAM) scheme. This is done through modulation profiles supported in Cisco IOS, which can be configured in a variety of ways to support the unique environment at each user's facility.
The Dynamic Upstream Modulation feature can be configured on interfaces with fixed upstream frequencies or on interfaces with spectrum groups assigned. Cisco IOS provides one preconfigured modulation profile resident in memory, which defines a typical profile for QPSK modulation. In order to use the Dynamic Upstream Modulation feature, a second profile must be created that is unique from the first profile and typically provides a higher modulation scheme.
The following CLI is the only configuration required:
cable upstream <n> modulation-profile <primary profile-number> <secondary profile-number>.For more information on the Dynamic Upstream Module feature, including information on creating modulation profiles using the cable modulation-profile command, see the Cisco uBR7200 Dynamic Upstream Modulation feature module. For information on creating spectrum groups using the cable spectrum-group command, see the Broadband Command Consolidation. The "Platform-Specific Documents" section provides details on how to access that document.
Enhanced Per-Modem Error Counter
The Cisco uBR7100 series supports display of per-modem error counters. A new command introduced is:
show cable modem [<ip-addr> | <mac-addr>] error
Sample display:
cmts# show cable modem errorsMAC Address SID I/F CRC HCS00d0.ba26.eee7 1 Cable1/0/U0 0 0
Note
Both the Cyclic Redundancy Check (CRC) and Header Check Sum (HCS) are on a per-CM basis.
Internal Modem Configuration File Editor
This feature adds support for internal cable modem configuration file storage and generation. The cable modem configuration file is generated and stored as part of CLI configuration. Configuration files are not stored in Flash memory.
"MAX-CPE" CLI Override
A new cable-specific configuration command has been added:
[no] cable modem max-cpe [<n> | unlimited]
When set to unlimited or if n is larger than the "MAX-CPE" value in the config file of a cable modem, it overrides the config file value.
MPLS VPN Support for Subinterfaces and Interface Bundles
Cisco IOS Release 12.1(5)EC1 and later releases include MPLS support as part of its VPN offerings for cable subinterfaces and interface bundles. The software offers enhancements made to tags placed on the fronts of packets that contain forwarding information used to make switching decisions for cable interfaces and bundles. This tag switching infrastructure combines advanced routing protocol capabilities to define IP VPNs by selectively advertising IP reachability information to just those subscribers within the same VPN or extranet on a cable interface.
The MPLS-VPN approach of creating VPNs for individual Internet service providers (ISPs) requires subinterfaces to be configured on cable interfaces or bundles. One subinterface is required for each ISP. The subinterfaces are tied to VPN Routing Forwarding (VRF) tables for respective ISPs.
For more feature information, refer to the Cisco uBR7200 Series MPLS VPN Cable Enhancements feature module. For information on feature modules, see the "Feature Modules" section.
Note
The cable source-verify [dhcp] cable interface command specifies that DHCP lease-query requests are sent to verify any unknown source IP address found in upstream data packets. This feature requires a DHCP server that supports the new LEASEQUERY message type.
Multicast BPI MIB Support
Because a multicast SID on CMTS is determined until the CMTS receives an Internet Group Management Protocol (IGMP) join request from a host, the following limitations apply to "docsBpiIpMulticastServiceId" and "docsBpiMulticastServiceId":
•
docsBpiIpMulticastServiceId
–
read-only
–
zero is its value when no SID is assigned to it
–
zero is its value when its sibling "docsBpiIpMulticastPrefixLength" is less than 32
•
docsBpiMulticastServiceId
–
value must derive from multicast SIDs created when the CMTS handled IGMP join requests
Link Up/Down Traps Support (RFC 2233)
The objects in the varbind list, based on the Internet Engineering Task Force (IETF) standard, are defined in IF-MIB. Because IF-MIB supports subinterfaces, all objects in this varbind list are also supported for subinterfaces. The feature allows you to base the Link Up/Down trap varbind list on a Cisco-specific or IETF standard with a new CLI configuration command:
snmp-server link-trap [cisco | ietf]
The default is a Cisco-specific link trap (snmp-server link-trap cisco). You can switch between Cisco and IETF standard.
Overlapping Subinterface IP Addresses
Multiprotocol Label Switching (MPLS)-based Virtual Private Networks (VPNs), which are created in Layer 3, provide privacy and security by constraining the distribution of a VPN's routes to those routers that are members of the VPN only, and by using MPLS forwarding. Each ISP's VPN is insulated from all others sharing the HFC and IP-over-cable infrastructure. MPLS VPN enforces traffic separation by assigning a unique VPN Routing/Forwarding (VRF) instance to each VPN. A VRF instance consists of an IP routing table, a derived forwarding table, a set of interfaces that use the forwarding table, and a set of rules and routing protocols that determine what is in the forwarding table.
Earlier Cisco IOS releases assumed that IP addresses were unique, but it is possible with an MPLS VPN to configure overlapped IP addresses within a VRF. A configuration of overlapped IP addresses could have caused errors. Cisco IOS Release 12.1(5)EC1 and later releases support a configuration of overlapping IP addresses for subinterfaces. The same IP subnet can be configured for CPEs on different VRFs using a Cisco uBR7100 series router to configure an MPLS VPN. See also the "MPLS VPN Support for Subinterfaces and Interface Bundles" section.
The following CLI commands have been updated in Cisco IOS Release 12.1(5)EC1 to support overlapping IP addresses on subinterfaces:
•
Old CLI commands:
cable host <ipaddr> [no] access-group <acl>
cable device <ipaddr> [no] access-group <acl>
show cable host <ipaddr> access-group
show cable device <ipaddr> access-group
clear cable host <ipaddr>•
New CLI commands:
cable host [vrf <vrfname>] <ipaddr> [no] access-group <ac >
cable device [vrf <vrfname> <ipaddr> [no] access-group <acl>
show cable host [vrf <vrfname>] <ipaddr> access-group
show cable device [vrf <vrfname>] <ipaddr> access-group
clear cable host [vrf <vrfname>] <ipaddr>SNMP Cable Modem Remote Query
This feature provides a new MIB, CISCO-DOCS-REMOTE-QUERY-MIB, which, when implemented on a CMTS, facilitates SNMP polling of remote CMs. This MIB includes the configuration of the CMTS CM Poller, as well as status objects of remote CMs that are polled by the CMTS CM Poller.
A new CLI command has been implemented for turning on the trap:
snmp-server enable cable cm-remote-quer
SNMP Objects for Clear Host, Clear Cable Modem, and Show Current CPEs
Host or cable modems can be cleared via the "cdxCmCpeResetNow" MIB object. The number of current CPEs can be displayed using the "cdxCmtsCmCurrCpeNumber" MIB object.
SNMP-Specific Trap CLI Enhancements
The old CLI for SNMP-specific traps was the following command:
[no] snmp-server enable traps snmp [authentication]Even though authentication was provided as an option, it did not behave as expected because entering the snmp-server enable traps snmp authentication command enabled not only the authentication traps, but also all other SNMP traps—viz, linkUp, linkDown and coldStart.
The CLI has been modified to allows all SNMP traps to be enabled or disabled separately. The modified CLI is the following command:
[no] snmp-server enable traps snmp [authentication | linkup | linkdown | coldstart]To allow all SNMP traps to be enabled or disabled simultaneously, issue the following command:
[no] snmp-server enable traps snmpSNMP Warm Start Trap
When two Cisco uBR7100 series routers are configured for failover and the active unit fails, the standby unit takes over and becomes the active unit. Whenever this occurs, a Failover Switchover SNMP trap is generated and will appear to the SNMP server as a "Warm Start" trap. This functionality is supported in Cisco IOS Release 12.1(5)EC1 and later releases.
Note
When a Cisco uBR7100 series router is powered up, an SNMP trap is generated and will appear to the SNMP server as a "Cold Start" trap. This functionality is also supported in Cisco IOS Release 12.1(5)EC1 and later releases.
Important Notes
The following sections contain important notes about Cisco IOS Release 12.1 EC that apply to the Cisco uBR7100 series universal broadband routers.
Using cable helper-address and ip helper-address Commands
On the Cisco CMTS, the Cisco IOS software provides two commands to forward User Datagram Protocol (UDP) broadcasts, such as DHCP/BOOTP packets, that are received on an interface—the ip helper-address and cable helper-address commands.
Use the ip helper-address command on all non-cable interfaces, and use the cable helper-address command for cable interfaces.
The cable helper-address command is optimized for cable interfaces and DOCSIS networks and should be used on cable interfaces instead of the ip helper-address command.
For more information on the ip helper-address command, refer to the Cisco IOS Command Reference, Release 12.2 T index page at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122tcr/crftindx.htm
For more information on the cable helper-address command, refer to the "Cable Modem Termination System Commands" chapter of the Cisco Broadband Cable Command Reference Guide at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/cable/bbccmref/bbcmts.htm
Limitation on CPE IP Addressing in Bridging Mode
When using the Cisco uBR7100 series router in bridging mode, be aware that bridging mode considers all CPE IP addresses to be static, even if they were acquired from a DHCP server. Because of this, it is possible that two or more PCs or CPE devices could be associated with the same IP address. However, only one CPE MAC address will be shown for that IP address in the show cable host command and when querying the cdxCmCpeEntry SNMP attribute. This limitation was tracked as caveat CSCdx37287.
SNR Algorithm Updated
In Cisco IOS Release 12.1(10)EC, the algorithm for calculating the SNR estimate in the show controllers cable upstream command was refined for a more accurate value. The new SNR estimate uses the algorithm as recommended by the chip manufacturer, and depending on plant characteristics, the new SNR value could be up to 6 dB lower than the values shown in earlier software releases.
Note
This value is only an estimate—for the most accurate value, use specialized test equipment such as a spectrum analyzer.
Limitation on Vendor-Specific Information in the DOCSIS Configuration File
DOCSIS requires that when the cable modem sends its Registration Request (REG-REQ) message to the CMTS, it must include the configuration information found in the DOCSIS configuration file. This configuration information must include all vendor-specific information fields (VSIF). Because MAC-layer management messages, such as REG-REQ, have a maximum data size of 1522 bytes, this limits the amount of VSIF information that can be included in the DOCSIS configuration file.
In particular, the maximum packet size imposes a limit on the number of Cisco IOS CLI commands you can include as VSIF fields in the DOCSIS configuration file. The exact number of commands that will fit depends on the other information included in the file, as well as the length of each command.
If the REG-REQ message is larger than 1522 bytes, the cable modem will likely report errors similar to the following errors that appears on Cisco uBR900 series cable access routers:
%LINK-4-TOOBIG: Interface cable-modem0, Output packet size of 1545 bytes too big%LINEPROTO-5-UPDOWN: Line protocol on Interface cable-modem0, changed state to downIn addition, the CMTS will also report that the cable modem timed out during the registration process. If this occurs, you can try the following steps:
•
Reduce the length of the commands by using the abbreviated form of the command. For example, you can specify the int c0 instead of the full command interface cable-modem0.
•
SNMP MIB objects are not included in the Registration Request message, so wherever possible, replace the CLI commands with the corresponding SNMP MIB object statements in the DOCSIS configuration file.
•
If a large number of CLI commands must be given, use VSIF option 128 to download a Cisco IOS configuration file to the cable modem.
For complete details on what is included in the REG-REQ message, see Chapter 6 of the current DOCSIS 1.1 specification (SP-RFIv1.1-I07-010829 or later).
Note
This limitation is being tracked by caveat CSCdv83892 but is not expected to be resolved unless the DOCSIS specification is changed to remove the maximum size limit for MAC-layer management messages.
NBAR Performance Impact
The Cisco IOS NBAR feature requires CPU resources to inspect, recognize, and process the packets coming through the router. In laboratory conditions, the use of NBAR can impact CPU performance by approximately 30 percent—the actual performance impact depends on the current CPU load, the number of packets processed, and the type of traffic being inspected. To limit the performance impact when using NBAR, activate the Turbo ACL feature to increase the performance of access list handling.
Hot-Standby 1+1 Redundancy Not Supported
The hot-standby 1+1 redundancy feature is not supported on any model of the Cisco uBR7100 series universal broadband router. The HCCP protocol therefore should not be configured on the cable interface using the hccp interface configuration commands.
EIGRP, IS-IS, and OSPF Not Supported on Cable Interfaces
The Cisco uBR7100 series router supports advanced routing protocols such as Enhanced Interior Gateway Routing Protocol (EIGRP), Intermediate System-to-Intermediate System (IS-IS), and Open Shortest Path First (OSPF) only on the WAN interfaces, not on the cable interfaces. On cable interfaces, use a routing protocol that is supported by the cable modems, such as RIPv2.
Configuring the Routing Protocol Causes a Reset of the Cable Modems
Be aware that when configuring a routing protocol on a Cisco uBR7100 series router, the Cisco IOS software must reset the interfaces to enable the change. This normally does not significantly affect operations on the interface, except that when this is done on a cable interface, it causes all cable modems on that particular downstream to reinitialize, potentially interfering with data transmission on that downstream. Therefore, you should use the routing protocol global configuration commands, such as router rip, only when a minimum of subscribers would be affected.
Cable Source-Verify and Routing Configurations
In current Cisco IOS Release 12.1 EC software images, the Cisco CMTS can crash with a "bus error exception" when the cable source-verify command is configured on a cable interface, and the routing configuration of that interface is being changed while traffic is passing through the interface.
To avoid this problem, temporarily disable this feature (using no cable source-verify) on the interface before you configure the routing parameters. Then after you have finished the routing configuration, reenable the feature using the cable source-verify command. Alternatively, you can also change the routing parameters when the interface is not passing traffic (such as when the interface is shut down).
PA-MC-2T1 Port Adapter Not Supported in Release 12.1(7)EC
The Cisco uBR7100 Series Universal Broadband Router Hardware Installation Guide incorrectly identifies the PA-MC-2T1 port adapter as being supported for the Cisco uBR7100 series routers in Cisco IOS Release 12.1(7)EC. The PA-MC-2T1 port adapter is not supported in Cisco IOS Release 12.1(7)EC for the Cisco uBR7100 series routers, but requires Cisco IOS Release 12.1(8)EC for support.
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 web site on Cisco.com at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
Supported MIBs
The Cisco uBR7100 series universal broadband routers support the following categories of MIBs:
•
SNMP standard MIBs—These MIBs are required by any agent supporting SNMPv1 or SNMPv2 network management.
•
Cisco's platform and network-layer enterprise MIBs—Common across most of Cisco's router platforms. If your network management applications are already configured to support other Cisco routers, such as the Cisco 2600 series or Cisco 7200 series, no further configuration is needed unless the version of Cisco IOS software being used has updated these MIBs.
•
Cable-specific MIBs—Provide information about the cable interfaces and related information on the Cisco uBR7100 series routers. They include both DOCSIS-specific MIBs and Cisco-specific enterprise MIBs. If your network management applications have not already been configured for the Cisco uBR7100 series routers, these MIBs must be loaded.
•
Deprecated MIBs—Supported in earlier releases of Cisco IOS software but have been replaced by more standardized, scalable MIBs. Network Management applications and scripts should convert to the replacement MIBs as soon as possible.
The cable-specific MIBs are described in the following section. For information on the SNMP standard MIBs and Cisco's platform and network-layer enterprise MIBs, see Cisco's MIB web site at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
Cable-Specific MIBs
Table 6 shows the cable-specific MIBs that are supported on the Cisco uBR7100 series universal broadband routers. The table also provides a brief description of each MIB's contents and the Cisco IOS software release in which the MIB was initially functional—earlier releases might have had unsupported prototype versions of the MIB; later releases might have added new attributes and functionality. Because of interdependencies, the MIBs must be loaded in the order given in the table.
Note
The 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.
Deprecated MIBs
Old Cisco MIBs will be replaced in a future release. Currently, OLD-CISCO-* MIBs are being converted into more scalable MIBs without affecting existing Cisco IOS products or network management system (NMS) applications. You can update from deprecated MIBs to the replacement MIBs as shown in Table 7.
Note
Some of the MIBs listed in Table 7 represent feature sets that are not supported on Cisco uBR7100 series universal broadband routers.
Note
Cisco Management Information Base (MIB) User Quick Reference is no longer published. If you have an account with Cisco.com, you can find the current list of MIBs supported by Cisco. To reach the Cisco Network Management Toolkit, go to Cisco.com, press Login, and then go to Software Center: Network Mgmt Products: Cisco Network Management Toolkit: Cisco MIB.
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.
This section only contains open and resolved caveats for the current Cisco IOS maintenance release.
All caveats in Cisco IOS Release 12.1 EC and Cisco IOS Release 12.1 are also in Cisco IOS Release 12.1(22)EC1.
For information on caveats in Cisco IOS Release 12.1, see Caveats for Cisco IOS Release12.1, which lists severity 1 and 2 caveats and select severity 3 caveats for Cisco IOS Release 12.1 and is located on Cisco.com and the Documentation CD-ROM.
Note
If you have an account on Cisco.com, you can use the Bug Toolkit to find select caveats of any severity. To reach the Bug Toolkit, log in to Cisco.com and click Technical Support: Tools & Utilities: Software BUG TOOLKIT (under Configuration Tools). Another option is to enter the following URL in your web browser or go to
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl
Open Caveats for Release 12.1(22)EC1
This section documents possible unexpected behavior by Cisco IOS Release 12.1(22)EC1 and describes only severity 1 and 2 caveats and select severity 3 caveats.
There are no known open caveats for Cisco IOS Release 12.1(22)EC1.
Closed and Resolved Caveats for Release 12.1(22)EC1
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(22)EC1. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Open Caveats for Release 12.1(22)EC
This section documents possible unexpected behavior by Cisco IOS Release 12.1(22)EC and describes only severity 1 and 2 caveats and select severity 3 caveats.
There are no known open caveats for Cisco IOS Release 12.1(22)EC.
Closed and Resolved Caveats for Release 12.1(22)EC
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(22)EC. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Table 9 Closed and Resolved Caveats for Release 12.1(22)EC
Caveat ID Number DescriptionCSCdy66891
When a cable modem receives a docsis binary file with network access disabled and bpi enabled, the CMTS will show it in the "online(pt)" state instead of "online(d)".
Workaround: Remove BPI from the docsis binary file.
CSCea00322
Under rare circumstances, namely when the service provider tftp server is down of unreachable, a cable modem may still be able to come online against a CMTS if it obtains an illicit DOCSIS configuration file from a local tftp server.
There are no known workarounds.
CSCec26369
Some Cable Modems goes offline every 3 weeks 3 days 20 hours 30 minutes after reloaded the CMTS.
There are no known workarounds.
CSCec85359
snmpwalk failed OID.1.3.6.1.2.1.10.127.1.3.7
This issue is observed on 7206VXR running IOS 12.1(13)EC3 and having PA-A3-8E1IMA interfaces.
Workaround: OIR the linecard.
CSCec86611
The CMTS logs the MAX-cpe errors when seeing the US traffic (as the CMTS still has the old PC in its database). However, the arp table and bridge table are still polled !, so the CMTS is bridging the traffic for this new PC to cable interface, even if it is not associated to any SID's.
Workaround: Perform the following:
•
CMTS: clear cable host <old_host> ---> so now the new PC is associated to the sid of the CM.
•
CMTS: increase the MAX-CPE to allow the new PC to be associated to the CM and let the old one get removed by timeout.
•
CMTS: use BPI to encrypted dedicated traffic to that CM.
•
CMTS: remove bridging setup.
CSCed12672
Mac clients behind cable modem sometimes are randomly unable to get IP address via dhcp. Debugs on CMTS shows an encapsulation failure for packets that are destined for that mac client
Workaround: Configure the static ip address on the mac client.
CSCed50533
Spurious interrupts are incrementing on ubr7246vxr/NPE-300 while running 12.1.13.EC1 code. They increment anywhere from 10-30 per minute.
There are no known workarounds.
CSCed65778
Certain release trains of Cisco Internetwork Operating System (IOS), when configured to use the Cisco IOS Secure Shell (SSH) server in combination with Terminal Access Controller Access Control System Plus (TACACS+) as a means to perform remote management tasks on Cisco IOS devices, may contain two vulnerabilities that can potentially cause Cisco IOS devices to exhaust resources and reload. Repeated exploitation of these vulnerabilities can result in a Denial of Service (DoS) condition. Use of SSH with Remote Authentication Dial In UserService (RADIUS) is not affected by these vulnerabilities.
Cisco has made free software available to address these vulnerabilities for all affected customers. There are workarounds available to mitigate the effects of the vulnerability (see the "Workarounds" section of the full advisory for details.)
This advisory will be posted at http://www.cisco.com/warp/public/707/cisco-sa-20050406-ssh.shtml
CSCed68829
Some modems might not be queried from SNMP cdxCmCpeTable and linecard CLI "show cable device access-group".
Workaround: shut/no shut cable interface.
CSCed76837
If there are lots of CM/CPE in the linecard, the SNMP query MIB tables related the CM/CPE info will possibly have SNMP-3-CPUHOG message and trackback. Also the CM/CPE may have connection problem (drop offline or lose VPN).
The MIB tables are listed below. They are all invoke the same API to get the sorted table which the entry is searched.
CISCO-DOCS-EXT-MIB:cdxCmCpeTable,DOCS-IF-MIB:docsIfCmtsMacToCmTableDOCS-QOS-MIB:docsQosCmtsMacToSrvFlowTableCISCO-DOCS-REMOTE-QUERY-MIB:cdrqCmtsCmStatusTableAfter the fix:
1. All the SNMP query for above tables will get info from RP/NPE only. So LC will not be affected.
2. The SNMP query Get EXACT will have real time response.
3. SNMP Get NEXT for above MIB tables is too expensive in a big system since it needs to go through whole CM/CPE in order to know which CM/CPE is the next entry of the query. Users are recommended to use SNMP GET EXACT to retrieve the info for a specific device.
In order to prevent CPU spiking for GET NEXT for above MIB tables, in the CMTS which number of devices (CM/CPE) is greater than 1000, the SNMP query GET NEXT will not get any entries returned. GetBulk has also the same problem as GetNext since internally, it searches for the next entry.
GET NEXT/GET BULK support is back via CSCed90740.
CSCed77196
The ubr7100 does not enforce MAX-CPE on a CMTS interface when it is configured as a member of a bridge group. This is because the method used to glean host information relies on ARP and DHCP packets, which may not be available to the CMTS code. As a result, if the CMTS bridging code can not find a CPE's SID in the host table, it will apply a default QoS setting, which may provide a greater than expected downstream bitrate.
This change does the following:
•
It stores the primary upstream SID for each CPE on the CMTS interface in the bridging table and passes the SID value to the CMTS bridging code when packets are bridged in a downstream direction.
•
It gleans information from upstream packets and adds the MAC address and SID information to the CMTS host tables.
Note
It will not glean IP addresses.
•
It Enforces the MAX-CPE setting on downstream packets.
The problem is as follows:
The CMTS logs the MAX-cpe errors when seeing the US traffic (as the CMTS still has the old PC in its database). However, the arp table and bridge table are still polled !, so the CMTS is bridging the traffic for this new PC to cable interface, even if it is not associated to any SID's.
Workaround: Perform the following:
•
CMTS: clear cable host <old_host> ---> so now the new PC is associated to the sid of the CM.
•
CMTS: increase the MAX-CPE to allow the new PC to be associated to the CM and let the old one get removed by timeout.
•
CMTS: use BPI to encrypted dedicated traffic to that CM.
•
CMTS: remove bridging setup.
CSCee26361
A DHCPACK or DHCPNACK with a chaddr == 0 is not forwarded by the Cisco DHCP stack to the cable CMTS code when the CMTS is a relay agent.
The DHCP stack must forward such a reply to the CMTS code so that the CMTS can make a decision on an active or inactive lease on the DHCP server.
There are no known workarounds.
CSCee27549
SNMP query does not detect specific modems via cdxCmCpeCmStatusIndex in new IOS code 12.2(15)BC1c code. The issue exhibit only for few cable modems on ubr10k chassis.
It is noticed that same cable modem, for which snmp poll is failing, appeared under multiple cable interfaces
There are no known workarounds.
CSCee46169
The old host is getting aged out of the arp table. The same host is not getting aged out of the SID table as evident in a "show interface cable 1/0 modem" <z>. Since the modem never gets aged out of the SID table max, CPE is eventually reached. The next CPE attempting to register behind that modem will not be permitted. A duplicate IP error message is inserted into the log.
This condition exist only in ridge mode. To allow subsequent cable modem onto that cmts, the bad host must be removed from the SID table with a "clear cable host" or the cable modem must be power cycled.
There are no known workarounds.
CSCin40371
Traffic loss may occur when you configure the no ip cef global configuration command.
This issue is observed on a Cisco router that has Cisco Express Forwarding (CEF) enabled by default, but that does not have the no ip cef global configuration command configured in the startup configuration.
Workaround: After CEF has been enabled by default, disable CEF.
CSCin50894
Active modems field under <show int cable down> and shows the wrong values
There are no known workarounds.
Open Caveats for Release 12.1(20)EC3
There are no open caveats specific to Cisco IOS Release 12.1(19)EC3 that require documentation in the release notes.
Closed or Resolved Caveats—Release 12.2(20)EC3
Table 10 lists the significant closed or resolved caveats that exist in Cisco IOS Release 12.2(20)EC3.
Open Caveats for Release 12.1(20)EC2
This section documents possible unexpected behavior by Cisco IOS Release 12.1(20)EC2 and describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Closed and Resolved Caveats for Release 12.1(20)EC2
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(20)EC2. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Table 12 Closed and Resolved Caveats for Release 12.1(20)EC2
Caveat ID Number DescriptionCSCed68575
Cisco Internetwork Operating System (IOS) Software releases trains 12.0S, 12.1E, 12.2, 12.2S, 12.3, 12.3B and 12.3T may contain a vulnerability in processing SNMP requests which, if exploited, could cause the device to reload.
The vulnerability is only present in certain IOS releases on Cisco routers and switches. This behavior was introduced via a code change and is resolved with CSCed68575.
This vulnerability can be remotely triggered. A successful exploitation of this vulnerability may cause a reload of the device and could be exploited repeatedly to produce a Denial of Service (DoS).
This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040420-snmp.shtml
Open Caveats for Release 12.1(20)EC1
This section documents possible unexpected behavior by Cisco IOS Release 12.1(20)EC1 and describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Closed and Resolved Caveats for Release 12.1(20)EC1
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(20)EC1. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Open Caveats for Release 12.1(20)EC
This section documents possible unexpected behavior by Cisco IOS Release 12.1(20)EC and describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Closed and Resolved Caveats for Release 12.1(20)EC
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(20)EC. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Open Caveats for Release 12.1(19)EC1
There are no open caveats specific to Cisco IOS Release 12.1(19)EC1 that require documentation in the release notes.
Closed and Resolved Caveats for Release 12.1(19)EC1
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(19)EC1. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Open Caveats for Release 12.1(19)EC
This section documents possible unexpected behavior by Cisco IOS Release 12.1(19)EC and describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Closed and Resolved Caveats for Release 12.1(19)EC
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(19)EC. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Table 19 Closed and Resolved Caveats for Release 12.1(19)EC
Caveat ID Number DescriptionCSCdu13269
Attempt to free Unassigned memory, System reloads
CSCdu53656
A Cisco device running IOS and enabled for the Border Gateway Protocol (BGP) is vulnerable to a Denial of Service (DOS) attack from a malformed BGP packet. The BGP protocol is not enabled by default, and must be configured in order to accept traffic from an explicitly defined peer. Unless the malicious traffic appears to be sourced from a configured, trusted peer, it would be difficult to inject a malformed packet. BGP MD5 is a valid workaround for this problem.
Cisco has made free software available to address this problem. For more details, please refer to this advisory, available at http://www.cisco.com/warp/public/707/cisco-sa-20040616-bgp.shtml.
CSCdx00274
PA-FE input stuck with burst traffic
CSCdx35070
Change the default unique word (uw) to 16 for 16qam short/long burst
CSCdx37957
SNMP:Unerrored MIB decrementing (transmission.127.1.1.4.1.2)
CSCdx63927
7200:reload due to memory corruption in PA-1FE
CSCdy17114
Memory allocation failure in public buffer pools
CSCdy46139
ALL FF mac entry shown in cable bundle forwarding table
CSCdy52079
ubr7200:modem lookup at CMTS fails, so DHCP for CPE fails
CSCdy61007
CEF causing 50% packet drops for VPN 3002 client
CSCdy70193
Crash in timer_start64, cmts_update_lease_time, cmts_dhcp_glean
CSCdy73203
Through SSH Session Successful DOCSIS Pings Will Return FFFF Values
CSCdy76674
source-verify leasetimer config shows up on sub-interface
CSCdy76724
PRE Crash at sch_handle_headsail_pak,ip_fastswitch_wrapper
CSCdz01140
Overlapping IP address assignment can cause denial of service
CSCdz03584
crash when configuring more than 6 OUIs with int config file editor
CSCdz06164
CMTS:IP connectivity failure to Cable Modem and CPE
CSCdz28856
DHCP fails if Virtual template uses ip unnumbered
CSCdz42924
unable to enable wccp on cef switching path
CSCdz55120
cdxIfUpChannelCmRegistered doesn't include OnlineNetAccessDisabled
CSCdz55178
QoS profile name of more then 32 chars will crash the router
CSCdz65143
Spurious memory access at cmts_mac_timer_proc
CSCdz82859
%SYS-3-NOELEMENT displayed.
CSCdz88353
Traffic forwarded to CM/CPE when in Reject(m) state
CSCea08892
change buffer allocations in VXR
CSCea14372
CMTS should calculate the dynamic map advance based on max delay
CSCea23522
CMTS crashes on OIR
CSCea28131
A Cisco device running IOS and enabled for the Border Gateway Protocol (BGP) is vulnerable to a Denial of Service (DOS) attack from a malformed BGP packet. The BGP protocol is not enabled by default, and must be configured in order to accept traffic from an explicitly defined peer. Unless the malicious traffic appears to be sourced from a configured, trusted peer, it would be difficult to inject a malformed packet. BGP MD5 is a valid workaround for this problem.
Cisco has made free software available to address this problem. For more details, please refer to this advisory, available at http://www.cisco.com/warp/public/707/cisco-sa-20040616-bgp.shtml.
CSCea42973
Changing QoS profile for modems does not work in 12.1(13)EC2
CSCea67337
CM fails to come online when spectrum-group is configured at CMTS
CSCea68444
NPE-G1 turn off prefetching
CSCea82308
hide atp command due to being obsolete and causing traceback
CSCea88356
ubr7200/MC16B:Calibration bad for 3.2MHz channel width
CSCeb38067
all cms offline on MC16C/MC28C in 12.1EC and 12.2BC
CSCeb39565
bus error in the address of 0xDEADBEEF at arp_ager.
CSCeb40414
CLI for modulation profile does not check validity if first digit 0
CSCeb42675
Remove wedged queue workaround
CSCec01689
Add CERF Support on uBR7200 NPE-400
CSCec04003
High CPU on process CMTS Mac protocol
CSCin13783
Bundling crash on bootup and after LC switch-over
CSCin19062
After OIR, some of the cable features are removed from the running-c
CSCin19989
SM Aborted time field does not reflect correct values
CSCin20036
interface resets counters under show interface cable ? too high
CSCin20365
Tracebacks seen while configuring badipsource buffer to high value
CSCin20444
CMTS got hanged while doing clear cable host ? after done with sour
CSCin24305
CMTS shows incorrect/invalid value with cable max-host ? CLI
CSCin29826
uBR7200:crashes at %SYS-2-CHUNKFREE:Attempted to free nonchunk memo
CSCin29873
Inconsistent ouput shown by show env last
CSCin29936
ciscoEnvMonSupplySource returns incorrect values
CSCin30375
ciscoEnvMonEnableVoltageNotification does not return any value
CSCin36943
Show Version displays erratic number of interfaces after OIR of FE
CSCin38107
CPE count under show cable modem set to 0 when CM goes offline
Open Caveats for Release 12.1(13)EC4
There are no open caveats specific to Cisco IOS Release 12.1(13)EC4 that require documentation in the release notes.
Closed and Resolved Caveats for Release 12.1(13)EC4
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(13)EC4. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Table 20 Closed and Resolved Caveats for Release 12.1(13)EC4
Caveat ID Number DescriptionCSCdz71127
corrupted packet can cause input queue wedge - reg to CSCdx02283
Cisco routers and switches running Cisco IOS software and configured to process Internet Protocol version 4 (IPv4) packets are vulnerable to a Denial of Service (DoS) attack. A rare sequence of crafted IPv4 packets sent directly to the device may cause the input interface to stop processing traffic once the input queue is full. No authentication is required to process the inbound packet. Processing of IPv4 packets is enabled by default. Devices running only IP version 6 (IPv6) are not affected. A workaround is available.
Cisco has made software available, free of charge, to correct the problem.
This advisory is available at:
http://www.cisco.com/warp/public/707/cisco-sa-20030717-blocked.shtml
CSCdz82859
%SYS-3-NOELEMENT displayed.
CSCea02355
rare ip packets may cause input queue wedge
Cisco routers and switches running Cisco IOS software and configured to process Internet Protocol version 4 (IPv4) packets are vulnerable to a Denial of Service (DoS) attack. A rare sequence of crafted IPv4 packets sent directly to the device may cause the input interface to stop processing traffic once the input queue is full. No authentication is required to process the inbound packet. Processing of IPv4 packets is enabled by default. Devices running only IP version 6 (IPv6) are not affected. A workaround is available.
Cisco has made software available, free of charge, to correct the problem.
This advisory is available at:
http://www.cisco.com/warp/public/707/cisco-sa-20030717-blocked.shtml
CSCeb42675
Remove wedged queue workaround.
Open Caveats for Release 12.1(13)EC3
There are no open caveats specific to Cisco IOS Release 12.1(13)EC3 that require documentation in the release notes.
Closed and Resolved Caveats for Release 12.1(13)EC3
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(13)EC3. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Open Caveats for Release 12.1(13)EC2
There are no open caveats specific to Cisco IOS Release 12.1(13)EC2 that require documentation in the release notes.
Closed and Resolved Caveats for Release 12.1(13)EC2
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(13)EC2. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Open Caveats for Release 12.1(13)EC1
There are no open caveats specific to Cisco IOS Release 12.1(13)EC1 that require documentation in the release notes.
Closed and Resolved Caveats for Release 12.1(13)EC1
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(13)EC1. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Table 23 Closed and Resolved Caveats for Release 12.1(13)EC1
Caveat ID Number DescriptionCSCdz06164
CMTS: IP connectivity failure to Cable Modem and CPE
Open Caveats for Release 12.1(13)EC
This section documents possible unexpected behavior by Cisco IOS Release 12.1(13)EC and describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Closed and Resolved Caveats for Release 12.1(13)EC
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(13)EC. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Open Caveats for Release 12.1(12c)EC1
There are no open caveats that require documentation in the release notes for Cisco IOS Release 12.1(12c)EC1.
Closed and Resolved Caveats for Release 12.1(12c)EC1
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(12c)EC1. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Table 26 Closed and Resolved Caveats for Release 12.1(12c)EC1
Caveat ID Number DescriptionCSCdy04242
ubr7100 failed netbooting after formatting flash
Open Caveats for Release 12.1(12c)EC
This section documents possible unexpected behavior by Cisco IOS Release 12.1(12c)EC and describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Closed and Resolved Caveats for Release 12.1(12c)EC
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(12c)EC. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Open Caveats for Release 12.1(11b)EC1
This section documents possible unexpected behavior by Cisco IOS Release 12.1(11b)EC and describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Closed and Resolved Caveats for Release 12.1(11b)EC1
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(11b)EC1. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Open Caveats for Release 12.1(11b)EC
This section documents possible unexpected behavior by Cisco IOS Release 12.1(11b)EC and describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Closed and Resolved Caveats for Release 12.1(11b)EC
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(11b)EC. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Open Caveats for Release 12.1(10)EC1
This section documents possible unexpected behavior by Cisco IOS Release 12.1(10)EC1 and describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Closed and Resolved Caveats for Release 12.1(10)EC1
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(10)EC1. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Open Caveats for Release 12.1(10)EC
This section documents possible unexpected behavior by Cisco IOS Release 12.1(10)EC and describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Closed and Resolved Caveats for Release 12.1(10)EC
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(10)EC. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Open Caveats for Release 12.1(9)EC
This section documents possible unexpected behavior by Cisco IOS Release 12.1(9)EC and describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Closed and Resolved Caveats for Release 12.1(9)EC
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(9)EC. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Open Caveats for Release 12.1(8)EC
This section documents possible unexpected behavior by Cisco IOS Release 12.1(8)EC and describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Closed and Resolved Caveats for Release 12.1(8)EC
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(8)EC. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Open Caveats for Release 12.1(7)EC
This section documents possible unexpected behavior by Cisco IOS Release 12.1(7)EC and describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Closed and Resolved Caveats for Release 12.1(7)EC
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(7)EC. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
Open Caveats for Release 12.1(6)EC
This section documents possible unexpected behavior by Cisco IOS Release 12.1(6)EC and describes only severity 1 and severity 2 caveats and select severity 3 caveats.
There are no open caveats that require documentation in the release notes for Cisco IOS Release 12.1(6)EC.
Closed and Resolved Caveats for Release 12.1(6)EC
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(6)EC. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
There are no closed and resolved caveats that require documentation in the release notes for Cisco IOS Release 12.1(6)EC.
Open Caveats for Release 12.1(5)EC1
This section documents possible unexpected behavior by Cisco IOS Release 12.1(5)EC1 and describes only severity 1 and severity 2 caveats and select severity 3 caveats.
•
CSCdt66295
This caveat is resolved in Cisco IOS Release 12.1(7)EC. See the "Closed and Resolved Caveats for Release 12.1(7)EC" section.
Closed and Resolved Caveats for Release 12.1(5)EC1
All the caveats listed in this section are closed or resolved in Cisco IOS Release 12.1(5)EC1. This section describes only severity 1 and severity 2 caveats and select severity 3 caveats.
•
CSCds04747
Cisco IOS software contains a flaw that permits the successful prediction of TCP Initial Sequence Numbers.
This vulnerability is present in all released versions of Cisco IOS software running on Cisco routers and switches. It only affects the security of TCP connections that originate or terminate on the affected Cisco device itself; it does not apply to TCP traffic forwarded through the affected device in transit between two other hosts.
To remove the vulnerability, Cisco is offering free software upgrades for all affected platforms. The defect is described in DDTS record CSCds04747.
Workarounds are available that limit or deny successful exploitation of the vulnerability by filtering traffic containing forged IP source addresses at the perimeter of a network or directly on individual devices.
This notice will be posted at http://www.cisco.com/warp/public/707/ios-tcp-isn-random-pub.shtml.
This is resolved in Cisco IOS Release 12.1(5)EC1.
Open Caveats for (Deferred) Release 12.1(5)EC
This section documents possible unexpected behavior by Cisco IOS Release 12.1(5)EC and describes only severity 1 and severity 2 caveats and select severity 3 caveats.
There are no open caveats that require documentation in the release notes for Cisco IOS Release 12.1(5)EC.
Closed and Resolved Caveats for (Deferred) Release 12.1(5)EC
Because Cisco IOS Release 12.1(5)EC is the initial release for the Cisco uBR7100 series routers, there are no closed or resolved caveats that require documentation in the release notes.
Related Documentation
The following sections describe the documentation available for the Cisco uBR7100 series. These documents consist of hardware and software installation guides, Cisco IOS configuration guides and command references, system error messages, feature modules, and other documents.
Documentation is available as printed manuals or electronic documents, except for feature modules, which are available online on Cisco.com and the Documentation CD-ROM.
Use these release notes with these documents:
•
Cisco IOS Software Documentation Set
Release-Specific Documents
The following documents are specific to Release 12.1 and are located on Cisco.com and the Documentation CD-ROM:
•
Product bulletins, field notices, and other release-specific documents on Cisco.com, beginning under the Service & Support heading:
Technical Documents
•
Caveats for Cisco IOS Release 12.1
On Cisco.com, beginning under the Service & Support heading:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Release Notes: Caveats: Caveats for Release 12.1
On the Documentation CD-ROM:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Caveats
Note
If you have an account on Cisco.com, you can use the Bug Toolkit to find select caveats of any severity. To reach the Bug Toolkit, log in to Cisco.com and click Technical Support: Tools & Utilities: Software BUG TOOLKIT (under Configuration Tools). Another option is to enter the following URL in your web browser or go to
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl
Platform-Specific Documents
The following documents are available for the Cisco uBR7100 series universal broadband routers on Cisco.com and the Documentation CD-ROM:
•
Cisco uBR7100 Series Hardware Installation Guide
•
Cisco uBR7100 Series Software Configuration Guide
•
Cisco uBR7100 Series Power Supply Installation
•
Broadband Command Consolidation
On Cisco.com, beginning under the Service & Support heading:
Technical Documents: Documentation Home Page: Broadband Access: Cable: Cisco uBR7100 Series Universal Broadband Routers
Note
The Broadband Command Consolidation is available on Cisco.com through the following path:
Technical Documents: Documentation Home Page: Broadband/Cable SolutionsOn the Documentation CD-ROM:
Cisco Product Documentation: Broadband Access: Cable: Cisco uBR7100 Series Universal Broadband Routers
Note
The Broadband Command Consolidation is available on the Documentation CD-ROM through the following path:
Cisco Product Documentation: Broadband/Cable Solutions
Tips
Information about features of the Cisco uBR7100 series universal broadband router, as well as software release notes, are available on Cisco.com at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/cable/index.htm
Feature Modules
Feature modules describe new software enhancements, committed as features, supported by Cisco IOS Release 12.1(7)EC, and are updates to the Cisco IOS documentation set. A feature module consists of a brief overview of the feature, benefits, and 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 Cisco.com, beginning under the Service & Support heading:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: New Feature Documentation
On the Documentation CD-ROM:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: New Feature Documentation: New Features in Release 12.1
Cisco Feature Navigator
Cisco IOS software is packaged in feature sets that are supported on specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Cisco Feature Navigator is a web-based tool that enables you to quickly determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.
To access Cisco Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you.
Qualified users can establish an account on Cisco.com by following the directions found at this URL:
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
http://www.cisco.com/pcgi-bin/Support/FeatureNav/FN.pl
Cisco IOS Software Documentation Set
The Cisco IOS software documentation set consists of the Cisco IOS configuration guides, Cisco IOS command references, and several other supporting documents. The Cisco IOS software documentation set is shipped with your order in electronic form on the Documentation CD-ROM, unless you specifically ordered the printed versions.
Documentation Modules
Each module in the Cisco IOS documentation set consists of one or more configuration guides and one or more corresponding command references. 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 Cisco.com and the Documentation CD-ROM, two master hot-linked documents provide information for the Cisco IOS software documentation set.
On Cisco.com, beginning under the Service & Support heading:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
On the Documentation CD-ROM:
Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
Release 12.1 Documentation Set Contents
Table 43 lists the contents of the Cisco IOS Release 12.1 software documentation set, which is available in electronic form, and also in printed form upon request.
Note
You can find the most current Cisco IOS documentation on Cisco.com and the Documentation CD-ROM. These electronic documents may contain updates and modifications made after the paper documents were printed.
On Cisco.com, beginning under the Service & Support heading:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
On the Documentation CD-ROM:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
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 Cisco Network Management Toolkit on Cisco.com. From Cisco.com, click on the following path: Service & Support: Software Center: Network Mgmt Products: Cisco Network Management Toolkit: Cisco MIB.
Obtaining Documentation
The following sections provide sources for obtaining documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at this URL:
Translated documentation is available at this URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Ordering Documentation
You can order Cisco documentation in these ways:
•
Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:
http://www.cisco.com/public/ordsum.html
•
Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:
http://www.cisco.com/go/subscription
•
Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).
Documentation Feedback
You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.
You can email your comments to bug-doc@cisco.com.
You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you with these tasks:
•
Streamline business processes and improve productivity
•
Resolve technical issues with online support
•
Download and test software packages
•
Order Cisco learning materials and merchandise
•
Register for online skill assessment, training, and certification programs
If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:
Technical Assistance Center
The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Cisco TAC inquiries are categorized according to the urgency of the issue:
•
Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.
•
Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
•
Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.
•
Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.
The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:
http://www.cisco.com/register/
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
![]()


