With 72 days to go I am studying in a slightly bizarre way but it suits my working/personal life so go figure. I am currently working 3 different lab scenarios and what I call my master lab document simultaneously. I have IEWB-SP labbed up on my home PC and from here I am posting this blog as I progress through the labs.
I have my own master lab document which is basically a word document split down the middle [Inserted table with two columns] and I document from every lab scenario I get through, the question on the left and the solutions on the right. Basically this gives me two things  the various ways of wording a question thus helping with interpretation in the lab and  the various ways to configure the same solution from different vendors.
I am also carrying around [as they are light] and studying, the NLI SP Labs simply by reading as I do not have time to lab them up but they help fill on the gaps of knowledge, take a look at their publicly available sample to see what I mean -> http://www.ccbootcamp.com/download/NLI_CCIE_SP_Lab-sample.pdf
Finally I have labbed up on my laptop, customised labs [entitled SB3 on my whiteboard] which are basically concept labs taken from CCO, Cisco Press, Soares, IEWB-SP Vol1, etc.
IEWB-SP Vol2 Lab1 Multicast:
Q. PIM:- Enable PIM on a number of interfaces to enable two routers to transport IPv4 multicast traffic, configure PIMv2 on a router so that is disseminates RP to group mappings & accepts all PIM related register messages for the multicast network.
Solution: In a nutshell, referencing the diagrams, the solution should present itself -> trace the route the packets will take getting from the source to the destination, note the interfaces listed in the table provided, identify the RP [Rendezvous Point], PIMv2 tells us BSR [Bootstrap Router]. Cross reference with CCO -> http://www.cisco.com/en/US/docs/ios/ipmulti/configuration/guide/imc_basic_cfg_ps6350_TSD_Products_Configuration_Guide_Chapter.html#wp1054362
Enable ip-multicast-routing on the relevant routers, enable ip pim sparse-mode on the interfaces listed, enable the BSR & RP via the ip pim bsr-candidate and ip pim rp-candidate commands on the router in the question. A multicast route [via ip mroute] is required to allow for RPF failure on a given route. Verification via sh ip pim nei command, noting the neighbour address and interfaces, also sh ip pim rp mapping and looking for the statements “This system is a candidate RP” and “this system is a Bootstrap Router”.
Q. Multicast over MPLS VPN’s:- Configure PIM sparse mode for a given VRF on two routers, one of which will be the RP, all multicast traffic between two routers should use admin scoped multicast address 126.96.36.199.
Solution:- First part completed with the ip pim sparse-mode command at the interface levels for the two routers and the ip multicast-routing VRF <name> command on both. Specify the RP for the VRF with the ip pim vrf <name> rp-address <ip address of interface facing the client> command. Finally we need to use MDT [Multicast Distribution Tree] to allow the multicast traffic between the two routers using the address given ->
ip vrf <name>
mdt default 188.8.131.52
This creates a tunnel across the network for the multicast traffic.
A nice treatment of MDT is available here ->
Verification, use sh ip pim mdt and sh ip mroute 184.108.40.206
Q. Multicast Testing:- When one router sends ICMP to a given 224.x.x.x address the other router sends corresponding echo-reply 192.x.x.x.
Solution:- Use the ip igmp join-group command with the specified 224.x.x.x address under the interface configured with the 192.x.x.x address thus allowing the router to accept multicast packets and respond, verification by way of ping and sh ip mroute commands .
Final Note: Internetworkexpert have a free v-seminar on Multicast here -> http://www.internetworkexpert.com/free_ccie_vseminar.htm