Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. Interface rate / speed from all interfaces

Interface rate / speed from all interfaces

Scheduled Pinned Locked Moved Support
2 Posts 2 Posters 29.7k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L
    L
    letabawireless
    wrote on last edited by
    #1

    Hi all

    I first of all want to thank you for an awesome product !! Can't imagine my support life without it ! Now, the question:
    We mostly use Mikrotik nodes, and I can get the interface rate (the speed at which it connects) using .1.3.6.1.2.1.31.1.1.1.15 . This however, gives me all the interfaces listed, which is fine. As the nodes have different amount of interfaces, adding this dynamically might be quite a job. I would like to know if I can add an DCC entry for each interface found on the particular node, or alternatively if I can do just a DCI summary table and get a table view of all the interfaces for each of the nodes.
    I actually only need those with a value of 100, so I would like to filter on that as well.

    Thanks again !

    1 Reply Last reply
    0
    • F
      F
      Filipp Sudanov
      wrote on last edited by
      #2

      Hi!

      If I understand correctly what you a trying to achieve, instance discoverу should help. Have a look at attached screenshots. The idea is that NetXMS during instance discovery poll reals all indexes and values under .1.3.6.1.2.1.31.1.1.1.15 and creates DCIs using these indexes. It's possible to filter by OID or value.

      Or you can create NXSL script that will communicate to the device via SNMP and query what you need and use that script as a method for instance discovery.


      Screenshot at 2020-10-19 18-14-36.png

      Screenshot at 2020-10-19 18-14-44.png

      1 Reply Last reply
      0

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      Powered by NodeBB Contributors
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups