Cisco Cable Modem High-Speed WAN Interface Cards Configuration Guide
Available Languages
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.com
Feature 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.html
The 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
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/dtudlr.htm#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.pdf
To 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!interface Vlan1ip address 192.168.129.1 255.255.255.0ip pim sparse-dense-modeip igmp mroute-proxy Loopback0load-interval 30!router ripversion 2network 209.165.201.0network 192.168.129.0no auto-summary!ip route 192.168.101.0 255.255.255.0 10.0.0.200ip route 172.16.6.254 255.255.255.255 192.168.1.1!no ip http serverno ip http secure-serverip pim rp-address 209.165.202.130!endConfiguring Circuit Emulation over IP
Circuit Emulation over IP (CEoIP) provides protocol-independent transport over IP networks. It enables proprietary or legacy applications to be carried transparently to the destination, in a manner similar to that of a leased line.
Note
Note
http://www.cisco.com/en/US/products/ps6350/products_configuration_guide_chapter09186a008045523e.html
Configuring the NM-CEM-4TE1 Card Type
Perform this task to configure the Cisco cable modem HWIC.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring the T1/E1 Line
Perform this task to configure the T1 or E1 line.
This task does not apply to the NM-CEM-4SER.
SUMMARY STEPS
1.
2.
3.
4.
or
framing {crc4 | no-crc4 | unframed}5.
6.
7.
8.
9.
10.
DETAILED STEPS
Creating Circuit Emulation Channels on the T1/E1 Line
Perform this task to create CEM channels on the T1 or E1 line.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring the Connection Using the xconnect Command
Perform this task to configure a connection using the xconnect command.
This task applies to configuring CEoIP on both the NM-CEM-4TE1 and the NM-CEM-4SER.
Note
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Router#
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Router(config)#
Enters global configuration mode.
Step 3
cem slot/port/channel
Example:Router(config)# cem 3/1/0
Router(config-cem)#
Enters CEM configuration mode to configure CEM channels.
•
•
•
Step 4
xconnect remote-ip-address virtual-connect-ID encapsulation encapsulation-type
Example:Router(config-cem)# xconnect 10.2.0.1 0 encapsulation udp
Router(config-cem-xconnect)#
Creates one end of a connection between two CEM network modules and enters xconnect configuration mode.
•
•
Note
Step 5
local ip address ip-address
Example:Router(config-cem-xconnect)# local ip address 10.2.0.2
Router(config-cem-xconnect)#
Configures the IP address of an interface (regular or loopback) on the source router.
Note
Step 6
local udp port port
Example:Router(config-cem-xconnect)# local udp port 15901
Router(config-cem-xconnect)#
Specifies the User Datagram Protocol (UDP) port number of the local CEM channel.
Note
Step 7
remote udp port port
Example:Router(config-cem-xconnect)# remote udp port 15902
Router(config-cem-xconnect)#
Specifies the UDP port number of the remote CEM channel.
Note
Step 8
end
Example:Router(config-cem-xconnect)# end
Router#
Exits xconnect configuration mode and returns to privileged EXEC mode.
Configuring the Circuit Emulation Channel
Perform this task to configure the CEM T1/E1 or serial channel.
This task applies to both the NM-CEM-4TE1 and the NM-CEM-4SER.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Router#
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Router(config)#
Enters global configuration mode.
Step 3
cem slot/port/channel
Example:Router(config)# cem 3/1/0
Router(config-cem)#
Enters CEM configuration mode to configure CEM channels.
•
•
•
Step 4
clock rate rate
Example:Router(config-cem)# clock rate 38400
Router(config-cem)#
(Optional) For serial channels only. Specifies the nominal bit rate of a serial CEM channel.
•
Step 5
clock mode {normal | split}
Example:Router(config-cem)# clock mode split
Router(config-cem)#
(Optional) For serial channels only. Specifies the clock mode of a serial CEM channel.
•
•
Note
Step 6
clock source {internal | loop | adaptive}
Example:Router(config-cem)# clock source loop
Router(config-cem)#
(Optional) Configures the clock source for a serial CEM channel.
•
•
•
•
Note
Step 7
payload-size size
Example:Router(config-cem)# payload-size 512
Router(config-cem)#
(Optional) Specifies the number of bytes encapsulated into a single IP packet.
•
•
Step 8
dejitter-buffer size
Example:Router(config-cem)# dejitter-buffer 80
Router(config-cem)#
(Optional) Specifies the size of the dejitter buffer used to compensate for the network filter.
•
Step 9
control-lead sampling-rate rate
Example:Router(config-cem)# control-lead sampling-rate 10
Router(config-cem)#
(Optional) For serial channels only. Specifies the sampling rate of input control leads on a serial CEM channel.
•
Note
Step 10
control-lead state {active | fail} output-lead {on | off | follow} [{local | remote} input-lead]
Example:Router(config-cem)# control-lead state active rts follow remote cts
Router(config-cem)#
(Optional) For serial channels only. Specifies the state of each output control lead on a serial CEM channel.
•
•
•
•
•
•
•
Note
Note
Step 11
data-strobe input-lead {on | off}
Example:Router(config-cem)# data-strobe dtr on
Router(config-cem)#
(Optional) For serial channels only. Specifies that an input control lead is to be monitored and data is to be packetized and sent only when the specified control lead is in the specified state.
•
•
•
•
Note
Step 12
Cisco NM-CEM-4SER
idle-pattern pattern length pattern1 [pattern2]
Cisco NM-CEM-4TE1
idle-pattern pattern1
Example:Cisco NM-CEM-4SER
Router(config-cem)# idle-pattern 53 0x12345678 0x87654321
Router(config-cem)#
Cisco NM-CEM-4TE1
Router(config-cem)# idle-pattern 0x66
Router(config-cem)#
(Optional) Defines the idle data pattern to send to the attached CPE when packets are lost or the dejitter buffer experiences an underrun condition.
For serial CEM channels:
•
•
•
•
For T1 or E1 CEM channels:
•
Step 13
failure {activation | deactivation} msec
Example:Router(config-cem)# failure activation 1000
Router(config-cem)#
(Optional) Specifies a time period before a CEM connection enters, or recovers from, a failed state.
•
•
•
Step 14
signaling [on-hook-pattern] [off-hook-pattern] [msec]
Example:Router(config-cem)# signaling
Router(config-cem)#
(Optional) For framed T1 or E1 data channels only. Enables the transport of channel-associated signaling (CAS) bits.
Step 15
payload-compression
Example:Router(config-cem)# payload-compression
Router(config-cem)#
(Optional) Enables payload compression on a CEM channel.
Note
Step 16
data-protection
Example:Router(config-cem)# data-protection
Router(config-cem)#
(Optional) Enables data protection by transmitting each data bit twice, once in each of two consecutive data packets.
•
Caution
Step 17
ip dscp [dscp-value]
Example:Router(config-cem)# ip dscp 36
Router(config-cem)#
(Optional) Configures the IP differentiated services code point (DSCP) for packets originating from this CEM channel.
•
Note
Step 18
ip tos tos
Example:Router(config-cem)# ip tos 11
Router(config-cem)#
(Optional) Configures the IP type of service (ToS) bits for the CEM channel.
•
Note
Step 19
ip precedence precedence
Example:Router(config-cem)# ip precedence 7
Router(config-cem)#
(Optional) Configures the IP precedence bits for the CEM channel.
•
Note
Step 20
loopback {local | network}
Example:Router(config-cem)# loopback network
Router(config-cem)#
(Optional) Creates a loopback from a CEM serial channel.
•
•
Note
Step 21
end
Example:Router(config-cem)# end
Router#
Exits CEM configuration mode and returns to privileged EXEC mode.
Step 22
show cem {slot/port/channel | summary}
Example:Router# show cem summary
Router#
Displays CEM statistics.
Examples
Sample Output for the show cem Command Using the Summary Keyword
The following example shows partial output from the show cem command using the summary keyword:
Router# show cem summarycem summaryCSTATE: CEM stateLSTATE: line stateOSTATE: operational statePSIZE: payload-sizePCOMP: payload-compressionDPROT: data-protectionCEM CSTATE LSTATE OSTATE PSIZE PCOMP DPROT----------------------------------------------------------------------2/0/0 shutdown up config-incomplete 256 disabled disabled2/1/0 shutdown up config-incomplete 256 disabled disabled2/2/0 shutdown up config-incomplete 256 disabled disabled2/3/0 shutdown up config-incomplete 256 disabled disabled4/0/1 up up active 96 enabled disabled4/0/2 up up active 96 enabled disabled4/0/3 up up active 96 enabled disabled4/0/4 up up active 96 enabled disabled4/0/5 up up active 96 enabled disabled4/0/6 up up active 96 enabled disabled4/0/7 up up active 96 disabled disabled4/0/8 up up active 96 disabled disabled4/0/9 up up active 96 disabled disabled4/0/10 up up active 96 disabled disabledSample Output of Basic Configuration of a T1 Network Module to Configure the CEoIP
The following example shows a basic configuration of a T1 network module to configure the CEoIP feature:
card type t1 0controller t1 4/0cem-group 6 timeslots 1-4,9,10 speed 64framing esflinecode b8zsclock source adaptive 6cablelength long -15dbcrc-threshold 512description T1 line to 3rd floor PBXloopback networkno shutdownexitcem 2/1/6xconnect 10.2.0.1 0 encapsulation udplocal ip address 10.2.0.9local udp port 15901remote udp port 15902payload-size 512dejitter-buffer 80signalingexitSample Output of Serial CEM Network Module
The following example shows a basic configuration of a CEM serial channel to configure the CEoIP feature. Each end of the CEM connection must be configured before the CEM channel is configured.
cem 2/0/0xconnect 10.3.0.1 0 encapsulation udplocal ip address 10.3.0.9local udp port 15901remote udp port 15902endSerial CEM Network Module 2
cem 2/1/0xconnect 10.3.0.9 0 encapsulation udplocal ip address 10.3.0.1local udp port 15902remote udp port 15901endSerial Channel Configuration
cem 2/0/0clock rate 38400clock mode splitclock source looppayload-size 512dejitter-buffer 80control-lead sampling-rate 10control-lead state active rts follow remote ctsdata-strobe dtr onidle-pattern 53 0x12345678 0x87654321payload-compressiondata-protectionip dscp 36loopback networkendConfiguration for the Multiple Service Operator
This section describes how to configure the Cisco cable modem HWIC:
•
•
Note
How to Download Firmware from the CMTS
This section explains how to download a firmware file from the CMTS to a Cisco cable modem HWIC through the cable modem configuration file for the MSO.
Prerequisites
When using a cable modem configurator tool, you must enable or designate these settings:
•
•
•
Note
•
•
•
•
Note
Preparing the Cable Modem Configuration File
To prepare the cable modem configuration file, follow these steps:
Step 1
Caution
FileVersion = Version 5.003 (Net Access Control) = 109 (Software Upgrade File) = C21031012eFU02172006.CDF11 (MIB Object) = 30 12 06 0a 2b 06 01 02 01 45 01 03 03 00 02 04 00 00 00 0217 (BLP Config Settings)S01 (Author Timeout) = 5S02 (Re-auth Wait Timeout) = 5S03 (Author Wait Timeout) = 60S04 (Oper Wait Timeout) = 2S05 (Re-Key Wait Timeout) = 2S06 (TEK Grace Time) = 60S07 (Auth Rej Wait Timeout) = 5S08 (SA Map Wait Timeout) = 521 (Software Upgrade Addr) = 007.000.000.00132 (Manufacturer CVC) = us_cvc_cert.crt18 (Maximum Number of CPE) = 1024 (Upstream Service Flow Encodings)S01 (Service Flow Reference) = 1S06 (QoS Parameter Set Type) = 7S08 (Max Sustained Traffic Rate) = 20000000S15 (Service Flow Sched Type) = 225 (Downstream Service Flow Encodings)S01 (Service Flow Reference) = 5S06 (QoS Parameter Set Type) = 7S08 (Max Sustained Traffic Rate) = 2000000029 (Privacy Enable) = 0Step 2
Step 3
Step 4
Router(config)# tftp-server firmware-nameRouter(config)# tftp-server bootflash:C21031013cFU04072006.CDFRouter(config)# tftp-server Cable-Modem config-fileRouter(config)# tftp-server bootflash:00dd_2bbo_695a.binStep 5
ats1-cmts-1# clear cable modem 00d0.2bfe.66ce resetStep 6
Router# show controller port-number statusRouter# show controller cable 0/0/1 status
Note
The following example shows the output from this command. The new firmware version is displayed in the Software Hidden version line of text.
Router# show controller cable 0 statusCable Modem Information:Software version 2.103.1012Software Hidden version 2.103.1012eHardware versionCable IP address 7.0.0.23/24DOCSIS mode 3 (2_0)BPI status 1 (DISABLED)Uptime (seconds) 170871Current state 16 (OPERATIONAL)Cable MAC address 00d0.2bfe.66ceInternal MAC address 00d0.2bfe.66cfInternal IP address 192.168.100.1/24Downstream buffers free 128Downstream buffers used 0Upstream buffers free 254Upstream buffers used 0MAC SDRAM free (Kbytes) 20361008MAC SDRAM used (Kbytes) 7563552MAC Flash free (Kbytes) 1823657MAC Flash used (Kbytes) 2337879
Note
1.
CMTS# clock set hh:mm:ss day month yearCMTS# clock set 12:22:36 23 July 2006CMTS# clock update-calendarCMTS# clock update-calendar2.
To download the DOCSIS root certificate to the CMTS, see Downloading the DOCSIS Root Certificate to the CMTS at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/cable/cab_rout/cmtsfg/ufg_docs.htm#wp1217174
Vendor Specific Type-Length-Values 42
Use the Cisco vendor-specific Type-Length-Value (TLVs) 42 in the text file to convert to binary in the configuration file.
TLV 42
Use TLV 42 to enable downstream routing protocols using multicast address such as RIPv2.
To support DOCSIS configuration file-based enabling downstream routing protocols using multicast address such as RIPv2, your DOCSIS configuration file editor must support the inclusion of the Cisco vendor-specific TLV 42.
The following example shows how to use TLV 42 in the configuration file. This information can be found in the vendor information specific field (VISF):
00 (Multicast Mac Address) = 42 %hex 01 00 5e 00 00 09
Note
Additional References
Related Documents
Hardware installation instructions for interface cards
Configuration fundamentals for Cisco IOS software release 12.4
Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.4
DOCSIS 2.0 specifications
Configuration information for configuring NAT
Configuration information for configuring DHCP
Configuration information for configuring Easy VPN
Configuration information for configuring IGMP
Configuration information for configuring CoIP
MIBs
RFCs
Technical Assistance
Commands at a Glance
This section documents new and modified commands only.
New Commands
•
Modified Commands
clear interface cable-modem
To reset the controller for a specified cable modem daughter card, use the clear interface cable-modem command in privileged EXEC mode.
clear interface cable-modem
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command as an alternative to the cable-modem power cycle command.
Examples
The following example clears the interface on the selected slot and port:
*May 17 16:36:57.344: %CABLE_MODEM_HWIC-6-RESET: Interface Cable-Modem0/2/0 has been reset: clear command *May 17 16:37:05.348: %LINK-3-UPDOWN: Interface Cable-Modem0/2/0, changed state to down *May 17 16:37:06.348: %LINEPROTO-5-UPDOWN: Line protocol on Interface Cable-Modem0/2/0, changed state to down *May 17 16:37:19.740: %LINK-3-UPDOWN: Interface Cable-Modem0/2/0, changed state to up *May 17 16:37:27.996: %LINEPROTO-5-UPDOWN: Line protocol on Interface Cable-Modem0/2/0, changed state to upRelated Commands
show interfaces
Displays statistics for all interfaces configured.
show interfaces cable-modem
Displays statistics for all interfaces configured on the port.
debug cable-modem driver
To enable debugging on the WIC and HWIC driver, use the debug cable-modem driver command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable-modem driver [detail | error]
no debug cable-modem driver [detail | error]
Syntax Description
detail
(Optional) Provides additional detailed debugging information.
error
(Optional) Enables driver debugging of the driver error paths.
Defaults
This command is disabled by default.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Significant errors are acknowledged by counters or error messages. Error debugging provides more detailed information.
Debugging can also be enabled or disabled by using the debug condition interface cable-modem port command. If a condition interface is enabled for one port, the debugging capability is disabled for the remaining ports.
Examples
The following example turns CM driver debugging on:
Router# debug cable-modem driverCM driver debugging is onRelated Commands
debug condition interface cable-modem port
Enables debugging messages for additional interfaces.
debug cable-modem rbcp
To activate debugging on the modem router blade control port (RBCP) code, use the debug cable-modem rbcp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable-modem rbcp {events | messages | states}
Syntax Description
Defaults
This command is disabled by default.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
When no keyword is selected, this command enables miscellaneous RBCP debugging.
When the messages keyword is enabled, a debug message is generated for every RBCP request and response.
Cisco IOS software RBCP support also contains its own debug facility with the debug scp data and debug scp packets commands.
Debugging can be also be enabled or disabled by using the debug condition interface cable-modem port command. If a condition is enabled for one port, the debugging capability is disabled for the remaining ports.
Examples
Router# debug cable-modem rbcp messagesCM rbcp messages debugging is onRelated Commands
debug cable-modem startup
To enable modem initialization code debugging, use the debug cable-modem startup command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug cable-modem startup
no debug cable-modem startup
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Debugging can also be enabled or disabled by using the debug condition interface cable-modem port command. If a condition is enabled for one port, the debugging capability is disabled for the remaining ports.
Examples
The following shows CM startup debugging turned on:
Router# debug cable-modem startupCM startup debugging is onRelated Commands
debug condition interface cable-modem port
service-flow primary upstream
To assign a QoS policy to the data traveling between the cable modem to the multiple service operator (MSO) cable modem termination system (CMTS), use the service-flow primary upstream command in interface configuration mode. To disable, use the no form of this command.
service-flow primary upstream
no service-flow primary upstream
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is supported in the upstream direction only so only the output form of the command is available. Service flows are unidirectional.
Examples
The following example assigns a QoS policy to the data traveling between the cable modem to the MSO CMTS:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface Cable-Modem 0/2/0 Router(config-if)# service-flow primary upstreamRouter(config-serviceflow)#service-module ip address
To define the IP address for the internal network module-side interface on a content engine network module (NM-CE-BP) or Cisco IP cable modem interface satellite WAN network module, use the service-module ip address command in content-engine interface configuration mode or satellite interface configuration mode. To delete the IP address associated with this interface, use the no form of this command.
service-module ip address {nm-side-ip-addr subnet-mask}
no service-module ip address
Syntax Description
Defaults
No default behavior or values
Command Modes
Content-engine interface configuration
Satellite interface configurationCommand History
Usage Guidelines
For the NM-1VSAT-GILAT network module, the service-module ip address command is typically not used. The NM-1VSAT-GILAT network module IP address is automatically configured when you enter the ip address command in satellite interface configuration mode to configure the IP address and subnet mask of the router satellite interface with the following conditions:
•
•
If you use this method to configure the IP address for the router satellite interface, the system automatically configures the IP address and subnet mask on the NM-1VSAT-GILAT network module with these results:
•
•
You can override the automatically configured IP address and mask by manually entering the service-module ip address command.
Note
Examples
The following example shows how to define an IP address for the internal network-module-side interface on the content engine network module in slot 1:
Router(config)# interface content-engine 1/0Router(config-if)# service-module ip address 172.18.12.26 255.255.255.0Router(config-if)# exitIn the following example, the router satellite interface is assigned an IP address (10.0.0.7), the last octet of which does not leave a remainder of 2 when divided by 4. The system displays a message to manually configure the IP address for the NM-1VSAT-GILAT network module. Notice that the IP addresses for both the router satellite interface and the NM-1VSAT-GILAT network module appear in the running configuration.
Router(config)# interface satellite 1/0Router(config-if)# ip address 10.0.0.7 255.255.255.0%VSAT-6-PIMINCOMPADDR: The IP address configured on Satellite1/0requires a manually configured IP address for the satellite moduleRouter(config-if)# service-module ip address 10.0.0.6 255.255.255.0Router(config-if)# endRouter# show running-config | begin Satelliteinterface Satellite 1/0ip address 10.0.0.7 255.255.255.0service-module ip address 10.0.0.6 255.255.255.0...In the following example, the router satellite interface IP address is configured as 10.0.0.6. Because the last octet of the IP address leaves a remainder of 2 when divided by 4, the system automatically configures the IP address for the NM-1VSAT-GILAT network module.
Although the NM-1VSAT-GILAT network module IP address and mask do not appear in the router configuration, you know that the IP address is 1 less than the IP address of the router satellite interface and has a subnet mask of /30. In this case, the NM-1VSAT-GILAT network module is automatically configured with the following IP address and mask: 10.0.0.5 255.255.255.252.
!interface Satellite 1/0ip address 10.0.0.6 255.255.255.0!In the following example, the router satellite interface IP address is configured as 10.0.0.6. Because the last octet of the IP address leaves a remainder of 2 when divided by 4, the system automatically configures the IP address and mask for the NM-1VSAT-GILAT network module as 10.0.0.5 255.255.255.252.
Nevertheless, the NM-1VSAT-GILAT network module IP address and mask are manually configured as 10.0.0.1 255.255.255.0 to override the automatically derived IP address and mask. Notice that the IP addresses for both the router satellite interface and the NM-1VSAT-GILAT network module appear in the running configuration.
!interface Satellite 1/0ip address 10.0.0.6 255.255.255.0service-module ip address 10.0.0.1 255.255.255.0!Related Commands
show controllers cable-modem
To display status information for the router, use the show controllers cable-modem port command in privileged EXEC mode.
show controllers cable-modem port [all | classifiers | cm-cert | crypto des | filters | internal-mac | lookup-table | mac {counts crashdump | hardware | log | state} | manuf-cert | phy | service-flows | status | tuner]
Syntax Description
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following example displays information about the cable modem physical interface:
Router# show controllers cable-modem 1 phyPhy Minislots to MAC Bytes table for kLongDataGrantIUCMAC Bytes for (Mslot 10's + offset)Mslot Mslot offset10's 0 1 2 3 4 5 6 7 8 9===== ===== ===== ===== ===== ===== ===== ===== ===== ===== =====0 0 0 0 0 0 0 0 0 213 2311 261 293 325 357 389 421 453 462 501 5332 565 597 629 661 693 709 741 773 805 8373 869 901 924 949 981 1013 1045 1077 1109 11414 1155 1189 1221 1253 1285 1317 1349 1381 1386 14295 1461 1493 1525 1557 1589 1617 1637 1669 1701 17336 1765 1797 1829 1848 1877 1909 1941 1973 2005 <-- max burstRequest Opportunity Burst Size (Mslots) = 2Initial Ranging Opportunity Burst Size (Mslots) =Phy Burst Size (Mslots) to send (1) MAC byte forStd Short grant = 2Std Long grant =The following example displays firmware status information:
Router# show controllers cable-modem 1 statusCable Modem Information:Software version 2.103.1003Software Hidden version 2.01Hardware version 2.103.1003aCable IP address 0.0.0.0/0DOCSIS mode 0 (UNKNOWN)BPI status 1 (DISABLED)Uptime (seconds) 0Current state 2 (NOT_SYNCHRONIZED)Cable MAC address 00d0.59e1.03feInternal MAC address 00d0.59e1.03ffInternal IP address 0.0.0.0/0Downstream buffers free 128Downstream buffers used 0Upstream buffers free 255Upstream buffers used 255MAC SDRAM free (Kbytes) 255MAC SDRAM used (Kbytes) 255MAC Flash free (Kbytes) 255MAC Flash used (Kbytes) 255show interfaces cable-modem
To display statistics for all interfaces configured on the port, use the show interfaces cable-modem in privileged EXEC mode.
show interfaces cable-modem port
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The resulting output varies, depending on the network for which an interface has been configured.
Examples
The following example shows the HFC state on the modem:
c2801-61# show interfaces Cable-Modem 0/1/0cable-modem0/1/0 is up, line protocol is upHFC state is OPERATIONAL, HFC MAC address is 00d0.59e1.2073Hardware is Cable modem, address is 0014.f26d.10b2 (bia 0014.f26d.10b2)Internet address is 12.0.0.61/8MTU 1500 bytes, BW 1544 Kbit, DLY 6470 usec,reliability 255/255, txload 247/255, rxload 246/255Encapsulation ARPA, loopback not setARP type: ARPA, ARP Timeout 04:00:00Last input 00:00:01, output 00:00:00, output hang neverLast clearing of "show interface" counters 00:07:03Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 83594Queueing strategy: Class-based queueingOutput queue: 61/1000/64/83594 (size/max total/threshold/drops)Conversations 2/5/256 (active/max active/max total)Reserved Conversations 0/0 (allocated/max allocated)Available Bandwidth 232 kilobits/sec30 second input rate 2581000 bits/sec, 987 packets/sec30 second output rate 1585000 bits/sec, 639 packets/secHFC input: 0 errors, 0 discards, 0 unknown protocols 0 flow control discardsHFC output: 0 errors, 0 discards304582 packets input, 105339474 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 1 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored0 input packets with dribble condition detected228195 packets output, 78392605 bytes, 0 underruns0 output errors, 0 collisions, 1 interface resets0 babbles, 0 late collision, 0 deferred0 lost carrier, 0 no carrier0 output buffer failures, 0 output buffers swapped outThis following table describes the fields within the HFC state (the DOCSIS state for the cable modem connection to the CMTS.
The following table describes input error descriptions.
The following table describes output error descriptions.
Related Commands
show interfaces
Displays statistics for all interfaces.
show interfaces cable-modem
Displays statistics for all interfaces configured on the port.
show ip access-list
To display the contents of all current IP access lists, use the show ip access-list command in user EXEC or privileged EXEC mode.
show ip access-list [access-list-number | access-list-name | dynamic access-list-name | interface interface-name [in | out]]
Syntax Description
Defaults
All standard and extended IP access lists are displayed.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The show ip access-list command provides output identical to the show access-lists command, except that the first command is IP-specific and allows you to specify a particular access list.
Examples
The following is sample output from the show ip access-list command when all access lists are requested:
Router# show ip access-listExtended IP access list 101deny udp any any eq ntppermit tcp any anypermit udp any any eq tftppermit icmp any anypermit udp any any eq domainThe following is sample output from the show ip access-list command when the name of a specific access list is requested:
Router# show ip access-list InternetfilterExtended IP access list Internetfilterpermit tcp any 10.31.0.0 0.0.255.255 eq telnetdeny tcp any anydeny udp any 10.31.0.0 0.0.255.255 lt 1024deny ip any any logThe following is sample output from the show ip access-list command, which shows input statistics for FastEthernet interface 0/0:
Router#show ip access-list interface FastEthernet 0/0 inExtended IP access list 150 in10 permit ip host 10.1.1.1 any30 permit ip host 20.2.2.2 any (15 matches)The following is sample output from the show ip access-list command using the dynamic keyword:
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#To check your configuration when the dynamic keyword is used, use the show run interfaces cable command:
show run interfaces cable 0/1/0Building configuration...Current configuration : 144 bytes!interface cable-modem0/1/0ip address dhcpload-interval 30no keepaliveservice-flow primary upstreamservice-policy output llqendc2801-61#Related Commands
Feedback