If everything is set up correctly (device responds to SNMP requests from NetXMS server and provides information via CDP MIB) you should see picture like attached. Also, may be I didn't understand your question correctly - NetXMS is able to collect information from CDP-enabled devices (like switches or routers) and display it. NetXMS server or agents by itself does not work as CDP peers. Best regards, Victor [image: topology.png]

Hi! Versions starting from 0.2.23 available at https://www.netxms.org/download/archive. You can try to use console version 0.2.23. If it will not work, I'll try to find 0.2.22 version installer. Best regards, Victor

It will be available in a few days. Best regards, Victor

[solved] https://www.netxms.org/forum/oe-oo/ok-oke-netxms/ sudo ldconfig sudo make install

Works now, updated to 1.0.7... Weird. We use Ubuntu Linux as operating system.

Hi! You can use situations in conjunction with dummy DCI. For example, you can update situation object each time you got line from a log, setting situation's attribute to current time stamp. Then, create dummy DCI with transformation script, check situation's attribute, and return different values depending on how long time was passed since last situation update, and set thresholds as usual. And starting from 1.0.8, you will be able to generate new event directly from transformation script. Best regards, Victor

Hi! It's a bug in a server. I have fixed it, and version 1.0.8 should work fine. If you are running server on UNIX, I can post a patch. Also, as a workaround, you can use function GetSituationAttribute to get attribute's value instead of directly accessing it. Btw, you should specify attribute name without quotes in configuration dialog. Best regards, Victor

Hi! Please replace file dbinit_mssql.sql with attached one and run nxconfig.exe again. It should initialize database properly. Best regards, Victor dbinit_mssql.sql

Hi! Fixed that, thank you! Best regards, Victor

Hi! Parser file should be placed on the agent. Best regards, Victor

Hi! Last special build uses SO_REUSEADDR option - it makes no difference. As for MaxUserPort, things are different on Windows 2008 - http://support.microsoft.com/kb/929851. So by default we should have about 16000 ports for outgoing connections, which is much more then required. Best regards, Victor

It's working. Found the file test.txt in c:\NetXMS\var Was expecting it in the same dir as the executed command. Maurice Spronkers

Hi! Alex-san. I applied patch. And I confirmed the problem had been solved. Thank you for your support. Sincerely. Shin

@victor said in Viewing SNMP Traps: is it possible that incoming SNMP packets blocked by firewall at NetXMS server machine? Port was indeed blocked by Windows Firewall. I usually turn-off that, but Recently I've opted a new m/c which had Firewall turned on Trap messages now seen into both Event Browser and SNMP Trap Log. I see a problem where Event Browser shows SNMP_UNMATCHED_TRAP, while I've proper mapping of Trap OID with Event type. You already have PCAP so we can figure out who is doing what wrong However Event Type is properly shown as SYS_SERVICE_UP/SYS_SERVICE_DOWN for SNMPv2 Trap.

Apologies in advance for being OT.  It seems like the best channel for hands-on knowledge. I'm looking for a network system monitoring package with the most flexible presentation layer.  Nagios and company all do fine at monitoring servers and links; cacti/mrtg/RRD and friends do a great job of compiling statistics and making endless graphs. We're looking for something with a dynamic display that automatically displays the "interesting" stuff.  Imagine a display that shows things that are farthest from their norms - the overloaded server or network link, and has at most a click away the historical data that shows why something is wrong now.  Broken functionality, of course, comes at the top of the list of things to display. Is this something I can configure NetXMS to do?  If not, does anyone know of any existing packages that do something like this? TIA, --- David

Correct - one '0' too much. Sorry for that. It works Br, Jdamien

Alarm termination by regular expression implemented in 1.0.7. You have to upgrade both server and management console to be able to configure it. Best regards, Victor

Agent reload config on restart - so if change agent's config, you have to restart it. Maybe you just press "Save" instead of "Save & Apply" after first change? Best regards, Victor

Hi! This can be done by setting "proxy" attribute for a DCI. For example, if you need to have DCI on node A, but get information from node B, you can configure DCI on node A and set it's "proxy" attribute to node B. For security reasons, you must also add node A to list of trusted nodes for node B, or disable trusted nodes checking globally. Best regards, Victor

Thanks