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

[NOAAPORT #LQO-967392]: [noaaport] Lack of GOES16 L2 products from HDS feed

Hi Mike,

I'll skip down to the bottom of the email you sent to answer the
question you posed...

re:
> Thanks, Tom, I'll keep this in mind.  You've confirmed for me that this is
> on my end, so I'll keep digging and see if I can find out what happened.
> 
> I suppose the only other question I have at this time is, do you know what
> multicast address those products should be arriving under?  We
> have 224.0.1.1 thru 224.0.1.10 & 224.1.1.1 opened up, but if they've moved
> to anything outside of those then we may need to make some slight network
> changes.  But to my knowledge, that should be all there is:
> http://www.nws.noaa.gov/noaaport/document/Multicast%20Addresses%201.0.pdf

I think that I know the cause of the problem you are seeing, but I have
no idea of why it took so long to affect you:

The set of PIDs that need to be enabled on your Novra are shown in the
following CMCS listing from one of our Novra S300Ns (and LSU and UW/SSEC
are the same):

CMCS Utility

CMCS 192.168.1.20> show pids

        MPE PIDs being processed:       101     102     103     104     105
                                        106     107     108     150     151

        PIDs being forwarded raw:

It may be the case that you do not have 150 and 151 enabled.

The set of multicast addresses as instantiated in LDM configuration file
invocations of NoaaportIngester has not changed.  Here is what we, LSU
and UW/SSEC are using:

# 20170313 - changed set of noaaportIngester instances to match:
#            
http://www.nws.noaa.gov/noaaport/document/Multicast%20Addresses%201.0.pdf
#            CHANNEL PID MULTICAST ADDRESS Port DETAILS
#            NMC     101     224.0.1.1     1201 NCEP / NWSTG
#            GOES    102     224.0.1.2     1202 GOES / NESDIS
#            NMC2    103     224.0.1.3     1203 NCEP / NWSTG2
#            NOPT    104     224.0.1.4     1204 Optional Data - OCONUS Imagery 
/ Model
#            NPP     105     224.0.1.5     1205 National Polar-Orbiting 
Partnership / POLARSAT
#            EXP     106     224.0.1.8     1208 Experimental
#            GRW     107     224.0.1.9     1209 GOES-R Series West
#            GRE     108     224.0.1.10    1210 GOES-R Series East
#            NWWS    201     224.1.1.1     1201 Weather Wire
#
exec    "noaaportIngester -n -m 224.0.1.1  -l /data/tmp/nwstg.log"
exec    "noaaportIngester -n -m 224.0.1.2  -l /data/tmp/goes.log"
exec    "noaaportIngester -n -m 224.0.1.3  -l /data/tmp/nwstg2.log"
exec    "noaaportIngester -n -m 224.0.1.4  -l /data/tmp/oconus.log"
exec    "noaaportIngester -n -m 224.0.1.5  -l /data/tmp/nother.log"
exec    "noaaportIngester -n -m 224.0.1.8  -l /data/tmp/nother.log"
exec    "noaaportIngester -n -m 224.0.1.9  -l /data/tmp/nother.log"
exec    "noaaportIngester -n -m 224.0.1.10 -l /data/tmp/nother.log"

I seem to recall that you should reboot your Novra S300N after
changing the list of PIDs that are enabled, but I might have
done that just to be safe.

re:
> Thanks for your help,

No worries.  I hope that the list of PIDs is the fix you need!

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: LQO-967392
Department: Support NOAAPORT
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.