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.
Hi Heather, I logged onto your NOAAPort ingest machine yesterday and started poking around. I was soon joined by our system administrator and our LDM developer. After trying a few things including changing the Ethernet interface to jumbo frames (MTU of 9000), we came to the tentative conclusion that the problem is possibly (likely?) being caused by whatever is is responsible for the 'band length' messages that are seen in 'tcpdump -i eno2' invocations. We now need to research what could possibly be the cause of the 'bad length' messages. I am not sure when we'll figure this out, but I am hopeful for sometime soon as there are a lot of other fires that need putting out. 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.