* Legacy Documentation for Installing Statseeker v5.5.4 *

Index

Download Location and File

New & Existing customers: please contact your Regional Sales Manager prior to attempting any new installations.

[top]

Important Notes

Unsupported Configurations

As of version 5.3, Statseeker requires CPUs which support the SSE4.2 instruction set, see System Requirements for details

Statseeker does NOT support the following configurations for physical (non-VM) installations:

  • Raid 5
  • Raid 6
  • SAN Drives

Virtualized Installations

Statseeker supports virtualized installations, recommending VMware ESXi version 5 and above.

Whether installing on a VM or migrating to a VM, the VM specifications should be equivalent to those specified for a physical installation, see Version 5.x System Requirements for details.

In addition:

  • The Operating System (OS) being installed will be FreeBSD, 64bit, specify this OS if prompted (if this option is not available then select Other, 64bit)
  • The RAM and CPU must be dedicated, not shared resources
  • The installation drive should be thick-provisioned that is, pre-allocate the required disk-space. The dynamic allocation provided via thin-provisioning could potentially produce performance issues with most Statseeker installations and if disk space over-subscription occurs, this will impact the Statseeker server directly.
Note: if you are running Statseeker on an VM, it is strongly advised that you do not use VM snapshots as an alternative to Statseeker backups. For more information on this, see Backup and Restore: Virtual Machine Snapshots.

Installation Drive
  • All data on the drive will be deleted during a new install
  • See Version 5.x System Requirements for more information on installation drive requirements
  • If installing on a server with multiple drives, ensure that there is no other instance of Statseeker installed on the server
Note: avoid multiple Statseeker installations on a single server.

User Accounts

The installation process will create the following administrative system accounts:

  • admin – the web user administrator account
  • statseeker – the system user account used by the Statseeker application
  • root – the superuser account in the backend operating system

You will be prompted to provide the root user password during the installation process. This password will become the default password for both the admin and statseeker accounts. This password can be changed after the installation process via:

  • The command line ssadmin tool
  • The web interface in the Administration Tool, see Admin Tool > Statseeker Administration > OS Configuration

[top]

Prerequisites

A Valid Server ID Number

The Server ID is used during the installation process to produce your License Key. To obtain a Server ID, either:

Installation Media

Contact your Regional Sales Manager for access to the Statseeker installation media (ISO/IMG) image file appropriate for your license. Once this file has been downloaded:

  • CD/DVD: use 3rd party software to burn the ISO/IMG image file to disc
  • USB: use 3rd party software to convert the USB and ISO/IMG to bootable drive
  • VM: request the *.iso file from Statseeker support to ensure compatibility with your destination platform

Configuration Information

You will also need to provide, or define, the following information during the install process:

  • The root user password for the server
  • A host name for the server
  • A domain name suffix for the server
  • Static IP (IPv4 is required, optionally include IPv6), Netmask and Default Gateway addresses for the server
  • The IP address of your Domain Name Server
  • The SNMP read access community string to your devices (routers, switches, servers, etc.)

[top]

Install Process

CD/DVD/USB Installation
  • Configure the BIOS time and time zone as desired
  • Set the boot sequence:
    • Installation media as first boot preference
    • Installation destination drive as secondary boot preference
  • Connect the server to your LAN as needed
  • Insert installation media
  • Boot the server
VM Installation
  • Configure the VM
  • Mount the ISO
  • Launch the VM

The FreeBSD welcome screen will be displayed.

su ssadmin

When launching ssadmin for the first time you may be prompted to confirm server settings.

_install_screen_

,

tunefs -t enable {File System}
Example: tunefs -t enable /dev/ada0p2

.png" />

  • Press Enter to continue with the installation

Some basic hardware/system compatibility checks are run, and if any aspect of your system does not meet minimum requirements:

  • An error message detailing the failed check will be displayed
  • Installation will not proceed

If all system checks pass, the Statseeker Welcome screen is displayed.

su ssadmin

When launching ssadmin for the first time you may be prompted to confirm server settings.

_install_screen_2.png" />

  • Press Enter to continue with the installation

If you have multiple hard disks, the Installation Disk Selection screen is displayed.

Note: This screen will only be presented if you have multiple disks configured or if you have a RAID configuration and a separate disk.tunefs -t enable {File System} Example: tunefs -t enable /dev/ada0p2 .png"/>

  • Select the disk you want to use, select OK and press Enter

The data wipe alert is displayed; continuing with the installation will delete all data on the hard disk.

su ssadmin

When launching ssadmin for the first time you may be prompted to confirm server settings.

_install_screen_3.png" />

  • Press Enter to continue with the installation

The server timezone prompt is displayed.

su ssadmin

When launching ssadmin for the first time you may be prompted to confirm server settings.

_install_screen_5.png" />

  • If you are certain that the CMOS clock is set to UTC, then select Yes, otherwise select No
  • Select the time zone region

su ssadmin

When launching ssadmin for the first time you may be prompted to confirm server settings.

_install_screen_6.png" />

  • Select the time zone

su ssadmin

When launching ssadmin for the first time you may be prompted to confirm server settings.

_install_screen_7.png" />

  • Select Yes to confirm the time zone configuration

su ssadmin

When launching ssadmin for the first time you may be prompted to confirm server settings.

_install_screen_8.png" />

The Date configuration screen is presented, either Skip, or:

  • Configure the month, year, and day-of-month and select Set Date

The Time configuration screen is presented, either Skip, or:

  • Configure the time and select Set Time

A prompt will be displayed asking you to set the password for the server root account.

Note: This password will become the default password for both the admin and statseeker user accounts.


su ssadmin

When launching ssadmin for the first time you may be prompted to confirm server settings.

_install_screen_9.png" />

  • Enter the password and press Enter
  • Repeat this to confirm the password

The installation process will proceed to Network Configuration.

Note: Statseeker's primary interface must be assigned an IPv4 address, an additional IPv6 address can also be assigned if needed, and additional interfaces can be configured with either an IPv4 or IPv6 address.
  • Select the network interface to be used to connect the Statseeker server to the LAN, select OK and press Enter

su ssadmin

When launching ssadmin for the first time you may be prompted to confirm server settings.

_install_screen_

,

tunefs -t enable {File System}
Example: tunefs -t enable /dev/ada0p2

,

tunefs -t enable {File System}
Example: tunefs -t enable /dev/ada0p2

.png" />

You will be asked if you would like to use DCHP to configure your primary Statseeker server interface.

Note: IPv6 DHCP is NOT SUPPORTED. If your DHCP server is going to return an IPv6 address then you will need to manually configure the interface, assigning an IPv4 address. An additional IPv6 address can also be configured on the same interface if needed, but Statseeker requires an IPv4 address.

For DHCP:

  • Select Yes and press Enter

For manual interface configuration:

  • Select No and press Enter

Manual Interface Configuration

  • Use the arrow keys to navigate through the dialog and set the IP Address, Subnet Mask and Default Router
  • Use the Tab key to select OK and press Enter

The IPv6 configuration option is displayed. If you do not wish to assign and IPv6 address to the interface, select No and proceed, otherwise:

  • Select Yes, displaying the IPv6 configuration screen
  • Specify the IPv6 address you wish to employ
  • Set the default IPv6 router
  • Use the Tab key to select OK and click Enter

IPv6 Address Syntax

Statseeker supports standard IPv6 address formats:

  • Full address - 2
    
    

    ,

    su
    ssadmin
    
    

    When launching ssadmin for the first time you may be prompted to confirm server settings.

    
    

    ,

    su
    ssadmin
    
    

    When launching ssadmin for the first time you may be prompted to confirm server settings.

    
    

    ,

    tunefs -t enable {File System}
    Example: tunefs -t enable /dev/ada0p2
    

    :

    
    

    ,

    su
    ssadmin
    
    

    When launching ssadmin for the first time you may be prompted to confirm server settings.

    db8:85a3:

    
    

    ,

    su
    ssadmin
    
    

    When launching ssadmin for the first time you may be prompted to confirm server settings.

    
    

    ,

    su
    ssadmin
    
    

    When launching ssadmin for the first time you may be prompted to confirm server settings.

    
    

    ,

    su
    ssadmin
    
    

    When launching ssadmin for the first time you may be prompted to confirm server settings.

    
    

    ,

    su
    ssadmin
    
    

    When launching ssadmin for the first time you may be prompted to confirm server settings.

    :

    
    

    ,

    su
    ssadmin
    
    

    When launching ssadmin for the first time you may be prompted to confirm server settings.

    
    

    ,

    su
    ssadmin
    
    

    When launching ssadmin for the first time you may be prompted to confirm server settings.

    
    

    ,

    su
    ssadmin
    
    

    When launching ssadmin for the first time you may be prompted to confirm server settings.

    
    

    ,

    su
    ssadmin
    
    

    When launching ssadmin for the first time you may be prompted to confirm server settings.

    :8a2e:

    
    

    ,

    su
    ssadmin
    
    

    When launching ssadmin for the first time you may be prompted to confirm server settings.

    37

    
    

    ,

    su
    ssadmin
    
    

    When launching ssadmin for the first time you may be prompted to confirm server settings.

    :7334

  • Leading zeros omitted - 2
    
    

    ,

    su
    ssadmin
    
    

    When launching ssadmin for the first time you may be prompted to confirm server settings.

    
    

    ,

    su
    ssadmin
    
    

    When launching ssadmin for the first time you may be prompted to confirm server settings.

    
    

    ,

    tunefs -t enable {File System}
    Example: tunefs -t enable /dev/ada0p2
    

    :db8:85a3:

    
    

    ,

    su
    ssadmin
    
    

    When launching ssadmin for the first time you may be prompted to confirm server settings.

    :

    
    

    ,

    su
    ssadmin
    
    

    When launching ssadmin for the first time you may be prompted to confirm server settings.

    :8a2e:37

    
    

    ,

    su
    ssadmin
    
    

    When launching ssadmin for the first time you may be prompted to confirm server settings.

    :7334

  • Empty group replacement - 2
    
    

    ,

    su
    ssadmin
    
    

    When launching ssadmin for the first time you may be prompted to confirm server settings.

    
    

    ,

    su
    ssadmin
    
    

    When launching ssadmin for the first time you may be prompted to confirm server settings.

    
    

    ,

    tunefs -t enable {File System}
    Example: tunefs -t enable /dev/ada0p2
    

    :db8:85a3::8a2e:37

    
    

    ,

    su
    ssadmin
    
    

    When launching ssadmin for the first time you may be prompted to confirm server settings.

    :7334

While any number of consecutive empty groups can be collapsed to the double colon replacement (::), only a single instance of this replacement can be used in an address. Address range statements for IPv6 addresses are not supported.

  • Set the Hostname of the server, including the domain suffix (requires a fully-qualified domain name) and press Enter

  • Use the arrow keys to navigate through the dialog and set the Domain and DNS configuration
  • Use the Tab key to select OK and press Enter

Statseeker will now install all required packages and reboot.

su ssadmin

When launching ssadmin for the first time you may be prompted to confirm server settings.

_install_screen_

,

tunefs -t enable {File System}
Example: tunefs -t enable /dev/ada0p2

6.png" />

After installation is complete a login prompt will be displayed.

su ssadmin

When launching ssadmin for the first time you may be prompted to confirm server settings.

_install_screen_

,

tunefs -t enable {File System}
Example: tunefs -t enable /dev/ada0p2

8.png" />

Enable TRIM for all file systems (only required for installation to SSD)

Only enable TRIM on SSD's which not support it, refer to your drive specifications for confirmation of TRIM support.

If Statseeker deployment is to a physical server and the installation drive is an SSD, then TRIM should be enabled for all file systems. If this does not apply to you, proceed to the next step, otherwise:

  • Login as the statseeker user, when prompted provide the password specified during installation
  • Switch to the root user account (same password)
  • reboot the server via the ssadmin utility

,

su
ssadmin

When launching ssadmin for the first time you may be prompted to confirm server settings.

>

  • From within ssadmin select:
    • 8. Operating System
    • 2. Reboot server
  • Enter sduring the boot countdown to access single user mode
  • enable TRIM on each filesystem with:

,

tunefs -t enable {File System}
Example: tunefs -t enable /dev/ada0p2

>

  • Reboot the server with reboot

Once the CLI displays the login prompt:

  • Do not log in, rather move on to the Web Installation Wizard

[top]

Web Installation Wizard

Once Statseeker is installed you can access the web interface, to do this:

  • Enter the server IP address, which you configured for the server, in your browser URL

By default, the Statseeker web server will use HTTPS in conjunction with a self-signed certificate. Modern browsers will view self-signed certificates as potentially suspect and post an alert prior to loading the Statseeker interface for the first time. To suppress any future alerts for that specific certificate:browser combination:

  • Follow the browser prompts to acknowledge the risk and add an exception for the certificate

For details on how to upload and use alternative SSL certificates, or configure the server to use HTTP instead, see Web Server Configuration.

You will then be prompted with a login screen.

  • Select Sign in with username/password
  • User Name - admin
  • Password - the root user account password as specified during installation

Once logged in to the web interface, you will be prompted with the Statseeker License configuration screen.

  • Enter your Server ID and select Download a new Key
Note: to obtain a Server ID, contact your Regional Sales Manager.

It may take a minute or two to obtain your license key.

  • Select the checkbox to accept the Statseeker license
  • Select Save to activate the license key

su ssadmin

When launching ssadmin for the first time you may be prompted to confirm server settings.

_install_screen_2

,

su
ssadmin

When launching ssadmin for the first time you may be prompted to confirm server settings.

.png" />

The screen will update to display the license details.

su ssadmin

When launching ssadmin for the first time you may be prompted to confirm server settings.

_install_screen_2

,

tunefs -t enable {File System}
Example: tunefs -t enable /dev/ada0p2

.png" />

  • Click Next
Multi-Disk Servers

If your Statseeker server has multiple disks you will be given the option to assign another disk as the repository for Statseeker data. This screen will only be displayed if Statseeker detects more than one disk.

Prepare Secondary Disk for Statseeker Data

Optionally, you can store all Statseeker data on another disk on the server. Assigning a disk as the repository for Statseeker data will delete all current content on the disk.

To store Statseeker data on a second disk:

  • Select the disk that will act as the Statseeker data repository - all existing data on this drive will be erased
  • Click Save and Continue, then confirm the decision when prompted

You may need to re-authenticate with the server once this process has been completed.

You will now be presented with the Server Summary screen, containing a range of details pertinent to your Statseeker installation.

tunefs -t enable {File System} Example: tunefs -t enable /dev/ada0p2 .png"/>

Edit Server Date/Time

To edit the server date/time settings:

  • Click the associated Edit link on the Server Summary page
  • Use the calendar control to edit the date and/or time
  • Use the drop-downs to modify the timezone for the server
  • Click Save when done

Note: adjusting the server date or time will require a server restart to apply the changes. On clicking the Save button you will be prompted to confirm your action. Clicking Yes in the confirmation modal will restart your Statseeker server.

The configuration changes will be saved, and the server will be restarted to apply those changes.


Once the changes have been applied you will be returned to the Date/Time/NTP Configuration screen (in Display mode) to confirm that the changes have been applied correctly.


[top]

Edit NTP Configuration

To edit the NTP server settings:

  • Click the associated Edit link on the Server Summary page
  • Enter the address of the NTP server to use
  • Click the associated Delete button to remove unwanted NTP server entries
  • Click Save when done

When you click Save Statseeker will attempt to contact the specified NTP servers and:

  • Inform you if it is unable to receive a response from the NTP server, no changes have been applied at this point
  • If it receives a valid response from the NTP server, apply the changes and return the Date/Time/NTP Configuration screen (in Display mode) and enable a Test button that can be used to confirm the validity of the current configuration.


[top]

Configure an HTTP Proxy Connection

To add or edit the HTTP proxy configuration:

  • Click the Network > Edit link on the Server Summary page
  • Enter the required proxy server details
  • Click Save to apply the configuration


[top]

Edit the Network Configuration

To edit the existing network configuration:

  • Click the Network > Edit link on the Server Summary page
  • Enter the required details
  • Click Save to apply the configuration


[top]

Edit Interface Configuration

To edit the existing network configuration:

  • Click the associated Edit link on the Server Summary page
  • Click Edit to reconfigure the interface, optionally click Clear to remove the current configuration before editing

  • Enter the required details
  • Click Save to apply the configuration
  • Click Close to return to the Server Summary


[top]

Run Network Discovery

Statseeker's network discovery process is used to add networked devices, interfaces, and other SNMP enabled components on your network to Statseeker. Statseeker can then collect configuration information and timeseries data from those devices to be used for polling, reporting, and alerting purposes. There are several methods that can be used to direct the discovery process towards the devices on your network that you want Statseeker to report on:

  • Discover Using Ranges (IPv4) - specify one or more IP address ranges and discover all devices responding to SNMP within that range
  • Discover Using Hosts (IPv4/IPv6) – add and entry for the device to the hosts file, and run a Discover Using Hosts
  • Add Single Device (IPv4/IPv6) – use the Add Single Device option to individually add IPv6 devices
  • Add SNMPv3 Device (IPv4/IPv6) – single or batch addition of SNMPv3 devices
  • Ping-Only (IPv4/IPv6) – add an IPv6 device to be monitored via ping, but not SNMP

For details on these discovery methods, see Statseeker Network Discovery.

IPv6-Only Networks

The Discovery option available from the installation screen is limited to Discovery Using Ranges, so it is not compatible for IPv6-only networks. For IPv6-only networks:

  • Select Finish Setup
  • Select the Admin Tool from the main navigator and discover your network using one of the other discovery options, see Statseeker Network Discovery for details.

IPv4 Network Discovery

  • Click Network Discovery

tunefs -t enable {File System} Example: tunefs -t enable /dev/ada0p2 .png"/>

  • Click Start Discovery

su
ssadmin

When launching ssadmin for the first time you may be prompted to confirm server settings.

_install_screen_22.png" />

  • Enter the SNMP Community Strings for the devices that you want Statseeker to discover. Multiple community strings may be specified, one per line.
  • Define the Network Discovery Ranges that you wish Statseeker to query

Once the discovery process is active and running, you will be presented with an in-product video highlighting the discovery process. There is a progress wheel in the bottom left-hand corner of the screen that will indicate when the discovery process is complete.

Note: The Discovery Process can take some time to complete, this being dependent upon factors such as the size, speed and responsiveness of the network and devices.
  • Once the discovery process has completed, click Finish Setup

The Statseeker Dashboard Homepage will be displayed providing access to the default dashboards as well as a news panel detailing recent updates with links to associated documentation and videos. The main Statseeker Console and reporting panels are available from the main navigator.


[top]