All things related to multicast

["Marshall Eubanks" <>]

>Hi *,
>
>We have set up a beacon from the Nanog23 site to allow checking in
>advance if multicast transmission works fine (both routing and
>bandwidth). So far we could not get anything but routers into
>the Oakland conference site, so we just have a router test application
>sending empty UDP packets:
>   
>       "H.261": ~384 kbps -> 60 packets/sec at 800 bytes
>                (65.174.250.11,233.24.11.1) port 25011
Toerless;

Port 25011 ? Hope this will change before the rtp goes
up:)


>       "MPEG1": ~1 Mbps -> 160 packets/sec at 800 bytes
>                (65.174.250.12,233.24.11.2) port 25012

Received these just fine 
from=65.174.250.12 - through Sprint

multicasttech-2>show ip mbgp 65.174.250.12
BGP routing table entry for 65.174.0.0/16, version 190
Paths: (2 available, best #2)
  Advertised to non peer-group peers:
  192.168.1.2 
  145 6509 24 1239
    204.147.129.89 from 204.147.129.89 (204.147.128.136)
      Origin IGP, localpref 100, valid, external
      Community: 1572894 9503719 426576325
  1239
    160.81.38.225 from 160.81.38.225 (144.228.242.54)
      Origin IGP, metric 1, localpref 100, valid, external, best
multicasttech-2>mtrace 
Source address or name: 65.174.250.12
Destination address or name: 63.105.122.1
Group address or name: 233.24.11.2
Multicast request TTL [64]: 255
Response address for mtrace: 
Type escape sequence to abort.
Mtrace from 65.174.250.12 to 63.105.122.1 via group 233.24.11.2
>From source (?) to destination (dmz-mct2.multicasttech.com)
Querying full reverse path... 
 0  dmz-mct2.multicasttech.com (63.105.122.1)
-1  dmz-mct2.multicasttech.com (63.105.122.1) PIM/MBGP Reached RP/Core 
[65.174.0.0/16]

-2  sl-gw5-rly-9-0-0-TS19.sprintlink.net (160.81.38.225) [AS 1239] PIM/MBGP
Prune sent upstream [65.174.248.0/22]
-3  sl-bb21-rly-0-0.sprintlink.net (144.232.25.244) [AS 1239] PIM/MBGP Prune
sent upstream [65.174.248.0/22]
-4  sl-bb22-sj-5-1.sprintlink.net (144.232.9.125) [AS 1239] PIM/MBGP Prune 
sent
upstream [65.174.248.0/22]
-5  sl-bb21-stk-10-2.sprintlink.net (144.232.9.170) [AS 1239] PIM/MBGP  
[65.174.248.0/22]

-6  sl-gw28-stk-8-0.sprintlink.net (144.232.4.110) [AS 1239] PIM  
[65.174.248.0/22]

-7  sl-nanog23-0-0-0.sprintlink.net (144.223.59.18) [AS 1239] PIM  
[65.174.250.8/29]

multicasttech-2>

Could you do something for us ? Try and join one
of our streams (such as channel 1 sub stream 1 at 160 kbps;
sdp attached below. We lost multicast state
through Sprint this Tuesday and have not regained out that
interface yet - this is highly unusual, and I was
intending to complain to Jeff and company today.

I hope this is not a Sprint/MIX peering problem, as it
will be upstream of you...

Marshall

SDP file :

n=242903359 1063877134 1003468493 224.2.127.254 9875 255 trusted none none 
noauth noenc notset notset 
k=
v=0
o=- 10000000 10000 IN IP4 63.105.122.6
s=On-The-I.com Livecast 160k
i=MP3 audio See web site for start time
u=http://www.on-the-i.com/livecast

p=703-293-9601
t=3181579002 3255580622
a=type:broadcast
a=tool:msad v0.5
m=audio 7000 RTP/AVP 14
c=IN IP4 233.64.133.40/255

>       "MPEG2": ~5 Mbps -> 800 packets/sec at 800 bytes
>                (65.174.250.13,233.24.11.3) port 25013
>
> Notes:  MPEG2 transmission is targeted at 4 mbps, just the beacon
> is 20% higher to be on the safe side. Also the packet sizes
> are set lower than the typical apps will give us to be on the
> safe side of performance - if the beacon get's through without
> loss, the actual video stream would too.
>
>We'll try to let the beacon run until the conference begins, but
>no guarantees.
>
>The actual conference session info can be found on:
>    http://www.nanog.org/mtg-0110/network.html#multi
>
>Cheers
>       Toerless
>
>P.S.:
>
>
>If you don't have a favourite router or host tool to receive and
>count such void streams, then check out my own messy program in
>ftp://ftpeng.cisco.com/eckert/push (no, i do not have a windows
>binary, but yes, this is just a hack).
>
>      push -c -r 233.24.11.1 -p 25011 -m 10 &
>      push -c -r 233.24.11.2 -p 25012 -m 10 &
>      push -c -r 233.24.11.3 -p 25013 -m 10 &
>
>Should display:
>
>Received   60 pps of size  800 in  10 sec =    46.875 kbyte/sec from 
>65.174.250.11

>Received  160 pps of size  800 in  10 sec =   125.000 kbyte/sec from 
>65.174.250.12

>Received  800 pps of size  800 in  10 sec =   625.000 kbyte/sec from 
>65.174.250.13

>
>Every 10 seconds.
>
>
Marshall Eubanks