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. SNMP Seperating a VarBinds

SNMP Seperating a VarBinds

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 11.4k 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.
  • S
    S
    Sympology
    wrote on last edited by
    #1

    I'm new to SNMP and NetXMS and I've got most things I want working ok so far.

    I'm now struggling with seperating a trap out. If I can get this I can work out the rest.
    In the Log the bit I'm interested appears in the Varbinds, but I can't work out how ot filter each one to create a seperate event for each. At the moment I report on the trap as an issue, but can't say for example "Port 1 is down" as I can't seperate Port 1 from Port 2.
    An example trap is below, but how do I set it up so that I can alert on each seperatly? (not full varbind, this is the key bit)

    .1.3.6.1.4.1.4111.1.2.2.1.1.1.0=='Port ID:1'
    .1.3.6.1.4.1.4111.1.2.2.1.1.1.0=='Port ID:2'

    1 Reply Last reply
    0
    • V
      V
      Victor Kirhenshtein
      wrote on last edited by
      #2

      You cannot create different events from same trap based on varbinds. However, you can process events differently based on event parameters. For example, if you wish to process differently events related to port 1, you can do the following:

      1. set varbind .1.3.6.1.4.1.4111.1.2.2.1.1.1.0 as event parameter (let assume that it will be parameter #2)
      2. in event processing policy, set appropriate event in event column, and in script column, create filtering script like this:
      $2 == 'PortID:1'
      

      This rule will match only events where parameter #2 is equal to string 'PortID:1'.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • S
        S
        Sympology
        wrote on last edited by
        #3

        Thanks for you help, that worked brilliantly

        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