This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Samuel, re: > I see shu.cup.edu is in the list of culprits, but I'm not aware of any > mis-configuration on our side. Culprits? The feed tree view is not intended to indicate culprits... Here is the topology list for the NEXRAD2 feed to shu.cup.edu: http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_topo_nc?NEXRAD2+shu.cup.edu Topology for NEXRAD2 to shu.cup.edu 0 shu.cup.edu 1 ldm.meteo.psu.edu [no stats] 1 storm.plymouth.edu 2 140.90.113.165 3 205.124.249.245 [no stats] 3 164.113.226.3 [no stats] 3 216.38.80.15 [no stats] 3 216.38.95.9 [no stats] The reason that shu.cup.edu is showing up as an orphan is: - ldm.meteo.psu.edu is not reporting real time stats (it is the director for a cluster, and PSU is not reporting the stats as the director) - the NEXRAD2 feed request on storm.plymouth.edu is evidently by IP address, not fully qualified name The lack of rtstats reporting or requet by IP makes it impossible for the feed tree display routine to figure out the linkages (IP to name lookup is not done for speed). So, lots of connections look like orphans. This is nothing to worry about. Cheers, Tom **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: GGE-742484 Department: Support IDD Priority: Normal Status: Closed