Multicast Advanced

Scenario:

In an effort to load balance various multicast responsibilities across your routers, you decide to implement Cisco's AutoRP feature along with MSDP and SSM so you can use the same IP addresses as RPs for the same multicast groups while increasing security. Only problem is, your boss tells you that you cannot use sparse-dense mode as he never wants multicast traffic to be flooded unnecessarily. Additionally, responsibilities are being distributed to all (5) backbone routers in your network.

Goal:

• Nothing has been preconfigured for you! Configure IP addresses and interface assignments in accordance with the diagram.
• Enable EIGRP on all routers and all interfaces for basic connectivity. Do NOT enable EIGRP on R1 and R7 as those devices simulate hosts. Instead, configure a default route on each one.
• Enable multicast-routing and PIM-SM on all interfaces, including loopbacks.
• Configure AutoRP on all (5) routers. R4 should be both the mapping agent and the RP using Lo0 for AutoRP's discovery group using Lo1. R5 should be the RP for AutoRP's announcement group using Lo0.
• Ensure all routers know these two RP addresses so they can receive AutoRP information.
• Configure R2 Lo0 to be the RP for 225.1.1.1 only.
• Configure R5 Lo1 to be the RP for 225.1.1.1 only.
• Configure R3 Lo0 to be the RP for 225.2.2.2 only.
• Configure R6 Lo1 to be the RP for 225.2.2.2 only.
• Configure MSDP so RPs can share appropriate RP-related information. You are only allowed to create (2) peerings.
• R7 needs to tell R6 that it wants to receive multicast traffic on groups 225.1.1.1 and 225.2.2.2. Use SSM to ensure that only multicast traffic on these groups is forwarded by R6. Do not use the "ip access-group" command or any explicit filtering mechanisms.
• R1 should be able to ping 225.1.1.1 and 225.2.2.2 and receive responses from R7.

IOS:

c3725-adventerprisek9-mz.124-7.image

Topology: