Lab 160 - Multicast Stub Routing

Lab 160 - Multicast Stub Routing
Di Posting Oleh : Simple Learning
Kategori :

Prerequisites: CCNP level skills.

Personal Note!
Other dimensions and universes which existence we sense, took a more tangible form a few days ago. My friend, artist, who goes by the name Valcari, seems to live in many of them at the same time. He is no longer the same person I have known for ages. Not better, not worse ... just different. Evolution?

Topology

Pic. 1 - Topology Diagram.

Note!
Routers and switches are already configured as per the topology diagram. All devices use OSPF area 0 as their routing protocol as well as multicast routing.

Task 1

R1 is to be the RP for all multicast groups. VLAN 26 clients will join the group 224.26.26.26. R4 is going to be server for the group 224.26.26.26.

Task 2
Configure R1 and R2 in such a way that they do not form PIM adjacency over Frame-Relay cloud, but IGMP join messages must be sent to R1 and the multicast traffic from from VLAN 14 should be sent via WAN connection to the clients in VLAN 26.

Solution

Task 1

R1 is to be the RP for all multicast groups. VLAN 26 clients will join the group 224.26.26.26. R4 is going to be server for the group 224.26.26.26.

R1 Configuration:

interface Loopback101
ip address 172.16.101.1 255.255.255.255
ip pim sparse-mode

interface FastEthernet0/0
ip address 10.1.14.1 255.255.255.0
ip pim sparse-mode
speed 100
full-duplex
!

interface Serial0/0.125 multipoint
ip address 10.1.125.1 255.255.255.0
ip pim dense-mode
ip ospf network point-to-multipoint
snmp trap link-status
frame-relay map ip 10.1.125.1 102
frame-relay map ip 10.1.125.5 105 broadcast
frame-relay map ip 10.1.125.2 102 broadcast
!

ip pim rp-address 172.16.101.1

R4 Configuration:

!

 interface FastEthernet0/0
 ip address 10.1.14.4 255.255.255.0
 ip pim sparse-mode
 speed 100
 full-duplex
!

ip pim rp-address 172.16.101.1

!

Note!
At this stage R1 configuration is not complete yet. I use 'dense-mode' on Serial0/0.125 interface, otherwise the multicast traffic would not be sent down to R2. In the next task, I will allow R2 to send the IGMP join-message to be sent towards R1.

Task 2

Configure R1 and R2 in such a way that they do not form PIM adjacency over Frame-Relay cloud, but IGMP join messages must be sent to R1 and the multicast traffic from from VLAN 14 should be sent via WAN connection to the clients in VLAN 26.

R1 Configuration:

!

access-list 1 deny   10.1.125.2
access-list 1 permit any
!

interface Serial0/0.125 multipoint
 ip address 10.1.125.1 255.255.255.0
 ip pim neighbor-filter 1
 ip pim dense-mode
 ip ospf network point-to-multipoint
 snmp trap link-status
 frame-relay map ip 10.1.125.1 102
 frame-relay map ip 10.1.125.5 105 broadcast
 frame-relay map ip 10.1.125.2 102 broadcast

!

Note!
The ACL will make it impossible for R2 to form PIM adjacency over FR link.

R2 Configuration:

!

interface FastEthernet0/1
 ip address 10.1.26.2 255.255.255.0
 ip pim dense-mode
 ip igmp helper-address 10.1.125.1

 ip igmp join-group 224.26.26.26
 speed 100
 full-duplex

!

interface Serial0/0
 ip address 10.1.125.2 255.255.255.0
 ip pim dense-mode
 encapsulation frame-relay
 ip ospf network point-to-multipoint
 clock rate 2000000
 frame-relay map ip 10.1.125.5 201
 frame-relay map ip 10.1.125.1 201 broadcast
 frame-relay map ip 10.1.125.2 201
 no frame-relay inverse-arp