Complete the Upgrade

To complete the upgrade, complete the following procedures:
Re-Enable the Automatic Recovery of the Data Aggregator Process
Re-enable the automatic recovery of the data aggregator process. You disabled the automatic recovery before you upgraded the data aggregator. When enabled, if the database server runs out of memory, or if the data repository is unavailable for a time, the data aggregator shuts down automatically to help ensure that data consistency is maintained.
In a fault-tolerant environment, Consul manages the start and stop state of the data aggregator. You can skip this procedure.
For more information, see Fault Tolerance.
Follow these steps:
  1. Log in to the computer where the data aggregator is installed as the root user.
  2. Open a console and issue the following command:
    crontab -e
    A vi session opens.
  3. Uncomment out the following line by removing the pound symbol (#) from the beginning of the following line:
    # * * * * * /sbin/service dadaemon start > /dev/null
    For example:
    * * * * * /sbin/service dadaemon start > /dev/null
    The automatic recovery of the data aggregator process is re-enabled.
Perform the Post-Upgrade Configuration
Do the following steps after you upgrade
DX NetOps Performance Management
:
  • Upgrading the data aggregator backs up the
    /opt/IMDataAggregator/
    <apache-karaf-version>
    directory to the
    /opt/IMDataAggregator/backup/apache-karaf
    directory. Upgrades back up the customizations that are located in the
    /opt/IMDataAggregator/<apache-karaf-version>/etc/
    directory, such as default logging levels or other configurations, but does not restore them to the installation directory automatically. To avoid losing these customizations, restore these customizations manually.
  • Upgrading the data collector backs up the
    /opt/IMDataCollector/<apache-karaf-version>
    directory to the
    /opt/IMDataCollector/backup/apache-karaf
    directory. Upgrades back up the customizations that are located in the
    /opt/IMDataCollector/<apache-karaf-version>/etc/
    directory, such as default logging levels or other configurations, but does not restore them to the installation directory automatically. To avoid losing these customizations, restore these customizations manually.
Vendor Certification Priorities
New vendor certifications are placed at the bottom of the Vendor Certification Priorities list for the corresponding metric family. To take advantage of the new vendor certifications, manually change the vendor certification priorities.
For example, F5 CPU vendor certifications are modeled as normal CPUs but do not get discovered because F5 also supports Host Resources. After an upgrade, the Host Resources CPU priority entry is higher than the F5 entries appended to the end of the priority list. To discover F5 CPU devices and components, update the vendor certification priority for the CPU metric family.
CA Business Intelligence
Integrations
After you upgrade to a CABI version that
DX NetOps Performance Management
supports, reinstall your CABI content.
For more information:
(Optional) Disable the ActiveMQ Admin Console for the Data Aggregator or Data Collector
Generally, the ActiveMQ admin console should not be available on the network. Therefore, you can disable it for the data aggregator or the data collector.
Follow these steps:
  1. Go to the
    activemq.xml
    file in the data aggregator or data collector installation directory:
    <installation_directory>
    /broker/
    <apache-activemq-version>
    /conf/activemq.xml
  2. Comment out
    <import resource="jetty.xml"/>
    .
  3. Shut down the ActiveMQ broker on each data collector by issuing the following command:
    service activemq stop
  4. Shut down the ActiveMQ broker on the data aggregator by issuing the following command:
    service activemq stop
  5. Start the ActiveMQ broker on the data aggregator by issuing the following command:
    service activemq start
    If you do not start the broker on the data aggregator, the data aggregator starts it automatically.
  6. The data collectors automatically restart the ActiveMQ brokers.
    You can restart the brokers manually by issuing the following command:
    service activemq start
The ActiveMQ admin console is disabled for the data aggregator or the data collector and is not be available on the network.
(Optional) Update ActiveMQ Admin Console Access
Generally, the ActiveMQ admin console should not be available on the network. However, if certain users require the console, you can grant them access.
Follow these steps:
  1. Go to the
    activemq.xml
    file in the data aggregator or data collector installation directory:
    <installation_directory>
    /broker/
    <apache-activemq-version>
    /conf/activemq.xml
  2. To update user access, edit the
    jetty-realm.properties
    file.
  3. To encrypt the user passwords, issue the following command from the data aggregator or data collector installation directory:
    java -cp
    <installation_directory>
    /broker/
    <apache-activemq-version>
    /lib/web/jetty-all-9.2.22.v20170606.jar org.eclipse.jetty.util.security.Password
    password
    password
  4. Shut down the ActiveMQ broker on each data collector by issuing the following command:
    service activemq stop
  5. Shut down the ActiveMQ broker on the data aggregator by issuing the following command:
    service activemq stop
  6. Start the ActiveMQ broker on the data aggregator by issuing the following command:
    service activemq start
    If you do not start the broker on the data aggregator, the data aggregator starts it automatically.
  7. The data collectors automatically restart the ActiveMQ brokers.
    Issue the following command to restart the brokers manually:
    service activemq start
Users have not been granted access to the ActiveMQ admin console on the network.