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.
>From: Jeff Masters <address@hidden> >Organization: The Weather Underground, Inc. >Keywords: 200309300045.h8U0jvk1023216 IDD LDM upgrade Hi Jeff, >Tom, we are good to serve the IDD off of berry.wunderground.com, the >machine is pulling NOAAPORT data only from our SDI ingest box, so there >should be no conflict with checksums. OK. So, given that the SDI is a single channel receiver, you will only be able to serve the NWSTG data. Correct me if I am wrong. Did you ever get your NOAAPORT ingest box setup to calculate MD5 checksums that were compatible with the Unidata-operated NOAAPORT systems, or did you drop that effort and decide to simply run the SSEC SDI? Just curious... >We recently upgraded our bandwidth >to 200 Mbits/s, so we have plenty of bandwidth to support multiple >feeders. Excellent. >I currently have allow lines for: > >allow NNEXRAD|NEXRAD|FNEXRAD|UNIDATA|DIFAX stokes.metr.ou.edu >allow NNEXRAD|NEXRAD|FNEXRAD|UNIDATA|DIFAX flood.atmos.uiuc.edu >allow NNEXRAD|NEXRAD|FNEXRAD|UNIDATA|DIFAX ldm.meteo.psu.edu >allow UNIDATA|DIFAX|NNEXRAD|FNEXRAD profhorn.meteor.wisc.edu >allow UNIDATA|DIFAX|NNEXRAD|FNEXRAD cirp.met.utah.edu >allow UNIDATA|DIFAX|NNEXRAD|FNEXRAD pircsl4.agron.iastate.edu >allow UNIDATA|DIFAX|NNEXRAD|FNEXRAD vortex.esc.brockport.edu You can collapse the allows to: allow NNEXRAD|FNEXRAD|DIFAX|UNIDATA ... You could also change the allows to: allow ANY-NLDN-WSI-PCWS-GEM ... and use this for all requests. Can you add several machines: Top level IDD nodes ---------------------------- atm.geo.nsf.gov seistan.srcc.lsu.edu thelma.ucar.edu unidata2.ssec.wisc.edu Secondary IDD nodes ---------------------------- flood.atmos.uiuc.edu <- I know you already have this listed above f5.aos.wisc.edu stokes.metr.ou.edu <- I know you already have this listed above West coast sites ---------------------------- aeolus.ucsd.edu cirp.met.utah.edu <- I know you already have this listed above enso.sfsu.edu nimbus.atmo.arizona.edu rossby.met.sjsu.edu ^[a-z].*.atmos.washington.edu ^[a-z].*.ser.usu.edu Unidata machines ^[a-z].*.unidata.ucar.edu The number of machines who _will_ feed from you will be a small subset of the above. I would just like all top level inject nodes to have a certain set of allows for failover purposes. >I took out the stats job from frost.wunderground.com. Thanks for the help! Cheers, Tom >From address@hidden Mon Oct 6 12:05:50 2003 Hi Tom, On Mon, 6 Oct 2003, Unidata Support wrote: >The box puts out DDPLUS|IDS, HDS, NNEXRAD data. I've forgotten, but I >think you are correct, this all comes in on one channel, yes? re: getting your NOAPORT boxes to calculate Unidata-compatible MD5 checksums >Yes, but we got so bogged down in the number of exceptions, we gave up the >effort. We can try again if our SDI box eventually fails. We have 2 >non-SDI ingest boxes we feed our internal network with. re: collapse into allow NNEXRAD|FNEXRAD|DIFAX|UNIDATA ... >I collapsed things to the top line. I don't want to allow ANY, since we >use the EXP, FSL3, etc, feeds for our own crazy products. re: add several machines >All added and ldm restarted. >Cheers, Jeff >------------------------------------------------------------------------------ > Jeff Masters (address@hidden) ( ) > Chief Meteorologist /\ Home of the ( ) > The Weather Underground, Inc. /\ / \ /\ /\ ( ) > 300 N. Fifth Ave #240 / \/ \/ \ /\ / \ ------ > Ann Arbor, MI 48104 ______/ / \/ \_ \\\\\ > 734-994-8824 Weather Underground \`\`\ http://www.wunderground.com