Table Of Contents
Cisco Cable Modem High-Speed
WAN Interface Cards Configuration GuideOpen Source License Acknowledgements
Restrictions for the Cisco Cable Modem HWICs
Information About the Cisco Cable Modem HWICs
Platform Support for Cisco Cable Modem HWICs
Software Features and Benefits
How to Configure the Router to Interact with the Cable Modem
Configuring Network Address Translation
Configuring Dynamic Host Configuration Protocol
Configuring Easy Virtual Private Network
Configuring Multicast with IGMP Proxy
Configuring Circuit Emulation over IP
Configuring the NM-CEM-4TE1 Card Type
Creating Circuit Emulation Channels on the T1/E1 Line
Configuring the Connection Using the xconnect Command
Configuring the Circuit Emulation Channel
Configuration for the Multiple Service Operator
How to Download Firmware from the CMTS
Preparing the Cable Modem Configuration File
Vendor Specific Type-Length-Values 42
Cisco Cable Modem High-Speed
WAN Interface Cards Configuration Guide
This document describes how to configure Cisco Data-Over-Cable Service Interface Specification (DOCSIS) cable modem high-speed WAN interface cards (HWICs) in the following supported Cisco routers: Cisco IAD2431 integrated access devices; Cisco 2691, Cisco 3725, Cisco 3745 series routers; Cisco 815, Cisco 1800, Cisco 2800, and Cisco 3800 integrated services routers (ISRs).
Cisco cable modem HWICs are designed to be fully compliant with DOCSIS 2.0 standards in the United States, Europe, and Japan. Cisco cable modem HWICs provide secure, high-speed connections to hybrid fiber-coaxial (HFC) cable networks.
The Cisco cable modem HWICs allow the router to communicate over high-speed data (HSD) cable networks for office-to-Internet connectivity or for branch-to-branch connectivity. Supported on a wide range of platforms, the Cisco cable modem HWICs are suitable for installations ranging from small office/home office (SOHO) to small and medium business (SMB) to enterprise branch offices. When the Cisco cable modem HWIC is combined with the powerful Cisco IOS software and Cisco's wide range of industry-leading access routers, an unparalleled range of services possible, all within a single, easily manageable platform. This combination allows a provider or business to minimize operational expenses while maximizing the potential return on invested capital.
Note
The Cisco cable modem HWIC is fully DOCSIS 2.0 compliant. To see the DOCSIS 2.0 U.S. requirements and specifications, see the CableLabs website at
http://www.cablemodem.com/specifications/specifications20.html
To see Euro DOCSIS 2.0 requirements, see the ComLabs website at
http://www.tcomlabs.comFeature History for Cisco Cable Modem HWICs (HWIC-CABLE-D-2, HWIC-CABLE-E/J-2)
12.4(11)T (router software)
This feature was introduced.
12.4(6)XE (router software)
This command was integrated into Cisco IOS Release 12.4(6)XE.
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://tools.cisco.com/ITDIT/CFN/jsp/index.jsp. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
•
•
•
•
Open Source License Acknowledgements
The following notices pertain to this software license.
OpenSSL/Open SSL Project
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
License Issues
The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.
OpenSSL License:
Copyright © 1998-2007 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.
2.
3.
4.
5.
6.
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS"' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).
Original SSLeay License:
Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.
This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).
The implementation was written so as to conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).
Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.
2.
3.
"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)".
The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.
4.
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].
Restrictions for the Cisco Cable Modem HWICs
The Cisco IOS software version and feature set software that are installed on the host router must be compatible with the cable modem HWIC. See the "Feature History for Cisco Cable Modem HWICs (HWIC-CABLE-D-2, HWIC-CABLE-E/J-2)" section. To view the Cisco IOS software release and router feature set, enter the show version command in privileged EXEC mode.
Note
http://www.cisco.com/en/US/products/ps6350/products_configuration_guide_book09186a0080430ee6.html
Information About the Cisco Cable Modem HWICs
This section describes the features of and some important concepts about Cisco cable modem HWICs:
•
Accessibility
These HWICs can be configured using the Cisco command-line interface (CLI). The CLI conforms to accessibility code 508 because it is text based and because it relies on a keyboard for navigation. All functions of the router can be configured and monitored through the CLI.
For a complete list of guidelines and Cisco products adherence to accessibility, see Cisco Accessibility Products at the following URL:
http://www.cisco.com/web/about/responsibility/accessibility/products
Hardware Overview
The two types of Cisco cable modem HWICs are as follows:
•
HWIC-CABLE-D-2 is the cable modem HWIC that is designed for North American customers.
•
HWIC-CABLE-E/J-2 is the cable modem HWIC that is designed for European and Japanese customers.
Note
http://www.cisco.com/en/US/products/hw/modules/ps2797/products_module_installation_guide_book09186a0080692a92.html
Platform Support for Cisco Cable Modem HWICs
Cisco cable modem HWICs can be inserted into WIC or HWIC slots. Table 1 lists the Cisco routers that support WICs and HWICs.
Note
Table 1 Cisco Router Support for WICs and HWICs
8151
Note
Yes
No
1800
No
Yes
IAD24311
Yes
No
26911
Yes
No
2800 series
No
Yes
3700 series1
Yes
No
3800 series
No
Yes
1 When the cable modem HWIC is placed in these routers, the HWIC operates only in WAN interface card (WIC) mode, providing total throughput of 8 Mbps on the cable modem HWIC.
Note
Port Numbering Schemes
Table 2 shows the port number schemes used on the Cisco routers. For information about port numbering on interface cards in specific routers, see the Cisco Interface Cards Installation Guide.
Note
Table 2 Port Numbering on the Cisco Routers
1841, 2800, and 3800 ISRs
x/y/z
IAD2431, 2691, 3725, 3745, and 1800 ISR
x/y
815 ISR
x
Note
Note
Software Features and Benefits
Cisco cable modem HWICs are configured automatically by the network (in compliance with DOCSIS provisioning specifications). The configuration file is defined and generated by the cable service provider and delivered over the WAN/DOCSIS network through the radio frequency (RF) interface on the Cisco cable modem HWIC installed in the router. The HWIC provides a path from the router to the service provider network-based DHCP server for host address assignment on the Cisco cable modem HWIC and on the WAN interface of the router.
Note
http://www.cablemodem.com/specifications/specifications20.htmlThe Cisco cable modem HWICs provide the following features and benefits.
Note
•
•
•
How to Configure the Router to Interact with the Cable Modem
This section describes how to configure the host router when interacting with the Cisco cable modem HWIC:
•
•
•
•
•
Cisco cable modem HWICs are configured automatically through a configuration file that is generated by the cable service provider. You can configure the router to function either as a bridge or as a router. The following sections briefly describe both applications.
Note
http://www.cisco.com/en/US/products/ps6350/products_configuration_guide_book09186a0080430ee6.html
Note
http://www.cablemodem.com/specifications/specifications20.html
Configuring Bridging
Cisco cable modem HWICs comply with the Multimedia Cable Network System Partners Ltd. Consortium (MCNS) standard for interoperable cable modems; it supports full transparent bridging as well as DOCSIS-compliant transparent bridging.
To configure bridging between the router and the cable modem, perform the following tasks, beginning in global configuration mode.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
DETAILED STEPS
Configuring Routing
Routing for the Cisco cable modem HWIC is on by default. To bring the Cisco cable modem HWIC online, use the interface Cable-Modem and ip address dhcp commands.
Note
To configure routing between the router and the cable modem, perform the following tasks, beginning in global configuration mode.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring Network Address Translation
Network Address Translation (NAT) operates on a router that is connecting two networks; one of these networks (designated as the inside network) is addressed with either private or obsolete addresses that must be converted into legal addresses before it forwards packets to the other network (designated as the outside network). The translation operates in conjunction with routing, so that NAT can simply be enabled on a customer-side Internet access router when translation is desired.
Note
http://www.cisco.com/en/US/tech/tk648/tk361/tk438/tsd_technology_support_sub-protocol_home.html
Configuring Dynamic Host Configuration Protocol
As explained in RFC 2131, Dynamic Host Configuration Protocol (DHCP) provides configuration parameters to Internet hosts. DHCP consists of two components: a protocol for delivering host-specific configuration parameters from a DHCP server to a host, and a mechanism for allocating network addresses to hosts. DHCP is built on a client/server model, in which designated DHCP server hosts allocate network addresses and deliver configuration parameters to dynamically configured hosts. By default, Cisco routers that are running Cisco IOS software simultaneously run DHCP server and relay agent software.
Note
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a00800ca75c.html
Configuring QoS
Cisco cable modem HWICs have the ability to transmit congestion notification for the primary flow, as defined by the configuration received from the cable modem termination system (CMTS). The primary flow is for traffic that has the lowest priority. With this notification, Cisco IOS software performs QoS to manage congestion for primary flow traffic.
The remaining traffic going to secondary service flows is handed directly to the Cisco cable modem HWIC. During this process, the traffic bypasses the Cisco IOS software QoS classification or queuing mechanisms established by the Cisco cable modem HWIC. The Cisco cable modem HWIC then relays the CMTS policies to Cisco IOS software. Cisco IOS software then parses the classification parameters and defines an ACL that will match any non-primary flow traffic. This ACL is invoked before the Cisco IOS QoS classification step in the Cisco Express Forwarding (CEF) egress feature path.
With this functionality, class maps can be defined by using parameters that subclassify the primary flow traffic.
Note
To configure QoS between the router and the cable modem, perform the following tasks, beginning in global configuration mode.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
DETAILED STEPS
Examples
The following example shows configuration of QoS on the router.
Identify the class to which you want to apply QoS. In this example, the voice class is identified by the alphanumeric characters ef:
Router(config)# ip cefclass-map match-all VOICEmatch ip dscp efclass-map match-any CALL-SETUPmatch ip dscp af31match ip dscp cs3class-map match-any INTERNETWORK-CONTROLmatch ip dscp cs6The following example specifies the priority assigned to the different classes. Voice is assigned the highest priority in this example:
Router(config)# policy-map anynameclass CALL-SETUPbandwidth percent 2class INTERNETWORK-CONTROLbandwidth percent 5class VOICEpriority 234class class-defaultfair-queuerandom-detectinterface Cable-Modem0/2/0ip address dhcpservice-module ip address 209.165.200.225 255.255.255.224Use the interface Cable-Modem command to apply the priority policy to the cable modem interface:
Router(config)# interface Cable-Modem0/2/0service-flow primary upservice-policy output anynameUse the show ip access-lists dynamic command to view the dynamic IP access lists:
Router# show ip access-lists dynamicExtended IP access list CM_SF#110 permit udp any any eq 5060 (650 matches)20 permit tcp any any eq 506030 permit udp any any dscp ef (806184 matches)c2801-61#Configuring Easy Virtual Private Network
VPN provides security by performing a high level of authentication and by encrypting the data between two particular endpoint routers. Establishing a VPN connection between two routers can be complicated; it typically requires tedious coordination between network administrators to configure the VPN parameters of the two routers.
The Cisco Easy VPN remote feature eliminates much of this tedious work by implementing Cisco Unity Client Protocol, which allows most VPN parameters to be defined at a Cisco IOS Easy VPN server.
After the Easy VPN server has been configured, a VPN connection can be created with minimal configuration on an Easy VPN remote router. When the Easy VPN remote router initiates the VPN tunnel connection, the Cisco Easy VPN server pushes the IPsec policies to the Easy VPN remote and creates the VPN tunnel connection.
To learn more about configuring Easy VPN, see Configuration Example: Easy VPN, which is available at the following URL:
http://www.cisco.com/en/US/products/ps5854/prod_configuration_guide09186a00802c3270.html
Configuring Multicast with IGMP Proxy
The Internet Group Management Protocol (IGMP) proxy mechanism permits hosts that are not directly connected to a downstream router to join a multicast group sourced from an upstream network.
Figure 1 shows a typical multicast configuration.
Figure 1 Typical Multicast Configuration
Note
/en/US/docs/ios/12_1t/12_1t5/feature/guide/dtudlr.html#1020541
Prerequisites
The Cisco cable modem HWIC can be configured for multicast with IGMP proxy.
Using a DOCSIS cable modem configurator tool, specify the following fields in the ASCII configuration file:
42 = 01 00 5e 00 00 0942 = 01 00 5e 00 00 0d42 = 01 00 5e 00 01 2742 = 01 00 5e 00 01 28=================================================================CM MIC = b5 22 c0 24 5d 8e 64 97 93 e0 94 35 f8 a6 3e 53CMTS MIC = 72 c0 d2 d8 01 67 d5 57 5b 7c 91 df 00 6d 9e 71=================================================================
Note
http://www.cablemodem.com/downloads/specs/CM-SP-RFI2.0-I10-051209.pdfTo configure multicast with IGMP proxy, perform the following tasks.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
DETAILED STEPS
Examples
The following example shows configuration of the router with multicast and IGMP proxy.
Router# show ip mrouteIP Multicast Routing TableFlags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,L - Local, P - Pruned, R - RP-bit set, F - Register flag,T - SPT-bit set, J - Join SPT, M - MSDP created entry,X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,U - URD, I - Received Source Specific Host Report,Z - Multicast Tunnel, z - MDT-data group sender,Y - Joined MDT-data group, y - Sending to MDT-data groupOutgoing interface flags: H - Hardware switched, A - Assert winnerTimers: Uptime/ExpiresInterface state: Interface, Next-Hop or VCD, State/Mode(*, 224.1.1.1), 02:14:42/stopped, RP 209.165.202.130, flags: SJCIncoming interface: Cable-Modem0, RPF nbr 209.165.201.1Outgoing interface list:Vlan1, Forward/Sparse-Dense, 02:14:42/00:02:51(209.165.200.226, 224.1.1.1), 02:14:21/00:02:50, flags: JTIncoming interface: Cable-Modem0, RPF nbr 209.165.201.1Outgoing interface list:Vlan1, Forward/Sparse-Dense, 02:14:21/00:02:51(*, 224.0.1.40), 21:03:48/00:02:40, RP 209.165.202.130, flags: SJCLIncoming interface: Cable-Modem0, RPF nbr 209.165.201.1Outgoing interface list:Loopback0, Forward/Sparse-Dense, 21:03:48/00:02:40Router# show interfaces c0Cable-Modem0 is up, line protocol is upHFC state is OPERATIONAL, HFC MAC address is 00d0.2bfe.66eaHardware is Cable modem, address is 0014.a875.8dec (bia 0014.a875.8dec)Internet address is 209.165.201.130MTU 1500 bytes, BW 2000 Kbit, DLY 5000 usec,reliability 255/255, txload 1/255, rxload 21/255Encapsulation ARPA, loopback not setARP type: ARPA, ARP Timeout 04:00:00Last input 00:00:00, output 00:00:01, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: Class-based queueingOutput queue: 0/1000/64/0 (size/max total/threshold/drops)Conversations 0/1/256 (active/max active/max total)Reserved Conversations 1/1 (allocated/max allocated)Available Bandwidth 520 kilobits/sec30 second input rate 2961000 bits/sec, 243 packets/sec30 second output rate 0 bits/sec, 0 packets/secHFC input: 0 errors, 0 discards, 0 unknown protocols 0 flow control discardsHFC output: 0 errors, 0 discards11299559 packets input, 4245935967 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles9 input errors, 0 CRC, 0 frame, 9 overrun, 0 ignored0 input packets with dribble condition detected59044 packets output, 6089309 bytes, 0 underruns0 output errors, 0 collisions, 32 interface resets0 babbles, 0 late collision, 0 deferred0 lost carrier, 0 no carrier0 output buffer failures, 0 output buffers swapped outRouter# show ip igmp membershipFlags: A - aggregate, T - trackedL - Local, S - static, V - virtual, R - Reported through v3I - v3lite, U - Urd, M - SSM (S,G) channel1,2,3 - The version of IGMP the group is inChannel/Group-Flags:/ - Filtering entry (Exclude mode (S,G), Include mode (*,G))Reporter:<mac-or-ip-address> - last reporter if group is not explicitly tracked<n>/<m> - <n> reporter in include mode, <m> reporter in excludeChannel/Group Reporter Uptime Exp. Flags Interface*,224.1.1.1 172.16.0.33 02:14:51 02:09 2A Lo0*,224.0.1.40 172.16.0.33 21:04:16 02:12 2LA Lo0Router# show ip pim neighborPIM Neighbor TableMode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,S - State Refresh CapableNeighbor Interface Uptime/Expires Ver DRAddress Prio/Mode10.0.0.1 Cable-Modem0 19:49:29/00:01:29 v2 16384/ DR SRouter# show running-configBuilding configuration...Current configuration : 4362 bytes!! Last configuration change at 23:48:55 PST Mon Feb 27 2006! NVRAM config last updated at 23:48:56 PST Mon Feb 27 2006!version 12.4service timestamps debug datetime localtimeservice timestamps log datetime localtimeno service password-encryptionservice internal!hostname Router!boot-start-markerboot-end-marker!logging buffered 500000 debuggingno logging consoleenable password lab!no aaa new-model!resource policy!no ip dhcp use vrf connected!no ip domain lookupip multicast-routing!interface Loopback0ip address 172.16.0.33 255.255.255.255ip pim sparse-dense-modeip igmp helper-address 209.165.201.1ip igmp proxy-service!interface FastEthernet0ip address 172.16.5.203 255.255.255.0load-interval 30duplex autospeed auto!interface FastEthernet1load-interval 30duplex fullspeed 100!interface FastEthernet2load-interval 30!interface FastEthernet4load-interval 30!interface Cable-Modem0ip address dhcpip pim sparse-dense-modeload-interval 30no keepalive!
Guest
