NetXMS Support Forum

Hi,

just fix that. Next release will show clusters correctly.

Best regards,
Victor

Hi,

yes, it's a bug in mssql.ddr - it cannot work with MS SQL 2012 Native Client. It is already fixed, and agent 2.0-M1 will work correctly. IN the meantime, you can try to install earlier version of MS SQL Native Client (not sure if they can coexist on one machine though).

Best regards,
Victor

Hi,

looks like a bug in nxdbmgr. As this is interface object, you can safely answer "no" here, and answer "yes" when nxdbmgr offers you to delete it. It then will be re-created by configuration poll.

Best regards,
Victor

Hi,

could you please run server with debug 6 for some time and then send me the log (pointing to fake node down moments)?

Best regards,
Victor

Hi,

did you do configuration poll on that node? We didn't do anything to parameter selection in 1.2.17...

Best regards,
Victor

Hi,

you can create a script which will compare current table rows with rows from previous poll (you can get previous value using GetDCIValue function - when transformation script runs previous value still available) and generate events as needed using PostEvent function.

Best regards,
Victor

Hi,

can you check if TCP port 4700 is listening on this machine after initial agent bootup? If yes, is it reachable from server machine?

Best regards,
Victor

Hi,

currently it's not possible. It is planned though.

Best regards,
Victor

Hi,

looks like we test our driver on quite old H3C models - they report OIDs in .1.3.6.1.4.1.43 subtree. Can you please check if your switches supports .1.3.6.1.4.1.43.45.1.2.23.1.18.4.5.1.3 OIDs?

Best regards,
Victor

Hi,

can you show a screenshot of DCI "MUXD_CurrentPA" configuration?

Best regards,
Victor

Hi,

unfortunately you problem cannot be solved by configuration. We will need to make changes in log monitoring subagent, so you'll have to wait for release with a fix.

Best regards,
Victor

Hi!

1. I think that separate those two will be better. I'll do this for next release.
2. Yes, this is a bug. Also notifications sometimes not filtered properly.
3. You can turn on object-level access control in logs by setting server configuration variable ExtendedLogQueryAccessControl to 1. You can try that, but depending on number of objects that could lead to complicated and ineffective SQL queries.
4. Yes, it's planned.

Best regards,
Victor

Could you please turn on debug level 6 and filter out all records in server log containing name or IP address of this switch?

Best regards,
Victor

Hi,

currently it's not possible in a straight way. In not very straight way, it could be like call PostEvent from script, put an external script action for this new event, and use nxpush from that internal script.
There is a feature request for push data function in NXSL. Most likely it will be implemented in 2.0-M1 or 2.0-M2.

Best regards,
Victor

А могли бы мне прислать файл базы (оригинальный, до обновления)? Попробую с ним разобратся.