JANET Multicast Beacon Server

This page is showing: Central Loss (%) - Beacons: 3

Time: Tue Sep 16 0:50:20 GB 2008 CST | Page Refresh: 60 seconds | Started: Tue Sep 16 0:49:20 GB 2008 | Beacons: 3
Target Multicast Group: 233.3.18.4 | Client-to-Client (RTP) multicast traffic on port: 10002, RTCP traffic on port: 10003
TCP unicast reports going back to the Central Server on port 10006

Central Loss | Beacon Info |

#	Hostname	IP Address	S0	S1	S2
R0	beacon.abman.net.uk	194.81.60.70	0	0	0
R1	beacon.eastman.net.uk	194.81.56.217	0	0	0
R2	yhbeaco1.yhman.net.uk	194.81.2.172	0	0	0

Central Loss | Beacon Info |

Diagnosing problems with your multicast setup | Contributed code and patches

Central Loss is the reported loss between two Beacons in the current multicast group, sent via TCP unicast back to the Central Server (in this case, "chilton.beacon.ja.net") for the group. This allows for the reporting of Beacons that might not otherwise be able to see each other via UDP multicast.

• Central_loss of 0 - 10 = Green, 10 - 30 = Yellow, 30 - 100 = Red, No data ("NA") = Gray
• R# and S# are the same Beacon. Any given cell in this table is read as "How well does Beacon R# see Beacon S#?".
  
• The dark green background in the R column shows which Beacon is generating the table you are seeing here.
  

Please share your comments, questions, bug reports, concerns, and feedback with us via the Beacon listserv. Please note this list can only be posted to by SUBSCRIBERS, in order to keep it spam-free. Non-subscriber email is automatically discarded. You can subscribe to the list by sending an email to "majordomo /at/ dast.nlanr.net", with "subscribe beacon /at/ dast.nlanr.net" (with real "at" signs, of course) in the body. This list is publicly archived at http://archive.ncsa.uiuc.edu/lists/beacon.

Another way to contact us is to use the DAST contact webform.