Cisco Catalyst 4500 Series, Software Configuration Manual

Page: 85 / 2086

1-5
Catalyst 4500 Series Switch, Cisco IOS Software Configuration Guide - Cisco IOS XE 3.9.xE and IOS 15.2(5)Ex
Chapter 1 Product Overview
Layer 2 Software Features
IPv6 Multicast BSR and BSR Scoped Zone Support
The bootstrap router (BSR) protocol for PIM-SM provides a dynamic, adaptive mechanism to
distribute group-to-RP mapping information rapidly throughout a domain. With the IPv6 BSR
feature, if an RP becomes unreachable, it will be detected and the mapping tables will be modified
so that the unreachable RP is no longer used, and the new tables will be rapidly distributed
throughout the domain.
BSR provides scoped zone support by distributing group-to-RP mappings in networks using
administratively scoped multicast. The user can configure candidate BSRs and a set of candidate
RPs for each administratively scoped region in the user's domain.
For information on BSR and BSR Scoped Zone Support, see this URL with the following caveats
related to support on a Catalyst 4500 series switch:
http://www.cisco.com/en/US/docs/ios-xml/ios/ipmulti_pim/configuration/xe-3s/ip6-mcast-bsr.html
– In the section “IPv6 BSR: Scoped Zone Support," a paragraph starts as follows:
Unless the C-RP is configured with a scope, it discovers the existence of the administratively
scoped zone and its group range through reception of a BSM from the scope zone's elected BSR
containing the scope zone's group range.
A C-RP can no longer be configured with a scope. So, the sentence should read:
A C-RP discovers the existence of the administratively scoped zone and its group range through
reception of a BSM from the scope zone's elected BSR containing the scope zone's group range.
– In the section "Configuring a BSR and Verifying BSR Information" in Step 3 under Summary
Steps and Detailed Steps, the command for configuring a C-BSR is listed as:
ipv6 pim [ vrf vrf-name ] bsr candidate bsr ipv6-address [ hash-mask-length ] [ priority
priority-value ]
Because the original syntax mistakenly excludes scope scope-value and the “new” option
( accept-rp-candidate access-list-name ) is supported with this release.
ipv6 pim [ vrf vrf-name ] bsr candidate bsr ipv6-address [ hash-mask-length ] [ priority
priority-value ] [ scope scope-value ] [ accept-rp-candidate access-list-name ]
– In the section "Sending PIM RP Advertisements to the BSR" in Step 3 under Summary and
Detailed Steps, the keyword
scope scope-value should be removed. The scope keyword no
longer exists for C-RPs.
–
In the section "Configuring BSR for Use Within Scoped Zones,” several changes apply.
The following paragraph:
If scope is specified on the candidate RP, then this device will advertise itself as C-RP only to
the BSR for the specified scope. If the group list is specified along with the scope, then only
prefixes in the access list with the same scope as that configured will be advertised.
Should read:
The candidate RP will advertise the different ranges it serves to the respective elected BSRs. If
a group list is specified, for each of the prefixes in the group list, it will verify that there is an
elected scoped BSR for the scope of the prefix. If none exists, the prefix will be announced to the
elected non-scoped BSR, provided one is present.
Note: If a prefix is not scope specific (for example, FF00::/8), it will only be announced to a
non-scoped BSR. If the candidate RP is not configured with a group list, it will behave as if a
group list with only the prefix FF00::/8 is configured.