Prerequisites: CCNP level skills.
Topology
Pic. 1 - Topology Diagram.
Icons designed by: Andrzej Szoblik - http://www.newo.pl
Task 1
Enable EIGRP AS 100 on all routers to provide reachability between all subnets including loopbacks (172.16.10x.x/24).
Task 2
On 10.1.56.0/24 a video server has been installed. It will send traffic towards 224.5.5.5. Since almost all users will be receiving the stream use the push method to enable multicast support on all routers. Segments which do not wish to receive the video stream should prune the traffic. Verify that the multicast towards 224.5.5.5 works for the clients in 10.1.234.0/24 subnet.
Solution
Task 1
Enable EIGRP AS 100 on all routers to provide reachability between all subnets including loopbacks (172.16.10x.x/24).
R1 Configuration:
!
router eigrp 100
network 10.1.15.1 0.0.0.0
network 10.1.51.1 0.0.0.0
network 10.1.123.1 0.0.0.0
network 172.16.101.1 0.0.0.0
no auto-summary
eigrp router-id 172.16.101.1
!
network 10.1.15.1 0.0.0.0
network 10.1.51.1 0.0.0.0
network 10.1.123.1 0.0.0.0
network 172.16.101.1 0.0.0.0
no auto-summary
eigrp router-id 172.16.101.1
!
interface Serial1/0
ip address 10.1.123.1 255.255.255.0
ip pim dense-mode
encapsulation frame-relay
ip address 10.1.123.1 255.255.255.0
ip pim dense-mode
encapsulation frame-relay
no ip split-horizon eigrp 100
serial restart-delay 0
frame-relay map ip 10.1.123.2 102 broadcast
frame-relay map ip 10.1.123.3 103 broadcast
no frame-relay inverse-arp
serial restart-delay 0
frame-relay map ip 10.1.123.2 102 broadcast
frame-relay map ip 10.1.123.3 103 broadcast
no frame-relay inverse-arp
!
R2 Configuration:
!
router eigrp 100
network 10.1.123.2 0.0.0.0
network 10.1.234.2 0.0.0.0
network 172.16.102.2 0.0.0.0
no auto-summary
eigrp router-id 172.16.102.2
network 10.1.123.2 0.0.0.0
network 10.1.234.2 0.0.0.0
network 172.16.102.2 0.0.0.0
no auto-summary
eigrp router-id 172.16.102.2
!
R3 Configuration:
!
router eigrp 100
network 10.1.123.3 0.0.0.0
network 10.1.234.3 0.0.0.0
network 172.16.103.3 0.0.0.0
no auto-summary
eigrp router-id 172.16.103.3
network 10.1.123.3 0.0.0.0
network 10.1.234.3 0.0.0.0
network 172.16.103.3 0.0.0.0
no auto-summary
eigrp router-id 172.16.103.3
!
R4 Configuration:
!
router eigrp 100
network 10.1.234.4 0.0.0.0
network 172.16.104.4 0.0.0.0
no auto-summary
eigrp router-id 172.16.104.4
network 10.1.234.4 0.0.0.0
network 172.16.104.4 0.0.0.0
no auto-summary
eigrp router-id 172.16.104.4
!
R5 Configuration:
!
router eigrp 100
network 10.1.15.5 0.0.0.0
network 10.1.51.5 0.0.0.0
network 10.1.56.5 0.0.0.0
network 172.16.105.5 0.0.0.0
no auto-summary
eigrp router-id 172.16.105.5
network 10.1.15.5 0.0.0.0
network 10.1.51.5 0.0.0.0
network 10.1.56.5 0.0.0.0
network 172.16.105.5 0.0.0.0
no auto-summary
eigrp router-id 172.16.105.5
!
R6 Configuration:
!
router eigrp 100
network 10.1.56.6 0.0.0.0
network 172.16.106.6 0.0.0.0
no auto-summary
eigrp router-id 172.16.106.6
network 10.1.56.6 0.0.0.0
network 172.16.106.6 0.0.0.0
no auto-summary
eigrp router-id 172.16.106.6
!
Task 2
On 10.1.56.0/24 a video server has been installed. It will send traffic towards 224.5.5.5. Since almost all users will be receiving the stream use the push method to enable multicast support on all routers. Segments which do not wish to receive the video stream should prune the traffic. Verify that the multicast towards 224.5.5.5 works for clients in 10.1.234.0/24 subnet.
R1 Configuration:
!
ip multicast-routing
!
interface Ethernet0/0
ip address 10.1.51.1 255.255.255.0
ip pim dense-mode
!
ip address 10.1.51.1 255.255.255.0
ip pim dense-mode
!
interface Serial1/0
ip address 10.1.123.1 255.255.255.0
ip pim dense-mode
encapsulation frame-relay
ip address 10.1.123.1 255.255.255.0
ip pim dense-mode
encapsulation frame-relay
no ip split-horizon eigrp 100
serial restart-delay 0
frame-relay map ip 10.1.123.2 102 broadcast
frame-relay map ip 10.1.123.3 103 broadcast
no frame-relay inverse-arp
!
interface Serial1/1
ip address 10.1.15.1 255.255.255.0
ip pim dense-mode
serial restart-delay 0
!
serial restart-delay 0
frame-relay map ip 10.1.123.2 102 broadcast
frame-relay map ip 10.1.123.3 103 broadcast
no frame-relay inverse-arp
!
interface Serial1/1
ip address 10.1.15.1 255.255.255.0
ip pim dense-mode
serial restart-delay 0
!
R2 Configuration:
!
ip multicast-routing
!
interface Ethernet0/0
ip address 10.1.234.2 255.255.255.0
ip pim dense-mode
!
interface Ethernet0/0
ip address 10.1.234.2 255.255.255.0
ip pim dense-mode
!
interface Serial1/0
ip address 10.1.123.2 255.255.255.0
ip pim dense-mode
encapsulation frame-relay
serial restart-delay 0
frame-relay map ip 10.1.123.1 201 broadcast
frame-relay map ip 10.1.123.3 201
no frame-relay inverse-arp
ip address 10.1.123.2 255.255.255.0
ip pim dense-mode
encapsulation frame-relay
serial restart-delay 0
frame-relay map ip 10.1.123.1 201 broadcast
frame-relay map ip 10.1.123.3 201
no frame-relay inverse-arp
!
R3 Configuration:
!
ip multicast-routing
!
interface Ethernet0/0
ip address 10.1.234.3 255.255.255.0
ip pim dense-mode
ip address 10.1.234.3 255.255.255.0
ip pim dense-mode
!
interface Serial1/0
ip address 10.1.123.3 255.255.255.0
ip pim dense-mode
encapsulation frame-relay
serial restart-delay 0
frame-relay map ip 10.1.123.1 301 broadcast
frame-relay map ip 10.1.123.2 301
no frame-relay inverse-arp
ip address 10.1.123.3 255.255.255.0
ip pim dense-mode
encapsulation frame-relay
serial restart-delay 0
frame-relay map ip 10.1.123.1 301 broadcast
frame-relay map ip 10.1.123.2 301
no frame-relay inverse-arp
!
R4 Configuration:
!
ip multicast-routing
!
interface Ethernet0/0
ip address 10.1.234.4 255.255.255.0
ip pim dense-mode
ip address 10.1.234.4 255.255.255.0
ip pim dense-mode
!
R5 Configuration:
!
ip multicast-routing
!
interface Ethernet0/0
ip address 10.1.56.5 255.255.255.0
ip pim dense-mode
!
ip address 10.1.56.5 255.255.255.0
ip pim dense-mode
!
interface Ethernet0/1
ip address 10.1.51.5 255.255.255.0
ip pim dense-mode
!
ip address 10.1.51.5 255.255.255.0
ip pim dense-mode
!
interface Serial1/0
ip address 10.1.15.5 255.255.255.0
ip pim dense-mode
serial restart-delay 0
ip address 10.1.15.5 255.255.255.0
ip pim dense-mode
serial restart-delay 0
!
R6 Configuration:
!
ip multicast-routing
!
interface Ethernet0/0
ip address 10.1.56.6 255.255.255.0
ip pim dense-mode
ip address 10.1.56.6 255.255.255.0
ip pim dense-mode
!
Verification:
Pic. 2 - R1's PIM-enabled Interfaces and Neighbors.
Pic. 3 - R2's PIM-enabled Interfaces and Neighbors.
Pic. 4 - R5's PIM-enabled Interfaces and Neighbors.
I also checked 'show ip pim neighbor' on all routers to make sure the PIM neighbor relationship has been established.
In order to verify the multicast, R6 will be my server sending ping packets towards 224.5.5.5. R4 will emulate the client to verify if it receives the traffic.
R4 Configuration:
!
interface Ethernet0/0
ip address 10.1.234.4 255.255.255.0
ip pim dense-mode
ip igmp join-group 224.5.5.5
ip address 10.1.234.4 255.255.255.0
ip pim dense-mode
ip igmp join-group 224.5.5.5
!
Verification:
Pic. 5 - The multicast routing table on R4.
As expected, the client has been registered since the entry (*,G) shows in the multicast routing table. Ping from R6 towards the group should work now.
Pic. 6 - Ping Test.
One ping lost due to the path optimization. While continuous pinging from R6 the multicast routing table on R5 below:
Pic. 7 - R5's Multicast Routing Table.
Note!
RPF check is always performed based on the IGP routing protocol (here: EIGRP). STP-bit, chooses the shortest path prunning less optimal EIGRP paths.
