All things related to multicast

["Lucy E. Lynch" <>]

don't know if this helps - but your source machine seems to
be unreachable:

98% traceroute 128.182.61.51
traceroute: Warning: Multiple interfaces found; using 128.223.142.13 @ ge0
traceroute to 128.182.61.51 (128.182.61.51), 30 hops max, 40 byte packets
 1  128.223.142.3 (128.223.142.3)  0.691 ms  0.628 ms  0.502 ms
 2  cisco7-gw.uoregon.edu (128.223.2.7)  0.529 ms  0.439 ms  0.375 ms
 3  ogig-uo.oregon-gigapop.net (198.32.163.1)  1.338 ms  2.249 ms  3.013
ms
 4  den.oregon-gigapop.net (198.32.163.14)  33.394 ms  32.230 ms  32.308
ms
 5  kscy-dnvr.abilene.ucaid.edu (198.32.8.14)  44.164 ms  43.030 ms
44.382 ms
 6  ipls-kscy.abilene.ucaid.edu (198.32.8.6)  51.814 ms  52.599 ms  53.167
ms
 7  clev-ipls.abilene.ucaid.edu (198.32.8.26)  58.726 ms  59.275 ms
61.183 ms
 8  abilene-gp.psc.net (192.88.115.122)  61.827 ms  62.211 ms  62.400 ms
 9  fear.psc.net (198.32.224.31)  63.671 ms !H  65.936 ms !H  63.814 ms !H
99% nslookup 128.182.61.51
Server:  phloem.uoregon.edu
Address:  128.223.32.35

Name:    sandoz.psc.edu
Address:  128.182.61.51

100% ping 128.182.61.51 (dies)

Can you send the announce info from your sdr cache ???

Lucy E. Lynch                           Academic User Services
Computing Center                        University of Oregon

                (541) 346-1774
Cell: (541) 912-7998                    

Key fingerprint =  2C 80 2F 8C 5F 68 37 E3  AC 16 09 F1 36 E4 61 15 

On Mon, 8 Jan 2001, Michael H. Lambert wrote:

> To update the responses I have received (thank you!):
> 
> IOS Versions:  internal router     12.1(3a)T1  [RSP2]
>                border router       12.0(12)S   [RSP4]
> 
> I changed the addresses of the RPs after verifying that the previous ones
> didn't pass RPF checks in the Abilene core.
> 
> I'm not sure how often the SDP announcement is being sent (it's being
> originated by SDR under MS Windows and exhibiting the usual black-box
> behavior of that OS).  I'm going to see if I can get some of the tools up
> under FreeBSD.
> 
> Behavior I'm seeing now:  The internal router carries the announcement for
> three minutes; it disappears for a while (hard to time); it comes back for
> another three minutes.  It's not showing up in the sa-cache on the border
> router at all.
> 
> Any more hints?
> 
> Thanks,
> 
> Michael
>