IPv6 Bidirectional PIM
|
|||||||||||||
Contents
IPv6 Bidirectional PIMLast Updated: July 17, 2012
Bidirectional PIM allows multicast devices to keep reduced state information, as compared with unidirectional shared trees in PIM-SM. Bidirectional shared trees convey data from sources to the rendezvous point address (RPA) and distribute it from the RPA to the receivers.
Finding Feature InformationYour 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. Information About IPv6 Bidirectional PIMBidirectional PIMBidirectional PIM allows multicast devices to keep reduced state information, as compared with unidirectional shared trees in PIM-SM. Bidirectional shared trees convey data from sources to the RPA and distribute them from the RPA to the receivers. Unlike PIM-SM, bidirectional PIM does not switch over to the source tree, and there is no register encapsulation of data from the source to the RP. A single designated forwarder (DF) exists for each RPA on every link within a bidirectional PIM domain (including multiaccess and point-to-point links). The only exception is the RPL on which no DF exists. The DF is the device on the link with the best route to the RPA, which is determined by comparing MRIB-provided metrics. A DF for a given RPA forwards downstream traffic onto its link and forwards upstream traffic from its link toward the rendezvous point link (RPL). The DF performs this function for all bidirectional groups that map to the RPA. The DF on a link is also responsible for processing Join messages from downstream devices on the link as well as ensuring that packets are forwarded to local receivers discovered through a local membership mechanism such as MLD. Bidirectional PIM offers advantages when there are many moderate or low-rate sources. However, the bidirectional shared trees may have worse delay characteristics than do the source trees built in PIM-SM (depending on the topology). Only static configuration of bidirectional RPs is supported in IPv6. How to Configure IPv6 Bidirectional PIMConfiguring Bidirectional PIM and Displaying Bidirectional PIM InformationSUMMARY STEPS
DETAILED STEPS Configuration Examples for IPv6 Bidirectional PIMExample: Configuring Bidirectional PIM and Displaying Bidirectional PIM InformationThe following example displays the DF-election states: Device# show ipv6 pim df
Interface DF State Timer Metrics
Ethernet0/0 Winner 4s 8ms [120/2]
RP :200::1
Ethernet1/0 Lose 0s 0ms [inf/inf]
RP :200::1
The following example displays information on the RP: Device# show ipv6 pim df
Interface DF State Timer Metrics
Ethernet0/0 None:RP LAN 0s 0ms [inf/inf]
RP :200::1
Ethernet1/0 Winner 7s 600ms [0/0]
RP :200::1
Ethernet2/0 Winner 9s 8ms [0/0]
RP :200::1
Additional ReferencesRelated DocumentsMIBsTechnical Assistance
Feature Information for IPv6 Bidirectional PIMThe 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.
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. © 2012 Cisco Systems, Inc. All rights reserved.
|
|||||||||||||