Feedback
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
Restrictions for IPv6 Dual Stack CPE Support on the CMTS
Restrictions for Implementing IPv6 VPN over MPLS
Restrictions for Multiple IAPDs in a Single Advertise
Information About IPv6 on Cable
Features Supported from Cisco IOS Release 12.2(33)SCE
Features Supported from Cisco IOS Release 12.2(33)SCF4
Features Supported from Cisco IOS Release 12.2(33)SCG1
Overview of the DOCSIS 3.0 Network Model Supporting IPv6
Overview of Cable Modem IPv6 Address Provisioning
Overview of IPv6 Dual Stack CPE Support on the CMTS
Overview of IPv6 over Subinterfaces
Overview of High Availability on IPv6
Overview of IPv6 VPN over MPLS
Overview of IPv6 CPE Router Support on the Cisco CMTS
Support for IPv6 Prefix Stability on the CMTS
Configurable DHCPv6 Relay Address
Support for Multiple IAPDs in a Single Advertise
IPv6 Neighbor Discovery Gleaning
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
Configuring IPv6 VPN over MPLS
Configuring DHCPv6 Relay Agent
How to Verify IPv6 Dual Stack CPE Support on the CMTS
Configuration Examples for IPv6 on Cable
IPv6 over Subinterfaces Example:
Basic IPv6 Cable Filter Groups Example:
Complete Cable Configuration with IPv6 Example:
BGP Configuration for 6VPE Example:
Subinterface Configuration for 6VPE Example:
Cable Interface Bundling Example:
VRF Configuration for 6VPE Example:
Verifying IPv6 VRF Configuration
Verifying MPLS Forwarding Table
Verifying IPv6 Cable Modem and its Host State
Verifying Multiple IAPDs in a Single Advertise
Feature Information for IPv6 on Cable
IPv6 on Cable
First Published: February 18, 2008Last Updated: October 15, 2012
Note
Cisco IOS Release 12.2(33)SCA integrates support for this feature on the Cisco CMTS routers. This feature is also supported in Cisco IOS Release 12.3BC, and this document contains information that references many legacy documents related to Cisco IOS 12.3BC. In general, any references to Cisco IOS Release 12.3BC also apply to Cisco IOS Release 12.2SC.
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.
Note
The IPv6 feature support available in the Cisco IOS software and for 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.
•
–
–
•
–
–
–
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for IPv6 on Cable" section.
Use Cisco Feature Navigator to find information about platform support and Cisco 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
•
Table 1 shows the hardware compatibility prerequisites for the IPv6 on Cable feature.
Table 1 IPv6 on Cable Hardware Compatibility Matrix
Cisco uBR10012 Universal Broadband Router
Cisco IOS Release 12.2(33)SCA and later
•
Cisco IOS Release 12.2(33)SCB and later
•
Cisco IOS Release 12.2(33)SCA and later
•
Cisco IOS Release 12.2(33)SCC and later
•
Cisco IOS Release 12.2(33)SCE and later
•
•
Cisco uBR7246VXR Universal Broadband Router
Cisco IOS Release 12.2(33)SCA and later
•
•
Cisco IOS Release 12.2(33)SCA and later
•
Cisco IOS Release 12.2(33)SCD and later
•
—
Cisco uBR7225VXR Universal Broadband Router
Cisco IOS Release 12.2(33)SCA and later
•
Cisco IOS Release 12.2(33)SCD and later
•
Cisco IOS Release 12.2(33)SCA and later
•
Cisco IOS Release 12.2(33)SCD and later
•
—
1 Supports only DOCSIS 2.0 and IPv6 cable modems.
2 Supports only DOCSIS 3.0 and IPv6 cable modems.
3 Cisco uBR-MC88V cable interface line card is compatible only with NPE-G2
Note
Restrictions for IPv6 on Cable
The following capabilities are not supported by IPv6 on the Cisco CMTS routers:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Note
•
•
•
•
•
•
Note
•
Note
Other restrictions for IPv6 on cable:
•
•
•
•
•
•
•
•
•
•
•
•
•
DHCPv6 Restrictions for IPv6 on Cable
•
•
The following DHCPv6 areas are not supported by the Cisco CMTS routers:
•
•
–
–
–
–
–
IPv6 Access Services Restrictions for IPv6 on Cable
The following areas of IPv6 access services are not supported by the CMTS routers:
•
•
•
•
•
•
•
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:
•
•
•
•
•
•
•
•
•
Multicast Restrictions for IPv6 on Cable
IPv6 multicast has the following behavior restrictions on the Cisco CMTS routers:
•
•
•
•
The following areas of IPv6 multicast are not supported by the Cisco CMTS routers:
•
•
•
•
•
•
•
•
•
•
•
•
•
Provisioning Restrictions for IPv6 on Cable
The following areas of IPv6 provisioning are not supported on the Cisco CMTS routers:
•
•
•
•
•
Note
Note
Note
QoS Restrictions for IPv6 on Cable
The following areas of DOCSIS QoS are not supported by the Cisco CMTS routers:
•
•
Note
Routing Restrictions for IPv6 on Cable
The following areas of IPv6 routing are not supported by the Cisco CMTS routers:
•
•
Note
•
•
Services and Management Restrictions for IPv6 on Cable
The following areas of IPv6 services and management are not supported by the Cisco CMTS routers:
•
•
Switching Restrictions for IPv6 on Cable
The following areas of IPv6 switching services are not supported by the Cisco CMTS routers:
•
•
•
•
•
Note
Tunneling Restrictions for IPv6 on Cable
The following areas of IPv6 tunneling services are not supported by the Cisco CMTS routers:
•
•
•
•
•
•
•
Restrictions for IPv6 Dual Stack CPE Support on the CMTS
The IPv6 Dual Stack CPE Support on the CMTS feature in Cisco IOS Release 12.2(33)SCC has the following limitations:
Note
•
•
Restrictions for Implementing IPv6 VPN over MPLS
•
•
•
Note
Restrictions for Multiple IAPDs in a Single Advertise
•
•
•
•
•
Information About IPv6 on Cable
This section includes the following topics:
•
•
•
•
•
•
•
•
•
•
•
•
•
Features Supported from Cisco IOS Release 12.2(33)SCE
The following features are supported on the Cisco CMTS routers from Cisco IOS Release 12.2(33)SCE onwards:
•
•
•
•
•
•
•
•
•
•
•
Features Supported from Cisco IOS Release 12.2(33)SCF4
The following features are supported on the Cisco CMTS routers from Cisco IOS Release 12.2(33)SCF4 onwards:
•
•
•
Features Supported from Cisco IOS Release 12.2(33)SCG1
The following features are supported on Cisco CMTS routers from Cisco IOS Release 12.2(33)SCG1 onwards:
•
•
•
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:
•
Note
•
•
The CMTS router supports IPv6 address assignment, routing, and forwarding of IPv6 multicast and unicast packets.
Note
•
•
•
•
•
Note
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.
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
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.
2.
Note
3.
If the Rapid-Commit option is not used by the CM, then the CM responds to the Advertise message of the server with a Request message to select the server that the CMTS router relays to the DHCPv6 server. If the Rapid-Commit option is used, then multiple DHCPv6 servers that could assign different addresses to the same CPE must not be used.
The CM starts the DAD process to verify the uniqueness of the IPv6 address that the DHCPv6 server assigns to it.
4.
Overview of IPv6 Dual Stack CPE Support on the CMTS
In Cisco IOS Release 12.2(33)SCA and later releases, IPv6 was added to the CMTS. Most operating systems (OS) deployed at homes support dual stack operation. In Cisco IOS Release 12.2(33)SCC and later releases, CMTS also supports dual stack, which is both IPv4 and IPv6 addressing on the CPE.
Overview of IPv6 over Subinterfaces
In Cisco IOS Release 12.2(33)SCC, CMTS supports IPv6 over bundle subinterfaces. To configure IPv6 on bundle subinterfaces, see the Implementing IPv6 Addressing and Basic Connectivity for Cable Interfaces and Bundles section. For a CMTS bundle configuration example, see the IPv6 over Subinterfaces Example: section.
To enable IPv6 on subinterfaces, configure IPv6 on bundle subinterfaces and not the bundle. Reset the CMs after the subinterface is configured.
Note
Overview of High Availability on IPv6
In Cisco IOS Release 12.2(33)SCE, CMTS supports HA features on IPv6. IPv6 HA is supported on PRE2 with IPv6 punt path forwarding and on PRE4 with IPv6 PXF forwarding.
Note
The IPv6 HA feature support in Cisco CMTS routers covers the following capabilities:
•
•
•
DOCSIS PRE HA
The DOCSIS PRE HA has the following behavior restrictions and prerequisites on the Cisco CMTS routers:
•
•
•
•
•
DOCSIS Line Card HA
The DOCSIS line card HA has the following behavior restrictions and prerequisites on the Cisco CMTS routers:
•
•
•
•
Dynamic Channel Change
The Dynamic Channel Change (DCC) feature makes use of the line card HA for CM data structure synchronization and rebuilds.
Note
The IPv6 and IPv4 DCC functionality has the following behavior restrictions and prerequisites on the Cisco CMTS routers:
Narrowband Cable Modem
•
•
Wideband Cable Modem
•
•
Overview of IPv6 VPN over MPLS
The Multiprotocol Label Switching (MPLS) VPN feature represents an implementation of the provider edge (PE) based VPN model. This document describes the IPv6 VPN over MPLS (6VPE) feature.
The 6VPE feature allows Service Providers to provide an IPv6 VPN service that does not require an upgrade or reconfiguration of the PE routers in the IPv4 MPLS Core. The resulting IPv6 VPN service has a configuration and operation which is virtually identical to the current IPv4 VPN service.
In principle, there is no difference between IPv4 and IPv6 VPNs. In both IPv4 and IPv6, the multiprotocol BGP is the core of the MPLS VPN for IPv6 (VPNv6) architecture. It is used to distribute IPv6 routes over the service provider backbone using the same procedures to work with overlapping addresses, redistribution policies, and scalability issues.
Figure 3 illustrates the 6PE/6VPE reference architecture diagram.
Figure 3 6PE/6VPE Reference Architecture
For more information about these tasks, see the Implementing IPv6 VPN over MPLS chapter in the Cisco IOS IPv6 Configuration Guide, Release 12.2SR.
Cable Monitor
The Cable Monitor and Intercept features for Cisco CMTS routers provide a software solution for monitoring and intercepting traffic coming from a cable network. These features give service providers Lawful Intercept capabilities.
For more information, see Cable Monitor and Intercept Features for the Cisco CMTS Routers guide at: http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_mon_intrcpt.html
Overview of IPv6 CPE Router Support on the Cisco CMTS
In Cisco IOS Release 12.2(33)SCF and later releases, the IPv6 CPE router support is provided on the Cisco CMTS. The IPv6 CPE router is a node primarily for home or small office use that connects the end-user network to a service provider network. It is also referred to as the home router.
The IPv6 CPE router is responsible for implementing IPv6 routing; that is, the IPv6 CPE router looks up the IPv6 destination address in its routing table and decides to which interface the packet should be sent.
The IPv6 CPE router performs the following functions:
•
•
•
Figure 4 illustrates the CPE router reference architecture diagram between the CPE router, the CMTS, and the DHCPv6 server (CNR) when the CM is requesting an IPv6 address.
Figure 4 IPv6 CPE Router Reference Architecture
As part of the IPv6 CPE Router Support feature, the following enhancements are introduced:
•
•
•
Support for IPv6 Prefix Stability on the CMTS
Cisco IOS Release 12.2(33)SCF1 supports IPv6 prefix stability on the Cisco CMTS as specified in DOCSIS 3.0 MULPI CM-SP-MULPIv3.0-I15-110210 standard. The IPv6 prefix stability allows an IPv6 home router to move from one Cisco CMTS to another while retaining the same prefix.
The multiple service operators (MSOs) can use this feature to allow their business customers (with IPv6 routers) to retain the same IPv6 prefix during a node split.
Configurable DHCPv6 Relay Address
The DHCPv6 Cisco IOS relay agent on the Cisco CMTS router sends relay-forward messages from a source address to all configured relay destinations. The source address is either an IPv6 address provisioned on the network interface or a Cisco CMTS WAN IPv6 address. The relay destination can be a unicast address of a server, another relay agent, or a multicast address. The relay-forward messages contain specific DHCPv6 link-addresses.
A DHCP relay agent is used to relay messages between the client and server. A client locates a DHCP server using a reserved, link-scoped multicast address.
To configure DHCPv6 Relay Address on the Cisco CMTS bundle subinterfaces, see the "Configuring DHCPv6 Relay Agent" section section.
For more information about the DHCPv6 client, server, and relay functions, see the "Implementing DHCP for IPv6" chapter in the Cisco IOS IPv6 Configuration Guide, Release 12.2SR.
Support for Multiple IAPDs in a Single Advertise
Cisco IOS Release 12.2(33)SCG1supports assignment of multiple IA_NA and IAPD to CPEs behind a CM. This feature include support for link-local addresses and IA_NA and IAPD. However, a CM can be assigned only one IA_NA. This IA_NA can be either static or DHCP-assigned.
The CPEs behind the CM can request for multiple DHCPv6 IA_NAs and IAPDs. Each CPE is assigned multiple IA_NAs and IAPDs in a single Advertise/Reply message .. Each CPE request for IA_NA and IAPD is treated as a separate Advertise/Reply message.
IPv6 Neighbor Discovery Gleaning
The IPv6 Neighbor Discovery (ND) Gleaning feature enables Cisco CMTS routers to automatically recover lost IPv6 CPE addresses and update the CPE records in the Cisco CMTS subscriber database. The Cisco CMTS router gleans only the solicited neighbor advertise (NA) messages transmitted in the upstream direction. IPv6 ND gleaning is similar to Address Resolution Protocol (ARP) gleaning for IPv4 CPE recovery.
The IPv6 ND Gleaning feature is configured by default on Cisco CMTS routers. To disable this feature, use the no form of the cable nd command in bundle interface configuration mode. The cable nd command adds a CPE (host behind a cable modem) to the Cisco CMTS subscriber database. This command does not impact the IPv6 ND protocol operation on the router.
Note
How to Configure IPv6 on Cable
This section includes the following tasks:
•
•
•
•
•
•
•
•
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):
•
•
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 universal broadband 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.
The show ipv6 cef platform command is supported on the Cisco CMTS platform from Cisco IOS Release 12.2(33)SCE onwards. You can use the show ipv6 cef platform command for debugging purposes.
Prerequisites
•
Note
•
•
•
Restrictions
In Cisco IOS Release 12.2(33)SCA, Parallel Express Forwarding (PXF) switching is not supported on the Cisco uBR10012 universal broadband router.
Note
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
What To Do Next
•
Note
•
Implementing IPv6 Addressing and Basic Connectivity for Cable Interfaces and Bundles
•
•
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 addresses 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. 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.
Starting with Cisco IOS Release 12.3(33)SCB10, IPv6 commands can be configured on multiple bundle subinterfaces.
Prerequisites
The cable ipv6 source-verify and cable nd commands are not compatible with each other in Cisco IOS release 12.2(33)SCE and later. You must disable IPv6 ND gleaning using the no form of the cable nd command before using the cable ipv6 source-verify command to ensure that only DHCPv6 and SAV-based CPEs can send traffic on the router. For details on disabling IPv6 ND gleaning, see the "Disabling IPv6 ND Gleaning" section.
Restrictions
All multicast traffic is flooded onto bundle member interfaces.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
What To Do Next
•
•
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
Prerequisites
Configuration of a bundle interface is required.
Restrictions
APM is not supported in Cisco IOS Release 12.2(33)SCA. Support for APM feature is provided from Cisco IOS Release 12.2(33)SCC onwards.
Note
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
What To Do Next
•
•
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, which can be established using the following configuration methods:
•
•
•
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:
•
•
•
–
–
•
–
–
Note
Prerequisites
You must create the cable filter group before you assign it to a CM or CPE upstream or downstream.
Restrictions
•
•
•
•
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
DETAILED STEPS
Examples
The following example shows how to create 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:DB8::/32cable filter group 254 index 128 v6-src-pfxlen 48cable filter group 254 index 128 v6-dest-address 2001:DB8::/32cable 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:DB8::/32 (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
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:DB8::/32Destination IPv6 address : 2001:DB8::/32Match 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.
2.
3.
4.
Note
The following platform-independent Cisco IOS software commands are supported using host names by the CMTS router for IPv6 DNS on cable:
•
•
•
•
•
Prerequisites
•
•
•
•
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:
http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/1cfipadr.html#wp1001317
Restrictions
•
•
•
•
•
•
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
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 verifies the MAC address-MD-SID-IP binding of the packet. If the source verification succeeds, the packet is forwarded. If the verification fails, the packet is dropped.
When a CM is operating as a bridge modem device, then the CMTS router verifies all the IPv6 addresses related to that CM and the CPEs behind that CM.
The cable ipv6 source-verify command controls only the source verification of IPv6 packets. For IPv4-based source verification, 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).
Note
Configuring IPv6 VPN over MPLS
Starting with Cisco IOS Release 12.2(33)SCF, the Cisco CMTS routers support the IPv6 VPN over MPLS (6VPE) feature. Implementing this feature includes the following configuration tasks.
•
•
•
•
•
•
•
•
For detailed information about these tasks, see the Implementing IPv6 VPN over MPLS chapter in the Cisco IOS IPv6 Configuration Guide, Release 12.2SR at:
http://www.cisco.com/en/US/docs/ios-xml/ios/ipv6/configuration/12-2sr/ip6-ov-mpls-6vpe.html
For detailed information about the configuration examples, see "Configuration Examples for IPv6 on Cable" section.
Note
Configuring DHCPv6 Relay Agent
Starting with Cisco IOS Release 12.2(33)SCE5, the Cisco CMTS router supports DHCPv6 relay agent to forward relay-forward messages from a specific source address to client relay destinations.
Perform the steps given below to enable the DHCPv6 relay agent function and specify relay destination addresses on an interface.
Prerequisites
The relay-forward messages should contain specific source IPv6 address. This is required because the firewall deployed between the Cisco CMTS DHCPv6 relay agent and the DHCPv6 server expects only one source address for one Cisco CMTS bundle interface.
Restrictions
If you change one or more parameters of the ipv6 dhcp relay destination command, you have to disable the command using the no form, and execute the command again with changed parameters.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Disabling IPv6 ND Gleaning
You must disable IPv6 ND gleaning before configuring IPv6 source verification using DHCPv6 leasequery.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
How to Verify IPv6 Dual Stack CPE Support on the CMTS
This section describes how to use show commands to verify the configuration of the IPv6 Dual Stack CPE Support on the CMTS feature in Cisco IOS Release 12.2(33)SCC.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Examples
Use the show cable modem ipv6 command to display the IPv6 portion of a dual stack CPE and use the show cable modem cpe command to display the IPv4 mode of a dual stack CPE. Both show cable modem ipv6 registered and show cable modem registered commands display CPE count as one for a dual stack CPE.
The following example shows the output of the show cable modem ipv6 command:
Router# show cable modem ipv6 registeredInterface Prim Online CPE IP Address MAC AddressSid StateC4/0/U2 1 online 0 --- 0019.474a.c18cC4/0/U2 3 online(pt) 1 2001:420:3800:809:EDA4:350C:2F75:4779 0019.474a.c14aRouter# show cable modem 0019.474a.c14a ipv6 cpeMAC Address IP Address Domain Name0005.0052.2c1d 2001:420:3800:809:48F7:3C33:B774:9185Starting from Cisco IOS Release 12.2(33)SCG1, the output of the show cable modem ipv6 command for keyword cpe is changed.
The following example shows the output of the show cable modem ipv6 command:
Router# show cable modem 0023.bed9.4c8e ipv6 cpeLoad for five secs: 0%/0%; one minute: 1%; five minutes: 1%Time source is hardware calendar, *06:37:20.439 UTC Thu Aug 2 2012MAC Address IP Address0023.bed9.4c91 2001:40:3:4:200:5EB7:BB6:C7592001:40:3:4:210:D73B:7A50:2D05The following example shows the output of the show cable modem registered command:
Router# show cable modem registeredInterface Prim Online Timing Rec QoS CPE IP address MAC addressSid State Offset PowerC4/0/U2 3 online 1022 0.00 2 1 50.3.37.12 0019.474a.c14aThe following example shows the output of the show cable modem cpe command:
Router# show cable modem 0019.474a.c14a cpeIP address MAC address Dual IP50.3.37.3 0005.0052.2c1d Y
Configuration Examples for IPv6 on Cable
This section includes the following examples:
•
•
•
•
•
•
•
IPv6 over Subinterfaces Example:
The following example shows the CMTS bundle configuration that can be used with subinterfaces:
Router# show cable modem ipv6Device Type: B - CM Bridge, R - CM RouterIP Assignment Method: D - DHCPMAC Address Type Interface Mac State D/IP IP Address0019.474a.c18c B/D C4/0/U2 online Y 2001:420:3800:809:4C7A:D518:91C6:8A18Router# show run interface bundle2Building configuration...Current configuration : 138 bytes!interface Bundle2no ip addresscable arp filter request-send 3 2cable arp filter reply-accept 3 2no cable ip-multicast-echoendRouter# show run interface bundle2.1Building configuration...Current configuration : 382 bytes!interface Bundle2.1ip address 50.3.37.1 255.255.255.0no cable ip-multicast-echocable helper-address 10.10.0.12ipv6 address 2001:DB8::/32ipv6 enableipv6 nd prefix default no-advertiseipv6 nd managed-config-flagipv6 nd other-config-flagipv6 nd ra interval msec 2000ipv6 dhcp relay destination 2001:420:3800:800:203:BAFF:FE11:B644arp timeout 240endBasic 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:DB8::1/48) behind a cable router to an IPv6 host on the network (with destination address 2001:DB8::5/64):
configure terminal!! Specify the filter group criteria using a common group ID!cable filter group 254 index 128 v6-src-address 2001:DB8::1cable filter group 254 index 128 v6-src-pfxlen 128cable filter group 254 index 128 v6-dest-address 2001:DB8::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 254Complete Cable Configuration with IPv6 Example:
The following example shows a complete cable configuration example; it also displays the configuration of multiple cable filter groups using both IPv4 and IPv6 and separate indexes to associate the filter definitions with the same group ID.
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:DB8::/32ipv6 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:DB8::/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!endBGP Configuration for 6VPE Example:
The following example shows a sample BGP configuration on CMTS 6VPE.
Router# router bgp 1no synchronizationbgp log-neighbor-changesneighbor 11.1.1.5 remote-as 1neighbor 11.1.1.5 update-source Loopback1no auto-summary!address-family vpnv6 --- Enable vpnv6 AFneighbor 11.1.1.5 activate --- Activate neighbor 6VPE-2neighbor 11.1.1.5 send-community extendedexit-address-family!address-family ipv6 vrf vrf_mgmtredistribute connected ---- Publish directly connected routeredistribute staticno synchronizationexit-address-family!address-family ipv6 vrf vrfa --- Enable IPv6 vrf AF for each VRFredistribute connectedno synchronizationexit-address-family!address-family ipv6 vrf vrfb --- Enable IPv6 vrf AF for each VRFredistribute connectedno synchronizationexit-address-family!Subinterface Configuration for 6VPE Example:
The following example shows how to define a subinterface on virtual bundle interface 1.
When configuring IPv6 VPNs, you must configure the first subinterface created as a part of the management VRF. In the following example, Bundle 1.10 is the first sub-interface, which is configured into management VRF. Make sure the CNR server is reachable in management VRF.
interface Bundle1.10 --- Management VRFvrf forwarding vrf_mgmtcable dhcp-giaddr primaryipv6 address 2001:40:3:110::1/64ipv6 enableipv6 nd managed-config-flagipv6 nd other-config-flagipv6 dhcp relay destination 2001:10:74:129::2interface Bundle1.11 --- VRF Avrf forwarding vrfacable dhcp-giaddr primaryipv6 address 2001:40:3:111::1/64ipv6 enableipv6 dhcp relay destination 2001:10:74:129::2interface Bundle1.12 --- VRFBvrf forwarding vrfbcable dhcp-giaddr primaryipv6 address 2001:40:3:112::1/64ipv6 enableipv6 dhcp relay destination 2001:10:74:129::2Cable Interface Bundling Example:
The following example shows how to bundle a group of physical interfaces.
int C5/0/4 and int c5/0/3 are bundled.int c5/0/4cable bundle 1int c5/0/3cable bundle 1VRF Configuration for 6VPE Example:
The following example shows how to create VRFs for each VPN.
vrf definition vrf_mgmtrd 1:1!address-family ipv4route-target export 1:1route-target import 1:1route-target import 2:2route-target import 2:1exit-address-family!address-family ipv6route-target export 1:1route-target import 1:1route-target import 2:1 -- import route of vrfaroute-target import 2:2 -- import route of vrfbexit-address-familyVerifying IPv6 on Cable
This section explains how to verify IPv6 on cable configuration and it contains the following topics:
•
•
•
•
Verifying IPv6 VRF Configuration
To verify the IPv6 VRF configuration, use the show vrf ipv6 command in privileged EXEC mode.
Router# show vrf ipv6 vrfaName Default RD Protocols Interfacesvrfa 2:1 ipv4,ipv6 Bu1.11Router# show vrf ipv6 interfacesInterface VRF Protocol AddressBu1.10 vrf_mgmt up 2001:40:3:110::1Fa0/0/0 vrf_mgmt up 2001:20:4:1::38Bu1.11 vrfa up 2001:40:3:111::1Bu1.12 vrfb up 2001:40:3:112::1CMTS#Verifying IPv6 BGP Status
To verify the IPv6 BGP status, use the show ip bgp command in privileged EXEC mode.
Router# show ip bgp vpnv6 unicast all neighborsBGP neighbor is 11.1.1.5, remote AS 1, internal linkBGP version 4, remote router ID 11.1.1.5Session state = Established, up for 00:35:52Last read 00:00:37, last write 00:00:14, hold time is 180, keepalive interval is 60 secondsBGP multisession with 2 sessions (2 established), first up for 00:40:07Neighbor sessions:2 active, is multisession capableNeighbor capabilities:Route refresh: advertised and received(new) on session 1, 2Address family IPv4 Unicast: advertised and receivedAddress family VPNv6 Unicast: advertised and received......Verifying MPLS Forwarding Table
To verify the output of the MPLS forwarding table, use the show mpls forwarding-table command in the privileged EXEC mode.
Router# show mpls forwarding-tableLocal Outgoing Prefix Bytes Label Outgoing Next HopLabel Label or VC or Tunnel Id Switched interface......19 No Label 2001:40:3:110::/64[V] \ ---Route in vrf_mgmt0 aggregate/vrf_mgmt21 No Label 2001:40:3:111::/64[V] \ ---Route in vrfa0 aggregate/vrfa22 No Label 2001:40:3:112::/64[V] \ ---Route in vrfb0 aggregate/vrfb......Verifying IPv6 Cable Modem and its Host State
To verify IPv6 addresses and connected host states of cable modems and CPEs, use the show interface cable modem command in the privileged EXEC mode:
Router# show interface cable 7/0/0 modem ipv6SID Type State IPv6 Address M MAC address11 CM online 2001:420:3800:809:3519:5F9C:B96A:D31 D 0025.2e2d.743a11 CPE unknown 2001:420:3800:809:3DB2:8A6C:115F:41D8 D 0011.2544.f33bVerifying Multiple IAPDs in a Single Advertise
To verify the multiple IPv6 prefixes assigned to devices on a network, use the show cable modem ipv6 prefix command in privileged EXEC mode:
Router# show cable modem ipv6 prefixLoad for five secs: 1%/0%; one minute: 1%; five minutes: 1%Time source is hardware calendar, *06:36:53.075 UTC Thu Aug 2 2012Device Type: B - CM Bridge, R - CM RouterIP Assignment Method: D - DHCPMAC Address Type IPv6 prefix0023.bed9.4c91 R/D 2001:40:1012::/64R/D 2001:40:2012:1::/640000.002e.074c R/D 2001:40:1012:8::/64R/D 2001:40:2012:1D::/640000.002e.074b R/D 2001:40:1012:23::/64R/D 2001:40:2012:1C::/640000.002e.074a R/D 2001:40:1012:22::/64R/D 2001:40:2012:1B::/64To verify the multiple IPv6 prefixes assigned to CPEs behind a CM with a specific MAC address, use the show cable modem mac-address ipv6 prefix command in privileged EXEC mode:
Router# show cable modem 0023.bed9.4c8e ipv6 prefixLoad for five secs: 0%/0%; one minute: 1%; five minutes: 1%Time source is hardware calendar, *06:37:22.335 UTC Thu Aug 2 2012Device Type: B - CM Bridge, R - CM RouterIP Assignment Method: D - DHCPMAC Address Type IPv6 prefix0023.bed9.4c91 R/D 2001:40:1012::/64R/D 2001:40:2012:1::/64To verify the IPv6 information of CPEs behind a CM with a specific MAC address, use the show cable modem mac-address ipv6 cpe command in privileged EXEC mode:
Router# show cable modem 0023.bed9.4c8e ipv6 cpeLoad for five secs: 0%/0%; one minute: 1%; five minutes: 1%Time source is hardware calendar, *06:37:20.439 UTC Thu Aug 2 2012MAC Address IP Address0023.bed9.4c91 2001:40:3:4:200:5EB7:BB6:C7592001:40:3:4:210:D73B:7A50:2D05Additional References
The following sections provide references related to the IPv6 on Cable feature.
Related Documents
Standards
CM-SP-MULPIv3.0-I04-070518
DOCSIS 3.0 MAC and Upper Layer Protocols Interface Specification
CM-SP-MULPIv3.0-I15-110210
DOCSIS 3.0 MAC and Upper Layer Protocols Interface Specification
MIBs
RFCs
Technical Assistance
Feature Information for IPv6 on Cable
Table 2 lists the features in this module and provides links to specific configuration information.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which 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 2 Feature Information for 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:
•
•
•
•
•
•
•
•
12.2(33)SCA
The following modified commands are supported:
•
•
•
•
•
•
•
•
12.2(33)SCA
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
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:
•
•
•
•
•
12.2(33)SCA
•
•
•
•
•
•
•
•
IPv6 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:
•
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 address-MD-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:
•
Syslog 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 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:
•
•
IPv6 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: 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 section of the "Implementing IPv6 Addressing and Basic Connectivity" chapter of the Cisco IOS IPv6 Configuration Library provides 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 provides information about this feature.
ICMPv6
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:
•
•
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 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:
•
•
•
•
•
•
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:
•
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:
•
•
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: 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:
•
IPv6 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 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 section of the "Implementing IPv6 Addressing and Basic Connectivity" chapter of the Cisco IOS IPv6 Configuration Library provides information about this feature:
IPv6 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:
•
•
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:
•
•
IPv6 Routing: Multiprotocol BGP Extensions 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:
•
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:
•
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
Platform-Independent Cisco IOS Software Documentation
The following sections of the "Implementing OSPF for IPv6" chapter of the Cisco IOS IPv6 Configuration Library provide 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:
•
•
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:
•
•
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: 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 provides 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 provides 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 provides 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:
•
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:
•
•
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 provide information about this feature:
•
•
•
•
•
IPv6 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:
•
•
Platform-Specific Documentation for the Cisco CMTS Routers
For information about configuring IPv6 switching on the Cisco CMTS routers, see the "Configuring DHCPv6 Relay Agent" section.
IPv6 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 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:
•
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 Guide provide information about this feature:
•
IPv6 Dual Stack CPE Support on the CMTS
12.2(33)SCC
Cisco IOS Release 12.2(33)SCC introduced this feature on the Cisco CMTS routers.
The following sections provide information about this feature:
•
•
IPv6 over Subinterfaces
12.2(33)SCC
Cisco IOS Release 12.2(33)SCC introduced this feature on the Cisco CMTS routers.
The following sections provide information about this feature:
•
IPv6 ND Gleaning
12.2(33)SCC
The IPv6 ND Gleaning feature enables Cisco CMTS routers to automatically recover lost IPv6 CPE addresses. This feature is configured by default on routers.
The cable nd command was introduced to support this feature.
The following sections provide information about this feature:
•
IPv6 Support on Multiple Subinterfaces
12.2(33)SCB10
Starting with Cisco IOS Release 12.2(33)SCB10, IPv6 commands are supported on multiple CMTS bundle subinterfaces.
IPv6 HA
12.2(33)SCE
Cisco IOS Release 12.2(33)SCE introduced this feature on the Cisco CMTS routers.
IPv6 Access Services: DHCPv6 Prefix Delegation
12.2(33)SCE3
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 Guide provide information about this feature:
•
•
•
IPv6: 6PE & 6VPE
12.2(33)SCF
The Multiprotocol Label Switching (MPLS) virtual private network (VPN) feature represents an implementation of the provider edge (PE)-based VPN model. The 6VPE feature allows Service Providers to provide an IPv6 VPN service that does not require an upgrade or reconfiguration of the PE routers in the IPv4 MPLS core.
The following sections provide information about this feature:
•
IPv6 CPE Router Support on the Cisco CMTS
12.2(33)SCF
The IPv6 CPE router is a node for home or small office use that connects the end-user network to a service provider network.
The following section provides information about this feature:
•
The following commands were introduced or modified:
•
•
Support for IPv6 Prefix Stability on the Cisco CMTS
12.2(33)SCF1
The IPv6 prefix stability on the Cisco CMTS allows an IPv6 home router to move from one Cisco CMTS to another while retaining the same prefix.
The following section provides information about this feature:
Configurable DHCPv6 Relay Address
12.2(33)SCE5
The Cisco CMTS router supports the DHCPv6 relay agent to send relay-forward messages from a specific source address to client relay destinations.
The following sections provide information about this feature:
Platform-Specific Documentation for the Cisco CMTS Routers
•
•
The ipv6 dhcp relay destination command was modified for this feature.
Platform-Independent Cisco IOS Software Documentation
The following section of the "Implementing DHCP for IPv6" chapter of the Cisco IOS IPv6 Configuration Guide provides more information about this feature.
DHCPv6 with Full 6VPE Support
12.2(33)SCF4
Starting with Cisco IOS Release 12.2(33)SCF4, the following capabilities are supported by IPv6 on the Cisco CMTS routers:
•
•
•
The following commands were modified:
•
•
Platform-Independent Cisco IOS Software Documentation
For more information on the modified commands, see Cisco IOS IPv6 Command Reference.
Multiple IAPDs in a Single Advertise
12.2(33)SCG1
The Multiple IAPDs in a Single Advertise feature supports assignment of multiple IA_NAs and IAPDs for a CPE in a single advertise.
The output of the show cable modem ipv6 command was modified to support this feature.
The following sections provide more information about this feature:
•
•
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
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-2012 Cisco Systems, Inc. All rights reserved.
