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

20040914: adde.ucar.edu IP address change

>From: Unidata User Support <address@hidden>
>Organization: Unidata Program Center/UCAR
>Keywords: McIDAS ADDE IP

Users of the McIDAS ADDE server on adde.ucar.edu:

The IP address of adde.ucar.edu (aka motherlode.ucar.edu) has been
changed from 128.117.13.119 to 128.117.15.119.  During a short overlap
period, adde.ucar.edu will continue to respond to ADDE data requests
under the old IP address.  After the overlap period (currently
scheduled to extend to through the week of September 20), ADDE requests
to adde.ucar.edu will stop working _unless_ you take corrective
action.

The procedure needed to update the cached IP address used for
McIDAS ADDE transactions is as follows:

- start a McIDAS session for the user who accesses adde.ucar.edu
  using ADDE

- determine if you are "pointing" at adde.ucar.edu for any ADDE dataset
  by running:

DATALOC LIST
  
- if you are using adde.ucar.edu (remember that your listing might
  reference motherlode.ucar.edu instead of adde.ucar.edu), update your
  client routing table by running:

DATALOC HOST

  If your ADDE access to adde.ucar.edu is through cron-initiated shell
  scripts, you will need to run 'DATALOC HOST' as the user that is
  running the cron-initiated scripts.

This procedure may need to be run by each who accesses adde.ucar.edu,
or it may be sufficient to update the client routing table for the user
'mcidas'.  Which option is needed will depend on how you configured the
MCTABLE_READ environment variable for each McIDAS user on your system.

Please contact Unidata User Support <address@hidden> if you
have any questions about what you need to do to update your McIDAS
client routing table to continue to access data through the ADDE server
on adde.ucar.edu.

Cheers,

Tom Yoksas