• To support embedded RP, the router configured as the RP must use a configured access-list that permits the embedded RP group ranges derived from the embedded RP address. If embedded RP support is available, only the RP must be statically configured as the RP for the embedded RP ranges – no additional configuration is required on other PIMv6 routers. The other routers will discover the RP address from the IPv6 group address. For these routers to select a static RP instead of the embedded RP, the specific embedded RP group range must be configured in the access list of the static RP, and embedded RP support must be disabled.

• If RP-address configured through BSR and RP-address configured statically are both available for a group range, the RP-address configured through BSR is chosen over statically configured RP-address.

• A single static-RP can be configured for multiple group ranges using Access Lists. However, configuring multiple static RPs (using ipv6 pim rp-address command) with the same RP address is not allowed. The static-RP can be configured either for the whole multicast group range ff00::/8 (without ACL) or for specific group ranges (using ACL).

• If multiple static-RPs are available for a group range, then one with the highest IP address is chosen.

• Only permit filters in ACL are considered as valid group ranges. The default permit filter ::/0 is converted to default multicast filter ff00::/8.

• When selecting static-RPs for a group range, the first element, with static-RP with the highest IP address is chosen.

• Group mode and RP address mappings learned through BSR take precedence over mappings statistically defined by the ipv6 pim rp-address command without the override keyword. Commands with the override keyword take precedence over dynamically learned mappings.