6 Days to go

* Mock Lab2 spoiler ahead

7pm Mock lab2 complete, made one mistake from what I can spot with the eye. Again on the same multicast question I lost marks on the first time. Requirement is for auto-rp mapping agent not to allow any other rp to group mappings. The solution is to create two mappings for the known two rp’s and then to make a third rp to group mapping denying ANY group:

ip pim rp-announce-filter rp-list NOT_R2_OR_R4 group-list NO_GROUPS
!
ip access-list standard NO_GROUPS
deny any
!
ip access-list standard NOT_R2_OR_R4
deny 150.1.2.2
deny 150.1.4.4
permit any

Starting mock lab6 now, trying to complete it by 12am which gives me 5 hours.

1:30am Mock lab6 completed. Havent gone through the answer sheet yet, will do that tomorrow. Completed in 5hours 15minutes with. Had to take a 1hour break since 7pm.

I came across the same problem I had while did the lab for real. One of the routers would respond to two multicast pings and after that timeout. I found a way to fix it but Im not sure whether I should spend time trying to find out why this fixed to problem or why to problem occured in the first place. I now know it has something to do with the topology and not the equipment. Not much time to explain this, but here is the output on the mapping agent during the first two pings (R5 is the mapping agent and also the first hop from the RP R3 where the packets are coming from, going to the destination R2 239.2.2.2 ):

Rack2R5(config-if)#
*Mar  1 04:52:55.018: MRT(0): Reset the z-flag for (176.2.35.3, 239.3.2.2)
*Mar  1 04:52:55.018: MRT(0): Set the F-flag for (176.2.35.3, 239.3.2.2)
*Mar  1 04:52:55.018: MRT(0): Create (176.2.35.3,239.3.2.2), RPF Ethernet0/1/0.0.0.0
*Mar  1 04:52:55.018: MRT(0): WAVL Insert interface: Serial0/0 in (176.2.35.3,239.3.2.2) Successful
*Mar  1 04:52:55.022: MRT(0): set min mtu for (176.2.35.3, 239.3.2.2) 0->1500
*Mar  1 04:52:55.022: MRT(0): Add Serial0/0/224.0.0.2 to the olist of (176.2.35.3, 239.3.2.2), Forward state – MAC not built
*Mar  1 04:52:55.026: IP(0): s=176.2.35.3 (Ethernet0/1) d=239.3.2.2 (Serial0/0) id=248, prot=1, len=100(100), mforward
Rack2R5(config-if)#
*Mar  1 04:52:57.166: MRT(0): Update Serial0/0/224.0.0.2 in the olist of (*, 239.3.2.2), Forward state – MAC built
*Mar  1 04:52:57.166: MRT(0): Update Serial0/0/224.0.0.2 in the olist of (176.2.35.3, 239.3.2.2), Forward state – MAC built

Ok so at this point the timeouts start. I fixed it with a “no ip mroute-cache” on the interface between the RP and Mapping agent. If I run into something similar this is one option to try, but I would like to know why this solved the problem and why it occured in the first place and why the IE solution guide does not 1) detect the problem and 2) not have a solution to it. I cant see that Im doing anything different from the rest of the solution guide, but then again it is 1:30am.