Rendezvous Point Configuration and Static RP Configuration
| Rendezvous Point Configuration and Static RP
Configuration |
| |
 |
| |
There is not a default RP and one or more must be configured using
one of the three methods. For the static case, the RP does not need to be
configured, only the leaf routers. To configure the static RP, use the global
configuration command |
| |
 |
| |
ip pim rp-address ip-address [access-list-number] [override] |
| |
 |
| |
ip-address |
| |
 |
| |
ip
address of the RP |
| |
|
 |
| |
group-access-list-number |
| |
 |
| |
Optional. Standard IP access list number, 1—100. If no access list is
used, then the RP can handle all groups. Use an access list to limit the groups
that the RP will service. |
| |
|
 |
| |
override |
| |
 |
| |
Optional. If there is a conflict between the static RP and one
configured using Auto-RP, then the static RP takes precedence. |
| |
|
 |
| |
For
example, to configure an RP that handles all groups, use |
| |
 |
| |
ip pim rp-address 172.16.1.1 |
| |
 |
| |
where 172.16.1.1 is the address of the RP. If we want the RP to only
handle a subset of multicast groups, then an access list is needed. If the RP is
to handle only group 239.252.1.1, then we would use the following
commands: |
| |
 |
| |
ip pim rp-address 172.16.1.1 1 |
| |
| |
access-list 1 permit 239.252.1.1 0.0.0.0 |
| |
 |
| |
If
the RP is to service the groups 239.252.1.0 through 239.252.1.255, then the
access list would contain |
| |
 |
| |
access-list 1 permit 239.252.1.0 0.0.0.255. | |
429 times read
|
Related news
|
| No matching news for this article |
|
Did you enjoy this article?
(total 0 votes)
|