FAQ - Frequently Asked Questions
Can I integrate SysOrb with my Help Desk system?
Yes, you can.
From SysOrb 2.4.4 we have included extended e-mail header information. So, you can have your help desk system sort the incoming notification e-mails from SysOrb according to specific strings in the e-mail header.
Your Help Desk system could e.g. classify according to the IP no. and/or node label of the node in question, and the SysOrb Domain in which it is placed, or by which user is being alerted etc.
Here is an example excerpt from an e-mail header, for your reference:
X-Mailer: SysOrb Monitoring Server v.2.4.4 build 2478 on NT (IA-32)
Subject: Alert - XYZ laptop (10.0.1.12) - Services for Norton AntiVirus Client
X-So-Check-Label: Services for Norton AntiVirus Client
X-So-Check-Name: scm.Norton AntiVirus Server
X-So-Explanation: Service state is bad
X-So-Node-Label: XYZ laptop (10.0.1.12)
X-So-Result-Str: The service is stopped
X-OriginalArrivalTime: 16 Dec 2003 14:29:15.0214 (UTC) FILETIME=[FB4416E0:01C3C3E0]
Date: 16 Dec 2003 15:29:15 +0100
Can I upgrade my 30-day trial license to a full license without reinstalling?
Yes. When you have purchased the appropriate SysOrb licenses, all you need to do is to insert the purchased - and permanent - license file in your present SysOrb installation, then restart the SysOrb Server, and it will work with the features and options you purchased.
If you have further questions on how to do this, please contact firstname.lastname@example.org
Can I use SysOrb in conjunction with my existing management framework?
If you install your SysOrb Server on a Windows machine, you can let the SysOrb Server report all of its events (warnings, alarms etc.) to the NT Event Log.
Then, all you need is an Event Log agent from e.g. Unicenter TNG, Tivoli or others, and the events generated by SysOrb can be integrated into your management framework console in real-time.
This may turn out to be a considerable source of rationalization of your overall license cost for network and systems management.
For LogChecks, is there an overview of how to use regular expressions for rule creation?
Apart from the examples in the web interface, and in the Administrator's and User's Guide, you can read more about regular expressions in general here: regular-expressions
How are the time-series data aggregated in the SysOrb database?
For each check parameter you configure in SysOrb, 1 MB of space is allocated in the database. To ensure that the SysOrb database does not grow in a linear fashion over time, the data stored are aggregated to make sure that each check does not store more than 1 MB of data in the database.
The aggregation levels are as follows:
- The most recent 10 minutes of data: 1-second resolution (or as per your check configuration).
- The following 1 week of data: 1-minute resolution.
- The following 1 month of data: 15-minute resolution.
- The following 2 months of data: 30-minute resolution.
- The following 1 year of data: 1-hour resolution.
- The following 3 years of data: 3-hour resolution.
Data older than 4 years, 3 months, 1 week and 10 minutes are discarded.
I would like to test SysOrb in a larger environment than the default license allows. How can I do this?
If you contact us at email@example.com stating your contact information, and how many agents and servers you need a license for, we will be happy to supply you an evaluation license which will work for a limited test period.
LogChecks - where can I find more information on creating rules?
The rules for the SysOrb LogChecks must be defined using regular expressions. In order to learn more about how to use those for creating more precise LogCheck rules, please refer to this online tutorial:regular-expressions
What are the hardware requirements of the SysOrb Agent?
CPU: Intel® 80486 compatible, UltraSPARC (SPARCv9) or PA-RISC v.1.1
Disk space: 1-2MB for the installation, 5MB recommended for logs
Refer to the System Requirements section of the Administrator's Guide for a more detailed overview of requirements. If in doubt, contact firstname.lastname@example.org.
What are the hardware requirements of the SysOrb Server?
We test our software under extreme conditions to ensure optimal stability and accuracy. The minimum requirements vary, however, depending on the OS platforms applied. In general, Intel® Pentium® type performance is sufficient for small networks, 5 to 20 SysOrb Agents, and multiple NetChecks and snmpChecks. Each check configured in SysOrb uses approx. 1MB of diskspace, so if you have 10 checks configured on 10 hosts the database will take up 100MB. SysOrb requires a minimum of 64MB RAM, although we recommend to use 128MB RAM.
For larger networks, we recommend scaling the processing power, memory and disk space accordingly.
What is the default administrator password for the SysOrb web interface?
Which OS platforms are/will be supported?
SysOrb currently supports the following Windows/Unix/Linux/Novell platforms:
- Windows 2008, Windows 2012 and Windows 2016
- RedHat Linux 5.2, 6.2, 7.x and all newer versions
- SuSE Linux 7.3 and all newer versions
- Debian GNU/Linux 2.2/3.0
- Mandrake Linux 9.0
- Novell NetWare 5.1
- FreeBSD 3.5, 4.5 and newer versions
- HP-Unix 11, 11i
- IBM AIX 4.3, 4.3+, 5.x
- Sun Solaris 2.6 (SPARC), 8/9/19 (UltraSPARC), and 8/9/10 (x86)
- Tru64 UNIX 4.0F
Why won't the SysOrb Agent check-in to the SysOrb Server?
When setting up new SysOrb Agents to check in to your SysOrb Server, you should be aware of two things:
- How many agents are allowed to check-in according to your license key?
- Did you name the Agent identically on the Agent itself and in the Web Interface?
To check how many SysOrb Agents can check-in, open your "sysorb.lic" file on your SysOrb Server in a text editor. The number of check-in hosts is the number of SysOrb Agents that can be added to your set-up. If you need to add more SysOrb Agents to your license, please contact sales.
It is important that the Agent names (server name, DNS, or IP) is exactly identical (case sensitive) on both Agent side and SysOrb Server (Web Interface) side. Also, the SysOrb Domains in which the Agent is configured must be specified correctly.
For HOWTO-guides on this issue for Windows OS, please click here:
- SysOrb Server installation
- SysOrb Agent installation