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

[NOAAPORT #ZNX-891732]: 20181004: hardware recommendation for ingesting NOAAPort data?

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: [NOAAPORT #ZNX-891732]: 20181004: hardware recommendation for ingesting NOAAPort data?
  • Date: Wed, 10 Oct 2018 13:18:55 -0600
Hi Amenda,

Sorry for dropping the ball on this one... I thought that there was
nothing more to add, but I now feel that some comments to things you
said in your reply are in order...

re:
> Thanks for your quick response and specs on your ingest systems. And I
> don't mind at all that you put this out on support-noaaport.
> 
> I've embedded my answers to your questions below. Please let me know if you
> have further insights.

re:
> I see the "Gap in packet" messages in the noaaportIngester logs. We have
> another system (newer)  that is not showing as many of these messages, so
> my conclusion is that stream is at least better than what is getting into
> our older system.

Are both systems getting the UDP stream(s) from the Novra S300N receiver(s)
in the exact same way?

re:
> /sbin/ifconfig does not show any dropped packets. Does this make sense
> given the errors in the noaaportIngester logs?

Well, it should mean that there is not a problem with the Ethernet
interface being used to ingest the UDP stream from the Novra S300N
receiver.

Given our testing on less powerful (meaning older and slower) machines,
I would be surprised if your ingest machine was not fast enough to
correctly ingest the stream from the receiver.

re:
> I'll need to ask my SA for some of the info, but I do know  that it has the
> following:
> RHEL 6.10
> 6 processors
> 16 GB RAM
> ~500 GB disk

This should be more than enough of a machine to run a robust NOAAPort
ingest (IMHO).

re:
> Also, we run the ldm.pq out of a tmpfs partition in memory.

We do not do this as we have not found the need to do this.

re:
> C/N is 17.5 right now.

This is much different from what it used to be.  With this kind of C/N,
I wouldn't expect any problems in the receive system unless there is some
sort of local terrestrial interference source, but such a source would
effect all of your ingest machines.

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: ZNX-891732
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.