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

20051115: further help need migrating SSEC users off of old adde.ucar.edu



>From: Unidata Support <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200508291349.j7TDnujo003962 McIDAS ADDE

Hi again Jerry,

Since you help previously, I am back asking again ;-)

There are three SSEC machines that are hitting the old adde.ucar.edu
for data:

128.104.108.111  - pmf_pb.ssec.wisc.edu
128.104.109.119  - popeye.ssec.wisc.edu
128.104.109.55   - mica.ssec.wisc.edu

Could you help figure out who is running McIDAS from thse machines
so I can get the information about the need to run DATALOC HOST
to them?  Thanks!

Here is the original message I sent out the the Unidata-maintained
mcidas-x and ldm-users email lists:

  Users of the McIDAS ADDE server adde.ucar.edu:
  
  We have transitioned the machine known as adde.ucar.edu (aka
  motherlode.ucar.edu) from Sun Enterprise E420 to SunFire 480 hardware.
  The machine has also been moved from the NCAR machine room to the
  Unidata offices at Foothills Lab #4.
  
  Because of the relocation of adde.ucar.edu, the IP address has changed
  from 128.117.15.119 to 128.117.114.119.  This change coupled with
  McIDAS' cache of ADDE server IP addresses in its client routing table
  requires the following steps be undertaken by sites accessing data from
  the ADDE server adde.ucar.edu:
  
    <login as the user 'mcidas'>
    cd $MCDATA
    dataloc.k HOST
  
  If you have cron-initiated scripts run from an account other than 'mcidas'
  that access adde.ucar.edu:
  
    <login as the user running the cron-initiated scripts>
    cd $MCDATA
    dataloc.k HOST
  
  'DATALOC HOST' will force McIDAS to update its client routing table
  (pointed at through $MCTABLE_WRITE) cache of IP address for all hosts.
  
  Please follow the above procedures as soon as you are able.  ADDE
  access to the old adde.ucar.edu machine (IP address 128.117.15.119)
  will begin failing at the beginning of the week of November 7.
  
  Thanks in advance for your prompt attention in this matter!
  
  Please send any questions/comments regarding the above procedure to
  Unidata User Support <address@hidden>.

Thanks again for your help.

Cheers,

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

>From address@hidden  Tue Nov 15 14:45:04 2005

Hi Tom,

I notified pmf_pb.ssec.wisc.edu .. and he was going to run the DATALOC 
HOST command.

The other two machines are from MUG, and I forwarded on your request to 
update their tables.

Jerry


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.