Index
Important Notes
- 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 restrictions do not apply to existing installations upgrading to v5.6.2 from an earlier version, but will apply when restoring a v5.6.2 (or higher) from backup.
- Physical server hardware requirements depend on the size of the network being monitored and the type and volume of data being collected, stored, and processed
- Statseeker recommends the use of a single large disk or disks configured as RAID 0, RAID 1 or RAID 10
- Please contact our Customer Satisfaction Team at customerservice@statseeker.com for any bespoke Netflow or Syslog requirements as this does affect the server memory/disk configuration when deploying such a solution
- Virtual machine hardware recommendations are designed for deployment on VMware, specific requirements may vary depending on your virtualization platform and environment. In addition:
- The RAM and CPU must be dedicated, not shared resources
- Disks should be thick-provisioned (pre-allocate the required disk-space). We recommend using thick provisioning with most Statseeker installations when running on VMware.
- Network Interface Controller should be VMXNET3
- Boot Firmware must be set to EFI
Hardware Requirements
The information provided details the minimum specifications for a 24-month data retention period.
MonitoredNetwork | ServerRequirements | ||||
Size | Max. Interface Count (*1) | CPU Cores | Memory (*2) | Hard Drive | |
Small | 50,000 | 4-8 | 16GB | 200GB | |
Medium | 100,000 | 4-8 | 32GB | 500GB | |
Large | 250,000 | 8-16 | 32GB-64GB | 1TB (*3) | |
X-Large | 500,000 | 16-32 | 64GB-128GB | 1TB-2TB (*3) | |
Note:
|
Meraki Network Monitoring
If your Statseeker server will also be monitoring Meraki environments, then the following should be considered in addition to the requirements presented above.
- RAM - an additional 2GB will be consumed by Meraki monitoring processes (the size/number of Meraki environments monitored does affect this)
- Data Storage - assume a maximum of 3GB of storage per year per 1000 Meraki interfaces polled
- CPU - Meraki monitoring is not CPU intensive, no additional requirements
Boot Configuration
As of Statseeker v5.6.2 the follow requirements apply to new installations and systems restored 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 restrictions do not apply to existing installations upgrading to v5.6.2 from an earlier version.
Browser Version - Support for Statseeker Web Interface
Statseeker offers a web UI as the primary method for interacting with Statseeker and the data that Statseeker collects. We support the latest stable (non-BETA) versions of:
- Edge
- Firefox
- Chrome
- Safari
The use of older (or less common) browsers may result in the reduced functionality of Statseeker.