[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[CONDUIT #PGY-808322]: Upcoming NCEP CONDUIT maintenance
- Subject: [CONDUIT #PGY-808322]: Upcoming NCEP CONDUIT maintenance
- Date: Wed, 22 Jan 2014 14:27:09 -0700
Hi Carissa,
Sorry for the slow reply today; there is too much going on here at
the moment...
re:
> Here is the list of IPs allowed from our Network folk:
>
> 192.12.209.57
> 193.61.196.74
> 128.174.80.16
> 128.118.64.134
> 128.118.64.140
> 128.118.64.143
> 128.118.64.146
> 144.92.130.88
> 128.117.149.8
> 128.104.109.52
> 128.117.130.220
> 128.117.132.3
> 128.117.134.103
> 128.117.140.220
> 128.117.149.220
> 128.117.156.220
> 128.117.156.80
> 128.117.156.85
> 128.117.181.38
OK, this works out to be:
192.12.209.57 - atm.cise-nsf.gov
193.61.196.74 - ECMWF ???
128.174.80.16 - flood.atmos.uiuc.edu
128.118.64.134 - idd-ingest.meteo.psu.edu
128.118.64.140 - iddrs1a.meteo.psu.edu
128.118.64.143 - iddrs2a.meteo.psu.edu
128.118.64.146 - iddrs3a.meteo.psu.edu
144.92.130.88 - idd.aos.wisc.edu
128.117.149.8 - rtstats.unidata.ucar.edu
128.104.109.52 - unidata2-new.ssec.wisc.edu
128.117.140.220 - conduit.unidata.ucar.edu
128.117.130.220 - conduit1.unidata.ucar.edu
128.117.156.220 - conduit2.unidata.ucar.edu
128.117.149.220 - conduit3.unidata.ucar.edu
128.117.134.103 - lead4.unidata.ucar.edu
128.117.156.80 - gale.unidata.ucar.edu
128.117.156.85 - flip.unidata.ucar.edu
128.117.132.3 - datagrid.ucar.edu
128.117.181.38 - dataportal.ucar.edu
Comments:
1) 192.12.209.57 - atm.cise-nsf.gov
This machine was removed from the NSF machine room in Vienna, Va
and relocated to the main machine room here in NCAR/UCAR. The
updated info for this machine is:
128.117.12.35 <-> atm.ucar.edu
2) 128.117.149.8 - rtstats.unidata.ucar.edu
This is the machine to which real-time statistics are reported
by all LDMs fully participating in the IDD.
3) 128.117.181.38 - dataportal.ucar.edu
This is an NCAR machine.
4) 128.117.140.220 - conduit.unidata.ucar.edu
128.117.130.220 - conduit1.unidata.ucar.edu
128.117.156.220 - conduit2.unidata.ucar.edu
128.117.149.220 - conduit3.unidata.ucar.edu
I got together with our system administrator Mike Schmidt to
find out what these are... they are place holders on all of
our 4 subnets that could be used for CONDUIT relay instances.
5) the machine that I was concerned about was the one that
we are currently using to ingest CONDUIT from ncepldm4.woc.noaa.gov,
128.117.140.208 <-> daffy.unidata.ucar.edu
It turns out that Mike had setup specific routing on daffy to
send all traffic to 140.90.33.20[345] through our 128.117.156.
subnet. What was missing was a new static route entry that
would send all traffic for 140.90.101.42 (conduit.ncep.noaa.gov)
through our same 128.117.156. subnet. This is why the notifyme
attempt I tried at the end of last week failed:
<as 'ldm' on daffy>
notifyme -vl- -f CONDUIT -h conduit.ncep.noaa.gov
After adding the needed static route, this now works, so no
modification is needed on your side.
6) 128.117.134.103 - lead4.unidata.ucar.edu
128.117.156.80 - gale.unidata.ucar.edu
128.117.156.85 - flip.unidata.ucar.edu
These are Unidata workstations that are commonly used to test
LDM/IDD feeds. Please keep their access open.
7) 128.104.109.52 - unidata2-new.ssec.wisc.edu
This is a Unidata machine that is housed in the UW/SSEC Data Center.
Since it is currently a toplevel IDD relay node, we would like it
to continue to be able to REQUEST CONDUIT from NCEP/NOAA toplevel(s).
8) 128.117.132.3 - datagrid.ucar.edu
128.117.181.38 - dataportal.ucar.edu
These are NCAR/CISL machines. Please keep their access open.
re:
> Again, let me know what is missing and we will get it worked out.
Please switch the current access for atm.cise-nsf.gov to atm.ucar.edu;
IP addresses for both are listed above.
After that, everything should be good. I will send out an email to the
LDM/IDD administrators at UIllinois (flood.atmos.uiuc.edu), PennState
(idd-ingest.meteo.psu.edu, iddrs[123]a.meteo.psu.edu) and UWisconsinAOS
(idd.aos.wisc.edu) advising them to setup test their connectivity
to conduit.ncep.noaa.gov using 'notifyme' and then to setup redundant
feed REQUEST(s).
Cheers,
Tom
--
****************************************************************************
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: PGY-808322
Department: Support CONDUIT
Priority: Normal
Status: Closed