NLANR/DAST Beacon Webview on Wed Sep 7 17:48:04 2005

Multicast Beacon v1.1-0 This page is showing: Beacon Information

Time: Wed Sep 7 17:48:04 2005 CST | Page Refresh: 60 seconds | Started: Tue Jul 12 12:33:11 2005 | Beacons: 0
Target Multicast Group: 233.4.200.19 | 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 10004

# Hostname IP Address SSRC User OS Uptime Started Last Heard Contact Name Contact Info Contact Location Next Burst Test Next Silence Test Prev Burst Test Prev Silence Test

* Note: Started and Uptime columns assume an accurate local clock.

* Note: Beacons marked with a white number on a blue background are "Blind Beacons".

Diagnosing problems with your multicast setup | Contributed code and patches

The "RRs" column is the count of RTP Receiver Reports received from each SR during the previous interval. For any given interval, the count of reports should be approximately the same. If your Beacon's report count is much lower than the others, it means your Beacon has only recently joined the multicast If you know you Beacon has been running for some time, it may be showing router-level multicast problems, which is why the option was included in this release of the Beacon. If your Beacon is joining and leaving and joining and leaving, this it what that would look like.

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.