Table Of Contents
Additional Notes for the Cisco Voice Gateway 200
Additional Notes for the Cisco 800 Series
Cisco uBR924 Cable Access Router
Additional Notes for the Cisco uBR924 Cable Access Router
Additional Notes for the Cisco 1400 Series Routers
Additional Notes for the Cisco 1700 Series Routers
Cisco MC3810 Multiservice Access Concentrator
Additional Notes for the Cisco MC3810 Multiservice Access Concentrator
Cisco Catalyst 4500 Access Gateway Module
Additional Notes for the Cisco Catalyst 4500 Access Gateway Module
Cisco AS5300 Universal Access Servers
Microcode and Modem Code Software
Additional Notes for the Cisco AS5300 Universal Access Server
Cisco AS5400 Universal Gateway
Cisco AS5800 Universal Access Servers
Additional Notes for the Cisco AS5800
Additional Notes for the Cisco 7000 Family Routers
Cisco uBR7200 Series Universal Broadband Routers
Cisco MGX 8850 Route Processor Module
Cisco 15104 Optical Networking System
Feature Support
Cisco IOS software is packaged in feature sets that consist of software images that support specific platforms. The feature sets available for a specific platform depend on which Cisco IOS software images are included in a release. Each feature set contains a specific set of Cisco IOS features.
CautionCisco IOS images with strong encryption (including, but not limited to 168-bit (3DES) data encryption feature sets) are subject to U.S. government export controls and have limited distribution. Strong encryption images to be installed outside the United States are likely to require an export license. Customer orders may be denied or subject to delay because of U.S. government regulations. When applicable, the purchaser/user must obtain local import and use authorizations for all encryption strengths. Please contact your sales representative or distributor for more information, or send an e-mail to export@cisco.com.
The feature set tables have been removed from the Cisco IOS Release 12.2 release notes to improve the usability of the release notes documentation. The feature-to-image mapping that was provided by the feature set tables is available through Cisco Feature Navigator.
Cisco Feature Navigator is a web-based tool that enables you to 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 by feature set (software image). Under the release section, you can compare Cisco IOS software releases side by side to display both the features unique to each software release and the features that the releases have in common.
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:
For frequently asked questions about Cisco Feature Navigator, see the FAQs at the following URL:
http://www.cisco.com/support/FeatureNav/FNFAQ.html
Determining Which Software Images (Feature Sets) Support a Specific Feature
To determine which software images (feature sets) in Cisco IOS Release 12.2 support a specific feature, go to the Cisco Feature Navigator home page, and perform the following steps.
Step 1
Step 2
Step 3
Note
Repeat this step to add additional features. A maximum of 20 features can be chosen for a single search.
Step 4
Step 5
Step 6
Step 7
Determining Which Features Are Supported in a Specific Software Image (Feature Set)
To determine which features are supported in a specific software image (feature set) in Cisco IOS Release 12.2, go to the Cisco Feature Navigator home page and perform the following steps.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Memory Recommendations
The memory recommendation tables have been removed from the Cisco IOS Release 12.2 release notes to improve the usability of the release notes documentation. The memory recommendations that were provided by these tables are available through Cisco Feature Navigator.
Cisco Feature Navigator is a web-based tool that enables you to 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 by feature set (software image). Under the release section, you can compare Cisco IOS software releases side by side to display both the features unique to each software release and the features that the releases have in common.
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:
For frequently asked questions about Cisco Feature Navigator, see the FAQs at the following URL:
http://tools.cisco.com/ITDIT/CFN/jsp/help.jsp
Determining Memory Recommendations for Software Images (Feature Sets)
To determine memory recommendations for software images (feature sets) in Cisco IOS Release 12.2, go to the Cisco Feature Navigator home page and perform the following steps.
Step 1
Step 2
a.
b.
The Search Results table will list all the software images (feature sets) that support the release that you chose, plus the DRAM and flash memory recommendations for each image.
Step 3
a.
b.
c.
d.
The Search Results table will list all the software images (feature sets) that support the release that you chose, plus the DRAM and flash memory recommendations for each image.
Platform-Specific Information
This section describes the platform-specific information for the Cisco platforms supported by Cisco IOS Release 12.2. Each section includes memory recommendations and supported features. Additional information is provided when applicable. This information is provided for the platforms described in the following sections:
•
•
•
•
•
•
•
•
•
•
Cisco Voice Gateway 200
This section contains the following sections with information that is specific to the Cisco Voice Gateway 200 (VG200):
•
Introduction
The Cisco VG200 is designed to provide easy integration between Voice over IP (VoIP) network resources, especially the Cisco IP Telephony solution and the public switched telephone system (PSTN). The current release of the Cisco VG200 gateways provides the following main features:
•
•
•
•
Memory Recommendations
For memory recommendations for the Cisco Voice Gateway 200 in Cisco IOS Release 12.2, refer to the "Memory Recommendations" section.
Hardware Supported
For detailed descriptions of the new hardware features, see the "New and Changed Information" section on page 93.
Table 1 summarizes the modules and interfaces supported on the Cisco Voice Gateway 200.
Feature Support
For feature support in Cisco IOS Release 12.2, refer to the "Feature Support" section.
Additional Notes for the Cisco Voice Gateway 200
This section describes additional notes for the Cisco Voice Gateway 200 for Cisco IOS Release 12.2.
Handling Incoming Caller ID Digits on an E&M Port
When using an H.323 T1-CAS E&M port on the Cisco VG200, incoming caller ID digits may not be processed correctly by Cisco IP Interactive Voice Response (IVR) applications, such as Cisco IP Auto-Attendant.
Depending on the T1-CAS line provisioning, incoming dialed number information service (DNIS) digits received by the Cisco VG200 after its first wink to the Central Office (CO) are treated as user-entered digits and are sent to the remote endpoint as out-of-band dual tone multifrequency (DTMF) digits. If the remote endpoint is a Cisco IP IVR application, the out-of-band digits will be interpreted as a user entry and will change the application response. There are two ways to handle this situation:
•
•
Managing Input Gain for Cisco IP Voice Applications
When using the FXO ports on a Cisco VG200, set the input gain greater than 10 to achieve adequate audio quality for use with Cisco IP voice applications or the Cisco IP Phone 7960. Enter the following series of commands from the Cisco IOS command line to set the correct value for input gain:
vg200# configure terminalvg200(config)# voice-port x/x/x input gain <value>Permitted entries for <value> are from -6 to 14. Gain values higher than 12 may cause DTMF recognition difficulties.
Enabling DTMF Relay with MGCP
Make sure that you use the MGCP configuration command for enabling DTMF relay. If this command is not configured, DTMF tones will be not be regenerated correctly on the remote endpoint. The required command is as follows:
router(config)# mgcp dtmf-relay codec all mode out-of-bandFor further information about configuring MGCP, refer to the Software Configuration Guide for the Cisco VG200.
Cisco 800 Series Routers
This section contains the following sections with information that is specific to the Cisco 800 series:
•
Memory Recommendations
For memory recommendations for the Cisco 800 series routers in Cisco IOS Release 12.2, refer to the "Memory Recommendations" section.
Hardware Supported
Cisco IOS Release 12.2 supports the Cisco 800 series routers:
•
•
•
•
•
For detailed descriptions of the new hardware features, see the "New and Changed Information" section on page 93.
Table 2 lists the supported interfaces for the Cisco 800 series routers for Cisco IOS Release 12.2.
Cisco 801-804 Routers
The Cisco 801-804 routers provide the following key hardware features:
•
•
•
Note
•
•
•
•
Cisco 805 Router
The Cisco 805 router connects small professional offices over serial lines to corporate networks and to the Internet, and provides the following key features:
•
•
•
•
•
•
Feature Support
For feature support in Cisco IOS Release 12.2, refer to the "Feature Support" section.
Additional Notes for the Cisco 800 Series
caller-id Command
When using the caller-id command, which appears under "dial-peer" in the configuration commands, the default setting is "off" for Japan and "on" for the U.S. This command was introduced in Cisco IOS Release 12.1(2)XF.
DHCP Client Support
To configure the router for Dynamic Host Configuration Protocol (DHCP) client support, perform the following steps:
Step 1
Specifying the value client-id ethernet0 causes the MAC address of the Ethernet interface to be used as the client ID when the DHCP request is sent. Otherwise, the MAC address of the BVI interface is used as the client ID.
Step 2
a.
b.
c.
d.
The following is a sample configuration:
Current configuration:!version 12.0no service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname c827!!ip subnet-zeroip dhcp excluded-address 10.10.10.1!ip dhcp pool SERVERnetwork 10.10.10.0 255.255.255.0default-router 10.10.10.1import all!!!bridge irb!!!!interface Ethernet0ip address 10.10.10.1 255.255.255.0no ip directed-broadcastip nat inside!interface ATM0no ip addressno ip directed-broadcastno atm ilmi-keepalivebundle-enablehold-queue 208 in!interface ATM0.1 point-to-pointno ip directed-broadcastpvc 1/100encapsulation aal5snap!bridge-group 1!interface ATM0.2 point-to-pointip address 5.0.0.2 255.0.0.0no ip directed-broadcastpvc 1/101protocol ip 5.0.0.1 broadcastprotocol ip 5.0.0.5 broadcastencapsulation aal5snap!!interface BVI1ip address dhcp client-id Ethernet0no ip directed-broadcastip nat outside!ip nat inside source list 1 interface BVI1 overloadip classlessip route 0.0.0.0 0.0.0.0 BVI1no ip http server!access-list 1 permit 10.10.10.0 0.0.0.255bridge 1 protocol ieeebridge 1 route ip!voice-port 1timing hookflash-in 0!voice-port 2timing hookflash-in 0!voice-port 3timing hookflash-in 0!voice-port 4timing hookflash-in 0!!line con 0exec-timeout 0 0transport input nonestopbits 1line vty 0 4password lablogin!scheduler max-task-time 5000endDownloading Images
Delete files in the router Flash memory before attempting to download new images.
Caution
Flash Memory
Cisco 800 series routers use 4 MB of Flash memory for storing internal information such as the ROM monitor. Only the remainder of the Flash memory is available for storing Cisco IOS images and is displayed by using the show flash command. For example, if the router reports 8 MB of Flash, the actual amount of onboard Flash memory is 12 MB, even though only 8 MB are displayed and available for Cisco IOS image storage.
Multilink PPP and Interleaving
Multilink PPP fragments large data packets to allow small voice packets to be interleaved between them. However, apart from FIFO queuing, no other kind of output queuing mechanisms are currently supported with PPP over ATM. Consequently, when multilink PPP is configured on the Cisco 800 series routers, large packets are fragmented, but small voice packets are not interleaved between them.
NAT Support for H.323 Signaling
NAT does not support alerting H.225 messages; therefore, NAT communication cannot be established between router end points. NAT support for H.323 signaling is limited to the application NetMeeting.
PPP over AAL5SNAP Encapsulation Support
PPP over AAL5SNAP encapsulation is currently not supported, although the context sensitive help mentions that it can be configured.
Cisco 800 Series Router Clock—CSCdp09409
To run IP Security (IPSec) successfully, the Cisco 800 series router clock needs to be set accurately. Cisco 800 series router clocks are set and maintained using Simple Network Time Protocol (SNTP). For best results, set up a Network Time Protocol (NTP) server to periodically send time information messages to Cisco 800 series routers. See the SNTP configuration and command reference documentation for configuration instructions. If you do not have an NTP server, you must reset the Cisco 800 series router clock using the clock set command each time you restart the router.
Dial Peer Limitation
The isdn answer1 and isdn answer2 commands determine which called telephone numbers, for example, 555-1111 and 555-2222, a Cisco 800 series router can answer. Using these commands limits a router to using the two dial peers that contain the telephone numbers 555-1111 and 555-2222. (When not using these commands, a router can use up to six dial peers.)
A sample scenario in which the isdn answer1 and isdn answer2 commands are used is when a Cisco 801 or Cisco 803 router is connected with other ISDN devices to an ISDN S-bus.
Excessive ISDN Line Activation
The following protocols send updates that can cause an ISDN line to be activated excessively, thereby increasing your monthly ISDN line cost:
•
•
•
•
•
For information on preventing this situation, refer to the Cisco 800 Series Routers Software Configuration Guide. This guide contains information on setting up extended access lists to prevent IP, UDP, IPX, and SNTP updates from activating the ISDN line. For CDP, make certain that you enter the no cdp enable command to disable CDP.
Hanging During Boot
If an illegal console configuration is issued to the router, the console will fail the POST test during boot and cause the router to hang. There is no way to recover a unit in this state except by pulling the soldered boot Flash and reburning the boot ROM.
This problem has been resolved in TinyROM version 1.0(3), a downloadable ROM upgrade available from Cisco.com. Please contact Cisco to upgrade to this version or later, and prevent this problem from occurring.
Phone Mate Answering Machine Model 9200
A Phone Mate answering machine model 9200 failed to recognize the ringing signal sent by AMD R79 ringing SLIC. This was confirmed by testing against Phone Mate model 3750 and newer model 9300.
B Channel Activation
When a call comes in, a B channel is activated. If the amount of traffic on the B channel exceeds a threshold, the other B channel is activated. If the amount of traffic falls below the threshold, one of the B channels is deactivated. The B channel that is initially activated when the call comes in is not necessarily B1, nor is the B channel that is deactivated when the traffic level lessens necessarily B2.
Cisco uBR924 Cable Access Router
This section contains the following sections with information that is specific to the Cisco uBR924 cable access router:
•
Introduction
The DOCSIS-based Cisco uBR924 cable access router gives residential or small office/home office (SOHO) subscribers high-speed Internet or intranet access. The Cisco uBR924 cable access router supports both data traffic and packet voice and fax traffic via a shared two-way cable system and IP backbone network. The Cisco uBR924 cable access router connects computers and other customer premises devices at a subscriber site to the service provider's cable, hybrid-fiber coaxial (HFC), and IP backbone network.
The Cisco uBR924 cable access router is based on Data-over-Cable Service Interface Specifications (DOCSIS) and interoperates with any bidirectional, DOCSIS-qualified cable modem termination system (CMTS). The Cisco uBR924 cable access router ships from the Cisco factory with a Cisco IOS software image stored in nonvolatile Flash memory that supports DOCSIS-compliant bridging data operations. The Cisco uBR924 cable access router functions as a cable modem at the subscriber site to convey data communications on the cable television system.
Based on the feature licenses your company purchased, other Cisco IOS images can be downloaded from Cisco.com. Special operating modes, based on your service offering and the practices in place for your network, can be supported for the Cisco uBR924 router, based on the available images in Cisco IOS Release 12.2. The Cisco uBR924 Cable Access Router can also function as an advanced router, providing WAN data connectivity in a variety of configurations.
Note
Cisco uBR924 Cable Access Router
The Cisco uBR924 Cable Access Router features a single F-connector interface to the cable system, four RJ-45 (10BASE-T Ethernet) hub ports, two RJ-11 Foreign Exchange Station (FXS) voice ports, one RJ-11 port for an optional backup analog telephone line connection, and one RJ-45 console port to connect to a laptop computer/console terminal for local Cisco IOS configuration. The Cisco uBR924 Cable Access Router supports voice and data Cisco IOS software images; available feature sets include Easy IP, Firewall Phase II (Cisco Secure Integrated Software), and IP Security (IPSec).
Memory Recommendations
For memory recommendations for the Cisco uBR924 cable access router in Cisco IOS Release 12.2, refer to the "Memory Recommendations" section.
Headend Interoperability
Cisco Cable Clock Card Support
When using Cisco IOS Release 12.1(1)T or greater, the Cisco uBR924 cable access router automatically supports the Cisco Cable Clock Card feature for voice traffic when the CMTS is a Cisco uBR7200 series universal broadband router with the Cisco Cable Clock Card feature.
DOCSIS Concatenation
If using DOCSIS concatenation with a 16-QAM (quadrature amplitude modulation) symbol rate, the CMTS must be configured for Unique Word 16 in the preamble for both short and long data burst profiles. On the Cisco uBR7200 series universal broadband routers, use the cable modulation-profile global configuration command and specify "uw16" for both the long and short modulation profiles.
DOCSIS 1.0+ Extensions
Cisco IOS Release 12.2 images support the Cisco DOCSIS 1.0+ Extensions, which include dynamic multi-SID assignment and concatenation. To use the dynamic multi-SID and concatenation features, both the Cisco uBR924 router and the CMTS router must support them. If you are using the Cisco uBR7200 series headend equipment as the CMTS router, Cisco IOS Release 12.0(7)XR, Release 12.1(1)T, or greater is required on both the Cisco uBR924 cable access router and the CMTS router to ensure that these features are activated.
To configure the Cisco uBR924 cable access router to support multiple classes of service, use either the Cisco Subscriber Registration Center (CSRC) tool or the configuration file editor of your choice. DOCSIS configuration files can contain multiple classes of service (CoS) to support voice. The first CoS is used for data (and voice if no other CoS is defined), and up to three additional classes of service can be defined to give higher priority for voice traffic.
IPSec Encryption Support
To use IPSec encryption, both the Cisco uBR924 cable access router and the destination endpoint must support IPSec encryption and be configured for the same encryption policy. The endpoint is typically an IPSec gateway such as a peer router, PIX Firewall, or other device that can be configured for IPSec. (The CMTS does not need to support IPSec encryption unless it is desired that the CMTS act as an IPSec gateway.)
Note
Voice Protocol Support
When using a voice-enabled Cisco IOS Release 12.1 image, the Cisco uBR924 cable access router can packetize and transport voice in compliance with the H.323 protocol. H.323v2 is integrated in Cisco gatekeeper/gateway products, such as the Cisco 2600 series and Cisco 3600 series, using Cisco IOS Release 12.0(5)T. The gatekeeper must be running Cisco IOS Release 12.0(5)T or greater to support registration of the full E.164 address for each Cisco uBR924 Cable Access Router voice port.
The Cisco uBR924 cable access router also supports the Simple Gateway Control Protocol (SGCP) when using voice-enabled Cisco IOS Release 12.1 images. SGCP is an alternative to the H.323 protocol that provides signaling and feature negotiation via a remote Call Agent. SGCP eliminates the need for a dial plan mapper. It also eliminates the need for static configuration on the router to map IP addresses to telephone numbers because this function is provided by the remote Call Agent.
Hardware Supported
The Cisco uBR924 cable access router contains the following interfaces:
•
•
–
Note
–
•
•
•
For detailed descriptions of the new hardware features, see the "New and Changed Information" section on page 93.
Feature Support
For feature support in Cisco IOS Release 12.2, refer to the "Feature Support" section.
Limitations and Restrictions
Bridging Support
The Cisco uBR924 Cable Access Router interoperates with DOCSIS cable networks. Cisco IOS Release 12.1 T does not support bridging traffic across a non-DOCSIS cable network.
Detecting Carrier Sense Errors
The Cisco uBR924 cable access router cannot detect carrier sense errors on the four Ethernet ports that connect the router to the subscriber's local area network. This limitation is because the four Ethernet ports are provided by an internal hub that always provides a carrier sense signal to the Cisco IOS software, even if no Ethernet devices are connected to the external ports. In particular, this means that the dot3StatsCarrierSenseErrors attribute in ETHERLIKE-MIB (RFC 2665) will never indicate any drops in carrier of the Ethernet interface.
DOCSIS CLI Commands Are Removed
To comply with DOCSIS requirements that restrict access to commands that change DOCSIS parameters, Cisco IOS Release 12.1(2)T has removed a number of commands from the command line interface (CLI). These commands are now reserved exclusively for DOCSIS use.
IP Address Negotiation
The DOCSIS specifications require that a cable modem obtain its IP address at power-on or reset from a Dynamic Host Configuration Protocol (DHCP) server that is available through the cable interface. For this reason, the Cisco uBR924 cable access router defaults to a configuration that uses the ip address docsis command for the cable interface. It is not possible to override this setting by specifying a specific static IP address; to assign a static IP address to the Cisco uBR924 router, configure the DHCP server so that it assigns the desired IP address on the basis of the unit's MAC address. However, service providers should warn subscribers that changes in the topology of the cable network—because of traffic levels, growth, or changes to the cable plant and other hardware—might still require changing the subnets and IP addresses assigned to a particular cable modem.
Note
Upgrading Software Images Using BPI
To enable BPI encryption, the Cisco uBR924 cable access router must use a Cisco IOS image that supports BPI encryption. If the router's current software image does not support BPI encryption (or if the current software image is corrupted), you must disable BPI encryption in the DOCSIS configuration file and reset the router before you will be able to download a new software image.
Using Access Lists with IPSec Images
Access lists 100 and 101 should never be manually configured on the Cisco uBR924 cable access router. Configuring these access lists with Cisco IOS Release 12.1 T images that support any form of IPSec encryption can crash the router. Use any access lists 102 through 199 instead.
Using Multiple PCs with the Cisco uBR924 Cable Access Router
The "MAX CPE" parameter in a Cisco uBR924 cable access router's DOCSIS configuration file determines how many PCs (or other customer premises equipment [CPE] devices) are supported by the Cisco uBR924 cable access router. The default value for the "MAX CPE" parameter is 1, which means only one PC can be connected to the Cisco uBR924 cable access router.
The DOCSIS 1.0 specification states that a CMTS cannot age out MAC addresses for CPE devices, so the first PC that is connected to the Cisco uBR924 cable access router is normally the only one that the CMTS recognizes as valid. If a subscriber replaces an existing PC or changes its network interface card (NIC) to one that has a different MAC address, the CMTS will refuse to let the PC come online because this would exceed the maximum number of CPE devices specified by the "MAX CPE" parameter. A similar result would occur if a user decided to move a PC from one Cisco uBR924 router to another.
To allow a subscriber to replace an existing PC or NIC, the following workarounds are possible:
•
•
Using the Reset Switch
The reset switch on the back panel of the Cisco uBR924 cable access router is recessed to prevent accidental resets of the router. To depress the switch, use a blunt object, such as a pen or pencil point; do not use a sharp object, such as a knife or awl, because this could damage the switch and the router's circuitry.
Additional Notes for the Cisco uBR924 Cable Access Router
CPE Device Filtering
In Cisco IOS Release 12.1(2)T and above, the "docsDevCpeIpMax" attribute defaults to -1 instead of the previous default of 1. This attribute controls the maximum number of CPE devices that can pass traffic through the router from its Ethernet interface as follows:
•
•
•
CPE IP address filtering is done as part of the following process:
1.
2.
3.
4.
Refer to the DOCS-CABLE-DEVICE-MIB.my MIB for more information on the attributes and tables listed above.
Disabling the Finger Server
By default, the Cisco uBR900 series cable access router enables its onboard TCP/IP "finger" server to allow remote users to query the number and identities of any users who are logged in to the router. Unless your network operations center (NOC) requires this service, it should be disabled to prevent denial-of-service attacks that access the finger server's well-known port (TCP port 79). To disable the finger server, include the no service finger command in the Cisco IOS configuration file that the router downloads at initial power-on.
Supplemental and Corrected Text for the Online Feature Module
Troubleshooting Tips for the uBR924 cable access router, page 15, indicates:
"Some CATV systems use alternative frequency plans such as the IRC (Incrementally Related Carrier) and HRC (Harmonically Related Carrier) plans. Most of the IRC channel slots overlap the EIA plan. The HRC plan is not supported by Cisco's cable access routers since so few cable plants are using this plan."
The correction should read:
"For the Cisco uBR924 cable access router, both the IRC (Incrementally Related Carrier) and HRC (Harmonically Related Carrier) plans are supported. Most of the IRC channel slots overlap the EIA plan. For the Cisco uBR924 cable access router, both the IRC and HRC plans are supported.
"The list of downstream search bands added for HRC have appropriate center frequencies and step values for an HRC channel plan. The expanded search band list may increase the amount of time required by the Cisco uBR924 cable access router to acquire the downstream signal on the HRC channel plan, which can add to the total time for complete registration of the modem the very first time it is added to the cable system."
Supported MIBs
The Cisco uBR924 cable access router supports the following categories of MIBs:
•
•
•
•
•
•
•
Cable Device MIBs
The Cisco uBR924 Cable Access Router supports the Cable Device MIB, which is defined by RFC 2669 and describes DOCSIS-compliant cable modems and CMTS. The Cable Device MIB records statistics related to the configuration and status of the cable modem. Statistics include an events log and device status. The following list details the components of the Cable Device MIB:
•
•
•
•
•
•
The Cable Device MIB is very similar to the RFI MIB in that both allow access to statistics; they are different in that the Cable Device MIB reports statistics on the cable modem, while the RFI MIB reports statistics on the radio frequency transmissions over the cable television line.
Cisco Standard MIBs
The Cisco uBR924 Cable Access Router supports the Cisco Standard MIBs, which consist of the following components:
•
•
•
•
•
•
Note
Products and Services: Cisco IOS Software: Cisco IOS Software Releases 12.2: Troubleshooting: Bug Toolkit.
Cisco Voice MIBs
The Cisco uBR924 Cable Access Router supports the Cisco Voice MIBs, which consist of the following components:
•
•
•
•
•
•
•
Radio Frequency Interface MIBs
The Cisco uBR924 Cable Access Router supports the Radio Frequency Interface (RFI) MIB. The RFI MIB module is defined in RFC 2670 and describes DOCSIS-compliant radio frequency interfaces in cable modems and CMTS. On the cable modem, RFI MIB entries provide:
•
•
•
•
•
The RFI MIB includes tables that describe both the CMTS and the cable modem side of the cable interface. All cable modem tables are implemented.
With IPSec, data can be transmitted across a public network without fear of observation, modification, or spoofing. This enables applications such as VPNs, extranets, and remote user access.
IPSec services are similar to those provided by Cisco Encryption Technology, a proprietary Cisco security solution. However, IPSec provides a more robust security solution and is standards based.
SGCP and MGCP MIBs
The Cisco uBR924 Cable Access Router supports the Simple Gateway Control Protocol (SGCP) and Media Gateway Control Protocol (MGCP) through a single MIB (XGCP-MIB). This MIB supports configuration, performance, and fault management of the SGCP and MGCP interfaces.
The key attributes of this MIB are as follows:
•
•
•
•
•
•
•
•
•
•
•
•
Note
Cable-Specific MIBs
Table 3 shows the cable-specific MIBs that are supported on the Cisco uBR924 Cable Access Router. This table also provides a brief description of each MIB 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.
Note
Table 3 Supported MIBs for the Cisco uBR924 Cable Access Router
SNMPv2-SMI.my
SNMPv2-SMI-V1SMI.my
This module specifies the Structure of Management Information (SMI) for SNMPv2, as defined in RFC 1902.
12.0(4)XI
SNMPv2-TC.my
SNMPv2-TC-V1SMI.my
This module defines the textual conventions as specified in pages 4 and 10-11 of RFC 854.
12.0(4)XI
CISCO-SMI.my
CISCO-SMI-V1SMI.my
This module specifies the SMI for Cisco's enterprise MIBs.
12.0(4)XI
CISCO-TC.my
CISCO-TC-V1SMI.my
This module defines the textual conventions used in Cisco's enterprise MIBs.
12.0(4)XI
IF-MIB.my
IF-MIB-V1SMI.my
This module describes generic objects for the Layer 3 network interface sublayers. This MIB is an updated version of MIB-II's if table and incorporates the extensions defined in RFC 2233.
12.0(4)XI
RFC 2233 support: 12.1(2)T
CISCO-CABLE-SPECTRUM-MIB.my
CISCO-CABLE-SPECTRUM-MIB-V1SMI.my
This module describes the spectrum management flap list
attributes.12.0(5)T1
DOCS-IF-MIB.my
DOCS-IF-MIB-V1SMI.my
This module describes the DOCSIS-compliant Radio Frequency (RF) interfaces in cable modems and cable modem termination systems, as described in RFC 2670.
12.0(4)XI
RFC 2670 support: 12.1(1)T
DOCS-BPI-MIB.my
DOCS-BPI-MIB-V1SMI.my
This module describes the attributes for the DOCSIS-specified Baseline Privacy Interface (BPI) on cable modems and the CMTS.
12.0(5)T
CISCO-DOCS-EXT-MIB.my
CISCO-DOCS-EXT-MIB-V1SMI.my
This module extends the DOCSIS standard RFI MIB (DOCS-IF-MIB) with Cisco-specific extensions, such as QoS attributes and connection status and other information regarding the cable modems and CPE devices supported by the CMTS.
Note
Partial support:
12.0(4)XIFull support:
12.0(5)T1DOCS-CABLE-DEVICE-MIB.my
DOCS-CABLE-DEVICE-MIB-V1SMI.my
This module was previously known as the CABLE-DEVICE-MIB and contains cable-related objects for DOCSIS-compliant cable modems, as specified in RFC 2669.
12.0(4)XI
RFC 2669 support:
12.1(1)T
Note
Guest
