Got it! I've missed (twice!) task 25.4(b) --> R4(config)#ip pim rp-address 200.0.0.4
Everything works now, lesson learned! Gian Paolo On 11/apr/2010, at 00.09, Gian Paolo wrote: > Hi all, > I'm labbing Vol1 Lab 25, > > I'm having an issue with the ping from R1 and R5 to address 227.0.0.44 joined > on F0/0 of R4, the ping from R2 works. I've double-checked all the configs > and restarted the lab from scratch but I can't figure out why the ping > doesn't work. > I can ping from R1 and R5 to 226.0.0.66, the address of group joined by R6 > f0/0. > > This is the output I get on R2: > > *** ping from R1 to 226.0.0.66 > > R2# > *Mar 1 00:30:15.591: IP(0): s=200.0.0.1 (FastEthernet0/0) d=226.0.0.66 > (Serial1/0.26) id=85, ttl=254, prot=1, len=100(100), mforward > > *** ping from R1 to 227.0.0.44 > > R2# > *Mar 1 00:30:59.471: IP(0): s=200.0.0.1 (FastEthernet0/0) d=227.0.0.44 > id=86, ttl=254, prot=1, len=114(100), mroute olist null > > > *** sh ip mroute on R2 > > > R2#sh ip mroute 226.0.0.66 > IP Multicast Routing Table > Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected, > L - Local, P - Pruned, R - RP-bit set, F - Register flag, > T - SPT-bit set, J - Join SPT, M - MSDP created entry, > X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement, > U - URD, I - Received Source Specific Host Report, > Z - Multicast Tunnel, z - MDT-data group sender, > Y - Joined MDT-data group, y - Sending to MDT-data group > Outgoing interface flags: H - Hardware switched, A - Assert winner > Timers: Uptime/Expires > Interface state: Interface, Next-Hop or VCD, State/Mode > > (*, 226.0.0.66), 00:20:20/stopped, RP 200.0.0.2, flags: SP > Incoming interface: Null, RPF nbr 0.0.0.0 > Outgoing interface list: Null > > (200.0.0.1, 226.0.0.66), 00:01:35/00:02:40, flags: TA > Incoming interface: FastEthernet0/0, RPF nbr 150.50.12.1 > Outgoing interface list: > Serial1/0.26, Forward/Sparse, 00:01:35/00:02:53 > > (200.0.0.2, 226.0.0.66), 00:03:19/00:00:10, flags: T > Incoming interface: Loopback0, RPF nbr 0.0.0.0 > Outgoing interface list: > Serial1/0.26, Forward/Sparse, 00:03:19/00:03:07 > > R2#sh ip mroute 227.0.0.44 > IP Multicast Routing Table > Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected, > L - Local, P - Pruned, R - RP-bit set, F - Register flag, > T - SPT-bit set, J - Join SPT, M - MSDP created entry, > X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement, > U - URD, I - Received Source Specific Host Report, > Z - Multicast Tunnel, z - MDT-data group sender, > Y - Joined MDT-data group, y - Sending to MDT-data group > Outgoing interface flags: H - Hardware switched, A - Assert winner > Timers: Uptime/Expires > Interface state: Interface, Next-Hop or VCD, State/Mode > > (*, 227.0.0.44), 00:01:54/stopped, RP 200.0.0.2, flags: SP > Incoming interface: Null, RPF nbr 0.0.0.0 > Outgoing interface list: Null > > (200.0.0.1, 227.0.0.44), 00:01:54/00:01:05, flags: PTA > Incoming interface: FastEthernet0/0, RPF nbr 150.50.12.1 > Outgoing interface list: Null > > *** ping from R2 to 227.0.0.44 > > I don't understand why the ping from R2 works since it reports "mroute olist > null" but the packet reaches R4: > > R2#ping 227.0.0.44 > > Type escape sequence to abort. > Sending 1, 100-byte ICMP Echos to 227.0.0.44, timeout is 2 seconds: > > *Mar 1 00:41:10.599: IP(0): MAC sa=**Unknown SNPA type** (Loopback0) > *Mar 1 00:41:10.599: IP(0): IP tos=0x0, len=100, id=10, ttl=254, prot=1 > *Mar 1 00:41:10.599: IP(0): s=200.0.0.2 (Loopback0) d=227.0.0.44 id=10, > ttl=254, prot=1, len=100(100), mroute olist null > Reply to request 0 from 150.50.24.1, 92 ms > > R4# > *Mar 1 00:50:36.915: IP(0): s=200.0.0.2 (Serial0/0.24) d=227.0.0.44 > (FastEthernet0/0) id=24, ttl=254, prot=1, len=100(100), mforward > > > > > MSDP peers, BGP peers with both ipv4 and multicast address family are up. > Tried to remove ip multicast boundary acl. IP reachability is full. > > RPF on R4 is good: > > R4#sh ip rpf 200.0.0.2 > RPF information for ? (200.0.0.2) > RPF interface: Serial0/0.24 > RPF neighbor: ? (150.50.24.2) > RPF route/mask: 200.0.0.2/32 > RPF type: mbgp > RPF recursion count: 0 > Doing distance-preferred lookups across tables > R4#sh ip rpf 200.0.0.1 > RPF information for ? (200.0.0.1) > RPF interface: Serial0/0.24 > RPF neighbor: ? (150.50.24.2) > RPF route/mask: 200.0.0.1/32 > RPF type: mbgp > RPF recursion count: 0 > Doing distance-preferred lookups across tables > > > Need help to understand, thanks. > > Gian Paolo > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
