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 Rosie, re: > We currently get our ldm CONDUIT feed from idd.aos.wisc.edu only, which > had problems today and we realized that a backup source would be > beneficial to our users. OK. re: > Do you have a machine we could allow our conduit servers to feed from? > > Our conduit machines are: > > pepe.ssec.wisc.edu 128.104.109.252 > fred.ssec.wisc.edu 128.104.109.245 > wilma.ssec.wisc.edu 128.104.111.51 First, it would be best to have one machine REQUEST CONDUIT from multiple upstream machines and then relay the data to your other machines. Having more than one machine REQUEST the same feed increases your inbound network bandwidth use by the number of machines making the REQUEST(s) to machines off campus. You can use idd.ssec.wisc.edu as your redundant upstream for CONDUIT. This will give you needed redundancy as idd.ssec.wisc.edu REQUESTs CONDUIT from idd.unidata.ucar.edu. You should be able to implement a feed REQUEST to idd.ssec.wisc.edu immediately since it has a blanket ALLOW for all machines in the ssec.wisc.edu domain. Please, however, consider _not_ simply configuring pepe, fred and wilma to all REQUEST CONDUIT from idd. Instead, choose one of these machines as the primary and have the other two feed from it. 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: OSX-818257 Department: Support IDD Priority: Normal Status: Closed