Auto-RP uses 224.0.1.39 and 224.0.1.40 multicast groups to send
information. Auto-RP floods this information through PIM dense mode.
For auto-RP to work properly, the routers must use the ip pim sparse-dense-mode interface command. Without the dense mode capability, the RP will never be learned.
The auto-RP functionality also includes mapping agents. Mapping agents hear about RPs (via the 224.0.1.39 multicast group) and send RP-to-group mappings in a discovery statement via 224.0.1.40.
The mapping agents receive messages from candidate RPs throughout the network. The mapping agent is responsible for creating consistent multicast group-to-RP mappings and sending these announcements to all multicast routers by dense mode flooding.
To configure the router as the RP and announce so that other multicast routers can automatically learn, use the ip pim send-rp-announce source intf scope ttl-value global command. To function as a mapping agent, use the ip pim send-rp-discovery scope ttl-value global command.
In case of multiple RPs service the same group ranges. The one with the highest IP address will be selected by the MA.
R3#show run | i pim
ip pim sparse-mode
ip pim sparse-mode
ip pim sparse-mode
ip pim send-rp-announce Loopback0 scope 255
RP with Access-List
ip access-list standard R8_GROUPS
deny 224.110.110.110
permit 224.0.0.0 7.255.255.255
permit 224.0.0.0 15.255.255.255
!
ip pim send-rp-announce Loopback0 scope 10 group-list R8_GROUPS
Auto-RP - Filtering Candidate RPs
The Auto-RP mapping agent allows for the filtering of incoming RP announcements sent by RP candidates. This type of filtering applies only to Auto-RP announcements received by listening to the 224.0.1.39 multicast IP address and thus is only effective on Mapping Agents.
ip access-list standard RP_LIST
permit 150.1.10.10
!
ip access-list standard GROUP_LIST
deny 224.110.110.110
permit any
!
#ip pim rp-announce-filter rp-list RP_LIST group-list GROUP_LIST
For auto-RP to work properly, the routers must use the ip pim sparse-dense-mode interface command. Without the dense mode capability, the RP will never be learned.
The auto-RP functionality also includes mapping agents. Mapping agents hear about RPs (via the 224.0.1.39 multicast group) and send RP-to-group mappings in a discovery statement via 224.0.1.40.
The mapping agents receive messages from candidate RPs throughout the network. The mapping agent is responsible for creating consistent multicast group-to-RP mappings and sending these announcements to all multicast routers by dense mode flooding.
To configure the router as the RP and announce so that other multicast routers can automatically learn, use the ip pim send-rp-announce source intf scope ttl-value global command. To function as a mapping agent, use the ip pim send-rp-discovery scope ttl-value global command.
In case of multiple RPs service the same group ranges. The one with the highest IP address will be selected by the MA.
R3#show run | i pim
ip pim sparse-mode
ip pim sparse-mode
ip pim sparse-mode
ip pim send-rp-announce Loopback0 scope 255
RP with Access-List
ip access-list standard R8_GROUPS
deny 224.110.110.110
permit 224.0.0.0 7.255.255.255
permit 224.0.0.0 15.255.255.255
!
ip pim send-rp-announce Loopback0 scope 10 group-list R8_GROUPS
Auto-RP - Filtering Candidate RPs
The Auto-RP mapping agent allows for the filtering of incoming RP announcements sent by RP candidates. This type of filtering applies only to Auto-RP announcements received by listening to the 224.0.1.39 multicast IP address and thus is only effective on Mapping Agents.
ip access-list standard RP_LIST
permit 150.1.10.10
!
ip access-list standard GROUP_LIST
deny 224.110.110.110
permit any
!
#ip pim rp-announce-filter rp-list RP_LIST group-list GROUP_LIST
No comments:
Post a Comment