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.
Donna & Chris, The "smoking gun" is the fact that the command "telnet ldm-relay1.tamu.edu 388" fails when executed inside the campus firewall but not outside. > > ---------- Forwarded message ---------- > > From: "Chris Mouchyn" <address@hidden> > > Date: Nov 10, 2016 12:14 PM > > Subject: ldm-relay1 problems > > To: "Donna Cote" <address@hidden>, "Arif, Taimur" <address@hidden> > > Cc: > > > > So, there is a network routing issue going on. > > > > > > I've been using the following command for testing: > > > > > > notifyme -vl- -f ANY -h 165.91.55.27 > > > > > > That command fails from ldm1,2,3. It succeeds from ldm-relay0 to > > > ldm-relay1. That tells me that: > > > > > > 1. there is nothing wrong with the LDM service on ldm-relay1 > > > 2. there is nothing wrong with the iptables firewall ldm-relay1; it is > > > properly configured and allowing connections on port 388 > > > > > > The only thing left is some weird network-level routing issue between the > > > ldm cluster nodes and ldm-relay1. Getting CIS to find and fix that problem > > > won't be easy... It's my understanding that the ldm-relays are OUTSIDE of > > > the TAMU firewall, but the ldm cluster nodes are INSIDE the firewall. That > > > might have something to do with our problems, especially since CIS just > > > upgraded the TAMU firewall recently. > > > > > > We might need to get Guy to pull some TAMU IT strings on this one. Regards, Steve Emmerson Ticket Details =================== Ticket ID: ZJW-284386 Department: Support LDM 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.