NetXMS Support Forum

Another possible solution could be script DCI that will collect all necessary tables and built one common table.

Best regards,
Victor

Hi,

currently web page dashboard element do not refresh web site periodically (it expects that web page will refresh itself). Feel free to add feature request for that.

Best regards,
Victor

Hi,

on Windows it should be located in C:\NetXMS\var (or <install path>\var if you install server into non-standard location). You can compile it yourself by running

nxmibc -z -d C:\NetXMS\share\mibs -o C:\NetXMS\var\netxms.mib

Best regards,
Victor

Hi,

check that you have lm_sensors-devel package installed. Source build will just skip lmsensors subagent build without lmsensors development package.

Best regards,
Victor

Hi,

do the server crash after that or just drops connection? Also, please try 2.0.2 release that just came out.

Best regards,
Victor

Hi all,

NetXMS version 2.0.2 is out. It is another patch release for 2.0 branch. Changes since previous release are following:


- Optimized LDAP synchronization for large directories
- Added NXSL API for manipulating object geolocation
- Fixed bug that allows to crash server remotely by sending garbage to client connector port
- NXSL: new hash map attributes "keys" and "values"
- Object custom attributes can be accessed as hash map in NXSL
- New server debug console commands "log" and "logmark"
- Management console:
        - Improved file transfer error handling
        - Double click on geo map zoom in and center map on point under cursor
- Android Console:
        - Updated ACRA library: now crash reports are sent via e-mail (will use the app installed on device to send mail)
        - Fixed bug in action bar commands: disconnect and exit sometimes wasn't working
- Android Agent:
        - Updated ACRA library: now crash reports are sent via e-mail (will use the app installed on device to send mail)
- Fixed issues: #1042, #1049, #1093, #1111, #1117, #1125, #1128, #1133, #1134, #1139

Best regards,
Victor

Hi,

you can install agent and then use Process.Count(exe_name) parameter to monitor how many instances of given process are running, and setup threshold to raise an alarm when it is 0 (or below any other required number). There are video tutorials available on setting up basic stuff like installing agent, configuring thresholds, event processing rules, etc.

Best regards,
Victor

Do you see correct MAC address on workstation's interface? If yes, is this MAC address present in FDB table you see in console and is it the only MAC address on a port?

So the problem is not with reading FDB, but with internal logic. Can you run manual topology poll (from Poll->Topology context menu) on Cisco switch and your workstation and show results?

Hi,

do you remember what exact version you were using before? From the log it seems that driver cannot receive anything from serial port, and there were no changes in driver code since 1.2.12.

Best regards,
Victor

I just noticed that you check FDB on switch using object tools. What is shown if you use Topology -> Switch forwarding database context menu on switch?

Is it all MAC addresses that should be? If not, try to use community@vlan for different vlans (for example, public@100 as community string for vlan 100) - will it report all MAC addresses? Also please do walk on .1.3.6.1.2.1.17.4.3.1.2 and .1.3.6.1.2.1.17.4.3.1.3 (or just one walk on .1.3.6.1.2.1.17.4.3.1).

Best regards,
Victor

Hi,

check if you have -D0 in service command line. If yes, remove it.

Best regards,
Victor

Could you please send result of SNMP walk on .1.3.6.1.2.1.17.4.3.1.1 for that switch?

Best regards,
Victor

Hi,

logic behind node down/node up is following:

if status poll detects that all interfaces and agents are not responding, it marks node as unreachable. Then it checks network path - for nodes behind proxy it involves proxy checking. If server considers proxy node down, it marks current node as having network path problems and generates SYS_NODE_UNREACHABLE event, otherwise SYS_NODE_DOWN is generated. When contact with node restored, SYS_NODE_UP generated. To distinguish between SYS_NODE_UP generated from down nodes or nodes with network path problems, SYS_NODE_UP comes with parameter number 1 set to 0 if node recovered from "down" state or 1 if node recovered from "network path problem" state.

Is it possible that you had proxy node down?

Best regards,
Victor