wg-multicast - Re: Persistent "Prune sent upstream"
Subject: All things related to multicast
List archive
- From: Havard Eidnes <>
- To:
- Cc: ,
- Subject: Re: Persistent "Prune sent upstream"
- Date: Wed, 07 Feb 2001 23:18:22 +0100
Hi,
I've been in some off-line communication with some Cisco folks
trying to resolve this case, and the conclusions we've arrived at
are basically the following:
o Don't always trust "mtrace" output to tell you the whole
truth; instead check forwarding counts for S,G entries in your
routers. The "Prune sent upstream" appears to be an artifact
caused by a lack of traffic from the source, and is indeed not
caused by the router returning this flag.
o The problem with the missing traffic from the sources in the
accessgrid beacon group appears to lie upstream from NORDUnet;
all the traffic visible on our border router with Abilene
makes it to the recipient beacon(s) inside UNINETT.
Best regards,
- HÃ¥vard
- Persistent "Prune sent upstream", Havard Eidnes, 02/06/2001
- Re: Persistent "Prune sent upstream", Jan Novak, 02/06/2001
- Re: Persistent "Prune sent upstream", Havard Eidnes, 02/06/2001
- Re: Persistent "Prune sent upstream", Beau Williamson, 02/07/2001
- Re: Persistent "Prune sent upstream", Havard Eidnes, 02/07/2001
- Re: Persistent "Prune sent upstream", Havard Eidnes, 02/07/2001
- Re: Persistent "Prune sent upstream", Bill Fenner, 02/07/2001
- Re: Persistent "Prune sent upstream", Havard Eidnes, 02/08/2001
- Re: Persistent "Prune sent upstream", Bill Fenner, 02/08/2001
- Re: Persistent "Prune sent upstream", Havard Eidnes, 02/08/2001
- Re: Persistent "Prune sent upstream", Bill Fenner, 02/07/2001
- Re: Persistent "Prune sent upstream", Beau Williamson, 02/07/2001
- Re: Persistent "Prune sent upstream", Havard Eidnes, 02/06/2001
- Re: Persistent "Prune sent upstream", Jan Novak, 02/06/2001
Archive powered by MHonArc 2.6.16.