Let me load again this lab and we will clarify this. Regards,
Antonio Soares, CCIE #18473 (R&S) [email protected] _____ From: Rin [mailto:[email protected]] Sent: sábado, 20 de Junho de 2009 3:55 To: [email protected] Cc: [email protected] Subject: [OSL | CCIE_SP] VOL2 - Section 1 - Task 9.1 Antonio, Thanks a lot for your help. Sorry I made mistake when saying that I cannot ping from R2 (I messed up with other topo :P) BTW, its working right now after my third try so I suspect something wrong with Dynamips. However, in task 9.3, I face this same problem when ping 239.7.7.7 from R2. Here the output - ping is not successful: R2#ping Protocol [ip]: Target IP address: 239.7.7.7 Repeat count [1]: 5 Datagram size [100]: Timeout in seconds [2]: Extended commands [n]: y Interface [All]: loopback0 Time to live [255]: Source address: 125.125.125.2 Type of service [0]: Set DF bit in IP header? [no]: Validate reply data? [no]: Data pattern [0xABCD]: Loose, Strict, Record, Timestamp, Verbose[none]: Sweep range of sizes [n]: Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 239.7.7.7, timeout is 2 seconds: Packet sent with a source address of 125.125.125.2 Reply to request 0 from 192.168.87.7, 252 ms.... ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ - show ip mroute on R8 & R7 shows ok R7#sho ip mroute 239.7.7.7 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 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 (*, 239.7.7.7), 00:56:06/stopped, RP 6.7.8.7, flags: SJCL Incoming interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: Loopback0, Forward/Sparse-Dense, 00:56:06/00:01:53 (125.125.125.2, 239.7.7.7), 00:00:58/00:02:19, flags: LM Incoming interface: FastEthernet0/0.807, RPF nbr 192.168.87.8, Mbgp Outgoing interface list: Loopback0, Forward/Sparse-Dense, 00:00:58/00:02:01 R8#sho ip mroute 239.7.7.7 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 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 (*, 239.7.7.7), 00:01:12/stopped, RP 6.7.8.7, flags: SP Incoming interface: FastEthernet0/0.807, RPF nbr 192.168.87.7 Outgoing interface list: Null (125.125.125.2, 239.7.7.7), 00:01:12/00:02:17, flags: Incoming interface: Serial4/0.801, RPF nbr 125.8.1.1, Mbgp Outgoing interface list: FastEthernet0/0.807, Forward/Sparse-Dense, 00:01:12/00:03:25 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ - mtrace from R2 shows ok: R2#mtrace 125.125.125.2 6.7.8.7 239.7.7.7 Type escape sequence to abort. Mtrace from 125.125.125.2 to 6.7.8.7 via group 239.7.7.7 >From source (?) to destination (?) Querying full reverse path... * switching to hop-by-hop: 0 6.7.8.7 -1 * 192.168.87.7 PIM/MBGP Reached RP/Core [125.125.125.2/32] -2 * 192.168.87.8 PIM/MBGP [125.125.125.2/32] -3 * 125.8.1.1 PIM [125.125.125.2/32] -4 * 172.16.21.2 PIM Reached RP/Core [125.125.125.2/32] -5 * Route must have changed...try again ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ When I ping 239.2.2.2 from R7, it works well. R7#ping 239.2.2.2 so lo0 re 3 Type escape sequence to abort. Sending 3, 100-byte ICMP Echos to 239.2.2.2, timeout is 2 seconds: Packet sent with a source address of 6.7.8.7 Reply to request 0 from 172.16.21.2, 188 ms Reply to request 1 from 172.16.21.2, 192 ms Reply to request 2 from 172.16.21.2, 320 ms Regarding your post about Task 9.3 to add command mpls traffic-eng multicast eng, I dont think this command is necessary because we have already enabled multicast BGP between R8&R7. Thanks Rin
