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
What is IPMI ?
The SysOrb agent supports IPMI. The Intelligent Platform Management Interface (IPMI) specification defines a set of common interfaces to computer hardware and firmware which system administrators can use to monitor system health and manage the system. Several dozen companies support IPMI.
Dell, HP, Intel Corporation and NEC Corporation announced IPMI v1.0 on 1998-09-16, v1.5 on 2001-03-01, and v2.0 on 2004-02-14.
IPMI operates independently of the operating system (OS) and allows administrators to manage a system remotely even in the absence of the OS or the system management software, or even if the monitored system is not powered on. IPMI can also function when the OS has started, and offers enhanced features when used with the system management software. IPMI gives only the structure and format of the interfaces as a standard, where the implementation may vary.
IPMI version 1.5 and later can send out alerts via a direct serial connection, a local area network (LAN) or a serial over LAN (SOL) connection to a remote client. System administrators can then use IPMI messaging to query platform status, to review hardware logs, or to issue other requests from a remote console through the same connections. The standard also defines an alerting mechanism for the system to send a simple network management protocol (SNMP) platform event trap (PET).
The IPMI consists of a main controller called the Baseboard Management Controller (BMC) and other satellite controllers. The satellite controllers within the same chassis are connected to the BMC via the system interface called IPMB (Intelligent Platform Management Bus/Bridge). IPMB is an enhanced implementation of I²C (inter-integrated chip). The BMC connects to satellite controllers or another BMC in another chassis via IPMC (Intelligent Platform Management Chassis) bus/bridge. It can be managed through the Remote Management Control Protocol (RMCP), a specialized wire protocol defined by this spec. Field Replaceable Unit (FRU) holds the inventory (such as vendor id, manufacturer etc.) of the devices that are replaceable. A Sensor Data Records (SDR) repository provides the properties of the individual sensors present on the board. For example, sensors may be for temperature, fan speed, and voltage.