Table Of Contents
Prerequisites for IPv6 on Cable
Restrictions for IPv6 on Cable
DHCPv6 Restrictions for IPv6 on Cable
IPv6 Access Services Restrictions for IPv6 on Cable
IPv6 Data Link Layer Restrictions for IPv6 on Cable
Multicast Restrictions for IPv6 on Cable
Provisioning Restrictions for IPv6 on Cable
QoS Restrictions for IPv6 on Cable
Routing Restrictions for IPv6 on Cable
Services and Management Restrictions for IPv6 on Cable
Switching Restrictions for IPv6 on Cable
Tunneling Restrictions for IPv6 on Cable
Information About IPv6 on Cable
Overview of the DOCSIS 3.0 Network Model Supporting IPv6
Overview of Cable Modem IPv6 Address Provisioning
How to Configure IPv6 on Cable
Configuring IPv6 Switching Services
Implementing IPv6 Addressing and Basic Connectivity for Cable Interfaces and Bundles
Configuring the Cable Virtual Bundle Interface
Configuring the IP Provisioning Mode and Bundle on the Cable Interface
Configuring IPv6 Cable Filter Groups
Cable Filter Groups and the DOCSIS Subscriber Management MIB
Configuring IPv6 Domain Name Service
Configuring IPv6 Source Verification
Configuration Examples for IPv6 on Cable
Basic IPv6 Cable Filter Groups: Example
Multiple Cable Filter Groups: Example
Complete Cable Configuration with IPv6: Example
Feature Information for IPv6 on Cable
IPv6 on Cable
First Published: February 14, 2008, Cisco IOS Release 12.2(33)SCA
Support for the IPv6 on Cable feature is introduced in Cisco IOS Release 12.2(33)SCA for the Cisco uBR7225VXR, Cisco uBR7246VXR, and Cisco uBR10012 universal broadband routers to extend IP addressing functionality on these Cisco Cable Modem Termination System (CMTS) routers to include support for both IPv4 and IPv6 protocol stacks.
The IPv6 feature support available in the Cisco IOS software and for the Cisco CMTS routers is extensive. This document provides a comprehensive overview of all of the IPv6 features supported on the Cisco CMTS routers, and their restrictions.
However, the details of every feature are not covered in this document. The areas of IPv6 protocol support for the Cisco CMTS routers discussed in this document are classified by platform-independence or by platform-specific feature support.
•
Platform-independent IPv6 features—Describes IPv6 features that are supported in the Cisco IOS software for several other Cisco platforms, and which generally do not have any platform-specific behavior or configuration differences on the Cisco CMTS routers.
–
Documentation about the restrictions for these platform-independent features can be found in the "Restrictions for IPv6 on Cable" section.
–
Detailed information about these features, including conceptual and task-based configuration information, is documented outside of this feature and in the Cisco IOS software documentation. Detailed information about the location of this related documentation in the Cisco IOS software documentation is described in the "Feature Information for IPv6 on Cable" section.
•
Platform-specific IPv6 features—Describes IPv6 features that are specific to the cable technology area and that only apply to the supported Cisco CMTS routers. The cable-specific IPv6 feature support includes new or modified cable features supporting IPv6, and any transparent support of the IPv6 protocol in existing (legacy) cable features on the CMTS router platforms.
–
Restrictions for new or existing cable-specific features in support of IPv6 can be found within the documentation of all IPv6 cable restrictions in the "Restrictions for IPv6 on Cable" section.
–
Identification of the support of the IPv6 protocol stack in existing cable features is identified in Table 3 in the "Feature Information for IPv6 on Cable" section. The configuration of these legacy cable features is essentially unchanged and is not covered in this document.
–
Complete configuration information for new or modified configuration of cable-specific IPv6 features is provided in this document. This information can be found in the the "How to Configure IPv6 on Cable" section.
Finding Feature Information in This Module
Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and other related documentation, and to see a list of the releases in which each feature is supported, use the "Feature Information for IPv6 on Cable" section.
Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for IPv6 on Cable
•
Restrictions for IPv6 on Cable
•
Information About IPv6 on Cable
•
How to Configure IPv6 on Cable
•
Configuration Examples for IPv6 on Cable
•
Feature Information for IPv6 on Cable
Prerequisites for IPv6 on Cable
Table 1 shows the hardware compatibility prerequisites for the IPv6 on Cable feature.
Restrictions for IPv6 on Cable
The following areas are not supported by IPv6 on the Cisco CMTS routers:
•
Access Control List (ACL) extensions for mobile IPv6
•
Blocking upstream Router Advertisement (RA) messages from cable network
•
Cable Intercept (PacketCable)
•
Cable monitoring based on IPv6 ACL
•
Configuration file generation for Dynamic Message Integrity Check (DMIC) for IPv6 cable modems (CMs)
•
DOCSIS Set-top Gateway (DSG) for IPv6
•
Hot Standby Router Protocol (HSRP) for IPv6
•
Internet Control Message Protocol for IPv6 (ICMPv6) filtering and policing
•
IPv6 anycast addressing
•
IPv6 default router preference (DRP)
•
IPv6 high availability (HA)
•
IPv6 virtual private networks (VPNs)
•
Load balancing used with Hot Standby Connection to Connection Protocol (HCCP)
•
Mobile IPv6 home agent
•
Multiprotocol Label System-Virtual Private Network (MPLS-VPN)
•
Netflow for IPv6
•
Network Address Translation-Protocol Translation (NAT-PT)
•
PacketCable and PacketCable Multimedia
•
Quality of Service (QoS) for IPv6
•
Scalable differential IP address assignment (DOCSIS 3.0 assignment of different prefixes to cable modem [CM] and customer premises equipment [CPE] based on DHCPv6 MAC address)
•
Service Independent Intercept (SII)
•
Static IPv6 addressing for CPE devices
•
Subinterfaces with IPv6
See also the following other areas of restrictions for IPv6 on cable:
•
DHCPv6 Restrictions for IPv6 on Cable
•
IPv6 Access Services Restrictions for IPv6 on Cable
•
IPv6 Data Link Layer Restrictions for IPv6 on Cable
•
Multicast Restrictions for IPv6 on Cable
•
Provisioning Restrictions for IPv6 on Cable
•
QoS Restrictions for IPv6 on Cable
•
Routing Restrictions for IPv6 on Cable
•
Services and Management Restrictions for IPv6 on Cable
•
Switching Restrictions for IPv6 on Cable
•
Tunneling Restrictions for IPv6 on Cable
DHCPv6 Restrictions for IPv6 on Cable
The following Dynamic Host Configuration Protocol for IPv6 (DHCPv6) areas are not supported by the Cisco CMTS routers:
•
DHCP lease queries
•
The following DHCPv6 relay agent options are not supported by the Cisco CMTS routers:
–
Syslog server address option
–
CableLabs client configuration
–
DHCPv6 relay agent subscriber-ID option
–
DHCPv6 relay agent RADIUS attribute option
–
RAAN option
IPv6 Access Services Restrictions for IPv6 on Cable
The following areas of IPv6 access services are not supported by the CMTS routers:
•
Authorization, authentication, and accounting (AAA) support for Cisco IPv6 vendor-specific attributes (VSAs)
•
AAA support for RFC 3162 IPv6 Remote Access Dial-In User Service (RADIUS) attributes
•
DHCPv6 prefix delegation via AAA
•
Point-to-Point Protocol (PPP) over ATM (PPPoA)
•
PPP over Ethernet (PPPoE)
•
Prefix pools
•
Remote bridged encapsulation
IPv6 Data Link Layer Restrictions for IPv6 on Cable
The following areas of the IPv6 Data Link Layer are not supported by the Cisco CMTS routers:
•
Asynchronous Transfer Mode (ATM) permanent virtual circuit (PVC) and ATM LAN emulation (LANE)
•
Fiber Distributed Data Interface (FDDI)
•
Frame Relay PVC13
•
Cisco High-Level Data Link Control (HDLC)
•
PPP service over Packet over SONET (POS)
•
Integrated Services Digital Network (ISDN)
•
Serial (synchronous and asynchronous)
•
Virtual LANs (VLANs) using Cisco Inter-Switch Link (ISL)
•
Dynamic Packet Transport (DPT)
Multicast Restrictions for IPv6 on Cable
IPv6 multicast has the following behavior restrictions on the Cisco CMTS routers:
•
IPv6 multicast packets on the Cisco uBR10012 universal broadband router are process-switched by the Performance Routing Engines (PREs).
•
IPv6 multicast support is not compliant with DOCSIS 3.0; it complies with DOCSIS 2.0.
•
ICMP redirects are not sent to the originating host if the packet is destined for another CPE behind the same CM. All CPE-to-CPE traffic is processed by the Cisco CMTS router.
The following areas of IPv6 multicast are not supported by the Cisco CMTS routers:
•
Address family support for Multiprotocol Border Gateway Protocol (MBGP)
•
Bidirectional Protocol Independent Multicast (PIM)
•
Bootstrap router (BSR)
•
DOCSIS 3.0 encrypted multicast
•
Explicit tracking of receivers
•
IPv6 multicast echo
•
Multicast Forwarding Information Base (MFIB) display enhancements
•
Multicast use authentication and profile support
•
PIM embedded rendezvous point
•
Protocol Independent Multicast sparse mode (PIM-SM) accept register feature
•
Reverse path forwarding (RPF) flooding of bootstrap router (BSR) packets
•
Routable address hello option
•
Source Specific Multicast (SSM) mapping for Multicast Listener Device (MLD) version 1 SSM
Provisioning Restrictions for IPv6 on Cable
The following areas of IPv6 provisioning are not supported by the Cisco CMTS routers:
•
Alternate provisioning mode and pre-registration downstream service ID (DSID) notification
•
Bonded-Downstream Channel Descriptor (B-DCD) messages
•
Dual-stack CPE
•
Multiple DHCPv6 IPv6 addresses per CM or CPE
•
Static IP address assignment
•
Stateless address auto-configuration (SLAAC) address assignment
Note
Due to restrictions with DSID and B-DCD messaging support in Cisco IOS Release 12.2(33)SCA, DOCSIS 3.0 CMs must operate with DOCSIS 2.0-level functionality.
QoS Restrictions for IPv6 on Cable
The following areas of DOCSIS QoS are not supported by the Cisco CMTS routers:
•
Upstream IPv6 Type of Service (ToS) overwrite
•
Downstream IPv6 classification
Routing Restrictions for IPv6 on Cable
The following areas of IPv6 routing are not supported by the Cisco CMTS routers:
•
Authenticate route injection via Routing Information Protocol (RIP) for IPv6 (RIPng)
•
Differential address/prefix assignment for cable modem (CM) and customer premises equipment (CPE) behind CM
•
Enhanced Interior Gateway Routing Protocol (EIGRP)
•
Open Shortest Path First (OSPF) cannot operate with IPv6 multicast routing. To use OSPF, you must disable the ipv6 multicast-routing command on the Cisco CMTS routers.
Services and Management Restrictions for IPv6 on Cable
The following areas of IPv6 services and management are not supported by the Cisco CMTS routers:
•
IPv6 general prefixes
•
IPv6 IOS firewall, including IOS firewall FTP application support
Switching Restrictions for IPv6 on Cable
The following areas of IPv6 switching services are not supported by the Cisco CMTS routers:
•
Automatic 6to4 tunnels
•
Provider edge router over Multiprotocol Label Switching (MPLS) (6PE)
•
CEFv6 switched Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) tunnels
•
CEFv6 switched automatic IPv4-compatible tunnels
•
Parallel Express Forwarding (PXF) switching on the Cisco uBR10012 router
Tunneling Restrictions for IPv6 on Cable
The following areas of IPv6 tunneling services are not supported by the Cisco CMTS routers:
•
Automatic 6to4 tunnels
•
Automatic IPv4-compatible tunnels
•
IPv6 over Universal Transport Interface (UTI) using a Tunnel Line Card
•
ISATAP tunnel support
•
IPv6 over IPv6 tunnels
•
IP over IPv6 Generic Routing Encapsulation (GRE) tunnels
•
IPv6 GRE tunnels in Connectionless Network Service (CLNS) networks
Information About IPv6 on Cable
This section includes the following topics:
•
Overview of the DOCSIS 3.0 Network Model Supporting IPv6
•
Overview of Cable Modem IPv6 Address Provisioning
Overview of the DOCSIS 3.0 Network Model Supporting IPv6
Figure 1 illustrates the network model described by the DOCSIS 3.0 MAC and Upper Layer Protocols Interface Specification.
Figure 1 DOCSIS 3.0 Network Model
In this model, the different devices support the following functions and services:
•
Customer premises equipment (CPE)—Supports IPv4, IPv6, or dual-stack operation.
Note
In Cisco IOS Release 12.2(33)SCA, the Cisco CMTS routers do not support CPE devices provisioned for dual-stack operation.
•
Cable modem (CM)—Functions as a bridging or eRouter device and supports IPv4, IPv6, or dual-stack operation.
•
Cable modem termination system (CMTS) router—Works with the CM over the hybrid fiber coaxial cable (HFC) network to provide IPv4 and/or IPv6 network connectivity to the provisioning servers and the core data network behind the CMTS router.
The CMTS router supports IPv6 address assignment, routing, and forwarding of IPv6 multicast and unicast packets.
Note
In Cisco IOS Release 12.2(33)SCA, the Cisco CMTS routers only support a single DHCPv6 IPv6 address per client CM or CPE.
•
Simple Network Management Protocol (SNMP) agent—Provides management tools to configure and query devices on the network.
•
Syslog server—Collects messages from the CM to support its functions.
•
Dynamic Host Control Protocol (DHCP) server—The DOCSIS 3.0 network model supports both DHCPv4 and DHCPv6 servers to control the assignment of IP addresses.
•
Time server—Provides the current time to the CM.
•
Trivial File Transport Protocol (TFTP) server—Provides the CM configuration file.
Overview of Cable Modem IPv6 Address Provisioning
Prior to CM registration with a CMTS router, the CMTS router sends a MAC Domain Descriptor (MDD) message to provide information to the CM about its supported IP provisioning mode. You configure the CMTS router provisioning mode using the cable ip-init interface configuration command. For more information, see the "Implementing IPv6 Addressing and Basic Connectivity for Cable Interfaces and Bundles" section.
Table 2 provides a summary of the types of IP address provisioning and their support by the Cisco CMTS routers for both CM and CPE devices.
Table 2 CM and CPE IPv6 Provisioning Supported by the Cisco CMTS Routers
The MDD contains an IP initialization parameters type length value (TLV) that defines the IP version, management and alternate provisioning mode, and pre-registration downstream service ID (DSID) that is used by CMs that are capable of downstream traffic filtering.
Note
In Cisco IOS Release 12.2(33)SCA, the Cisco CMTS routers do not support alternate provisioning mode or pre-registration DSID.
To support the MULPIv3.0 I04 or later version of the DOCSIS 3.0 MAC and Upper Layer Protocols Interface Specification, the CM must attempt IPv6 address acquisition first.
Figure 2 illustrates the message flow between a CM, the CMTS router, and the DHCP server when the CM is requesting an IPv6 address.
Figure 2 Message Flow for CM Provisioning of DHCP IPv6 Address Assignment
1.
Link-local address assignment—The CM sends a Neighbor Solicit (NS) message with its link-local address (LLA) to the CMTS router, which starts the duplicate address detection (DAD) process for that LLA. The CM expects no response to the NS message.
2.
Router discovery—The CM sends a Router Solicit (RS) message to find the router on the link (all nodes multicast). The CMTS router responds with a Router Advertise (RA) message with the M and O bits set to 1 to instruct the CM to perform stateful address configuration.
Note
In Cisco IOS Release 12.2(33)SCA, the Cisco CMTS routers do not support SLAAC address assignment.
3.
DHCPv6—The CM sends a DHCPv6 Solicit message to the CMTS router to request an IPv6 address. The CMTS router relays this message to the DHCPv6 servers. The DHCPv6 servers send an Advertise message indicating the server's availability.
If the Rapid-Commit option is not used by the CM, then the CM responds to a server's Advertise message with a Request message to select that server, which the CMTS router relays to the DHCPv6 server. The DHCPv6 server returns an IPv6 address, other configuration information, and a network prefix if the modem is configured as an eRouter.
The CM starts the DAD process to verify uniqueness of the IPv6 address that it was assigned.
4.
Time of Day (ToD) and TFTP—Once the CM establishes IP connectivity, it requests the current time from the ToD server and sends a request to the TFTP server to download a configuration file to complete its boot process.
How to Configure IPv6 on Cable
This section includes the following tasks:
•
Configuring IPv6 Switching Services (Required)
•
Implementing IPv6 Addressing and Basic Connectivity for Cable Interfaces and Bundles (Required)
•
Configuring IPv6 Cable Filter Groups (Optional)
•
Configuring IPv6 Domain Name Service (Optional)
•
Configuring IPv6 Source Verification (Optional)
Configuring IPv6 Switching Services
The CMTS routers support forwarding of unicast and multicast IPv6 traffic using either Cisco Express Forwarding for IPv6 (CEFv6) or distributed CEFv6 (dCEFv6):
•
CEFv6—All CMTS platforms
•
dCEFv6—Cisco uBR10012 router only
The CMTS routers also support Unicast Reverse Path Forwarding (RPF), as long as you enable Cisco Express Forwarding switching or distributed Cisco Express Forwarding switching globally on the router. There is no need to configure the input interface for Cisco Express Forwarding switching. As long as Cisco Express Forwarding is running on the router, individual interfaces can be configured with other switching modes.
To configure forwarding of IPv6 traffic using Cisco Express Forwarding or distributed Cisco Express Forwarding (supported on the Cisco uBR10012 router only) on the CMTS routers, you must configure forwarding of IPv6 unicast datagrams using the ipv6 unicast-routing global configuration command, and you must configure an IPv6 address on the bundle interface using the ipv6 address command.
Prerequisites
•
You must enable Cisco Express Forwarding for IPv4 globally on the router by using the ip cef or ip cef distributed command before configuring CEFv6 or dCEFv6.
Note
The ip cef command is enabled by default on all Cisco CMTS routers. Therefore, you only must configure the command if it has been disabled. However, you must explicitly configure the ip cef distributed command on a Cisco uBR10012 router if you want to run distributed CEF switching services for IPv4 or IPv6.
•
You must configure forwarding of IPv6 unicast datagrams using the ipv6 unicast-routing global configuration command.
•
You must configure IPv6 addressing on the cable bundle interface. Anycast addressing is not supported in Cisco IOS Release 12.2(33)SCA. For more information about configuring IPv6 features on a virtual cable bundle interface, see the "Configuring the Cable Virtual Bundle Interface" section.
•
CEF switching is required for Unicast RPF to work.
Restrictions
In Cisco IOS Release 12.2(33)SCA, Parallel Express Forwarding (PXF) switching is not supported on the Cisco uBR10012 router.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ip cef or ip cef distributed
4.
ipv6 cef or ipv6 cef distributed
5.
ipv6 unicast-routing
DETAILED STEPS
What To Do Next
•
(Optional) Enable IPv6 multicast routing using the ipv6 multicast-routing global configuration command and configure other multicast features. For more information about IPv6 multicast features that are supported on the Cisco CMTS routers, see the corresponding information in Table 3.
Note
In Cisco IOS Release 12.2(33)SCA, the Cisco CMTS routers do not support OSPF with IPv6 multicast routing.
•
Proceed to the "Implementing IPv6 Addressing and Basic Connectivity for Cable Interfaces and Bundles" section.
Implementing IPv6 Addressing and Basic Connectivity for Cable Interfaces and Bundles
•
Configuring the Cable Virtual Bundle Interface (Required)
•
Configuring the IP Provisioning Mode and Bundle on the Cable Interface (Required)
Configuring the Cable Virtual Bundle Interface
The only required IPv6 configuration on a cable line card interface is the IP provisioning mode. The remainder of the IPv6 features are configured at the virtual bundle interface, which is then associated with a particular cable line card interface to establish its configuration.
Most of the IPv6 features that are supported in interface configuration mode (both cable-specific as well as platform-independent IPv6 features) are configured at a cable bundle interface.
The Cisco CMTS routers support IPv6 routing on the bundle interface and map both IPv6 unicast and multicast addesses into the cable bundle forwarding table for packet forwarding.
Each bundle interface has a unique link-local address (LLA) to support link-local traffic when IPv6 is enabled. The Cisco CMTS routers can support a maximum of 40 active bundle interfaces, which also translates to a maximum of 40 active IPv6-enabled bundle interfaces.
Note
This section does not include the configuration of all possible IPv6 features. For information about legacy cable features, refer to the other feature documentation in the Cisco IOS CMTS Cable Software Configuration Guide.
Restrictions
All multicast traffic is flooded onto bundle member interfaces.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface bundle n
4.
ipv6 address ipv6-prefix/prefix-length [eui-64]
or
ipv6 address ipv6-address/prefix-length link-local
5.
ipv6 enable
6.
cable ipv6 source-verify
DETAILED STEPS
What To Do Next
•
See the "Feature Information for IPv6 on Cable" section to configure the desired platform-independent IPv6 features on the bundle interface, such as Neighbor Discovery and DHCPv6 features.
•
Proceed to the "Configuring the IP Provisioning Mode and Bundle on the Cable Interface" section.
Configuring the IP Provisioning Mode and Bundle on the Cable Interface
In Cisco IOS Release 12.2(33)SCA, the CMTS routers allow you to configure cable interfaces to support CMs provisioned for both IPv4 and IPv6 addressing support (known as "dual stack"), only IPv4 addressing, or only IPv6 addressing. Prior to CM registration, the CMTS router sends its supported provisioning mode to the CM in the MDD message.
In addition to configuring the provisioning mode on the cable interface, you must also associate the cable interface with a cable bundle. You perform most of the other IPv6 feature configuration at the bundle interface.
Note
This section only describes the commands asssociated with establishing IPv6 support on a CMTS router. Other typical cable interface commands optionally apply but are not shown, such as to configure upstream and downstream features.
Prerequisites
Configuration of a bundle interface is required.
Restrictions
Alternative Provisioning mode is not supported in Cisco IOS Release 12.2(33)SCA.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface cable {slot/subslot | slot/subslot/port}
4.
cable ip-init {dual-stack | ipv4 | ipv6}
5.
cable bundle n
DETAILED STEPS
What To Do Next
•
Proceed to configuring any other cable interface features that you want to support, such as upstream and downstream features. For more information about the other cable interface features, refer to the Cisco IOS CMTS Cable Software Configuration Guide.
•
Proceed to configure other optional IPv6 cable features. See the optional tasks in the "How to Configure IPv6 on Cable" section.
Configuring IPv6 Cable Filter Groups
Cisco IOS Release 12.2(33)SCA extends the CMTS router IPv4 cable filter group capability to add support for IPv6 filter options.
Cable Filter Groups and the DOCSIS Subscriber Management MIB
Cable subscriber management is a DOCSIS 1.1 specification, the functionality of which can be established using the following configuration methods:
•
CMTS router configuration (via command-line interface [CLI])
•
SNMP configuration
•
DOCSIS 1.1 configuration file (TLVs 35, 36, and 37)
This section describes the IPv6 cable filter group feature support of the packet filtering portion of the DOCSIS Subscriber Management MIB (DOCS-SUBMGMT-MIB) using configuration commands on the CMTS routers. This IPv6 cable filter group support extends filter classifiers with IPv6 addressing options for CM and CPE traffic, but is independent of DOCSIS IPv6 classifiers, which are used to match packets to service flows.
Configuration of IPv6 cable filter groups on the CMTS routers is supported according to the following guidelines:
•
A cable filter group consists of a set of cable filter group commands that share the same group ID.
•
Separate indexes can be used to define different sets of filters for the same group ID. This can be used to define both IPv4 and IPv6 filters to the same filter group.
•
CMs can be associated with one upstream and one downstream filter group.
–
Upstream traffic—All traffic coming from CMs is evaluated against the assigned upstream filter group that is configured by the cable submgmt default filter-group cm upstream command.
–
Downstream traffic—All traffic going to CMs is evaluated against the assigned downstream filter group that is configured by the cable submgmt default filter-group cm downstream command.
•
CPEs can be associated with one upstream and one downstream filter group.
–
Upstream traffic—All traffic coming from CPEs is evaluated against the assigned upstream filter group that is configured by the cable submgmt default filter-group cpe upstream command.
–
Downstream traffic—All traffic going to CPEs is evaluated against the assigned downstream filter group that is configured by the cable submgmt default filter-group cpe downstream command.
•
There are certain CMTS configuration requirements if the DOCSIS 1.1 CM configuration file is not used to activate cable subscriber management for the CPE. Specifically, if the docsSubMgtCpeActive object is not provisioned using TLVs 35, 36, and 37 in the DOCSIS 1.1 CM configuration file, then the object uses the docsSubMgtCpeActiveDefault object setting, which is false. This means that cable subscriber management functionality is disabled. In this case, you must activate the functionality by specifying the cable submgmt default active global configuration command on the CMTS router.
Note
Because TLVs 35, 36, and 37 do not apply to DOCSIS 1.0 CM configuration files, the only way to enable cable subscriber management for a DOCSIS 1.0 CM is to configure it explicitly on the CMTS router and activate it by using the cable submgmt default active global configuration command.
Prerequisites
You must create the cable filter group before you assign it to a CM or CPE upstream or downstream.
Restrictions
•
Chained IPv6 headers are not supported.
•
An individual filter group index cannot be configured to support both IPv4 and IPv6 versions at the same time. If you need to support IPv4 and IPv6 filters for the same filter group, then you must use a separate index number with the same filter group ID, and configure one index as ip-version ipv4, and the other index as ip-version ipv6.
•
Only a single upstream and a single downstream filter group can be assigned for CM traffic.
•
Only a single upstream and a single downstream filter group can be assigned to CPEs attached to a CM such that all CPEs behind a CM share a common filter group.
•
For the filter group to work for CMs, a CM must re-register after the CMTS router is configured for the filter group.
•
If you do not provision TLVs 35, 36, and 37 in the DOCSIS CM configuration file, then you must activate the functionality by specifying the cable submgmt default active global configuration command on the CMTS router.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
cable filter group group-id index index-num dest-port port-num
4.
cable filter group group-id index index-num ip-proto proto-type
5.
cable filter group group-id index index-num ip-tos tos-mask tos-value
6.
cable filter group group-id index index-num ip-version ipv6
7.
cable filter group group-id index index-num match-action {accept | drop}
8.
cable filter group group-id index index-num src-port port-num
9.
cable filter group group-id index index-num status {active | inactive}
10.
cable filter group group-id index index-num tcp-flags flags-mask flags-value
11.
cable filter group group-id index index-num v6-dest-address ipv6-address
12.
cable filter group group-id index index-num v6-dest-pfxlen prefix-length
13.
cable filter group group-id index index-num v6-src-address ipv6-address
14.
cable filter group group-id index index-num v6-src-pfxlen prefix-length
15.
cable submgmt default filter-group {cm | cpe} {downstream | upstream} group-id
16.
cable submgmt default active
DETAILED STEPS
Examples
The following example creates an IPv6 filter group with ID 254 and an index number of 128. The ip-version ipv6 keywords must be configured to create the IPv6 filter group; otherwise, the default is an IPv4 filter group:
configure terminalcable filter group 254 index 128 v6-src-address 2001:0DB8:0:ABCD::1cable filter group 254 index 128 v6-src-pfxlen 48cable filter group 254 index 128 v6-dest-address 2001:0DB8:0:1:FFFF:1234::5cable filter group 254 index 128 v6-dest-pfxlen 64cable filter group 254 index 128 ip-version ipv6cable filter group 254 index 128 match-action dropcable submgmt default filter-group cm upstream 254This group filters CM upstream traffic and drops any packets with an IPv6 source address of 2001:33::20B:BFFF:FEA9:741F (with network prefix of 128) destined for an IPv6 address of 2001:1::224 (with network prefix of 128).
All of the cable filter group commands are associated by their group ID of 254 (and index of 128), and the cable submgmt default filter-group command applies the corresponding filter group ID of 254 to CM upstream traffic.
To monitor your cable filter group configuration, use forms of the show cable filter command as shown in the following examples. In these output examples, the output from the show cable filter, show cable filter group 254, and show cable filter group 254 index 128 commands all display the same information because there is currently only a single filter group and index defined.
Note
The "Use Verbose" string appears in the output area of the SrcAddr/mask and DestAddr/Mask fields suggesting use of the show cable filter group verbose form of the command to display the complete IPv6 address.
Router# show cable filterFilter SrcAddr/Mask DestAddr/Mask Prot ToS SPort DPort TCP Action StatusGrp Id v6 Flags254 128Y Use Verbose Use Verbose drop activeRouter# show cable filter group 254Filter SrcAddr/Mask DestAddr/Mask Prot ToS SPort DPort TCP Action StatusGrp Id v6 Flags254 128Y Use Verbose Use Verbose drop activeRouter# show cable filter group 254 index 128Filter SrcAddr/Mask DestAddr/Mask Prot ToS SPort DPort TCP Action StatusGrp Id v6 Flags254 128Y Use Verbose Use Verbose drop activeRouter# show cable filter group 254 index 128 verboseFilter Group : 254Filter Index : 128Filter Version : IPv6Matches : 0Source IPv6 address : 2001:33::20B:BFFF:FEA9:741F/128Destination IPv6 address : 2001:1::224/128Match action : dropStatus : activeTroubleshooting Tips
You should configure the cable filter group commands prior to applying a filter group using the cable submgmt default filter-group command. Failure to do so results in the following message, and an association to a filter group that is undefined:
Router(config)# cable submgmt default filter-group cm upstream 100Default value set to a nonexistent filter-group 100.Configuring IPv6 Domain Name Service
Cisco IOS Release 12.2(33)SCA introduces the domain name service (DNS) capability for devices using IPv6 addressing on the Cisco CMTS routers. DNS simplifies the identification of cable devices by associating a hostname with what can often be a complex 128-bit IPv6 address. The hostname can then be used in place of the IPv6 address within the CMTS router CLI that supports use of hostnames.
There are two separate DNS caches supported on a CMTS router—an IOS DNS cache and a cable-specific DNS cache that stores IPv6 addresses learned by the CMTS router for CMs and CPEs.
In this phase of the IPv6 DNS service on cable, the DNS server is queried for domain name information as needed when you use the show cable modem domain-name command. When you use this command, the following actions take place:
1.
The CMTS router checks whether CMs are online. If a CM is online, the CMTS router uses the corresponding IPv6 address assigned to the CM and looks up its domain name from the IOS DNS cache.
2.
If no match is found, the CMTS router sends a DNS-QUERY message with the IPv6 address of the CM to the DNS server, which tries to resolve the domain name.
3.
When the DNS reply is received, the CMTS router stores the domain name in the IOS DNS cache for each IPv6 address.
4.
The CMTS router also stores the fully-qualified domain name (FQDN) that is replied by the DNS server in the cable-specific DNS cache.
The following platform-independent Cisco IOS software commands are supported using hostnames by the CMTS router for IPv6 DNS on cable:
•
connect
•
ping ipv6
•
show hosts
•
telnet
•
traceroute
Prerequisites
•
A DNS server must be configured.
•
You must identify and assign the host names to the IPv6 addresses. If you are using the Cisco DNS server, use the ip host global configuration command to map hostnames to IP addresses.
•
You must configure the DNS server using the ip name-server global configuration command before use of DNS host names (or domains) are available in the supported commands.
•
The show cable modem domain-name command must be run first on the Route Processor (RP) of the CMTS router before any domain name can be used as part of a cable command.
For more information about configuring these prerequisites and related IP domain configuration options, refer to the "Mapping Host Names to IP Addresses" section in the Cisco IOS IP Configuration Guide at:
Restrictions
•
DNS for cable devices using IPv4 addressing is not supported.
•
Due to column size limitations within the command-line interface (CLI), the domain name display is limited to 32 characters. Therefore, the entire domain name cannot always be seen in CMTS router command output.
•
Only those cable devices where IPv6 address learning takes place are supported, such as acquiring an IPv6 address through DHCPv6 or the IPv6 (ND) process.
•
The cable-specific DNS cache is only updated when you use the show cable modem domain-name command on the Route Processor (RP). A DNS-QUERY can only be sent on the RP using this command, therefore the DNS cache cannot update if you use the show cable modem domain-name command on a line card console. The output is displayed on the RP only.
•
The cable-specific DNS cache does not store partially qualifed domain names—only FQDNs are stored.
•
The cable-specific DNS cache is not associated with the timeouts that apply to the IOS DNS cache. Therefore, a cable-specific DNS cache entry is not removed when an IOS DNS cache timeout occurs for that device. The cable-specific DNS cache is only updated when you use the show cable modem domain-name command.
•
The CMTS router supports storage of only one domain name per IPv6 address in the cable-specific DNS cache.
•
Domain names for the link local address are not supported.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ip name-server [vrf vrf-name] server-address1 [server-address2...server-address6]
4.
exit
5.
show cable modem domain-name
DETAILED STEPS
Configuring IPv6 Source Verification
Typically, the IPv6 source verification feature is enabled on a cable bundle interface. From there, the cable interface is associated with the virtual bundle interface to acquire its configuration.
When you enable IPv6 source verification on a cable line card interface, the source verification routine is run to verify the MAC-SID-IP binding of the packet. If the source verification succeeds, the packet is forwarded. If the verification fails, then the packet is dropped.
When a CM is operating as a bridge modem device, then the CMTS router verifies the entire IPv6 address for that CM and the CPEs behind that CM.
When a CM is operating as a router modem device, then the CMTS router only verifies the network prefix for that CM and the CPEs behind that CM. To be successful, this means that all cable modem routers mut have different prefixes assigned to them.
The cable ipv6 source-verify command only controls the source verification of IPv6 packets. For IPv4-based source verification, you must use the cable source-verify command, which also supports different options.
For more information about how to configure IPv6 source verification on a bundle interface, see the "Configuring the Cable Virtual Bundle Interface" section.
Restrictions
On the Cisco uBR10012 router in Cisco IOS Release 12.2(33)SCA, source verification of IPv6 packets occurs only on packets in the process-switched path of the Route Processor (RP).
Configuration Examples for IPv6 on Cable
This section includes the following examples:
•
Basic IPv6 Cable Filter Groups: Example
•
Multiple Cable Filter Groups: Example
•
Complete Cable Configuration with IPv6: Example
Basic IPv6 Cable Filter Groups: Example
The following example shows the configuration of an IPv6 filter group that drops traffic from a specific IPv6 host (with source address 2001:0DB8:0:0:ABCD::1/48) behind a cable router to an IPv6 host on the network (with destination address 2001:1:0DB8:0:1:FFFF:1234::5/64):
configure terminal!! Specify the filter group criteria using a common group ID!cable filter group 254 index 128 v6-src-address 2001:0DB8:0:0:ABCD::1cable filter group 254 index 128 v6-src-pfxlen 128cable filter group 254 index 128 v6-dest-address 2001:1:0DB8:0:1:FFFF:1234::5cable filter group 254 index 128 v6-dest-pfxlen 128!! Specify that the filter group is IP version 6!cable filter group 254 index 128 ip-version ipv6!! Specify the drop action for matching packets!cable filter group 254 index 128 match-action drop!! Apply the filter group with ID 254 to all CM upstream traffic!cable submgmt default filter-group cm upstream 254Multiple Cable Filter Groups: Example
The following example shows configuration of multiple cable filter groups using both IPv4 and IPv6 and separate indexes to associate the filter definitions with the same group ID.
Complete Cable Configuration with IPv6: Example
Router# show running-configBuilding configuration...Current configuration : 15010 bytes!! Last configuration change at 08:32:14 PST Thu Nov 8 2007!version 12.2no service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryptionservice internalservice compress-config!hostname router!boot-start-markerboot-end-marker!enable password password1!no aaa new-modelclock timezone PST -9clock summer-time PDT recurringclock calendar-validfacility-alarm core-temperature major 53facility-alarm core-temperature minor 45facility-alarm core-temperature critical 85facility-alarm intake-temperature major 49facility-alarm intake-temperature minor 40facility-alarm intake-temperature critical 67!!card 1/0 2jacket-1card 1/0/0 24rfchannel-spa-1card 5/0 5cable-mc520h-dcable admission-control preempt priority-voicecable modem vendor 00.18.68 SA-DPC2203cable modem vendor 00.19.47 SA-DPC2505no cable qos permission createno cable qos permission updatecable qos permission modems!cable filter group 1 index 1 src-ip 0.0.0.0cable filter group 1 index 1 src-mask 0.0.0.0cable filter group 1 index 1 dest-ip 0.0.0.0cable filter group 1 index 1 dest-mask 0.0.0.0cable filter group 2 index 1 src-ip 0.0.0.0cable filter group 2 index 1 src-mask 0.0.0.0cable filter group 2 index 1 dest-ip 0.0.0.0cable filter group 2 index 1 dest-mask 0.0.0.0cable filter group 3 index 1 src-ip 0.0.0.0cable filter group 3 index 1 src-mask 0.0.0.0cable filter group 3 index 1 dest-ip 0.0.0.0cable filter group 3 index 1 dest-mask 0.0.0.0cable filter group 4 index 1 src-ip 0.0.0.0cable filter group 4 index 1 src-mask 0.0.0.0cable filter group 4 index 1 dest-ip 0.0.0.0cable filter group 4 index 1 dest-mask 0.0.0.0cable filter group 5 index 1 src-ip 0.0.0.0cable filter group 5 index 1 src-mask 0.0.0.0cable filter group 5 index 1 dest-ip 0.0.0.0cable filter group 5 index 1 dest-mask 0.0.0.0cable filter group 6 index 1 src-ip 0.0.0.0cable filter group 6 index 1 src-mask 0.0.0.0cable filter group 6 index 1 dest-ip 0.0.0.0cable filter group 6 index 1 dest-mask 0.0.0.0cable filter group 7 index 1 src-ip 0.0.0.0cable filter group 7 index 1 src-mask 0.0.0.0cable filter group 7 index 1 dest-ip 0.0.0.0cable filter group 7 index 1 dest-mask 0.0.0.0cable filter group 8 index 1 src-ip 0.0.0.0cable filter group 8 index 1 src-mask 0.0.0.0cable filter group 8 index 1 dest-ip 0.0.0.0cable filter group 8 index 1 dest-mask 0.0.0.0cable filter group 9 index 1 src-ip 0.0.0.0cable filter group 9 index 1 src-mask 0.0.0.0cable filter group 9 index 1 dest-ip 0.0.0.0cable filter group 9 index 1 dest-mask 0.0.0.0cable filter group 10 index 1 src-ip 0.0.0.0cable filter group 10 index 1 src-mask 0.0.0.0cable filter group 10 index 1 dest-ip 0.0.0.0cable filter group 10 index 1 dest-mask 0.0.0.0cable filter group 12 index 1 src-ip 0.0.0.0cable filter group 12 index 1 src-mask 0.0.0.0cable filter group 12 index 1 dest-ip 0.0.0.0cable filter group 12 index 1 dest-mask 0.0.0.0cable filter group 16 index 1 src-ip 0.0.0.0cable filter group 16 index 1 src-mask 0.0.0.0cable filter group 16 index 1 dest-ip 0.0.0.0cable filter group 16 index 1 dest-mask 0.0.0.0ip subnet-zeroip domain name cisco.comip host host1 239.192.254.254ip host host2 239.192.254.253ip name-server 10.39.26.7ip name-server 2001:0DB8:4321:FFFF:0:800:20CA:D8BA!!!!ipv6 unicast-routingipv6 cefpacketcable multimediapacketcable!!!redundancymode sso!!controller Modular-Cable 1/0/0annex B modulation 64qam 0 23ip-address 10.30.4.175modular-host subslot 5/0rf-channel 0 cable downstream channel-id 24rf-channel 1 cable downstream channel-id 25rf-channel 2 cable downstream channel-id 26rf-channel 3 cable downstream channel-id 27rf-channel 4 cable downstream channel-id 28rf-channel 5 cable downstream channel-id 29rf-channel 6 cable downstream channel-id 30rf-channel 7 cable downstream channel-id 31rf-channel 8 cable downstream channel-id 32rf-channel 9 cable downstream channel-id 33rf-channel 10 cable downstream channel-id 34rf-channel 11 cable downstream channel-id 35rf-channel 12 cable downstream channel-id 36rf-channel 13 cable downstream channel-id 37rf-channel 14 cable downstream channel-id 38rf-channel 15 cable downstream channel-id 39rf-channel 16 cable downstream channel-id 40rf-channel 17 cable downstream channel-id 41rf-channel 18 cable downstream channel-id 42rf-channel 19 cable downstream channel-id 43rf-channel 20 cable downstream channel-id 44rf-channel 21 cable downstream channel-id 45rf-channel 22 cable downstream channel-id 46rf-channel 23 cable downstream channel-id 47!!policy-map foopolicy-map 1policy-map cospolicy-map qpolicypolicy-map shapepolicy-map dscp!!!!!!interface Loopback0ip address 127.0.0.1 255.255.255.255!interface FastEthernet0/0/0ip address 10.39.21.10 255.255.0.0speed 100half-duplexipv6 address 2001:0DB8:4321:FFFF::10/64ipv6 enable!interface Wideband-Cable1/0/0:0no cable packet-cachecable bonding-group-id 1!interface Wideband-Cable1/0/0:1no cable packet-cachecable bonding-group-id 2!interface Wideband-Cable1/0/0:2no cable packet-cachecable bonding-group-id 3!interface Wideband-Cable1/0/0:3no cable packet-cachecable bonding-group-id 4!interface Wideband-Cable1/0/0:4no cable packet-cachecable bundle 1cable bonding-group-id 5cable rf-channel 1 bandwidth-percent 60!interface Wideband-Cable1/0/0:5no cable packet-cachecable bundle 1cable bonding-group-id 6cable rf-channel 0 bandwidth-percent 40cable rf-channel 2cable rf-channel 3!interface Wideband-Cable1/0/0:6no cable packet-cachecable bonding-group-id 7!interface Wideband-Cable1/0/0:7no cable packet-cachecable bonding-group-id 8!interface Wideband-Cable1/0/0:8no cable packet-cachecable bonding-group-id 9!interface Wideband-Cable1/0/0:9no cable packet-cachecable bonding-group-id 33!interface Wideband-Cable1/0/0:10no cable packet-cachecable bonding-group-id 34!interface Wideband-Cable1/0/0:11no cable packet-cachecable bonding-group-id 35!interface Cable5/0/0no cable packet-cachecable bundle 1cable downstream channel-id 119cable downstream annex Bcable downstream modulation 256qamcable downstream interleave-depth 32cable downstream frequency 99000000no cable downstream rf-shutdowncable upstream max-ports 4cable upstream 0 connector 0cable upstream 0 frequency 6000000cable upstream 0 ingress-noise-cancellation 200cable upstream 0 docsis-mode tdmacable upstream 0 channel-width 1600000 1600000cable upstream 0 minislot-size 4cable upstream 0 range-backoff 3 6cable upstream 0 modulation-profile 21no cable upstream 0 shutdowncable upstream 1 connector 1cable upstream 1 ingress-noise-cancellation 200cable upstream 1 docsis-mode tdmacable upstream 1 channel-width 1600000 1600000cable upstream 1 minislot-size 4cable upstream 1 range-backoff 3 6cable upstream 1 modulation-profile 21cable upstream 1 shutdowncable upstream 2 connector 2cable upstream 2 ingress-noise-cancellation 200cable upstream 2 docsis-mode tdmacable upstream 2 channel-width 1600000 1600000cable upstream 2 minislot-size 4cable upstream 2 range-backoff 3 6cable upstream 2 modulation-profile 21cable upstream 2 shutdowncable upstream 3 connector 3cable upstream 3 ingress-noise-cancellation 200cable upstream 3 docsis-mode tdmacable upstream 3 channel-width 1600000 1600000cable upstream 3 minislot-size 4cable upstream 3 range-backoff 3 6cable upstream 3 modulation-profile 21cable upstream 3 shutdown!interface Cable5/0/1cable ip-init ipv6no cable packet-cachecable bundle 1cable downstream channel-id 120cable downstream annex Bcable downstream modulation 64qamcable downstream interleave-depth 32cable downstream frequency 705000000no cable downstream rf-shutdowncable upstream max-ports 4cable upstream 0 connector 4cable upstream 0 frequency 6000000cable upstream 0 ingress-noise-cancellation 200cable upstream 0 docsis-mode tdmacable upstream 0 channel-width 1600000 1600000cable upstream 0 minislot-size 4cable upstream 0 range-backoff 3 6cable upstream 0 modulation-profile 21no cable upstream 0 shutdowncable upstream 1 connector 5cable upstream 1 ingress-noise-cancellation 200cable upstream 1 docsis-mode tdmacable upstream 1 channel-width 1600000 1600000cable upstream 1 minislot-size 4cable upstream 1 range-backoff 3 6cable upstream 1 modulation-profile 21cable upstream 1 shutdowncable upstream 2 connector 6cable upstream 2 ingress-noise-cancellation 200cable upstream 2 docsis-mode tdmacable upstream 2 channel-width 1600000 1600000cable upstream 2 minislot-size 4cable upstream 2 range-backoff 3 6cable upstream 2 modulation-profile 21cable upstream 2 shutdowncable upstream 3 connector 7cable upstream 3 ingress-noise-cancellation 200cable upstream 3 docsis-mode tdmacable upstream 3 channel-width 1600000 1600000cable upstream 3 minislot-size 4cable upstream 3 range-backoff 3 6cable upstream 3 modulation-profile 21cable upstream 3 shutdown!interface Cable5/0/2no cable packet-cachecable downstream channel-id 121cable downstream annex Bcable downstream modulation 64qamcable downstream interleave-depth 32cable downstream rf-shutdowncable upstream max-ports 4cable upstream 0 connector 8cable upstream 0 ingress-noise-cancellation 200cable upstream 0 docsis-mode tdmacable upstream 0 channel-width 1600000 1600000cable upstream 0 minislot-size 4cable upstream 0 range-backoff 3 6cable upstream 0 modulation-profile 21cable upstream 0 shutdowncable upstream 1 connector 9cable upstream 1 ingress-noise-cancellation 200cable upstream 1 docsis-mode tdmacable upstream 1 channel-width 1600000 1600000cable upstream 1 minislot-size 4cable upstream 1 range-backoff 3 6cable upstream 1 modulation-profile 21cable upstream 1 shutdowncable upstream 2 connector 10cable upstream 2 ingress-noise-cancellation 200cable upstream 2 docsis-mode tdmacable upstream 2 channel-width 1600000 1600000cable upstream 2 minislot-size 4cable upstream 2 range-backoff 3 6cable upstream 2 modulation-profile 21cable upstream 2 shutdowncable upstream 3 connector 11cable upstream 3 ingress-noise-cancellation 200cable upstream 3 docsis-mode tdmacable upstream 3 channel-width 1600000 1600000cable upstream 3 minislot-size 4cable upstream 3 range-backoff 3 6cable upstream 3 modulation-profile 21cable upstream 3 shutdown!interface Cable5/0/3no cable packet-cachecable downstream channel-id 122cable downstream annex Bcable downstream modulation 64qamcable downstream interleave-depth 32cable downstream rf-shutdowncable upstream max-ports 4cable upstream 0 connector 12cable upstream 0 ingress-noise-cancellation 200cable upstream 0 docsis-mode tdmacable upstream 0 channel-width 1600000 1600000cable upstream 0 minislot-size 4cable upstream 0 range-backoff 3 6cable upstream 0 modulation-profile 21cable upstream 0 shutdowncable upstream 1 connector 13cable upstream 1 ingress-noise-cancellation 200cable upstream 1 docsis-mode tdmacable upstream 1 channel-width 1600000 1600000cable upstream 1 minislot-size 4cable upstream 1 range-backoff 3 6cable upstream 1 modulation-profile 21cable upstream 1 shutdowncable upstream 2 connector 14cable upstream 2 ingress-noise-cancellation 200cable upstream 2 docsis-mode tdmacable upstream 2 channel-width 1600000 1600000cable upstream 2 minislot-size 4cable upstream 2 range-backoff 3 6cable upstream 2 modulation-profile 21cable upstream 2 shutdowncable upstream 3 connector 15cable upstream 3 ingress-noise-cancellation 200cable upstream 3 docsis-mode tdmacable upstream 3 channel-width 1600000 1600000cable upstream 3 minislot-size 4cable upstream 3 range-backoff 3 6cable upstream 3 modulation-profile 21cable upstream 3 shutdown!interface Cable5/0/4no cable packet-cachecable downstream channel-id 123cable downstream annex Bcable downstream modulation 64qamcable downstream interleave-depth 32cable downstream rf-shutdowncable upstream max-ports 4cable upstream 0 connector 16cable upstream 0 ingress-noise-cancellation 200cable upstream 0 docsis-mode tdmacable upstream 0 channel-width 1600000 1600000cable upstream 0 minislot-size 4cable upstream 0 range-backoff 3 6cable upstream 0 modulation-profile 21cable upstream 0 shutdowncable upstream 1 connector 17cable upstream 1 ingress-noise-cancellation 200cable upstream 1 docsis-mode tdmacable upstream 1 channel-width 1600000 1600000cable upstream 1 minislot-size 4cable upstream 1 range-backoff 3 6cable upstream 1 modulation-profile 21cable upstream 1 shutdowncable upstream 2 connector 18cable upstream 2 ingress-noise-cancellation 200cable upstream 2 docsis-mode tdmacable upstream 2 channel-width 1600000 1600000cable upstream 2 minislot-size 4cable upstream 2 range-backoff 3 6cable upstream 2 modulation-profile 21cable upstream 2 shutdowncable upstream 3 connector 19cable upstream 3 ingress-noise-cancellation 200cable upstream 3 docsis-mode tdmacable upstream 3 channel-width 1600000 1600000cable upstream 3 minislot-size 4cable upstream 3 range-backoff 3 6cable upstream 3 modulation-profile 21cable upstream 3 shutdown!interface Bundle1ip address 10.46.2.1 255.255.0.0 secondaryip address 10.46.1.1 255.255.0.0cable arp filter request-send 3 2cable arp filter reply-accept 3 2cable dhcp-giaddr policy strictcable helper-address 10.39.26.8ipv6 address 2001:0DB8:4321:600::1/32ipv6 enableipv6 nd managed-config-flagipv6 nd other-config-flagipv6 nd ra interval 5ipv6 dhcp relay destination 2001:0DB8:4321:FFFF:0:800:20CA:D8BA!ip default-gateway 10.39.0.1ip classlessip route 0.0.0.0 0.0.0.0 10.39.26.12ip route 192.168.254.253 255.255.255.255 10.39.0.1ip route 192.168.254.254 255.255.255.255 10.39.0.1!!no ip http serverno ip http secure-server!logging cmts cr10k log-level errorscpd cr-id 1nls resp-timeout 1cdp run!tftp-server bootflash:docs10.cm alias docs10.cmtftp-server bootflash:rfsw_x373.bin alias rfsw_x373.binsnmp-server community private RWsnmp-server enable traps cablesnmp-server manager!!control-plane!!line con 0logging synchronousstopbits 1line aux 0line vty 0 4password lablogin!!cable fiber-node 1downstream Modular-Cable 1/0/0 rf-channel 1upstream Cable 5/0 connector 0!cable fiber-node 2downstream Modular-Cable 1/0/0 rf-channel 0 2-3upstream Cable 5/0 connector 4!endAdditional References
The following sections provide references related to the IPv6 on Cable feature.
Related Documents
Related Topic Document TitleCommands on the Cisco CMTS (universal broadband) routers
Platform-independent IPv6 commands
Platform-independent IPv6 concepts and feature configuration
Standards
Standard TitleCM-SP-MULPIv3.0-I04-070518
DOCSIS 3.0 MAC and Upper Layer Protocols Interface Specification
MIBs
RFCs
Technical Assistance
Feature Information for IPv6 on Cable
Table 3 lists the features in this module and provides links to specific configuration information. The table includes the list of legacy cable features that support IPv6 on Cable, and features that were introduced or modified in Cisco IOS Release 12.2(33)SCA or a later release.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 3 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.
Table 3 Feature Information for IPv6 on Cable
Feature Name Releases Feature Information IPv6 on Cable
12.2(33)SCA
This feature is introduced on the Cisco uBR7225VXR, Cisco uBR7246VXR, and Cisco uBR10012 Universal Broadband Routers.
The following new commands are supported:
•
cable ip-init
•
cable ipv6 source-verify
•
clear cable modem name
•
debug cable ipv6
•
show cable modem classifiers
•
show cable modem domain-name
•
show cable modem ipv6
•
show cable modem type
12.2(33)SCA
The following modified commands are supported:
•
cable event syslog-server
•
cable filter group
•
clear cable host
•
clear cable modem reset
•
ping docsis
•
show cable filter
•
show cable modem
•
show cable modem access-group
IPv6 on Cable (continued)
12.2(33)SCA
•
show cable modem calls
•
show cable modem classifiers
•
show cable modem cnr
•
show cable modem connectivity
•
show cable modem counters
•
show cable modem cpe
•
show cable modem errors
•
show cable modem flap
•
show cable modem mac
•
show cable modem maintenance
•
show cable modem offline
•
show cable modem phy
•
show cable modem qos
•
show cable modem registered
•
show cable modem rogue
•
show cable modem unregistered
•
show interface cable modem
•
show interface cable sid
12.2(33)SCA
The following existing cable features support the IPv6 protocol stack without any other modification to the configuration of the cable feature on the Cisco CMTS routers:
•
Baseline Privacy Plus (BPI+)
•
Cable Monitor (Except cable monitoring based on IPv6 ACL)
•
Cable Transport LAN Service (TLS)
•
CM configuration files
•
DHCP Relay Agent option for DOCSIS 3.0, Annex J (See also "DHCPv6 Restrictions for IPv6 on Cable" section)
IPv6 on Cable
12.2(33)SCA
•
DMIC (except configuration file generation for DMIC IPv6 CMs)
•
Dynamic Channel Change (DCC)
•
DOCSIS Dynamic Service Addition (DSA) and Dynamic Service Change (DSC) operations
•
DOCSIS load balancing (except load balancing with HCCP)
•
Flap list
•
IPv6 L2VPN
•
Spectrum management
•
Virtual bundles (See the "Configuring the Cable Virtual Bundle Interface" section)
IPv6 Access ServicesIPv6 Access Services: DHCP for IPv6 Relay Agent
12.2(33)SCA
A DHCP relay agent, which may reside on the client's link, is used to relay messages between the client and server.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing DHCP for IPv6" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
How to Implement DHCP for IPv6
IPv6 Access Services: DHCPv6 Prefix Delegation
12.2(33)SCA
The DHCP for IPv6 prefix delegation feature can be used to manage link, subnet, and site addressing changes. DHCP for IPv6 can be used in environments to deliver stateful and stateless information.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing DHCP for IPv6" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
Configuring the DHCP for IPv6 Server Function
•
Configuring the DHCP for IPv6 Client Function
•
Configuring the DHCP for IPv6 Server Function: Example
IPv6 Access Services: Source Verification
12.2(33)SCA
Enabling IPv6 source verification on a cable line card interface, allows the source verification routine to verify the MAC-SID-IP binding of the packet. If the source verification succeeds, the packet is forwarded. If the verification fails, then the packet is dropped.
Platform-Specific Documentation for the Cisco CMTS Routers
For information about configuring IPv6 source verification, see the "Configuring IPv6 Source Verification" section.
IPv6 Access Services: Stateless DHCPv6
12.2(33)SCA
Stateless DHCP for IPv6 allows DHCP for IPv6 to be used for configuring a node with parameters that do not require a server to maintain any dynamic state for the node.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing DHCP for IPv6" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
Configuring Nodes Without Prefix Delegation
•
Configuring the Stateless DHCPv6 Function
IPv6 Basic ConnectivitySyslog over IPv6
12.2(33)SCA
The Cisco IOS syslog process in IPv6 allows users to log syslog messages to external syslog servers and hosts with IPv6 addresses.
Platform-Independent Cisco IOS Software Documentation
The Simplified IPv6 Packet Header section of the "Implementing IPv6 Addressing and Basic Connectivity" chapter and the Configuring Syslog over IPv6 section of the "Implementing IPv6 for Network Management" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature.
IPv6 Unicast
12.2(33)SCA
An IPv6 unicast address is an identifier for a single interface, on a single node.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing IPv6 Addressing and Basic Connectivity" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
IPv6 Neighbor Solicitation Message
•
IPv6 Router Advertisement Message
IPv6 Unicast Reverse Path Forwarding (uRPF)
12.2(33)SCA
The Unicast RPF feature mitigates problems caused by malformed or forged (spoofed) IPv6 source addresses that pass through an IPv6 router. Malformed or forged source addresses can indicate denial-of-service (DoS) attacks based on source IPv6 address spoofing.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing IPv6 Addressing and Basic Connectivity" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
Prerequisites for Implementing IPv6 Addressing and Basic Connectivity
•
Cisco Express Forwarding and distributed Cisco Express Forwarding Switching for IPv6
IPv6 Cable Filter GroupsIPv6 Cable Filter Groups: IPv6 Filter Classifiers for CM and CPE traffic
12.2(33)SCA
The IPv6 cable filter group feature support of the packet filtering portion of the DOCSIS Subscriber Management MIB (DOCS-SUBMGMT-MIB) using configuration commands on the CMTS routers. This IPv6 cable filter group support extends filter classifiers with IPv6 addressing options for CM and CPE traffic, but is independent of DOCSIS IPv6 classifiers which are used to match packets to service flows.
Platform-Specific Documentation for the Cisco CMTS Routers
For information about configuring IPv6 cable filter groups, see the "Configuring IPv6 Cable Filter Groups" section.
IPv6 Data Link LayerIPv6 Data Link: Ethernet, Fast Ethernet, Gigabit Ethernet, 10-Gigabit Ethernet
12.2(33)SCA
In IPv6 networks, a data link is a network sharing a particular link-local prefix. Ethernet, Fast Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet are data links supported for IPv6.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing IPv6 Addressing and Basic Connectivity" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
IPv6 Data Link: VLANs Using IEEE 802.1q Encapsulation
12.2(33)SCA
In IPv6 networks, a data link is a network sharing a particular link-local prefix. VLANs using IEEE 802.1Q encapsulation is a type of data link supported for IPv6.
Platform-Independent Cisco IOS Software Documentation
The "IPv6 Data Links" section of the "Implementing IPv6 Addressing and Basic Connectivity" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature.
IPv6 ICMPv6ICMPv6
12.2(33)SCA
ICMP for IPv6 generates error messages, such as ICMP destination unreachable messages, and informational messages, such as ICMP echo request and reply messages. Additionally, ICMP packets in IPv6 are used in the IPv6 neighbor discovery process, path MTU discovery, and the MLD protocol for IPv6.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing IPv6 Addressing and Basic Connectivity" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
IPv6 Neighbor Solicitation Message
•
IPv6 Router Advertisement Message
•
Configuring IPv6 ICMP Rate Limiting
ICMPv6 Redirect
12.2(33)SCA
A value of 137 in the Type field of the ICMP packet header identifies an IPv6 neighbor redirect message. Routers send neighbor redirect messages to inform hosts of better first-hop nodes on the path to a destination.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing IPv6 Addressing and Basic Connectivity" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
IPv6 Neighbor Redirect Message
IPv6 Multicast
IPv6 Multicast
12.2(33)SCA
An IPv6 multicast address is an identifier for a set of interfaces that typically belong to different nodes.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing IPv6 Multicast" chapter of the Cisco IOS IPv6 Configuration Library provide information about the supported IPv6 multicast features on the Cisco CMTS routers:
•
Prerequisites for Implementing IPv6 Multicast
•
Restrictions for Implementing IPv6 Multicast
•
Information about Implementing IPv6 Multicast
•
Enabling IPv6 Multicast Routing
•
Disabling Default Features in IPv6 Multicast
•
Configuration Examples for Implementing IPv6 Multicast
IPv6 Multicast: MLD Access Group
12.2(33)SCA
The MLD access group provides receiver access control in Cisco IOS IPv6 multicast routers.
The following sections of the "Implementing IPv6 Multicast" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
IPv6 Multicast: MLD Group Limits
12.2(33)SCA
The MLD group limits feature provides protection against denial of service (DoS) attacks caused by MLD packets.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing IPv6 Multicast" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
Multicast Listener Discovery Protocol for IPv6
IPv6 Multicast: PIM Sparse Mode (PIM-SM)
12.2(33)SCA
PIM-SM uses unicast routing to provide reverse-path information for multicast tree building. PIM-SM is used in a multicast network when relatively few routers are involved in each multicast and these routers do not forward multicast packets for a group, unless there is an explicit request for the traffic.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing IPv6 Multicast" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
Restrictions for Implementing IPv6 Multicast
•
IPv6 Multicast Routing Implementation
IPv6 Multicast: PIM Source Specific Multicast (PIM-SSM)
12.2(33)SCA
PIM-SSM supports the implementation of SSM and is derived from PIM-SM. The SSM feature forwards datagram traffic to receivers from only those multicast sources that the receivers have explicitly joined, optimizing bandwidth utilization and denying unwanted Internet broadcast traffic.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing IPv6 Multicast" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
IPv6 Multicast Routing Implementation
•
Protocol Independent Multicast
•
PIM-Source Specific Multicast
•
IPv6 Multicast Process Switching and Fast Switching
IPv6 Multicast: Scope Boundaries
12.2(33)SCA
IPv6 includes support for global and nonglobal addresses.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing IPv6 Multicast" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
IPv6 Multicast: Static Multicast Routing (Mroute)
12.2(33)SCA
IPv6 static mroutes share the same database as IPv6 static routes and are implemented by extending static route support.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing IPv6 Multicast" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
Restrictions for Implementing IPv6 Multicast
IPv6 Neighbor DiscoveryIPv6 Neighbor Discovery
12.2(33)SCA
The IPv6 neighbor discovery process uses ICMP messages and solicited-node multicast addresses to determine the link-layer address of a neighbor on the same network (local link), verify the reachability of a neighbor, and track neighboring routers.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing IPv6 Addressing and Basic Connectivity" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
IPv6 Neighbor Discovery Duplicate Address Detection
12.2(33)SCA
IPv6 neighbor discovery duplicate address detection is performed first on a new, link-local IPv6 address before the address is assigned to an interface (the new address remains in a tentative state while duplicate address detection is performed).
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing IPv6 Addressing and Basic Connectivity" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
IPv6 Neighbor Solicitation Message
IPv6 Neighbor Discovery Static Cache Entry
12.2(33)SCA
The IPv6 static cache entry for neighbor discovery feature allows static entries to be made in the IPv6 neighbor cache.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing IPv6 Addressing and Basic Connectivity" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
IPv6 RoutingIPv6 Routing: IS-IS Support for IPv6
12.2(33)SCA
IPv6 enhancements to IS-IS allow IS-IS to advertise IPv6 prefixes in addition to IPv4 and OSI routes.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing IS-IS for IPv6" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
Configuring Single-Topology IS-IS for IPv6
•
Redistributing Routes into an IS-IS Routing Process
IPv6 Routing: IS-IS Multitopology Support for IPv6
12.2(33)SCA
IS-IS multitopology support for IPv6 allows IS-IS to maintain a set of independent topologies within a single area or domain.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing IS-IS for IPv6" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
IS-IS Multitopology Support for IPv6
•
Transition from Single-Topology to Multitopology Support for IPv6
IPv6 Routing: Multiprotocol BGP Extenstions for IPv6
12.2(33)SCA
Multiprotocol BGP extensions for IPv6 supports the same features and functionality as IPv4 BGP.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing Multiprotocol BGP for IPv6" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
Multiprotocol BGP Extensions for IPv6
IPv6 Routing: Multiprotocol BGP Link-local Address Peering
12.2(33)SCA
IPv6 on Cable supports multiprotocol BGP link-local address peering.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing Multiprotocol BGP for IPv6" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
Configuring an IPv6 Multiprotocol BGP Peer Using a Link-Local Address
IPv6 Routing: OSPF for IPv6 (OSPFv3)
12.2(33)SCA
OSPF version 3 for IPv6 expands on OSPF version 2 to provide support for IPv6 routing prefixes and the larger size of IPv6 addresses.
Platform-Independent Cisco IOS Software Documentation
The "Implementing OSPF for IPv6" chapter of the Cisco IOS IPv6 Configuration Library provides information about this feature.
IPv6 Routing: OSPF for IPv6 Authentication Support with IPSec
12.2(33)SCA
OSPF for IPv6 uses the IPSec secure socket API to add authentication to OSPF for IPv6 packets.
Note
In Cisco IOS Release 12.2(33)SCA, the Cisco CMTS routers do not support OSPF with IPv6 multicast routing.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing OSPF for IPv6" chapter of the Cisco IOS IPv6 Configuration Library provides information about this feature:
•
OSPF for IPv6 Authentication Support with IPSec
•
Configuring IPSec on OSPF for IPv6
•
Defining Authentication on an Interface
IPv6 Routing: Policy-Based Routing
12.2(33)SCA
Policy-based routing for IPv6 in Cisco IOS software allows a user to manually configure how received packets should be routed.
Platform-Independent Cisco IOS Software Documentation
The "Implementing Policy-Based Routing for IPv6" chapter of the Cisco IOS IPv6 Configuration Library provides information about this feature.
IPv6 Routing: RIP for IPv6 (RIPng)
12.2(33)SCA
RIP enhancements for IPv6 include support for IPv6 addresses and prefixes, and the use of the all-RIP-routers multicast group address FF02::9 as the destination address for RIP update messages.
Platform-Independent Cisco IOS Software Documentation
The "Implementing RIP for IPv6" chapter of the Cisco IOS IPv6 Configuration Library provides information about this feature.
IPv6 Routing: Route Redistribution for RIPng
12.2(33)SCA
Routes may be specified by prefix, using a route-map prefix list, or by tag, using the route-map "match tag" function.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing RIP for IPv6" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
Redistributing Routes into an IPv6 RIP Routing Process
•
Configuring Tags for RIP Routes
IPv6 Routing: Route Redistribution for IS-IS
12.2(33)SCA
IS-IS for IPv6 supports redistributing routes into an IPv6 IS-IS routing process and redistributing IPv6 IS-IS routes between IS-IS levels.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing IS-IS for IPv6" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
Information about Implementing IS-IS for IPv6
•
Redistributing Routes into an IS-IS Routing Process
IPv6 Routing: Static Routes
12.2(33)SCA
Static routes are manually configured and define an explicit path between two networking devices.
Platform-Independent Cisco IOS Software Documentation
The "Implementing Static Routes for IPv6" chapter of the Cisco IOS IPv6 Configuration Library provides information about this feature.
IPv6 Services and ManagementIPv6 Services: AAAA DNS Lookups over an IPv4 Transport
12.2(33)SCA
IPv6 basic connectivity can be enhanced by configuring support for AAAA record types in the DNS name-to-address and address-to-name lookup processes.
Platform-Independent Cisco IOS Software Documentation
The "DNS for IPv6" section of the "Implementing IPv6 Addressing and Basic Connectivity" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature.
IPv6 Services: Cisco Discovery Protocol—IPv6 Address Family Support for Neighbor Information
12.2(33)SCA
The Cisco Discovery Protocol IPv6 address support for neighbor information feature adds the ability to transfer IPv6 addressing information between two Cisco devices.
Platform-Independent Cisco IOS Software Documentation
The "Cisco Discovery Protocol IPv6 Address Support" section of the "Implementing IPv6 Addressing and Basic Connectivity" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature.
IPv6 Services: CISCO-IP-FORWARD-MIB
12.2(33)SCA
A MIB is a database of the objects that can be managed on a device. The managed objects, or variables, can be set or read to provide information on the network devices and interfaces.
Platform-Independent Cisco IOS Software Documentation
The "Implementing IPv6 Addressing and Basic Connectivity" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature.
IPv6 Services: CISCO-IP-MIB Support
12.2(33)SCA
A MIB is a database of the objects that can be managed on a device. The managed objects, or variables, can be set or read to provide information on the network devices and interfaces.
Platform-Independent Cisco IOS Software Documentation
The "Implementing IPv6 Addressing and Basic Connectivity" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature.
IPv6 Services: DNS Lookups over an IPv6 Transport
12.2(33)SCA
IPv6 supports DNS record types that are supported in the DNS name-to-address and address-to-name lookup processes.
Platform-Independent Cisco IOS Software Documentation
The "DNS for IPv6" section of the "Implementing IPv6 Addressing and Basic Connectivity" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature.
Platform-Specific Documentation for the Cisco CMTS Routers
For information about configuring DNS for IPv6 on the Cisco CMTS routers, see the "Configuring IPv6 Domain Name Service" section.
IPv6 Services: IPv6 IPSec VPN
12.2(33)SCA
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing IPSec in IPv6 Security" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
Information About Implementing IPSec for IPv6 Security
IPv6 Services: Secure Shell (SSH) Support over IPv6
12.2(33)SCA
SSH in IPv6 functions the same and offers the same benefits as SSH in IPv4—the SSH Server feature enables an SSH client to make a secure, encrypted connection to a Cisco router and the SSH Client feature enables a Cisco router to make a secure, encrypted connection to another Cisco router or to any other device running an SSH server.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing IPv6 for Network Management" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
IPv6 Services: SNMP over IPv6
12.2(33)SCA
SNMP can be configured over IPv6 transport so that an IPv6 host can perform SNMP queries and receive SNMP notifications from a device running Cisco IOS IPv6.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing IPv6 for Network Management" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
Configuring an SNMP Notification Server over IPv6
•
Configuring an SNMP Notification Server over IPv6: Examples
IPv6 Services: Standard Access Control Lists
12.2(33)SCA
Access lists determine what traffic is blocked and what traffic is forwarded at router interfaces and allow filtering based on source and destination addresses, inbound and outbound to a specific interface.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing Traffic Filters and Firewalls for IPv6 Security" chapter of the Cisco IOS IPv6 Configuration Library provides information about this feature:
•
Restrictions for Implementing Traffic Filters and Firewalls for IPv6 Security
•
Access Control Lists for IPv6 Traffic Filtering
•
PAM in Cisco IOS Firewall for IPv6
•
How to Implement Traffic Filters and Firewalls for IPv6 Security
•
Configuration Examples for Implementing Traffic Fitlers and Firewalls for IPv6 Security
IPv6 SwitchingIPv6 Switching: CEF/dCEF Support
12.2(33)SCA
Cisco Express Forwarding for IPv6 is advanced, Layer 3 IP switching technology for the forwarding of IPv6 packets. Distributed Cisco Express Forwarding for IPv6 performs the same functions as CEFv6 but for distributed architecture platforms.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing IPv6 Addressing and Basic Connectivity" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
Cisco Express Forwarding and distributed Cisco Express Forwarding Switching for IPv6
•
Configuring Cisco Express Forwarding and distributed Cisco Express Forwarding Switching for IPv6
Platform-Specific Documentation for the Cisco CMTS Routers
For information about configuring IPv6 switching on the Cisco CMTS routers, see the "Configuring IPv6 Switching Services" section.
IPv6 TunnelingIPv6 Tunneling: Manually Configured IPv6 over IPv4 Tunnels
12.2(33)SCA
A manually configured tunnel is equivalent to a permanent link between two IPv6 domains over an IPv4 backbone.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing Tunneling for IPv6" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
IPv6 Manually Configured Tunnels
•
Configuring Manual IPv6 Tunnels
IPv6 Tunneling: IPv6 over IPv4 GRE Tunnels
12.2(33)SCA
GRE tunnels are links between two points, with a separate tunnel for each link. The tunnels are not tied to a specific passenger or transport protocol, but in this case carry IPv6 as the passenger protocol with the GRE as the carrier protocol and IPv4 or IPv6 as the transport protocol.
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing Tunneling for IPv6" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
GRE/IPv4 Tunnel Support for IPv6 Traffic
IPv6 Tunneling: IPv4 over IPv6 Tunnels
12.2(33)SCA
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing Tunneling for IPv6" chapter of the Cisco IOS IPv6 Configuration Library provide information about this feature:
•
IPv6 Manually Configured Tunnels
CCDE, CCVP, Cisco Eos, Cisco StadiumVision, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn is a service mark; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0801R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2008 Cisco Systems, Inc. All rights reserved.



