mcast over frame topology not working - I am all out of

I'm trying to determine why I'm not getting a response to a multicast
ping over a frame-relay hub (r3) and spoke (r4) when traffic is originated
from one hop away from the hub frame relay router. But I am getting it to
work when originated from the hub? I have been trying debug ip
packet and debug ip mpacket on R4 the spoke. Then I realized it would be
unicast. Right? The odd thing is that I'm seeing mpacket counts go up when
traffic is sourced from the hub R3. So wait, will it be unicast or mcast
over the pvc?

I'm not seeing a single mpacket on R4 when debuging mpacket on serial
interface when the traffic is originated from either R5 or R3. The mpacket
count only increases when traffic origniates from the hub, R3. Not at all
when originiated from R5.

I am getting ping responses to 226.6.6.6 from R4 when traffic originates on
R3, but not when originated from R5. Yes, R4 passes the rpf check for
156.2.35.5.

*Topology*

r5 - (PPPoF virtual-template) r3 , then r3 (frame relay) to both r2 and r4.
R5 originates the mcast stream to 226.6.6.6 from 156.2.35.5

I'm having a hell of a time debuging this even with an acl on "debug ip
packet." Since R3 is going to unicast this, will the source be the
originating source (for this lab R5) or does r3 change the source address?

I'm going to focus on R4 since both hubs are having the same issue.

*multicast source R5:*

R5# show int virtual-tem 35
 interface Virtual-Template35
 ip address 156.2.35.5 255.255.255.0
 ip pim dense-mode
 no peer neighbor-route

R5#sho ip pim neig
PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
      P - Proxy Capable, S - State Refresh Capable, G - GenID Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
156.2.35.3 Virtual-Access2 02:03:30/00:01:15 v2 1 / S P G

*hub R3:*

R3# show int virtual-tem 35
interface Virtual-Template35
 ip address 156.2.35.3 255.255.255.0
 ip pim dense-mode
 no peer neighbor-route

interface Serial0/0/0
 ip address 156.2.234.3 255.255.255.0
 ip load-sharing per-packet
 ip pim dense-mode
 no ip mfib forwarding output
 encapsulation frame-relay
 frame-relay map ip 156.2.234.3 304
 frame-relay map ip 156.2.234.4 304 broadcast
 frame-relay map ip 156.2.234.2 302 broadcast
 no frame-relay inverse-arp

R3#sho ip pim neig
PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
      P - Proxy Capable, S - State Refresh Capable, G - GenID Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
156.2.234.4 Serial0/0/0 02:16:42/00:01:17 v2 1 / DR S
P G
156.2.234.2 Serial0/0/0 02:16:47/00:01:44 v2 1 / S P G
156.2.35.5 Virtual-Access1 02:01:22/00:01:25 v2 1 / S P G

*Spoke R4:*

R4#sr int s 0/0/0.234
!
interface Serial0/0/0.234 point-to-point
 ip address 156.2.234.4 255.255.255.0
 ip pim dense-mode
 ip nat inside
 no ip mfib forwarding output
 ip virtual-reassembly
 frame-relay interface-dlci 4

R4#sho ip rpf 156.2.35.5
RPF information for ? (156.2.35.5)
  RPF interface: Serial0/0/0.234
  RPF neighbor: ? (156.2.234.3)
  RPF route/mask: 156.2.35.0/24
  RPF type: unicast (rip)
  Doing distance-preferred lookups across tables
  RPF topology: ipv4 multicast base, originated from ipv4 unicast base

R4#sho ip mroute
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, E - Extranet,
       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,
       V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
 Timers: Uptime/Expires
 Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 226.6.6.6), 00:00:13/00:02:46, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Serial0/0/0.234, Forward/Dense, 00:00:13/00:00:00
     Loopback104, Forward/Dense, 00:00:13/00:00:00

R4#sho ip pim neig
PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
      P - Proxy Capable, S - State Refresh Capable, G - GenID Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
156.2.234.3 Serial0/0/0.234 02:10:51/00:01:44 v2 1 / S P G

* Ping testing from R5 and the show commands on R4:*

ping from R5 - Notice that R4 doesn't register a mpacket being recieved.

R5#pin 226.6.6.6 source 156.2.35.5
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 226.6.6.6, timeout is 2 seconds:
Packet sent with a source address of 156.2.35.5
Reply to request 0 from 3.3.3.3, 72 ms

R4#sho ip mrout count
IP Multicast Statistics
2 routes using 1312 bytes of memory
2 groups, 0.00 average sources per group
Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kilobits per
second
Other counts: Total/RPF failed/Other drops(OIF-null, rate-limit etc)

Group: 226.6.6.6, Source count: 0, Packets forwarded: 0, Packets received: 0
Group: 224.0.1.40, Source count: 0, Packets forwarded: 0, Packets received:
0

* Ping testing from R3 and the show commands on R4:*

ping from R5 - Notice that R4 registers a mpacket being recieved.

 Ping from R3
R3#ping 226.6.6.6
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 226.6.6.6, timeout is 2 seconds:
Reply to request 0 from 3.3.3.3, 4 ms
Reply to request 0 from 156.2.104.1, 104 ms
Reply to request 0 from 156.2.102.1, 92 m

R4#sho ip mrout count
IP Multicast Statistics
3 routes using 1656 bytes of memory
2 groups, 0.50 average sources per group
Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kilobits per
second
Other counts: Total/RPF failed/Other drops(OIF-null, rate-limit etc)

Group: 226.6.6.6, Source count: 1, Packets forwarded: 1, Packets received: 1

  Source: 156.2.234.3/32, Forwarding: 1/0/100/0, Other: 1/0/0
Group: 224.0.1.40, Source count: 0, Packets forwarded: 0, Packets received:
0

*i'm really not sure what else to do here or how to figure out just what the
problem is. r3 and r5 are clearly pim neighbors, the mpacket clearly goes
from r5 to r3. But I don't understand what is happening after that. debug
ip mpacket on r4 does not display a sinlge mpacket (mroute-cache is turned
off on R4 ser 0/0/0.234).*

*HELP!*

-- 
r/
LG
Blogs and organic groups at http://www.ccie.net