NetXMS Support Forum

Похоже что в CableDiag.mib.txt надо добавить

Counter32 FROM SNMPv2-SMI

в секции IMPORTS.

Надо компилировать не отдельный файл, а все сразу, например так:

cd c:\nextms\var\mibs
c:\netxms\bin\nxmibc -d .

не забудьте переименовать новые MIB файлы в .txt!

Сейчас push можно сделать только через C API - там есть функция NXCPushDCIData. Сделаю соответствующий метод в NXCSession в следующем релизе.

Hi!

Can you also please send me walk result for .1.3.6.1.4.1.9.5.1.4.1.1, .1.3.6.1.4.1.9.5.1.3.1.1, .1.3.6.1.4.1.9.5.1.2 and .1.3.6.1.2.1.2.2.1.2 ?
Looks like I have to do some changes in the Catalyst driver.

Best regards,
Victor

Hi!

Check that:

1. NetXMS agent is running on your monitoring server
2. It has both 127.0.0.1 and monitoring server's IP address listed in MasterServers parameter
3. Port check subagent is loaded (there should be line SubAgent=portcheck.nsm in nxagentd.conf)

Best regards,
Victor

Это имелось ввиду, что мне надо менять Я постараюсь сделать в 1.2.1 возможность использовать английские названия счетчиков.

Мне удалось повторить эту ситуацию у себя. Похоже что баг в инсталляторе. Исправлю в 1.2.1.

Надо сначала сделать session.syncObjects().

Hi!

Check what dependencies you have in NetXMS Core service. Looks like one of this services cannot start. Try to start each dependency service manually and see what happens.

You can have web frontend for NetXMS. It is installed as separate package. For Windows it is https://www.netxms.org/download/webui/netxms-webui-1.2.0.exe (32 bit) or https://www.netxms.org/download/webui/netxms-webui-1.2.0-x64.exe (64 bit).

Best regards,
Victor

Looks like memory leak in server. You mention that all conversion functions are kept in one library script. How do you call them?

Best regards,
Victor

Yes, it should support stacked switches as well. From management system point of view, it's just one device with multiple modules. We already support stackable Avaya (Nortel) switches for example.

Best regards,
Victor

Hi!

It's overdue already I plan to made a release on Monday, but it's still not ready. Should be released in the few days however.

Best regards,
Victor

This can be done with scripts in event processing policy. You can determine switch where host is connected, and ignore event if it is down. I will also add a feature request for implementing it as standard event correlation rule.

Best regards,
Victor

Can you please send me the output of snmp walk for .1.3.6.1.4.1.9.5.1.2.14 and .1.3.6.1.2.1.1 for that switch?

Best regards,
Victor

Hi!

The most generic would be to just dump everything, like this:

nxsnmpwalk -v 2c -c community switch_ip .1.3.6.1 > file_name

Best regards,
Victor