[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDD #OSX-818257]: Conduit feed?

Hi Rosie,

> 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.


> Do you have a machine we could allow our conduit servers to feed from?
> Our conduit machines are:
> pepe.ssec.wisc.edu
> fred.ssec.wisc.edu
> wilma.ssec.wisc.edu

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.


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

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.