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.
Hi Pat, re: Level II feed from Purdue > Everything is back. Very good. re: > For the sake of redundancy, please set your service to pull from both > castor.rcac.purdue.edu and pollux.rcac.purdue.edu, and ldm will > automatically switch over if there are any problems. The "accumulator" front ends to our top level IDD relay cluster, idd.unidata.ucar.edu, request redundantly from multiple sites for all datastreams. We have one accumulator requesting from pollux, and the other requesting from castor. They also request the Level II data from the MAX and IRaDS (one from the MAX, the other from IRaDS). It was because of this multiple, redundant requests that we didn't notice the problem with castor that we reported earlier today: we simply didn't know there was a problem because we continued to receive all of the data. We only noticed that castor was not available when we looked at our LDM log files. Thanks for the quick action! 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: MXE-616655 Department: Support IDD Priority: Normal Status: Closed