Re: [ldm-users] noaaportIngester config issues

Make sure nothing in the IPTABLES is blocking it. 

Mike 

> On Mar 29, 2020, at 9:41 AM, Jack Snodgrass <jack@xxxxxxxxxxxxxx> wrote:
> 
>  First of all  LDM is toally new to me.  I am try to set this up for a 
> friend. 
> 
> I have a new LDM 6.13.12.42 installation. 
> 
> I used the latest from github - https://github.com/Unidata/LDM.git. 
> 
> I used: 
> 
> ./configure --with-noaaport --with-ingester --with-retrans --with-gribinsert
> 
> to configure. I am in a Centos 7 server. 
> 
> The main goal of this system is to receive data from a noaaport reciver / 
> modem. 
> 
> The system reports: 
> cmcs -list
> S300    IP address: 192.168.1.2    MAC: 00-06-76-05-02-4d
> so I 1) know that the server sees the modem and 2) it is a Novra type modem: 
> http://www.satcomsource.com/Novra-S300-Technical-User-Manual.pdf
> 
> Currently we have an OLD Centos 5 system with propriatary noaaport software 
> that works with that modem.  The Centos 5 system is having some issues so 
> we're looking to move the noaaport receive process to a newer system. 
> 
> The modem is on a 192.168.1.x network that is just setup for the modem and 
> the servers receiving data from it. 
> 
> 
> According to: 
> https://www.unidata.ucar.edu/software/ldm/ldm-current/utilities/noaaport/index.html
> 
> I need to setup: 
>  sysctl -w net.ipv4.ipfrag_max_dist=4096
>  sysctl -w net.ipv4.conf.default.rp_filter=2
>  sysctl -p
> which I have done. I have disabled selinux and he firewall on the Centos 7 
> box.  I have verified that the 
> /proc/sys/net/ipv4/conf/default/rp_filter
> and
> /proc/sys/net/ipv4/ipfrag_max_dist
> are the expected values after the system has booted. 
> 
> If I run 
> 
> tcpdump -n -i enp7s0f1 | grep 192.168.1.
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on enp7s0f1, link-type EN10MB (Ethernet), capture size 262144 bytes
> 08:30:55.413481 IP 192.168.1.2.6516 > 255.255.255.255.6516: UDP, length 130
> 08:30:55.905608 IP 192.168.1.2.6516 > 255.255.255.255.6516: UDP, length 130
> 08:30:56.412681 IP 192.168.1.2.6516 > 255.255.255.255.6516: UDP, length 130
> 08:30:56.900813 IP 192.168.1.2.6516 > 255.255.255.255.6516: UDP, length 130
> 
> I see data from the S300 modem...  I assume that is the Multcast Data that 
> the modem sends.. but that is  guess on my  part. 
> 
> I have tried server different instances ( different values ) for: 
> EXEC    "noaaportIngester -x -m 224.0.1.1 -I 192.168.1.99 -l 
> /home/ldm/var/logs/ldmd.log"
> EXEC    "noaaportIngester -x -m 224.0.1.2 -I 192.168.1.99 -l 
> /home/ldm/var/logs/ldmd.log"
> EXEC    "noaaportIngester -x -m 224.0.1.3 -I 192.168.1.99 -l 
> /home/ldm/var/logs/ldmd.log"
> EXEC    "noaaportIngester -x -m 224.0.1.4 -I 192.168.1.99 -l 
> /home/ldm/var/logs/ldmd.log"
> 
> or 
> EXEC    "noaaportIngester -x -m 224.0.1.1 -l /home/ldm/var/logs/ldmd.log"
> EXEC    "noaaportIngester -x -m 224.0.1.2 -l /home/ldm/var/logs/ldmd.log"
> EXEC    "noaaportIngester -x -m 224.0.1.3 -l /home/ldm/var/logs/ldmd.log"
> EXEC    "noaaportIngester -x -m 224.0.1.4 -l /home/ldm/var/logs/ldmd.log"
> 
> but when I do ldmadmin start or ldmadin restart the logs show: 
> 
> ------------
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE  Ingestion Statistics:
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE      Since Previous Report (or 
> Start):
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE          Duration          
> PT4M59.454614S
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE          Raw Data:
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE              Octets        0
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE              Mean Rate:
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE                  Octets    0/s
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE                  Bits      0/s
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE          Received frames:
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE              Number        0
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE              Mean Rate     0/s
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE          Missed frames:
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE              Number        0
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE              %             -nan
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE          Full FIFO:
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE              Number        0
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE              %             -nan
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE          Products:
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE              Inserted      0
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE              Mean Rate     0/s
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE      Since Start:
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE          Duration          
> PT4M59.454614S
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE          Raw Data:
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE              Octets        0
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE              Mean Rate:
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE                  Octets    0/s
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE                  Bits      0/s
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE          Received frames:
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE              Number        0
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE              Mean Rate     0/s
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE          Missed frames:
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE              Number        0
> 20200329T125412.495533Z noaaportIngester[20413]     
> noaaportIngester.c:reportStats:784  NOTE              %             -nan
> 20
> 
> 
> and never any data received from the modem. 
> 
> netstat -ang | grep -v ff
> 
> reports: 
> 
> IPv6/IPv4 Group Memberships
> Interface       RefCnt Group
> --------------- ------ ---------------------
> lo              1      224.0.0.1
> enp7s0f0        1      224.0.0.1
> enp7s0f1        1      224.0.1.4
> enp7s0f1        1      224.0.1.2
> enp7s0f1        1      224.0.1.3
> enp7s0f1        1      224.0.1.1
> enp7s0f1        1      224.0.0.1
> 
> 
> so .. what am I missing in order to received data from this S300 noaaport 
> receiver? 
> 
> On the OLD / WORKING system we have: 
> [PARAMS]
> 
> NOAAPORT_BUF_SIZE = 1,1,1,1
> LOGMASK = 0x06,5
> NUM_USERS = 4
> NUM_SATCOMM_BOARDS = 1
> SAVE_HDLC_FRAMES = {1,0}, {2,0}, {3,0}, {4,0}
> NOAAPORT_DATA_STREAM = DVB_NWSTG,DVB_GOES,DVB_NWSTG2,DVB_OCONUS
> MULTICAST_INTERFACE = 192.168.1.4
> 
> On the new LDM system... I didn't configure:  MULTICAST_INTERFACE = 
> 192.168.1.99 ( the new box is 192.168.1.99 ) anyplace. 
> 
> 
> any one have any ideas on why the LDM noaaportIngester stuff doesn't appear 
> to be ingesting? 
> 
> - jack
> 
> -- 
> jack - Southlake Texas - http://mylinuxguy.net
> _______________________________________________
> NOTE: All exchanges posted to Unidata maintained email lists are
> recorded in the Unidata inquiry tracking system and made publicly
> available through the web.  Users who post to any of the lists we
> maintain are reminded to remove any personal information that they
> do not want to be made public.
> 
> 
> ldm-users mailing list
> ldm-users@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe,  visit: 
> https://www.unidata.ucar.edu/mailing_lists/ 
  • 2020 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the ldm-users archives: