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

[NOAAPORT #YJE-806765]: new LDM server ingesting NOAAPort feed



Rodger,

First thing: are you seeing any "gap" or "missing frame" messages from 
noaaportIngester(1) in the LDM log file?

> Iâm trying to set up a new LDM server to ingest our NOAAPort feed. Itâs 
> running on
> Ubuntu 16.04 with LDM version ldm-6.13.1. Itâs ingesting and processing 
> products, but
> tcpdump is showing packet issues:
> 
> 13:59:57.769495 IP 10.0.9.51.34586 > 224.0.1.1.1201: UDP, bad length 4032 > 
> 1472
> 13:59:57.769647 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
> 13:59:57.770605 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
> 13:59:57.771487 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
> 13:59:57.772283 IP 10.0.9.51.34586 > 224.0.1.1.1201: UDP, bad length 2397 > 
> 1472
> 13:59:57.774520 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
> 13:59:57.775168 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
> 13:59:57.776143 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
> 13:59:57.776493 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
> 13:59:57.776585 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
> 13:59:57.777016 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
> 13:59:57.777236 IP 10.0.9.51.34586 > 224.0.1.1.1201: UDP, bad length 4032 > 
> 1472
> 13:59:57.777820 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
> 13:59:57.777919 IP 10.0.9.51 > 224.0.1.1: ip-proto-17
> 13:59:57.778035 IP 10.0.9.51.34586 > 224.0.1.1.1201: UDP, length 1207
> 
> Hereâs the ifconfig output:
> 
> ifconfig eth1
> eth1      Link encap:Ethernet  HWaddr 00:15:c5:f4:78:24
> inet addr:10.0.0.72  Bcast:10.0.0.255  Mask:255.255.255.0
> inet6 addr: fe80::215:c5ff:fef4:7824/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> RX packets:7369043 errors:0 dropped:0 overruns:0 frame:0
> TX packets:169 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:10065696198 (10.0 GB)  TX bytes:18130 (18.1 KB)
> Interrupt:17
> 
> Iâve tried setting in /etc/sysctl.conf net.ipv4.ipfrag_max_dist to 0, 1472, 
> 4096, and
> 8192 with no change in behavior. Did reboots after changing just to be sure. 
> The
> net.ipv4.conf.default.rp_filter is set to 2.
> 
> Our Novra S300N is running the latest firmware (Rev 15).
> 
> The proper entries are in ldmd.conf:
> 
> EXEC  "noaaportIngester -m 224.0.1.1"
> EXEC  "noaaportIngester -m 224.0.1.2"
> EXEC  "noaaportIngester -m 224.0.1.3"
> EXEC  "noaaportIngester -m 224.0.1.4"
> EXEC  "noaaportIngester -m 224.0.1.5"
> EXEC  "noaaportIngester -m 224.0.1.6"
> EXEC  "noaaportIngester -m 224.0.1.7"
> EXEC  "noaaportIngester -m 224.0.1.8â
> 
> Finally, here are the entries in /etc/network/interfaces for the port:
> 
> auto eth1
> iface eth1 inet static
> address 10.0.0.72
> netmask 255.255.255.0
> network 10.0.0.0
> broadcast 10.0.0.255
> up route add -net 224.0.0.0 netmask 240.0.0.0 gw 10.0.0.72 dev eth1
> 
> The above entries are legacy ones from the setup done years ago by the vendor 
> we used
> prior to switching the LDM with the builtin NOAAPort ingesting.
> 
> What do you see in any of the above is not correct? By the way, the 
> documentation at
> http://www.unidata.ucar.edu/software/ldm/ldm-current/utilities/noaaport/index.html
>  needs
> updating to reflect the 10 multicast addresses that are now available (11 if 
> you count
> NWWS). Also, the networking changes that are required are not discussed. 
> Iâm sure that
> few folks are putting in their own dishes anymore, but it would help anyone 
> starting
> from zero to have all the relevant steps and settings.
> 
> I searched the support archives but could not find any resolution to my 
> problem of the
> packet losses. Itâs strange because it appears that Iâm getting products 
> based on
> ldmd.log and checking actual products here and there.
> 
> Any help would be appreciated!

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: YJE-806765
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.



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.