Section 8: Multicast (6 Points)

• Configure Multicast PIM Sparse-mode on VLAN_22 to allow multicast traffic between R3, R5, and R6. Make R6 the rendezvous point.

If you configured this correctly as shown in Example 5-43, you have scored 3 points.

Example 5-43 shows the configuration to set up the Multicast between R3, R5, and R6 with R6 as the RP of the group.

Example 5-43. R3, R5, and R6 Multicast Configuration

 R3#show run Building configuration... ! ! ip multicast-routing ! ! interface FastEthernet0/0  ip address 160.10.22.3 255.255.255.0  ip pim sparse-mode ! ! ip pim rp-address 160.10.22.6 ! ! ________________________________________________________________ R5#show run Building configuration... ! ! ip multicast-routing ! ! interface FastEthernet0/0  ip address 160.10.22.5 255.255.255.0  ip pim sparse-mode ! ! ip pim rp-address 160.10.22.6 ! ! ! ________________________________________________________________ R6#show run Building configuration... ! ! ip multicast-routing ! ! interface Ethernet0/0  ip address 160.10.22.6 255.255.255.0   ip pim sparse-mode ! R3#show ip pim rp Group: 224.0.1.40, RP: 160.10.22.6, uptime 1d01h, expires never ! ! ________________________________________________________________ R5#show ip pim rp Group: 224.0.1.40, RP: 160.10.22.6, uptime 1d01h, expires never R5# 

• Configure Multicast Routing Monitor between R3, R5, and R6 with R6 as the Manager. Make R3 the "test sender" and R5 the "test receiver."

If you configured this correctly as shown in Example 5-44, you have scored 3 points.

Example 5-44 has the configuration for Multicast Routing Monitor (MRM) on R3 and R5. The MRM feature is a management diagnostic tool that provides network fault detection and isolation in a multicast routing infrastructure. It is designed to notify a network administrator of multicast routing problems in near real time. If the Test Receiver detects an error (such as packet loss or duplicate packets), it sends an error report to the router configured as the Manager. The Manager immediately displays the error report. (Also, by issuing a certain show EXEC command, you can see the error reports, if any.) You then troubleshoot your multicast environment as normal, perhaps using the mtrace command from the source to the Test Receiver.

Example 5-44. R3, R5, and R6 MRM Configuration

 R3#sh run int fa0/0 Building configuration... Current configuration : 185 bytes ! interface FastEthernet0/0  ip address 160.10.22.3 255.255.255.0  ip pim sparse-mode  ip mrm test-sender ! ________________________________________________________________ R5#sh run int fa0/0 Building configuration... Current configuration : 187 bytes ! interface FastEthernet0/0  ip address 160.10.22.5 255.255.255.0   ip pim sparse-mode  ip mrm test-receiver  end ! ________________________________________________________________ R6#sh run | b TEST1 ip mrm manager TEST1  manager Ethernet0/0 group 239.1.1.1  senders 1  receivers 2 sender-list 1 ! ! access-list 1 permit 160.10.22.3 access-list 2 permit 160.10.22.5 ! R6# ! ________________________________________________________________ R3#sh ip mrm interface Interface                Address          Mode                  Status FastEthernet0/0          160.10.22.3      Test-Sender           Up R3# ! ________________________________________________________________ R5#sh ip mrm interface Interface                Address          Mode                  Status FastEthernet0/0          160.10.22.5      Test-Receiver         Up R5# ! ________________________________________________________________ R6#sh ip mrm manager Manager:TEST1/160.10.22.6 is not running   Beacon interval/holdtime/ttl:60/86400/32   Group:239.1.1.1, UDP port test-packet/status-report:16384/65535   Test senders:     160.10.22.3   Test receivers:     160.10.22.5