|
Table Of Contents
Multicast Subsecond Convergence
Prerequisites for Multicast Subsecond Convergence
Restrictions for Multicast Subsecond Convergence
Information About Multicast Subsecond Convergence
Benefits of Multicast Subsecond Convergence
Multicast Subsecond Convergence Scalability Enhancements
Topology Changes and Multicast Routing Recovery
How to Configure Multicast Subsecond Convergence
Modifying the Periodic RPF Check Interval
Configuring PIM RPF Failover Intervals
Modifying the PIM Router Query Message Interval
Verifying Multicast Subsecond Convergence Configurations
Configuration Examples for Multicast Subsecond Convergence
Example: Modifying the Periodic RPF Check Interval
Example: Configuring PIM RPF Failover Intervals
Example: Modifying the PIM Router Query Message Interval
Feature Information for Multicast Subsecond Convergence
Multicast Subsecond Convergence
First Published: July 22, 2002Last Updated: September 10, 2010The Multicast Subsecond Convergence feature comprises a comprehensive set of features and protocol enhancements that provide for improved scalability and convergence in multicast-based services. This feature set provides for the ability to scale to larger services levels and to recover multicast forwarding after service failure in subsecond time frames.
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 Multicast Subsecond Convergence" 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 Multicast Subsecond Convergence
•Restrictions for Multicast Subsecond Convergence
•Information About Multicast Subsecond Convergence
•How to Configure Multicast Subsecond Convergence
•Configuration Examples for Multicast Subsecond Convergence
•Feature Information for Multicast Subsecond Convergence
•Feature Information for Multicast Subsecond Convergence
Prerequisites for Multicast Subsecond Convergence
Service providers must have a multicast-enabled core in order to use the Cisco Multicast Subsecond Convergence feature.
Restrictions for Multicast Subsecond Convergence
Routers that use the subsecond designated router (DR) failover enhancement need to be able to process hello interval information arriving in milliseconds. Routers that are congested or do not have enough CPU cycles to process the hello interval may assume that the Protocol Independent Multicast (PIM) neighbor is disconnected, although this may not be the case.
Information About Multicast Subsecond Convergence
•Benefits of Multicast Subsecond Convergence
•Multicast Subsecond Convergence Scalability Enhancements
•Topology Changes and Multicast Routing Recovery
Benefits of Multicast Subsecond Convergence
•The scalability components improve on the efficiency of handling increases (or decreases) in service users (receivers) and service load (sources or content).
•New algorithms and processes (such as aggregated join messages, which deliver up to 1000 individual messages in a single packet) reduce the time to reach convergence by a factor of 10.
•Multicast subsecond convergence improves service availability for large multicast networks.
•Multicast users such as financial services firms and brokerages receive better quality of service (QoS), because multicast functionality is restored in a fraction of the time previously required.
Multicast Subsecond Convergence Scalability Enhancements
The Multicast Subsecond Convergence feature provides scalability enhancements that improve on the efficiency of handling increases (or decreases) in service users (receivers) and service load (sources or content). Scalability enhancements in this release include the following:
•Improved Internet Group Management Protocol (IGMP) and PIM state maintenance through new timer management techniques
•Improved scaling of the Multicast Source Discovery Protocol (MSDP) Source-Active (SA) cache
The scalability enhancements provide the following benefits:
•Increased potential PIM multicast route (mroute), IGMP, and MSDP SA cache state capacity
•Decreased CPU usage
PIM Router Query Messages
Multicast subsecond convergence allows you to send PIM router query messages (PIM hellos) every few milliseconds. The PIM hello message is used to locate neighboring PIM routers. Before the introduction of this feature, you could send the PIM hellos every few seconds. By enabling a router to send PIM hello messages more often, this feature allows the router to discover unresponsive neighbors more quickly. As a result, the router can implement failover or recovery procedures more efficiently.
Reverse Path Forwarding
Unicast Reverse Path Forwarding (RPF) helps to mitigate problems caused by the introduction of malformed or forged IP source addresses into a network by discarding IP packets that lack a verifiable IP source address. Malformed or forged source addresses can indicate denial-of-service (DoS) attacks based on source IP address spoofing.
RPF uses access control lists (ACLs) in determining whether to drop or forward data packets that have malformed or forged IP source addresses. An option in the ACL commands allows system administrators to log information about dropped or forwarded packets. Logging information about forged packets can help in uncovering information about possible network attacks.
Per-interface statistics can help system administrators quickly discover the interface serving as the entry point for an attack on the network.
RPF Checks
PIM is designed to forward IP multicast traffic using the standard unicast routing table. PIM uses the unicast routing table to decide if the source of the IP multicast packet has arrived on the optimal path from the source. This process, the RPF check, is protocol-independent because it is based on the contents of the unicast routing table and not on any particular routing protocol.
Triggered RPF Checks
Multicast subsecond convergence provides the ability to trigger a check of RPF changes for mroute states. This check is triggered by unicast routing changes. By performing a triggered RPF check, users can set the periodic RPF check to a relatively high value (for example, 10 seconds) and still fail over quickly.
The triggered RPF check enhancement reduces the time needed for service to be restored after disruption, such as for single service events (for example, in a situation with one source and one receiver) or as the service scales along any parameter (for example, many sources, many receivers, and many interfaces). This enhancement decreases in time-to-converge PIM (mroute), IGMP, and MSDP (SA cache) states.
RPF Failover
In an unstable unicast routing environment that uses triggered RPF checks, the environment could be constantly triggering RPF checks, which places a burden on the resources of the router. To avoid this problem, use the ip multicast rpf backoff command to prevent a second triggered RPF check from occurring for the length of time configured. That is, the PIM "backs off" from another triggered RPF check for a minimum amount of milliseconds as configured by the user.
If the backoff period expires without further routing table changes, PIM then scans for routing changes and accordingly establishes multicast RPF changes. However, if more routing changes occur during the backoff period, PIM doubles the backoff period to avoid overloading the router with PIM RPF changes while the routing table is still converging.
Topology Changes and Multicast Routing Recovery
The Multicast Subsecond Convergence feature set enhances both enterprise and service provider network backbones by providing almost instantaneous recovery of multicast paths after unicast routing recovery.
Because PIM relies on the unicast routing table to calculate its RPF when a change in the network topology occurs, unicast protocols first need to calculate options for the best paths for traffic, and then multicast can determine the best path.
Multicast subsecond convergence allows multicast protocol calculations to finish almost immediately after the unicast calculations are completed. As a result, multicast traffic forwarding is restored substantially faster after a topology change.
How to Configure Multicast Subsecond Convergence
This section contains the following procedures:
•Modifying the Periodic RPF Check Interval (optional)
•Configuring PIM RPF Failover Intervals (optional)
•Modifying the PIM Router Query Message Interval (optional)
•Verifying Multicast Subsecond Convergence Configurations (optional)
Modifying the Periodic RPF Check Interval
Perform this task to modify the intervals at which periodic RPF checks occur.
Restrictions
Cisco recommends that users keep the default values for the ip rpf interval command. The default values allow subsecond RPF failover. The default interval at which periodic RPF checks occur is 10 seconds.
SUMMARY STEPS
1. enable
2. configure terminal
3. ip multicast rpf interval seconds [list access-list | route-map route-map]
DETAILED STEPS
What to Do Next
Proceed to the "Configuring PIM RPF Failover Intervals" section to configure the intervals at which PIM RPF failover will be triggered by changes in the routing tables. Proceed to the "Modifying the PIM Router Query Message Interval" section to modify the interval at which IGMP host query messages are sent. Proceed to the "Verifying Multicast Subsecond Convergence Configurations" section to display information about and to verify information regarding the Multicast Subsecond Convergence feature.
Configuring PIM RPF Failover Intervals
Perform this task to configure the intervals at which PIM RPF failover will be triggered by changes in the routing tables.
Restrictions
Cisco recommends that users keep the default values for the ip multicast rpf backoff command. The default values allow subsecond RPF failover.
SUMMARY STEPS
1. enable
2. configure terminal
3. ip multicast rpf backoff minimum maximum [disable]
DETAILED STEPS
What to Do Next
Proceed to the "Modifying the PIM Router Query Message Interval" section to modify the interval at which IGMP host query messages are sent. Proceed to the "Verifying Multicast Subsecond Convergence Configurations" section to display information about and to verify information regarding the Multicast Subsecond Convergence feature.
Modifying the PIM Router Query Message Interval
Perform this task to modify the PIM router query message interval.
SUMMARY STEPS
1. enable
2. configure terminal
3. interface type slot/port
4. ip pim query-interval period [msec]
DETAILED STEPS
What to Do Next
Proceed to the "Verifying Multicast Subsecond Convergence Configurations" section to display information about and to verify information regarding the Multicast Subsecond Convergence feature.
Verifying Multicast Subsecond Convergence Configurations
Perform this task to display detailed information about and to verify information regarding the Multicast Subsecond Convergence feature.
SUMMARY STEPS
1. enable
2. show ip pim interface type number
3. show ip pim neighbor
4. show ip rpf events
DETAILED STEPS
Step 1 enable
Enables privileged EXEC mode.
Step 2 show ip pim interface type number
Use this command to display information about interfaces configured for PIM.
The following is sample output from the show ip pim interface command:
Router# show ip pim interface Ethernet 1/0Address Interface Ver/ Nbr Query DR DRMode Count Intvl Prior172.16.1.4 Ethernet1/0 v2/S 1 100 ms 1 172.16.1.4Step 3 show ip pim neighbor
Use this command to display the PIM neighbors discovered by the Cisco IOS software.
The following is sample output from the show ip pim neighbor command:
Router# show ip pim neighborPIM Neighbor TableNeighbor Interface Uptime/Expires Ver DRAddress Prio/Mode172.16.1.3 Ethernet1/0 00:03:41/250 msec v2 1 / SStep 4 show ip rpf events
Use this command to display information regarding the last 15 triggered multicast RPF check events.
The following sample output from the show ip rpf events command:
Router# show ip rpf eventsLast 15 triggered multicast RPF check eventsRPF backoff delay:500 msecRPF maximum delay:5 secDATE/TIME BACKOFF PROTOCOL EVENT RPF CHANGESMar 7 03:24:10.505 500 msec Static Route UP 0Mar 7 03:23:11.804 1000 sec BGP Route UP 3Mar 7 03:23:10.796 500 msec ISIS Route UP 0Mar 7 03:20:10.420 500 msec ISIS Route Down 3Mar 7 03:19:51.072 500 msec Static Route Down 0Mar 7 02:46:32.464 500 msec Connected Route UP 3Mar 7 02:46:24.052 500 msec Static Route Down 0Mar 7 02:46:10.200 1000 sec Connected Route UP 3Mar 7 02:46:09.060 500 msec OSPF Route UP 3Mar 7 02:46:07.416 500 msec OSPF Route Down 0Mar 7 02:45:50.423 500 msec EIGRP Route UP 3Mar 7 02:45:09.679 500 msec EIGRP Route Down 0Mar 7 02:45:06.322 500 msec EIGRP Route Down 2Mar 7 02:33:09.424 500 msec Connected Route UP 0Mar 7 02:32:28.307 500 msec BGP Route UP 3
Configuration Examples for Multicast Subsecond Convergence
This section provides the following configuration examples
•Example: Modifying the Periodic RPF Check Interval
•Example: Configuring PIM RPF Failover Intervals
•Example: Modifying the PIM Router Query Message Interval
Example: Modifying the Periodic RPF Check Interval
In the following example, the ip multicast rpf interval has been set to 10 seconds. This command does not show up in show running-config output unless the interval value has been configured to be the nondefault value.
!ip multicast-routingip multicast rpf interval 10...interface Ethernet0/0ip address 172.16.2.1 255.255.255.0...ip pim sparse-mode!Example: Configuring PIM RPF Failover Intervals
In the following example, the ip multicast rpf backoff command has been configured with a minimum backoff interval value of 100 and a maximum backoff interval value of 2500. This command does not show up in show running-config command output unless the interval value has been configured to be the nondefault value.
!ip multicast-routing...ip multicast rpf backoff 100 2500!!interface Ethernet0/0ip address 172.16.2.1 255.255.255.0...ip pim sparse-mode!Example: Modifying the PIM Router Query Message Interval
In the following example, the ip pim query-interval command has been set to 100 milliseconds. This command does not show up in show running-config command output unless the interval value has been configured to be the nondefault value.
!interface Ethernet0/0ip address 172.16.2.1 255.255.255.0ip pim query-interval 100 msecip pim sparse-modeAdditional References
Related Documents
Related Topic Document TitlePIM-SM and SSM concepts and configuration examples
"Configuring Basic IP Multicast" module
PIM-SM optimization concepts and configuration examples
"Optimizing PIM Sparse Mode in a Large IP Multicast Deployment" module
Cisco IOS IP multicast commands: complete command syntax, command mode, defaults, command history, usage guidelines, and examples
Standards
Standard TitleNo new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
RFC TitleNo new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Feature Information for Multicast Subsecond Convergence
Table 1 lists the release history for this feature.
Table 1 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 1 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.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R)
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.
© 2002-2010 Cisco Systems, Inc. All rights reserved.