From: Bruce Williams (bruce@xxxxxxxxxxxxxxxxxxxxxx)
Date: Wed Jun 19 2002 - 08:49:13 GMT-3
That is kind of what I thought is meant, but it does not make sense as to
why. The router that this debug message came (R1) from has a loopback
interface in this multicast group and it also has a PIM neighbor (R2) on
it's point to multipoint frame-relay serial interface s1/0.123 and R2 also
has a loopback in this group and a neighbor in this group. I corrected the
RPF issue with a static mroute and I am still receiving this message. There
is another router connected to R1's multipoint interface of (R3) which is
not a multicast router. When I shut down R3's serial interface everything
works fine so that leads me to believe that this non multicast router is
sending a prune message to R1 and therefore R1 is pruning that entire
multipoint interface. I added the PIM nbma-mode command and still no
success. Is there anything else that I can do.
Bruce
-----Original Message-----
From: Chris Hugo [mailto:chrishugo@yahoo.com]
Sent: Wednesday, June 19, 2002 5:39 AM
To: Bruce Williams; Ccielab@Groupstudy. Com
Subject: Re: debug ip mpacket
hi,
A source node with a ip address of 172.16.35.5 on your network is sending
multicast packets to a multicast group address of 232.2.2.2. Source
interface of the multicast packets is Serial1/0.14.The router is also
pruning back packets for this particular multicast group because all packets
that are being received from Serial1/0.14 are being sent straight to your
bit-bucket (null).
hth,
chris hugo
Bruce Williams <bruce@williamsnetworking.com> wrote:
Can someone tell me what this debug output from the debug ip mpacket
means:
2d10h: IP: s=172.16.35.5 (Serial1/0.14) d=232.2.2.2 len 104, mroute
olist
null
Bruce
This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:37 GMT-3