Vunetrix Manual: System Administration—Core & Probes

When a New Version is Available

Define how Vunetrix will react to available software updates. This option will be used with the Auto Update function. Choose between:

• Automatically download and install the latest version: Any new Vunetrix version will be downloaded and installed automatically as soon as your installation detects that there is a newer version available (a check is performed once per day). Note: Without prior notice, installation will restart the Vunetrix Windows services and may also include a server restart.
• Automatically download the latest version and alert the admin: Any new Vunetrix version will be downloaded automatically as soon as your installation detects that there is a newer version available (a check is performed once per day). After successful download, Vunetrix will create a ToDo message for the administrator.

• Alert the admin only: When Vunetrix detects that there is a newer version available, it will not download updates automatically, but create a ToDo message only. You can still download updates manually on the Auto Update page.

Installation Time

If you have select the automatic installation option above, choose the desired time for updates from the drop-down menu.

Release Channel

Vunetrix updates are delivered in different release channels. You can choose between maximum stability, or most early access to new features. Please choose between:

• Stable: Updated about once per month (most conservative option, recommended): These are our best tested versions. Choose this channel for live environments you have to depend on!
• Preview: Updated about once per week: Versions in this channel are already thoroughly tested in our labs, but may still contain limitations in certain monitoring configurations. Choose this channel if you are willing to take a little risk for the benefit of getting new features and bug fixes a little earlier.
• Canary: Updated daily (testing only, should not be used on live systems): Updated every night. Use with CAUTION! Software versions in this channel are not tested yet, might contain severe bugs, and are provided for testing purposes only. We strongly recommend to not use those versions in live environments you have to depend on!

For more information about the different release channels, please see the blog article linked in the More section below.

Use Proxy Server

We recommend using Vunetrix with a direct internet connection. However, if you need to use a proxy, you can configure according settings here. Choose between:

• No, use direct connection to the Internet (default): Do not use a proxy. Use this setting if there is a direct internet connection available to the server running the Vunetrix core server.

• Yes, in our network a proxy is mandatory: Define proxy settings below.

Note: Proxy settings are valid for Auto-Update, Activate the Product, obtaining Geo Maps tiles, and for sending out HTTP and SMS text message Notifications.

Proxy Server

This setting is only visible if proxy usage is enabled above. Enter the address of the proxy server that will be used for outbound connections. Please enter a valid address.

Port

This setting is only visible if proxy usage is enabled above. Enter the port of the proxy server that will be used for outbound connections. Please enter an integer value.

Use Proxy Credentials

This setting is only visible if proxy usage is enabled above. Determine whether the proxy server needs credentials. Choose between:

• Yes: Define credentials below.
• No: Do not use credentials for proxy connections.

Username

This setting is only visible if proxy credentials are enabled above. Enter a username for proxy authentication. Please enter a string.

Password

This setting is only visible if proxy credentials are enabled above. Enter a password for proxy authentication. Please enter a string.

Probe Connections IPs

Define how Vunetrix will handle incoming connections from probes. Choose between the following options:

• Local Probe only, 127.0.0.1 (Vunetrix will not be accessible for Remote Probes): This is the default setting. Only local probe connections will be accepted by the Vunetrix core server. You cannot use remote probes with this setting enabled.
• All IPs available on this computer: Use all IP addresses available on this computer and enable access to the core server for all of these addresses.
• Specify IPs: Incoming connections from remote probes will only be accepted on the selected IP address(es) of the core server. In the list, select the IP addresses by adding a check mark in front the IPs. You can also select and deselect all addresses by clicking on the check box in the table header.

Note: If you change this setting, Vunetrix needs to restart the core server. Because of this, all users of Vunetrix's web interface, of the Enterprise Console, or of Smartphone Apps will be disconnected. After clicking on the Save button, a popup will appear which asks you to confirm the required core server restart. Click on OK to trigger the restart and follow the instructions on the screen.

Probe Connection Port

Define on which TCP port number Vunetrix listens to for incoming probe connections. Enter a port number. We recommend using the default value.

Note: If you change this setting, Vunetrix needs to restart the core server. Because of this, all users of Vunetrix's web interface, of the Enterprise Console, or of Smartphone Apps will be disconnected. After clicking on the Save button, a popup will appear which asks you to confirm the required core server restart. Click on OK to trigger the restart and follow the instructions on the screen.

Access Keys

Enter a list of access keys, one in each line. Every (remote) probe that wants to connect to this Vunetrix installation has to use one of these keys. For information how to set this key for a probe, please see Vunetrix Probe Administrator (Probe Settings) section.

Allow IPs

Enter a list of remote probe IPs that will be accepted when connecting to this Vunetrix installation; each IP address in one line. The local probe (127.0.0.1) is always allowed automatically. Allowed IPs are checked first (before denied IPs). You can use Vunetrix's syntax for IP address ranges here (for information about the syntax please see Define IP Ranges section).

• [Empty]: An empty field does not allow any remote probes (but only the local probe). Please enter IP addresses to allow remote probe connections.
• any: Enter the word any to automatically allow all remote probe connections. Note: This is recommended for use in Intranets only!

Note: If the IP address of your remote probe changes regularly (e.g. due to an internet provider assigning IP addresses dynamically), please enter the potential IP range for this remote probe or use the any option.

Deny IPs

Enter a list of remote probe IPs that will not be accepted when connecting to this Vunetrix installation; each IP address in one line. This is useful to explicitly deny connections from certain remote probes you do not want to include in your setup any more (e.g., for a certain time). Access to IP addresses allowed above will be denied if you enter them here. This is useful to allow access to an IP range in the field above, but deny access to a single IP address. You can use Vunetrix's syntax for IP address ranges here (see Define IP Ranges section).

Deny GIDs

Enter a list of GIDs, each global ID (GID) in one line. The access to matching GIDs will be denied. If you remove a remote probe from the device tree or if you deny a remote probe after installation, its global ID (GID) will be automatically entered here. This specific remote probe will not be able to connect anymore. Denying GIDs is more precise than denying IPs, where other remote probes at the same location could be excluded too.

Mini Probes

Define if Mini Probes will be able to connect to your Vunetrix server. If you want to use Mini Probes, you must allow them to connect. Choose between:

• No Mini Probes
• Allow Mini Probes to connect

See the Vunetrix API for the Mini Probe documentation.

Note: If you change this setting, Vunetrix needs to restart the core server. Because of this, all users of Vunetrix's web interface, of the Enterprise Console, or of Smartphone Apps will be disconnected. After clicking on the Save button, a popup will appear which asks you to confirm the required core server restart. Click on OK to trigger the restart and follow the instructions on the screen.

Domain Name

In order to use Active Directory Integration please enter the name of your local domain. Please enter a string or leave the field empty.

Access Type

Define which user account will be used to configure Active Directory access. This account will be used to query the AD for existing groups. Choose between:

• Use the Vunetrix core service account (usually LOCAL SYSTEM): Use the same Windows user account configured for the "Vunetrix Core Server Service". In a default installation, this is the "local system" Windows user account. If this account does not have the right to query all groups of your Active Directory you should not use this option.

• Use explicit credentials: Define a user account that will be used by Vunetrix to authenticate against the Active Directory. This should be a user account with full access to all of your Active Directory groups.

Access User

This field is only visible if the use of explicit credentials is chosen above. Enter the Windows user account name which will be used to authenticate for Active Directory configuration.

Access Password

This field is only visible if the use of explicit credentials is chosen above. Enter the password for the Windows user account which will be used to authenticate for Active Directory configuration.

Data purging enables you to automatically delete unnecessary data to free up disk space and improve system performance. You can define different time spans for several kinds of data. Select here for how many days historic data remains accessible. For further information on storage locations, please see Data Storage section.

Logfile Records

Define how long records in the system logfile Log Database.db will be kept. Enter a value in days. All entries older than this value will be deleted from the log file automatically. Keep this value as low as possible to enhance system performance.

Web Server Log Records

Vunetrix creates one web server log file every day. Define how many web server log files will be kept. Enter a value in days. All web server log files files older than this value will be deleted automatically.

Historic Sensor Data

Define for how many days historic sensor data will be kept for all sensors. It is used to create reports of monitoring data. Enter a value in days. Depending on the used intervals and the number of sensors in your setup, the file containing this data can become large. For smaller installations (500 sensors or less) a value of 365 should be fine. Historic sensor data is the basis for reports on monitoring data. If you decrease this value, there will be less historic monitoring data available!

Toplist Records

Define how long toplist records for Flow and Packet Sniffer sensors will be kept. Enter a value in days. We recommend using 30 days here.

Closed Tickets

Define how long tickets which are in status closed will be kept. Enter a value in days.

Reports

Reports generated in PDF format are stored on disk for later reference. Define the maximum age for these reports. Enter a value in days. All reports older than this value will be deleted automatically.

Configuration Auto-Backups

Vunetrix creates one backup of your configuration every day. Define the maximum age for these backups. Enter a value in days. All configuration backup files older than this value will be deleted automatically.

Full HTTP Sensor Screenshots

Define how long the screenshots of the HTTP Full Web Page Sensor (PhantomJS browser engine) will be kept. Enter a value in days. Vunetrix will delete older screenshots with every sensor scan.