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

[LDM #CFG-797475]: NOAA - LDM Issue

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [LDM #CFG-797475]: NOAA - LDM Issue
  • Date: Mon, 27 Feb 2017 14:46:35 -0700
Hi Russ,

We've been trying to come up with some reasonable sounding hypothesis
for why both 'noaaportIngester' and 'cmcs' are not able to read
the UDP stream coming from your Novra S300N, but so far we are drawing
a blank.

One thing that did come up, however, was the ability to use the output
from 'tcpdump' to find out the IP address of your Novra.  Please
run the following and send the results back:

<as 'root'>
tcpdump -i ens34 | grep -v 10.0

The lines that don't get filtered out by the 'grep -v 10.0' should
contain the IP address of your Novra.  Here is example output from
one of our CentOS 6 NOAAPort ingest machines:

[root@leno ~]# tcpdump -i eth1 | grep -v 10.0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
21:27:12.303437 IP 192.168.1.20.6516 > 255.255.255.255.6516: UDP, length 130
21:27:12.994445 IP 192.168.1.20.6516 > 255.255.255.255.6516: UDP, length 130
21:27:13.688410 IP 192.168.1.20.6516 > 255.255.255.255.6516: UDP, length 130
21:27:14.375679 IP 192.168.1.20.6516 > 255.255.255.255.6516: UDP, length 130
21:27:15.072661 IP 192.168.1.20.6516 > 255.255.255.255.6516: UDP, length 130
21:27:15.747225 IP 192.168.1.20.6516 > 255.255.255.255.6516: UDP, length 130
21:27:16.458760 IP 192.168.1.20.6516 > 255.255.255.255.6516: UDP, length 130
21:27:17.155773 IP 192.168.1.20.6516 > 255.255.255.255.6516: UDP, length 130
21:27:17.840263 IP 192.168.1.20.6516 > 255.255.255.255.6516: UDP, length 130
^C8835 packets captured
9430 packets received by filter
594 packets dropped by kernel

This kind of output on your machine should (will) clear up the question of
what the IP address of your Novra S300N actually is.

Another idea:

Since 'cmcs' reads/tries to read the status packets and will use the IP
address garnered from the status packets in a listing of what Novra S300Ns
are seen, it will be interesting to see if the 'tcpdump' invocation shows
what we think it will show.

By the way, here is an example of what I was expecting you would see when
you ran 'cmcs':

~: cmcs
CMCS Utility

CMCS> list
1. S300N        IP address: 192.168.1.20        MAC: 00-06-76-05-02-a9

Select receiver by number to connect to or 0 to exit: 

Note how the listed IP address matches the one shown in the 'tcpdump'
listing.

Looking forward to the results of these tests on your machine...

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: CFG-797475
Department: Support LDM
Priority: High
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.