8.4 PIM Sparse-Dense Mode
• Remove the previous PIM Sparse Mode configuration and replace it with Sparse-Dense-Mode on all interfaces.
• Do not enable PIM on the Frame Relay link between R4 and R5.
• Modify the static RP assignments so that R5 is only used as the RP for groups in the range 224.0.0.0/8.
• Configure SW4’s VLAN 10 interface to join the groups 224.10.10.10 and 239.0.0.1, and ensure that R6 can send multicast packets to this segment for both groups.
-------------------------------------------------
R4:
ip access-list standard SPARSE_GROUPS
permit 224.0.0.0 0.255.255.255
!
ip multicast-routing
ip pim rp-address 150.1.5.5 SPARSE_GROUPS
!
interface FastEthernet 0/1
ip pim sparse-dense-mode
!
interface Serial 0/1/0
ip pim sparse-dense-mode
R5:
ip access-list standard SPARSE_GROUPS
permit 224.0.0.0 0.255.255.255
!
ip multicast-routing
ip pim rp-address 150.1.5.5 SPARSE_GROUPS
!
interface Serial 0/1/0
ip pim sparse-dense-mode
!
interface FastEthernet 0/0
ip pim sparse-dense-mode
!
! Needed to fix RPF check for R5’s Loopback0
!
interface Loopback0
ip ospf network point-to-point
R6:
ip access-list standard SPARSE_GROUPS
permit 224.0.0.0 0.255.255.255
!
ip multicast-routing
ip pim rp-address 150.1.5.5 SPARSE_GROUPS
!
interface FastEthernet 0/0.146
ip pim sparse-dense-mode
SW2:
ip multicast-routing distributed
ip access-list standard SPARSE_GROUPS
permit 224.0.0.0 0.255.255.255
!
ip pim rp-address 150.1.5.5 SPARSE_GROUPS
!
interface Vlan 58
ip pim sparse-dense-mode
!
interface Port-Channel1
ip pim sparse-dense-mode
SW4:
ip access-list standard SPARSE_GROUPS
permit 224.0.0.0 0.255.255.255
!
ip multicast-routing
ip pim rp-address 150.1.5.5 SPARSE_GROUPS
!
interface Port-Channel1
ip pim sparse-dense-mode
!
interface Vlan 10
ip igmp join-group 224.10.10.10
ip igmp join-group 239.0.0.1
ip pim sparse-dense-mode
-------------------------------------------------
First, ping the group that has no RP from R6. Notice that all routers on the path to the receiver create (S,G) dense state entries. There is also a corresponding (*,G) state as well, but it has an RP value of 0.0.0.0 and has all PIM-enabled interfaces listed in the OIL.
Rack1R6#ping 239.0.0.1 repeat 100 - 變成是(*,G) - Dense mode
Now, again from R6, ping the group that has an RP configured. Notice that (*,G) now represents the shared tree, and is used to forward the first packets from the sources. The SPT is built by the RP and the router is connected to the receiver.
Rack1R6#show ip mroute 224.10.10.10 - 變成是(S,G) - Sparse mode
-------------------------------------------------
沒有留言:
張貼留言