Upgrade external syslog server to Java 11

Java 11 is mandatory for the log collection functionality of your external syslog server. This topic explains how to prepare your syslog server to work with A32.50 by either:

  • Option 1: Replacing the server; or,

  • Option 2: Upgrading the Java version.

If your syslog server is running CentOS 6, we recommend you use option 1: to replace an existing external syslog server and reassign its IP to a new server.

Tip: To check what version a syslog server is running, login to the syslog server via CLI and use the following command:

java -version 2>&1 | egrep -o '[0-9]+\.[0-9]+' | head -n1

Warning: Traffic logs that are sent during the following procedures may be lost.

Option 1: To replace an existing external syslog in ASMS

If you want to deploy a new external syslog server, do the following steps to maintain the same IP address/hostname as the old server on the new server:

  1. Deploy a new external syslog server (see Configure an external Syslog server) and assign it a temporary IP.

  2. Remove the public key of the old syslog server by logging in to the Central Manager as afa user and running this script:

    ssh-keygen -R <original IP of the old syslog server>
  3. Assign a different IP address/hostname to the old external syslog server.

  4. Assign the original IP of the old server to the new external syslog server.

  5. Run Edit-Next (Edit device wizard) on one of the devices that connects to the external syslog server. This can preferably be a small and stable device which will take a short time.

    Important: After running Edit-next, check the list of child devices and remove unwanted devices.

  6. After verifying that the new syslog is functioning correctly, you can safely delete the old machine.

Option 2: To upgrade your syslog to Java 11

Before proceeding, make sure your syslog server is not already running Java 11.

Important: After running Edit-next, check the list of child devices and remove unwanted devices.