iMS 5.2 in a Veritas Cluster
I am currently planning the upgrade of three NMS 4.15 VCS based servers to iMS5.2. The H/A instructions are pretty clear for the mail server but does not mention the admin server in this environment. We are currently starting the admin server in the 4.15 environment but really use VCS to manage the mail servers. Is the lack of instruction in the H/A area because VCS is really the admin server and there is no need to include it in the H/A setup?
[462 byte] By [
708533] at [2007-11-25 8:03:43]
I hate to reply to my own question, but it looks like the admin server is still needed with the iMS5.2 server in H/A. I have tested H/A on a box and it works pretty much like it is documented with a couple of gotchas:
1) The normal HTTP generated out going mail goes on port 127.0.0.1 by default. When H/A is installed, it no longer listens to this port but rather the port assigned to H/A for the application.
2) The typical installation as opposed to the custom installation does not ask for an address for the Admin Server. In most cases it is the default address of the server being installed to.
The variable configuration.nsServerAddress is the location in the local.conf file, but this file is regenerated each time the admin server is restarted. Is there a configutil variable that can be set after doing the typical install? The ha_ip_config script would be a good candidate for updating the variable wherever it is stored.
The configuration.nsServerAddress variable is actually a configuration entry on the LDAP Configuration Server you installed iMS against. I got caught out by this too. If you update the value in the Configuration Directory master, and restart the admin server, it will re-write your local.conf with the appropriate value and start the listener.
