Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • 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 (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. SNMP informs (assured-delivery traps?)

SNMP informs (assured-delivery traps?)

Scheduled Pinned Locked Moved C / C++ / MFC
questionhelptutoriallounge
5 Posts 2 Posters 0 Views 1 Watching
  • 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.
  • B Offline
    B Offline
    BambooMoon
    wrote on last edited by
    #1

    I have a program that uses Microsoft's WinSNMP to send traps to a configured receiver when certain error conditions occur. This program was pretty much cobbled together using sealing wax and duct tape, as I know very little about SNMP in practice, but it works well. Now someone told me that they would prefer to use SNMP informs instead of traps because the latter, based on UDP, have no assured delivery, whereas the former have an aknowledgement/retry/timeout mechanism to "guarantee" delivery. So I googled on SNMP inform till the cows came home and found a few places that describe what SNMP informs are in a general sense but none that shows exactly how to accomplish it, particularly with WinSNMP. My impression is as described below, and my question to anyone who knows better is whether my impression is correct. If not, can you please point me to how I can accomplish this with WinSNMP? My impression is that SNMP informs basically consist of the sender sending the trap just as it always did, but saving a copy of the message sent until it receives the acknowledgement, or until the sender, independently of WinSNMP, determines that it time to resend. It appears to me that the acknowledgement is not something handled in WinSNMP at all, but is just any kind of message that the sender of the trap and the receiver mutually agree on that the receiver sends back to the sender to tell him that the trap was received. In other words, it appears to me that SNMP inform is not something supported by WinSNMP as distinct from a trap, but is nothing more than a mutually agreed upon conversation between trap sender and receiver. Is this true? :confused: Thanks for any information.

    D 1 Reply Last reply
    0
    • B BambooMoon

      I have a program that uses Microsoft's WinSNMP to send traps to a configured receiver when certain error conditions occur. This program was pretty much cobbled together using sealing wax and duct tape, as I know very little about SNMP in practice, but it works well. Now someone told me that they would prefer to use SNMP informs instead of traps because the latter, based on UDP, have no assured delivery, whereas the former have an aknowledgement/retry/timeout mechanism to "guarantee" delivery. So I googled on SNMP inform till the cows came home and found a few places that describe what SNMP informs are in a general sense but none that shows exactly how to accomplish it, particularly with WinSNMP. My impression is as described below, and my question to anyone who knows better is whether my impression is correct. If not, can you please point me to how I can accomplish this with WinSNMP? My impression is that SNMP informs basically consist of the sender sending the trap just as it always did, but saving a copy of the message sent until it receives the acknowledgement, or until the sender, independently of WinSNMP, determines that it time to resend. It appears to me that the acknowledgement is not something handled in WinSNMP at all, but is just any kind of message that the sender of the trap and the receiver mutually agree on that the receiver sends back to the sender to tell him that the trap was received. In other words, it appears to me that SNMP inform is not something supported by WinSNMP as distinct from a trap, but is nothing more than a mutually agreed upon conversation between trap sender and receiver. Is this true? :confused: Thanks for any information.

      D Offline
      D Offline
      David Crow
      wrote on last edited by
      #2

      BambooMoon wrote:

      Now someone told me that they would prefer to use SNMP informs instead of traps because the latter, based on UDP, have no assured delivery, whereas the former have an aknowledgement/retry/timeout mechanism to "guarantee" delivery.

      Instead of UDP (unreliable delivery), I think you'll want to use TCP (reliable delivery).


      "Take only what you need and leave the land as you found it." - Native American Proverb

      B 1 Reply Last reply
      0
      • D David Crow

        BambooMoon wrote:

        Now someone told me that they would prefer to use SNMP informs instead of traps because the latter, based on UDP, have no assured delivery, whereas the former have an aknowledgement/retry/timeout mechanism to "guarantee" delivery.

        Instead of UDP (unreliable delivery), I think you'll want to use TCP (reliable delivery).


        "Take only what you need and leave the land as you found it." - Native American Proverb

        B Offline
        B Offline
        BambooMoon
        wrote on last edited by
        #3

        SNMP is built on top of UDP, not TCP. I'm not looking for an alternative to SNMP. I'm looking for information on how to use SNMP informs. Thanks anyway.

        D 1 Reply Last reply
        0
        • B BambooMoon

          SNMP is built on top of UDP, not TCP. I'm not looking for an alternative to SNMP. I'm looking for information on how to use SNMP informs. Thanks anyway.

          D Offline
          D Offline
          David Crow
          wrote on last edited by
          #4

          BambooMoon wrote:

          SNMP is built on top of UDP, not TCP. I'm not looking for an alternative to SNMP.

          Fair enough.

          BambooMoon wrote:

          I'm looking for information on how to use SNMP informs.

          I've not ever come across that term. Does this help?


          "Take only what you need and leave the land as you found it." - Native American Proverb

          B 1 Reply Last reply
          0
          • D David Crow

            BambooMoon wrote:

            SNMP is built on top of UDP, not TCP. I'm not looking for an alternative to SNMP.

            Fair enough.

            BambooMoon wrote:

            I'm looking for information on how to use SNMP informs.

            I've not ever come across that term. Does this help?


            "Take only what you need and leave the land as you found it." - Native American Proverb

            B Offline
            B Offline
            BambooMoon
            wrote on last edited by
            #5

            Thanks for the web site, but unfortunately it uses some product other than Microsoft's WinSNMP. It is interesting in that it claims that to use informs, you just set a flag in the outgoing trap that says it is an inform (and then the document glosses over what it means by handling the acknowledgement). But it doesn't say who decides what goes in the acknowledgement, how the sender of the trap knows that a given acknowledgement is for a certain trap (since it may have sent hundreds of traps all awaiting acknowledgement) or anything else. Thanks, but I need WinSNMP info.

            1 Reply Last reply
            0
            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.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • World
            • Users
            • Groups