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
Does SysOrb support SNMP traps?
No, SysOrb works with the "SNMP GET" system. The SNMP protocol describes several ways of communication between the SNMP agent and a SNMP surveillance station (SysOrb Server). One method is the SNMP "GET" where the SNMP surveillance station asks the agent for a specific number, and the agent replies with a value. The question could be "how many bites of information has been sent out of port 1", since the router was rebooted?
Another way is the "SNMP traps", where the agent will respond spontaneous to the surveillance station when a certain issue has happened, for example the router loses a connection on port 1.
SysOrb works with the "SNMP GET" system.The reason for this is, that in most cases one can get the same information with "get", (eg. Ask the router for the link status on port 1,) plus one is sure to discover if data are lost on the net. If SysOrb with SNMP "get" ask about reading, for example. link status, and do not get a reply within 5 seconds, then SysOrb will ask again, and if it still has not received a reply after a number of attempts, then SysOrb know that there is a problem. With traps SysOrb would not know when the SNMP agent had sent a message, and it would not be able to detect the message, if it was lost on the network.
Therefore you can say that using "Get" the reliability is higher and it is a more secure way to monitor nodes.