Vunetrix Manual: System Administration—User Interface

Vunetrix Site Name

When using the web interface, the site name is shown in the title bar of your browser window. It is also used by default in notification emails. Please enter a string.

DNS Name

If your Vunetrix web interface is (additionally) reachable via a DNS name, please enter it here. It is e.g. used by default in notification emails to generate links. Please enter a string.

Website Language

Choose the system language from the drop down menu. Default is English. Depending on your installation, you may be able to choose other languages here. This setting will influence the language of the Ajax and the Mobile Web GUI web interfaces, as well as of the Vunetrix System Administration Tools.

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.

Graph Type

Select how graphs will be displayed throughout the web interface and in reports.

• Use area charts (recommended): Display filled graphs.
• Use line charts: Display graphs using single lines only.

We recommend using area charts, as they're better to read. Note: Graphs containing data from more than one cluster node will always be displayed with line charts automatically.

Map Service Provider

Select if and how you want to integrate the Geo Maps feature into the web interface. If enabled, Vunetrix uses the first line of the location setting of an object to show it on a geographical map. Please choose a map provider:

• Do not show maps (disables Geo Maps integration): Disable Geo Maps integration and do not show geographical maps in the web interface.
• MapQuest: Use MapQuest to show geographical maps. This is the recommended option.
• Nokia Maps: Use Nokia Maps to show geographical maps.
• CloudMade (API key required): Use CloudMade to show geographical maps. Please sign up for an API key on their developer website to use this service.
• Google Static Maps (API key required): Use Google Static Maps to show geographical maps. Please sign up for a Google Maps API v2 key to use this service. Note: As of Vunetrix version 13 you will need to acquire a Google Maps API v3 key!

For more information about the different map providers, please see the More section below.

Map Type

This setting is only visible for some map providers. Depending on the chosen provider, several options are shown. Each will show map tiles in a different appearance. Please choose a map type from the list.

API Key (required)

This field is only visible if you selected a provider that requires an API key. Please obtain your personal key and paste it here. For more information on how to get an API key, please see the More section below. Please enter an alphanumeric string.

Performance Strategy

Select if you want to enable performance improvements for the web interface.

• All Features: Show all features and live data (recommended): Provide full functionality and show all menu items.
• More Speed: Limit features and delay display (experimental): Improve reaction time and speed of the web interface by delaying display of monitoring data and hiding some features.

For more information on how to speed up the web interface, please see More section below.

IP Address for Web Server

Vunetrix is running a web server in order to provide access via the web and Windows interface. Please specify which IP address this web server will run on. Note: Later, you can log into Vunetrix by simply pointing your browser to the specified IP address.

Choose between:

• Localhost, 127.0.0.1 (Vunetrix will not be accessible from other computers): Use 127.0.0.1 only. Vunetrix's web and Windows interface will only be accessible from the computer Vunetrix is installed on.
  Note: Either the selected port or at least one port in the range from 8080 to 8089 has to be available on 127.0.0.1.

Note: If you run Vunetrix on localhost, please do not use the DNS name http://localhost to log in to the web server, as this may considerably slow down Vunetrix's web interface. Please use your local IP address or http://127.0.0.1 instead.

• All IPs available on this computer: Use all IP addresses available on this computer and enable access to the web server for all of these addresses. Note: The TCP port selected below must be free on every available IP address.
• Specify IPs: Select specific IP addresses on which the Vunetrix Web server will run on. A list specific to your system is shown. Add a check mark in front of every IP address you want the Vunetrix web server to be available at. You can also select and deselect all addresses by clicking on the check box in the table header.
  Note: Either the selected port or at least one port in the range from 8080 to 8089 has to be available on the specified IP address.

Note: Regardless of the selected setting above, one port in the range from 8080 to 8180 has to be available on the specified IP address so Vunetrix can create reports. The report engine will try to connect to the core server on one of these ports.

Note: If Vunetrix does not find a network card on startup it will switch the IP setting to Localhost. This setting will remain, even if a network card is available later on. If you disabled or removed the network card on the machine running the Vunetrix core server, please re-check this setting.

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.

TCP Port for Web Server

Vunetrix is running a web server in order to provide the web and Windows interface. Please specify on which port this web server will run. Choose between:

• Secure HTTPS server (recommended, mandatory for internet access): This is the recommended setting and needed to access the Vunetrix server via the internet. Use a secure HTTPS connection that is encrypted via SSL on port 443.
  Note: Although the connection is secure, you will see an SSL Certificate Warning in your browser when logging in to the Vunetrix web interface, because the default certificate is unknown to your browser. You can install another SSL certificate for Vunetrix later. Please see Using Your Own SSL Certificate.
  Note: If port 80 is free, Vunetrix will reserve it as well. When users try to connect on port 80 via HTTP, they will then be redirected to port 443 via HTTPS. You can change this behavior using a registry setting.
• Insecure HTTP server (standard port 80, not recommended): Use a standard web server without SSL encryption on port 80. This setting is not recommended for WAN connections.
  Note: If used on the internet, attackers could potentially spy on credentials you enter into Vunetrix. We strongly recommend using this option in a LAN only.
• Expert configuration: This setting allows you to specify a custom web server port and the security of the connection. This option is intended for systems with an existing web server on the standard port. Define port and encryption below.

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.

Web Server Port

This setting is only visible if the expert configuration is selected above. Enter the desired TCP port number you want the Vunetrix web server to run on. Please enter an integer value.

Note: If you use a secure connection and port 80 is free, Vunetrix will reserve it as well. When users try to connect on port 80 via HTTP, they will then be redirected to the custom port via HTTPS. You can change this behavior using a registry setting.

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.

Web Server Security

This setting is only visible if the expert configuration is selected above. Specify if you want to use an SSL encryption. Choose between:

• Use SSL encryption (HTTPS): Use a secure HTTPS connection that is encrypted via SSL on a custom port as defined above.
  Note: Although the connection is secure, you will see an SSL Certificate Warning in your browser when logging in to the Vunetrix web interface, because the default certificate is unknown to your browser. You can install another SSL certificate for Vunetrix later. Please see Using Your Own SSL Certificate.
• Don't use encryption (not recommended): This setting is not recommended for WAN connections. Use a standard web server without SSL encryption on a custom port as defined above.
  Note: If used on the internet, attackers could potentially spy on credentials you enter into Vunetrix. We strongly recommend using this option in a LAN only.

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.

Currently Active IP Address/Port Combination(s)

Shows all currently active combinations of IP addresses and ports on which the Vunetrix server listens for web requests. This setting is shown for your information only and cannot be changed here.

Note: Vunetrix internally uses port 8085 for report generation.

Vunetrix shows several graphs in the objects' detail pages in the web interface. These are kept in RAM memory for fast display without causing extra CPU load or disk usage. The longer the time frames and the shorter the intervals are, the more memory will be used for this. You can adapt the details for all four graphs. This setting will also change the caption of the objects' tabs in the web interface and Enterprise Console.

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.

Live Graph

The live graph is available for sensors only. For the live graph, no fixed time span is given, but you can define how many values will be displayed. The actual time span covered by the live graph depends on the scanning interval set for the sensor you're viewing and is calculated automatically. By default, 120 Values is set, which results in a graph covering a time span of two hours, if a scanning interval of 60 seconds is set for the sensor. Other scanning intervals will result in graphs covering different time spans. Choose between:

• 60 Values: This corresponds to a live graph covering a time span of one hour if a 1 minute scanning interval is set. Uses least RAM memory. We recommend this setting for installations with 10,000 sensors or more.
• 120 Values: This corresponds to a live graph covering a time span of two hours if a 1 minute scanning interval is set.
• 240 Values: This corresponds to a live graph covering a time span of four hours if a 1 minute scanning interval is set.
• 480 Values: This corresponds to a live graph covering a time span of eight hours if a 1 minute scanning interval is set.
• 960 Values: This corresponds to a live graph covering a time span of 16 hours if a 1 minute scanning interval is set. Uses most RAM memory.

Graph 1

By default, this is the 2 days graph in the web interface. You can change it to more or less detail by choosing a time span and a monitoring interval average associated with it. Monitoring results will be averaged regardless of the actual scanning interval set for the sensors. Choose between:

• 1 day with 1 minute averages: Results in 1440 values.
• 1 day with 5 minutes averages: Results in 288 values.
• 1 day with 15 minutes averages: Results in 96 values. Uses least RAM memory. We recommend this setting for installations with 10,000 sensors or more.
• 2 days with 1 minute averages: Results in 2880 values. Uses most RAM memory.
• 2 days with 5 minutes averages: Results in 576 values.
• 2 days with 15 minutes averages: Results in 192 values.
• 4 days with 1 hour averages: Results in 96 values. Uses least RAM memory. We recommend this setting for installations with 10,000 sensors or more.

Graph 2

By default, this is the 30 days graph in the web interface. You can change it to more or less detail by choosing a time span covered and a monitoring interval average associated with it. Choose between:

• 10 days with 1 hour averages: Results in 240 values.
• 20 days with 1 hour averages: Results in 480 values.
• 30 days with 1 hour averages: Results in 720 values.
• 30 days with 6 hour averages: Results in 120 values. Uses least RAM memory. We recommend this setting for installations with 10,000 sensors or more.
• 40 days with 1 hour averages: Results in 960 values.
• 40 days with 6 hour averages: Results in 160 values.
• 60 days with 1 hour averages: Results in 1440 values. Uses most RAM memory.
• 60 days with 6 hour averages: Results in 240 values.
   

Graph 3

By default, this is the 365 days graph in the web interface. You can change it to more or less detail by choosing a time span covered and a monitoring interval average associated with it. Choose between:

• 100 days with 1 day averages: Results in 100 values. Uses least RAM memory. We recommend this setting for installations with 10,000 sensors or more.
• 200 days with 1 day averages: Results in 200 values.
• 365 days with 1 day averages: Results in 365 values.
• 400 days with 1 day averages: Results in 400 values.
• 750 days with 1 day averages: Results in 750 values. Uses most RAM memory.