NetXMS Support Forum

Looks like typo - you use = instead of == for comparison.

Best regards,
Victor

Check that you really get the value with SNMPGetValue - it will return null if SNMP query fails for some reason, and null != 0, so instance that cannot be read will be accepted.

Best regards,
Victor

Hi!

PhysicalDisk parameters are deprecated and may not work. They most likely will not work with RAID controllers. I think you should try to wrap call to smartmontools into external parameter(s) to monitor disks behind RAID controller.

Best regards,
Victor

Please try to run agent in debug mode 9 and add trace="9" to parser tag (like <parser trace="9">) and provide agent's log.

Best regards,
Victor

It could be because Java 7 may try to use IPv6 for connection by default. Try to use 127.0.0.1 instead of localhost or host name when connecting.

Best regards,
Victor

Hi!

If legacy console can connect to the server it means that server and database is ok and problem is only with console. What Java version you have installed? Is there any messages in file %USERPROFILE%\.nxmc\data\.metadata\.log?

Best regards
Victor

Hi!

It is possible to build Windows agent for IA64 (Itanium) architecture, but I need Visual Studio 2005 Team System Edition to do that. I could also try to use IA64 compiler from platform SDK with existing VS project - but this will take some time.

Best regards,
Victor

Hi!

Once you configure summary table, it is available from container's context menu under Summary Tables (see attached screenshot).

Best regards,
Victor

Hi!

In the script you have access to DCI's "instance" field (via $event->instance). If you have correct disk name in that field (and it will be populated automatically if DCI in question was created by instance discovery) you can form correct DCI name for FindDCIByName.

Best regards,
Victor

Yes, main reason for moving name resolution to configuration poll was concern that there will be too much DNS requests. I'll see how I could make this configurable.

Best regards,
Victor

Currently NetXMS do name resolve only on configuration poll. Looks like we have to move it to status poll.

Best regards,
Victor

Hi!

Drivers are written in C++. They all extends base driver class and overrides methods needed to provide accurate information. Most important is to mark physical ports in interface list and provide VLAN information. All existing driver sources located under src/server/drivers - you can take a look.

My main problem with H3C driver is that I currently does not have access to any HP A series device for testing. I can assist you in driver development if you want to take it. Alternatively, I can write a driver if you can provide me with remote access over SNMP to some test device.

Best regards,
Victor

Hi!

Could you run agent in debug mode and provide me with debug log (at least last messages before freeze)?

Best regards,
Victor

Hi!

That means that flag NF_HAS_WINPDH (Node supports Windows PDH parameters) set and cleared periodically. Node considered to support PDH if it has NetXMS agent and agent responds correctly to PDH requests (PDH.Objects list and others). You can check server debug log (running with debug level 5 or higher) for error messages started with WinPerfObject::getWinPerfObjectsFromNode prefix.

Best regards,
Victor

Hi!

Everything is correct except event tag - it should be

<event params="1">100005</event>

Value in params attribute should match number of capture groups in regular expression (1 in your case).

Best regards,
Victor