StableNet Administrator Manual

StableNet® Version 8.3.
2
Admin Manual
System for Service Fulfillment and Assurance
October-2018
Infosim®, Inc. · 13809 Research Blvd., Suite 802 · Austin, TX 78750 · USA · F: +1.512.792.4200
Infosim® GmbH & Co. KG · Landsteinerstraße 4 · 97074 Würzburg · Germany · F: +49.931.20592.200
Infosim® Asia Pacific Pte Ltd · 8 Ubi Road 2 · #08-04 Zervex · 408538 Singapore · F: +65.6562.8286
https://www.infosim.net · docu@infosim.net
StableNet® Version 8.3.2
Admin Manual: System for Service Fulfillment and Assurance
© 2004 - 2018 Infosim® GmbH & Co. KG
All rights reserved. No part of this work may be reproduced in any form or by any person without prior written permission of the copyright owner.
This document is proprietary and confidential to Infosim®, and is subject to a confidentiality agreement, as well as applicable common and
statutory law. If you send information to Infosim®, you grant Infosim® a non-exclusive right to use or distribute the information in any way it
believes appropriate without incurring any obligation to you.
Infosim® Disclaimer of Warranty and Statement of Limited Liability
Infosim® provides this document "as is", without warranty of any kind, either express or implied, including, but not limited to, the implied
warranties of merchantability, fitness for a particular purpose or non-infringement. This document may contain technical inaccuracies or
typographical errors. Infosim® may make improvements and changes to the programs described in this document or this document at any time
without notice. Infosim® assumes no responsibility for the use of the programs or this document except as expressly set forth in the applicable
Infosim® agreement(s) and subject to terms and conditions set forth therein. Infosim® does not warrant that the functions contained in the
programs will meet your requirements, or that the operation of the programs will be uninterrupted or error-free. Infosim® shall not be liable for
any indirect, consequential or incidental damages arising out of the use or the ability to use the programs or this document. Infosim® specifically
disclaims any express or implied warranty of fitness for high-risk activities. Infosim® programs and this document are not certified for fault
tolerance, and are not designed, manufactured or intended for use or resale as on-line control equipment in hazardous environments requiring
fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life-
support machines, or weapon systems ("High-Risk Activities") in which the failure of programs could lead directly to death, personal injury, or
severe physical or environmental damage.
Compliance with Applicable Laws; Export Control Laws
Use of Infosim® programs and documents is governed by all applicable federal, state, and local laws. All information therein is subject to German
export control laws and may also be subject to the laws of the country where you reside. All Infosim® programs and documents are commercial in
nature.
Trademarks and Acknowledgments
Infosim® and StableNet® are registered trademarks of Infosim® GmbH & Co. KG. Other Infosim® trademarks include but are not limited to: StableNet®
Enterprise, StableNet® Express, StableNet® Telco, StableNet® CMC. All other product names are the property of their respective trademark or
service mark holders and are hereby acknowledged.
Table of Contents
1. Introduction to StableNet®.................................................................................................1
1.1. About StableNet®....................................................................................................2
1.2. Technical Details.....................................................................................................3
1.3. About Measurements and Monitors.............................................................................3
1.4. StableNet® Enterprise and StableNet® Telco..................................................................4
2. System Requirements........................................................................................................5
2.1. General Requirements..............................................................................................6
2.2. Operating System Requirements................................................................................6
2.3. Hardware Requirements...........................................................................................7
2.4. Database Requirements............................................................................................8
2.4.1. Database Sizing............................................................................................8
2.4.2. Physical Drive Requirements...........................................................................9
3. Installation....................................................................................................................10
3.1. Database Installation.............................................................................................11
3.1.1. MariaDB Database Installation.......................................................................11
3.1.2. Oracle Database Installation..........................................................................12
3.2. StableNet® Agent Installation on Linux......................................................................18
3.3. StableNet® Agent Installation on Windows.................................................................18
3.4. StableNet® Server Installation on Linux.....................................................................18
3.5. StableNet® Server Installation on Windows.................................................................20
3.6. StableNet® GUI Installation.....................................................................................20
3.7. Memory Configuration............................................................................................20
3.8. Default Ports........................................................................................................21
3.8.1. Connection between Server and Agent.............................................................22
3.8.2. Connection between GUI and Server................................................................22
3.8.3. Connection between Server and Database........................................................22
3.8.4. Measurement Ports......................................................................................22
3.8.5. Netflow.....................................................................................................23
3.8.6. Additional Ports..........................................................................................23
3.9. High Availability Installation...................................................................................23
4. Initial Configuration........................................................................................................24
4.1. Agent Onboarding.................................................................................................25
4.2. User Role Administration........................................................................................25
4.3. StableNet® Settings...............................................................................................26
4.3.1. Mail Server.................................................................................................26
4.3.2. Default Properties: Data Storage....................................................................26
4.4. Defining Data Sources............................................................................................27
5. Web Portal Customization.................................................................................................29
5.1. Portal Customization.............................................................................................30
5.2. Default and Customer Portal Design..........................................................................30
5.2.1. Default Portal Design...................................................................................30
5.2.2. Customer Portal Design................................................................................31
5.3. Migration from StableNet® 7....................................................................................32
5.4. Application Name and Default Links..........................................................................33
5.5. Providing Up-To-Date Documentation.......................................................................34
5.6. Providing GUI Installers..........................................................................................34
6. Role-Based Access Control................................................................................................35
6.1. Terminology: User, Profiles, Groups, and Roles............................................................36

Admin Manual - Infosim® Confidential - iii
6.2. Management of Users, Profiles, Groups, and Roles.......................................................36
6.2.1. Users........................................................................................................36
6.2.2. Profiles.....................................................................................................39
6.2.3. Groups and Roles........................................................................................40
6.3. Examples.............................................................................................................49
6.3.1. Read-Only Group.........................................................................................49
6.3.2. NOC Group.................................................................................................50
7. Settings and Properties....................................................................................................52
7.1. Local GUI Settings.................................................................................................53
7.2. Interface Filter.....................................................................................................53
7.3. Business Hour Groups............................................................................................55
7.4. TCP Port Management............................................................................................57
7.5. Report Template Management.................................................................................58
7.6. MIB File Management.............................................................................................59
7.6.1. MIB Management........................................................................................59
7.6.2. MIB Browser...............................................................................................60
7.7. Default Properties.................................................................................................62
8. Agent...........................................................................................................................64
8.1. Overview.............................................................................................................65
8.2. Agent Configuration..............................................................................................67
8.2.1. Agent List and Agent States..........................................................................68
8.2.2. Update Agents............................................................................................69
8.2.3. Agent Expert..............................................................................................70
8.3. High Availability (HA)............................................................................................82
9. Agent Repository............................................................................................................83
9.1. Supported Functionality.........................................................................................84
9.2. Agent Synchronization Settings...............................................................................85
9.3. File System Structure.............................................................................................85
9.4. Client Agent Repositories........................................................................................86
9.5. Mode of Operation.................................................................................................87
10. Maintenance................................................................................................................89
10.1. StableNet® Maintenance.......................................................................................90
10.1.1. Daily Maintenance.....................................................................................90
10.1.2. Full Maintenance.......................................................................................90
10.2. Backup..............................................................................................................90
10.2.1. StableNet® Server......................................................................................90
10.2.2. StableNet® Agent......................................................................................93
10.2.3. StableNet® GUI.........................................................................................93
10.3. Update..............................................................................................................93
10.3.1. StableNet® Update.....................................................................................93
10.3.2. License Update.........................................................................................94
11. StableNet® Tools...........................................................................................................95
11.1. StableNet® Database Manager................................................................................96
11.1.1. General...................................................................................................96
11.1.2. Performance.............................................................................................96
11.1.3. Import....................................................................................................97
11.1.4. Export.....................................................................................................97
11.1.5. SQL Operations.........................................................................................97
11.1.6. Expert Parameters.....................................................................................98
11.2. StableNet® Management Tool.................................................................................98
12. Bootstrap Importer......................................................................................................100
13. Troubleshooting..........................................................................................................103

Admin Manual - Infosim® Confidential - iv
13.1. StableNet® Server not available............................................................................104
13.2. StableNet®Agent State down/not connected...........................................................105
13.3. StableNet® Client Agent is not working...................................................................105
13.4. E-Mails are not sent by the StableNet® Server..........................................................106
13.5. Cannot connect to StableNet® Server remotely.........................................................106
13.6. StableNet® License is invalid or expired..................................................................106
A. License Agreement ........................................................................................................107
A.1. License Grant.....................................................................................................107
A.2. License Fees.......................................................................................................108
A.3. Confidentiality....................................................................................................109
A.4. Limited Warranty and Disclaimer............................................................................109
A.5. Limitation on Liability..........................................................................................110
A.6. Indemnity..........................................................................................................110
A.7. Term and Termination..........................................................................................111
A.8. General.............................................................................................................111

Admin Manual - Infosim® Confidential - v
List of Figures
1.1. Interaction of the three StableNet® components...................................................................2
1.2. General view of a StableNet® installation.............................................................................3
1.3. StableNet® communication ports.......................................................................................3
3.1. Default ports...............................................................................................................22
4.1. Adding a StableNet® Agent in the GUI after the installation...................................................25
4.2. Setting the Mail Server Properties....................................................................................26
4.3. Default Properties - Data Storage.....................................................................................27
5.1. Default Property Editor - Web Portal.................................................................................31
5.2. Group Management Dialog.............................................................................................32
5.3. StableNet® Default Properties Editor - Web Portal Dual Login.................................................33
6.1. List of users.................................................................................................................37
6.2. User properties............................................................................................................37
6.3. User/Customer Properties - Groups / Profiles.....................................................................39
6.4. List of profiles..............................................................................................................40
6.5. Group assignment for a profile........................................................................................40
6.6. List of all groups...........................................................................................................41
6.7. Properties of a group.....................................................................................................41
6.8. Web menu display settings for a group..............................................................................42
6.9. Role assignment to a group............................................................................................43
6.10. Roles example: Read-Only Group....................................................................................50
6.11. Roles example: NOC Group............................................................................................50
7.1. GUI settings................................................................................................................53
7.2. Proxy settings..............................................................................................................53
7.3. Business Hour Group Management...................................................................................55
7.4. Dialog for creating or modifying a business hour group........................................................56
7.5. Business hour group once-off maintenance.......................................................................57
7.6. TCP Port Management....................................................................................................58
7.7. Report Template Management.........................................................................................59
7.8. MIB Management.........................................................................................................60
7.9. SNMP Walk Selection Dialog............................................................................................61
7.10. SNMP Walk Dialog.......................................................................................................62
7.11. Location of the Default Property Editor............................................................................62
7.12. Default Property Editor................................................................................................63
8.1. StableNet® Agent role....................................................................................................65
8.2. Agent list....................................................................................................................68
8.3. Agent details...............................................................................................................68
8.4. Agent states................................................................................................................69
8.5. Agent Update Manager..................................................................................................70
8.6. Agent Expert - Info tab..................................................................................................70
8.7. Agent Expert - License tab..............................................................................................71
8.8. Agent Expert - Options tab.............................................................................................72
8.9. Agent Expert - Flow Router tab........................................................................................73
8.10. Agent Expert - Script tab..............................................................................................74
8.11. Agent Expert - Measurement tab....................................................................................75
8.12. Agent Expert - Data Store tab........................................................................................76
8.13. Agent Expert - Monitor Store tab....................................................................................77
8.14. Agent Expert - Log tab.................................................................................................78
8.15. Agent Expert - Duplicate Log tab....................................................................................79

Admin Manual - Infosim® Confidential - vi
8.16. Agent Expert - Flow tab................................................................................................80
8.17. Agent Expert - Syslog tab.............................................................................................81
8.18. Agent Expert - Trap tab................................................................................................82
10.1. StableNet® Full Maintenance Job Default Properties...........................................................91

Admin Manual - Infosim® Confidential - vii
List of Tables
2.1. Operating system requirements (StableNet® Enterprise).........................................................6
2.2. Operating system requirements (StableNet® Telco)...............................................................7
2.3. Recommended hardware requirements for 100.000 measurements and 2 StableNet® Agents.........7
2.4. Minimum hardware requirements (< 5.000 measurements, < 500 devices, no NetFlow
measurements )...................................................................................................................7
2.5. Database hardware requirements......................................................................................8
2.6. Approximate storage requirements for a data row.................................................................8
2.7. Storage examples...........................................................................................................8
3.1. Linux library installation................................................................................................18
3.2. Linux library installation................................................................................................19
3.3. Ports for measurements.................................................................................................22
3.4. Additional ports...........................................................................................................23
6.1. Role group: Agent.........................................................................................................43
6.2. Role group: Backup Jobs................................................................................................44
6.3. Role group: Common.....................................................................................................44
6.4. Role group: Dashboard..................................................................................................45
6.5. Role group: Device........................................................................................................45
6.6. Role group: Device Jobs.................................................................................................45
6.7. Role group: Discovery Jobs.............................................................................................46
6.8. Role group: Elements....................................................................................................46
6.9. Role group: Phone Mappings...........................................................................................47
6.10. Role group: Reports.....................................................................................................47
6.11. Role group: Service Domains.........................................................................................47
6.12. Role group: Service Layers............................................................................................47
6.13. Role group: Service Types.............................................................................................47
6.14. Role group: Services....................................................................................................48
6.15. Role Group: Syslog Query Templates...............................................................................48
6.16. Role group: Tag Filter..................................................................................................48
6.17. Role group: Tag Tree Configuration.................................................................................48
6.18. Role group: Trap/Syslog Color Management.....................................................................49
6.19. Role group: Users/Groups.............................................................................................49
6.20. Role group: Weather Maps............................................................................................49
12.1. Structure of imports.zip......................................................................................100

Admin Manual - Infosim® Confidential - viii
List of Examples
7.1. Interface filters............................................................................................................54

Admin Manual - Infosim® Confidential - ix
Chapter 1. Introduction to StableNet®
Abstract
This chapter introduces the reader to the basic architecture of StableNet® and describes the most
fundamental StableNet® terms.
1.1. About StableNet®...........................................................................................................2

1.2. Technical Details............................................................................................................3
1.3. About Measurements and Monitors....................................................................................3
1.4. StableNet® Enterprise and StableNet® Telco.........................................................................4
Introduction to StableNet® - Infosim® Confidential - 1

1.1. About StableNet®
StableNet® is an advanced, unified, and scalable network management solution. It consists of three
essential components:
• StableNet® Agent
• StableNet® Server
• User interface (StableNet® GUI or StableNet® Web Portal)
The role of the StableNet® Agent is to gather data about the monitored network. It caches the data until
the StableNet® Server logs on to it to import it. Then, the StableNet® Server processes and stores the data
in the StableNet® database. To access and evaluate, as well as to manage StableNet®, you can log in to the
StableNet® Server via the StableNet® GUI, as shown in Figure 1.1. Alternatively, the StableNet® Web Portal
can be used.
StableNet® GUI / StableNet® StableNet® Network

StableNet® Web Portal Server Agents
Database
Figure 1.1: Interaction of the three StableNet® components
To interact with StableNet®, two GUI types are available: a desktop application (StableNet® GUI) and a
web client (StableNet® Web Portal). The StableNet® Web Portal provides only a subset of the StableNet®
GUI features and is not a replacement for the StableNet® GUI.
Note
You can use multiple GUIs simultaneously to manage the same StableNet® Server instance.
The StableNet® Agents' responsibility is to collect network topology and network health information. They
work autonomously and buffer the information locally until the StableNet® Server collects it.
The StableNet® Server is the main component of the solution, as shown in Figure 1.2. It manages the
configuration of StableNet® and polls StableNet® Agents from time to time to collect the buffered data.
Multiple networks can be managed by one StableNet® Server instance. The StableNet® Server is the only
component that directly interacts with the database. 1
StableNet® is designed to support high-availability scenarios. That is why StableNet® Agents work
independently of each other and even continue to work if the StableNet® Server is not reachable.
A minimal StableNet® setup consists of a StableNet® Server instance, a StableNet® GUI installation, and a
single StableNet® Agent. However, in typical installations many StableNet® GUIs and Web Portals access
the StableNet® Server in parallel. For critical environments, StableNet® can be installed in a "High
Availability" mode (please refer to the technical document ADM - High Availability).
In difference to the StableNet® Agents, which are installed and run on their own server hardware, StableNet®
Client Agents can also be installed directly on network nodes to provide enhanced notification and
management features. It executes custom scripts that provide StableNet® with extra information, which
for example can be used to measure the free storage space on a Windows server using a WMI template.
In general, StableNet® is able to monitor multiple, independent networks using at least one StableNet®
Agent per network, as shown in Figure 1.2.
1
If StableNet® is used to monitor its database, the StableNet® Agent must access the database for monitoring, too.

Figure 1.2: General view of a StableNet® installation
The following Section 1.2 describes important technical details of StableNet®. Finally, Section 1.3 provides
a fundamental understanding of the important StableNet® terms "Measurement" and "Monitor".
1.2. Technical Details

In general, StableNet® GUI, the StableNet® Server, and StableNet® Agents communicate via TCP/IP over
the ports listed in Figure 1.3. Of course, the StableNet® Agent may use more ports to connect to devices
to monitor. The ports depend on the protocols used to connect to the devices. For example, the StableNet®
Agent requires the SNMP ports to be open in order to connect to a device.
The StableNet® GUI is a Java based applications, while the StableNet® Agent is a native C++ application.
The StableNet® Server is a managed Java applications which runs on a Wildfly application server. On the
one hand it listens for StableNet® GUI instances to connect, and on the other hand it fetches data from
the StableNet® Agents. In general, the StableNet® Server never communicates directly with managed
network devices. In this sense, a StableNet® Agent is a proxy for the StableNet® Server.
StableNet® Web GUI StableNet® GUI
5443 HTTPS 5443 HTTPS
StableNet® Server
5100 TCP
StableNet® Agents
Figure 1.3: StableNet® communication ports
Note
HTTP upgrade is used when connecting to the StableNet® Server. If a proxy is used, that has
to support HTTP upgrade as well.
1.3. About Measurements and Monitors

Unlike many other network management systems, StableNet® has a unique concept of measurements and
monitors. A measurement in StableNet® is a recurring job that is configured to acquire data from one of
the network devices. Measurements collect data that is later used, for example, to do performance analysis
or to get notifications on improper behavior of managed network entities. For example, a measurement
for a switch interface measures op-status, [in/out]-octets, [in/out]-errors, and
[in/out]-discards in a fixed time interval. Note, that in StableNet® a single measurement can
measure multiple values at once. Each recurring measurement execution creates a new data entry that is

added to the StableNet® database periodically. It contains a timestamp (of the time the measurement was
taken) and the measured values.
A monitor in StableNet® watches a value of a measurement and compares it to configured thresholds. For
example, a monitor may trigger a notification, also called alarm, if the in-errors of an interface exceed
a threshold of 0.1%. Another example is a monitor that creates an alarm if the op-status changes to
down.
1.4. StableNet® Enterprise and StableNet® Telco

There are some key differences between the Enterprise version and the Telco version of StableNet®. The
following features are only included in the Telco version:
Multi Tenancy Support
This allows to run a single instance of StableNet® for multiple tenants. For example, there can be
two tenants that manage completely different networks and each tenant only sees the agents,
devices, measurements, etc. that belong to him. This is why the user roles (see Chapter 6) View
Agent (Global) and View Phone Mappings (Global) are only supported in the Telco version.
Network Service Analyzer
The Network Service Analyzer is a tool to visualize network services that were discovered by
StableNet®. It is only available in the Telco version.
Service Management
A service is a data structure that models different objects, e.g. a cluster of devices. The Service
Management is only available in the Telco version. This includes the Service Management, Service
Layer Management, Service Domain Management, Service Type Management as well as the Service
Analyzer that is used to visualize the created or discovered services.
Scalability for more than 250.000 measurements
The Enterprise version only supports up to 250.000 measurements. For more measurements, the
Telco version is required.

Chapter 2. System Requirements
2.1. General Requirements.....................................................................................................6
2.2. Operating System Requirements........................................................................................6
2.3. Hardware Requirements..................................................................................................7
2.4. Database Requirements...................................................................................................8
2.4.1. Database Sizing...................................................................................................8
2.4.2. Physical Drive Requirements...................................................................................9
System Requirements - Infosim® Confidential - 5

The hardware and software requirements that are needed to install and run StableNet® 8.3.2 are described
in the following subsections. If you have a newer StableNet® version than 8.3.2, you can find the up-to-date
information at https://support.infosim.net/download.
All requirements largely depend on the intended use. Hence, the following requirements are an estimate.
To accurately estimate your hardware and software needs, feel free to contact info@infosim.net.
2.1. General Requirements

The following requirements apply to all hardware and software where you would like to install StableNet®
components (i.e. StableNet® Server, StableNet® Agent, StableNet® GUI and the database).
• Clock of the servers must be synced, NTP is mandatory.
• All servers must have a static IP address.
• Virus scanner must not scan StableNet® folders.
• Intrusion detection, endpoint protection or firewall systems must not impact StableNet® operation.
• 64-bit operating system is required.
• Virtualization is supported for the StableNet® Server and StableNet® GUI if the virtual instances
meet the system requirements below.
• For virtualized installations, the StableNet® "Cold Standby Solution" (CA) license is required. If
you use StableNet® in an HA setup (Agent, Database, Server), the StableNet® "Hot Standby
Solution" (HA) license is required.
• The StableNet® Agent is supported in a virtual environment if the virtual instances meet the system
requirements below. However, the accuracy of real-time measurements is restricted because of
timing and resource constraints of the host (hypervisor).
2.2. Operating System Requirements

The following two sections list the supported operating systems for the individual StableNet® components.
StableNet® Enterprise
Windows Linux OS X
®
StableNet Server Windows Server 2008 R2 RHEL, CentOS 6.8+ -
Windows Server 2012 R1, R2 RHEL, CentOS 7.2+
Windows Server 2016 Ubuntu LTS 16.04
StableNet® Server - latest CentOS 7 version -
High Availability (see note below)
StableNet® Agent Windows Server 2008 R2 RHEL, CentOS 6.8+ -
Windows Server 2012 R1, R2 RHEL, CentOS 7.2+
Windows Server 2016 Ubuntu LTS 16.04
StableNet®GUI Windows 7 SP1 RHEL, CentOS 6.8+ OS X (10.10+)
Windows 8, 8.1 RHEL, CentOS 7.2+
Windows 10 Ubuntu LTS 16.04
Table 2.1: Operating system requirements (StableNet® Enterprise)

StableNet® Telco
Windows Linux OS X
StableNet® Server - RHEL, CentOS 6.8+ -
RHEL, CentOS 7.2+
StableNet® Server - latest CentOS 7 version -
High Availability (see note below)
StableNet® Agent - RHEL, CentOS 6.8+ -
RHEL, CentOS 7.2+
StableNet®GUI Windows 7 SP1 RHEL, CentOS 6.8+ OS X (10.10+)
Windows 8, 8.1 RHEL, CentOS 7.2+
Windows 10
Table 2.2: Operating system requirements (StableNet® Telco)
Note
The latest CentOS version is not necessarily the same as the latest RHEL version. For example,
the latest RHEL version might be 7.4 and the latest CentOS version is 7.3. Then, RHEL 7.3 is
supported for High Availability, but RHEL 7.4 is not supported!
2.3. Hardware Requirements

As a general requirement, all hardware should be server grade:
• Redundant power supplies and fans, connected to UPS.
• Teaming/Pairing of gigabit network interfaces connected to separate HA switches.
• Redundant disks (e.g. RAID-1).
The recommended hardware for a setup with 2 StableNet® Agents (50.000 measurements each) should
meet the requirements listed in Table 2.3. The minimum hardware requirements for a setup of less than
5.000 measurements and less than 500 devices (minimal license without NetFlow measurements) are listed
in Table 2.4.
Server Agent (50.000 GUI

measurements, no
SNMPv3)
CPU 4 Socket, 32 - 64 Cores 8 Cores* 4 Cores
RAM 64 GB 16 GB* 16 GB
Disk 512 GB 2x 1 TB (RAID-1) 8 GB
Table 2.3: Recommended hardware requirements for 100.000 measurements and 2 StableNet® Agents
* If NetFlow processing is done on the StableNet® Agent, 16 cores and 32 GB RAM are recommended.
Server Agent GUI

CPU 16 Cores 4 Cores 2 Cores

Server Agent GUI
RAM 32 GB 8 GB 8 GB
Disk 512 GB 64 GB 8 GB
Table 2.4: Minimum hardware requirements (< 5.000 measurements, < 500 devices, no NetFlow measurements )
2.4. Database Requirements

StableNet® supports the database management systems MySQL 5.6 or higher (only for existing installations
up to StableNet® 7.5.2), MariaDB 10.1 or higher (only for new installations starting with StableNet®
7.5.3), Oracle Enterprise 11g R2 with Partitioning and Oracle Enterprise 12c R2 with Partitioning. To
ensure the performance of StableNet®, no other application should use the StableNet® database instance.
For large installations, however, an Oracle database is mandatory. Table 2.5 shows database hardware
requirements.
Note
If you do not have a suitable Oracle DBMS, you may order StableNet® with an embedded Oracle
DMBS (Oracle Embedded License). Contact support@infosim.net for more information.
Minimum Recommended
CPU 4 Cores 16 Cores
RAM 8 GB 32 GB
Disk Direct attached storage (e.g.
12×300GB RAID-10)
Table 2.5: Database hardware requirements
2.4.1. Database Sizing

Table 2.6 shows the approximate storage requirements for one measurement of a particular type and
Table 2.7 gives some calculation examples.
Measurement type Approximate storage requirement

Ping 48 bytes
Interface (for 12 values, each 64 bytes) 768 bytes
Connect 48 bytes
SNMP 64 bytes per SNMP OID
WMI 64 bytes per WMI results
External 64 bytes per data value
Script 64 bytes per script output parameter
NetFlow TopN (for 10 types the top 100 each) 64 kByte
Table 2.6: Approximate storage requirements for a data row
Per day Per month Per year

Ping (1min) 70 kB 2 MB 24 MB

Per day Per month Per year
Template (5min, 4 values) 75 kB 2.2 MB 27 MB
Interface (5min, 12 values) 220 kB 6.6 MB 80 MB
100.000 measurements (5min, 8 values average) 14.8 GB 444 GB 5.4 TB
Table 2.7: Storage examples
Additional storage space is required for generated reports, device configurations and job results. The size
of this storage depends on the complexity of the objects that are to be saved. To get a good estimation,
multiply the size of one object with the number of objects that will be generated.
2.4.2. Physical Drive Requirements

Since the StableNet® performance is highly dependent on database performance, a well-equipped database
back-end is recommended. Infosim® recommends taking the following into consideration:
• More physical drives improve I/O throughput.
• Directly attached storage can reduce seek time.
• SSDs are in most cases preferred over HDDs.
• A dedicated tablespace for the StableNet® database user is recommended.
• A dedicated physical storage unit for the tablespace can improve the performance in many cases.
Note
Infosim® strongly recommends consulting a database specialist.

Chapter 3. Installation
3.1. Database Installation....................................................................................................11
3.1.1. MariaDB Database Installation..............................................................................11
3.1.2. Oracle Database Installation.................................................................................12
3.2. StableNet® Agent Installation on Linux.............................................................................18
3.3. StableNet® Agent Installation on Windows.........................................................................18
3.4. StableNet® Server Installation on Linux.............................................................................18
3.5. StableNet® Server Installation on Windows........................................................................20
3.6. StableNet® GUI Installation............................................................................................20
3.7. Memory Configuration...................................................................................................20
3.8. Default Ports...............................................................................................................21
3.8.1. Connection between Server and Agent....................................................................22
3.8.2. Connection between GUI and Server.......................................................................22
3.8.3. Connection between Server and Database................................................................22
3.8.4. Measurement Ports.............................................................................................22
3.8.5. Netflow............................................................................................................23
3.8.6. Additional Ports.................................................................................................23
3.9. High Availability Installation..........................................................................................23
Installation - Infosim® Confidential - 10

For the installation, all system requirements described in Chapter 2 have to be met and the user must have
administrative privileges. Infosim® recommends to install the components in the following order:
1. MariaDB or Oracle database management system. See Section 3.1 for more information.
2. StableNet® Agent. See Section 3.2 and Section 3.3 for more information.
3. StableNet® Server. See Section 3.4 and Section 3.5 for more information.
4. StableNet® GUI. See Section 3.6 for more information.
3.1. Database Installation

Depending on the use case, a MariaDB or Oracle database can be used. For information about which database
system to use, contact info@infosim.net. The following two sections describe how to install a
MariaDB or an Oracle database. Independent of the chosen database, the indexes of StableNet® tables
should be checked regularily.
3.1.1. MariaDB Database Installation

To install the MariaDB database on Linux, the easiest way is to add a YUM repository by following the
instructions at https://downloads.mariadb.org/mariadb/repositories/. For Windows systems, the most
recent installer can be found at https://downloads.mariadb.org. After the installation, the configuration
of the MariaDB database has to be adapted using the sample config file provided below. You can use the
command mysqld --help --verbose to see directories where the configuration is read.
#
# Example MySQL database server configuration file for use with StableNet(R)
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html
#
[mysqld]
# Statements that take a long time, e.g. during maintenance,

# may fail if the wait_timeout is too short.
wait_timeout = 86400
# Instead of skip-networking the default is now to listen only on

# localhost which is more compatible and is not less secure.
bind-address = 127.0.0.1
# Increase the maximum for MySQL packets to support handling

# of large files and blocks of data like reports and images.
max_allowed_packet = 1G
transaction-isolation = READ-COMMITTED
# Increase buffer pool size for more performance.

# Increase log file size or files in group to support larger transactions, like
# The ones caused by StableNet database maintenance.
# You can set innodb_buffer_pool_size up to 50 - 80 %

# Of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 16G
innodb_log_file_size = 1G
innodb_log_files_in_group = 8

innodb_log_buffer_size = 64M
innodb_lock_wait_timeout = 7200
# The option 0 sets the commit interval to commit only every

# 1s which improves performance.
innodb_flush_log_at_trx_commit = 0
# The file handles for the MySQL database need to be increased

# Note: on RedHat (CentOS) 7.x you also need to change the system configuration:
# 1. stop mysqld
# 2. add to "/etc/systemd/system/mysql.service"
# 2.1. "LimitNOFILE=10000"
# 3. systemctl daemon-reload
# 4. start mysqld
open-files-limit = 10000
# The number of connections to the database must be high enough
max_connections = 1000
# Configure UTF-8 mode
character-set-server=utf8
# Configure UTF-8 mode for client connections
[mysql]
default-character-set=utf8
After the installation, create the database instance by starting the MariaDB client with mysql -u root.
Then, execute the commands below replacing stablenet-server-ip with your StableNet® Server’s
IP. These will create a new database instance called pme, with the username infosim and password
stablenet to connect to the database granting all privileges on all tables in pme.
CREATE DATABASE pme;

CREATE USER 'infosim'@'stablenet-server-ip' IDENTIFIED BY 'stablenet';
GRANT ALL PRIVILEGES ON pme.* TO 'infosim'@'stablenet-server-ip' WITH GRANT OPTION;
FLUSH PRIVILEGES;
Note
The database pme, user infosim and password stablenet are the default settings of
the StableNet® Server installer. The database settings can be changed, but in that case they
also have to be changed during the installation of the StableNet® Server!
3.1.2. Oracle Database Installation

The first section describes the recommended database configuration for an Oracle database. For more
information, it is recommended to consult an Oracle database specialist.
The second section contains a step-by-step guide to install a basic Oracle database that can be used for
testing purposes. Note, that the described installation is neither performance-optimized nor secure and
thus it should not be used in a production environment.
3.1.2.1. Database Specification

Infosim® supports the following database system and configuration:

Item Configuration
Edition Oracle 11g R2 Enterprise with partitioning 64bit
Oracle 12c R2 Enterprise with partitioning 64bit
Block size 8 KB
Character set WE8MSWIN1252 (for all existing installations up to StableNet® 7.5.2)
AL32UTF8 (for all new installations starting with StableNet® 7.5.3)
Initialization parameter processes=1000
Database service name pme
Username infosim
Password stablenet
Required user permissions CONNECT, OEM_MONITOR, RESOURCE
Note
StableNet® always requires the service name for the database which could be different from
the database SID!
Note
The database pme, user infosim and password stablenet are the default settings of
the StableNet® Server installer. The database settings can be changed, but in that case they
also have to be changed during the installation of the StableNet® Server!
3.1.2.2. Step-by-Step Oracle Database Installation

This section presents a step-by-step guide for a setup with:
• Oracle 12c R2 Enterprise, version 12.2.0.1.0
• Default Desktop installation of Oracle Linux Release 7
• The required free disk space depends on the planned StableNet® installation (number of
measurements, devices, etc.)
• Minimum of 8 GB RAM
• Internet connection
• Disabled firewall on Oracle Linux
• Static server IP
Oracle Linux can be downloaded at www.oracle.com after creating a free Oracle account.
Warning
The described installation is neither performance-optimized nor secure and thus it should
not be used in a production environment. For a production environment, it is recommended
to consult an Oracle database specialist for the database installation.
Perform as root user:

1. Make sure that the file /etc/hosts contains the fully qualified name of the server. For example:
127.0.0.1 localhost.localdomain localhost

10.1.2.222 odb.localdomain odb

2. Install required packages:
yum install oracle-database-server-12cR2-preinstall -y
3. Change password of the oracle user:
passwd oracle
4. Edit /etc/security/limits.d/20-nproc.conf and change it as described below:
# Change this
* soft nproc 1024
# To this
* - nproc 16384
5. Edit /etc/selinux/config and change the line with SELINUX= to the following:
SELINUX=permissive
6. Restart the server.

7. Create the installation directories for the database:
mkdir -p /u01/app/oracle/product/12.2.0.1/db_1
chown -R oracle:oinstall /u01
chmod -R 775 /u01
Perform as oracle user with graphical login session:

1. If the Linux firewall is enabled, execute the following and disable the firewall:
systemctl stop firewalld

systemctl disable firewalld
2. Replace odb.localdomain with the server’s host name execute in a terminal window:
xhost +odb.localdomain
3. Add the following to the end of the ~/.bash_profile file:
# Oracle Settings
export TMP=/tmp
export TMPDIR=$TMP
export ORACLE_HOSTNAME=<server_name>
export ORACLE_UNQNAME=pme
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=$ORACLE_BASE/product/12.2.0.1/db_1
export ORACLE_SID=$ORACLE_UNQNAME
export PATH=/usr/sbin:$PATH
export PATH=$ORACLE_HOME/bin:$PATH
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib
export CLASSPATH=$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib
4. Log out and log in again to make sure the changes in the .bash_profile are applied.

5. If X emulation is used, execute the following:
export DISPLAY=<machine-name>:0.0
6. Unzip the installation file:
unzip linuxx64_12201_database.zip
7. Execute and follow the installer in the database directory:
cd database
./runInstaller
8. During the installation, make sure to set the encoding to AL32UTF8, and the database name is
set to pme.
9. After the installer completed successfully, edit /etc/oratab and change the N in the end of
every line to a Y:
pme:/u01/app/oracle/product/12.2.0.1/db_1:Y
10. Open an sqlplus session with the password you specified during installation:
sqlplus sys@pme as sysdba
11. Issue the following SQL statements to set up a tablespace and user for StableNet®. Using a BIGFILE
instead of a SMALLFILE might increase the performance of the database, depending on the setup.
Note, that autoextend should only be activated for test installations. In a production environment,
autoextend should be turned of (as described in the next section):
CREATE SMALLFILE TABLESPACE "INFOSIM" DATAFILE

'/u01/app/oracle/oradata/pme/data1' SIZE 10G AUTOEXTEND ON NEXT 10G
MAXSIZE UNLIMITED LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE
MANAGEMENT AUTO;
CREATE USER "INFOSIM" PROFILE "DEFAULT" IDENTIFIED BY "stablenet" DEFAULT

TABLESPACE "INFOSIM" ACCOUNT UNLOCK;
GRANT "CONNECT", "OEM_MONITOR", "RESOURCE" TO "INFOSIM";

GRANT UNLIMITED TABLESPACE TO INFOSIM;
12. Quit the sqlplus session:
quit
The database is now ready for the StableNet® Server to connect to. To test the connection, try to log in
with the newly created infosim user:
sqlplus infosim@pme
To automatically start the database after a server reboot, perform the following steps:
Perform as root user:

1. Create the file /etc/init.d/dbora with the following content (including the comments):

#!/bin/bash
#
# chkconfig: 35 95 5
# description: init script to start/stop oracle database 12c, TNS listener
#
# Run-level Startup script for the Oracle Listener and Instances
# It relies on the information on /etc/oratab
export ORACLE_BASE=/home/oracle/app/oracle
export ORACLE_HOME=$ORACLE_BASE/product/12.2.0.1/db_1
export ORACLE_OWNR=oracle
if [ ! -f $ORACLE_HOME/bin/dbstart -o ! -d $ORACLE_HOME ]; then

echo "Oracle startup: cannot start"
exit 1
fi
case "$1" in
start)
# Oracle listener and instance startup
echo -n "Starting Oracle: "
su - $ORACLE_OWNR -c "lsnrctl start"
su - $ORACLE_OWNR -c "dbstart $ORACLE_HOME"
touch /var/lock/oracle
echo "OK"
;;
stop)
# Oracle listener and instance shutdown
echo -n "Shutdown Oracle: "
su - $ORACLE_OWNR -c "lsnrctl stop"
su - $ORACLE_OWNR -c "dbshut $ORACLE_HOME"
rm -f /var/lock/oracle
echo "OK"
;;
reload|restart)
$0 stop
$0 start
;;
*)
echo "Usage: `basename $0` start|stop|restart|reload"
exit 1
esac
exit 0
2. Run the following to change privileges and register the service:
chmod 750 /etc/init.d/dbora

chkconfig --add dbora
Now the database can be started and stopped with the following commands:
service dbora start

service dbora stop
If the database started properly, the database console can be started or stopped using the following
commands (the commands must be executed by the oracle user and the correct environment from the
bash_profile must be used):

emctl start dbconsole
emctl stop dbconsole
If the console started successfully, it is available under https://odb.localdomain:1158/em/.
3.1.2.3. Configuration Hints

StableNet® only creates tables, indices and index organized tables. StableNet® does not create sequences,
procedures, functions or triggers.
User Rights
The following user roles are required (Admin option is not required):
• CONNECT
• OEM_MONITOR
• RESOURCE (System privileges: Create cluster, create index type, create operator, create procedure,
create sequence, create table, create type)
Optimizations for StableNet®

• It is recommended to use an Oracle 11g R2 64-bit version.
• It is recommended to use a separate Oracle database server for StableNet® to reduce the impact
of other applications.
• The character set has to be set to WE8MSWIN1252 for existing installations up to StableNet®
7.5.2 and it has to be set to AL32UTF8 for new installations starting with StableNet® 7.5.3.
• The Number of Processes has to be set to 1000 (the maximum number of sessions will automatically
be increased to 1522).
• StableNet® tablespace:
• StableNet® should use its own tablespace to separate the data and optimize the performance.
• The StableNet® tablespace should use a separate physical device.
• A fixed tablespace size has to be used.
• The autoextend feature for the tablespace has to be turned off.
• ReDo Log:
• The ReDo Log Groups should use a separate physical device.
• At least 16 ReDo Log Groups with 512 MB each have to be created.
• UnDo Tablespace:
• The UnDo tablespace should use a separate physical device.
• The UnDo tablespace must be at least 32 GB. This is important for the StableNet® maintenance.
• The Oracle instance should use as much physical memory as possible.
3.1.2.4. Further links

Oracle database installation guide 11g Release 2 (11.2) for Linux:
https://docs.oracle.com/cd/E11882_01/install.112/e24326/toc.htm
Caution
After installation/reinstallation, the server needs to be rebooted and the functionality of the
database has to be checked!
Please be aware that without a reboot the database will not work correctly!

3.2. StableNet® Agent Installation on Linux
For the StableNet® Agent, there are two different installers. One for 32-bit systems and one for 64-bit
systems. The 64-bit version is recommended for most customers.
Usually, the required libraries are already installed on Linux systems. However, if the StableNet® Agent
installer cannot be executed, make sure to install the following libraries.
Operating System Command

RHEL 6.x yum install libXtst.i686 libXtst-devel.i686 \
compat-libstdc++-33.i686 libstdc++.i686 \
libstdc++-devel.i686
RHEL 7.x yum install libXtst.i686 libXtst-devel.i686 \
libXrender.i686 libgcc.i686
Ubuntu 16.04 apt install libxtst6:i386 libc6:i386 libxrender1:i386 libxi6:i386
Table 3.1: Linux library installation
Independent of the operating system, unzip has to be installed as well.

After adding the libraries, the StableNet® Agent can be installed by executing the file
StableNetAgentInstall.bin. It is possible to use custom values for username, password and
port. These have to be specified when registering the StableNet® Agent on the StableNet® Server.
Alternatively, it is possible to install the StableNet® Agent in silent mode with the command line option
-i silent. The silent installer installs the StableNet® Agent with the following default values:
Username
infosim
Password
stablenet
Port
5100
Installation directory
/opt/stablenet/snagent
After the silent installation is completed, the license file (license.dat) must be copied into
/opt/stablenet/snagent/conf/. The snagent executable located in the
/opt/stablenet/snagent/bin directory can be used to change username, password and port.
The available command line options can be shown using -help.
3.3. StableNet® Agent Installation on Windows

The StableNet® Agent can be installed by executing the file StableNetAgentInstall.exe. It is
possible to use custom values for username, password and port. These have to be specified when registering
the StableNet® Agent on the StableNet® Server.
3.4. StableNet® Server Installation on Linux

If the installer cannot be executed, make sure to install the following libraries.

Operating System Command
RHEL 6.x yum install libXtst.x86_64 libXrender.x86_64 \
libstdc++.x86_64
RHEL 7.x yum install libXtst.x86_64 libXrender.x86_64 \
libgcc.x86_64
Ubuntu 16.04 apt install libxtst6 libc6
Table 3.2: Linux library installation
Independent of the operating system, unzip has to be installed as well. The hostname has to be provided
in the /etc/hosts file.
After adding the libraries, the StableNet® Server can be installed by executing the file
StableNetServerInstall.bin.
Without a graphical user interface, it is possible to install the StableNet® Server using the command line
option -i console. To change server settings after the installation, the standalone.xml file
located in the /opt/stablenet/snmw/wildfly/standalone/configuration directory
can be adapted. The installer uses the following default values:
Database type
MariaDB
Database server
127.0.0.1
Database port
3306
Database name
pme
Database user
infosim
Database password
stablenet
StableNet® HTTPS port
5443
Before the StableNet® Server installation is finished, a database check is done which checks if the database
is configured correctly. That includes a check whether 250 concurrent connections can be opened, the
correct charset is used and if BLOBs can be written to the database. If the database check fails, the database
has to be configured correctly and the StableNet® Server has to be reinstalled.
During the first installation of any StableNet® version starting from 7.5.3, the installation of the database
driver for MySQL requires additional steps. Due to the license definition, the MySQL driver must not be
bundled, but installed by the customer during the installation of StableNet®. This means that the customer
has to follow the download instructions given in the installer and select the downloaded driver. The driver
is then stored in the config/database-driver folder for later updates. During later updates, this
driver will be selected automatically and no extra work is required then.
This does not apply to Oracle drivers or MariaDB drivers which are bundled in the installer. The MariaDB
driver can be used for all new MariaDB 10.1 and MySQL 5.7 installations in full UTF-8 mode. For existing
installations, the original MySQL driver is still required. Also, updating an existing MySQL 5.6 database
to, e.g. MySQL 5.7, will still require the MySQL driver since the internal encoding of the database data is
not in UTF-8.

3.5. StableNet® Server Installation on Windows
The StableNet® Server can be installed by executing the file StableNetServerInstall.exe. If
the database was created using custom values for database name, user, password or port, the respective
values have to be entered during the installation.
Before the StableNet® Server installation is finished, a database check is done which checks if the database
is configured correctly. That includes a check whether 250 concurrent connections can be opened, the
correct charset is used and if BLOBs can be written to the database. If the database check fails, the database
has to be configured correctly and the StableNet® Server has to be reinstalled.
During the first installation of any StableNet® version starting from 7.5.3, the installation of the database
driver for MySQL requires additional steps. Due to the license definition, the MySQL driver must not be
bundled, but installed by the customer during the installation of StableNet®. This means that the customer
has to follow the download instructions given in the installer and select the downloaded driver. The driver
is then stored in the config/database-driver folder for later updates. During later updates, this
driver will be selected automatically and no extra work is required then.
This does not apply to Oracle drivers or MariaDB drivers which are bundled in the installer. The MariaDB
driver can be used for all new MariaDB 10.1 and MySQL 5.7 installations in full UTF-8 mode. For existing
installations, the original MySQL driver is still required. Also, updating an existing MySQL 5.6 database
to, e.g. MySQL 5.7, will still require the MySQL driver since the internal encoding of the database data is
not in UTF-8.
3.6. StableNet® GUI Installation

The GUI installation is straight forward. It can be installed by executing the file
StableNetGUIInstall.exe. On Linux systems, some additional libraries might have to be installed.
See Table 3.2 for the installation commands. On Linux systems, unzip has to be installed as well.
The GUI installer does not install the complete StableNet® GUI. Instead, only a bootstrapper is installed
that downloads all files that are necessary to start the StableNet® GUI. The advantage of that approach is
that the user can connect to StableNet® Servers with different versions using the same GUI installation.
For the bootstrapping to work correctly, the user needs write-access to the following folders.
• Windows:
• %user_dir%\.stablenet
• %user_dir%\AppData\Local\Infosim\StableNetGUI
• Linux: /home/%user_dir%/.stablenet
To use the Connect to Device feature in the StableNet® GUI, PuTTY has to be installed on the system. The
StableNet® GUI installer for Windows contains the binary, so no additional action is required. However,
on MacOS and Linux, an additional package has to be installed:
• Linux: putty package must be installed
• MacOS: XQuartz package must be installed
3.7. Memory Configuration

The memory configuration of the StableNet® Server and the StableNet® GUI can be found in the following
files if the default paths were used during installation:
StableNet® Server (Windows) %windir%/snmw/config/memory.conf

StableNet® Server (Linux) /opt/stablenet/snmw/config/memory.conf

StableNet® GUI installation %windir%/snmw/wildfly/update/resources/startup.vmoptions
(Windows)
StableNet® GUI installation /opt/stablenet/snmw/wildfly/update/resources/startup.vmoptions
(Linux)
Each file contain the terms -Xms### and -Xmx###, where ### is the amount of configured memory.
For example, -Xms1g defines 1GB of memory for the -Xms option. The options have the following
meaning:
-Xms###
Defines how much memory the application (StableNet® Server respective StableNet® GUI) acquires
on startup.
-Xmx###
Specifies the maximum memory the application (StableNet® Server respective StableNet® GUI)
can use.
Note
All values must be at least the size specified in Chapter 2. If the memory settings for the
StableNet® GUI has been changed, the file update.xml has to be deleted. It can be found
in /opt/stablenet/snmw/wildfly/update/ (Linux) or
%windir%/snmw/wildfly/update/ (Windows) if the default paths were used during
the installation.
3.8. Default Ports

StableNet® Agent, Server and GUI use different ports for communication. The StableNet® Agent port (5100),
StableNet® GUI port (5443) and the database port (1521/3306) must be unlocked at the firewall for
StableNet® to run correctly. Other ports can be unlocked if necessary. Figure 3.1 provides an overview on
the default ports.

Figure 3.1: Default ports
3.8.1. Connection between Server and Agent

By default, the StableNet® Server and the StableNet® Agent communicate via TCP port 5100. This port can
be customized during the StableNet® Agent installation.
3.8.2. Connection between GUI and Server

By default, the StableNet® GUI and the StableNet® Web Portal communicate with the Server using TCP port
5443.
3.8.3. Connection between Server and Database

The required port for the database connection depends on the used database and can be customized. By
default, Oracle databases use TCP 1521 and MySQL/MariaDB databases use TCP 3306.
3.8.4. Measurement Ports

Depending on the used measurements or services, different ports are required. Some examples:
Measurement/Service Port
SNMP UDP 161
SNMP Traps UDP 162
Syslog UDP 514
Client Agent TCP 5100

Measurement/Service Port
CLI Ports TCP 22, TCP 23
Alarming TCP 25 (SMTP)
Table 3.3: Ports for measurements
3.8.5. Netflow
The StableNet® Agent receives Netflow data on UDP port 5100.
3.8.6. Additional Ports

If StableNet® communicates with an external authentication server, the following ports are required.
Authentication Server Type Port

TACACS TCP 49
Radius UDP 1813
ADS (LDAP) TCP/UDP 389
Table 3.4: Additional ports
3.9. High Availability Installation

For details about a StableNet® High Availability installation, please refer to the technical document ADM
- High Availability.

Chapter 4. Initial Configuration
Abstract
Upon installing each StableNet® component - the server, the agent, and the GUI - it is necessary to do an
initial configuration. First of all, the StableNet® Agent needs to be added to the server. Afterwards, user
role administration takes place adding different groups and corresponding users. Finally, global settings
like data storage properties need to be adjusted.
4.1. Agent Onboarding........................................................................................................25

4.2. User Role Administration...............................................................................................25
4.3. StableNet® Settings......................................................................................................26
4.3.1. Mail Server........................................................................................................26
4.3.2. Default Properties: Data Storage............................................................................26
4.4. Defining Data Sources...................................................................................................27
Initial Configuration - Infosim® Confidential - 24

The following sections describe the initial configuration of the StableNet® environment. Section 4.1
describes how to initialize the agent upon the first start of the StableNet® GUI after the installation.
Section 4.2 gives a quick introduction to the initial user set up. The last section introduces important
settings of StableNet® that can be adjusted.
4.1. Agent Onboarding

Upon finishing the installation of the StableNet® environment with all components, it is necessary to add
the StableNet® Agent to the StableNet® Server. When starting the GUI, a window opens to prompt a
configuration of an agent shown in Figure 4.1.
Figure 4.1: Adding a StableNet® Agent in the GUI after the installation
Section 8.1 describes how to set the different properties of the agent. After adding the agent to the server,
devices can be added and the network can be monitored.
4.2. User Role Administration

StableNet® provides a powerful User and Group Management system to add multiple users, profiles and
groups with different access rights set by predefined roles (see Chapter 6). One step of the initial
configuration is to create users and groups in StableNet® in addition to the already existing ones.
In most cases, users of StableNet® are distinguished by their area of operations.
For example, the Administrators group will have all rights when working with StableNet®. Whereas normal
users will focus on the operation in the GUI with read-only access. The Back Office group has extended

rights compared to normal users and works on adding content to StableNet® (for example devices, reports,
etc.).
More information about creating or modifying users, groups and profiles or assigning roles is found in
Chapter 6.
4.3. StableNet® Settings

After the installation of StableNet® and the initialization of the agent, it may be necessary to adjust the
existing default properties in StableNet®. The next sections describe the most important settings for the
initial configuration.
4.3.1. Mail Server

There are two ways to adjust the mail server properties. The first way is to use the dialog shown in Figure 4.2.
It can be opened via the Mail Server Properties entry in the Options menu.
Figure 4.2: Setting the Mail Server Properties
The IP address or name of the mail server.

The port of the mail server.
The protocol that should be used. Possible values are SMTP, SMTPS and TLS.
The sender email address of all mails that are sent by the StableNet® Server.
Optional username for the mail server authentication.
Optional password for the mail server authentication.
Opens a dialog that allows to send a test mail.
4.3.2. Default Properties: Data Storage

Before starting to measure devices in the monitored network the Data Storage properties shoud be adjusted
in the Default Property Editor.
StableNet® supports two concepts when storing data in the database. One concept is the aggregation of
data, and the second is the lifetime of data. Both concepts avoid an ongoing growth of the database size
and can be used in combination.

Figure 4.3: Default Properties - Data Storage
The Data Aggregation has three stages. Each stage takes all data measurement points in the defined
interval and aggregates them to one single data measurement point. A stage gets active, if data is older
than the defined age. For example, if a ping measurement is executed once per minute, one hour of
measurements consists of 60 measurement points. According to the settings of Figure 4.3 stage one of
the data aggregation will aggregate all 60 data measurement points to one data measurement point. As
the age is 14, only data older than this time value is aggregated. Stage two then takes all data that is older
than 60 days and aggregates all measurement points in an interval of eight hours to one measurement
point. This means that eight measurement points from the ping measurement in stage one are aggregated
to one measurement point. This is repeated for the third stage as well.
The Time to Live properties set the time when measurement data is removed from the database. In
addition to measurement data, it is also possible to set a time to live for other data, for example Action
Events, Log Data or Job Results.
4.4. Defining Data Sources

Database variables allow querying information from external data sources. For that, additional data sources
have to be added to the Wildfly Application Server. They are defined in the config/deploy directory
of the StableNet® Server. To add a new data source, a text file named <name>-ds.xml has to be added
to that directory. An example of the format can be found in the subsystem
urn:jboss:domain:datasources:2.0 of the standalone.xml file located in the
wildfly/standalone/configuration directory. The top-level element of the custom data
source is datasources.
After finishing the described process, it may take up to 60 seconds until the new data source is available
in StableNet®.
Warning
It is highly recommended to not use a mix of MySQL and MariaDB databases for database
variables and/or the main StableNet® database. Only one of these should be used and all
databases should use the same encoding to prevent driver issues.

Note
To increase security, the StableNet® database is not available as a data source by default.
However, it is possible to add a data source referencing the StableNet® database to the Wildfly
Application Server as shown above.

Chapter 5. Web Portal Customization
5.1. Portal Customization.....................................................................................................30
5.2. Default and Customer Portal Design..................................................................................30
5.2.1. Default Portal Design..........................................................................................30
5.2.2. Customer Portal Design........................................................................................31
5.3. Migration from StableNet® 7...........................................................................................32
5.4. Application Name and Default Links.................................................................................33
5.5. Providing Up-To-Date Documentation...............................................................................34
5.6. Providing GUI Installers.................................................................................................34
Web Portal Customization - Infosim® Confidential - 29

This chapter describes how to setup and configure StableNet® for web portal customizations. It provides
a description on how to change the design (e.g. coloring, fonts, etc.) of the portal for all users and on a
per group basis. It also describes the migration from previous versions of StableNet® to the current version.
Note
This chapter does not describe CSS or web design in general. It only provides information on
where to put the respective files and how to configure StableNet® to use the provided styles.
5.1. Portal Customization

StableNet® provides a directory on the host machine for placing style sheets. Those style sheets are
automatically used to change the facing of the web portal. The directory is available within the installation
directory:
<SNMW_INSTALLATION_DIRECTORY>/config/gui/assets/
It already contains a subdirectory called default which reflects the file structure that is necessary to
adjust the web portal:
favicon.ico
The favicon that is used in the browser's address bar.
design.css
The style sheet used for the design of users who are logged into the StableNet® portal.
login.css
The style sheet used for the login page of the StableNet® portal.
The default design is already available to be customized and all changes are reflected directly in the portal
without restarting the server. However, the default design is always overridden on updates of StableNet®.
Therefore, it is a best practice to add a new subdirectory for each custom design to the assets directory.
Each customization should have a significant name and at least the three files listed above. The complete
portal can be customized using normal Cascading Style Sheets. Respective classes or IDs must be taken
from the portal's source code (available via browsers) and may require a deep understanding of how CSS
selectors and inheritance work.
After adding new designs to the assets directory, a small reconfiguration of StableNet® is necessary.
The next section describes two different ways to use web portal customizations.
Note
All changes to the assets directory files are reflected directly to the portal and may impact
the user experience if the customized design is actively used.
5.2. Default and Customer Portal Design

StableNet® provides the possibility to configure a default portal design which is used for all users and
portal designs on a per group basis.
5.2.1. Default Portal Design

The default portal design is configured globally for all users of StableNet®. The respective default property
is available in the Default Property Editor, displayed in Figure 5.1.

Figure 5.1: Default Property Editor - Web Portal
The Portal Custom Design property reflects the directory name of the default design which
is used for each user of StableNet®. The directory needs to be located in the following directory:
If the directory is not existing, the StableNet® internal design is used as a fallback solution. Changing
this property affects the design of all users if not specified otherwise on a per group basis described
in the next section.
5.2.2. Customer Portal Design

Since StableNet® 8, it is possible to specify a different design for different user groups. The Group
Management dialog contains a property that allows to set the design for that specific group, shown in
Figure 5.2.

Figure 5.2: Group Management Dialog
The Group Web Design property reflects the directory name of the default design used for all
members of this specific group.
The user group design has precedence over the default design specified for all users. If a user is member
of multiple groups with different designs, the selected design is based on StableNet® internal identifiers.
Therefore, it is a best practice to define explicit custom design groups and assign only one of those groups
to each user.
Note
The login page cannot be customized on a per group basis because group assignments are
only available for logged in users. Instead, the globally defined login page customization is
used.
5.3. Migration from StableNet® 7

In StableNet® 7, custom designs were located in the following directory:
<SNMW_INSTALLATION_DIRECTORY>/config/webgui/
All CSS data and images referenced from CSS files need to be moved to the directory structure and files
described in Section 5.1.
Taking the custom design of StableNet® 7 as an example, all relevant data is located in the following two
directories:
<SNMW_INSTALLATION_DIRECTORY>/config/webgui/login/custom/
<SNMW_INSTALLATION_DIRECTORY>/config/webgui/design/custom/

All images of both directories need to be copied to a new directory in the following directory:
All style sheets located in the design directory need to be copied into the design.css of the previously
created directory. Style sheets in the login directory need to be copied into the login.css.
Customers using the dual login concept of StableNet® 7 are able to activate it via the default property,
shown in Figure 5.3.
Figure 5.3: StableNet® Default Properties Editor - Web Portal Dual Login
Enable the check box of the Dual Login property to enable the dual login feature of the StableNet®
Web Portal.
The dual login feature adds two additional fields to the normal login, summing up to four fields, two for
a username and two for a password. Thus, it is possible to split knowledge of login credentials among two
persons, each one knowing a part of the secret to authenticate against StableNet®. A normal user account
is taken for this, but username and password consist of two parts where each part is shared with two
persons.
Note
Starting with StableNet® 8, it is not possible to customize HTML pages directly. All design
changes need to be made via CSS.
5.4. Application Name and Default Links

In addition to the design itself, it is also possible to customize the application title and the three links on
the top right via Default Properties at the Web Portal tab. Default Properties relevant to application name
and default links are:

• Display name of the web portal
• Display name of the first default link
• Display name of the second default link
• Display name of the third default link
• Link destination of the first default link
• Link destination of the second default link
• Link destination of the third default link
5.5. Providing Up-To-Date Documentation

Every StableNet® Server installer is shipped with the latest documentation available at the time of its
creation. This documentation can be accessed via the Web Portal (see the user manual). If you have received
updated documentation through other means (e.g. our support), these documents can be provided to all
users via the Web Portal.
The documents provided by default can be found at <SNMW_INSTALLATION_DIRECTORY>/doc/
in PDF format. Any PDF file in this directory will be displayed in the Web Portal. Logging out and back in
again to get a new session might be necessary for your users to see the changes.
5.6. Providing GUI Installers

To configure the optional GUI download via the StableNet® Web Portal, copy the relevant installer files to
<SNMW_INSTALLATION_DIRECTORY>/wildfly/update. The files will appear automatically
within the GUI Installer panel.

Chapter 6. Role-Based Access Control
Abstract
Role-Based Access Control (RBAC) allows granting users access on StableNet® components (e.g.
measurements, devices, reports, etc.). However, a user itself is not directly granted rights to components.
Therefor, it is important to understand the assignment of users to profiles, groups, and roles, and the
relationship to components. The advantage of this concept is the possibility to manage access rights in a
simple way after setting up required profiles and groups once. Some examples shown in this section handle
common settings.
6.1. Terminology: User, Profiles, Groups, and Roles...................................................................36

6.2. Management of Users, Profiles, Groups, and Roles...............................................................36
6.2.1. Users...............................................................................................................36
6.2.2. Profiles.............................................................................................................39
6.2.3. Groups and Roles................................................................................................40
6.3. Examples....................................................................................................................49
6.3.1. Read-Only Group................................................................................................49
6.3.2. NOC Group.........................................................................................................50
Role-Based Access Control - Infosim® Confidential - 35

6.1. Terminology: User, Profiles, Groups, and Roles
Security objects of RBAC belong together in the following relations:
• User → User Groups ← Roles, and in addition:
• User → Profiles ← User Groups ← Roles
In detail:
• Users belong to profiles (e.g. Administrator Set) or groups (e.g. Administrator).
• Profiles are a set of groups (e.g. Administrators).
• Groups are a set of roles (e.g. Modify Device).
After setting up profiles and group, and assigning them to users, the next step is to assign components
to users:
• Groups → StableNet® components
Groups are assigned to StableNet® components (e.g. measurements, devices, reports, …). This assignment
is stored on component level. All users belonging to such an assigned group indirectly get access to the
component based on the set of roles of that group.
A user object itself stores e.g. a login name and password. This is required to login to the StableNet® GUI.
The assigned groups or profiles (as a set of groups) result in a set of roles. These roles are split into global
and component-based roles. Component-based roles allow authorization only on the assigned components.
Global roles grant you access to all components although they are not explicitly assigned. By default, each
group assigned to a component has at least read access to it. For example, a device for a user is only shown
in the GUI if it has group assignment of one of the user's attached groups or if the user is member of a
group with the View Devices (Global) role.
6.2. Management of Users, Profiles, Groups, and

Roles
To manage users/customers, go to the menu Options → User/Customer Management in the StableNet® GUI.
Service providers are also able to manage the logins of their customers in StableNet®.
6.2.1. Users
The user infosim with the default password stablenet has administrative rights and, therefore, has
access to all StableNet® functionalities.
Opening the menu Options → User/Customer Management shows a list of all users, as shown in Figure 6.1.

Figure 6.1: List of users
Allows searching for elements in the table below based on the selected column.
Allows switching the column for element search.
Shows a list of all users according to the content of the Search field.
Creates a new user.
Imports users, groups, and other security settings from a CSV file to StableNet®.
The file can be modified prior to the import process.
Exports all manually created users into a CSV file.
When adding new users manually, the dialog shown in Figure 6.2 opens.
Figure 6.2: User properties
The upper area contains input fields for user information.

User Name (mandatory)
Case-sensitive username for the login. Whitespace characters are allowed in usernames,
however, they might not be supported by external authentication!
First Name
First name of the user.
Last Name
Last name of the user.

Email-Address
Email address, used e.g. for sending reports to.
Password (mandatory)
The password of the user.
Confirm Password (mandatory)
The password confirmation.
Customer ID, Company, Technical Manager, Extra Text, Description,
Account Manager, Postal Address
Additional information for the user to be stored in the database.
Password Hash
Hash value that can also be used to login on StableNet® Web Portal. Additionally, it can be
used to call web elements like charts and statistics using links.
Active
Check box to enable the user. If disabled, the user will not be able to sign on.
External Authentication
Selecting this check box allows to use external authentication instead of the StableNet®
built-in authentication. For this option, an authentication service, like Active Directory
Service (ADS), TACACS+ or RADIUS is required.
Note
The type of external authentication is configured in the
snmw/config/system.properties file of the StableNet® Server. A
restart of the StableNet® Server is required after the file has been modified.
Synchronization Type, Sync Config Name

If the user is synchronized via an External Authentication Synchronization Job, these fields
contain the type of the synchronization (LDAP or Active Directory) and the name of the
synchronization config as defined in the User/Group Synchronization Management.
Default Dashboard
Combo box to predefine a dashboard to be displayed in the Dashboard page in the Web Portal
and in the StableNet® GUI.
Web Portal Start Page
Selects the start page shown after user logs in to the web page.
New Hash
Generates a new password hash. All old URLs generated with Tokenize URL become invalid.
Tokenize URL
Generates a URL using password hash and username. The URL is tokenized and can be used
to call web elements like charts and statistic using weblinks. The tokenized URL does not
show username or hash and is unique for each link. If the URL prior the token or the token
itself is modified, the link will not work anymore.
Allows assignment of groups and profiles to the user.

Shows the effective roles of the user based on the group and profile assignments.
The following Figure 6.3 shows the corresponding tab content to assign profiles and groups to the user.

Figure 6.3: User/Customer Properties - Groups / Profiles
Assigns selected profiles to the user.

Assigns selected groups to the user.
6.2.2. Profiles
Profiles have a set of groups assigned and allow assigning the correct user settings depending on the
user's role in StableNet®. If profiles are well-defined, a profile can easily be assigned to a new user. This
saves time and effort.
Tip
From a technical point of view, for example, it is the same to assign a user to the groups
ReadOnly and NOC
or
to assign a user to a profile RONOC (which consists of the groups ReadOnly and NOC).
The Profiles tab in the window User/Customer Management shows a list of all available profiles and allows
searching and managing them.

Figure 6.4: List of profiles
The buttons New or Modify open the following Profile Properties dialog:
Figure 6.5: Group assignment for a profile
The dialog allows specifying a Profile Name and a Profile Description. In addition, groups can be added to
the profile by selecting them in column Select.
If the profile is synchronized via an External Authentication Synchronization Job, the Synchronization
Type contains the type of the synchronization (LDAP or Active Directory) and the Synchronization
Configuration contains the name of the configuration as defined in the User/Group Synchronization
Management.
6.2.3. Groups and Roles

A group is a set of roles. Roles give authorization, for example, to view, modify or create reports.
There are two types of roles:
1. Global roles - e.g. Modify Reports (Global): Users inheriting this role from groups can
modify all reports, although the corresponding group is not directly assigned to any report.
2. Component-based roles - e.g. Modify Reports: Users inheriting this role from groups can
modify reports only if the group is assigned to them.

All available groups are displayed in the following Groups tab in the User/Customer Management window.
Figure 6.6: List of all groups
In this example, members of the default group Administrators have full role authorization, except the GUI
Expert Properties. The group Users has no roles selected, but grants read-only access to StableNet®
components.
When creating a new or modifying an existing group, the dialog in Figure 6.7 opens.
Figure 6.7: Properties of a group
In addition to the Group Name and the Group Description, this dialog allows to specify a Group Web Design
only for members assigned to this group. For more information on Web Portal customization, refer to the
Administrators manual. In addition, it is possible to assign users to this group via the column Member of
the table displayed in the bottom of the dialog.
The tab Web Menu Display Settings allows to authorize the group members visibility and access to the
different sections of the StableNet® Web Portal.

Figure 6.8: Web menu display settings for a group
Please be aware of the different categories shown in the tabs Status, Inventory, Analyzer, Reporting, Device
Automation, Settings, and Help. More information on the StableNet® Web Portal is available in the StableNet®
User Manual.
The Roles tab shows all available and assigned roles to the current group.

Figure 6.9: Role assignment to a group
The Search field allows filtering within the list of roles. The corresponding selection box allows filtering
on active or inactive roles. The roles are grouped and can be also used for filter purposes. For example,
searching for the text Agent in the column Role Group will list all roles that belong to agent authorization
(e.g. modify, view, create agent).
Searching the text View in the column Role shows all view authorization roles available for all objects.
6.2.3.1. List of Roles
Role Description
All Agent Rights (Global) Allows to view, add, and modify all StableNet® Agents.
Create Agent (Global) Allows adding a StableNet® Agent to the system.
Flow Query (Global) Determines whether the Flow Query Analyzer can be used based
on the NetFlow raw data of the StableNet® Agent.
Modify Agent Allows modifying a StableNet® Agent.
Modify Agent (Global) Allows modifying a StableNet® Agent.
View Agent (Global) Allows viewing all StableNet® Agents. Only supported in the Telco
version. In the Enterprise version, all users see all StableNet®
Agents.
Table 6.1: Role group: Agent

Role Description
All Backup Job Rights (Global) Grants access to all Backup Jobs.
Create Backup Jobs (Global) Allows creating Backup Jobs.
Create Backup Jobs without The owner of this role can create jobs without the need to confirm
Confirmation (Global) them (two-man rule).
Modify Backup Jobs Allows modifying Backup Jobs.
Modify Backup Jobs (Global) Grants access to modify existing Backup Jobs.
Restore Configurations (Global) Restores saved backups to a device.
View Backup Jobs (Global) Grants access to the Job View. For users, all existing Backup Jobs
will be visible.
View Device Configurations (Global) Grants you access to the backups of the devices.
Table 6.2: Role group: Backup Jobs
Role Description
All Alarm Group Rights (Global) Allows modifying default properties.
All Business Hour Group Rights Allows modifying all business hour groups.
(Global)
Confirm Prepared Jobs (Global) The owner of that role can confirm Prepared Jobs (two-man rule).
Custom Service Job (Global) The owner of that role can handle Custom Service Jobs. These jobs
are only available with special license and module.
GUI Expert Settings (Global) The owner of that role has access to the expert settings in the GUI.
Modify Cisco Extension Mapping Allows modifying the entries within the
(Global) Cisco Extension Mapping Management.
Modify Config Job Templates (Global) Allows modifying the Config Job templates in StableNet®.
Modify Configuration Snippets (Global) Allows creating, modifying, and deleting configuration snippets.
Modify Database Variables (Global) Allows creating, modifying, and deleting database variables.
Modify Device Info Commands (Global) Allows creating, modifying, and deleting device info commands.
Modify End-of-X Information (Global) The owner can create, modify, and delete End-of-X data.
Modify Global Parameters (Global) Allows modifying default properties.
Modify Report or Measurement Allows modifying the SNMP, WMI or trap templates in StableNet®
Templates (Global) as well as reports.
Modify Trap/Syslog/Store Filters Allows modifying the trap or syslog filters for those events.
(Global)
Modify Vulnerability Information Allows creating, modifying, and deleting vulnerabilities.
(Global)
Read Configuration Snippets (Global) The owner of this role can see the configuration snippets.
Read Database Variables (Global) The owner of this role can see the database variables.

Role Description
Read Device Info Commands (Global) The owner of this role can see the device info commands.
Read Vulnerability Information Allows to see vulnerability information.
(Global)
Show Audit Information (Global) Allows using the Audit Analyzer.
Show Trap/Syslog for unmanaged Allows making traps and syslogs visible for devices that are not in
Devices (Global) the inventory.
Tag Category Rights (Global) Allows to create or remove Tag Categories from the system.
View Log Files (Global) The owner of that role has access to Server Log File Management.
Table 6.3: Role group: Common
Role Description
All Dashboard Rights (Global) This role allows to create, modify, and delete dashboards.
Create Dashboard (Global) This role allows to create dashboards.
Modify Dashboard This role allows to modify own dashboards.
Modify Dashboard (Global) This role allows to modify all dashboards.
View Dashboard (Global) The user is allowed to view all dashboards.
Table 6.4: Role group: Dashboard
Role Description
All Device Rights (Global) Allows doing anything within the inventory. This includes adding,
deleting, and modifying devices.
Create Device (Global) Allows creating devices within the own group.
Modify Device Allows modifying assigned devices.
Modify Device (Global) Allows modifying devices.
Rediscover Device (Global) Allows to rediscover devices.
View Devices (Global) Makes all devices visible within the inventory.
Table 6.5: Role group: Device
Role Description
All Device Job Rights (Global) Grants full access control to all Device Jobs.
Create Device Jobs (Global) Allows creating Device Jobs.
Create Device Jobs without The owner of that role can create jobs without the need to confirm
Deploy Device Jobs (Global) Allows deploying Device Jobs.
Modify Device Jobs Allows modifying assigned Device Jobs.

Role Description
Modify Device Jobs (Global) Allows modifying existing Device Jobs.
Use Device/Default Login Credentials Allows a user to use the device-specific or global default credentials
(Global) for device configuration. Otherwise, the user must use his own
credentials.
View Device Jobs (Global) Allows making all Device Jobs visible.
Table 6.6: Role group: Device Jobs
Role Description
All Discovery Job Rights (Global) Grants all permissions to Discovery Jobs.
Create Discovery Jobs (Global) Allows creating Discovery Jobs.
Create Discovery Jobs without The owner of that role can create jobs without the need to confirm
Modify Discovery Jobs Allows modifying Discovery Jobs assigned to groups.
Modify Discovery Jobs (Global) Allows modifying Discovery Jobs.
View Discovery Jobs (Global) Makes all Discovery Jobs visible.
Table 6.7: Role group: Discovery Jobs
Role Description
Acknowledge/Unacknowledge Alarm Allows to acknowledge or unacknowledge Alarms.
(Global)
All Element Rights (Global) Sets full rights to all elements (= folders, measurements).
All Maintenance Rights Set full maintenance rights to all elements.
Create Elements (Global) Allows creating elements within the Measurement Tree if
permissions are present to the parent folder.
Create Ticket (Global) Set permissions to create and clear tickets.
Create/Clear Alarm (Global) Allows to create or clear alarms.
Maintenance Alarming Allows to create maintenance for devices, which will disable only
monitors (Alarming).
Maintenance Override Interval Allows to create maintenance for devices, which will override
measurement interval.
Modify Elements Allows modifying elements within the Measurement Tree if
Modify Elements (Global) Allows modifying elements within the Measurement Tree if
View Elements (Global) Allows making all elements visible within the Measurement Tree.
Table 6.8: Role group: Elements

Role Description
All Phone Mappings Rights (Global) Allows user to view, create, and modify RTCP Agent Phone Filter
types.
Create Phone Mappings (Global) Allows creating RTCP Agent Phone Filter types.
Modify Phone Mappings Allows modifying RTCP Agent Phone Filter types.
Modify Phone Mappings (Global) Allows modifying RTCP Agent Phone Filter types.
View Phone Mappings (Global) Makes RTCP Agent Phone Filter types visible for the user. Only
supported in the Telco version. In the Enterprise version, all users
see the phone mappings.
Table 6.9: Role group: Phone Mappings
Role Description
All Report Rights (Global) Allows full control of the reporting features in StableNet®.
Create Reports (Global) Allows creating reports.
Modify Reports Allows modifying own reports.
Modify Reports (Global) Allows modifying all reports.
View Reports (Global) Allows viewing all reports.
Table 6.10: Role group: Reports
Role Description
All Service Domain Rights (Global) Allows full control of the Service Domains.
Create Service Domains (Global) Allows creating Service Domains.
Modify Service Domains Allows modifying assigned Service Domains.
Modify Service Domains (Global) Allows modifying Service Domains.
View Service Domains (Global) Allows viewing all Service Domains.
Table 6.11: Role group: Service Domains
Role Description
All Service Layer Rights (Global) Allows full control of the Service Layers.
Create Service Layers (Global) Allows creating Service Layers.
Modify Service Layers Allows modifying assigned Service Layers.
Modify Services Layers (Global) Allows modifying Service Layers.
View Service Layers (Global) Allows viewing all Service Layers.
Table 6.12: Role group: Service Layers
Role Description
All Service Type Rights (Global) Allows full control of the Service Types.
Create Service Types (Global) Allows creating Service Types.

Role Description
Modify Service Types Allows modifying assigned Service Types.
Modify Service Types (Global) Allows modifying Service Types.
View Service Types (Global) Allows viewing all Service Types.
Table 6.13: Role group: Service Types
Role Description
All Services Rights (Global) Allows full control of the Services.
Create Services (Global) Allows creating Services.
Modify Services Allows modifying assigned Services.
Modify Services (Global) Allows modifying Services.
View Services (Global) Allows viewing all Services.
Table 6.14: Role group: Services
Role Description
All Syslog Query Template Rights Grants access to all Syslog Query Templates.
(Global)
Create Syslog Query Templates (Global) Allows creating Syslog Query Templates.
Individual Syslog Queries (Global) Allows the execution of individual Syslog Queries.
Modify Syslog Query Templates Allows modifying own Syslog Query Templates.
Modify Syslog Query Templates Allows modifying all Syslog Query Templates.
(Global)
View Syslog Query Templates (Global) Makes all Syslog Query Templates visible.
Table 6.15: Role Group: Syslog Query Templates
Role Description
All Tag Filter Rights (Global) Allows full control on Tag Filter Management.
Create Tag Filter (Global) Allows creating Tag Filters.
Modify Tag Filter Allows modifying assigned Tag Filters.
Modify Tag Filter (Global) Allows modifying all Tag Filters.
View Tag Filter (Global) Allows viewing all Tag Filters.
Table 6.16: Role group: Tag Filter
Role Description
All Tag Tree Configuration Rights Allows full control of the Tag Tree Configuration.
(Global)
Create Tag Tree Configuration (Global) Allows creating Tag Tree Configurations.
Modify Tag Tree Configuration Allows modifying assigned Tag Tree Configurations.

Role Description
Modify Tag Tree Configurations Allows modifying Tag Tree Configurations.
(Global)
View Tag Tree Configuration (Global) Allows viewing all Tag Tree Configurations.
Table 6.17: Role group: Tag Tree Configuration
Role Description
All Trap/Syslog Color Management Allows to view the Trap/Syslog Color Management and allows to
Rights (Global) create and modify color mappings in the Trap/Syslog Color
Management.
Create Color Mappings (Global) Allows to create color mappings in the Trap/Syslog Color
Management.
Modify Color Mappings (Global) Allows to modify color mappings in the Trap/Syslog Color
Management.
View Trap/Syslog Color Management Allows to view the Trap/Syslog Color Management.
(Global)
Table 6.18: Role group: Trap/Syslog Color Management
Role Description
Modify Users and Groups (Global) Grants access to the user and group management.
View all Users and Groups (Global) Grants read-only access to the user and group management.
Table 6.19: Role group: Users/Groups
Role Description
All Weather Map Rights (Global) Grants access to all Weather Maps.
Create Weather Maps (Global) Allows creating Weather Maps.
Modify Weather Maps Allows modifying own Weather Maps.
Modify Weather Maps (Global) Allows modifying own Weather Maps.
View Weather Maps (Global) Makes all Weather Maps visible.
Table 6.20: Role group: Weather Maps
6.3. Examples
The following examples will give an idea on how groups can be used to fulfill specific security requirements.
These examples shall only give a basic understanding and may be adapted to specific needs.
6.3.1. Read-Only Group

The Read-Only Group should only have read-access permissions to element. It allows the user to work with
StableNet® without modifying anything.
Create a group named ReadOnlyGroup and assign the following roles to it:

Figure 6.10: Roles example: Read-Only Group
Additionally, the following tabs can be activated in Web Menu Display Settings tab (see Figure 6.8 for more
details):
• Analyzer: Charts Analyzer, Group Analyzer, and Category Statistic
• Help: all entries
6.3.2. NOC Group

People working in a Network Operation Center (NOC) need specific rights to do their daily job in network
monitoring. Create a group named NOC and assign for example the following roles to it:
Figure 6.11: Roles example: NOC Group
Users assigned to this group will have rights to rediscover assigned devices, acknowledge/unacknowledge
or create/clear alarms and schedule maintenances with Disable Monitors (Alarming) option.

Tip
Please be aware that this dialog only shows roles where the column Active is true. If you open
the Roles tab, you see all roles and you have to check all roles seen in the filtered list above.
Additionally, activate in Web Menu Display Settings tab (see Figure 6.8 for more details):
• Status: all entries
• Inventory: all entries
• Analyzer: all entries
• Reporting: all entries
• Device Automation: nothing
• Settings: all entries
• Help: all entries

Chapter 7. Settings and Properties
Abstract
This chapter describes the usage of the available settings and properties in StableNet®. Settings are
available for the StableNet® GUI and only affect the locally installed instance. Properties, however, change
the behavior of the StableNet® Server and all elements within StableNet®, like measurements, discoveries,
etc.
7.1. Local GUI Settings........................................................................................................53

7.2. Interface Filter.............................................................................................................53
7.3. Business Hour Groups....................................................................................................55
7.4. TCP Port Management....................................................................................................57
7.5. Report Template Management.........................................................................................58
7.6. MIB File Management....................................................................................................59
7.6.1. MIB Management...............................................................................................59
7.6.2. MIB Browser......................................................................................................60
7.7. Default Properties.........................................................................................................62
Settings and Properties - Infosim® Confidential - 52

7.1. Local GUI Settings
The GUI Settings are located in the main menu bar in the entry File. They offer several options in two tabs,
the GUI Settings and the Proxy Settings. Figure 7.1 and Figure 7.2 show the corresponding tabs. All settings
apply only to the currently running GUI.
Figure 7.1: GUI settings
If enabled, a sound is played when an alarm is raised.

If enabled, the GUI is maximized and the node the alarms corresponds to is selected.
If enabled, a message appears if an alarm is raised.
If enabled, duplicated event and log entries are filtered.
After changes in GUI Settings tab, a GUI restart is needed.

The Proxy Settings tab defines a system proxy to allow a connection to the internet GEO data search. These
settings are required if you want to use the GEO data view or need internet access.
Figure 7.2: Proxy settings
Defines the IP address of the proxy server.

Sets the port for the connection.
Sets a user to connect to the server.
Sets the corresponding password for the user.
7.2. Interface Filter

With interface filters, it is possible to select interfaces using their name, description, IP address, and type.
For example, they are used to specify the interfaces for which interface measurements should be created
automatically. The default properties "Auto measure Interface Additional: ... Filter" and "Auto measure

Interface Topology: ... Filter" are used for that. They can be found in the Auto Measure tab of the Default
Property Editor.
Interface filters are also used to specify the management interface that should be used to access devices
from StableNet®. The default properties "Management Interface ... Filter" are used for that. They can be
found in the Discovery tab of the Default Property Editor.
Each filter can consist of a comma-separated list of filter values. The filter values are case-insensitive. A
filter matches if the filter value is contained in the interface properties (e.g. the filter value eth matches
the interface name eth1). An interface is matched by a set of filters if at least one of the filters matches
the interface, even if the filters try to match different properties of the interface (for example, name and
description). So in technical terms, filters are OR-connected.
The prefix - is used to exclude matches. If an interface matches such an exclusion filter in any of the filter
types, this interface will not be part of the final interface list (even if another filter matches). Exclusion
filters always take precedence over other filters.
The prefix + is used to specify a mandatory match. Interfaces that do not match such a mandatory inclusion
filter will not be contained in the resulting interface set, even if another filter matched (see interface
eth2 in Example 7.1). A special case is using the value + without additional text. Then, an interface is
matched if the respective field is not empty. An example is to use the value + in the description field. That
matches all interfaces with a description.
It is possible that a single interface should be selected using interface filters and multiple interfaces match
the filters. In this case, the interface with the highest match score is selected. The entries in the
comma-separated list in each filter have a decreasing score. The matches of different interface filters are
added. If one interface is, for example, matched on the first entry of the list and another interface is
matched only in the second entry, then the first interface is selected.
Example 7.1: Interface filters

Consider the following interface filters:
Name Filter: eth,-eth10,-eth11

Description Filter: +automeasure
The list of interfaces that should be matched is as follows:
Interface Name Interface Description Filter Match

eth2 no
eth1 automeasure yes
eth10 no
eth11 automeasure no
serial no
serial2 automeasure yes
The interface eth2 is not matched, even though the name filter eth matched. That is because the
mandatory description filter +automeasure does not match.
The interface eth1 is matched because the mandatory description filter +automeasure matches. The
name filter does also match, but it is not necessary.
The interfaces eth10 and eth11 are not matched, because the name filter explicitly excludes them. It
does not matter whether the mandatory description filter matches.

The interface serial is not matched, because no filter matches. The interface serial2 is matched,
because the mandatory inclusion filter is matched. It is not necessary that the name filter matches as well.
7.3. Business Hour Groups

Business Hour Groups manage times of operation for measurements and monitor alarms. They are also
useful to define common maintenance intervals. If a business hour group is assigned to a device,
corresponding measurements will inherit the business hour group parameters.
A measurement or monitor will only be enabled during the time that is defined by the business hour group.
If no business hour group is assigned to a measurement, it is executed all the time.
Business hour groups are created via the Business Hour Group Management, shown in Figure 7.3. It can be
found under Options → Business Hour Group Management.
Figure 7.3: Business Hour Group Management
Filters the list of business hour groups depending on the input and the selected column.
Shows a list of all business hour groups available in the StableNet® system.
Allows creating a new business hour group.
Modifies the selected business hour group.
Deletes the selected business hour group.
The dialog shown in Figure 7.4 is used to create a new business hour group or modify existing ones.

Figure 7.4: Dialog for creating or modifying a business hour group
Specifies a name of the business hour group.

Describes the business hour group.
Defines one of the following actions for the business hour group:
• Disable Only Monitors (Alarming): The measurement will continue to run, data is imported,
but no alarming is performed.
• Disable Only Measurement Data: The measurement will continue to run, alarming is performed
but no measurement data will be imported.
• Disable Monitors (Alarming) and discard Measurement Data: The measurement will continue
to run, but no data is imported and no alarming is performed.
• Disable Measurement Execution and related Monitors: The measurement will not run at all
outside the business hours. If the measurement completely stops, no alarming will be
performed by these monitors as well. This is the only setting where the measurement is not
executed at all. This should normally be used.
Defines one of the following events if the business hour group stops a measurement:
• No Monitor Event: If a monitor is deactivated, no event will be created. The monitor will enter
a No Data Ok or No Data Alarm state.
• Create Monitor Maintenance Event: A maintenance event will be created. The monitor will be
in maintenance state outside the operation hours.
• Create Monitor No Data Event: A no data event will be created. The monitor will be in No Data
state outside the operation hours.
Sets the business hours. It is possible to configure up to two periods per day.

Note
The defined business hours are dependent on the time zone where the StableNet® Agent is
located.
Figure 7.5 shows the Once-Off Maintenance tab that allows defining maintenance intervals.
Figure 7.5: Business hour group once-off maintenance
Lists all once-off maintenance intervals.

Allows to add additional intervals.
Deletes the selected intervals.
Imports intervals from a CSV file.
Exports all intervals to a CSV file.
7.4. TCP Port Management

It is possible to discover and auto-measure usages of TCP ports of a device. If usages are found during the
device discovery, auto measurements for these can be created optionally.
The TCP ports are managed via the TCP Port Management entry in main menu bar entry Options. Figure 7.6
shows the corresponding dialog.

Figure 7.6: TCP Port Management
Filters the list of TCP port usages depending on the input. Allows filtering on different columns.
Lists all available TCP port usages in StableNet®.
Enables the discovery of the TCP port usage.
Enables the auto measurement of the TCP port if found during the discovery.
Opens a dialog to add a new TCP port usage to the system.
Modifies the currently selected TCP port usage.
Deletes the currently selected TCP port usage.
Imports TCP port usages from a CSV file.
Exports all TCP port usages to a CSV file.
7.5. Report Template Management

The Report Template Management allows to manage report templates for corporate identities or predefined
formula calculation in reports generated by StableNet®. HTML templates are used to create custom reports.
It is located in the main menu bar entry Templates → Report Template Management. Figure 7.7 shows the
management dialog.

Figure 7.7: Report Template Management
Lists all available report templates.

Allows to overwrite the selected template by importing a new one.
Deletes the selected template.
Exports the selected template.
Imports a new report template.
7.6. MIB File Management

Management Information Base (MIB) files are virtual databases and definitions. A MIB file provides formal,
tree-structured information of network objects that can be accessed with SNMP. Every object is identified
by an Object Identifier (OID). The OID is a node within the tree structure of the MIB.
7.6.1. MIB Management

StableNet® offers a MIB Management representing a list of all MIB files which are currently loaded. It is
located in the main menu entry Options → MIB Management and shown in Figure 7.8.

Figure 7.8: MIB Management
Allows filtering the list of MIB files depending on the input and the selected column.
Lists all available MIB files.
Imports a MIB file to StableNet®.
Exports the selected MIB files.
Deletes the selected MIB files.
Opens the MIB browser to connect to a device.
Opens the Agent Update Manager. This can be used to synchronize agents with MIB files from the
StableNet® Server.
7.6.2. MIB Browser

The MIB browser represents a tree of MIB definitions. Every definition is illustrated with a gray folder icon
inside of the tree.
Note
Because some public MIB definitions are not following the standard, many MIB file definitions
are known to have syntactical issues. This can cause problems, especially if some other MIB
definitions depend on them. Concerning MIB file syntax, the StableNet® MIB parser works
strictly. Even if other SNMP tools accept the file, there may be still syntactical errors.

Figure 7.9: SNMP Walk Selection Dialog
Selects a StableNet® Agent for the SNMP walk.

Defines the IP address of the device to connect to.
Sets the used SNMP version.
Defines the SNMP community and write community to access with SNMP to the device.
After connecting to the device, the SNMP Walk Dialog shown in Figure 7.10 is opened. It shows the MIB
tree structure. To look at the value of an OID, it is necessary to walk it.

Figure 7.10: SNMP Walk Dialog
Walks the subtree of the selected OID in the MIB tree.

Walks a single OID and retrieves the corresponding value.
Generates a table of all OIDs of the subtree of the selected OID.
Generates a table of the subtree of the selected OID with all OIDs and their corresponding values.
Finds an OID in the MIB tree. Supports regular expressions and reversed search direction.
7.7. Default Properties

The default properties are changeable via the StableNet® GUI and located in the Default Property Editor.
The editor opens by clicking Default Properties in the main menu bar entry Options or via the button shown
in Figure 7.11.
Figure 7.11: Location of the Default Property Editor
Figure 7.12 shows the Default Property Editor.

Figure 7.12: Default Property Editor
Displays the categories of the default properties.

Filters the property list depending on the input. Allows filtering on different columns.
Lists all properties of the corresponding category.
Resets the values of the currently shown category to the default values.
Backups all properties that are different from the default values to a template file.
Restores all default properties using a previously generated backup file. Before reading the backup
file, all properties are set to their default values. This way, all properties have the same values as at
the time the backup file was created (except for properties where the default values have been
changed by Infosim®, e.g. because of a StableNet® update).
Imports a template file provided by Infosim®. Here, only the changes in the file are applied (without
setting the properties to their default values).
Depending on the selected tab, additional buttons might be shown next to the Set Defaults button. These
allow to set additional properties for the respective tabs. For example, the report mail settings can be
changed in the Reporting tab and WMI credentails can be defined in the WMI tab.

Chapter 8. Agent
8.1. Overview.....................................................................................................................65
8.2. Agent Configuration......................................................................................................67
8.2.1. Agent List and Agent States..................................................................................68
8.2.2. Update Agents...................................................................................................69
8.2.3. Agent Expert.....................................................................................................70
8.3. High Availability (HA)...................................................................................................82
Agent - Infosim® Confidential - 64

StableNet® Agents are distributed instrumentation layer components that are responsible for all
device-related actions. All actions requested by the StableNet® Server are carried out by the StableNet®
Agent. In addition, StableNet® provides a special type of StableNet® Agent, the StableNet® Client Agent,
which is deployed directly on the monitored devices. An overview of the StableNet® Agent's role in
StableNet® is presented in Figure 8.1.
Figure 8.1: StableNet® Agent role
8.1. Overview
The StableNet® Agent is the critical component for monitoring in StableNet®. It executes all device-related
operations and is the single component that requires direct connection to the monitored devices. The
StableNet® Agent is scanning the network and querying device information during the discovery process.
Also, all measurements in StableNet®, such as SNMP, WMI, and script measurements, are executed by a

StableNet® Agent. Furthermore, the StableNet® Agent is also responsible for the fault monitoring. It
generates and clears alarms based on measurement data and monitor thresholds and performs root cause
analysis. In addition, the StableNet® Agent is an SNMP trap and syslog message receiver and can generate
alarms based on these notifications. The StableNet® Agent can also receive, process, and store flow data
locally. Finally, the StableNet® Agent also plays an important role when reading device configurations or
executing configuration commands on devices.
The role of the StableNet® Agent in different use cases is described in the following.
Discovery
During the discovery process, StableNet® performs a network scan based on the discovery input and queries
device information from the available devices. Although the StableNet® Server controls the discovery
process, the actions are performed by the StableNet® Agent. To scan the network, the StableNet® Agent
sends ICMP echo requests to the devices defined for discovery. In addition, device and topology information
is read from the available devices. For this purpose, the StableNet® Agent sends SNMP queries to the
devices. The StableNet® Server then stores the discovered data in the database and fills the StableNet®
inventory and topology graph.
Measurements
All measurements in StableNet® are executed by the StableNet® Agent. The StableNet® Agent is an SNMP
and WMI collector, SNMP trap and syslog message receiver, and can execute measurement scripts. Each
measurement is set up on the StableNet® Agent according to the measurement configuration received
from the StableNet® Server. After measurement setup, the StableNet® Agent will execute measurements
according to their schedule. The measurement execution is independent from the StableNet® Server and
will continue even if connection to the StableNet® Server is temporarily lost. Each measurement produces
measurement data, which is temporarily stored in a local database on the StableNet® Agent. The data is
regularly imported by the StableNet® Server and stored in the central StableNet® database. If the connection
from the StableNet® Server to the StableNet® Agent or to the database is lost, the measurement data
collected by the StableNet® Agent is imported after the connection is re-established without data loss.
Monitors and Alarming

The StableNet® Agent is also responsible for the handling of monitors and the generation of alarms, if
defined monitor thresholds are violated. In addition, the StableNet® Agent manages all other
monitor-related functions. These include alarm notifications based on Alarm Groups, enabling and disabling
monitors and measurements based on Maintenance Intervals or Business Hour Groups. Finally, the StableNet®
Agent also performs the root cause analysis in StableNet®, i.e. determining the root cause for a group of
alarms based on monitor dependencies and the root cause score of each monitor.
SNMP Traps
The StableNet® Agent acts as an SNMP trap receiver. For the correct textual representation of traps, the
StableNet® Agent requires all relevant SNMP MIB files that define traps, including their dependencies.
Otherwise, only OIDs and values will be shown. The required MIB files are marked for synchronization after
being loaded in StableNet®. However, they are not automatically synchronized to the StableNet® Agent.
The synchronization to the StableNet® Agents only takes place when manually triggered or during the
weekly full maintenance. After synchronizing MIB files to the StableNet® Agents, the StableNet® Agents
need to be restarted for the changes to take effect.
Whenever a trap is received, the StableNet® Agent will parse the trap data, including variable bindings,
according to the available MIB files, and store the data temporarily in a local database. The data is imported
regularly by the StableNet® Server and written to the central database. The trap data can then be viewed
in the StableNet® GUI.

If SNMP trap measurements are configured, the StableNet® Agent will check if received traps match the
defined measurements and generate monitor events accordingly.
SNMP version 3 provides the possibility to send encrypted traps. The StableNet® Agent can receive and
decrypt these traps using a file named trapuser.conf, which has to exist in the snagent/conf
folder. If the content of this file changes, the StableNet® Agent has to be restarted. The file specifies how
the encrypted traps have to be decrypted. It has to contain one line for each combination of a user and a
device in the following format:
user@authentication_pw@encryption_pw@authentication_type@engine_id@encryption_type
• user - SNMP username.
• authentication_pw - SNMP authentication password.
• encryption_pw - SNMP encryption password.
• authentication_type - SNMP authentication type. Possible values are md5 and sha.
• engine_id - The unique engine ID of the device.
• encryption_type - SNMP encryption type. Possible values are des or aes.
An @ character in the username or a password has to be quoted using -&+#AT.
Syslog
Similar to SNMP traps, the StableNet® Agent is also a syslog message receiver. Syslog messages are stored
temporarily in a local database and then imported by the server. The data will be stored in the central
database and can be viewed in the StableNet® GUI.
When processing syslog messages, the StableNet® Agent will check if they match any defined syslog
measurements. If this is the case, it will generate monitor events accordingly.
Flow
Another important function of the StableNet® Agent is to receive, process, and store flow data. Currently,
NetFlow (including v9), IPFIX, J-Flow, and sFlow (port 6343) are supported. The received data is stored
in a local database and can be analyzed using the Flow Query. The raw flow data is not imported by the
StableNet® Server or stored in the StableNet® database. Only flow measurement data is stored in the
database.
Device Configuration
The StableNet® Agent also plays a crucial role for the network configuration and change management
module. The connections to the devices are set up from the StableNet® Agent. The StableNet® Server does
not connect to the devices directly.
StableNet® Client Agent

The StableNet® Client Agent is deployed on the monitored devices and used to execute measurement scripts
or WMI queries locally on the devices. Each StableNet® Client Agent is managed by a StableNet® Agent.
The StableNet® Client Agent does not communicate directly with the StableNet® Server.
8.2. Agent Configuration

This section describes important StableNet® Agent configuration settings, how the current agent
configuration can be viewed and edited.

8.2.1. Agent List and Agent States
The StableNet® Agents are managed in the Agent List, shown in Figure 8.2. It contains one row for each
StableNet® Agent and displays basic StableNet® Agent information, such as name, IP address, version,
operating system, and the internal ID. In addition, the StableNet® Agent connection status and data import
progress information is also shown. The Last Commit column contains the date and time of the last data
import from the StableNet® Agent. The StableNet® Agent connection state is shown in the State column.
If the StableNet® Agent is running and a connection between the server and the StableNet® Agent is
established, the state displayed is connected, active or standby. Other states indicate a connection
problem to the StableNet® Agent. The StableNet® Agent may not be reachable, the license may have expired
or the StableNet® Agent could be down.
Figure 8.2: Agent list
If a StableNet® Agent is selected, additional details are displayed in the table on the right side, as shown
in Figure 8.3.
Figure 8.3: Agent details
The Agent States dialog displays a summary of the StableNet® Agents' status, as shown in Figure 8.4.

Figure 8.4: Agent states
Similar to the agent list, the StableNet® Agent name, version, and connection state are shown. The Last
Action Commit column shows the date and time of the action event, i.e. Alarm or OK, that was last imported
by the StableNet® Server and written to the database. Similarly, the Last Data Commit column shows the
timestamp of the measurement data that was last imported by the server.
Note
The Last Action Commit timestamps should be up to date. If this is not the case, the data import
to the server is lagging. This is usually caused by database or network problems. High load
on the StableNet® Agent can be another reason for data import issues. It is also known that
measurement data import can be delayed during the StableNet® full maintenance. In this
case, the delay is normal and represents no issue.
The table also shows the time difference between the StableNet® Agents and the StableNet® Server as well
as the time zone of each StableNet® Agent. The time difference should be equal to or nearly zero.
Note
Significant time differences between the StableNet® Server and the StableNet® Agents will
lead to problems with measurement, SNMP trap, syslog, and event data timestamps. For this
reason, time synchronization (e.g. NTP) is required for all StableNet® components.
The Measurements column shows the number of measurements configured on the StableNet® Agent. The
Work Queue shows the number of server requests that still need to be processed by the StableNet® Agent.
For example, changes in measurement or monitor settings, maintenance entries, etc.
8.2.2. Update Agents

The Agent Update Manager allows synchronizing the agent settings with the StableNet® Server. During the
synchronization process, all relevant settings and data from the server will be pushed to the agent. This
includes measurement and monitor configuration, alarm groups, and business hour groups. Depending
on the settings, other data is also synchronized: mail settings, business process scripts, MIB files, and
additional agent binaries. Additional binaries are, for example, special modules for SIP monitoring or
ticket system integration. Synchronization of the client agents managed by an agent is also possible. In
this case, business process scripts required by the client agent will be synchronized. The synchronization
to the client agents is done by the managing agent.
The Agent Update Manager, presented in Figure 8.5, shows a list of the agents. To synchronize agents,
select them from the list and click the Start Update button. If important settings or data, such as MIB files
or binaries, have been updated, the agent needs to be restarted. To make a restart mandatory after the
synchronization process is completed, regardless of the updated settings and data, the Force Restart check
box can be selected. Synchronizing client agents can be enabled using the Sync Client Agents check box.
The Status column shows the progress of the agent synchronization.

Figure 8.5: Agent Update Manager
8.2.3. Agent Expert

The Agent Expert displays important StableNet® Agent settings and configuration parameters. While some
parameters are read-only, others can be edited. The different Agent Expert tabs are presented in the
following.
8.2.3.1. Info
The Info tab displays general information about the StableNet® Agent, as shown in Figure 8.6. All information
is read-only.
Figure 8.6: Agent Expert - Info tab

General Information
Shows general information about the StableNet® Agent and the system it is running on. This
includes the StableNet® Agent version, IP address, and the number of measurements and monitors.
Load Information
Shows memory and CPU load performance data.
Timezone Information
Shows date and time information for the StableNet® Agent and the local GUI. It is important that
the UTC time of the StableNet® Agent and the GUI are equal. The date, local time, and time zone
of the StableNet® Agent and the GUI may differ. This is the case if the StableNet® Agent and the
GUI are running in different time zones.
Agent Modules
The table lists the modules of the StableNet® Agent, including their version. The available modules
depend on the license.
8.2.3.2. License
The License tab illustrates a summary of the license of the StableNet® Agent, as depicted in Figure 8.7. In
addition, it allows updating or saving the license to the local file system.
Figure 8.7: Agent Expert - License tab
8.2.3.3. Options
The Options tab shown in Figure 8.8 allows editing the StableNet® Agent's mail configuration and changing
the flow data storage settings.

Figure 8.8: Agent Expert - Options tab
The StableNet® Agent mail settings can only be edited if the option to synchronize them with the server
is disabled. This can be done in the Options tab of the Modify Agent dialog. For SMTP mail configuration,
set the mail server IP, the mail sender address and, optionally, mail server credentials. An option to enable
TLS for secure communication with the mail server is also available. The server IP can optionally specify a
port, for example 10.1.1.151:25. If the port is omitted, the default SMTP port 25 is used. To check
the mail settings, a test email can be sent.
Mails can also be sent by another StableNet® Agent as a proxy using the syntax agent:<ip>,<port>.
In that case, the mail server username and password will not be used. Instead, the mail configuration of
the proxy agent will be used. Both StableNet® Agents must have the same login credentials.
The flow storage settings define the maximum single and total file size for flow data stored locally by the
StableNet® Agent. This enables splitting the stored flow data into several files. If the size of the current
flow data file exceeds the limit, a new one is created. If the total size maximum is exceeded, the oldest
file is deleted.
8.2.3.4. Flow Router

The Flow Router table provides an overview of all flow data sources as well as traffic and flow statistical
data, as shown in Figure 8.9. For each source IP address, the last flow packet timestamp, the total traffic
rate, the flow traffic rate as well as the number of received flows per second and lost flows per second are
shown.

Figure 8.9: Agent Expert - Flow Router tab
8.2.3.5. Script
This view shows the alarm scripts and business process scripts available on the StableNet® Agent and
provides management functionality. Alarm scripts can be executed automatically when an alarm occurs
as part of the alarm groups in StableNet®. A list of all available alarm scripts on the StableNet® Agent is
displayed on the left. For managing alarm scripts, upload, download, and remove actions are provided.
Business process scripts are used to measure performance data in StableNet®. Similar to alarm scripts, a
new business process script can be added and existing scripts can be downloaded or removed.

Figure 8.10: Agent Expert - Script tab
8.2.3.6. Measurement
The Measurement tab shows a summary of all configured measurements on the agent. For each measurement,
the table consists of the internal measurement ID, the last and next measurement execution timestamp,
and the total number of measurement executions. The Database ID column shows the ID of the local agent
storage for that measurement. The internal agent module executing the measurement is displayed in the
Provider column. Status shows if the measurement is currently running or idle. Most of the time, the status
of a measurement will be idle, meaning the last execution is complete and it is waiting for its next scheduled
execution.

Figure 8.11: Agent Expert - Measurement tab
8.2.3.7. Data Store

The Data Store tab shows information about the local storage databases of the StableNet® Agent, called
stores. The StableNet® Agent manages different stores for the different type of data:
Type of data Description

db_<store ID> Measurement data.
log Log data.
trap Trap data.
syslog Syslog data.
netflow Flow data.
In addition to the database ID, the following data is provided:

First ID, Last ID Date and time of the first and last data entry stored.
Entry Count Number of data entries stored.
Total Size Total size of the store.
Last Commit Date and time of the last import to the StableNet® Server
from this store.

Commit IP IP address of the StableNet® Server collected this store.
Max. Totalsize The maximum total size for the store.
Figure 8.12: Agent Expert - Data Store tab
8.2.3.8. Monitor Store

The Monitor Store tab lists information about the local monitor storage databases of the StableNet® Agent.
Data storage per monitor is disabled by default and needs to be enabled if required. The data provided for
each monitor store is very similar to the Data Store table presented in Section 8.2.3.7.

Figure 8.13: Agent Expert - Monitor Store tab
8.2.3.9. Log
The Log tab shows the log entries of the StableNet® Agent similar to the StableNet® Agent's log file. For
each logged event, the event time, event ID, and the log message is displayed. The number of log entries
shown is limited by the End Date and Number of Logs parameters. The table always shows the
selected number of log entries up to the selected end date. By default, the end date is equal to the time
of the last log entry and the number of logs is 100.

Figure 8.14: Agent Expert - Log tab
8.2.3.10. Duplicate Log

Events that occur multiple times within a twenty-four-hour interval are marked as duplicates in the
StableNet® Agent's log and displayed in the Duplicate Log, as presented in Figure 8.15. For each duplicate
event, the interval within the repeated events occurred and the number of times the event was repeated
are shown. Similar to the log entries, the internal event ID and the event message are also displayed.

Figure 8.15: Agent Expert - Duplicate Log tab
8.2.3.11. Flow
The Flow tab allows editing flow settings for the StableNet® Agent. These flow settings are expert settings.
The user must have the GUI Expert Settings (Global) role to view or edit them.
The StableNet® Agent can forward flow data to other receivers. The Flow Receiver table shows all configured
receivers to which flow data is forwarded. To enable flow data forwarding to a specific receiver, add its IP
address and port to the table. To disable it, remove the corresponding entry from the table.

Figure 8.16: Agent Expert - Flow tab
8.2.3.12. Syslog
The Syslog tab allows editing syslog settings for the StableNet® Agent. These syslog settings are expert
settings. The user must have the GUI Expert Settings (Global) role to view or edit them.
The StableNet® Agent can forward syslogs to other receivers. The Syslog Receiver table shows all configured
receivers to which syslogs are forwarded. To enable syslog forwarding to a specific receiver, add its IP
address and port to the table. To disable forwarding, remove the corresponding entry from the table.
The bottom part of the tab allows to modify the source IP of received syslogs. If the syslog message contains
a string matching the specified regular expression, the source IP of the syslog will be set to the matched
IP address instead of the IP address where the syslog was actually received. This is very useful if syslogs
are forwarded from a centralized syslog collector. The default syntax is FORWARDED:<ip>, where <ip>
is an IPv4 address. The first capture group of the regular expression is used to set the new source IP address
of the syslog.

Figure 8.17: Agent Expert - Syslog tab
8.2.3.13. Trap
The Trap tab allows editing trap settings for the StableNet® Agent. These trap settings are expert settings.
The user must have the GUI Expert Settings (Global) role to view or edit them.
The StableNet® Agent can forward traps to other receivers. The Trap Receiver table shows all configured
receivers to which traps are forwarded. To enable trap forwarding to a specific receiver, add its IP address
and port to the table. To disable forwarding, remove the corresponding entry from the table.

Figure 8.18: Agent Expert - Trap tab
8.3. High Availability (HA)

For details about StableNet® Agent High Availability solutions, please refer to the technical document ADM
- High Availability.

Chapter 9. Agent Repository
Abstract
This chapter describes the StableNet® Agent Repository feature which helps to manage a large number of
installed StableNet® Agents by providing synchronization to the StableNet® Server.
9.1. Supported Functionality................................................................................................84

9.2. Agent Synchronization Settings......................................................................................85
9.3. File System Structure.....................................................................................................85
9.4. Client Agent Repositories...............................................................................................86
9.5. Mode of Operation........................................................................................................87
Agent Repository - Infosim® Confidential - 83

Depending on the synchronization settings, binaries, business process scripts and license files are updated
on the StableNet® Agents. It is recommended to use the same binaries, business process scripts and license
files for a StableNet® installation.
In addition, the StableNet® Agent Repository supports the update of StableNet® Client Agents used in
business process (script) measurements. StableNet® Client Agents are updated if the controlling StableNet®
Agents are synchronized and the option for Client Agent update is selected.
The update is triggered manually by the user for selected StableNet® Agents in the GUI.
9.1. Supported Functionality

This module allows synchronizing the following components to the StableNet® Agents:
• StableNet® Agent license file
• All business process scripts (userscript directory and all sub folders)
• All business process scripts additional data (userscriptdata directory and all sub folders)
• All system dependent scripts (userscript_dependent directory and all subfolders)
• All alarm scripts (alarmscript directory)
• StableNet® Agent binaries for the following operation systems:
• Windows 32 bit
• Windows 64 bit
• Linux 32 bit
• Linux 64 bit
• Additional binaries, e.g. MailSystem.jar, vmwared.jar, rtcpd.jar, cpuidsdk.dll,
ticketd.jar (bin directory)
• StableNet® Client Agent binaries for Windows and Linux
• StableNet® Client Agent license file
The following components are updated for the StableNet® Client Agents:
• StableNet® Client Agent license file
• All business process scripts (userscript directory)
• StableNet® Client Agent binaries for the following operating systems:
• Windows 32 bit
• Linux 32 bit
• The cpuidsdk.dll module on Windows based StableNet® Client Agents
Note
On Windows platforms, files (e.g. business process scripts) opened by the system or a running
process can not be replaced by the StableNet® Agent synchronization. This is a technical
limitation of the Windows platform. On Linux open files can be always replaced.
The script names must not use any blanks or non ASCII characters! The different platforms
disallow characters like ":", "\", "/".
For the StableNet® Client Agent Repository sub folders are used which are included in the
repository!

9.2. Agent Synchronization Settings
Find the synchronization settings during the Agent creation process. It is also possible to adjust
synchronization settings within the Modify StableNet Agent dialog.
Agent Synchronization Settings
Setting Description
Synchronize Business Process Scripts All Business Process Script related files (userscript,
userscriptdata and
userscript_dependent directory) are
synchronized with the StableNet® Agent.
Synchronize MIB Files and Binaries MIB files, StableNet® Agent binaries and additional
binaries directory are synchronized.
9.3. File System Structure

The Agent Repository is stored in the configuration directory of the StableNet® Server:
snmw/config/agent. The structure is described in the table below. Please note that the file names
and directory names are case-sensitive.
File System Description

snmw/config/agent Main directory of the Agent
Repository.
snmw/config/agent/modules Modules of the StableNet® Agent, e.g.
the flow module.
snmw/config/agent/license.dat License file replacing all license files
from the Agents.

File System Description
snmw/config/agent/client_license.dat License file replacing the license files
of all Client Agents used by the
updated Agent.
snmw/config/agent/Windows/client_snagent.exe Client Agent binary for Windows.
snmw/config/agent/Linux/client_snagent Client Agent binary for Linux.
snmw/config/agent/Windows/snagent.exe Agent binary for Windows 32-bit.
snmw/config/agent/Windows/snagent64.exe Agent binary for Windows 64-bit.
snmw/config/agent/Linux/snagent Agent binary for Linux 32-bit.
snmw/config/agent/Linux/snagent64 Agent binary for Linux 64-bit.
snmw/config/agent/Shared/userscript Directory structure for all Business
Process Scripts. All scripts located in
this directory and subdirectories are
synchronized to the Agent. Additional
scripts of the Agent are removed.
Please note that this directory
regarding to Client Agent
synchronization is described
separately (see Section 9.4).
snmw/config/agent/Shared/userscriptdata Directory for the Business Process
Scripts' additional data. All data files
located in this directory and
subdirectories are synchronized with
the Agent. Additional data files of the
Agent are removed. Please note that
this directory regarding to Client
Agent synchronization is described
separately (see Section 9.4).
snmw/config/agent/Shared/userscript_dependent Directory structure for all
system-dependent Business Process
Scripts.
snmw/config/agent/Shared/alarmscript Directory for all Alarm Scripts. All
Alarm Scripts missing in this directory
are also removed from the Agent.
snmw/config/agent/Shared/bin Directory for additional binaries.
9.4. Client Agent Repositories

When using StableNet® Client Agents, so-called Client Agent Repositories have to be defined that may be
deployed on the respective StableNet® Client Agents. In order to define a StableNet® Client Agent Repository,
create a subdirectory in the folders userscript and userscriptdata. The names of these directories
define the names of the StableNet® Client Agent Repositories.
Examples:

Setting Description
Synchronize Business Process Scripts All Business Process Script related files (userscript,
userscriptdata and
userscript_dependent directory) are
synchronized with the StableNet® Agent.
Synchronize MIB Files and Binaries MIB files, StableNet® Agent binaries and additional
binaries directory are synchronized.
In order to prevent data flood in the network, the content of a Client Agent Repository is not synchronized
by default during an update of the controlling StableNet® Agent. The respective devices have to be explicitly
configured, which can be done both in the GUI and via an XML Discovery by using the
clientagentrepository attribute of the device element. The syntax is a comma-separated list of
the repository names, for example windows,linux,mac. Prepending a "–" to the repository name
causes the respective files to be removed from the Client Agent machine. By default no file is deleted, at
most it is overridden if it had been changed in the repository.
Note
The subfolders in the StableNet® Client Agent Repository are only used for grouping the files
into repositories. In the StableNet® Client Agent, the files will be placed in the folders
userscript or userscriptdata without subfolders.
Examples:
Client Agent Repository Result from a StableNet® Agent's perspective

configuration
linux All scripts in the folders userscript/linux and
userscriptdata/linux are added to the StableNet® Client Agent.
linux,-windows All scripts in the folders userscript/linux and
userscriptdata/linux are added to the StableNet® Client Agent.
All files in the folders userscript/windows and
userscriptdata/windows are removed from the StableNet®
Client Agent.
9.5. Mode of Operation

StableNet® Agent synchronization is enabled once the directory structure, described in Section 9.3, has
been set up on the StableNet® Server. The update process starts with calculating the MD5 hash sum for
the respective file. If the file exists remotely, an MD5 sum will be calculated as well. If the MD5 sums do
not match or the file does not exist remotely, the file from the repository will be pushed onto the StableNet®
Agent.
The same procedure applies for each file in a directory. Files not being contained in the repository directories
or their sub folders, are removed from the StableNet® Agents.
If the userscript directory does not exist in the repository, the files in the directory
userscript_dependent and its sub folders will be added to the StableNet® Agents. Additional files
on the StableNet® Agents will not be removed in that case.
Dependent on the settings (see Section 9.2), the update executes the following procedures:
1. If a license file has been stored in the repository, it is uploaded to the StableNet® Agents.

2. Business Process Scripts in the directory userscript and sub folders are updated.
3. All scripts in the directory userscript_dependent are updated.
4. Business Process Scripts in the directory userscriptdata and sub folders are updated.
5. Alarm scripts in the directory alarmscript are updated.
6. The StableNet® Agent binary, depending on the installed operation system, is updated.
7. Additional binaries from the bin directory are updated.
8. The StableNet® Client Agent license is updated.
9. The StableNet® Client Agent directories userscript and userscriptdata are updated
according to the selected StableNet® Client Agent repository (see Section 9.4).
10. The StableNet® Client Agent binaries are updated.
11. The MIBs which define SNMP traps in the directory mibs are updated.
12. StableNet® Agents are restarted if files in the directories bin or mibs have been changed, the
license has been changed or a restart has been explicitly requested by the user.
13. StableNet® Client Agents are restarted if the StableNet® Client Agent binaries have been
changed.
StableNet® Client Agents are synchronized for all devices whose controlling StableNet® Agent is updated.
The same applies if a device with a configured StableNet® Client Agent is discovered.
The MIB files are not stored in the repository but synchronized from the MIB storage of the StableNet®
Server. Only MIB files needed for SNMP traps are synchronized.
The StableNet® Agent binary is updated basing on the installed version. 64-bit installations are always
updated with 64-bit binary versions, and 32-bit with 32-bit versions, even if the operating system supports
a different version. StableNet® Client Agent binaries are always 32-bit.

Chapter 10. Maintenance
10.1. StableNet® Maintenance...............................................................................................90
10.1.1. Daily Maintenance............................................................................................90
10.1.2. Full Maintenance..............................................................................................90
10.2. Backup.....................................................................................................................90
10.2.1. StableNet® Server.............................................................................................90
10.2.2. StableNet® Agent..............................................................................................93
10.2.3. StableNet® GUI.................................................................................................93
10.3. Update.....................................................................................................................93
10.3.1. StableNet® Update............................................................................................93
10.3.2. License Update.................................................................................................94
Maintenance - Infosim® Confidential - 89

10.1. StableNet® Maintenance
In StableNet® there are two integrated Maintenance Jobs. One is executed daily and the other one weekly,
where the execution time can be changed in the Data Storage tab of the Default Properties (Expert) dialog.
The GUI Expert Settings (Global) role is necessary to view this dialog.
10.1.1. Daily Maintenance

This job is executed every day at midnight and performs basic operations in order to maintain the database.
Hereby, partitions are dropped and created according to the Time To Live (TTL) defined in the Default
Properties. Furthermore, meta data (for example invalid user relations or measurements with missing
references) is cleaned up and archived reports exceeding their TTL are removed. All StableNet® Agents are
synchronized according to the selected options (SMTP, MIB, Binaries, Business Process Scripts). Finally,
log files are zipped and the ones exceeding their TTL are deleted.
10.1.2. Full Maintenance

This job starts every Saturday at midnight and extends the Daily Maintenance by additional tasks. During
the execution of the job missing Action Events are (re-)created and the configuration tables are backed
up as zip file. Additionally, the folder config is zipped as well. Both zip files are stored in the folder
auto-backup of the StableNet® Server. Finally, all remaining data is aggregated corresponding to the
settings in the Default Properties.
10.2. Backup
This chapter presents the backup and restore process of the StableNet® environment. This includes the
StableNet® Server, the Agent and the GUI as well as the database. For some actions, it is recommended to
use the StableNet® Database Manager. Additional information on the database manager can be found in
Section 11.1.
The following sections describe the backup and restore of each StableNet® component, the StableNet®
Server, the StableNet® Agent and the StableNet® GUI.
10.2.1. StableNet® Server

This section describes the automatic and manual backup procedure as well as the restore procedure of the
StableNet® Server. The installation directory of the server is denoted with <SNMW_HOME> from now on.
The default installation directory of the server is the following:
• Linux: /opt/stablenet/snmw
• Windows: C:\Windows\snmw
10.2.1.1. Automatic StableNet® Server Configuration Backup

Configuration backups are created automatically by the StableNet® Server during the full maintenance
job. The backup files are stored in the <SNMW_HOME>/auto_backup/ directory. The job creates two
ZIP files. One file contains the configuration files from the <SNMW_HOME>/config. The second file
contains all database tables with metadata like devices, measurement configurations, job definitions etc.

Figure 10.1: StableNet® Full Maintenance Job Default Properties
Property defining the interval of the full maintenance and thus, the frequency.
Offsets the full maintenance job. Default starting time is Saturday, 0:00 a.m.
In this example, the full maintenance job starts every Saturday morning at 0:00 a.m. by default. Hence,
a weekly backup of the configuration data exists. However, it is possible to adjust the time offset and the
interval in order to delay the job execution or change the frequency in the expert properties shown in
Figure 10.1.
Note
It is not recommended to set the interval below seven days.
10.2.1.2. Manual StableNet® Server Backup

In addition to the automatic configuration backup described in Section 10.2.1.1, it is possible to create
backups manually, as well. The database manager provides the necessary functionality. For more information
on StableNet® Tools and the database manager, see Chapter 11.
Several commands of the database manager allow the backup of data from StableNet®.
• A manual backup of the configuration data of StableNet® like in Section 10.2.1.1 is created by
using the parameter -backup.
On Linux systems, for example, run the command
./StableNetDatabaseManager.sh -backup
from the <SNMW_HOME> directory. It creates the two backup containers

backup_yyyy_mm_dd_hhmm.zip containing the configuration databases tables in ASCII
format and config_yyyy_mm_dd_hhmm.zip containing the StableNet® Server configuration
folder. Both files are stored in the <SNMW_HOME>/auto_backup directory.

• It is possible to export the database tables containing metadata only.
On Linux systems, for example, run the command
./StableNetDatabaseManager.sh -exportconfig configuration/backup_tables
from the <SNMW_HOME> directory. It creates ASCII files for all configuration database tables in
the <SNMW_HOME>/configuration folder with the prefix backup_tables. Hence, the
second parameter is an arbitrary prefix of all files.
• The complete database is backed up with the database manager parameter -exportdata
<fileprefix>.
All tables from the database are exported to ASCII files located and prefixed with corresponding
fileprefix from the call. On Linux systems, for example, run the command
./StableNetDatabaseManager.sh -exportdata database/backup_tables
from the <SNMW_HOME> directory. This will store all files in the <SNMW_HOME>/database
directory with the prefix backup_tables. When doing a full backup, the StableNet® Server
must not be running.
10.2.1.3. StableNet® Server Configuration Restore

For the restore process of the StableNet® Server, it is important that the database is up and running. The
restore procedure is as follows:
1. Run the StableNet® Server installer in silent mode (database and mail settings must not necessarily
be correct because these settings will be restored).
2. Stop the StableNet Server Controller service.
On Linux systems, the server service is stopped, for example, with service snmw stop. On
Windows systems, the server service is stopped, for example, in the Service Manager.
3. Overwrite the <SNMW_HOME>/config directory with the backup.
4. Import the configuration tables to the database. Depending on the type of backup, the
configuration table ASCII files have to be extracted from the corresponding ZIP file at first.
Afterwards, the files are imported using the StableNet® Database Manager. On Linux systems, this
is achieved by calling the command
./StableNetDatabaseManager.sh -importfile <fileprefix>
in the <SNMW_HOME> directory. The parameter <fileprefix> defines the location containing
the database table files as well as a chosen file prefix. The content of the tables will be overwritten
with the content of the imported files.
5. Start the StableNet Server Controller service.
On Linux systems, the service is started, for example, with the command service snmw
start on the command line. On Windows systems, it can be started in the Service Manager.
10.2.1.4. StableNet® Server Full Restore

The restore of the StableNet® Server including all measurement data is the same as for the configuration
data described in Section 10.2.1.3. But instead of importing only configuration tables, all tables are
imported using the command
./StableNetDatabaseManager.sh -importfile <fileprefix>

in the <SNMW_HOME> directory. The content of the tables will be overwritten with the content of the
imported files.
10.2.2. StableNet® Agent

The following two sections describe the backup and restore of the StableNet® Agent. The agent directory
is denoted with <SNAGENT_HOME> from now on. Its default location is the following:
• Linux: /opt/stablenet/snagent
• Windows: C:\Windows\snagent
10.2.2.1. StableNet® Agent Backup

The backup of the StableNet® Agent needs to include the following directories:
• <SNAGENT_HOME>/alarmscript
• <SNAGENT_HOME>/bin
• <SNAGENT_HOME>/conf
• <SNAGENT_HOME>/mibs
• <SNAGENT_HOME>/userscript
The listed directories contain only metadata. If raw data like Flow, Syslogs or SNMP traps need to backed
up as well, the directory <SNAGENT_HOME>/data needs to be included in the backup process.
10.2.2.2. StableNet® Agent Restore

The StableNet® Agent restore procedure is as follows:
1. Run the StableNet® Agent installer in silent mode.
2. Stop the StableNet Agent service.
On Linux systems, the agent service is stopped, for example, with service snagent stop.
On Windows systems, the agent service is stopped, for example, in the Service Manager.
3. Overwrite the directories listed in Section 10.2.2.1 with the backup.
4. Start the StableNet Agent service.
On Linux systems, the CLI command service snagent start starts the agent service. On
Windows systems, the Service Manager starts the agent service.
5. Synchronize the StableNet® Agent using the StableNet® GUI.
10.2.3. StableNet® GUI

A backup of the StableNet® GUI is not necessary because it contains no explicit configuration.
10.3. Update
This chapter describes the update process of the different StableNet® components. In the first section,
the update process of a normal environment is presented. After that, the license update is explained. The
update process for a StableNet® High Availability setup is explained in the technical document ADM - High
Availability.
10.3.1. StableNet® Update

The StableNet® Server and StableNet® Agent are updated by running the installer of the corresponding
component. The component being updated must not be running. The existing configurations are reused
after the installation routine is finished. Additionally, it is important to always have the same version of

the server and the agent installed. After updating the server, it is recommended to check the server.log
in the log directory of the StableNet® Server installation directory for errors. As the StableNet® Agent is
not running for a certain period, there will be a lack of measurement data during that short downtime.
The GUI can be updated by running the installer as well. If the GUI is not updated manually, it will be
updated automatically when connecting to a StableNet® server with a different version. In this case, the
rest of the GUI installation, for example the Java runtime, will remain the same.
If you are using a Windows machine, please make sure that the setups are run as administrator.
10.3.2. License Update

The license file license.dat of StableNet® is located in the StableNet® Agent installation directory:
<SNAGENT_HOME>/conf. It contains two expiration dates, the License Maintenance
Expiration and License Expiration. If the first date expires, StableNet® support and access
to updates is unavailable. If the latter date expires, the StableNet® Agent stops the measurement processes.
Hence, the license needs to be kept up to date. There are several ways to update an expired license file
with a new one:
• The license file can be updated in the StableNet® GUI Agent Expert dialog (see Section 8.1).
• The license file can be replaced manually in the agent directory.
• In a high availability, all agents are managed with an Agent Repository (see document
ADM - Agent Repository). The license file will be updated in the repository and afterwards all agents
will be synchronized in the GUI.

Chapter 11. StableNet® Tools
11.1. StableNet® Database Manager.......................................................................................96
11.1.1. General...........................................................................................................96
11.1.2. Performance....................................................................................................96
11.1.3. Import............................................................................................................97
11.1.4. Export............................................................................................................97
11.1.5. SQL Operations.................................................................................................97
11.1.6. Expert Parameters.............................................................................................98
11.2. StableNet® Management Tool........................................................................................98
StableNet® Tools - Infosim® Confidential - 95

The StableNet® Tools consist of the StableNet® Database Manager and the StableNet® Management Tool.
Since the StableNet® Database Manager works with the database, it is important that the StableNet® Server
is not running to avoid conflicts. The StableNet® Management Tool, however, is only able to work while
the server is running.
Both, the StableNet® Database Manager and the StableNet® Management Tool are located in the installation
directory of the StableNet® Server.
11.1. StableNet® Database Manager

The StableNet® Database Manager connects to the database with the configuration from the StableNet®
Server data source directly and is mainly used for backup and restore operations. The StableNet® Server
must not be running while working on the database to avoid conflicts.
The StableNet® Database Manager is located in the installation directory of the StableNet® Server. On a
Windows system, it is called like this:
StableNetDatabaseManager.bat <parameters>
On a Linux system, it is called like this:
StableNetDatabaseManager.sh <parameters>
In the following sections, all parameters of the Database Manager are listed and explained.
11.1.1. General
The following parameters are used to obtain general information about the database related to the data
source:
-info
Shows information about the database and the full maintenance state.
-list
Lists all database tables and the number of contained rows.
-partinfo
Shows information about all partitioned database tables.
-partlist <tablename>
Shows the list of partitions for the specified table.
-newlog
Creates a new unique log file for this call of the StableNet® Database Manager. Otherwise, the
existing one is overwritten.
11.1.2. Performance
For database performance checks, the following two parameters are used:
-check
Checks the database connection and executes a performance test with 10 million data rows and
50,000 measurements.
-performance [size in millions] [number of measurements]
Checks the database connection and executes a performance test with [size in millions]
data rows and [number of measurements] measurements. If one or both options are not
given, a standard performance test with 115.2 million data rows and 5,0000 measurements is
executed. The number of measurements is allowed to range from 10,000 to 500,000 in steps of
1,000.

11.1.3. Import
The following parameters are used to import tables or data to the database.
-importfile <filename>
Imports data from the file specified in the <filename> parameter. All previous data in the
respective tables is deleted. This parameter needs the -force parameter being added to the call
to be executed. The StableNet® Server must not be running.
-addfile <filename>
Imports data from the file specified in the <filename> parameter. This parameter needs the
-force parameter being added to the call to be executed. If this is used to import content to
data tables (as opposed to config tables), the StableNet® Server can be running. Otherwise, the
StableNet® Server must not be running. This command is usually used for moving data between
databases.
11.1.4. Export
The following parameters export data from the database to files. Some parameters require a filename to
specify where the data should be exported to. It is possible to add an existing directory to the filename,
e.g. sample_directory/exportfile.
-backup
Creates a backup of the configuration tables and the configuration folder of the StableNet® Server
in the folder <install_dir>/auto_backup. The files of the configuration tables are stored
in the ZIP file backup_yyyy_mm_dd_hhmm.zip. The configuration folder of StableNet® is
stored in the ZIP file config_yyyy_mm_dd_hhmm.zip.
-exportdata <filename>
Exports the complete database to the specified file.
-exportconfig <filename>
Exports the configuration tables to the specified file.
-exporttable <tablename> <filename>
Exports a single database table to the specified file. The exact table name is required to export
the table.
-exportpartition <tablename> <partitionname> <filename>
Exports the specified partition. To get an overview on all available tables with partitions, use the
command -partinfo. To get all partition names of a table, use the command -partlist
<tablename>.
11.1.5. SQL Operations

The following parameters execute SQL related operations on the database:
-createtables
Creates all database tables needed by the StableNet® Server.
-drop
Drops all tables and data created by StableNet® in the specified database. This parameter needs
the -force parameter being added to the call to be executed.
-droptable <tablename>
Drops the specified table. This parameter needs the -force parameter being added to the call
to be executed.
-deletetable <tablename>
Deletes all data from the specified table. This parameter needs the -force parameter being
added to the call to be executed.

-query <command>
Executes the SQL query <command>.
-update <command>
Executes the SQL update <command>.
11.1.6. Expert Parameters

The expert parameters list is shown by calling the database manager with the parameter -force.
The following list shows all available expert parameters:
-convertversion <version>
Executes the database converter from version <version>.
-setversion <version>
Sets the database serial to the version <version>.
-updatepartitions
If the database supports partitioning, this parameter creates new partitions the next 90 days and
drops old partitions that are outside of the time to live for the respective tables.
-convertcharacters
If the database uses the StableNet® encoding, all data that is exported using the parameters
-exportdata, -exportconfig, -exporttable or -exportpartition will be
converted from the StableNet® encoding during the export. Also, all data that is imported using
the parameters -importfile or -addfile will be converted to the StableNet® encoding
during the import.
-installtest
Executes the database test that is also executed after installing the StableNet® Server.
-dsfile <filename>, -dsname <datasource>
Allows to specify a data source file and a data source name that the StableNet® Database Manager
will use to connect to the database. Without these parameters, the StableNet® Database Manager
will connect to the data source StableNetDS specified in the file
<installdir>/standalone/configuration/standalone.xml.
11.2. StableNet® Management Tool

The StableNet® Management Tool is mainly used to do a full maintenance while the server is online or to
refresh the StableNet® Server caches. Therefore, it asks the server to perform the requested actions.
The StableNet® Management Tool is located in the installation directory of the StableNet® Server. On a
Windows system, it is called like this:
StableNetManagementTool.bat <parameters>
On a Linux system, it is called like this:
StableNetManagementTool.sh <parameters>
The server performing the action is specified via the following command line parameter:
-login "<ip>,<port>,<username>,<password>"
Specifies the login credentials for the StableNet® Server, e.g. -login
"127.0.0.1,5443,infosim,stablenet". If not passed as a parameter, the default
setting with server 127.0.0.1, port 5443, username infosim and password stablenet
is used.
Furthermore, the Management Tool supports the following parameters:

-maintenance
Starts the maintenance of the StableNet® Server.
-fullmaintenance
Starts the full maintenance of the StableNet® Server.
-invalidate
Invalidates all caches of the StableNet® Server and forces them to be reread from the database.
If the StableNet® Management Tool is called without a parameter, a list of all available parameters will be
printed.

Chapter 12. Bootstrap Importer
StableNet® provides the possibility to import a vast amount of data such as measurement templates, job
templates, default properties or MIB files at the server startup. This helps to deploy default measurement
templates, jobs, and properties at once. The imported data is available in StableNet® automatically after
the server startup and can be used out of the box.
To make use of the Bootstrap Importer, a file named imports.zip has to be placed in the
config/imports directory of the StableNet® Server and contain the data which shall be imported.
After the server startup has finished successfully, the file will be renamed and the current timestamp will
be appended. The ZIP file has to adopt a specific structure which is described in the following.
Table 12.1 shows all possible items which can be imported during the StableNet® Server startup as well as
the structure of the ZIP file. For each item that should be imported the corresponding files have to be put
in the respective folders as described by the Folder name and the File type column in the table.
Item Folder name File type

Agent Repository agent All components supported by the agent
repository module, as described in Section 2.1.
Supported Functionality in the document
ADM - Agent Repository.pdf. Inside the agent
directory the folder structure has to follow, as
described in Section 2.3. File System Structure.
Backup Script Files backup_job_templates One or more backup script files, as described in
the document OP - Backup Script.pdf.
Template-Based configuration_job_templates One or more XML templates for Template-Based
Configuration Job Configuration Jobs, as described in the
Templates document
OP - Template-Based Configuration Jobs.pdf.
Dashboards dashboards Exported dashboards, as described in Section
12.5. Dashboard in the document
StableNet-Back-Office-Manual.pdf.
Database Variables db_variables Exported database variables, as described in
Section 10 Database Variables in the document
Default Properties default_properties Default properties backups, as described in
Section 6.10. Default Properties in the
document StableNet-Back-Office-Manual.pdf.
Device Info Commands device_info_commands Exported device info commands, as described
in Section 17.2.2. Device Info Commands in the
XML Discovery discovery_job_templates XML Discovery templates and corresponding
Templates CSV files, as described in the document
OP - XML Discovery.pdf.
EoX Device Definitions eox_devices Exported EoX device definitions, as described
in Section 16. End-of-Life (EoX) in the document
Bootstrap Importer - Infosim® Confidential - 100

Item Folder name File type
EoX Module eox_modules Exported EoX module definitions, as described
Definitions in Section 16. End-of-Life (EoX) in the document
EoX Software eox_software Exported EoX software definitions, as described
Definitions in Section 16. End-of-Life (EoX) in the document
Measurement measurement_templates Templates for SNMP measurements, WMI
Templates measurements and external measurements, as
described in in the document
OP-TemplateCreation(Script,External,SNMP,WMI).pdf.
MIB Files mib_files MIB files.
Policy Checking Job policy_job_templates Perl scripts which are used for performing
Scripts script-based policy checks, as described in
Section 17.6. Script-Based Policy Checks in the
Usergroups usergroups Exported usergroups, as described in Section
5.2.
Management of Users, Profiles, Groups and Roles
in the document
Userprofiles userprofiles Exported userprofiles, as described in Section
5.2.
in the document
Users users Exported users, as described in Section 5.2.
in the document
Vulnerabilities vulnerabilities Exported vulnerabilities, as described in Section
18. Vulnerabilities in the document
Table 12.1: Structure of imports.zip
The following example shows how the structure of imports.zip may look like.
imports.zip
|
|---agent
| |
| |---Linux
| | |
| | |---client_snagent
| |
| |---Shared
| | |
| | |---bin
| | | |
| | | |---MailSystem.jar
| | |

| | |---userscript
| | | |
| | | |---linux_cpuload.sh
| | | |---linux_freedisk.sh
|
|---backup_job_templates
| |
| |---cisco_bu_script.pl
|
|---default_properties
| |
| |---default.template
|
|---device_info_commands
| |
| |---Cisco_info_commands.xml
|
|---mib_files
| |
| |---CISCO-MEMORY-POOL.MIB
| |---CISCO-ENHANCED-MEMPOOL.MIB
|
|---vulnerabilitites
| |
| |---Cisco_vulnerabilities.xml

Chapter 13. Troubleshooting
13.1. StableNet® Server not available....................................................................................104
13.2. StableNet®Agent State down/not connected...................................................................105
13.3. StableNet® Client Agent is not working..........................................................................105
13.4. E-Mails are not sent by the StableNet® Server..................................................................106
13.5. Cannot connect to StableNet® Server remotely................................................................106
13.6. StableNet® License is invalid or expired.........................................................................106
Troubleshooting - Infosim® Confidential - 103

The following chapter helps to solve basic problems that can occur when working with StableNet®. For
further questions, please contact Infosim® technical support by using the ticket system:
https://tickets.infosim.net/otrs/customer.pl
13.1. StableNet® Server not available
Solution 1
Check if the server service is running. For Windows, this can be done by opening the service view
and searching for StableNet® Server Controller. For Linux, log into the shell and execute ps. If
the service is not running, start it.
Solution 2
Check if the database service is reachable. This can be done by using the
StableNetDatabaseManager, located in the server installation folder. Enter
StableNetDatabaseManager.bat -info for Windows or
StableNetDatabaseManager.sh -info for Linux. If the database is not running, it
states Communications link failure.
Solution 3
Check if the database was created and the correct user was assigned to it. This can be done by
using the StableNetDatabaseManager, located in the server installation folder. Enter
StableNetDatabaseManager.bat -info for Windows or
StableNetDatabaseManager.sh -info for Linux. If there is no user or the user has
wrong credentials, it shows an error message, saying Access denied for User.
The user that is used by StableNet® to connect to the database can be found in the file
<server-install-dir>/wildfly/standalone/configuration/standalone.xml
in the datasources subsystem.
Solution 4
The database service may have been started after the server service, which will cause an incorrect
start. After restarting the server service, it will recognize the database and start properly.
Solution 5
The server is currently starting and adding the tables to the database. To prove that, check the
server.log (snmw/log) for DbUtil.createTable. This can take a couple of minutes,
depending on the resources of the system.

Solution 6
The server is currently starting and reading a lot of data. This can take a couple of minutes,
depending on the resources of the system.
13.2. StableNet®Agent State down/not connected

Solution 1
Check if the agent service is running. For Windows, this can be done by opening the service view
and searching for the StableNet® Agent. For Linux, log into the shell and execute ps. If the service
is not running, start it.
Solution 2
Open PuTTy, located in the server installation folder and connect to the corresponding agent. If
the connection is established, the service is running. If it is not working, check if the service is
running and start it if needed.
13.3. StableNet® Client Agent is not working

Solution 1
Open PuTTy, located in the server installation folder and connect to the corresponding agent.
Connect to the client agent via telnet using [telnet ip port]. If the connection is
established, the service is running. If it is not working, check if the service is running and start it
if needed.
Solution 2
Check if the TCP communication of the firewall is configured correctly. The firewall has to accept
connections to TCP port 5100.

13.4. E-Mails are not sent by the StableNet® Server
Solution
The mail server properties of the StableNet® Server can be set in the Mail Server Properties dialog
which can be found in the Options menu.
By default, the mail server properties of the StableNet® Server are synchronized to the StableNet®
Agent. This can be deactivated by removing the flag Synchronize Mail SMTP Setting in the Options
tab of the Modify Agent dialog. If the synchronization is deactivated, the mail server properties
of the StableNet® Agent can be set in the Options tab of the Agent Expert.
13.5. Cannot connect to StableNet® Server remotely

Solution
If there is a Linux server on which a StableNet® Server is running, the only IP address in the host
file is 127.0.0.1. Connecting with a GUI remotely will cause a problem. The StableNet® Server
host needs the IP address associated with the host name. Adapting the host file and entering the
according IP address will fix this problem.
13.6. StableNet® License is invalid or expired

Solution
Open a ticket at https://tickets.infosim.net/otrs/customer.pl. Attach the license and a screenshot
that describes the problem.

Appendix A. License Agreement
License Statement
AGREEMENT
relating to license and use of software
between
Infosim® GmbH & Co. KG
Landsteinerstraße 4
97074 Würzburg
Germany
Infosim® GmbH & Co. KG END USER SOFTWARE LICENSE AGREEMENT (EULA)
effective as of January 2006
The software (the "Licensed Software") enclosed with this End User Software License Agreement ("EULA")
or delivered via authorized download and related documents, training materials, and user guides
(collectively, the "Documentation") are licensed solely to the entity named as licensee in Infosim®'s
business records (the "Licensee") subject to the terms of this EULA, unless such terms are expressly and
unambiguously amended by a separate written license agreement between Licensee and Infosim® GmbH
& Co. KG or one of Infosim® GmbH & Co. KG's subsidiaries or affiliates (individually and collectively,
"Infosim®" as used herein).
Wherever possible, Infosim® will deliver Licensed Software by providing Licensee with the necessary access
rights (URL/IP address and password) to enable download of the Licensed Software directly to Licensee's
host computer. Licensed Software available via download (FTP or otherwise) will be deemed delivered as
of the time when Infosim® makes the download available to Licensee. If Licensee does not agree with these
terms, Licensee must take the following steps within five (5) business days after receipt of Licensed
Software: (1) for Licensed Software delivered on physical media, Licensee must return the unopened
package containing the media together with the Documentation to Infosim®; or (2) for Licensed Software
delivered via download, Licensee must erase the Licensed Software completely from any Licensee server
and/or systems, destroy or return any Documentation in printed or electronic form, and certify to Infosim®
in writing signed by an officer of Licensee that such actions have been taken. Infosim®'s address for returns
or notices worldwide is
Infosim® GmbH & Co. KG
Landsteinerstraße 4
97074 Würzburg
Germany
THIS IS A LICENSE AND NOT A SALE
A.1. License Grant

1. License Grant
1.1. Subject to the terms and conditions of this EULA, Infosim® grants, solely for use by Licensee,
a non-exclusive, non-transferable license to:
1.1.1. use Licensed Software solely for Licensee's own internal business purposes on the hardware
and the operating system software and at the site specified by Licensee (the "Site") at
the time of the order and solely in accordance with the accompanying Documentation;
License Agreement - Infosim® Confidential - 107

1.1.2. use Licensed Software licensed for failover or other fully operational backup purposes
solely for Failover or "hot" backup/on-demand disaster recovery purposes ("Failover"
as used herein is defined as when the primary or production copy of the Licensed Software
is unavailable for processing of events; when the primary copy of the Licensed Software
is restored, event processing must be returned to the primary copy as soon as operationally
possible);
1.1.3. use Licensed Software licensed for non-production purposes (e.g. lab and test/dev) strictly
for such non-production purposes; and
1.1.4. make one (1) copy of the Licensed Software exclusively for routine backup or archive
purposes; no other copies may be made. All copyright and other proprietary notices
appearing on the Licensed Software and its media, if any, shall be maintained and
reproduced on all copies of the Licensed Software.
1.2. All proprietary rights and trade secrets in the Licensed Software and the Documentation, and
all copies (in whole or part) shall be the exclusive property of Infosim®, and are protected by
German States laws and international treaty provisions. Licensee shall have no right, title, or
interest therein except for the rights expressly granted under this EULA.
1.3. Licensee shall not use the Licensed Software on any operating system software or hardware
other than as stated in the applicable order documents (e.g. sales quotation or invoice).
1.4. This EULA and the license contained herein may not be assigned, sublicensed or otherwise
transferred or used for the benefit of third parties without the prior written consent of Infosim®.
1.5. Licensee may not use, copy, alter, merge, adapt, modify, rent or lease the Licensed Software
or the Documentation, or any copy thereof, in whole or in part, except as expressly provided
in this EULA or under applicable statutes. Except to the extent applicable statutory law
specifically prohibits such restrictions, Licensee shall not reverse engineer or decompile the
Licensed Software for any reason.
1.6. Licensee shall not copy all or part of the Documentation provided by Infosim®. Additional
copies may be obtained from Infosim® for additional fees.
1.7. Upon payment by Licensee of applicable maintenance fees, Infosim® will provide maintenance
and support services in accordance with its then-current service level schedule, available
upon request.
1.8. Third Party Software. The Licensed Software may contain or be shipped with third party
applications ("Third Party Software") that are available under public license(s). Third Party
Software is included within each component of the Licensed Software together with the license
terms or required notices in files license_*.txt and, where applicable, source code or
instructions for obtaining source code, for such Third Party Software.
A.2. License Fees

2. License Fees
2.1. Licensee shall pay the non-refundable license fees and maintenance fees for the Licensed
Software set out in the applicable invoice within thirty (30) days of the date of such invoice.
Upon payment by Licensee of the applicable license fees ("Payment"), Infosim® will provide
to Licensee the instructions or devices to permanently enable the Licensed Software (the
"License Key"). In addition to other available remedies, additional license fees (and related
maintenance fees) may be charged if Licensed Software licensed for Failover for other than
Failover purposes, or Licensed Software licensed for non-production purposes in production,
as applicable.

2.2. Past due amounts owed by the Licensee shall bear interest at a rate of 1.5% per month or the
maximum allowed under applicable law.
2.3. Licensee shall be responsible for all reasonable costs incurred in the collection of past due
amounts owed by Licensee and all taxes and duties, including but not limited to any local
sales taxes, value added taxes, withholding taxes or use taxes, or import or export duties,
assessed in connection with the licensing of the Licensed Software (except for any taxes based
on Infosim®'s net income).
2.4. Infosim® reserves the right to withhold performance of any obligations, whether arising under
this EULA or otherwise, and/or change its credit terms, in the event of Licensee's non-payment
when due of any amounts owed to Infosim®.
A.3. Confidentiality
3. Confidentiality
3.1. The Licensed Software and the Documentation contain certain information that is confidential
and of substantial value to Infosim®. Except as expressly permitted herein, Licensee shall not
use or disclose said confidential information, or cause it to be disclosed, to any third party.
3.2. No benchmark results nor results of any functional testing or evaluation of the Licensed
Software shall be disclosed to any third party or used for any purpose other than to facilitate
Licensee's internal use of the Licensed Software.
3.3. Subject to Licensee's consent, which shall not be unreasonably withheld or delayed, Infosim®
may issue a press release regarding the subject matter of this EULA.
A.4. Limited Warranty and Disclaimer

4. Limited Warranty and Disclaimer
4.1. Infosim® warrants that the Licensed Software, when used in accordance with the
Documentation, and with the terms of this EULA, will operate substantially as set forth in the
accompanying Documentation for a period of ninety (90) days following delivery of the Licensed
Software to Licensee. If the Site is located in the Germany or elsewhere in Europe, the
applicable warranty period shall be the longer of (a) 90 (ninety days) or (b) the minimum
period required by applicable law following delivery of the Licensed Software to Licensee.
4.2. Infosim® warrants that Licensed Software delivered on physical media (e.g. CD-ROM) will be
free of defects in material and workmanship for a period of ninety (90) days following delivery
of the Licensed Software to Licensee.
4.3. Infosim® warrants that prior to delivery of Licensed Software to Licensee, Infosim® has used
commercially reasonable efforts to prevent the Licensed Software from being infected with,
and any modified or enhanced versions of the Licensed Software prepared by, or at the direction
of, Infosim® from being infected with, any "worms", "viruses", "Trojan Horses", "protect
codes", "data destruct keys" or other programs or programming devices that might be used
to access, modify, delete or damage the Licensed Software, or other software, computer
hardware or data of Licensee, other than as necessary to implement the License Key.
4.4. Licensee's sole and exclusive remedy for breach of any of the above warranties shall be, at
Infosim®'s option, the repair or replacement of the Licensed Software or the media.
4.5. EXCEPT AS EXPRESSLY SET FORTH IN THIS SECTION 4 AND NOTWITHSTANDING ANY OTHER TERMS
IN THIS EULA, INFOSIM® MAKES NO EXPRESS OR IMPLIED WARRANTY WITH RESPECT TO THE
LICENSED SOFTWARE, DOCUMENTATION OR MAINTENANCE AND SUPPORT SERVICES TO BE
SUPPLIED BY INFOSIM®, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTY OF QUALITY,
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, SUITABILITY, PERFORMANCE, OR

NON-INFRINGEMENT OF THIRD PARTY RIGHTS. INFOSIM® DOES NOT WARRANT THAT ANY LICENSED
SOFTWARE WILL BE ERROR-FREE OR THAT ANY DEFECTS THAT MAY EXIST IN ANY LICENSED
SOFTWARE CAN OR WILL BE CORRECTED.
A.5. Limitation on Liability

5. Limitation on Liability
Circumstances may arise where, because of a default on Infosim®'s part or other liability, Licensee
is entitled to recover damages from Infosim®. In each such instance, regardless of the basis on
which Licensee may be entitled to claim damages from Infosim® (including fundamental breach,
negligence, misrepresentation, or other contract or tort claim), Infosim® is liable for no more
than 1) damages for bodily injury (including death) and damage to real property and tangible
personal property and 2) the amount of any other actual direct damages up to the charges for the
Licensed Software that is the subject of the claim. This limitation of liability also applies to
Infosim®'s Licensed Software subsidiaries, affiliates, developers, and suppliers. It is the maximum
for which the subsidiaries, affiliates, developers, suppliers, and Infosim® are collectively
responsible.
UNDER NO CIRCUMSTANCES IS INFOSIM®, INFOSIM®'S SUBSIDIARIES, AFFILIATES, LICENSED
SOFTWARE DEVELOPERS OR SUPPLIERS LIABLE FOR ANY OF THE FOLLOWING, EVEN IF INFORMED OF
THEIR POSSIBILITY:
(i) LOSS OF, OR DAMAGE TO, DATA; (ii) SPECIAL, INCIDENTIAL, OR INDIRECT DAMAGES, OR FOR ANY
ECONOMIC CONSEQUENTIAL DAMAGES; OR (iii) LOST PROFITS, BUSINESS, REVENUE, GOODWILL, OR
ANTICIPATED SAVINGS. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF
INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATION MAY NOT APPLY TO LICENSEE.
A.6. Indemnity
6. Indemnity
6.1. Infosim® shall indemnify Licensee for any claim, demand or cause of action by a third party
("Demand") to the extent that it is based on a claim that the Licensed Software (excluding
any Third Party Software contained therein) infringes any trademark or patent issued in the
United States, Germany, or European Union, or any valid copyright recognized by a country
that is a member of the Berne Convention, or that the Licensed Software misappropriates any
trade secret of any third party within the country in which the Site is located. The foregoing
indemnification is conditioned on Licensee notifying Infosim® promptly in writing of such
Demand, Licensee giving Infosim® sole control of the defense thereof (and any negotiations
for settlement or compromise thereof), and Licensee cooperating in the defense thereof at
Infosim®'s request and expense, provided that Licensee may, at its own expense, participate
in such defense if it so chooses. In the event that Infosim® becomes aware of an actual or
potential Demand, Infosim® may, in its reasonable judgment, and at its sole option and
expense: (a) procure for Licensee the right to continue using the Licensed Software; or (b)
substitute a non-infringing version of the Licensed Software so that the Licensed Software
becomes non-infringing and still conforms to the applicable specifications; or (c) return the
license fee paid by Licensee hereunder for the Licensed Software, less an amount equal to
straight line depreciation of the Licensed Software over four years, and Licensee shall
immediately return the Licensed Software to Infosim®. Licensee shall not incur any costs or
expenses on behalf of Infosim® under or pursuant to this section without Infosim®'s prior
written consent.
6.2. For avoidance of doubt, the indemnity offered by Infosim® to Licensee in Section 6.1 above
with respect to the Licensed Software shall not apply to any Third Party Software contained
therein. Furthermore, Infosim® shall have no liability to Licensee for any Demand by a third

party alleging infringement or misappropriation for the remainder of the Licensed Software
based on (a) any use of the Licensed Software in a manner other than as permitted in this
EULA; (b) any use of the Licensed Software in combination with any product not provided by
Infosim®, to the extent that such Demand is directed against the combination; (c) use of a
release or version of the Licensed Software no longer supported by Infosim®; (d) use of a
release or version of the Licensed Software without having implemented all updates, the use
of which would have cured the alleged infringement; and (e) Licensed Software or maintenance
and support services for which Infosim® has not been paid.
THE FOREGOING STATES THE ENTIRE LIABILITY OF INFOSIM® WITH RESPECT TO INDEMNIFICATION
AND LICENSEE'S SOLE AND EXCLUSIVE REMEDY FOR SUCH DEMANDS.
A.7. Term and Termination

7. Term and Termination
7.1. The term of this EULA and the license granted herein shall be perpetual, subject to Infosim®'s
receipt of the applicable license fees and Infosim®'s right to terminate the EULA in accordance
with this section.
7.2. Infosim® may terminate this EULA immediately upon written notice to Licensee if Licensee
breaches the provisions of Section 1 (License Grant) or Section 3.1 (Confidentiality). Either
party may at its option terminate this EULA immediately upon written notice in the event that
the other party: (a) breaches any material term of this License, which breach remains uncured
for a period of thirty (30) days after written notice of such breach to the other party; or (b)
becomes insolvent or asserts that it is insolvent, fails to pay its general obligations as they
become due, institutes or has instituted against it any proceeding, arrangement, receivership
or assignment for the benefit of creditors, or files or has filed against it any petition under
applicable bankruptcy laws.
7.3. ON TERMINATION OF THIS EULA FOR ANY REASON LICENSEE SHALL CEASE USING THE LICENSED
SOFTWARE AND SHALL IMMEDIATELY RETURN THE DOCUMENTATION AND ALL COPIES OF THE
LICENSED SOFTWARE TO INFOSIM®.
7.4. The operation of Sections 2, 3, 4.5, 5, 6, 7, and 8 shall survive the termination of this License.
A.8. General
8. General
8.1. Export Requirements. The Licensed Software is subject to laws and regulations of the United
States and European Union that restrict its export. Licensee agrees that it shall not export or
"re-export" (or otherwise transfer) the Licensed Software unless Licensee has complied with
all applicable United States, European Union, and foreign government export controls and
approvals.
8.2. U.S. Government Rights, Government Users. Infosim® licenses software for ultimate end use
by United States federal government agencies and other U.S. federal government customers
("Federal Government Customers") only under the following conditions. Rights granted herein
include only those rights customarily provided to end use customers of Licensed Software and
related Documentation as defined in this License. This customary commercial license to the
Licensed Software is provided in accordance with FAR 12.211 (Technical Data) and 12.212
(Computer Software) and, for Department of defense purchases, DFAR 252.227–7015 (Technical
Data – Commercial Items) and DFAR 227.7202–3 (Rights in Commercial Computer Software
or Computer Software Documentation). If a federal government or other public sector customer
has a need for rights not conveyed under this License, it must negotiate with Infosim® to
determine if there are acceptable terms for transferring such rights, and a mutually acceptable

written agreement specifically conveying such rights must be executed by both parties. To
the extent that Licensee sublicenses Licensed Software pursuant to the terms and conditions
of the Agreement to any sublicense that is a federal government agency or other Federal
Government Customer, Infosim® will accept only the following subcontract or flow down
provisions: FAR 52.222–26, "Equal Opportunity"; FAR 52.222– 35, "Affirmative Action for
Disabled Veterans and Veterans of the Vietnam Era"; and FAR 52.222–36, "Affirmative Action
for Workers with Disabilities." Any additional subcontract or flow down provisions, including
any provisions imposed by federal, state, local or other governmental or quasi-governmental
entities, must be negotiated directly with Infosim® and reflected in a mutually acceptable
written agreement executed by Infosim® and all other involved parties.
8.3. Audits. Infosim® and its licensee shall have the right to conduct an audit of (and to copy)
Licensee's records on reasonable notice and not more than once in each twelve month period
to verify that Licensee is complying with the terms hereof. In the event that an underpayment
is revealed as the result of such audit, Licensee shall immediately upon being so requested
by Infosim® pay such underpayment together with the costs of any such audit.
8.4. Severability. If one or more provisions of this EULA are held to be illegal or unenforceable
under applicable law, such illegal or unenforceable provision(s) shall be limited or excluded
from this EULA to the minimum extent required so that this EULA shall otherwise remain in
full force and effect and enforceable in accordance with its terms.
8.5. Data Protection Act Consent. Licensee represents and warrants that all personally identifiable
information provided to Infosim® is done so with the informed consent of the individuals so
affected. Consent is hereby given: (i) for transfer of personal information to a third party; (ii)
for transfer of personal information to facilities outside the European Union, Canada, and
other jurisdictions where there may not be adequate data protection regulations; and (iii) to
use personal information for sales and marketing purposes.
8.6. Entire Agreement. Licensee agrees that this EULA is the complete and exclusive statement of
the mutual understanding between the parties and supersedes all previous written and oral
agreements and communications relating to the subject matter of this EULA including, but
not limited to, terms contained on any purchase order. The terms herein may not be modified
or waived except in writing signed by authorized representatives of both parties.
8.7. Notices. All notices under this EULA shall be in writing, and shall be deemed given when
personally delivered, or after being sent by prepaid recorded or registered post or reliable
courier services such as DHL or Federal Express, to and received by the address of the party
set forth on the applicable invoice or such other address as such party last provided to the
other by written notice.
8.8. Assignment. Licensee shall not assign, transfer, or sublicense any obligations or benefit under
this EULA without the prior written consent of Infosim® (and any such attempt shall be void).
Infosim® may assign this EULA in whole or in part.
8.9. Nuclear and Other Applications. The Licensed Software is not specifically developed or licensed
for use in any nuclear, aviation, mass transit or medical application or in any other inherently
dangerous applications. Neither Infosim® nor its suppliers shall be liable for any claims or
damages arising from such use and Licensee agrees to indemnify and hold harmless Infosim®
and its suppliers from any claims for losses, costs, damages, or liability arising out of or in
connection with the use of the Licensed Software in such applications.
8.10. You agree that you will not use Infosim® products for the development, design, manufacture,
or production of missiles, or nuclear, chemical or biological weapons.
8.11. Force Majeure. Neither party will be responsible for any failure to fulfill its obligations
hereunder (except for the obligation to pay money) due to causes beyond its reasonable
control, including without limitation acts or omissions of government or military authority,

acts of God, shortages of materials, transportation delays, fires, floods, labor disturbances,
riots or wars.
8.12. English Language. This EULA is in the English Language, which language shall be controlling
in all respects.
8.13. Choice of Law. This EULA is governed by and construed under laws of one country depending
on where the Site or Sites is/are located. Specifically,
8.13.1. the enforcement and interpretation of this EULA as well as the use of Licensed Software
by Licensees at Sites in Africa, Europe, and the Middle East shall be governed by the laws
of Germany;
8.13.2. the enforcement and interpretation of this EULA as well as the use of Licensed Software
by Licensees at a Site or Sites located anywhere not listed in subsection (i) above (including
but not limited to Sites located anywhere in the Americas or any Asian or Pacific Rim)
shall be governed by the laws of Germany.
LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THE TERMS OF THIS EULA AND AGREES TO BE BOUND
BY ITS TERMS.

StableNet Administrator Manual

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

StableNet Administrator Manual

Transféré par

Droits d'auteur :

Formats disponibles

StableNet® Version 8.3.

StableNet® Version 8.3.2

StableNet® Version 8.3.2

StableNet® Version 8.3.2

StableNet® Version 8.3.2

StableNet® Version 8.3.2

StableNet® Version 8.3.2

StableNet® Version 8.3.2

1.1. About StableNet®...........................................................................................................2

Introduction to StableNet® - Infosim® Confidential - 1

StableNet® GUI / StableNet® StableNet® Network

Figure 1.1: Interaction of the three StableNet® components

Introduction to StableNet® - Infosim® Confidential - 2

1.2. Technical Details

StableNet® Web GUI StableNet® GUI

5443 HTTPS 5443 HTTPS

Figure 1.3: StableNet® communication ports

1.3. About Measurements and Monitors

Introduction to StableNet® - Infosim® Confidential - 3

1.4. StableNet® Enterprise and StableNet® Telco

Introduction to StableNet® - Infosim® Confidential - 4

System Requirements - Infosim® Confidential - 5

2.1. General Requirements

2.2. Operating System Requirements

System Requirements - Infosim® Confidential - 6

2.3. Hardware Requirements

Server Agent (50.000 GUI

Server Agent GUI

System Requirements - Infosim® Confidential - 7

2.4. Database Requirements

2.4.1. Database Sizing

Measurement type Approximate storage requirement

Per day Per month Per year

System Requirements - Infosim® Confidential - 8

2.4.2. Physical Drive Requirements

System Requirements - Infosim® Confidential - 9

Installation - Infosim® Confidential - 10

3.1. Database Installation

3.1.1. MariaDB Database Installation

# Statements that take a long time, e.g. during maintenance,

# Instead of skip-networking the default is now to listen only on

# Increase the maximum for MySQL packets to support handling

# Increase buffer pool size for more performance.

# You can set innodb_buffer_pool_size up to 50 - 80 %

Installation - Infosim® Confidential - 11

# The option 0 sets the commit interval to commit only every

# The file handles for the MySQL database need to be increased

# The number of connections to the database must be high enough

# Configure UTF-8 mode

# Configure UTF-8 mode for client connections

CREATE DATABASE pme;

3.1.2. Oracle Database Installation

3.1.2.1. Database Specification

Installation - Infosim® Confidential - 12

3.1.2.2. Step-by-Step Oracle Database Installation

Perform as root user:

127.0.0.1 localhost.localdomain localhost

Installation - Infosim® Confidential - 13

yum install oracle-database-server-12cR2-preinstall -y

3. Change password of the oracle user:

4. Edit /etc/security/limits.d/20-nproc.conf and change it as described below:

6. Restart the server.

Perform as oracle user with graphical login session:

systemctl stop firewalld