[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MIGS Multicast 11/22/00



Here's the mtrace -- it seems to be dying at Berkeley for some reason.  Ugh.

Greg


./mtrace 169.229.12.95 banner.ecn.purdue.edu 22446
Usage: mtrace [-MUOPTWVlnpvs] [-e extra_hops] [-f first_hop] [-i if_addr]
              [-g gateway] [-m max_hops] [-q nqueries] [-r resp_dest]
              [-S statint] [-t ttl] [-w wait] source [receiver] [group]
<mtrace 169.229.12.95 banner.ecn.purdue.edu 233.0.25.2                       
Mtrace from 169.229.12.95 to 128.46.200.205 via group 233.0.25.2
Querying full reverse path... 
  0  banner.ecn.purdue.edu (128.46.200.205)
 -1  cisco1-200.ecn.purdue.edu (128.46.200.1)  PIM  thresh^ 0   [default]
 -2  cisco-tel-242.tcom.purdue.edu (128.210.242.22)  PIM/BGP4+  thresh^ 0  
Reached RP/Core
 -3  abilene.tcom.purdue.edu (192.5.40.10)  PIM/BGP4+  thresh^ 0  Reached 
RP/Core
 -4  kscy-ipls.abilene.ucaid.edu (198.32.8.5)  PIM/BGP4+  thresh^ 0  Reached 
RP/Core
 -5  dnvr-kscy.abilene.ucaid.edu (198.32.8.13)  PIM/BGP4+  thresh^ 0  Reached 
RP/Core
 -6  scrm-dnvr.abilene.ucaid.edu (198.32.8.1)  PIM/BGP4+  thresh^ 0  Reached 
RP/Core
 -7  QSV--abilene.POS.calren2.net (198.32.249.61)  PIM/BGP4+  thresh^ 64  
Reached RP/Core
 -8  BERK--SUNV.POS.calren2.net (198.32.249.13)  PIM/BGP4+  thresh^ 0  Reached 
RP/Core
 -9  pos1-0.inr-000-eva.Berkeley.EDU (128.32.0.89)  PIM  thresh^ 32  Reached 
RP/Core
-10  pos5-0-0.inr-001-eva.Berkeley.EDU (128.32.0.66)  PIM  thresh^ 0  
-11  vlan201.inr-004-eva.Berkeley.EDU (128.32.0.4)  PIM  thresh^ 0  
-12  ace.BMRC.Berkeley.EDU (169.229.12.95)
Round trip time 64 ms; total ttl of 69 required.

Waiting to accumulate statistics...* Results after 13 seconds:

  Source        Response Dest    Overall     Packet Statistics For Traffic From
169.229.12.95   224.0.1.32       Packet      169.229.12.95 To 233.0.25.2
     v       __/  rtt   96 ms     Rate       Lost/Sent = Pct  Rate
169.229.12.1   
128.32.0.4      vlan201.inr-004-eva.Berkeley.EDU 
     v     ^      ttl    2       218 pps        0/3    = --    0 pps
128.32.0.1     
128.32.0.66     pos5-0-0.inr-001-eva.Berkeley.EDU 
     v     ^      ttl    3       196 pps        0/3    = --    0 pps
128.32.0.65    
128.32.0.89     pos1-0.inr-000-eva.Berkeley.EDU Reached RP/Core
     v     ^      ttl   35       155 pps       -2/3    = --    0 pps
128.32.0.90    
198.32.249.13   BERK--SUNV.POS.calren2.net Reached RP/Core
     v     ^      ttl   35       306 pps        0/5    = --    0 pps
198.32.249.14  
198.32.249.61   QSV--abilene.POS.calren2.net Reached RP/Core
     v     ^      ttl   69       323 pps        0/5    = --    0 pps
198.32.249.62  
198.32.8.1      scrm-dnvr.abilene.ucaid.edu Reached RP/Core
     v     ^      ttl   69       451 pps        0/5    = --    0 pps
198.32.8.2     
198.32.8.13     dnvr-kscy.abilene.ucaid.edu Reached RP/Core
     v     ^      ttl   69      1983 pps        2/5    = --    0 pps
198.32.8.14    
198.32.8.5      kscy-ipls.abilene.ucaid.edu Reached RP/Core
     v     ^      ttl   69      1874 pps       -2/3    = --    0 pps
198.32.8.6     
192.5.40.10     abilene.tcom.purdue.edu Reached RP/Core
     v     ^      ttl   69       265 pps        2/5    = --    0 pps
192.5.40.9     
128.210.242.22  cisco-tel-242.tcom.purdue.edu Reached RP/Core
     v     ^      ttl   69       163 pps        0/3    = --    0 pps
128.210.242.188
128.46.200.1    cisco1-200.ecn.purdue.edu 
     v      \__   ttl   69       163 pps        ?/3            0 pps
128.46.200.205  128.46.200.53
  Receiver      Query Source

> 
> Well, it's being broadcast.  We can receive it on campus.  May be a
> multicast problem.
> 
> On Wed, 22 Nov 2000, Gregory W Cook wrote:
> 
> > Nope, no audio.  Are you sure it is going out?
> > 
> > I'll run some mtraces from here to see what the problem is.
> > 
> > Greg
> > 
> > > 
> > > I can see you in my Vat.  Are you still not getting audio?
> > > 
> > > Erik
> > > 
> > > On Wed, 22 Nov 2000, Gregory W Cook wrote:
> > > 
> > > > There is no audio for today's multicast -- anyone else having this 
problem?
> > > > 
> > > > Greg Cook
> > > > cook@purdue.edu
> > > > 
> > > 
> > 
> > Gregory W. Cook   cook@purdue.edu   http://www.ece.purdue.edu/~cook
> > 
> 

Gregory W. Cook   cook@purdue.edu   http://www.ece.purdue.edu/~cook