Upgrade
This chapter details how to update an existing KeySafe 5 install to the latest version.
Upgrade from v1.5 KeySafe 5 Service Deployment
| Entrust recommends that you back up your data and configuration items before performing an upgrade, as described in KeySafe 5 Service Backup. |
-
Stop the running KeySafe 5 Service.
-
Uninstall the existing KeySafe 5 Service as described in the KeySafe 5 v1.5 documentation.
-
Install the new KeySafe 5 Service. The installation package can be found in the
keysafe5-servicedirectory of the KeySafe 5 release package.On Linux:
-
Run
sudo tar -C / -xf /path/to/keysafe5-server-1.7.0-Linux.tar.gzto unpack the KeySafe 5 Service binaries and associated scripts into the/opt/nfast/directory. -
Run
sudo /opt/nfast/keysafe5/server/sbin/installto install KeySafe 5 Service.
On Windows:
-
Double-click on
keysafe5-server-1.7.0-windows.msiand follow the Installation Wizard. -
Restart KeySafe 5 Service using the standard Windows Services facility.
-
-
Open the KeySafe 5 WebUI (by default at
https://127.0.0.1:18080) and check that you can see your existing KeySafe 5 data. -
Upgrade each KeySafe 5 Agent as described in Agent Upgrade.
Configuration File Changes
The following configuration parameters have been added in this version of KeySafe 5 Service.
These parameters and their default values can be found in the config.yaml.example file shipped with this version.
To change any of these settings from their default values, copy the relevant parameters into your existing config.yaml file and restart the KeySafe 5 Service.
Default values apply to any configuration parameters not explicitly set in config.yaml. For details on configuration items, see KeySafe 5 Service Configuration.
Existing configuration items that have been updated:
| Parameter | Description | Default Value |
|---|---|---|
|
Type of database to use. Now supports |
|
|
Timeout for database requests has increased from |
|
The new configuration items are as follows:
| Parameter | Description | Default Value |
|---|---|---|
|
MongoDB database hosts list, comma separated. IPv6 addresses must be in the form |
|
|
Name of the MongoDB replica set. |
|
|
Database name prefix. Use this if pointing multiple KeySafe 5 instances at the same MongoDB server to avoid database conflict. |
|
|
Authentication method for the MongoDB connection. Valid values: |
|
|
The name of the Authentication Database for MongoDB. |
|
|
File containing the MongoDB username. Only applicable if |
|
|
File containing the MongoDB password. Only applicable if |
|
|
x.509 client certificate. Only applicable when |
|
|
x.509 client private key. Only applicable when |
|
|
Set to |
|
|
Server CA certificate for MongoDB TLS. |
|
|
Minimum TLS protocol version for MongoDB. Valid values: |
|
|
Allowed cipher suites for MongoDB TLS. |
|
|
Timeout for connection to the MongoDB server. |
|
|
Timeout for selecting a connection from the connection pool. |
|
|
Timeout waiting for read/write on the socket. |
|
|
Minimum connections in the MongoDB connection pool. |
|
|
Maximum connections in the MongoDB connection pool. |
|
|
Duration to retain metric samples in storage. Supported units: y, w, d, h, m, s, ms. |
|
|
Maximum total size of storage blocks to retain. Set to |
|
|
Absolute path to the directory where metric samples and alert databases are stored. |
|
|
SMTP server used for sending alert notifications. For example, |
|
|
Sender address used in alert notification emails. |
|
|
Enable authenticated sending for the SMTP server. The SMTP server must support TLS, and its CA certificate must be in the OS trust store. |
|
|
Absolute path to the file containing the SMTP username for authentication. |
|
|
Absolute path to the file containing the SMTP password for authentication. |
|
|
Address of the host shown in the email alert footer link. If not set, the footer is not displayed. For example, |