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

[IDD #OSS-839566]: IP address change for idd.unidata.ucar.edu

Hi Mike,

> Clarification:  I meant forward lookup still points to old IP

Yup, got it.

I see that vulcan.sjsu.edu is now feeding from the new idd.unidata.ucar.edu.
Can I assume that all SJSU LDMs have been restarted and their REQUEST(s)
to idd.unidata.ucar.edu are now aimed at the new instance of this cluster?

On a related note, I just noticed that vulcan is redundantly REQUESTing
NEXRAD3 data.  Here is a snippit from the LDM utility 'uldbutil' that
shows the redundant REQUESTs:

11271 6 feeder vulcan.science.sjsu.edu 20190822000101.735282 TS_ENDT {{NEXRAD3, 
".*"}} primary
36386 6 feeder vulcan.science.sjsu.edu 20190822042436.255196 TS_ENDT {{NEXRAD3, 
"^SDUS5."}} primary

There is no need to do a REQUEST using the pattern "^SDUS5." when also
doing a REQUEST for ".*" (everything).  Since both REQUESTs are in primary
mode, the net result is you are simply using more bandwidth that you
need to use.

I have not checked other SJSU feed REQUEST(s) to see if there are other 
of unneeded redundancy, so I can't say if this is the only instance.  If you
find other instances, it would be wise to remove them to lessen the bandwidth
that is being used both on your and on our ends.


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: OSS-839566
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.