Knowledge Base
Knowlegebase articles
Welcome to SysOrb knowledge base. Her you will find detailed explanation on questions regarding SysOrb. The list is under continues development and new articles will be added. You can follow the links below or enter a "key word" to search all of the articles.
- Agent crashes
- Automatic rescan of all nodes in a domain
- Bandwidth consumption estimate
- Basic database tuning
- Can I customize the reports in SysOrb?
- Disabling specific checks
- Does SysOrb support SNMP traps?
- Explanation of the score keeper strategy.
- How does HTTP Netcheck work in SysOrb?
- How to automatically update alert group on all nodes to “As domain”
- How to backup SysOrb database
- How to change time interval value of agent_checkin_delay
- How to move the SysOrb server to a new server
- How to quickly set downtime on an agent
- I cannot get all of the "performance counters/cache" entries to appear in SysOrb what should I do?
- Migrating MIB information from one SysOrb installation to another
- Migrating the configuration of a Windows SysOrb server from 32 to 64 bits
- No empty blocks in meta database.
- Script to get a list of nodes which have no AlertGroup
- SysOrb agent is not checking in to the Sysorb server
- SysOrb agent stops checking in from a windows server with very long system uptime
- SysOrb server shuts down unexpectedly
- System uptime no longer updates on windows
- Unable to monitor hardware (fans, disks, temperatures etc.) on Windows
- Upgrading SysOrb on Windows
- Uploading a SysOrb database to Evalesco
- What does KiB and MiB mean?
- What is IPMI ?
- Windows agent late for check-in every hour
Unable to monitor hardware (fans, disks, temperatures etc.) on Windows
After having installed the SysOrb Agent on a Windows Server running natively on a hardware system (not as a guest in a virtualized environment), there is no "IPMI Sensors" group in the agent checks section under agent checks in the web interface.
Hardware monitoring is facilitated by a subsystem called IPMI. The SysOrb Agent supports the IPMI protocol but requires operating system support in order to actually access the BMC (Baseboard Management Controller) that provides the sensor data.
Windows versions prior to Windows 2003 R2 do not include an IPMI driver at all. One can be downloaded from Intel, and the Intel IPMI driver is fully supported by the SysOrb Agent.
Windows versions from WIndows 2003 R2 and on, include an IPMI driver but the driver is not installed by default. The following technet article describes how to enable this:
http://technet.microsoft.com/en-us/library/cc781099%28WS.10%29.aspx
Windows versions from Windows 2008 installes the IPMI driver by default and should therefore not need any additional actions.
The hardware information is provided by a Baseboard Management Controller - if the server hardware on which you are running the SysOrb Agent does not have a BMC, the information will simply not be available. Furthermore, different vendors support very different sets of sensors with naming conventions of variying quality. The SysOrb Agent will provide all sensors (of the sensor types it supports) to the web interface, using the names chosen by the hardware vendor.
If running Windows versions prior to Windows 2003 R2, consider installing the Intel IPMI driver which can be downloaded from the Intel web site.
If running Windows versions prior to Windows 2008 but later than or equal to Windows 2003 R2, you can install the IPMI driver supplied with the operating system by following the technet arcitle: http://technet.microsoft.com/en-us/library/cc781099%28WS.10%29.aspx
If running Windows 2008 or later, you should have the IPMI driver installed already.
