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 Robert, OK. You've convinced me. I've added this issue to the development list. > I really shouldn't be trying to modify the routing table because of the > HA nature of the setup. The IP I'm using for LDM moves between two > servers. Trying to add it would complicate the configuration. My > installation is working with the default behavior. It just when I moved > to a HA configuration I noticed the upstream IP was not using the LDM > configured IP (HA IP). I would say it's really common for system > administrators to assign additional IP to a server for a service. That > way you can move the service to other hardware in the future with out > the headache of an IP change. This is very true with DNS servers. I > think it would be true with LDM. If I assign an IP and DNS entry for > LDM, tell the upstream providers about this. They configure their LDM > down stream config file and firewalls with the IP. I have the freedom > of moving my LDM service around to different hardware or HA it with no > impact. I also don't need to change DNS and wait for propagation to occur. Regards, Steve Emmerson Ticket Details =================== Ticket ID: FVT-875334 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.