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.
Hello Elmer and Russell, The IP# needed to be allowed into your domain on port 388 is: Name: idd.unidata.ucar.edu Address: 128.117.140.3 I ~believe we have allows for your entire cluster, please let us know if you encounter any problems. Cheers, Jeff Weber Unidata User Support > Sorry .... I messed that up didn't I ... it either has to be all of the > systems in the 2 clusters OR the 2 outward IPs. Just adding dev4e and > prod4e won't work. > > Russell Lancaster said the following on 1/7/2008 11:48 AM: > > Has Unidata added satepsprod1e, satepsprod2e, satepsprod3e, > > satepsprod4e, satepsprod5e, satepsdev1e, satepsdev2e, satepsdev3e, > > satepsdev4e, etc. to their system? > > > > Elmer Tipton wrote: > > > >> The LDM is on port 388, the firewall was set up to pull, has been > >> reset to allow pushes. > >> > >> The way the outward facing cluster is set up you would have to use > >> satepsdev4e.nesdis.noaa.gov and satepsprod4e.nesdis.noaa.gov. > >> > >> I did try the ldmping and notifyme commands after the firewall rules > >> were redone and got exactly the same results as previously. > >> > >> > >> Unidata IDD Support said the following on 1/4/2008 2:54 PM: > >> > >>> Hi Elmer, > >>> > >>> > >>> > >>>> We are still having a problem with this that we can't seem to find a > >>>> reason for. > >>>> > >>>> When trying to do an ldmping command I get the following result: > >>>> $ ldmping idd.cise-nsf.gov > >>>> Jan 04 17:53:54 INFO: State Elapsed Port Remote_Host > >>>> rpc_stat > >>>> Jan 04 17:53:54 INFO: Resolving idd.cise-nsf.gov to 192.12.209.62 took > >>>> 0.0015 seconds > >>>> Jan 04 17:54:06 ERROR: NAMED 12.002253 0 idd.cise-nsf.gov > >>>> can't contact portmapper: RPC: Timed out > >>>> > >>>> > >>> wow, a 12 second RPC timeout, a tad skinny, but should not be the > >>> problem. > >>> > >>> 1) Are you running the LDM on port 388? If so, there should be no > >>> need to contact portmapper. > >>> > >>> 2) Do you have any firewall restrictions for incoming traffic on port > >>> 388? > >>> > >>> If yes to #1 and no to #2, we will need to dig deeper :) > >>> > >>> > >>> > >>> > >>>> When trying an notifyme command all I get is: > >>>> $ notifyme -vxl- -f FNEXRAD -h idd.cise-nsf.gov -o 3600 > >>>> Jan 04 17:58:39 notifyme[8669] NOTE: Starting Up: idd.cise-nsf.gov: > >>>> 20080104165839.704 TS_ENDT {{FNEXRAD, ".*"}} > >>>> Jan 04 17:58:39 notifyme[8669] NOTE: LDM-5 desired product-class: > >>>> 20080104165839.704 TS_ENDT {{FNEXRAD, ".*"}} > >>>> Jan 04 17:58:39 notifyme[8669] INFO: Resolving idd.cise-nsf.gov to > >>>> 192.12.209.62 took 0.001648 seconds > >>>> Jan 04 17:59:09 notifyme[8669] NOTE: exiting > >>>> > >>>> When the SATEPSDEV & SATEPSPROD clusters were set up they were made > >>>> with > >>>> one outward facing IP each. The 140.90.213.100 will resolve to > >>>> satepsdev1e.nesdis.noaa.gov, satepsdev2e.nesdis.noaa.gov, > >>>> satepsdev3e.nesdis.noaa.gov, satepsdev4e.nesdis.noaa.gov, > >>>> satepsdev5e.nesdis.noaa.gov, satepsdev6e.nesdis.noaa.gov, > >>>> satepsdev7e.nesdis.noaa.gov, satepsdev8e.nesdis.noaa.gov & > >>>> satepsdev9e.nesdis.noaa.gov, the 140.90.213.34 address will resolve to > >>>> satepsprod1e.nesdis.noaa.gov, satepsprod2e.nesdis.noaa.gov, > >>>> satepsprod3e.nesdis.noaa.gov, satepsprod4e.nesdis.noaa.gov & > >>>> satepsprod5e.nesdis.noaa.gov. > >>>> > >>>> Do you use the numeric IP or the resolved satepsprod1e.nesdis.noaa.gov > >>>> version? > >>>> > >>>> > >>>> > >>> The resolved satepsprod1e.nesdis.noaa.gov, we ~can feed to IP, just > >>> need to configure that way. > >>> > >>> > >>> > >>> > >>>> Another question has come up, that is probably available somewhere that > >>>> I haven't been able to find. When there is a data set available is it > >>>> pushed from your end or pulled from this end? I had always been > >>>> told we > >>>> pulled when the point was brought up here. > >>>> > >>>> > >>> Nope, the LDM is "push" technology, once the product hits our queue > >>> it is sent out to all requesters. > >>> > >>> > >>> > >>> > >>>> Thanks for any light you can shed on this. > >>>> > >>>> > >>>> > >>> Cheers, > >>> > >>> Jeff Weber > >>> Unidata User Support > >>> > >>> > >>> > >>> > >>> > >>> > >>>> Unidata IDD Support said the following on 1/3/2008 11:14 AM: > >>>> > >>>> > >>>>> Hi Trung, > >>>>> > >>>>> Both: > >>>>> > >>>>> SATEPSDEV4 (140.90.213.100) > >>>>> SATEPSPROD4 (140.90.213.34) > >>>>> > >>>>> ..now have access to all radar data. > >>>>> > >>>>> Cheers, > >>>>> > >>>>> Jeff > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>> Hi Jeff, > >>>>>> > >>>>>> My sysadmin has just put the following name/IP addresses in the DNS. > >>>>>> They should resolve now. > >>>>>> > >>>>>> SATEPSDEV4 (140.90.213.100) > >>>>>> SATEPSPROD4 (140.90.213.34) > >>>>>> > >>>>>> I would like to request feed site for 1km BREF radar data for the > >>>>>> above > >>>>>> IP addresses. Thanks. > >>>>>> > >>>>>> -Trung > >>>>>> > >>>>>> > >>>>>> Unidata IDD Support said the following on 12/18/2007 12:40 PM: > >>>>>> > >>>>>> > >>>>>> > >>>>>>> Trung, > >>>>>>> > >>>>>>> That IP # will work. > >>>>>>> > >>>>>>> I have an allow for: > >>>>>>> 140.90.213.159 > >>>>>>> satepsdist4e.nesdis.noaa.gov > >>>>>>> > >>>>>>> to ingest level II radar data (from any or all sites) from: > >>>>>>> > >>>>>>> idd.cise-nsf.gov > >>>>>>> > >>>>>>> Let me know if you need any further help getting the feed going. > >>>>>>> > >>>>>>> Cheers, > >>>>>>> > >>>>>>> Jeff > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>> Jeff, > >>>>>>>> > >>>>>>>> Sorry. My sysadmin gave me the wrong IP address. Please try this > >>>>>>>> one - > >>>>>>>> 140.90.213.159. Please notify me when you finish setting it up. > >>>>>>>> Thanks. > >>>>>>>> > >>>>>>>> -Trung > >>>>>>>> > >>>>>>>> Unidata IDD Support said the following on 12/17/2007 5:11 PM: > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>> Trung, > >>>>>>>>> > >>>>>>>>> 140.90.213.100 does not seem to be resolveable: > >>>>>>>>> > >>>>>>>>> (jweber) laraine:/home/jweber 4 % nslookup 140.90.213.100 > >>>>>>>>> Server: laraine.unidata.ucar.edu > >>>>>>>>> Address: 128.117.140.62 > >>>>>>>>> > >>>>>>>>> *** laraine.unidata.ucar.edu can't find 140.90.213.100: > >>>>>>>>> Non-existent host/domain > >>>>>>>>> > >>>>>>>>> The IP address needs BOTH forward and reverse DNS capabilities > >>>>>>>>> for the LDM to function correctly. Can you take care of that? I > >>>>>>>>> suspect you are hosting the machine in a noaa.gov domain > >>>>>>>>> (correct?), so once you have BOTH forward and reverse DNS, you > >>>>>>>>> should be all set. > >>>>>>>>> > >>>>>>>>> You will be feeding from: > >>>>>>>>> > >>>>>>>>> idd.cise-nsf.gov > >>>>>>>>> > >>>>>>>>> ..after you have notified me of DNS capability. > >>>>>>>>> > >>>>>>>>> Please let me know if you have any questions. > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> Cheers, > >>>>>>>>> > >>>>>>>>> Jeff > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>> We're located in the NOAA Science Center in Suitland, > >>>>>>>>>> Maryland. We run > >>>>>>>>>> LDM on a system called SATEPSDEV4 (140.90.213.100). Thank you, > >>>>>>>>>> Jeff. > >>>>>>>>>> > >>>>>>>>>> -Trung > >>>>>>>>>> > >>>>>>>>>> Unidata IDD Support said the following on 12/17/2007 2:33 PM: > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>>> Hello, > >>>>>>>>>>> > >>>>>>>>>>> Yes, we did get your initial request, apologies for the > >>>>>>>>>>> delay. All large part of the support team were out of town at > >>>>>>>>>>> the AGU and other locations. > >>>>>>>>>>> > >>>>>>>>>>> Can you please provide us with your machine name and IP # > >>>>>>>>>>> (machine running the LDM for this request) and we will dial > >>>>>>>>>>> you in quickly today. > >>>>>>>>>>> > >>>>>>>>>>> Cheers, > >>>>>>>>>>> > >>>>>>>>>>> Jeff > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>>> Hi, > >>>>>>>>>>>> > >>>>>>>>>>>> I am wondering if my ticket has been processed. I am asking > >>>>>>>>>>>> for a feed > >>>>>>>>>>>> site for 1km BREF radar data. Thanks. > >>>>>>>>>>>> > >>>>>>>>>>>> -Trung Le > >>>>>>>>>>>> > >>>>>>>>>>>> Unidata IDD Support said the following on 12/12/2007 5:10 PM: > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>>> Trung Le, > >>>>>>>>>>>>> > >>>>>>>>>>>>> Your Ticket has been received, and a Unidata staff member > >>>>>>>>>>>>> will review it and reply accordingly. Listed below are > >>>>>>>>>>>>> details of this new Ticket. Please make sure the Ticket ID > >>>>>>>>>>>>> remains in the Subject: line on all correspondence related > >>>>>>>>>>>>> to this Ticket. > >>>>>>>>>>>>> > >>>>>>>>>>>>> Ticket ID: VQA-158250 > >>>>>>>>>>>>> Subject: Feed site for 1km BREF radar data > >>>>>>>>>>>>> Department: Support IDD > >>>>>>>>>>>>> Priority: Normal > >>>>>>>>>>>>> Status: Open > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> Please let us know if we can be of further assistance. > >>>>>>>>>>>>> > >>>>>>>>>>>>> Unidata User Support > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>> Jeff Weber > >>>>>>>>>>> Unidata User Support > >>>>>>>>>>> http://www.unidata.ucar.edu > >>>>>>>>>>> > >>>>>>>>>>> Ticket Details > >>>>>>>>>>> =================== > >>>>>>>>>>> Ticket ID: VQA-158250 > >>>>>>>>>>> Department: Support IDD > >>>>>>>>>>> Priority: Normal > >>>>>>>>>>> Status: Open > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>> Jeff Weber > >>>>>>>>> Unidata User Support > >>>>>>>>> http://www.unidata.ucar.edu > >>>>>>>>> > >>>>>>>>> Ticket Details > >>>>>>>>> =================== > >>>>>>>>> Ticket ID: VQA-158250 > >>>>>>>>> Department: Support IDD > >>>>>>>>> Priority: Normal > >>>>>>>>> Status: Open > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>> Jeff Weber > >>>>>>> Unidata User Support > >>>>>>> http://www.unidata.ucar.edu > >>>>>>> > >>>>>>> Ticket Details > >>>>>>> =================== > >>>>>>> Ticket ID: VQA-158250 > >>>>>>> Department: Support IDD > >>>>>>> Priority: Normal > >>>>>>> Status: Open > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>> Jeff Weber > >>>>> Unidata User Support > >>>>> http://www.unidata.ucar.edu > >>>>> > >>>>> Ticket Details > >>>>> =================== > >>>>> Ticket ID: VQA-158250 > >>>>> Department: Support IDD > >>>>> Priority: Normal > >>>>> Status: Open > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>> -- > >>>> Elmer Tipton > >>>> Computer Analyst > >>>> Software Maintenance > >>>> Northrop Grumman IT > >>>> (301) 763-8384 x170 > >>>> address@hidden > >>>> > >>>> > >>>> > >>>> > >>> Jeff Weber > >>> Unidata User Support > >>> http://www.unidata.ucar.edu > >>> > >>> Ticket Details > >>> =================== > >>> Ticket ID: VQA-158250 > >>> Department: Support IDD > >>> Priority: Normal > >>> Status: Open > >>> > >>> > >>> > >>> > > -- > Elmer Tipton > Computer Analyst > Software Maintenance > Northrop Grumman IT > (301) 763-8384 x170 > address@hidden > > Jeff Weber Unidata User Support http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: VQA-158250 Department: Support IDD Priority: Normal Status: Open