If I enable sparse-mode on the loopback then I can ping. How would I resolve this if I could not enable PIM on the loopback?
r3(config-if)#int lo0 r3(config-if)#ip pim sparse-mode r3(config-if)# *Jan 16 13:01:22.665: %PIM-5-DRCHG: DR change from neighbor 0.0.0.0 to 3.3.3.3 on interface Loopback0do ping 224.32.32.32 Type escape sequence to abort. Sending 1, 100-byte ICMP Echos to 224.32.32.32, timeout is 2 seconds: . r3(config-if)#do ping 224.32.32.32 Type escape sequence to abort. Sending 1, 100-byte ICMP Echos to 224.32.32.32, timeout is 2 seconds: Reply to request 0 from 3.3.3.3, 4 m On Thu, Aug 20, 2009 at 12:38 AM, Mark Matters <[email protected]> wrote: > I took the ip pim dr off the interfaces. > > r1 > ip multicast-routing > interface Loopback0 > ip address 1.1.1.1 255.255.255.0 > ! > interface FastEthernet0/0 > ip address 10.1.1.1 255.255.255.0 > ip pim sparse-mode > > interface Serial0/0 > no ip address > encapsulation frame-relay > no frame-relay inverse-arp > ! > interface Serial0/0.123 multipoint > ip address 150.1.123.1 255.255.255.0 > ip pim sparse-mode > ip ospf network point-to-multipoint non-broadcast > ip ospf priority 0 > snmp trap link-status > frame-relay map ip 150.1.123.1 102 > frame-relay map ip 150.1.123.2 102 broadcast > frame-relay map ip 150.1.123.3 102 > > interface FastEthernet0/1 > ip address 100.100.100.1 255.255.255.0 > ip pim sparse-mode > > router ospf 1 > log-adjacency-changes > network 0.0.0.0 255.255.255.255 area 123 > ! > > ip pim autorp listener > > > > > r1(config-if)#do sh ip pim int > > Address Interface Ver/ Nbr Query DR DR > Mode Count Intvl Prior > 10.1.1.1 FastEthernet0/0 v2/S 0 30 1 > 10.1.1.1 > 100.100.100.1 FastEthernet0/1 v2/S 0 30 1 > 100.100.100.1 > 150.1.123.1 Serial0/0.123 v2/S 1 30 1 > 150.1.123.2 > r1(config-if)# > r1(config-if)# > r1(config-if)# > r1(config-if)# > r1(config-if)# > r1(config-if)#do sh ip pim nei > PIM Neighbor Table > Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority, > S - State Refresh Capable > Neighbor Interface Uptime/Expires Ver DR > Address > Prio/Mode > 150.1.123.2 Serial0/0.123 00:49:31/00:01:30 v2 1 / DR S > r1(config-if)# > r1(config-if)# > r1(config-if)# > r1(config-if)# > r1(config-if)# > r1(config-if)# > r1(config-if)#do sh ip pim rp > Group: 224.24.24.24, RP: 2.2.2.2, v2, v1, uptime 00:48:44, expires 00:02:01 > r1(config-if)# > r1(config-if)# > r1(config-if)# > r1(config-if)#do sh ip pim rp map > PIM Group-to-RP Mappings > > Group(s) 224.24.24.24/32 > RP 2.2.2.2 (?), v2v1 > Info source: 2.2.2.2 (?), elected via Auto-RP > Uptime: 00:48:49, expires: 00:02:54 > Group(s) 224.32.32.32/32 > RP 2.2.2.2 (?), v2v1 > Info source: 2.2.2.2 (?), elected via Auto-RP > Uptime: 00:49:07, expires: 00:02:39 > r1(config-if)# > r1(config-if)# > r1(config-if)# > r1(config-if)# > r1(config-if)# > r1(config-if)#do sh ip pim auto > AutoRP Information: > AutoRP is enabled. > AutoRP groups over sparse mode interface is enabled > > PIM AutoRP Statistics: Sent/Received > RP Announce: 0/0, RP Discovery: 0/50 > r1(config-if)# > r1(config-if)# > r1(config-if)# > r1(config-if)#do sh ip igmp gr > IGMP Connected Group Membership > Group Address Interface Uptime Expires Last Reporter > Group Accounted > 224.0.1.39 Serial0/0.123 00:51:03 00:02:40 150.1.123.2 > > 224.0.1.40 Serial0/0.123 00:51:05 00:02:21 150.1.123.1 > > r1(config-if)# > r1(config-if)# > > > > > > > > > > > r2 > ip multicast-routing > > interface Loopback0 > ip address 2.2.2.2 255.255.255.0 > ip pim sparse-mode > ! > interface FastEthernet0/0 > ip address 20.20.20.2 255.255.255.0 > duplex auto > speed auto > ! > interface Serial0/0 > ip address 150.1.123.2 255.255.255.0 > ip pim nbma-mode > ip pim sparse-mode > encapsulation frame-relay > ip ospf network point-to-multipoint non-broadcast > ip ospf priority 255 > no dce-terminal-timing-enable > frame-relay map ip 150.1.123.1 201 broadcast > frame-relay map ip 150.1.123.2 201 > frame-relay map ip 150.1.123.3 203 broadcast > no frame-relay inverse-arp > router ospf 1 > log-adjacency-changes > network 0.0.0.0 255.255.255.255 area 123 > neighbor 150.1.123.3 > neighbor 150.1.123.1 > > ip pim autorp listener > ip pim send-rp-announce Loopback0 scope 16 group-list 1 > ip pim send-rp-discovery Loopback0 scope 16 > ! > access-list 1 permit 224.32.32.32 > access-list 1 permit 224.24.24.24 > > > > r2(config-if)#do sh ip pim int > > Address Interface Ver/ Nbr Query DR DR > Mode Count Intvl Prior > 2.2.2.2 Loopback0 v2/S 0 30 1 > 2.2.2.2 > 150.1.123.2 Serial0/0 v2/S 2 30 1 > 150.1.123.3 > r2(config-if)# > r2(config-if)# > r2(config-if)# > r2(config-if)# > r2(config-if)# > r2(config-if)#do sh ip pim nei > PIM Neighbor Table > Neighbor Interface Uptime/Expires Ver DR > Address > Prio/Mode > 150.1.123.1 Serial0/0 00:49:31/00:01:31 v2 1 / S > 150.1.123.3 Serial0/0 00:53:40/00:01:18 v2 1 / DR S > r2(config-if)# > r2(config-if)# > r2(config-if)# > r2(config-if)# > r2(config-if)# > r2(config-if)# > r2(config-if)#do sh ip pim rp > Group: 224.24.24.24, RP: 2.2.2.2, v2, v1, next RP-reachable in 00:01:05 > Group: 224.32.32.32, RP: 2.2.2.2, v2, v1, next RP-reachable in 00:01:05 > r2(config-if)# > r2(config-if)# > r2(config-if)# > r2(config-if)#do sh ip pim rp map > PIM Group-to-RP Mappings > This system is an RP (Auto-RP) > This system is an RP-mapping agent (Loopback0) > > Group(s) 224.24.24.24/32 > RP 2.2.2.2 (?), v2v1 > Info source: 2.2.2.2 (?), elected via Auto-RP > Uptime: 00:57:43, expires: 00:02:16 > Group(s) 224.32.32.32/32 > RP 2.2.2.2 (?), v2v1 > Info source: 2.2.2.2 (?), elected via Auto-RP > Uptime: 00:58:01, expires: 00:02:55 > r2(config-if)# > r2(config-if)# > r2(config-if)# > r2(config-if)# > r2(config-if)# > r2(config-if)#do sh ip pim auto > AutoRP Information: > AutoRP is enabled. > AutoRP groups over sparse mode interface is enabled > > PIM AutoRP Statistics: Sent/Received > RP Announce: 120/59, RP Discovery: 118/0 > r2(config-if)# > r2(config-if)# > r2(config-if)# > r2(config-if)#do sh ip igmp gr > IGMP Connected Group Membership > Group Address Interface Uptime Expires Last Reporter > 224.0.1.39 Serial0/0 00:59:52 00:02:40 150.1.123.2 > 224.0.1.39 Loopback0 00:59:52 00:02:54 2.2.2.2 > 224.0.1.40 Serial0/0 00:51:05 00:02:43 150.1.123.3 > 224.0.1.40 Loopback0 01:01:41 00:02:46 2.2.2.2 > r2(config-if)# > r2(config-if)# > > > > > > > > r3 > > ip multicast-routing > interface Loopback0 > ip address 3.3.3.3 255.255.255.0 > > > interface Serial0/0 > ip address 150.1.123.3 255.255.255.0 > ip pim sparse-mode > encapsulation frame-relay > ip ospf network point-to-multipoint non-broadcast > ip ospf priority 0 > frame-relay map ip 150.1.123.1 301 > frame-relay map ip 150.1.123.2 301 broadcast > frame-relay map ip 150.1.123.3 301 > no frame-relay inverse-arp > ! > interface FastEthernet0/1 > ip address 30.30.30.3 255.255.255.0 > ip pim sparse-mode > ip igmp join-group 224.24.24.24 > ip igmp join-group 224.32.32.32 > duplex auto > speed auto > ! > router ospf 1 > log-adjacency-changes > network 0.0.0.0 255.255.255.255 area 123 > > ip pim autorp listener > > > r3(config-if)#do sh ip pim int > > Address Interface Ver/ Nbr Query DR DR > Mode Count Intvl Prior > 150.1.123.3 Serial0/0 v2/S 1 30 1 > 150.1.123.3 > 30.30.30.3 FastEthernet0/1 v2/S 0 30 1 > 30.30.30.3 > r3(config-if)# > r3(config-if)# > r3(config-if)# > r3(config-if)# > r3(config-if)# > r3(config-if)#do sh ip pim nei > PIM Neighbor Table > Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority, > S - State Refresh Capable > Neighbor Interface Uptime/Expires Ver DR > Address > Prio/Mode > 150.1.123.2 Serial0/0 00:53:40/00:01:30 v2 1 / S > r3(config-if)# > r3(config-if)# > r3(config-if)# > r3(config-if)# > r3(config-if)# > r3(config-if)# > r3(config-if)#do sh ip pim rp > Group: 224.24.24.24, RP: 2.2.2.2, v2, uptime 00:52:40, expires 00:01:59 > Group: 224.32.32.32, RP: 2.2.2.2, v2, v1, uptime 00:52:40, expires 00:01:59 > r3(config-if)# > r3(config-if)# > r3(config-if)# > r3(config-if)#do sh ip pim rp map > PIM Group-to-RP Mappings > > Group(s) 224.24.24.24/32 > RP 2.2.2.2 (?), v2v1 > Info source: 2.2.2.2 (?), elected via Auto-RP > Uptime: 00:52:45, expires: 00:02:54 > Group(s) 224.32.32.32/32 > RP 2.2.2.2 (?), v2v1 > Info source: 2.2.2.2 (?), elected via Auto-RP > Uptime: 00:53:03, expires: 00:02:37 > r3(config-if)# > r3(config-if)# > r3(config-if)# > r3(config-if)# > r3(config-if)# > r3(config-if)#do sh ip pim auto > AutoRP Information: > AutoRP is enabled. > AutoRP groups over sparse mode interface is enabled > > PIM AutoRP Statistics: Sent/Received > RP Announce: 0/0, RP Discovery: 0/54 > r3(config-if)# > r3(config-if)# > r3(config-if)# > r3(config-if)#do sh ip igmp gr > IGMP Connected Group Membership > Group Address Interface Uptime Expires Last Reporter > Group Accounted > 224.24.24.24 FastEthernet0/1 01:04:48 00:02:44 30.30.30.3 > > 224.32.32.32 FastEthernet0/1 01:04:42 00:02:43 30.30.30.3 > > 224.0.1.39 Serial0/0 00:55:10 00:02:40 150.1.123.2 > > 224.0.1.40 Serial0/0 00:50:41 00:02:43 150.1.123.3 > > r3(config-if)# > r3(config-if)# > > > > On Wed, Aug 19, 2009 at 5:12 PM, Rick Mur <[email protected]> wrote: > >> Mark, >> >> Can you also along with the information Bryan requested, check if you see >> if auto-rp converged properly? By issuing a 'show ip pim rp mapping' on each >> router. >> >> Check the RPF information available with 'show ip rpf' on R3 of the router >> that has the connectivity issues. >> >> >> -- >> Regards, >> >> Rick Mur >> CCIE2 #21946 (R&S / Service Provider) >> Juniper JNCIA-ER & JNCIA-EX >> MCSA:Messaging, MCSE >> Sr. Support Engineer – IPexpert, Inc. >> URL: http://www.IPexpert.com >> >> >> >> On 19 aug 2009, at 23:08, Bryan Bartik wrote: >> >> Mark, >> >> R3 is the one that has the joins, but you say R3 cannot ping the groups? >> Is this correct? Or did you mean R1? >> >> Also, are they any other connections between these routers? >> >> What does show ip pim mroute look like on R2 and R3 after trying to ping >> from R1? >> >> On Wed, Aug 19, 2009 at 1:54 PM, Mark Matters <[email protected]> wrote: >> >>> I have an rpf issue I am trying to resolve. >>> >>> I have 3 routers ip multicast routing, ip pim sparse, Autorp and ip pim >>> autorp listener configured. >>> >>> I can ping the igmp groups from r1 and r2 but I can not ping the groups >>> from r3. The groups are configured on r3. Looking at it again I sometimes >>> the pings will work from R1 and sometimes they do not. r3 f0/1 was saying >>> it's not an rfp interface. I added a mroute ong r3 pointing to r2 and it did >>> not do anything. I added an mroute pointing to f0/1 on r3 and it did not do >>> anything. Ip v4 pings to all interfaces work fine, so no unicast routing >>> issues. >>> >>> >>> r1, r2 and r3 and connected to each other via frame-relay. The fast >>> ethernets all go to different vlans. >>> >>> >>> r1 - >>> ip pim autorp listener >>> >>> f0/0 >>> ip pim sparse mode >>> ip pim dr-priority 0 >>> >>> f0/1 >>> ip pim sparse mode >>> ip pim dr-priority 0 >>> >>> s0/0 (fr physical) >>> ip pim sparse mode >>> ip pim dr-priority 0 >>> >>> >>> r2 - hub >>> ip pim autorp listener >>> >>> f0/0 >>> ip pim sparse mode >>> ip pim dr-priority 255 >>> >>> loop0 >>> ip pim sparse mode >>> >>> s0/0 fr hub - physical int >>> ip pim dr-priority 255 >>> ip pim nbma >>> ip pim sparse mode >>> >>> ip pim send-rp-announce Loopback0 scope 16 group-list 1 >>> ip pim send-rp-discovery Loopback0 scope 16 >>> >>> Standard IP access list 1 >>> 10 permit 224.24.24.24 >>> 20 permit 224.32.32.32 >>> >>> >>> r3 >>> ip pim autorp listener >>> >>> f0/0 >>> ip pim sparse mode >>> ip pim dr-priority 0 >>> >>> f0/1 >>> ip pim dr-priority 0 >>> ip pim sparse mode >>> igmp join 224.24.24.24 >>> igmp join 224.32.32.32 >>> >>> s0/0 (fr multipoint) >>> ip pim sparse mode >>> ip pim dr-priority 0 >>> >>> >>> Any idea's? >>> >>> _______________________________________________ >>> For more information regarding industry leading CCIE Lab training, please >>> visit www.ipexpert.com >>> >>> >> >> >> -- >> Bryan Bartik >> CCIE #23707 (R&S), CCNP >> Sr. Support Engineer - IPexpert, Inc. >> URL: http://www.IPexpert.com >> _______________________________________________ >> 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
