Changing a Servers Hostname

Changing a server's hostname is an uncommon task but may be necessary for the following reasons:

• Company branding.

• Domain change.

• Complete a restore of an Assure1 server primary from redundant backup.

• Re-purpose servers for development, staging or production purposes.

Change HostFQDN

This section details the procedure for changing the HostFQDN within the Assure1 platform.

Best Practices

• If HostFQDN was and should continue to be the same as WebFQDN, refer to the Change WebFQDN section instead.

• All MySQL data files must be within one directory in order to use the Redundancy Wizard. Symbolic links or data directory mounts spanning multiple drive partitions are not currently supported by the Redundancy Wizard and manual resync of replication is required. Please contact Support for guidance prior to changing the HostFQDN if you have a non-standard database install.

Prerequisites

1. Update DNS information, flush caches, and wait for TTL.

All Servers

1. Stop all Assure1 applications on all servers using broker control and init scripts.

   cd $A1BASEDIR/
   bin/BrokerControl --batch stopall
   service assure1-web stop
   service assure1-broker stop
   service assure1-db stop
   

2. Update system host and/or domain information as required with new HostFQDN.

   /etc/sysconfig/network
   /etc/resolv.conf
   

3. If HostFQDN of Primary or Backup Presentation server is changing.

   1. On each server partner.

      1. Update Unison config to the new HostFQDN of partner.

         1. etc/unison/Packages.prf

         2. etc/unison/Repos.prf

   2. On server where HostFQDN that is changing.

      1. Regenerate SSL Host certificate.

   /opt/assure1/bin/CreateSSLCertificate --Type Host --CN <HostFQDN> --Force 
   

On Primary Presentation server

1. Regenerate Web SSL certificate.

   /opt/assure1/bin/CreateSSLCertificate --Type Web --CN <WebFQDN> --AltCN <PriPres HostFQDN> [--AltCN <BakPres HostFQDN>] --Force
   

2. Modify etc/http.conf; replace any instances of the old HostFQDN with the new.

   <VirtualHost _default_:443>
       DocumentRoot /opt/assure1/www
       ServerName   [WEBFQDN]:443
       ServerAlias  [NEW HOSTFQDN]:443
   

3. Update etc/Assure1.conf changing any old HostFQDNs.

4. Copy the following files from the Presentation to all servers:

   1. etc/Assure1.conf

5. Copy the following files from the Primary Presentation to any External or Redundant Presentation servers:

   1. etc/ssl/Web.crt.pem

   2. etc/ssl/Web.key.pem

Presentation Servers (including External)

1. Start Apache.

   service assure1-web start
   

2. Start Database.

   service assure1-db start
   

3. Connect to the primary Assure1 schema.

4. Update Assure1 Servers record.

   UPDATE Servers SET ServerHostFQDN = "<NEW-HOST-FQDN>" WHERE ServerHostFQDN = "<OLD-HOST-FQDN>";
   

5. Update Devices record.

   UPDATE Devices SET DNSName = "<NEW-HOST-FQDN>" WHERE DNSName = "<OLD-HOST-FQDN>";
   UPDATE Devices SET CustomName = REPLACE(CustomName, "<OLD-HOST-FQDN>", "<NEW-HOST-FQDN>") WHERE DNSName = "<NEW-HOST-FQDN>";
   

6. Update CoreDatabases records.

   UPDATE CoreDatabases SET DBHost = "<NEW-HOST-FQDN>" WHERE DBHost = "<OLD-HOST-FQDN>";
   UPDATE CoreDatabases SET DatabaseName = REPLACE(DatabaseName, "<OLD-HOST-FQDN>", "<NEW-HOST-FQDN>") WHERE DBHost = "<NEW-HOST-FQDN>";
   

7. Update Application Configurations of type Host or DSN.

   UPDATE BrokerComponentConfig 
       SET BrokerComponentConfigValue = REPLACE(BrokerComponentConfigValue, "<OLD-HOST-FQDN>", "<NEW-HOST-FQDN>") 
   WHERE BrokerComponentConfigTypeID IN (8, 19);
   

8. Start the broker.

   service assure1-broker start
   

On Primary Presentation Server

1. Login to web interface.

2. Navigate to Configuration -> Notifications -> Profiles.

3. Update Notification Profiles using old HostFQDN

On Presentation and Database Servers where HostName Changed

1. Rerun Redundancy Wizard with data resync.

Change WebFQDN

This saection details the procedure for changing the WebFQDN (or Web & HostFQDN if should be the same) within the Assure1 platform.

Best Practices

• If HostFQDN was and should continue to be the same as WebFQDN, any steps referencing HostFQDN can be considered synonymous with the new WebFQDN

• All MySQL data files must be within one directory in order to use the Redundancy Wizard. Symbolic links or data directory mounts spanning multiple drive partitions are not currently supported by the Redundancy Wizard and manual resync of replication is required. Please contact Support for guidance prior to changing the WebFQDN if you have a non-standard database install.

Prerequisites

1. Update DNS information, flush caches, and wait for TTL.

All Servers

1. Stop all Assure1 applications on all servers using broker control and init scripts.

   cd $A1BASEDIR/
   bin/BrokerControl --batch stopall
   service assure1-web stop
   service assure1-broker stop
   service assure1-db stop
   

2. Update system host and/or domain information as required with new WebFQDN.

   /etc/sysconfig/network
   /etc/resolv.conf
   

Primary Presentation Server

1. Regenerate SSL certificate.

    /opt/assure1/bin/CreateSSLCertificate --Type Web --CN <WebFQDN> --AltCN <PriPres HostFQDN> [--AltCN <BakPres HostFQDN>] --Force
   

2. Modify etc/http.conf; replace any instances of the old WebFQDN with the new EXCEPT any VirtualHost's ServerAlias entries, those stay as the HostFQDN:

   <VirtualHost _default_:443>
     DocumentRoot /opt/assure1/www
     ServerName   [NEW WebFQDN]:443
     ServerAlias  [HostFQDN]:443
   

3. Copy the following files from the Primary Presentation to any External or Redundant Presentation servers:

   1. etc/ssl/Web.crt.pem

   2. etc/ssl/Web.key.pem

Presentation Servers (Including External)

1. Start Apache.

   service assure1-web start
   

2. Start Database.

   service assure1-db start
   

3. Connect to the primary Assure1 schema.

4. If HostFQDN should be the same as the new WebFQDN: update the Assure1 Server's host fdqn record (replacing \<NEW-WEB-FQDN> and \<OLD-WEB-FQDN> respectively)

   UPDATE Servers SET ServerHostFQDN = "<NEW-WEB-FQDN>" WHERE ServerHostFQDN = "<OLD-WEB-FQDN>";
   

5. Update Server record.

   UPDATE Servers SET WebFQDN = "<NEW-WEB-FQDN>" WHERE WebFQDN = "<OLD-WEB-FQDN>";
   

6. Update Device record.

   UPDATE Devices SET DNSName = "<NEW-WEB-FQDN>" WHERE DNSName = "<OLD-WEB-FQDN>";
   UPDATE Devices SET CustomName = REPLACE(CustomName, "<OLD-WEB-FQDN>", "<NEW-WEB-FQDN>") WHERE DNSName = "<NEW-WEB-FQDN>";
   

7. Update CoreDatabases record.

   UPDATE CoreDatabases SET DBHost = "<NEW-WEB-FQDN>" WHERE DBHost = "<OLD-WEB-FQDN>";
   

8. Update any Application Configurations of type Host or DSN matching old FQDN.

   UPDATE BrokerComponentConfig 
      SET BrokerComponentConfigValue = REPLACE(BrokerComponentConfigValue, "<OLD-WEB-FQDN>", "<NEW-WEB-FQDN>") 
    WHERE BrokerComponentConfigTypeID IN (8, 19);
   

All Servers

1. Update the rules checkout paths to point to the new WebFQDN: (NOTE: not all checkout directories are used on a database or collection server)

   for CHECKOUT in config dashboards core event files metric topology
   do
     if [ -d /opt/assure1/var/checkouts/$CHECKOUT ] ; then
         cd /opt/assure1/var/checkouts/$CHECKOUT &&  /opt/assure1/vendor/svn/bin/svn --config-dir /opt/assure1/etc/svn relocate https://<NEW-WEB-FQDN>/repos/$CHECKOUT/
     fi
   done
   

2. Start the broker.

   service assure1-broker start
   

On Primary Presentation Server

1. Login to web interface.

2. Navigate to Configuration -> Notifications -> Profiles.

3. Update any Notification Profiles using the old WebFQDN.

On Presentation and Database Servers where WebFQDN was Changed

1. If HostFQDN is the same as WebFQDN, rerun Redundancy Wizard with data resync.