The CAC for IPv6 Flows feature provides IPv6 support for Resource Reservation Protocol (RSVP). By enabling this feature, the network is made to support the complete RSVP IPv6 functionality for Call Admission Control (CAC) and Medianet.
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see
Bug Search Tool and 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 table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to
www.cisco.com/go/cfn. An account on Cisco.com is not required.
Prerequisites for CAC for IPv6 Flows
You must configure RSVP on one or more interfaces on at least two neighboring routers that share a link within the network.
Restrictions for CAC for IPv6 Flows
The RSVP functionality is not High Availability (HA) compliant; hence, the CAC for IPv6 Flows feature is noncompliant with HA.
Multiprotocol Label Switching (MPLS) virtual private network (VPN) Virtual Routing and Forwarding (VRF) instances are not supported.
Information About CAC for IPv6 Flows
The CAC for IPv6 Flows feature provides IPv6 support for RSVP, which allows, services that run RSVP as a transport protocol such as CAC, TE, mediatrace, and medianet, to be IPv6 compliant.
RSVP signaling can be initiated and terminated by the following entities:
RSVP at the endpoint
RSVP source or receiver proxy
RSVP agent or application server
RSVP proxy from the network device (router or switch)
To enable the CAC for IPv6 Flows feature, the endpoints and application servers are designed to be IPv6 systems that signal RSVP to the network.
Following are the differences between IPv4 and IPv6 flows in an RSVP network:
For general routing purposes, global IPv6 addresses are not required on all intermediate devices. Link local adddresses are used instead. However, global IPv6 addresses are required on ingress and egress interfaces.
Link local addresses are used for neighbor authentication in an IPv6 network as opposed to how global IP addresses are used in an IPv4 network.
IPv6 Support for RSVP Features
The CAC for IPv6 Flows feature extends IPv6 support to the following RSVP features:
CAC
Transport Protocol
RSVP policy support for global and interface configuration modes, except access control list (ACL) support
RSVP authentication, except ACL support
Previous hop (PHOP) overwrite in interface configuration mode
Fast Local Repair (FLR)
Ingress CAC
Flexible bandwidth
Virtual Routing and Forwarding (VRF)
RSVP reliable messaging
Flow Metadata
For more information about each of these features, see
QoS: RSVP Configuration Guide.
Enables a networking device to behave like it is receiving and processing IPv6 RSVP PATH messages from the sender or previous hop routes containing the indicated attributes.
The related
ipv6
rsvpsender-host command enables a device to simulate a host generating IPv6 RSVP PATH messages. It is used mostly for debugging and testing purposes.
Adds receivers to the RSVP database and enables a device to behave like it is receiving and processing IPv6 RSVP RESV messages.
The related
ipv6rsvpreservation-host command enables a device to simulate a host generating RSVP RESV messages. It is used mostly for debugging and testing purposes.
Step 5
end
Example:
Device(config)# end
Exits global configuration mode and returns to privileged EXEC mode.
Configuring a Static Sender for IPv6 Flows
Perform this task to configure a static sender for IPv6 flows with a VRF on a headend device, to make the device proxy an IPv6 RSVP PATH message.
Enables a networking device to simulate a host generating IPv6 RSVP PATH messages.
The optional
identity
aliasidentity alias keyword and argument pair specifies an application ID alias. The string can have as many as 64 printable characters (in the range 0x20 to 0x7E).
Note
If you use the quotation marks (" ") or a question mark (?) as part of the alias string, you must type the CTRL/V key sequence before entering the embedded " " or ? characters. The alias is never transmitted to other networking devices.
Step 4
end
Example:
Device(config)# end
Exits global configuration mode and returns to privileged EXEC mode.
Configuring a Static Receiver for IPv6 Flows
Perform this task to configure a static RSVP receiver with an application ID to make the device proxy an IPv6 RSVP RESV message containing an application ID on behalf of an RSVP-unaware receiver application.
Enables a device to simulate a host generating IPv6 RSVP RESV messages.
The optional
identityalias keyword and argument pair specifies an application ID alias. The string can have as many as 64 printable characters (in the range 0x20 to 0x7E).
Note
If you use the quotation marks (" ") or a question mark (?) as part of the alias string, you must type the CTRL/V key sequence before entering the embedded " " or ? character. The alias is never transmitted to other devices.
Note
Use the
ipv6rsvpreservation-host command if the device is the destination or the
ipv6rsvpreservation command to have the device proxy on behalf of a downstream host.
Step 4
end
Example:
Device(config)# end
Exits global configuration mode and returns to privileged EXEC mode.
Configuring a Receiver Proxy for IPv6 Flows on a Tailend Device
The optional
interface-kbps and
single-flow-kbps arguments specify the amount of bandwidth that can be allocated by RSVP flows or to a single flow, respectively. Values are from 1 to 10000000.
Note
Repeat this command for each interface on which you want to enable RSVP.
Configures an RSVP device to populate an address other than the native interface address in the PHOP address field of the hop object when forwarding a PATH message onto that interface.
Note
The source IPv6 address that you configure should be a valid local IP address.
The following example shows how to configure PHOP for IPv6 flows:
Device# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Device(config)# interface ethernet 1/0
Device(config-if)# ipv6 rsvp source address 2001:DB8::1
Device(config-if)# end
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password.
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to
www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 1
Feature Information for CAC for IPv6 Flows
Feature Name
Releases
Feature Information
CAC for IPv6 Flows
15.2(3)T
The CAC for IPv6 Flows feature provides IPv6 support for RSVP. By enabling this feature, the network is made to support the complete RSVP IPv6 functionality for CAC and Medianet.
The following commands were introduced or modified:
clear ipv6 rsvp authentication,
clear ipv6 rsvp reservation,
clear ipv6 rsvp sender,
ip rsvp bandwidth,
ip rsvp listener outbound,
ip rsvp signaling rate-limit,
ipv6 rsvp sender,
ipv6 rsvp sender-host,
ipv6 rsvp source,
ipv6 rsvp listener,
ipv6 rsvp reservation,
ipv6 rsvp reservation-host,
ipv6 rsvp transport sender-host,
show ipv6 rsvp authentication,
show ipv6 rsvp host,
show ipv6 rsvp installed,
show ipv6 rsvp listeners,
show ipv6 rsvp neighbor,
show ipv6 rsvp request,
show ipv6 signaling blockade,
show ipv6 rsvp transport sender.
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 and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.