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

N

Nikk

@Nikk
Unfollow Follow
About
Posts
160
Topics
46
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • MQTT on windows
    N Nikk
    Support

    Hello,

    I tried installing the MQTT subagent, but i get this error:
    2019.01.08 11:19:36.533 *E* Error loading subagent module "mqtt.nsm": The specified procedure could not be found.

    mqtt.nsm is located in Netxms\bin .

    I have already installed mosquitto, and it is working.

    Have i missed some steps?

    Version 2.1.11.

    Best regards,
    Nikk


  • No trap events
    N Nikk
    Support

    Hi,

    Every setting regarding traps in server config is enabled.

    Event configuration is ok, Write to Event log is enabled.

    Nikk


  • No trap events
    N Nikk
    Support

    Hello,

    I was trying the SNMP Trap mapping, when i noticed that I don't even get an event, when I receive Unmatched trap.
    In SNMP Trap configuration i have added:
    Trap OID - .1
    Event - SNMP_UNMATCHED_TRAP

    In Trap log, i can see that i'm NetXMS is receiving traps, but they are not showing as events.

    What could be the problem?

    Best regards,
    Nikk


  • Auto unbind
    N Nikk
    Support

    So, when the next configuration poll happens, it doesn't see that this node is in the specified Subnet (assuming node is down) and unbinds it?

    Best regards,
    Nikk


  • Auto unbind
    N Nikk
    Support

    Hi,

    I have a container with auto bind

    if (AddrInSubnet($node->ipAddr, "10.175.10.0", "255.255.255.0")) {
      return true;
    }

    , but now i need to unbind the nodes, when they are down for a specified time? How could i do this? As i understood the code should return false to unbind right?

    Best regards,
    Nikk


  • Agent Proxy
    N Nikk
    Support

    Hi,

    I just wanted to make sure whether agent proxy is working on virtual machines? I know that agents work, but still, for peace of mind 🙂

    Best regards,
    Nikk


  • MIB Imports failing with Import Symbol "Trap-Type" unresolved
    N Nikk
    Support

    Hi Matthew,

    Did you find the solution for this? I've stumbled upon similar erro:

    .\RECORDER-MIB.txt" ERROR 003: Parser error - syntax error, unexpected TRAP_TYPE_SYM, expecting OBJECT_TYPE_SYM in line 350

    Best regards,
    Nikk


  • Node down - but for how long? And high latency notification
    N Nikk
    Support

    Hi Victor,

    Yes, that attribute is set and the script works as well. But since that day I haven't received this alarm anymore.
    And it seems that it is working fine now.

    I guess i will need to set up event for this alarm, and monitor this for a while.

    Thank you!

    Best regards,
    Nikk


  • Node down - but for how long? And high latency notification
    N Nikk
    Support

    Hi,

    This script was working for a long time, but now we are receiving error:
    "Script (DownTime) execution error: Error 5 in line 1: Invalid operation with NULL value"

    Script:

    return SecondsToUptime(time() - GetCustomAttribute($node, "DowntimeStart"));

    Has something changed there, and this script doesn't work anymore?
    Server version 2.0.1

    Best regards,
    Nikk


  • Logparser
    N Nikk
    Support

    Hi,

    We are trying to monitor backup log file using logwatch subagent. From test files everything works fine, but when we finally try the actual file, we receive this message:

    LogParser: file size for fstat(3) is greater then for
    stat(C:\Program Files\Cobian Backup 11\Logs\log.txt), assume file rename

    The parser is very simple, just:

    <parser>
        <file>C:\Program Files\Cobian Backup 11\Logs\log.txt</file>
        <rules>
            <rule>
                <match>ERR (20.*)</match>
                <event params="1">100083</event>
            </rule>
        </rules>
    </parser>

    What could be the problem?

    I upgraded server and agent to the latest version.

    Best regards,
    Nikk


  • Parser file name
    N Nikk
    Support

    Hi,

    We have a case where we need to monitor a log file on one server, but the problem is the logfile name is created like "log yyyy-mm-dd.txt'' and are changing each day, is it possible to configure this timestamp in parsers file name?

    Best regards,
    Nikk


  • Not polling
    N Nikk
    Support

    Hi Victor,

    Thank you for fast response.

    How does this threshold work? What do i specify as operation and value if dci's is not even polled, meaning, there are no data at all.
    Is it just 0, or there is something else?

    Best regards,
    Nikk


  • Not polling
    N Nikk
    Support

    Hi,

    We had this situation where some dci's from some nodes were not polled (previously they worked). There were no warnings or something, just clean dci's without data. Las polled value showed in 1970 (default). They started working after i restarted the server. Is there a way to somehow notify that some dci's are not working, because all this time we were assuming that everything is ok.

    I recently updated to version 2.0-M5.

    Best Regards,
    Nikk


  • libnxclient missing
    N Nikk
    Support

    Thank you!


  • libnxclient missing
    N Nikk
    Support

    Hi,

    I updated my server to 2.0-M2, but when trying to use nxevent or any other tool, it shows error:
    The program can't start because libnxclient.dll is missing from your computer.
    Tried to reinstall as suggested, but still the same.
    Is this bug in installation or something else?
    OS - Windows 8.1 Pro

    Regards,
    Nikk


  • Problem with SNMP
    N Nikk
    Support

    Thank you!


  • Problem with SNMP
    N Nikk
    Support

    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


  • Problem with SNMP
    N Nikk
    Support

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

    Regards,
    Nikk


  • Problem with SNMP
    N Nikk
    Support

    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).


  • Problem with SNMP
    N Nikk
    Support

    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.

  • 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