Index


Prerequisites

[top]


Download Location & Files

[top]


Important Notes

Discovery Update

Statseeker v5.6.2 features 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 v5.6.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 v5.6.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 v5.6.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:

Note: Statseeker v5.6.2 includes fundamental API changes relating to the Discovery process and managing IP scan ranges for Discovery. Any scripts that manage Discovery or Discovery related IP Ranges via the API will need to be updated, see Discovery via the API for details and examples.

Scheduled Rewalk and Discovery

All existing scheduled Rewalk and Discovery process are migrated with no changes to how they operate.

[top]

Local SNMP Agent Disabled

The operating system underpinning the Statseeker server includes a local SNMP agent, and this agent has been 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 v5.6.2.

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

[top]

Fresh Installs and v5.6.2 Server Restoration

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 v5.6.2, only new installs and v5.6.2 server restorations.

[top]

Additional Items when Upgrading from v5.6.0 -> v5.6.2

Alerting Update

Statseeker v5.6.1 features a substantial Alerting update. The upgrade process automatically updates any existing alerting configurations to the new format where possible.

The new alerting system includes support for HTML email content when using one of the email templates. Existing email alert configurations can be edited to take advantage of this new content after upgrade by setting Mode = HTML.

If you have alert configurations featuring complex regex filters, and the regex cannot be parsed by the upgrade process, then these configurations will not be upgraded. In this instance:

  • The alert configuration is maintained in its original state and will continue to function exactly as it did pre-upgrade
  • The value of the Alert Type field will be appended with (legacy) to indicate a non-upgraded alert
  • The alert configuration cannot be edited, but once an alternate alert is configured (optional, the existing configuration will continue to function), can be disabled or deleted

See Alerting for details on the new alerting system.

MAC-IP Data Collection Update

MAC-IP monitoring and tracking have been updated improving how your MAC-IP data is presented in reports and dashboards, and simplifying the process of tracking MACs as they move through your network.

  • Existing MAC-IP data is not compatible with the new system and will be deleted during the upgrade process
  • Please allow up to 60 minutes from completion of the upgrade process for fresh MAC-IP data to be available in Statseeker

For more information, see MAC-IP Tracking.

SCS Packages

Some custom SCS scripts may be removed during the upgrade process, you will need to reinstall those SCS packages after the upgrade. To access current SCS packages relevant to your version of Statseeker, please contact Statseeker Technical Support.

[top]


Upgrade Procedure

  • Backup your existing data using Administration Tool > Statseeker Administration > Backup/Restore
  • Ensure the backup is stored on a remote location, not locally on the existing Statseeker server
    • Note: for more information on the backup process see Backup and Restore.
  • Login to Statseeker as an Admin user
  • Select Console and confirm that:
    • The current installation is v5.6.v5.6.1 – version information is displayed at the bottom of the Console
    • The current user is admin, or is a user with the Admin role – current user is displayed in the top-right of the console

  • Select Administration Tool > Statseeker Administration > Software Upgrade
  • Click Edit (upper-right)
  • Click Choose File, browse to the location of the stored Statseeker Upgrade image, select it, and click Open
  • Click Upload

A progress bar will be displayed to map the progress of the upload process.

Once the ISO has been uploaded a series of checks against the upgrade requirements are run. In addition, a dry-run of the upgrade process is conducted to highlight any potential impacts on your installation resulting from contents of the upgrade.

The results of the upgrade checks are presented, and any items marked with a warning or failed icon should, prior to proceeding with the upgrade, be reviewed and addressed as needed.

Note: there is no requirement to complete the upgrade process at this point and no changes have been applied to your existing Statseeker installation. You can take the time to review and address failed/warning items as needed and return to the upgrade when ready. If you have any questions regarding the status of any of the upgrade checklist items, please contact Statseeker Technical Support.

If the checklist presents items that require attention, you can click on the associated doc link to view details. Some of these items can be addressed prior to proceeding with the upgrade and others advise a review of the affected element (threshold, report configuration, etc.) post-upgrade.

A complete, detailed report can be downloaded and used as a reference for these items and as a record of the changes made to affected elements as a result of the upgrade process. To download the upgrade report:

  • Click Download Report for an HTML report, or Download Report (gz) for an archived version of the same HTML report

Highlighted items in the upgrade checklist can be addressed and the pre-upgrade check re-run as desired.

When you are ready to proceed with the upgrade:

  • Click Complete Upgrade

If any warning or failed/error items remain in the pre-upgrade checklist a warning dialog is displayed asking you to confirm that you wish to proceed with the upgrade.

  • If you are happy to proceed, click Yes

The upgrade will now commence, during this process the Statseeker server will be unavailable.

[top]


Post-Upgrade Checks

There are a number of checks to be performed once the upgrade process is complete:

[top]


Confirm new version
  • Return to the Console and refresh your browser to confirm that the upgrade process is complete, and that you are running an updated Statseeker version.

The installed version number is displayed below the report list and filters.


[top]


Confirm License Details
  • From the Admin Tool select General > License Key

This will display your current license details.

Review those details and, if you require any changes to License Tier, Device, Interface or Custom Data limits, or feature set, please contact Customer Service.

[top]


Re-apply SCS Packages

The dry-run of the upgrade, which you will have run prior to the upgrade itself, will have highlighted any potential impacts to existing Statseeker Custom Script (SCS) packages.

  • Review your installed SCS packages after the upgrade and re-apply as required

[top]

Apply Service Packs

The currently available service pack for v5.6.2 is:

5.6.2 Service Pack 1.0.3(scs_service_pack_5_6_2-1.0.3.scs)

System & Administration fixes:

  • Fixes sporadic data gaps on very large Statseeker configurations due to slow poller load times after a configuration change
  • Fixes sporadic data gaps on SNMPv3 devices from the first SNMP packet received after a configuration change.
  • Fixes validation on device names with underscores in the manual device add page in the admin tool.
  • Fixes issues when adding/updating/deleting devices which have mappings to IPv6 addresses
  • Fixes issue where existing IPv4 entries in the hosts file could cause discovery of IPv6 entries to fail
  • Fixes an issue where API calls fail when filtering on a linked field
  • Fixes an issue where SNMP credentials fail to upgrade correctly
  • Fixes an issue where Ping discover exits ungracefully when no new devices are found

Dashboard fixes:

  • Addresses a dashboard graph display issue when presenting ‘ping lost’ data in addition to other data series

[top]

Backup Your Upgraded Server

Backup files from earlier versions may not have the required data structure to work correctly with your updated Statseeker server. Once an upgrade has been completed, it is strongly advised that a backup be created.

See Backup and Restoration Process for details.

[top]