Burk AutoPilot SNMP management with Telos devices

  • Published on Dec 31, 2024
  • 2 minute(s) read
  • Migration Team

Scope

This article is meant for reference purposes. The goal of this helpdoc is to show possible integration between Burk AutoPilot software SNMP management used with various Telos devices. AutoPilot requires no license, or require any physical Burk hardware for AutoPilot software to be used. Thus making it an excellent application to work with and test SNMP support in various ways

Quick start with Z/IPStream R/2 example

Configure Z/IPStream R/2 to allow SNMP

  1. In web UI go to Options, then Network, then SNMP

  2. Make sure SNMP service enabled checkbox is checked, and make sure the community field is set and click save

  3. Download SNMP MIB file from this page and save to your PC

Configure AutoPilot to communicate via SNMP with Z/IPStream R/2

  1. Install AutoPilot software from the Burk website

  2. Launch AutoPilot software

  3. Under Resources snap-in, right click on Network Devices folder and select New Network Device

  4. Click Next on the dialog box that appears

  5. Set a friendly name and enter IP address of the Z/IPStream R/2 and click Next

  6. Enable SNMP management, and enter in the Community name that was set prior and click Next

  7. Add in the MIB file that was saved from the R2 in a previous step and click Next

  8. Click Browse to bring up the OID browser

  9. Explode open the correct directories to be able to drill down into the OID definitions that the import R2 MIB file provide

    iso/org/dod/internet/private/enterprises/tlsCorp/zipStreamR2

  10. Add in a couple OID's of interest, this can all be done via the MIB Browser window, click OK when done
    Here we have selected sensor-system-temp. The upper right corner tells us about the OID, and what data structure it uses.
    We can click the Get button to send the request to the R2 for the value. This confirms that the OID is correct for this device and that we are communicating correctly with the device.  
    We can click the Add button to add to our list and continue browsing othe OID's we might also want to read or write

  11. Review the added OID's and click Next

  12. Configure Channel Assignments of each OID and Click Next
    In AutoPilot, readings typically come in via a Meter(Analog) or Status (GPI) channel. These require expected values. A meter needs to be numerical only and a Status needs to be matchable to a string value to determine ON or OFF of said status. If neither seem approproiate for the OID, channel type TEXT can be selected instead. For now leave these as text type.  The Polling Rate may be changed, this is how often the SNMP request will be sent for an update. Set to a value most reasonable for the OID. We will leave them as default of 60 seconds for now

  13. Configure optional logging and click Next, then click Finish
    This can be especially useful if we want to look back at historical values. For now we will leave logging turned off

  14. Inspect the newly added Network device under Resource snap-in, click Network Devices and find the device we just added and click on it once

All of the OID's that were selected now show in the table

Take it to next step with Custom Views

Custom Views is similiar to legacy Pathfinder panel designer, just with more options. When SNMP values can be intrepeted as Meter or Status type, it allows you to use many different metering/ display objects

A simple graph that displays total Audio Sources in use VS how many are silent

Related articles