Index


Prerequisites

  • A current v5.6.0 – v5.6.2 installation
  • A current and valid, non-local backup of your existing Statseeker server, see Backup and Restoration Process for details
  • Ensure that you meet the hardware requirements, see System Requirements for details
  • If you are changing product tier with this upgrade, then you will require a new License Key, please contact Customer Service

[top]


Download Location & Files

[top]


Important Notes

Statseeker Backup Changes

Statseeker v25.2 expands the SFTP backup method to include the option for SSH Certificate authorization. In addition, the SSH backup method is deprecated in Statseeker v25.2 and will be removed in a future version.

We recommend that servers currently utilizing SSH backups be migrated to SFTP backups, with SSH authorization. See Backup and Restoration Process for details.

[top]

Discovery Changes

Statseeker v25.2 introduces the ability to schedule Discovery (including Rewalk) from within the Discovery configuration. The Discovery My Network page provides the ability to review and manage these schedules.

  • The Crontab page has been removed from the Administration Tool
  • All existing Discovery/Rewalk cron jobs are migrated to the new system on upgrade to Statseeker v25.2

[top]

Additional Items when Upgrading from v5.6.0 / v5.6.1

Statseeker v5.6.2 introduced a new system requirement regarding the firmware employed by the system’s Boot configuration. This requirement applies to both new installations and when restoring a v5.6.2(+) server from backup.

  • The system must be using Extensible Firmware Interface (EFI) firmware
  • The Boot process must be set to EFI\UEFI
  • Legacy Boot or Compatibility Support Mode (CSM) must be disabled
  • Secure Boot must be disabled
  • The disk containing Statseeker boot partition must be set as the first boot device

These changes do not impact upgrading to Statseeker v25.2, only new v25.2 installs and v25.2 server restorations.


Discovery Update

Statseeker v5.6.2 included a reworking of the Discovery process. The upgrade process automatically updates:

  • The content of the v5.6.0 / v5.6.1 IP Address Scan Ranges file to a single v25.2 IP Address Ranges configuration
    Note: The upgrade process removes all commented entries (lines prefixed with a hash [#] character) in the IP Address Scan Ranges file. If your IP Address Scan Ranges file contains comment lines, then Statseeker recommends that you backup the file content to an off-server location prior to upgrading.

    If you have a large number of #’d lines, or use #’d entries as comments (for organization within the file etc.), then please contact Statseeker Support for assistance with importing these from the previously backed-up file.
  • SNMP v1 and v3 Credentials in use by Statseeker when communicating with devices on the network, upgrading them to individual v25.2 SNMP Credentials configurations adhering to the naming convention below
  • Each unique entry in the v5.6.0 / v5.6.1 SNMP Communities file into individual v25.2 SNMP Credentials configurations adhering to the naming convention below
SNMP Version Naming Convention for SNMP Credential configurations created during upgrade
SNMPv1 SNMPv1 <COMMUNITY>

Example:

SNMPv1 public

SNMPv1 notpublic
SNMPv2 SNMPv2 <COMMUNITY>

Example:

SNMPv2 public

SNMPv2 notpublic
SNMPv3 SNMPv3 <AUTH_METHOD> <AUTH_USER> <PRIVACY_METHOD>

Example:

SNMPv3 md5 v3_user_1 aes

SNMPv3 sha512 v3_user_1 des3

Where a configuration would duplicate an existing configuration (same Authentication, user, and privacy but differentiated by password), a number is appended to the configuration name

Example:

SNMPv3 md5 v3_user_1 aes

SNMPv3 md5 v3_user_1 aes 1

SNMPv3 md5 v3_user_1 aes 2

Note: details of which devices are currently assigned a given set of SNMP Credentials are presented in the new SNMP Credentials section of the Admin Tool.

For details on working with the new Discovery system , see:

Discovery related API Changes

The upgrade from v5.6.0 / v5.6.1 to 25.2 includes fundamental API changes relating to the Discovery process and managing IP scan ranges for Discovery. Any scripts that manage Discovery or IP Ranges via the API will need to be updated. See Discovery via the API for details and examples.


Local SNMP Agent Disabled

The operating system underpinning the Statseeker server includes a local SNMP agent, and this agent was disabled in Statseeker v5.6.2. This means that if you are currently monitoring a Statseeker server from another Statseeker server (or 3rd party system) via SNMP, then this monitoring will cease to function upon upgrade to v25.2.

The local SNMP agent can be re-enabled if required, please contact Statseeker Support for assistance.