Table Of Contents
Release Notes for Cisco uBR924 Cable Access Router for Cisco IOS Release 12.1(3a) T1
Cisco uBR924 Cable Access Router
Cisco Cable Clock Card Support
Determining the Software Version
Upgrading to a New Software Release
No New Hardware Features in Release 12.1(3a) T1
New Software Features in Release 12.1(3a) T1
HSRP Support for ICMP Redirects (CSCdp37610)
Media Gateway Control Protocol Residential Gateway Support
Secure Shell Version 1 Client Support
No New Hardware Features in Release 12.1(2) T
New Software Features in Release 12.1(2) T
Ecosystem Gatekeeper Interoperability Enhancements, Phase 2
H.323 Support for Virtual Interfaces
No New Hardware Features in Release 12.1(1) T
New Software Features in Release 12.1(1) T
Cable Monitor Web Diagnostics Tool
Cisco Cable Clock Card Support
Dynamic Host Configuration Protocol Proxy Support
Ecosystem Gatekeeper Interoperability Enhancements
New Hardware Features in Release 12.1(1)
New Software Features in Release 12.1(1)
Management Information Base (MIB) Features
DOCSIS CLI Commands are Removed
GRE IP Tunnels are Not Supported
Upgrading Software Images Using BPI
Using Access Lists with IPsec Images
Using Multiple PCs with the Cisco uBR924 Cable Access Router
Supplemental and Corrected Text for the Online Feature Module
Radio Frequency Interface MIBs
Open Caveats—Release 12.1(3a) T1
Closed or Resolved Caveats—Release 12.1(3a) T1
Cisco IOS Software Documentation Set
Release 12.1 Documentation Set
Obtaining Technical Assistance
Software Configuration Tips on the Cisco Technical Assistance Center Home Page
Release Notes for Cisco uBR924 Cable Access Router for Cisco IOS Release 12.1(3a) T1
July 24, 2000
Part Number: OL-0385-03-Rev.B0
Note
You can find the most current Cisco IOS documentation on Cisco Connection Online (CCO). These electronic documents may contain updates and modifications made after this document was published.
These release notes for the Cisco uBR924 Cable Access Router describe the enhancements provided in Cisco IOS Release 12.1(3a) T1. These release notes are updated as needed to describe new features, memory requirements, hardware support, software platform deferrals, and changes to the microcode or modem code and related documents.
For a list of software caveats that apply to Release 12.1(3a) T1, see the "Caveats" section and Caveats for Cisco IOS Release 12.1 T. The caveats document is updated for every maintenance release and is located on Cisco Connection Online (CCO) and the Documentation CD-ROM.
Use these release notes with Cross-Platform Release Notes for Cisco IOS Release 12.1 T located on CCO and the Documentation CD-ROM.
Note
Contents
These release notes describe the following topics:
•
Introduction
The DOCSIS-based Cisco uBR924 Cable Access Router gives residential or small office/home office (SOHO) subscribers high-speed Internet or Intranet access. The Cisco uBR924 Cable Access Router supports both data traffic and packet voice and fax traffic via a shared two-way cable system and 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 coax (HFC), and IP backbone network.
The Cisco uBR924 Cable Access Router is based on Data-Over-Cable Service Interface Specifications (DOCSIS) and interoperate with any bidirectional, DOCSIS-qualified Cable Modem Termination System (CMTS). The Cisco uBR924 Cable Access Router ships from the Cisco factory with a Cisco IOS software image stored in nonvolatile Flash memory that supports DOCSIS-compliant bridging data operations. The Cisco uBR924 Cable Access Router functions as a cable modem at the subscriber site to convey data communications on the cable television system.
Note
Based on the feature licenses your company purchased, other Cisco IOS images can be downloaded from Cisco Connection Online (CCO). Special operating modes, based on your service offering and the practices in place for your network, can be supported for the Cisco uBR924 router, based on the available images in Cisco IOS Release 12.1(3a) T1. The Cisco uBR924 Cable Access Router can also function as an advanced router, providing wide area network (WAN) data connectivity in a variety of configurations.
Note
Cisco uBR924 Cable Access Router
The Cisco uBR924 Cable Access Router features a single F-connector interface to the cable system, four RJ-45 (10BaseT Ethernet) hub ports, two RJ-11 Foreign Exchange Station (FXS) voice ports, one RJ-11 port for an optional backup analog telephone line connection, and one RJ-45 console port to connect to a laptop computer/console terminal for local Cisco IOS configuration. The Cisco uBR924 Cable Access Router supports voice and data Cisco IOS software images; available feature sets include Easy IP, Cisco Secure Integrated Software (Firewall Phase II), and IPsec encryption.
Early Deployment Releases
These release notes describe the Cisco uBR924 Cable Access Router for Cisco IOS Release 12.1(3a) T1, which is an early deployment (ED) release based on Cisco IOS Release 12.1. Early deployment releases contain fixes for software caveats and support for new Cisco hardware and software features.
Table 1 shows recent early deployment releases of the Cisco uBR924 Cable Access Router:
System Requirements
This section describes the system requirements for Cisco IOS Releases 12.1(3a) T1:
•
•
Memory Recommendations
Table 2 lists the memory recommendations for each of the feature sets available for the Cisco uBR924 Cable Access Router in Cisco IOS Release 12.1(3a) T1. The image subset legend for Table 2Table 2 is as follows:
•
•
•
•
•
•
Table 2 Memory Recommendations for the Cisco uBR924 Cable Access Router,
Release 12.1(3a) T1 Feature Sets
Flash
Memory
DRAM
Memory
FromHome Office with Voice—Base image with Easy IP and Voice
ubr920-k1v4y5-mz
4 MB Flash
16 MB DRAM
RAM
Value Telecommuter—Easy IP, Voice, and IPsec 56
ubr920-k1v4y556i-mz
4 MB Flash
16 MB DRAM
RAM
Performance Telecommuter— Easy IP, Voice, and IPsec 3DES
ubr920-k1k2v4y5-mz
4 MB Flash
16 MB DRAM
RAM
Value Small Office—Easy IP, Voice, FW2 , and IPsec 56
ubr920-k1o3v4y556i-mz
4 MB Flash
16 MB DRAM
RAM
Performance Small Office— Easy IP, Voice, FW2, and IPsec 3DES
ubr920-k1k2o3v4y5-mz
4 MB Flash
16 MB DRAM
RAM
1 L2TP is not supported in any Cisco IOS Release 12.1(3a) T1 images for the Cisco uBR924 Cable Access Router.
2 FW—Firewall (Cisco Secure Integrated Software)
Note
Headend Interoperability
Cisco Cable Clock Card Support
When using Cisco IOS Release 12.1(1) T or greater, the Cisco uBR924 Cable Access Router automatically supports the Cisco Cable Clock Card feature for voice traffic when the CMTS is a Cisco uBR7200 series universal broadband router with the Cisco Cable Clock Card feature.
DOCSIS Concatenation
If using DOCSIS concatenation with a 16 QAM symbol rate, the CMTS must be configured for Unique Word 16 in the preamble for both short and long data burst profiles. On the Cisco uBR7200 series universal broadband routers, use the cable modulation-profile global configuration command and specify uw16 for both the long and short modulation profiles. See caveats CSCdp76415 and CSCdp92139 for more detail.
DOCSIS 1.0+ Extensions
Cisco IOS Release 12.1 T images support the Cisco DOCSIS 1.0+ Extensions, which include dynamic multi-SID assignment and concatenation. To use the dynamic multi-SID and concatenation features, both the Cisco uBR924 router and the CMTS router must have 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 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 both 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 (CA). SGCP eliminates the need for a dial plan mapper. It also eliminates the need for static configuration on the router to map IP addresses to telephone numbers because this function is provided by the remote CA.
Hardware Supported
The Cisco uBR924 Cable Access Router contains:
•
•
–
–
•
•
•
Determining the Software Version
To determine the version of Cisco IOS software running on your Cisco uBR924 Cable Access Router, log into the Cisco uBR924 Cable Access Router and enter the show version EXEC command:
For the Cisco uBR924 Cable Access Router:
router# show versionCisco Internetwork Operating System SoftwareIOS (tm) 920 Software (ubr920-k1v4y5-mz), Version 12.1(3a) T1, RELEASE SOFTWAREUpgrading to a New Software Release
For technical information about upgrading to a new software release, see Cisco IOS Upgrade Ordering Instructions on CCO located at:
http://www.cisco.com/warp/public/620/6.html
For other information about upgrading to Cisco IOS Release 12.1, see the product bulletin Cisco IOS Software Release 12.1 Upgrade Paths and Packaging Simplification on CCO at:
Service & Support: Software Center: Cisco IOS Software: Product Bulletins: Software
Under Cisco IOS 12.1, click Cisco IOS Software Release 12.1 Ordering Procedures and Platform Support
Feature Set Tables
Cisco IOS software is packaged in feature sets consisting of software images—depending on the platform. Each feature set contains a specific set of Cisco IOS features.
Caution
Table 3 lists the voice and data software images by feature sets for the Cisco uBR924 Cable Access Router. This table uses the following conventions:
•
•
Note
Table 3 Feature List by Feature Set for the Cisco uBR924 Cable Access Router—Voice and Data
Baseline Privacy Interface (BPI) Encryption
Yes
Yes
Yes
Yes
Yes
Baseline Privacy Interface (BPI) MIB
Yes
Yes
Yes
Yes
Yes
Cable Device MIB (RFC 2669)
Yes
Yes
Yes
Yes
Yes
Cable Monitor
Yes
Yes
Yes
Yes
Yes
Cisco Secure Integrated Software (Firewall)
No
No
No
Yes
Yes
Cisco Standard MIBs
Yes
Yes
Yes
Yes
Yes
Cisco Voice MIBs
Yes
Yes
Yes
Yes
Yes
Configurable H.225 Timers
Yes
Yes
Yes
Yes
Yes
DHCP Proxy Support
Yes
Yes
Yes
Yes
Yes
DOCSIS 1.0+ Extensions (Dynamic multi-SID assignment and concatenation)
Yes
Yes
Yes
Yes
Yes
DOCSIS-Compliant Bridging
Yes
Yes
Yes
Yes
Yes
Easy IP
Yes
Yes
Yes
Yes
Yes
Ecosystem Gatekeeper Interoperability Enhancements
Yes
Yes
Yes
Yes
Yes
HSRP Support for ICMP Redirect
Yes
Yes
Yes
Yes
Yes
H.323v2 Protocol
Yes
Yes
Yes
Yes
Yes
H.323 Support for Virtual Interfaces
Yes
Yes
Yes
Yes
Yes
IPsec Encryption with 56-bit DES
No
Yes
Yes
Yes
Yes
IPsec Encryption with Triple DES (3DES)
No
No
Yes
No
Yes
Layer 2 Tunneling Protocol (L2TP)1
No
No
No
No
No
Media Gateway Control Protocol (MGCP) Residential Gateway (RGW) Support
Yes
Yes
Yes
Yes
Yes
RFC 2233 Support
Yes
Yes
Yes
Yes
Yes
Radio Frequency Interface MIB (RFC 2670)
Yes
Yes
Yes
Yes
Yes
Routing (RIP V2)
Yes
Yes
Yes
Yes
Yes
Secure Shell (SSH)—56-bit encryption
Yes
Yes
Yes
Yes
Yes
Secure Shell (SSH)—3DES encryption
No
No
Yes
No
Yes
Simple Gateway Control Protocol (SGCP)
Yes
Yes
Yes
Yes
Yes
XGCP MIB
Yes
Yes
Yes
Yes
Yes
1 The L2TP feature set is not supported in any Cisco IOS Release 12.1(3a) T1 images for the Cisco uBR924 Cable Access Router.
New and Changed Information
The following sections list the new hardware and software features supported by the Cisco uBR924 Cable Access Router.
No New Hardware Features in Release 12.1(3a) T1
Cisco IOS Release 12.1(3a) T1 does not contain any new hardware features for the Cisco uBR924 Cable Access Router.
New Software Features in Release 12.1(3a) T1
The following new software features are supported by the Cisco uBR924 Cable Access Router for Release 12.1(3a) T1.
IP Address Negotiation
Cisco IOS Release 12.1(3a) T1 for Cisco uBR900 series Cable Access Routers adds support for the ip address dhcp command on the cable interface. Previous releases used the ip address negotiated command for this purpose, but this command is now reserved for serial interfaces. This change is cosmetic only and does not change how the router obtains its IP address. See "IP Address Negotiation" section for additional information.
HSRP Support for ICMP Redirects (CSCdp37610)
The HSRP Support for ICMP Redirects feature enables Internet Control Message Protocol (ICMP) redirection on interfaces configured with the Hot Standby Router Protocol.
When running HSRP, it is important to prevent hosts from discovering the interface (or real) MAC addresses of routers in the HSRP group. If a host is redirected by ICMP to the real MAC address of a router, and that router later fails, then packets from the host will be lost. Previously, ICMP redirect messages were automatically disabled on interfaces configured with HSRP.
This feature now enables ICMP redirects on interfaces configured with HSRP. This functionality works by filtering outgoing ICMP redirect messages through HSRP, where the next-hop IP address may be changed to an HSRP virtual IP address.
Media Gateway Control Protocol Residential Gateway Support
Cisco IOS Release 12.1(3a) T1 for the Cisco uBR924 Cable Access Router supports version 0.1 of the Media Gateway Control Protocol (MGCP), a proposed IETF voice control protocol that is intended to eventually supersede the existing SCGP 1.1 protocol. The MGCP 0.1 and SGCP 1.1 protocols have been merged on the Cisco uBR924 router so that the router can respond efficiently to either protocol.
The Cisco uBR924 Cable Access Router functions as a Residential Gateway (RGW), providing an interface between analog FXS phone or fax systems and the Voice over IP (VoIP) network. The RGW uses a Trunking Gateway (TGW) to contact the call agent, which in turn provides access to the public telephone switched network (PTSN).
The Cisco uBR924 Cable Access Router supports both call waiting and caller ID when using either MGCP or SGCP for call control. Each of the two voice ports on the Cisco uBR924 router can be configured with the IP address for a default call agent. SNMP management of both the MGCP and SNMP protocols is provided by a single MIB (XGCP-MIB).
Note
Secure Shell Version 1 Client Support
Cisco IOS Release 12.1(3a) T1 enhances the router's support for the Secure Shell (SSH) protocol, which was introduced in Cisco IOS Release 12.1(1) T (see the "Secure Shell Server Support" section). SSH connections use encryption and user authentication to establish a secure communications channel over an insecure network, such as the Internet.
In Cisco IOS Release 12.1(3a) T1, SSH support now includes the following features:
•
•
•
•
Note
No New Hardware Features in Release 12.1(2) T
Cisco IOS Release 12.1(2) T does not contain any new hardware features for the Cisco uBR924 Cable Access Router.
New Software Features in Release 12.1(2) T
The following new software features are supported by the Cisco uBR924 Cable Access Router for Release 12.1(2) T. For more information on these features, see the documentation listed in the "Related Documentation" section.
Configurable H.225 Timer
In previous Cisco IOS releases, the H.225 TCP connection timeout timer was fixed at 15 seconds. Cisco IOS Release 12.1(2) T adds the ability to configure this timer to a value between 1-30 seconds, or to disable it entirely.
Note
Ecosystem Gatekeeper Interoperability Enhancements, Phase 2
This feature enhances the existing Ecosystem Gatekeeper Interoperability Enhancements feature to improve the ability of voice gateways to move between gatekeepers upon a failure or an outage. In addition to the existing features, phase 2 adds support for the alternate gatekeeper field (altGKInfo) to the admission rejection (ARJ) message. This allows a gateway to move between gatekeepers during the admission request (ARQ) phase.
Phase 2 of this feature is introduced in Cisco IOS Release 12.1(2) T.
Note
H.323 Support for Virtual Interfaces
Cisco IOS Release 12.1(2) T for the Cisco uBR924 Cable Access Router introduces a new interface command to control the IP address used for outgoing H.323 VoIP traffic:
h323-gateway voip bind srcaddr ip address
The h323-gateway voip bind command can be used with any interface, but its primary use is with the Cisco uBR924 router's Ethernet interface when configuring a virtual private network (VPN). In this configuration, the h323-gateway voip bind command configures the router so that VoIP traffic is sent and received using the IP address of the Ethernet interface (as opposed to the default behavior, which is to use the IP address of the default outgoing interface, which is the cable interface).
The h323-gateway voip bind command allows the enterprise network to maintain the H.323 gatekeeper and gateway in the enterprise network's address space. Without the h323-gateway voip bind command, outgoing voice traffic uses the IP address of the cable interface. This requires that the H.323 gatekeeper and gateway be maintained in the cable service provider's address space, which is not desirable if the enterprise needs to control the voice network and VPN configuration.
Note
This feature was tracked as caveat CSCdp11931, and it was introduced in Cisco IOS Release 12.1(2) T.
RFC 2233 Support
Cisco IOS Release 12.1(2) T updates the IF-MIB MIB with support for RFC 2233, which obsoletes the previous RFC 1573. This change adds the ifCounterDiscontinuityTime attribute and changes the ifTableLastChange attribute.
In addition, this feature adds support for RFC 2233-compliant link up and link down traps. By default, link up and link down traps are implemented as given in the CISCO-IF-CAPABILITY.my MIB. To generate link up and link down traps as defined by RFC 2233, use the snmp-server trap link ietf global configuration command.
This feature was tracked as caveats CSCdp41317 and CSCdp55546, and it is introduced in Cisco IOS Release 12.1(2) T.
No New Hardware Features in Release 12.1(1) T
Cisco IOS Release 12.1(1) T does not contain any new hardware features for the Cisco uBR924 Cable Access Router.
New Software Features in Release 12.1(1) T
The following new software features are supported by the Cisco uBR924 Cable Access Router for Release 12.1(1) T. For more information on these features, see the documentation listed in the "Related Documentation" section.
Cable Monitor Web Diagnostics Tool
The Cable Monitor is a web-based diagnostic tool to display the current status and configuration of the Cisco uBR924 router. The Cable Monitor can also be used when the cable network is down, providing an easy way for subscribers to provide necessary information to service technicians and troubleshooters.
The Cable Monitor is introduced in Cisco IOS Release 12.1(1) T.
Cisco Cable Clock Card Support
When using Cisco IOS Release 12.1(1) T or greater, the Cisco uBR924 Cable Access Router automatically supports the Cisco Cable Clock Card feature for voice traffic when the CMTS is a Cisco uBR7200 series universal broadband router with the Cisco Cable Clock Card feature. This feature can enhance reliability in a voice network and reduce delay and jitter in the voice traffic.
DOCSIS 1.0+ Extensions
In addition to the other QoS features, DOCSIS 1.1 supports a number of features that are required for the delivery of high quality voice traffic. To use these features before the DOCSIS 1.1 specification is finalized, Cisco has created the DOCSIS 1.0+ extensions that contain the most important of these features:
•
•
To avoid potentially wasting bandwidth in this manner, the DOCSIS 1.0+ extensions support the dynamic creation of multiple SIDs. New MAC messages dynamically add, delete, and modify SIDs when needed. When a phone connected to the router is taken off-hook, the Cisco uBR924 router creates a SID that has the QoS parameters needed for that particular voice call. When the call terminates, the router deletes the SID, releasing its bandwidth for use elsewhere.
The DOCSIS 1.0+ features are introduced in Cisco IOS Software Release 12.0(7) XR and 12.1(1) T.
Note
Dynamic Host Configuration Protocol Proxy Support
The DHCP Proxy Support feature helps to automate the configuration of the Cisco uBR924 Cable Access Router in two situations:
•
•
When configured for DHCP Proxy Support, during startup the Cisco uBR924 Cable Access Router sends a proxy DHCP request to the DHCP server using the Ethernet interface's MAC address. The DHCP server replies with a second IP address that the router assigns to either the Ethernet interface or to the NAT pool, depending on which option was specified.
Ecosystem Gatekeeper Interoperability Enhancements
The Ecosystem Gatekeeper Interoperability Enhancements feature improves the ability of voice gateways to move between gatekeepers upon a failure or an outage. Currently, gateways can be configured to switch from their primary gatekeeper to an alternate gatekeeper if a failure or outage occurs.
However, moving gateways from one gatekeeper to another can create an imbalance in the number of gateways registered to each gatekeeper. The Ecosystem Gatekeeper Interoperability Enhancements feature helps to restore the balance by moving some of the gateways back to their proper gatekeepers after the outage has been corrected.
This feature adds support for the alternate gatekeeper field (altGKInfo) to the gatekeeper rejection (GRJ) and registration rejection (RRJ) messages. This allows a gateway to move between gatekeepers during the gatekeeper request (GRQ) and registration request (RRQ) phases.
This feature is introduced in Cisco IOS Release 12.1(1) T.
Note
H.323 Enhancements
Cisco IOS Release 12.1(1) T adds a number of H.323v2 features for voice support:
•
•
–
–
This feature is introduced in Cisco IOS Release 12.0(7) XR and Release 12.1(1) T.
Note
Secure Shell Server Support
The Cisco uBR924 router supports the Secure Shell (SSH) Version 1 protocol, which allows network administrators to make a secure Telnet connection with the router. SSH provides for authentication and encryption at the application layer, providing a secure connection even when BPI or IPsec authentication and encryption are not used at the network layer.
By default, the SSH feature uses 56-bit DES encryption. Higher security 168-bit 3DES encryption is available when using Cisco IOS images that support 3DES IPsec encryption. (The SSH client must also support the same level of encryption.)
SSH client server is introduced in Cisco IOS Release 12.1(1) T.
SNMP Enhancements
Cisco IOS Release 12.1(1) T adds support for RFC 2669 and RFC 2670 to the DOCS-CABLE-DEVICE-MIB and DOCS-IF-MIB MIBs, respectively.
New Hardware Features in Release 12.1(1)
The following new hardware features are supported by the Cisco uBR924 Cable Access Router for Release 12.1(1):
•
New Software Features in Release 12.1(1)
The following new software features are supported by the Cisco uBR924 Cable Access Router for Release 12.1(1):
Software Features
•
•
•
•
•
•
•
•
•
•
•
•
•
Management Information Base (MIB) Features
•
•
•
•
•
•
Limitations and Restrictions
This section describes warnings and cautions about using Cisco IOS Release 12.1(3a) T1 software.
Bridging Support
The Cisco uBR924 Cable Access Router interoperates with DOCSIS cable networks. Cisco IOS Release 12.1 T does not support bridging traffic across a non-DOCSIS cable network.
DOCSIS CLI Commands are Removed
To comply with DOCSIS requirements that restrict access to commands that change DOCSIS parameters, Cisco IOS Release 12.1(2) T has removed a number of commands from the CLI. These commands are now reserved exclusively for DOCSIS use. See the description of caveat CSCdr32984 for more details.
GRE IP Tunnels are Not Supported
GRE IP tunnels cannot be built between two Cisco uBR924 Cable Access Routers because GRE IP tunnels are not supported in any Cisco IOS image for the Cisco uBR924 Cable Access Routers. IPsec tunnels, however, are supported when using Cisco IOS images that support IPsec encryption.
IP Address Negotiation
The DOCSIS specifications require that a cable modem obtain its IP address at power-on or reset from a DHCP server that is available through the cable interface. For this reason, the Cisco uBR924 Cable Access Router defaults to a configuration that uses the ip address dhcp command for the cable interface. It is not possible to override this setting by specifying a specific static IP address; to assign a static IP address to the Cisco uBR924 router, configure the DHCP server so that it assigns the desired IP address on the basis of the unit's MAC address.
Note
Upgrading Software Images Using BPI
To enable BPI encryption, the Cisco uBR924 Cable Access Router must use a Cisco IOS image that supports BPI encryption. If the router's current software image does not support BPI encryption (or if the current software image is corrupted), you must disable BPI encryption in the DOCSIS configuration file and reset the router before you will be able to download a new software image.
Using Access Lists with IPsec Images
Access lists 100 and 101 should never be manually configured on the Cisco uBR924 Cable Access Router. Configuring these access lists with Cisco IOS Release 12.1 T images that support any form of IPsec encryption can crash the router. Use any access lists 102 through 199 instead. See the description of caveats CSCdr45850 and CSCdr46128 for more information.
Using Multiple PCs with the Cisco uBR924 Cable Access Router
The MAX CPE parameter in a Cisco uBR924 Cable Access Router's DOCSIS configuration file determines how many PCs (or other CPE devices) are supported by the Cisco uBR924 Cable Access Router. The default value for the MAX CPE parameter is 1, which means only one PC can be connected to the Cisco uBR924 Cable Access Router.
The DOCSIS 1.0 specification states that a CMTS cannot age-out MAC addresses for CPE devices, so the first PC that is connected to the Cisco uBR924 Cable Access Router is normally the only one that the CMTS recognizes as valid. If a subscriber replaces an existing PC or changes its network interface card (NIC) to one that has a different MAC address, the CMTS will refuse to let the PC come online because this would exceed the maximum number of CPE devices specified by the MAX CPE parameter. A similar thing would happen if a user decides to move a PC from one Cisco uBR924 router to another.
To allow a subscriber to replace an existing PC or NIC, the following workarounds are possible:
•
•
Using the Reset Switch
The reset switch on the back panel of the Cisco uBR924 Cable Access Router is recessed to prevent accidental resets of the router. To depress the switch, use a blunt object, such as a pen or pencil point; do not use a sharp object, such as a knife or awl, because this could damage the switch and the router's circuitry.
Important Notes
This section contains important information about using Cisco IOS Release 12.1(3a) T1 software.
CPE Device Filtering
In Cisco IOS Release 12.1(2) T and above, the docsDevCpeIpMax attribute defaults to -1 instead of the previous default of 1. This attribute controls the maximum number of CPE devices that can pass traffic through the router from its Ethernet interface as follows:
•
•
•
CPE IP address filtering is done as part of the following process:
1.
2.
3.
4.
See the DOCS-CABLE-DEVICE-MIB.my MIB for more information on the attributes and tables listed above.
Disabling the Finger Server
By default, the Cisco uBR900 series Cable Access Router enables its onboard TCP/IP "finger" server to allow remote users to query the number and identities of any users who are logged in to the router. Unless your network operations center (NOC) requires this service, it should be disabled to prevent denial of service attacks that access the finger server's well-known port (TCP port 79). To disable the finger server, include the no service finger command in the Cisco IOS configuration file that the router downloads at initial power-on.
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, and the RFI MIB reports statistics on the radio frequency transmissions over the cable television line.
Cisco Standard MIBs
The Cisco uBR924 Cable Access Router supports the Cisco Standard MIBs, which consist of the following components:
•
•
•
•
•
•
Note
Cisco Voice MIBs
The Cisco uBR924 Cable Access Router supports the Cisco Voice MIBs are supported, which consist of the following components:
•
•
•
•
•
•
•
Radio Frequency Interface MIBs
The Cisco uBR924 Cable Access Router supports the Radio Frequency Interface (RFI) MIB. The RFI MIB module is defined in RFC 2670 and describes DOCSIS-compliant radio frequency interfaces in cable modems and CMTS. On the cable modem, RFI MIB entries provide:
•
•
•
•
•
The RFI MIB includes tables describing both the CMTS and the cable modem side of the cable interface. All cable modem tables are implemented.
With IPsec, data can be transmitted across a public network without fear of observation, modification, or spoofing. This enables applications such as VPNs, extranets, and remote user access.
IPsec services are similar to those provided by Cisco Encryption Technology, a proprietary Cisco security solution. However, IPsec provides a more robust security solution, and is standards based.
SGCP and MGCP MIBs
The Cisco uBR924 Cable Access Router supports the Simple Gateway Control Protocol (SGCP) and Media Gateway Control Protocol through a single MIB (XGCP-MIB). This MIB supports configuration, performance, and fault management of the SGCP and MGCP interfaces.
The key attributes of this MIB are as follows:
•
•
•
•
•
•
•
•
•
•
•
•
Note
Cable-Specific MIBs
Table 4 shows the cable-specific MIBs that are supported on the Cisco uBR924 Cable Access Router. This table also provides a brief description of each MIB's contents 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
Note
Deprecated MIBs
A number of Cisco-provided MIBs have been replaced with more scalable, standardized MIBs; these MIBs have filenames that start with "OLD" and first appeared in Cisco IOS Release 10.2. The functionality of these MIBs has already been incorporated into replacement MIBs, but the old MIBs are still present to support existing Cisco IOS products or NMS applications. However, because the deprecated MIBs will be removed from support in the future, you should update your network management applications and scripts to refer to the table names and attributes that are found in the replacement MIBs.
Table 5 shows the deprecated MIBs and their replacements. In most cases, SNMPv1 and SNMPv2 replacements are available, but some MIBs are available only in one version. A few of the deprecated MIBs do not have replacement MIBs; support for these MIBs will be discontinued in a future release of Cisco IOS software.
Note
Caveats
Caveats describe unexpected behavior in Cisco IOS software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious.
This section contains open and resolved caveats for Cisco IOS Release 12.1(3a) T1. All caveats in Release 12.1 are also in Release 12.1(3a) T1.
For information on caveats in Cisco IOS Release 12.1, see Caveats for Cisco IOS Release 12.1, which lists severity 1 and 2 caveats, and is located on CCO and the Documentation CD-ROM.
Note
Open Caveats—Release 12.1(3a) T1
All the caveats listed in this section are open in Release 12.1(3a) T1:
•
This caveat affects the Cisco uBR924 router when it is configured as an H.323 gateway using the following cable interface configuration commands:
–
–
–
When the Cisco uBR924 router reboots, this configuration will fail if these commands are executed before the cable interface acquires a valid IP address from the DHCP server. In this situation, the h323-gateway commands will be ignored, and voice calls that use that gateway will fail.
The workaround is to either reenter the gateway commands manually or to reload the entire configuration using the copy start-config running-config command.
•
The Cisco uBR924 router, when running the NAT and firewall features, crashes if establishing roughly 150 Telnet sessions (using the solaris_telnet client). The workaround is to avoid creating that many Telnet sessions.
•
The Cisco uBR924 Cable Access Router can stop responding to CMTS requests when upstreams are configured with different minislot sizes. The workaround is to configure the upstreams on the CMTS with the same minislot size.
•
When running Cisco IOS Release 11.3(11)NA, the Cisco uBR924 Cable Access Router does not come up when all four downstreams are combined through the upconverter and all of the upstreams of the four cards are combined. When the Cisco uBR924 router is instructed to go to a different downstream, it obtains the correct IP address for the new downstream, but fails to update the default gateway according to the DHCP reply; it subsequently fails to obtain the time-of-day (TOD) or to download the DOCSIS configuration file. The default gateway address must be corrected manually before the router succeeds in obtaining the configuration file and in getting the current time-of-day.
•
The voice-port cptone command does not support the set of telephony tones used in the Czech Republic or in Switzerland. There is no workaround.
•
Packets can be unexpectedly dropped on the upstream channel when the Cisco uBR924 is configured to use DOCSIS concatenation and the upstream is using 16 QAM symbol rate. The workaround is to configure the CMTS for a preamble with Unique Word 16 for both the short and long data burst profile. On the Cisco uBR7200 series universal broadband routers, this can be done with the cable modulation-profile global configuration command, specifying uw16 for both the long and short modulation profiles.
•
The show interface command can show an impossible number of CRC errors on the cable interface when transmitting VoIP traffic. When this error occurs, the number of CRC errors typically exceeds a billion errors and is greater than the total number of packets transmitted on the interface. The workaround is to use the show interface cable 0 counters command to display the correct number of errors.
•
The Cisco uBR924 Cable Access Router can crash when using an access list numbered 100 or 101 while running Cisco IOS Release 12.1 T images that support any form of IPsec encryption. Other access lists, however, can be used without problem.
The workaround is to not configure access list numbers 100 and 101 for any purpose. Instead use access lists 102 through 199 instead.
•
The Cisco uBR924 Cable Access Router defaults to using the ip address dhcp command to set the IP address for the cable interface during power-on provisioning. However, the start-up and running configurations show that the cable interface uses the ip address negotiated command instead. Because only the serial interface can use the ip address negotiated command, this generates an "invalid input" error during start-up. This is only a cosmetic error, however, and does not affect any functionality. There is no workaround.
•
Using the ip pim interface command on the cable interface can force the Cisco uBR924 to go off-line. The workaround is to avoid enabling IP multicast on the cable interface using the ip pim interface command.
•
Upstream performance for data traffic on a DOCSIS 1.0 cable modem is limited to approximately 1.7 mbits per second, due to the limits of using one SID for data traffic, as required by the DOCSIS 1.0 specification. This caveat cannot be resolved until the implementation of the DOCSIS 1.1 specification, which provides for multiple SIDs for data traffic. There is no workaround.
•
The Cisco uBR924 router can eventually crash with "out of memory" errors after making several thousand phone calls if the configuration includes the req-qos controlled-load dial-peer configuration command. The workaround is to remove the req-qos controlled-load dial-peer configuration command.
•
When voice and data are both running in the Frame Relay Low Latency Queuing (FR LLQ) configuration, some of the data packets are being classified as voice. This will result in police and consequent drops for the packets in the priority queue and hence cause bad voice quality.
Workaround: Turn on process-switching on the incoming interfaces for voice and data.
Closed or Resolved Caveats—Release 12.1(3a) T1
All the caveats listed in this section are closed or resolved in Release 12.1(3a) T1:
•
Previously, the Cisco uBR924 Cable Access Router would age-out a CPE device's MAC address after one week of inactivity. This behavior did not conform to the DOCSIS specification, which prohibits aging out of CPE devices.
This is resolved in Cisco IOS Release 12.1(1), so that CPE devices are no longer aged out.
•
These caveats improve the Cisco uBR924 router's error handling when it does not receive a valid response from the time-of-day (ToD) server during its power-on provisioning; an error message is also displayed when a ToD failure occurs. These caveats also add support for using multiple ToD servers when the DHCP server returns a list of two or more ToD servers.
This caveat is resolved in Cisco IOS Release 12.1(1) T.
•
The DOCS-CABLE-DEVICE-MIB.my MIB has been updated to be compliant with RFC 2669, DOCSIS Cable Device MIB Cable Device Management Information Base for DOCSIS compliant Cable Modems and Cable Modem Termination Systems." This includes the following changes:
The root object docsDevMIB has become docsDev. The Object Identifier (OID) for the root has changed from 83 (experimental) to 69 (mib-2).
The following attributes have been added:
–
–
The following attributes have been removed:
–
–
The following attributes have been renamed:
docsDevEvCount
docsDevEvCounts
docsDevFilterLLCDefault
docsDevFilterLLCUnmatchedAction
docsDevCpeMax
docsDevCpeIpMax
The following attributes were changed as noted:
This caveat is resolved in Cisco IOS Release 12.1(1) T.
•
The DOCS-IF-MIB has been updated to support RFC 2670, "Radio Frequency (RF) Interface Management Information Base for MCNS/DOCSIS compliant RF interfaces." This change is in the DOCS-IF-MIB file with a LAST-UPDATED field of "9908190000Z" or later.
The following attributes have been added:
–
–
–
–
The following attributes have been added but currently return an empty string:
–
–
–
–
–
–
The following attributes have been deleted:
–
–
The following attributes have been renamed:
The following attributes were changed as noted:
This caveat is resolved in Cisco IOS Release 12.1(1) T.
•
This caveat adds support for RFC 2233-compliant link up and link down traps. By default, link up and link down traps are implemented as given in the CISCO-IF-CAPABILITY.my MIB. To generate link up and link down traps as defined by RFC 2233, use the snmp-server trap link ietf global configuration command.
This caveat is resolved in Cisco IOS Release 12.1(2) T.
•
This caveat updates the IF-MIB MIB with support for RFC 2233, which obsoletes the previous RFC 1573. This change adds the ifCounterDiscontinuityTime attribute and changes the ifTableLastChange attribute.
This caveat is resolved in Cisco IOS Release 12.1(2) T.
•
The Cisco uBR924 Cable Access Router could not upgrade its software image if the fully-qualified filename for the new image was longer than 48 characters. The workaround was to rename the image with a shorter filename or to move it higher in the TFTP server's directory structure so that the fully-qualified pathname was shorter than 48 characters.
This caveat is resolved in Cisco IOS Release 12.1(1) T.
•
The Cisco uBR924 Cable Access Router, when running one of the Small Office feature sets, can crash with an exception when changing the running configuration. The crash occurs when using a specific configuration designed for test networks and is unlikely to occur when using configurations for real-life networks. This caveat is resolved in Cisco IOS Release 12.1(1) T.
•
This caveat described a problem with GRE IP tunnels that were built between two Cisco uBR900 series Cable Access Routers, using BPI encryption. The resulting tunnels experienced intermittent operation, going down after a few minutes of use. Tunnels built using IPsec encryption were successfully used.
This caveat was closed without modification because GRE tunnels are not currently supported on any software image for the Cisco uBR924 Cable Access Routers. IPsec tunnels, however, are supported when using Cisco IOS images that support IPsec encryption.
•
This caveat described a situation in which two Cisco uBR924 Cable Access Routers could no longer establish voice calls. The routers needed to be reloaded before being able to make additional voice calls.
This caveat is resolved in Cisco IOS Release 12.1(2) T.
•
To comply with DOCSIS regulations that restrict access to commands that change DOCSIS parameters, the following commands have been removed from the CLI:
–
–
–
–
–
In Cisco IOS Release 12.1(2) T, these commands are now reserved exclusively for DOCSIS use.
•
A defect could cause a Cisco router to crash and hang when the Cisco web server was enabled with the ip http server command and a browser connects to http://<router-ip>/%%. The defect could be exploited to produce a denial of service (DoS) attack. This fact was announced on public Internet mailing lists which are widely read both by security professionals and by security "crackers", and should be considered public information.
The workaround to this defect was to disable the Cisco web server with the command:
no ip http serverAlternatively, the administrator could choose to block port 80 connections to the router via access lists or other firewall methods. For further information a Security Advisory will be posted to http://www.cisco.com/warp/public/707/advisory.html.
This caveat is resolved in Cisco IOS Release 12.1(2) T.
•
The Cisco uBR924 Cable Access Router reverses the order in which it should obtain the IP address of its default gateway from the information that the DHCP server supplies during power-on provisioning. If both the router and giaddr fields are present, the Cisco uBR924 Cable Access Router should use the value from the router field as the address for the default gateway, but instead it uses the value from the giaddr field.
This caveat is resolved in Cisco IOS Release 12.1(2) T so that the Cisco uBR924 Cable Access Router uses the router field, if present, as its default gateway. If the DHCP server does not provide the router field, the Cisco uBR924 Cable Access Router then uses the giaddr field.
•
In Cisco IOS Release 12.1(2) T, if two (or more) dial-peers were configured with destination patterns terminated by T, then calls with a dial number that was completed by the # key were routed only to the first matching dial-peer, even if other dial-peers are a better match. There was no workaround.
Related Documentation
The following sections describe the documentation available for the Cisco uBR924 Cable Access Router. These documents consist of hardware and software installation guides, Cisco IOS configuration and command references, system error messages, feature modules, and other documents.
Most documentation is available as printed manuals or electronic documents, except for feature modules and select manuals, which are available online on CCO and the Documentation CD-ROM.
Use these release notes with these documents:
•
Release-Specific Documents
The following documents are specific to Release 12.1 and are located on CCO and the Documentation CD-ROM:
•
On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Release Notes: Cross-Platform Release Notes
•
Technical Documents
•
As a supplement to the caveats listed in these release notes, see Caveats for Cisco IOS Release 12.1, which contains caveats applicable to all platforms for all maintenance releases of Release 12.1.
On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Caveats
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS 12.1: Caveats
Note
Platform-Specific Documents
These documents are available for the Cisco uBR924 Cable Access Router on CCO and the Documentation DC-ROM:
•
•
•
•
•
•
Note
On CCO at:
Technical Documents: Documentation Home Page: Cisco Product Documentation: Broadband/Cable Solutions: Cisco uBR900 Series Cable Access Routers
On the Documentation CD-ROM at:
Cisco Product Documentation: Broadband/Cable Solutions: Cisco uBR900 Series Cable Access Routers
Feature Modules
Feature modules describe new features supported by Release 12.1, and are updates to the Cisco IOS documentation set. A feature module consists of a brief overview of the feature, benefits, configuration tasks, and a command reference. As updates, the feature modules are available online only. Feature module information is incorporated in the next printing of the Cisco IOS documentation set.
On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: New Feature Documentation
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: New Feature Documentation
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 that are available in electronic form on the Documentation CD-ROM and CCO, as well as separately orderable in printed versions.
Documentation Modules
Each module in the Cisco IOS documentation set consists of two books: a configuration guide and a corresponding command reference. Chapters in a configuration guide describe protocols, configuration tasks, Cisco IOS software functionality, and contain comprehensive configuration examples. Chapters in a command reference provide complete command syntax information. Use each configuration guide with its corresponding command reference.
On CCO and the Documentation CD-ROM, two master hot-linked documents provide information for the Cisco IOS software documentation set.
On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
Release 12.1 Documentation Set
Table 6 describes the contents of the Cisco IOS Release 12.1 software documentation set, which is available in electronic form and in printed form upon request.
Note
On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1
Note
Obtaining Documentation
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
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. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Ordering Documentation
Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.
Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Obtaining Technical Assistance
Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed documents, or by sending mail to Cisco.
Cisco Connection Online
Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access CCO in the following ways:
•
•
•
–
–
You can e-mail questions about using CCO to cco-team@cisco.com.
Technical Assistance Center
The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.
To contact by e-mail, use one of the following:
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
Software Configuration Tips on the Cisco Technical Assistance Center Home Page
If you have a CCO login account, you can access the following URL, which contains links and tips on configuring your Cisco products:
http://www.cisco.com/kobayashi/technotes/serv_tips.shtml
This URL is subject to change without notice. If it changes, point your Web browser to CCO, press Login, and click on this path: Technical Assistance Center: Technical Tips.
The following sections are provided from the Technical Tips page:
•
•
•
•
•
•
•
•
Documentation Feedback
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate and value your comments.
Guest
