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
Migrating MIB information from one SysOrb installation to another
It can be desirable to export the MIB information from one SysOrb server and import it on another SysOrb server. This is possible using the XML import and export utilities that ship with the SysOrb Server.
To export all MIB information from SERVER1, run the command
sysorb-exporter -s SERVER1 -d . -l USERNAME -f mib.xml -I MibModule,MibModuleObject,MibModuleType,MibTypeEnum,MibObject -c
You must replace USERNAME in the above with the user name of an administrative user on the SERVER1 SysOrb Server.
To import this MIB information to SERVER2, run the command
sysorb-importer -s SERVER2 -l USERNAME -f mib.xml -m
Again, you must replace USERNAME in the above with a user name of an administrative user on the SERVER2 SysOrb server.
The import will not erase existing MIB information, but it will overwrite whatever conflicting information may already be on SERVER2.
Once the import is complete, all MIB information from SERVER1 should now be available on SERVER2. You will need to re-scan SNMP devices on SERVER2 in order to actually benefit from the extended MIB information.