Restorepoint Release Notes, version 5.6

Restorepoint version 5.6 includes updates to its Change Detection feature, support for both IPv4 and IPv6 addresses, a new Labels page, and varying enhancements to the Restorepoint user interface.

Key Features

This section covers the key features that were included in this release:

  • Updated Restorepoint and its Agents to be deployed on an IPv6 or dual-stack network using manual or automatic IP address assignment. Meaning, both IPv4 and IPv6 devices can be added to the Restorepoint console. External servers (such as LDAP, RADIUS, storage, SMTP, SNMP, NTP, Syslog, and/or DNS) can now be v4 or v6. “Host” fields across Restorepoint can now accept an IPv4/IPv6 address or a hostname (excluding DNS servers (IP address-only). If a "hostname" field is specified, it is resolved at run-time. A newly added "Resolve" button is now available to attempt DNS-resolution for hostname verification.

  • Updated Restorepoint's Change Detection feature on the "Compare Configurations" page to allow you to ignore changes in Device Configurations that do not represent actual changes. Examples of changes that can be ignored are: run-time variables (e.g. Cisco IOS ntp clock-period value), salted hashes (e.g. hashed passwords, certificates, keys), and/or log files. You can now set Restorepoint to specifically ignore phrasing/words (like matching a regex), entire text-blocks (given the start/stop delimiters), and entire files (within tar/tgz/zip/xz config files).

Additional Features

  • Updated "Device Details" to use a new component that validates whether your IPv4 address, IPv6 address, or hostname are supported. To validate support, you must enter the desired field for either the "Hostname" or the "Address" and select the newly added "Resolve" button.

  • Updated Restorepoint's "Network Settings" to support IPv6 interface configurations. There are now two IP address options (IPv4 and IPv6) available in the "Additional Static Routes" window on the "System Settings" page.

  • Updated Radius and LDAP primary and secondary auth servers to use a new component that validates whether your IPv4 address, IPv6 address, or hostname are supported. To validate support, you must enter the desired field for either the "Hostname" or the "Address" and select the newly added "Resolve" button.

  • Updated the Agent console to use IPv6 addresses or hostnames in the additional Agent menu entries, Initial Restorepoint Master Setup, and Change Restorepoint Master IP address.

  • Updated this version of Restorepoint to disable automatic host-name resolution. A generic IPv4/IPv6/hostname field is now available for simpler processing.

  • Updated Restorepoint to allow you to list, add, and remove additional IPv6 routes. These routes are then validated with the new validation component.

  • Updated Restorepoint's "Static Routes" window to separately list both IPv4 and IPv6 routes.

To view release notes and manuals for all versions of Restorepoint, see Restorepoint Documentation.

Issues Addressed

The following issues were addressed in this release:

  • Addressed an issue where duplicate device assets were created, resulting in an unresponsive devices list page.
  • Addressed an issue in which the "TLS Cipher Options" window failed to allow users to check or uncheck options. (Case: FD32330)
  • Updated Restorepoint to identify the correct syntax for IPv6 addresses when you use SCP. Addresses are now read correctly if they are within square brackets to avoid filename or IP address confusion.

Known Issues

This release contains the following known issues:

  • Network Discovery over IPv6 is not yet implemented. IPv6 devices can only be added manually, via CSV import, or using the API.

  • IPv6 will only be supported on appliances based on Oracle Linux 8.

  • SNMP settings (Administration > System Settings > SNMP) may need to be reset/updated after upgrading to 5.6.

  • Failed user login attempts on the Slave node don't register correctly on the user login attempts table.

  • Failed user login attempts on the Master node sync the login attempt date incorrectly (without the timezone) to the Slave node. The user is then unable to log into the Slave node after a failed login attempt.

  • Observed an issue in which Restorepoint returned invalid data after a device's plugin type was changed; this was due to the device plugin's inability to permit specific config types used in the newly-changed plugin type's existing schedules.

  • Addressed an issue in which the Rescan button, located on the Devices > Discovery > Devices screen, failed to rescan devices if multiple were selected. The Rescan button only works correctly for the top-most selected device; this leaves all of the following devices selected to be rescanned and tested one-by-one.

Installing or Upgrading Restorepoint

For detailed steps about installing or upgrading to this version of Restorepoint, see Installing Restorepoint.

You should always upgrade to the most recent release of Restorepoint.