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. Problem with SNMP

Problem with SNMP

Scheduled Pinned Locked Moved Support
12 Posts 2 Posters 20.6k 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.
  • V
    V
    Victor Kirhenshtein
    wrote on last edited by
    #3

    Hi,

    sounds really weird. OID you mentioned used only during topology polls to get VLAN information. Unmanaging node or disabling topology polling on it should stop it. Can you check if there is an active topology poll for this switch at time you get those SNMP requests?

    Best regards,
    Victor

    1 Reply Last reply
    0
    • N
      N
      Nikk
      wrote on last edited by
      #4

      Yes, there is topology poll, and it just keeps requesting this  oid: 1.3.6.1.2.1.17.7.1.4.2.1.4. even if I disable topology polling.

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

        Could you please turn on debug level 6 and filter out all records in server log containing name or IP address of this switch?

        Best regards,
        Victor

        1 Reply Last reply
        0
        • N
          N
          Nikk
          wrote on last edited by
          #6

          So. here is the log:

          [19-Nov-2014 11:30:27.142] [DEBUG] StatusPoll(172.22.2.11): bAllDown=false, dynFlags=0x00001001
          [19-Nov-2014 11:30:27.142] [DEBUG] [CLSN-0] Sending message CMD_OBJECT_UPDATE
          [19-Nov-2014 11:30:27.142] [DEBUG] StatusPoll(172.22.2.11 [1338]): boot time set to 1402931335 from SNMP
          [19-Nov-2014 11:30:27.142] [DEBUG] StatusPoll(172.22.2.11 [1338]): unable to get agent uptime
          [19-Nov-2014 11:30:27.142] [DEBUG] Finished status poll for node 172.22.2.11 (ID: 1338)
          [19-Nov-2014 11:30:28.392] [DEBUG] Node 1338 "172.22.2.11" queued for routing table poll
          [19-Nov-2014 11:30:28.392] [DEBUG] Routing table updated for node 172.22.2.11 [1338]
          [19-Nov-2014 11:31:28.408] [DEBUG] Node 1338 "172.22.2.11" queued for status poll
          [19-Nov-2014 11:31:28.408] [DEBUG] Starting status poll for node 172.22.2.11 (ID: 1338)
          [19-Nov-2014 11:31:28.408] [DEBUG] StatusPoll(172.22.2.11): check SNMP
          [19-Nov-2014 11:31:28.408] [DEBUG] StatusPoll(172.22.2.11): SNMP check finished
          [19-Nov-2014 11:31:28.916] [DEBUG] StatusPoll(172.22.2.11): bAllDown=false, dynFlags=0x00001001
          [19-Nov-2014 11:31:28.918] [DEBUG] StatusPoll(172.22.2.11 [1338]): boot time set to 1402931334 from SNMP
          [19-Nov-2014 11:31:28.918] [DEBUG] StatusPoll(172.22.2.11 [1338]): unable to get agent uptime
          [19-Nov-2014 11:31:28.918] [DEBUG] Finished status poll for node 172.22.2.11 (ID: 1338)
          [19-Nov-2014 11:32:33.491] [DEBUG] Node 1338 "172.22.2.11" queued for status poll
          [19-Nov-2014 11:32:33.491] [DEBUG] Starting status poll for node 172.22.2.11 (ID: 1338)
          [19-Nov-2014 11:32:33.491] [DEBUG] StatusPoll(172.22.2.11): check SNMP
          [19-Nov-2014 11:32:33.491] [DEBUG] StatusPoll(172.22.2.11): SNMP check finished
          [19-Nov-2014 11:32:33.979] [DEBUG] StatusPoll(172.22.2.11): bAllDown=false, dynFlags=0x00001001
          [19-Nov-2014 11:32:33.979] [DEBUG] StatusPoll(172.22.2.11 [1338]): boot time set to 1402931334 from SNMP
          [19-Nov-2014 11:32:33.979] [DEBUG] StatusPoll(172.22.2.11 [1338]): unable to get agent uptime
          [19-Nov-2014 11:32:33.979] [DEBUG] Finished status poll for node 172.22.2.11 (ID: 1338)
          [19-Nov-2014 11:33:38.495] [DEBUG] Node 1338 "172.22.2.11" queued for status poll
          [19-Nov-2014 11:33:38.495] [DEBUG] Starting status poll for node 172.22.2.11 (ID: 1338)
          [19-Nov-2014 11:33:38.495] [DEBUG] StatusPoll(172.22.2.11): check SNMP
          [19-Nov-2014 11:33:38.495] [DEBUG] StatusPoll(172.22.2.11): SNMP check finished
          [19-Nov-2014 11:33:39.026] [DEBUG] StatusPoll(172.22.2.11): bAllDown=false, dynFlags=0x00001001
          [19-Nov-2014 11:33:39.026] [DEBUG] StatusPoll(172.22.2.11 [1338]): boot time set to 1402931335 from SNMP
          [19-Nov-2014 11:33:39.026] [DEBUG] StatusPoll(172.22.2.11 [1338]): unable to get agent uptime
          [19-Nov-2014 11:33:39.026] [DEBUG] Finished status poll for node 172.22.2.11 (ID: 1338)
          [19-Nov-2014 11:34:43.496] [DEBUG] Node 1338 "172.22.2.11" queued for status poll
          [19-Nov-2014 11:34:43.496] [DEBUG] Starting status poll for node 172.22.2.11 (ID: 1338)
          [19-Nov-2014 11:34:43.496] [DEBUG] StatusPoll(172.22.2.11): check SNMP
          [19-Nov-2014 11:34:43.496] [DEBUG] StatusPoll(172.22.2.11): SNMP check finished
          [19-Nov-2014 11:34:44.012] [DEBUG] StatusPoll(172.22.2.11): bAllDown=false, dynFlags=0x00001001
          [19-Nov-2014 11:34:44.012] [DEBUG] StatusPoll(172.22.2.11 [1338]): boot time set to 1402931335 from SNMP
          [19-Nov-2014 11:34:44.012] [DEBUG] StatusPoll(172.22.2.11 [1338]): unable to get agent uptime
          [19-Nov-2014 11:34:44.012] [DEBUG] Finished status poll for node 172.22.2.11 (ID: 1338)
          [19-Nov-2014 11:35:33.497] [DEBUG] Node 1338 "172.22.2.11" queued for routing table poll
          [19-Nov-2014 11:35:33.497] [DEBUG] Routing table updated for node 172.22.2.11 [1338]
          [19-Nov-2014 11:35:48.497] [DEBUG] Node 1338 "172.22.2.11" queued for status poll
          [19-Nov-2014 11:35:48.497] [DEBUG] Starting status poll for node 172.22.2.11 (ID: 1338)
          [19-Nov-2014 11:35:48.497] [DEBUG] StatusPoll(172.22.2.11): check SNMP
          [19-Nov-2014 11:35:48.497] [DEBUG] StatusPoll(172.22.2.11): SNMP check finished
          [19-Nov-2014 11:35:48.981] [DEBUG] StatusPoll(172.22.2.11): bAllDown=false, dynFlags=0x00001001
          [19-Nov-2014 11:35:48.981] [DEBUG] StatusPoll(172.22.2.11 [1338]): boot time set to 1402931334 from SNMP
          [19-Nov-2014 11:35:48.981] [DEBUG] StatusPoll(172.22.2.11 [1338]): unable to get agent uptime
          [19-Nov-2014 11:35:48.981] [DEBUG] Finished status poll for node 172.22.2.11 (ID: 1338)
          [19-Nov-2014 11:36:53.497] [DEBUG] Node 1338 "172.22.2.11" queued for status poll
          [19-Nov-2014 11:36:53.497] [DEBUG] Starting status poll for node 172.22.2.11 (ID: 1338)
          [19-Nov-2014 11:36:53.497] [DEBUG] StatusPoll(172.22.2.11): check SNMP
          [19-Nov-2014 11:36:53.497] [DEBUG] StatusPoll(172.22.2.11): SNMP check finished
          [19-Nov-2014 11:36:53.903] [DEBUG] StatusPoll(172.22.2.11): bAllDown=false, dynFlags=0x00001001
          [19-Nov-2014 11:36:53.919] [DEBUG] StatusPoll(172.22.2.11 [1338]): boot time set to 1402931334 from SNMP
          [19-Nov-2014 11:36:53.919] [DEBUG] StatusPoll(172.22.2.11 [1338]): unable to get agent uptime
          [19-Nov-2014 11:36:53.919] [DEBUG] Finished status poll for node 172.22.2.11 (ID: 1338)
          [19-Nov-2014 11:37:18.498] [DEBUG] Node 1338 "172.22.2.11" queued for topology poll
          [19-Nov-2014 11:37:18.498] [DEBUG] Started topology poll for node 172.22.2.11 [1338]
          [19-Nov-2014 11:37:58.512] [DEBUG] Node 1338 "172.22.2.11" queued for status poll
          [19-Nov-2014 11:40:38.589] [DEBUG] Node 1338 "172.22.2.11" queued for routing table poll
          [19-Nov-2014 11:40:38.589] [DEBUG] Routing table updated for node 172.22.2.11 [1338]
          [19-Nov-2014 11:45:43.607] [DEBUG] Node 1338 "172.22.2.11" queued for routing table poll
          [19-Nov-2014 11:45:43.607] [DEBUG] Routing table updated for node 172.22.2.11 [1338]
          [19-Nov-2014 11:50:24.953] [DEBUG] CorrelateEvent: event SYS_NODE_UNMANAGED id 4676 source 172.22.2.11 [1338]
          [19-Nov-2014 11:50:24.953] [DEBUG] CorrelateEvent: finished, rootId=0
          [19-Nov-2014 11:50:24.953] [DEBUG] [CLSN-0] Sending message CMD_OBJECT_UPDATE
          [19-Nov-2014 11:50:24.953] [DEBUG] EVENT 12 (ID:4676 F:0x0001 S:0 TAG:"") FROM 172.22.2.11: Node status changed to UNMANAGED

          At the end I changed status to unmanaged, but as I saw in Wireshark:

          4078950 3192.569851000 172.22.5.95 172.22.2.11 SNMP 93 get-next-request 1.3.6.1.2.1.17.7.1.4.2.1.4.56088.140
          4078952 3192.571206000 172.22.2.11 172.22.5.95 SNMP 141 get-response 1.3.6.1.2.1.17.7.1.4.2.1.4.56088.153

          It still keeps spamming this oid, but in server log nothing appears from that node (after unmanaging it).

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

            Hi,

            interesting is that I don't see "Finished topology poll" message for that node. This may indicate that server is stuck within topology poller for some reason. Can you please run snmp walk from command line on this node on OID .1.3.6.1.2.1.17.7.1.4.2.1.4? I suspect that walk may cycle for some reason thus forming infinite loop.

            Best regards,
            Victor

            1 Reply Last reply
            0
            • N
              N
              Nikk
              wrote on last edited by
              #8

              Yes, that walk is forming infinite loop, and is not stoping.

              Regards,
              Nikk

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

                So it's a bug in SNMP agent on switch then. The only workaround so far is to disable topology poll on that node and restart NetXMS server.

                Best regards,
                Victor

                1 Reply Last reply
                0
                • N
                  N
                  Nikk
                  wrote on last edited by
                  #10

                  Hi,

                  Here I got response from switch manufacturer:

                  Cause
                  These OIDs are time-filtered, so per the RFCs (e.g. RFC3512, RFC4502) must return entries for all valid timeMarks.

                  The SNMP browser should understand the behavior of a timeFiltered MIB and move on after seeing the timeFilter index increment. However, not all browsers behave in this manner.

                  Solution/Workaround
                  Ensure you are using an appropriate SNMP tool - such as NetSight MIB tools - that behaves correctly.

                  Workaround:
                  DFE firmware 6.01.01.0020 introduced a new command which can accommodate SNMP browsers that are not timeFilter-aware.

                  Release notes state, in the "Software Changes and Enhancements" section:
                   
                  A new SNMP control, "set snmp timefilter break", allows users to configure the
                  GET-NEXT behavior of MIBs indexed with timeMark. When this is set to 'enabled',
                  SNMP will not return incrementing index values. Many SNMP tools do not properly
                  support timefiltered MIBs and will benefit from this new setting. When disabled,
                  SNMP returns RFC conformant indexing.

                  Here is the command syntax, as seen in a sample cli session:
                    NSeries(rw)->set snmp timefilter

                    Command: set snmp Create SNMP agent entries

                    Object: timefilter            SNMP timefilter configuration
                    Usage:  set snmp timefilter break {disable | enable}

                  So maybe NetXMS doesn't support timeFiltered MIBs, or it could be something else?

                  Best Regards,
                  Nikk

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

                    Hi,

                    no, we do not support time filtered MIBs. I'll add this as feature request.

                    Best regards,
                    Victor

                    1 Reply Last reply
                    0
                    • N
                      N
                      Nikk
                      wrote on last edited by
                      #12

                      Thank you!

                      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