All things related to multicast

[Hans Kuhn <>]

Bill,

Can you send me your phone number. Marcos wants to call you
re: the problems with multicast.

-- 
Hans Kuhn, Academic User Services            office (541) 346-1714
University of Oregon, 237 CC                 fax    (541) 346-4397

Key fingerprint =  1E BC 32 03 AC E9 82 6C  44 4A CD 63 BB 2D 51 89

On Tue, 11 Jun 2002, Bill Owens wrote:

:    At 6:50 -0700 6/11/02, Lucy E. Lynch wrote:
:    >Bill -
:    >
:    >We'e seeing some oddities in multicast routing (inbound announcements)
:    >can you send an mtrace?
:    
:    This is from our NYC Juniper M20, which has an ATM OC-3 to CA*net 3.
:    
:    
owens@nyc-m20-0>
 ...e from-source source 192.35.169.6 group 224.2.242.11
:    Mtrace from 192.35.169.6 to 199.109.5.69 via group 224.2.242.11
:    Querying full reverse path... * *
:       0  nyc-m20-canet.nysernet.net (199.109.5.69)
:      -1  canet-nyc-m20.nysernet.net (199.109.5.70)  PIM  thresh^ 1
:      -2  c3-moncor01.canet3.net (205.189.32.177)  PIM/BGP4+  thresh^ 0 
:    Reached RP/Core
:      -3  c3-ottcor01.canet3.net (205.189.32.153)  PIM/BGP4+  thresh^ 0 
:    Reached RP/Core
:      -4  c3-torcor01.canet3.net (205.189.32.149)  PIM/BGP4+  thresh^ 0 
:    Reached RP/Core
:      -5  c3-ontgig01.canet3.net (205.189.32.209)  PIM/BGP4+  thresh^ 0 
:    Reached RP/Core
:      -6  tor-gigapop.onet.on.ca (205.211.94.234)  PIM/BGP4+  thresh^ 0
:      -7  ? (206.248.63.2)  PIM  thresh^ 0
:      -8  ? (192.35.169.6)
:    Round trip time 28 ms; total ttl of 7 required.
:    
:    Waiting to accumulate statistics...Results after 10 seconds:
:    
:       Source        Response Dest    Overall     Packet Statistics For 
Traffic From
:    192.35.169.6    199.109.5.69     Packet      192.35.169.6 To 224.2.242.11
:          v       __/  rtt   27 ms     Rate       Lost/Sent = Pct  Rate
:    192.35.169.1
:    206.248.63.2    ?
:          v     ^      ttl    2       132 pps        0/854  =  0%  85 pps
:    206.248.63.1
:    205.211.94.234  tor-gigapop.onet.on.ca
:          v     ^      ttl    3       282 pps        6/854  =  0%  85 pps
:    205.211.94.233
:    205.189.32.209  c3-ontgig01.canet3.net Reached RP/Core
:          v     ^      ttl    4       277 pps       14/848  =  1%  84 pps
:    205.189.32.210
:    205.189.32.149  c3-torcor01.canet3.net Reached RP/Core
:          v     ^      ttl    5       510 pps      -29/834  = -3%  83 pps
:    205.189.32.150
:    205.189.32.153  c3-ottcor01.canet3.net Reached RP/Core
:          v     ^      ttl    6       753 pps        0/863  =  0%  86 pps
:    205.189.32.154
:    205.189.32.177  c3-moncor01.canet3.net Reached RP/Core
:          v     ^      ttl    7     ^ 744 pps      863/863  =100%  86 pps
:    205.189.32.178
:    199.109.5.70    canet-nyc-m20.nysernet.net
:          v      \__   ttl    8                      ?/0            0 pps
:    199.109.5.69    199.109.5.69
:       Receiver      Query Source
:    
:    And here's from our local Cisco 7206:
:    
:    Mtrace from 192.35.169.6 to 199.109.5.17 via group 224.2.242.11
:    >From source (?) to destination (nnsyr-nyc-m20.nysernet.net)
:    Querying full reverse path...
:      0  nnsyr-nyc-m20.nysernet.net (199.109.5.17)
:    -1  nnsyr-nyc-m20.nysernet.net (199.109.5.17) [AS 3754] PIM Reached 
:    RP/Core [192.35.169.0/24]
:    -2  nyc-m20-nnsyr.nysernet.net (199.109.5.18) [AS 3754] PIM  
[192.35.169.0/24]
:    -3  canet-nyc-m20.nysernet.net (199.109.5.70) [AS 3754] PIM  
[192.35.169.0/24]
:    -4  c3-moncor01.canet3.net (205.189.32.177) [AS 6509] PIM/MBGP 
:    Reached RP/Core [192.35.169.0/24]
:    -5  c3-ottcor01.canet3.net (205.189.32.153) [AS 6509] PIM/MBGP 
:    Reached RP/Core [192.35.169.0/24]
:    -6  c3-torcor01.canet3.net (205.189.32.149) [AS 6509] PIM/MBGP 
:    Reached RP/Core [192.35.169.0/24]
:    -7  c3-ontgig01.canet3.net (205.189.32.209) [AS 6509] PIM/MBGP 
:    Reached RP/Core [192.35.169.0/24]
:    -8  tor-gigapop.onet.on.ca (205.211.94.234) [AS 549] PIM/MBGP 
:    [192.35.169.0/24]
:    -9  206.248.63.2 PIM  [192.35.169.0/25]
:    
:    The path looks fine to me, from either router. It appears that the 
:    loss is either on the ONet router or the connection to CA*net 3, but 
:    I never really trust mtrace to tell me that so I wanted to make sure 
:    other people were also seeing the problem. . .
:    
:    Bill.
: