Tips and Tricks: Use Kaseya for network monitoring of ESX, Cisco, Avaya, Juniper, Dell, Hp ….

We have a great new MIB packaging to allow for robust network monitoring and systems monitoring with Kaseya Network Monitor. A new MIB file package for KNMv4 has been added to the download center. This package contains 29 MIB files  from different vendors such as Cisco, Dell, HP, Checkpoint, Avaya, Sonicwall, Riverbed, VMWare and Juniper.

The mib files we provide in this package can be used for monitoring network devices and systems including:
  • VOIP equipment
  • VMWare ESX servers
  • fans in a Cisco switches
  • a number of active VPN
And many many more metrics.

Remember that you will need to restart KNM after you have added the mib files to the \mibs directory.

New MIB compiler version

A new updated version of the MIB compiler will also be released in the next few days. This new version comes with allot of improvements, simplified GUI, better performance and a few bug fixes.

New version of the Kaseya MIB compiler
New version of the Kaseya MIB compiler

If you like what you’ve seen here try some of our free tools to get a better sense of how truly powerful Kaseya Network Monitor can be for your IT operation.

UPDATE:  Click here to download the MIB from our Community Resources.

12 thoughts on “Tips and Tricks: Use Kaseya for network monitoring of ESX, Cisco, Avaya, Juniper, Dell, Hp ….

    1. If you want to resolve the OID’s of incoming traps you need them in the gateway folder. The server does not synchronize out MIB files in v4 since they can be quite large, so you have to move them there manually.

  1. How is this any easier than Kaseya VSA SNMP monitoring? At least there I can easily use snmpget SNMP sets after adding MIBS and modifying OID’s.

    Intellipool/Kaseya Network Monitor really seems to be lacking when compared to products like Nimsoft.

    1. I’m trying to give this a chance, as I’d like to use Kaseya Network Monitor, but the option to set the default MIB doesn’t even show up in Advanced Properties for any objects as the documentation suggests. I also can’t seem to figure out exactly how to compile these MIBS as I followed the documentation, but it is incorrect.

      Exactly how would I simply add one MIB file so it will show up in the KNM MIB Browser? I’d appreciate the assistance.

      I can’t select the knm.mib file as I can’t change the file type, and it’s looking for a .dat file or an invalid file type listed with special characters.

      I tried with the .dat file, but that doesn’t work.

      “…1. Start the MIB compiler and click the Load button.
      2. Locate the default knm.mib file in the KNM\mibs folder of the KNM host machine and double click it.
      3. Check the box Use base MIB when compiling.
      4. Click the Compile button and select the text MIB files that you want to compile.
      5. When the compiler is finished, save the file in the KNM\mibs directory.
      It’s recommended that you use the browse function to review the compiled MIB before saving it into the KNM\mibs directory…”

      I understand MIBs and OIDs some, but this is more of a pain than importing MIBs into Kaseya. lol

      The other portion of the documentation I mentioned which appears to be incorrect (or at least not in the version of KNM as downloaded today):

      “…Default MIB – Select the default MIB file to use with this object. This MIB file is automatically selected when opening the MIB browser when configuring SNMP monitors of this object…”

      1. Hi Jeff,

        If you want to compile a new MIB you start with downloading the new version of the MIB compiler, here:

        Step two is to take all your enterprise mib files compile them, Click compile and select them all.

        The result is a new .dat MIB file that you can place in the \mibs directory. At startup this will be merged together with the rest of the mib files in the directory.

        In the same directory there is a text file (knm.mib), thats the KNM MIB thats used by _other_ programs, for ex. if you want to send the log as traps to a higher order system.

        Notes on compiling MIB files:

        1. The new MIB compiler have the enterprise branch and a small default tree already in place, no need to include those any longer

        2. When compiling you need all dependent MIB files, each MIB file may be dependent on information in other MIB files. The MIB compiler is better to warn on this now.

        KNM have allot to offer and its not just SNMP, it complements the built in monitoring in a very nice way.

        The KNM forum is a great place if you have more questions about KNM.

        Best regards,

  2. I will test. I agree Network Monitor has a lot to offer. The problem is, we’re not out to replace what Kaseya can already do well. We just want some basic monitoring from the perspective of vcenter for VM’s and network device port monitoring.

    So far, this product offers nothing new that I’ve seen except maybe working SNMP Trap features that were never finished in Kaseya and hopefully bug free SNMPget that doesn’t have to be manually edited, but rather easy to set up monitoring from MIBs and OIDs.

    I think many companies would like to see out of the box support for and easy configuration of VM and network device monitoring. Kaseya covers Windows servers quite well…maybe lacking with *nix though.

    1. KNM offers allot of functionality not previously available, but its a whole new program so its hard to cover it all in a blog. Lua scripting, unix/linux monitoring systems, integrated reporting, toplists, 37 pre-built monitors, integrated network discovery, network “weather” maps, VMWare hardware monitoring, hyper-v monitoring, interactive mib browser, a mib compiler, just to name a few.

  3. Ahh, the 3 LUA scripts to monitor hardware for ESXi ? Those are maybe useful, but there’s more to a virtual environment than the physical hardware of an ESXi host to monitor, such as all the VM’s and Datastores within vCenter.

    We haven’t tested linux monitoring capabilities, but it might be another benefit.

    I did like the Mib browser in that it was more useful than Kaseya. It was a nice surprise to find after using the updated MIB compiler to import custom MIBs. Not ideal to have to restart KNM just to import a MIB, but it’s not often we will need to import more MIBs.

    I managed to kill KNM though after having added a second OID to a monitor and clicked save. Received a bunch of code in the browser and could not access KNM from any machine until I restarted it. After the restart, it worked just fine.

    Keep up the work and hopefully there will be a useable product with 4.1.

    1. Yea, they are example, easy to modify and extend to other type of hardware parameters. More VM functionality will come .

      If you experience a crash, please look in your KNM product directory, there will be a crash dump file there that you can send to us via the service desk, would give us a chance to debug the problem.

      I would also recommend checking out this blog the coming months for info on what direction KNM is taking in the future.

Leave a Reply

Your email address will not be published. Required fields are marked *