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 Traps and data

SNMP Traps and data

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

    Hi,

    I'm trying to setup traps for BGP-sessions, and I've managed to get netxms to set alarm when they go up/down. My problem is that I want the neighbor that went down to be in the alarm.

    I can see the following in my SNMP traps log:

    Trap OID: .1.3.6.1.2.1.15.7.2

    Varbinds:

    ...;.1.3.6.1.2.1.15.3.1.14.10.2.4.7

    The peer in this case 10.2.4.7 seems to be included in the Varbind/OID, is there some way to extract this in netxms?

    Regards
    Johan

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

      Hi!

      It's impossible to extract part of the varbind's OID as event's parameter. However, it's possible to extract varbind's value. If trap contains some value identifying BGP peer, then it can be extracted. I suppose that BGP trap can contain either .1.3.6.1.2.1.15.3.1.7.<peer_ip_here> (bgpPeerRemoteAddr) or .1.3.6.1.2.1.15.3.1.5.<peer_ip_here> (bgpPeerLocalAddr). In that case, you can add varbind matching in trap configuration, with matching OID set to .1.3.6.1.2.1.15.3.1.7 for example. When matching varbinds, NetXMS looks for longest possible match, so it will match OID with any peer IP appended to it, which is fine in that case, because there should be one trap per one peer down event.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • J
        J
        johanborch
        wrote on last edited by
        #3

        Hi,

        Thanks for your reply

        The only thing that i can see in my trap-log is the following when a BGP session goes down and none of the vars have data in the that looks like and IP address.

        .1.3.6.1.2.1.15.7.2

        var: .1.3.6.1.1.3.0
        .1.3.6.1.6.3.1.14.1.0
        1.3.6.1.2.1.15.7.2
        1.3.6.1.2.1.15.3.1.14.A.B.C.D
        1.3.6.1.2.1.15.3.1.2.10.10.4.201
        1.3.6.1.6.3.1.1.4.3.0

        Regards
        Johan

        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