michaelcolson.com » n-able

APC UPS Time Remaining Value for N-Able

michael — Fri, 09 Feb 2007 15:43:41 +0000

The APC service time remaining is calculated in 1000 of time ticks. the calculation is as follows.

The Time remaining threshold is currently showing a Value of 342.00 Time Ticks.

The mathematical calculation to determine how many minutes there are left will be

342 x 1000 = 342000
342000 / 100 time ticks = 3420 seconds
3420 seconds / 60 = 57 minutes

time remaining in minutes is 57 min.

The following illustrates the custom thresholds for:

Normal	10 min or more
Warning	5 min – 10 min
Failed	5 min or less

Windows Software Probe on Virtual Machines

michael — Thu, 14 Sep 2006 12:58:29 +0000

N-Able does not support the Windows Software Probe in a virutal machine. This is due to potential problems in writing/reading to the virtual disk.

Misconfigured Status for WMI Services

michael — Wed, 13 Sep 2006 17:23:56 +0000

If N-Able is reporting Misconfigured for WMI services (Active Directory, Exchange Services, etc.) with a similar error message to:

201 NAWMIConnection::QueryMethod: Invalid class name. Machine name: 172.17.232.10. Namespace: root\cimv2. WQL string: Select LDAPBindTime, LDAPSuccessfulBindsPersec, LDAPWritesPersec, LDAPUDPoperationsPersec, LDAPActiveThreads, LDAPClientSessions, DRAInboundObjectUpdatesRemaininginPacket, DRAPendingReplicationSynchronizations from Win32_PerfRawData_NTDS_NTDS. Error code = 0×80041010.

run the following commands from the monitored system: *It is safe to run these commands on a production system.

winmgmt /clearadap
winmgmt /kill
winmgmt /unregserver
winmgmt /regserver
winmgmt /resyncperf

Once the next scan interval passes the service should no longer report as Misconfigured.

Probe Reports Log Analysis (Appended) Failure

michael — Wed, 13 Sep 2006 14:13:35 +0000

For the nagent.log and the first netdisco.log files, If you click on the status details you can see that the file size is the part of the service that is failing. The failure threshold is 20KB. Since the logs are stored until they reach 5MB, and then rotated, this threshold should be changed to 6-7MB.

FYI this value is in bytes:
5MB = 5242880 bytes
6MB = 6291456 bytes
7MB = 7340032 bytes

For the second netdisco.log file, it is the time since the last log file growth that is failing. Unless you have a recurring net discovery task, you should not be monitoring this part of the service, because it will fail unless you do a manual net discovery at least every 1440 minutes.

These services should be fine once you make these adjustments.