rp-address access list
(IPv6)
rp-address< IPv6-ADDR >[access-list
no rp-address< IPv6-ADDR >[access-list
Description
Statically configures the router as the RP and associates the static RP to the specified ACL.
Thenoform of this command removes static RP ACL configuration.
Parameter |
Description |
|---|---|
< IPv6-ADDR > |
Specifies an address in IPv6 format (xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx), where x is a hexadecimal number from 0 to F. |
access-list |
Specifies the name of the access control list. |
override |
指定是否静态RP configuration precedes the information learned by a BSR. |
Usage
The ACL includes a list of permitted/ denied group addresses for the specified RP.
- When configured on a source DR, only permitted group addresses are registered to the RP. When applied on other routers, (\*,G) PIM join/prune messages are filtered according to the applied ACL.
- Only destination group addresses in the ACEs are filtered and any other fields configured in the ACE are ignored. If only PIM (\*,G) messages need to be filtered, configureaccept-rpACLs.
- When static RP ACL is configured, only one static RP can be configured per VRF and that configured RP handles all the multicast groups in range ff00::/8.
A change in the RP ACL does not impact the flows that have already switched to SPT. Only when the source information is expired and the RP is needed to establish the multicast tree, is the change in the ACL reflected. If the source is always active, PIM can be disabled and re-enabled to clear the learned sources information and re-establish multicast trees based on the latest RP ACL configurations.
Examples
Configuring the static RP ACL:
Removing the static RP ACL configuration:
Command History
Release |
Modification |
|---|---|
10.10 |
Added optional access list parameter[access-list |
10.07 or earlier |
-- |
Command Information
Platforms |
Command context |
Authority |
|---|---|---|
8400 9300 |
config-pim |
Administrators or local user group members with execution rights for this command. |
