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

[NOAAPORT #GGP-872890]: New Noaaport server with ldm

Hi Heather,

re:
> I added what you told me to the sysctl.conf file, and rebooted.
> 
> I also figured out how to get the route tables.  This is what I had first:
> [root@npingest ~]# route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> default         gateway         0.0.0.0         UG    100    0        0 eno1
> 10.2.15.0       0.0.0.0         255.255.255.0   U     100    0        0 eno1
> 10.2.15.0       gateway         255.255.255.0   UG    100    0        0 eno1
> link-local      0.0.0.0         255.255.0.0     U     1003   0        0 eth1
> 192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1

OK.  The multicast routing needed is not in this listing.

re:
> and then added what you told me and now I have this:
> [root@npingest ~]# route add -net 224.0.0.0 netmask 240.0.0.0 gw 192.168.0.10 
> dev eth1
> [root@npingest ~]# route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> default         gateway         0.0.0.0         UG    100    0        0 eno1
> 10.2.15.0       0.0.0.0         255.255.255.0   U     100    0        0 eno1
> 10.2.15.0       gateway         255.255.255.0   UG    100    0        0 eno1
> link-local      0.0.0.0         255.255.0.0     U     1003   0        0 eth1
> 192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1
> 224.0.0.0       npingest.triad. 240.0.0.0       UG    0      0        0 eth1

Hmm... I am guessing that 'npingest.triad....' is the name given
to 192.168.0.10 in your /etc/hosts file?  If yes, this looks correct.

re:
> I then restarted the ldm.  Still nothing.

Can you send me your LDM configuration file, ~ldm/etc/ldmd.conf?
I want to review the settings for doing the NOAAPort ingest.

For reference, here are the ldmd.conf settings from one of our NOAAPort
ingest machines:

# 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"

Something to note in this listing:

- we are no longer using the system logging daemon for LDM-related
  logging

  A new logging module was added to the LDM, and we are using it
  pretty much exclusively now.  Using the system logging daemon
  still works, but using the other logging capability works
  better.

By the way, I have not yet noted that your Novra is not configured
for all of the PIDs that are needed.  For comparison, here is
the output of the 'show pids' from one of our Novra S300Ns:

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:

Notice the addition of 150 and 151 to the list that your Novra is configured
for.

Since we do not have a NOAAPort ingest machine running CentOS 7 here, it
is difficult for me to readily give you the information you need.  Is
there any way I could logon to your machine so I could look around?

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: GGP-872890
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.