Follow Mike's blog
Archives for the month of: November, 2016

I was experimenting and testing with my second-hand Cisco ASA 5505.  I learned some things that might be useful.

I think starting with version 8.0 of Cisco’s ASA software, it shows your SNMP community string in your config as just ***** for security reasons. If you want to see the actual string, then get into ‘enable’ mode and type the command shown below:

MikeASA1# more system:running-config | inc snmp
snmp-server host inside community mysnmp805
snmp-server location Atlanta office
snmp-server contact
snmp-server community mysnmp805
snmp-server enable traps snmp authentication linkup linkdown coldstart

In this case, my community string is set to “mysnmp805”. Notice it’s on two lines. specifies the IP address that’s allowed to communicate. It’s also the IP address where the device sends the SNMP traps. MikeASA1# is just the prompt that shows the name of my device. I hope this helps.


This is useful if you want to be notified when you go over some desired quantity. For example, if your subscription commitment is 100 devices, you might send yourself a “warning” alert at 95 devices and “critical” alert at 99 devices.
It might also be useful if you have a “child accounts” which are additional LogicMonitor accounts that are entirely separate but get billed to the same person/company.


It’s a Datasource using a Groovy script which uses the REST API to get a list of all devices in your account. Fortunately, a total quantity of devices is also included in the API response. Maybe someday I will enhance it to give an alert when a device is added or deleted. To minimize load and because it usually doesn’t change rapidly, I set the collection interval to the max of 60 minutes.

Qty devices and threshold

Qty devices and threshold


  1. If you haven’t already, create a separate LogicMonitor user account (called for example “api.user”) and generate the API Token so you can use the API commands. Normally, I recommend you create a separate role with ‘manage’ permissions to “devices” (ie not dashboards, services, settings, reports, etc) but this particular datasource only needs ‘read only’ permissions.
  2. Set the following properties. For simplicity, I recommend you set them on the ‘root/base’ folder so it’s seen by any devices you apply this datasource to. = <the cryptic looking ID that you generated in step1>
    rest.api.key = <the cryptic looking key that you generated in step1>
    account = <the part of your URL before; usually your company name>
  3. Download the datasource file and add it to your company account via Settings > Datasource > Add > From file.
  4. Apply this datasource to any one of your servers. For simplicity, I suggest you apply it to one of your collectors.
  5. If desired, set an alert threshold and you might want a special Alert Rule and Escalation Chain to notify a person or group of people if it goes over a threshold.
  6. Test by waiting 1-3 minutes for the first poll/run then look at ‘Raw Data’ tab to make sure you see what you expect.


OpenVMS has a long history and was very popular because of it’s reliability and industry specific applications. It supports SNMP but the datapoints are not very helpful. Luckily, a company named ComTek makes an SNMP agent with lots of good datapoints. (click here for more details). Below are screenshots that show some examples of the datapoints and graphs.

vms-misc vms-disks vms-errors



  1. Buy (or get a trial) of ComTek and install it on your OpenVMS system.
  2. Download these DataSsource files (disk, misc, errors) and add them to your LogicMonitor account using Settings > Datasources > Add > From file.
  3. You can add more OIDs to these datasources or create additional datasources. Look at the MIB file to figure out which OIDs.


I bought UniFi for my home for these reasons:

  • Relatively low cost
  • Designed for enterprise with centralized controller
  • Has an API
  • We use it in our office
  • To learn more

I made this datasource using Groovy so it will work on Linux or Windows collectors. It shows lots of info including:

List of Access Points with info on:

  • Qty of clients
  • Bytes used on uplink port Tx and Rx
  • Bytes used by 2GHz client devices and 5GHz client devices
  • CPU, memory, and uptime


List of Client devices connected with info on:

  • Bytes transmitted and received and rate transmit and receive
  • Signal strength in dBm
  • Uptime
Graphs for each client

Graphs for each client


Download the DataSource for APs and download the datasource for Clients.

Import them into your LogicMonitor account using Settings > Datasources > Add > From file

If you haven’t already, add your UniFi controller or CloudKey to LogicMonitor and set properties for Unifi.user and Unifi.pass

If you have multiple sites, clone the datasource to make a copy and edit the site name at the top of both scripts in the datasource. I also made a datasource (download) to show the site name because the UniFi web interface has you changing the ‘description’ but the site name is assigned by the system and doesn’t show in the GUI. At least for me, the first site is named ‘default’ even if you change the site name in the GUI.

Test by looking at ‘Raw Data’ tab and graphs.


Thanks to Erik Slooff on the Ubiquiti community forum because he made it easier to find the API calls since Ubiquiti has not officially documented them.

Thanks to my co-worker Jerry Wiltse for helping me on the Groovy script. I did my initial one with cURL then PowerShell.

As usual, these datasources are not officially supported by LogicMonitor tech support (until/unless they get reviewed and published in the core repository)