From: Michael Zuo (mzuo@ixiacom.com)
Date: Sat Dec 02 2006 - 23:26:17 ART
Thanks guys,
I think my brain just stopped working. My R2 for some reason did not
receive the BSR mapping. After "clear ip pim rp", everything works
thanks
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
VirtRack.com Mailing Lists
Sent: Saturday, December 02, 2006 6:07 PM
To: ccielab@groupstudy.com
Subject: Fwd: how can this not work!?!?
From your R2 device....
Does your 'show ip pim rp' output look like:
Rack1R2#show ip pim rp
Group: 239.1.1.1, RP: 0.0.0.0
or like:
Rack1R2#show ip pim rp
Group: 239.1.1.1, RP: 1.1.1.1, v2, uptime 00:00:02, expires 00:02:31
If it looks like the first one, you probably dont have reachability to
the
RP address. The second one is a working setup:
Rack1R2#ping 239.1.1.1
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 239.1.1.1, timeout is 2 seconds:
Reply to request 0 from 150.1.12.2, 1 ms
Reply to request 0 from 2.2.2.2, 1 ms
On 12/2/06, Brian Dennis <bdennis@internetworkexpert.com> wrote:
>
> Can you send the output of the following commands from each router?
> Below each command is what I'm looking for with the command.
>
> 1) show ip route
>
> Ensure full reachability. You can also ping to be 100% sure.
>
> 2) show ip pim neighbor
>
> Verify the PIM neighbor relationship
>
> 3) show ip pim bsr-router
>
> Verify the BSR information
>
> 4) show ip pim rp mapping
>
> Verify the Group-to-RP mapping
>
> 5) show ip mroute count
>
> Look for RPF failures
>
>
> You should use a standard set of commands like these for basic
> verification.
>
> Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
> bdennis@internetworkexpert.com
>
> Internetwork Expert, Inc.
> http://www.InternetworkExpert.com <http://www.internetworkexpert.com/>
> Toll Free: 877-224-8987
> Direct: 775-745-6404 (Outside the US and Canada)
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> Michael Zuo
> Sent: Saturday, December 02, 2006 4:52 PM
> To: ccielab@groupstudy.com
> Subject: how can this not work!?!?
>
> Hi Group,
>
>
>
> i couldn't get this simple sparse mode multicast scenario working and
am
> pulling out my hair wondering why. I must've missed something simple
> and have not been able to figure out why for couple of hours. Please
> HELP!!
>
>
>
> thanks
>
>
>
>
>
> Rack1R4(config-if)#do ping 239.1.1.1 source 4.4.4.4
>
>
>
> Type escape sequence to abort.
>
> Sending 1, 100-byte ICMP Echos to 239.1.1.1, timeout is 2 seconds:
>
> Packet sent with a source address of 4.4.4.4
>
>
>
> *Mar 1 01:26:29.551: IP(0): s=150.1.14.4 (Ethernet0/0) d=239.1.1.1
> id=33, ttl=2
>
> 54, prot=1, len=114(100), mroute olist null
>
> *Mar 1 01:26:29.563: IP(0): s=4.4.4.4 (Loopback0) d=239.1.1.1 id=33,
> ttl=254, p
>
> rot=1, len=100(100), mroute olist null.
>
> Rack1R4(config-if)#
>
>
>
>
>
>
>
> R1:
>
>
>
> ip multicast-routing
>
> !
>
> interface Loopback0
>
> ip address 1.1.1.1 255.255.255.255
>
> ip pim sparse-mode
>
> !
>
> interface Ethernet0/0
>
> ip address 150.1.12.1 255.255.255.0
>
> ip pim sparse-mode
>
> no ip mroute-cache
>
> half-duplex
>
> !
>
> interface Ethernet0/1
>
> ip address 150.1.14.1 255.255.255.0
>
> ip pim sparse-mode
>
> no ip mroute-cache
>
> half-duplex
>
> !
>
> router ospf 1
>
> log-adjacency-changes
>
> network 1.1.1.1 0.0.0.0 area 0
>
> network 150.1.12.1 0.0.0.0 area 0
>
> network 150.1.14.1 0.0.0.0 area 0
>
> !
>
> !
>
> ip pim bsr-candidate Loopback0 0
>
> ip pim rp-candidate Loopback0
>
> !
>
>
>
>
>
>
>
>
>
> R2:
>
>
>
>
>
> ip multicast-routing
>
> !
>
> interface Loopback0
>
> ip address 2.2.2.2 255.255.255.255
>
> ip pim sparse-mode
>
> ip igmp join-group 239.1.1.1
>
>
>
> interface Ethernet0/0
>
> ip address 150.1.12.2 255.255.255.0
>
> ip pim sparse-mode
>
> no ip mroute-cache
>
> half-duplex
>
> end
>
>
>
> router ospf 1
>
> log-adjacency-changes
>
> network 2.2.2.2 0.0.0.0 area 0
>
> network 150.1.12.2 0.0.0.0 area 0
>
>
>
>
>
> R4:
>
>
>
> !
>
> ip multicast-routing
>
> !
>
> !
>
> interface Loopback0
>
> ip address 4.4.4.4 255.255.255.255
>
> ip pim sparse-mode
>
>
> !
>
> interface Ethernet0/0
>
> ip address 150.1.14.4 255.255.255.0
>
> ip pim sparse-mode
>
> no ip mroute-cache
>
> half-duplex
>
>
>
>
> !
>
>
>
> router ospf 1
>
> log-adjacency-changes
>
> network 4.4.4.4 0.0.0.0 area 0
>
> network 150.1.14.4 0.0.0.0 area 0
>
>
>
>
>
>
>
> !
>
>
This archive was generated by hypermail 2.1.4 : Tue Jan 02 2007 - 07:50:36 ART