iReasoning SysUpTime Network/Server Monitor FAQ

Q. Where can I get the license file?
A. The license files are available at download page.

Q. Does SysUpTime network monitor support more than 1000 devices?
A. Yes. SysUpTime is designed from the ground up to manage large-scale networks. The advanced clustering feature of SysUpTime network monitor can distribute loads among multiple servers, which makes the architecture extremely scalable.

Q. Does SysUpTime network monitor support custom MIBs?
A. Yes. It supports both standard and custom MIBs. A MIB browser is included for easily managing MIBs.

Q. Can I monitor interfaces with SysUpTime network monitor? Can I monitor system health (e.g., CPU/Memory)?
A. Yes. It supports SNMPv1/v2c/v3 monitoring of ifTable of MIB-II.

You can use SNMP, SSH/Telnet, WMI monitors to monitor system health metrics such as CPU, memory utilization.

The easiest way is to use SNMP and WMI wizards to create core performance metrics.

Q. Can the monitors be customized? If so, how?
A. Yes. Choose menu "Tools/Performance/Add monitors" and then pick a monitor type. Then you will be prompted to enter necessary parameters.

Q. Does SysUpTime network monitor provide event filtering?
A. Yes. You can use menu "Tools/Configuration/Alarm" and choose "Event" tab. SysUpTime network monitor also supports alarm de-duplication and escalation.

Q. Does your tool facilitate doing trend analysis of data?
A. Yes. We offer Top-N reports and monitor reports, which can be used for this purpose.

Q. Can SysUpTime network monitor send a notification to a cellphone or pager?
A. Not directly. Notification methods include email, sound, executing command, posting to a web page. You can use an email to SMS gateway or web to SMS gateway to relay the notifications.

Q. Does SysUpTime network monitor support WMI monitoring?
A. Yes, if SysUpTime network monitor server is running on a Windows machine.

You can add "WMI monitor" through client GUI ("Tools/Performance/Add Monitors" menu).

You can create your own WMI scripts to achieve other monitoring tasks.

Q. Does SysUpTime network monitor support other database servers for storing data?
A. Yes. You can use other relational database servers (Oracle, MS SQL Server, PostgreSql) as well.

Q. How to monitor Windows Event?
A. There are two ways:

  • Setup Windows Event log monitor.
  • Configure SNMP service to send SNMP traps to your SysUpTime network monitor server.
    • Locate event you want to monitor in Event viewer. Remember log(system, app or security), source (eg.SNMP) and EventID (eg.1001)
    • Start winnt\system32\evntwin.exe. Use custom configuration type -> edit -> locate desired action using log, source and eventid remembered from control panel -> add
    After you configured as many event as you want to monitor you have to configure event in SysUpTime network monitor to configure alert and/or automatic response.

Q. How can I start a monitor at a specific time?
A. When you create a new monitor, clicking the "Advanced" button and then setting the starting time to 7:30. And if you set the polling period to 24 hours, then the monitor will run at 7:30 every day.

Q. How can I monitor Windows Services?
A. You can create a Windows Service WMI monitor for this purpose. Open "Tools/Performance/Add Monitors", and select "WMI/Frequently used WMI command/Windows Service", then press "New..." button. Enter the service name you want to monitor in the threshold configuration screen. If the service is not running, an alarm will be raised.

Q. How can I monitor Linux/UNIX Services?
A. If your Linux box supports SNMP agent, then you can create SNMP monitors to query certain OIDs. If no SNMP agent, you can create Telnet/SSH monitors to check the status of LINUX services.

Q. Why network discovery didn't discover all the nodes in my network?
A. The reasons are:

  • If the timeout value is not long enough, some unresponsive nodes are ignored. The default timeout value is one second. You may need to increase it if there are unresponsive nodes. However, longer timeout value will make discovery slower.
  • Some subnets cannot be discovered based on the data from routing tables. You need to set the discovery filters to explicitly let it discover those subnets

Q. Network discovery can't correctly identify devices. Why?
A. Over three thousand devices are supported by SysUpTime network monitor and new devices can be added easily. If a device is discovered as an unknown device. Please check if it supports SNMP. Only SNMP enabled devices can be automatically identified. If it supports SNMP and it is still unknown, you can use "Tools/Discover/Device Manager" to add this device to the database. After that, next network discovery should be able to identify it.

Q. What Linux distributions does SysUpTime network monitor support?
A. SysUpTime network monitor can run on Redhat, Debian and Suse linux distributions on X86 platforms.

Q. Does SysUpTime Linux edition have the same functionality as the Windows edition?
A. Almost, except that SysUpTime Linux server cannot be used to do WMI moniotoring, which is used to monitor Windows performance metrics and it depends on Windows OS.

Q. When I use SNMP monitors to monitor jvmMemoryHeapUsed of JVM-MANAGEMENT-MIB, the value doesn't look right. Is it a bug?
A. JVM-MANAGEMENT-MIB defines the MIB that provides access to the Java Virtual Machine monitoring data.

jvmMemoryHeapUsed is defined as the following:

jvmMemoryHeapUsed OBJECT-TYPE
    SYNTAX      JvmUnsigned64TC
    UNITS       "bytes"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
    " Total amount of used memory (in bytes) 
      from heap memory pools."
    REFERENCE "J2SE 5.0 API Specification,
              java.lang.management.MemoryMXBean,
              java.lang.management.MemoryUsage"
    ::= { jvmMemory 11 }

The JvmUnsigned64TC is a 64-bit counter. According to RFC 2578, counter data type must monotonically increase until it reaches maximum value. jvmMemoryHeapUsed is declared as a counter64 object but its values actually fluctuate, it can increase or decrease. It should have been declared as a gauge64, but this data type is not available in SMIv2. Other similar objects in this MIB include jvmMemoryHeapCommitted, jvmMemoryNonHeapUsed, jvmMemoryNonHeapCommitted, jvmMemPoolUsed, jvmMemPoolCommitted, etc.

By default, all SNMP counter data types are converted to rate, which is calculated by (V2 - V1)/(T2 - T1). For objects such as JvmUnsigned64TC, its rate can be a negative number when its raw value dereases. This is why the results do not look right.

To solve this issue, you can create an expression with only one variable whose name starts with g_, which tells SysUpTime to treat it as a gauge object.

For instance,
create an expression jvmMemoryHeapUsed:
jvmMemoryHeapUsed = g_jvmMemoryHeapUsed
The OID of g_jvmMemoryHeapUsed is .1.3.6.1.4.1.42.2.145.3.163.1.1.2.11.0.

Then create a new SNMP monitor that uses this expression instead of raw OID.

Q. I'm using SysUpTime professional edition. Why its trap receiver can't receive any SNMP traps?
A. If your SysUpTime professional edition can't receive SNMP traps, please check:

  • Is the trap receiver up and running? If not, maybe UDP port 162 is already occupied by another application so trap receiver couldn't be started.
  • Is it blocked by the firewall? Make sure to configure the firewall to allow UDP port 162, and/or the SysUpTime application.

Q. Can't create WMI monitors.
A. Please refer to this WMI troubleshooting guide.