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

[LDM #AFT-567406]: GOES-17 data filing question

Hi Mike,

re: change Satellite to SATELLITE
> Okay, made this change just in case, and to clean it up.

Thanks.  This may not be needed as the LDM log file on the idd.unidata.ucar.edu
node that is feeding vulcan showed the SATELLITE REQUESTs correctly before
and after your change.  Here is the before:

20191031T205952.125480Z vulcan.science.sjsu.edu(feed)[16191] up6.c:up6_run:445  
                 NOTE  Starting Up(6.13.11/6): 20191031195950.991754 TS_ENDT 
{{SATELLITE, "ABI-L1b-RadC"}}, SIG=6bdceafe984b554883a314845e84c39a,
 Primary
20191031T205952.125543Z vulcan.science.sjsu.edu(feed)[16191] up6.c:up6_run:448  
                 NOTE  topo:  vulcan.science.sjsu.edu {{SATELLITE, (.*)}}
 ...
20191031T205952.134007Z vulcan.science.sjsu.edu(feed)[16197] up6.c:up6_run:445  
                 NOTE  Starting Up(6.13.11/6): 20191031195950.992630 TS_ENDT 
{{SATELLITE, "ABI-L1b-RadF"}}, SIG=82f4d4400149f47a050d3909d8455605,
 Primary
20191031T205952.134074Z vulcan.science.sjsu.edu(feed)[16197] up6.c:up6_run:448  
                 NOTE  topo:  vulcan.science.sjsu.edu {{SATELLITE, (.*)}}
 ...
20191031T205952.256212Z vulcan.science.sjsu.edu(feed)[16201] up6.c:up6_run:445  
                 NOTE  Starting Up(6.13.11/6): 20191031195951.159350 TS_ENDT 
{{SATELLITE, "GLM-L2-LFCA"}}, SIG=NONE, Primary
20191031T205952.256267Z vulcan.science.sjsu.edu(feed)[16201] up6.c:up6_run:448  
                 NOTE  topo:  vulcan.science.sjsu.edu {{SATELLITE, (.*)}}

I guess that Steve did make a change that allows for mixed case in feed names.

re: Even though you are not REQUESTing all of the SATELLITE feed, the volume and
peaks/valleys in volume is _heavily_ dominated by the FullDisk images especially
Channel 02 (0.64 um) images.

> Good tip.  I may alter my request to get just the Channels we are using.
> Not using fulldisk Channel02 at present.

This couldn't hurt.

re:
re: Can you send the output of:
/sbin/ifconfig -a

> Okay, below is output of ifconfig.  I'll look into the network connection
> piece.  Good background knowledge I should have anyhow.
> thanks again!
> 
> [ldm@vulcan etc]$ ifconfig -a
> eth0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
> ether b0:26:28:15:b4:0a  txqueuelen 1000  (Ethernet)
> RX packets 0  bytes 0 (0.0 B)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 0  bytes 0 (0.0 B)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> device interrupt 16
> 
> eth1: flags=4098<BROADCAST,MULTICAST>  mtu 1500
> ether b0:26:28:15:b4:0b  txqueuelen 1000  (Ethernet)
> RX packets 0  bytes 0 (0.0 B)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 0  bytes 0 (0.0 B)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> device interrupt 17
> 
> eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
> inet 10.32.42.3  netmask 255.255.255.0  broadcast 10.32.42.255
> inet6 fe80::b226:28ff:fe15:b40c  prefixlen 64  scopeid 0x20<link>
> ether b0:26:28:15:b4:0c  txqueuelen 1000  (Ethernet)
> RX packets 16442505091  bytes 24589298806072 (22.3 TiB)
> RX errors 0  dropped 0  overruns 0  frame 316
> TX packets 2376875621  bytes 734677079403 (684.2 GiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> eth3: flags=4098<BROADCAST,MULTICAST>  mtu 1500
> ether b0:26:28:15:b4:0d  txqueuelen 1000  (Ethernet)
> RX packets 0  bytes 0 (0.0 B)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 0  bytes 0 (0.0 B)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
> inet 127.0.0.1  netmask 255.0.0.0
> inet6 ::1  prefixlen 128  scopeid 0x10<host>
> loop  txqueuelen 1000  (Local Loopback)
> RX packets 1096  bytes 180014 (175.7 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 1096  bytes 180014 (175.7 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Steve just sent me a note pointing out that the IP address for eth2 is
a private 10. address, and this indicates that it must be NATed.
The question he poses is:

Is there more than one host behind the NAT?

Meaning, is there more than one machine running an LDM behind the
NAT?  If there is, this could be the smoking gun.

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: AFT-567406
Department: Support LDM
Priority: Normal
Status: Open
===================
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.