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.
Gilbert, [This reply is just so we have a publicly-visible copy of your email.] Updating Microsoft Windows caused problems. Interesting. Thanks for clearing that up. > > Society of Critical Care Medicine? System Center Configuration Manager? > > Microsoft's updates server here on campus. They started rolling > out September updates at 800+ mb/sec...and brought the > internal network almost to its knees on my end. > > > So, for 3 hours your LDM wasn't receiving data because the campus network > > was clogged by other downloads? > > Correct, from on-campus downloads. > > > That was rather draconian. The LDM uses TCP, which plays nice with > > others and automatically adjusts to available bandwidth -- using less if > > the network is congested and more as the network becomes uncongested. > > Agreed. > > >> Is there any way to have a feature "throttle" the LDM to some degree so > >> that it doesn't hit panic alarms when outages like this happen? With > >> gigabit comnnections and fast servers, this may be a problem > >> in the future, causing false DDOS alarms to ISP's and such. > > > > One might be able to use the tc(1) utility to impose a limit on TCP > >connections involving port 388. Would you please investigate this before > >adding to the LDM's "Issues" page. Thanks. > > OK, I will ook into it. Thanks! > > Gilbert Regards, Steve Emmerson Ticket Details =================== Ticket ID: BRZ-289323 Department: Support LDM Priority: Normal Status: Closed