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

T

Tom

@Tom
Unfollow Follow
About
Posts
28
Topics
8
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Server crashes after a few minutes
    T Tom
    Support

    Good morning,

    update:

    Discover found the new devices at about 8 pm.

    queues at the moment (still increasing):
    netxmsd: sh queue
    Condition poller                 : 0
    Configuration poller             : 0
    Data collector                   : 0
    Database writer                  : 0
    Event processor                  : 0
    Network discovery poller         : 0
    Node poller                      : 77701
    Routing table poller             : 0
    Status poller                    : 0

    I created the dump, but I think you can see all the devices and related community strings in it. For security reasons I renamed all community strings in the file, I hope it is still readable for you.

    Link to the dump was sent to you per pn.

    Thanks for the help,

    Greetings
    Tom


  • Server crashes after a few minutes
    T Tom
    Support

    The node pollers increase rapidly now...

    netxmsd: sh que
    Condition poller                : 0
    Configuration poller            : 0
    Data collector                  : 0
    Database writer                  : 0
    Event processor                  : 0
    Network discovery poller        : 0
    Node poller                      : 10422
    Routing table poller            : 0
    Status poller                    : 0

    netxmsd:


  • busy SNMP Agents - Node down / node up alarms in 1 Minute
    T Tom
    Support

    hm, ok... it's a pity cause it sounded so good 🙂


  • busy SNMP Agents - Node down / node up alarms in 1 Minute
    T Tom
    Support

    Just found the parameter "PollCountForStatusChange"  and I think I will test this one.


  • Server crashes after a few minutes
    T Tom
    Support

    Hi,

    the server runs normal now after activating the dump...

    But I think there is a problem now with the pollers or discovering. Discover is activated, but no new devices are found until now.

    Here is the output:
    netxmsd: sh qu
    Condition poller                : 0
    Configuration poller            : 0
    Data collector                  : 0
    Database writer                  : 0
    Event processor                  : 0
    Network discovery poller        : 0
    Node poller                      : 3469
    Routing table poller            : 0
    Status poller                    : 0

    netxmsd: sh poll
    PT  TIME                  STATE
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:41:01  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:41:01  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:41:01  wait
    S  29/May/2008 13:41:01  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:41:01  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:41:01  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:41:21  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:41:01  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:41:01  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:41:16  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    S  29/May/2008 13:40:56  wait
    C  29/May/2008 13:15:22  wait
    C  29/May/2008 13:12:51  wait
    C  29/May/2008 13:15:17  wait
    C  29/May/2008 13:14:47  wait
    R  29/May/2008 13:38:32  wait
    R  29/May/2008 13:38:32  wait
    R  29/May/2008 13:38:39  wait
    R  29/May/2008 13:38:32  wait
    R  29/May/2008 13:38:32  wait
    D  29/May/2008 13:06:46  wait
    N  29/May/2008 11:05:49  wait
    N  29/May/2008 11:05:49  wait
    N  29/May/2008 11:05:49  wait
    N  29/May/2008 11:05:49  wait
    N  29/May/2008 11:05:49  wait
    N  29/May/2008 11:05:49  wait
    N  29/May/2008 11:05:49  wait
    N  29/May/2008 11:05:49  wait
    N  29/May/2008 11:05:49  wait
    N  29/May/2008 11:05:49  wait
    A  29/May/2008 12:45:49  wait

    Is this a normal behavior?

    DiscoverInterval is set to 6000 and active.

    Greetings
    Tom


  • Server crashes after a few minutes
    T Tom
    Support

    yes, windows.

    ok, I will try to reproduce the error.

    Thanks


  • Server crashes after a few minutes
    T Tom
    Support

    it just happened again...

    I deleted round about 10 devices and changed the discover parameters. After restarting netxms core the server crashes after about 3 minutes.

    Server restart, crash after some minutes.

    server restart, disable discover - server restart - crash after a few minutes.

    server restart, now it runs for about 10 minutes without problems.

    Any idea? I think it happend because I deleted some devices...


  • busy SNMP Agents - Node down / node up alarms in 1 Minute
    T Tom
    Support

    Hi,

    I increased the value of of "SNMPREQUESTTIMEOUT" to 5000 (ms) and restarted the server.
    But this night there are still node down/node up events.

    So still another request for the next release 😉

    Greetings Tom


  • future plans and your work on zabbix
    T Tom
    Development

    Hi,

    thank you very much for the statement. It's easier for me now to stand on my decision of netxms as our new network management software.
    Nice to hear that development is still ongoing. I cant await some improvements 🙂

    Greetings
    Tom


  • future plans and your work on zabbix
    T Tom
    Development

    Hi,

    while reading the manual of zabbix I found the names victor and alexander kirhenstein (misspelled?) in the section "contributors".

    Are there plans to merge the two projects?
    We are really looking for a stable network management solution with ongoing development and now are unsure of the development of netxms. Today I would say "yes, netxms can help us in most cases, even if there are some bugs".

    It would be nice to hear what plans you have  😉

    Thanks,

    Greetings
    Tom


  • busy SNMP Agents - Node down / node up alarms in 1 Minute
    T Tom
    Support

    Hi,

    I thought about increasing the snmp timeout value, but I think this will not change anything, because the initial request can not be made. But I will test it.

    Thanks you for your plans to improve this 🙂

    Greetings
    Tom


  • Exclude some devices in autodiscover
    T Tom
    Support

    Thanks for the help, I will do a test with the script


  • Exclude some devices in autodiscover
    T Tom
    Support

    Hi,

    is there a way to exclude some clients in autodiscover process? I scan the networks for snmp devices. unfortunately, some HP Printers react on my snmp community and are added to the devicelist.

    Its only one subnet - I have 10 switches there to manage, and 10 printers that I dont want to include in the scan.

    Is there a way to exclude the whole subnet from configuration polls? There are nor changes in this network normally.

    Thanks,

    greetings
    Tom


  • busy SNMP Agents - Node down / node up alarms in 1 Minute
    T Tom
    Support

    Hi,

    we have a problem with busy snmp agents on some switches.

    We have some nodes that are changing the status in 1 minute from normal, to down, to normal.
    For example:
    "20:33:47" "warning" "switch1" "SYS_SNMP_UNREACHABLE" "SNMP agent is not responding"
    "20:33:47" "critical" "switch1" "SYS_NODE_DOWN" "Node down"
    "20:33:47" "critical" "switch1" "SYS_NODE_CRITICAL" "Node status changed to CRITICAL"
    "20:34:50" "normal" "switch1" "SYS_SNMP_OK" "Connectivity with SNMP agent restored"
    "20:34:50" "normal" "switch1" "SYS_NODE_UP" "Node up"

    I think the reason is that our older switches are sometimes heavy loaded at the management interface because we use Kiwi Cat Tools to get the actual mac table and port infos every 30 minutes.

    Is there a way to change the retry intervals for snmp connectivity? It would be no problem to receive a error message after 2 minutes instead of 1 minute. Its better than a system that produces 5 or more false error messages a day...

    Greetings
    Tom


  • Server crashes after a few minutes
    T Tom
    Support

    i enabled the autodiscover after it runs stable a while.

    no crash during the last hour now...

    strange, but ok  😉


  • Server crashes after a few minutes
    T Tom
    Support

    Seems ok with disabled Discovery... It now runs without crash, before it crashed after 3 minutes...

    netxmsd: sh mutex
    Mutex status:
      g_hMutexIdIndex: unlocked
      g_hMutexNodeIndex: unlocked
      g_hMutexSubnetIndex: unlocked
      g_hMutexInterfaceIndex: unlocked

    ---------------------------------------------------------
    netxmsd: sh queues
    Condition poller                 : 0
    Configuration poller             : 0
    Data collector                   : 0
    Database writer                  : 0
    Event processor                  : 0
    Network discovery poller         : 0
    Node poller                      : 0
    Routing table poller             : 0
    Status poller                    : 0


  • Server crashes after a few minutes
    T Tom
    Support

    Hi,

    now I have a big problem with netxms...

    I made some changes to devices. Deleted a few, changed the snmp community on some others and changed the default community in discovery.
    Suddenly the server crashed, means the service stopped.

    Now when I start it again, it runs a few minutes and then crashes again.
    I test now with a disabled Active Discover

    Any ideas what I can do?

    NetXMS 0.2.21
    75MB MySQL Database

    netxmsd: show stats
    Total number of objects:     5207
    Number of monitored nodes:   142
    Number of collectable DCIs:  724

    netxmsd: sh queues
    Condition poller                : 0
    Configuration poller            : 142
    Data collector                  : 0
    Database writer                  : 0
    Event processor                  : 0
    Network discovery poller        : 0
    Node poller                      : 1424
    Routing table poller            : 0
    Status poller                    : 0

    Thanks,

    Tom


  • No Hostname for Object "HP ProCurve Switch 2810-24G"
    T Tom
    Support

    Hi Victor,

    thank you again for the quick reply.
    I thought that a configuration poll will update the device name. Nice to have, but not really important.

    It's ok for me to delete the devices I have renamed. At the next discover they are found correctly.

    Greetings
    Tom


  • No Hostname for Object "HP ProCurve Switch 2810-24G"
    T Tom
    Support

    Hi,

    We have 2 switches of the HP ProCurve series in our network. They were both discovered through snmp at initial discover.

    In the object browser, both of them are called ""ProCurve Switch 2810-24G". I checked the config of these switches and gave them correct hostnames.
    Then I did a configuration poll to the host, with the following output:

    [21-May-2008 07:45:11] Sending poll request to server...
    [21-May-2008 07:45:11] Poll request accepted
    [21-May-2008 07:45:11] Starting configuration poll for node ProCurve Switch 2810-24G
    [21-May-2008 07:45:11] Checking node's capabilities...
    [21-May-2008 07:45:11]    SNMP agent is active (version 2c)
    [21-May-2008 07:45:12]    System description changed to ProCurve J9021A Switch 2810-24G, revision N.11.06, ROM N.10.01 (/sw/code/build/bass(bh2))
    [21-May-2008 07:45:13] Capability check finished
    Checking interface configuration...
    [21-May-2008 07:45:13] Interface configuration check finished
    [21-May-2008 07:45:13] Checking node name
    [21-May-2008 07:45:13] Node name is OK
    [21-May-2008 07:45:13] Finished configuration poll for node ProCurve Switch 2810-24G
    Node configuration was changed after poll
    [21-May-2008 07:45:13] Poll completed successfully
    

    The device name should be siebru001n, as seen here:

    Siebru001n                                                 21-May-2008   7:47:41
    ===========================- TELNET - MANAGER MODE -============================
                       Switch Configuration - System Information
    
      System Name : Siebru001n
      System Contact :
      System Location : 5161/1
    
      Inactivity Timeout (min) [0] : 0      MAC Age Time (sec) [300] : 300
      Inbound Telnet Enabled [Yes] : Yes    Web Agent Enabled [Yes] : Yes
      Time Sync Method [None] : None
    

    What I am doing wrong?

    Greetings
    Tom


  • saved Map view and discover of new devices
    T Tom
    Support

    As attachment you see the map how it looks at my network.

    Just as an information for you 😉

    Scale 1:4

    Btw: I played around with more maps in the latest release - but unfortunately there are no links between the devices, or I didnt check it 😉
    I will wait for the next release and then post again.

    Greetings
    Tom


    netxms_map.jpg

  • 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