NetXMS Support Forum

Hi!

What is A, B, and "Location" - containers? If you need to calculate status of Location based on statuses of subcontainers A and B, the beset way is to use status calculation/propagation rules. If this is the case, tell me what statuses could have A and B, and I'll try to create rules for your requirement.

Best regards,
Victor

As I found in log, interface Vl1 has IP address 172.30.1.25, and interface eth0 on management server has same address. This cause NetXMS server to interpret switch as local machine.

Looks like management server has the same IP address as on one of 6509 interfaces. Could you check it? Does NetXMS server has only one IP?

Hi!

Looks somehow similar to this bug: https://www.netxms.org/bugtrack/view.php?id=319. Could you please run server in debug mode (by adding -D 6 switch to netxmsd command line) and send me the logs (either here or to dump-at-netxms.org)?

Also, question to all readers: does anybody has Cisco device in a lab with such big number of ports and able to provide me with remote access to it for some days? My best Cisco device has only 24 ports, and I can reproduce such problem (either described here or listed in the bug record) on big Nortel switches

Best regards,
Victor

You should put all files from the archive into src/nxmibc directory (replacing existing files) and run command make (assuming you still have configured source tree). If you remove sources you have built NetXMS from, you need to unpack them again, replace files, and then run ./configure and make as usual. If build will be successful, run make install to put resulting binary to appropriate place.

Best regards,
Victor

Attached. Patch file contains modified parser.l and parser.y from src/nxmibc directory, and in case you don't have flex and bison resulting C files.

Compilation is not cumulative - each time nxmibc reads all presented source MIBs and generate compiled file, erasing previously created one, if any.

Best regards,
Victor

Hi!

I run MIB compiler against Cisco MIBs from location you provided. Some of the MIBs really contains errors, but most compiler errors are bugs in nxmibc. I have fixed them, next release will contain improved MIB compiler. If you need, I can post a patch for MIB compiler here.

Best regards,
Victor

Добрый день!

Нет, функций инвентаризации в NetXMS нет. В Википедии неверная информация.

Про Wiki - попробую, вроде существует дополнение к OpenOffice для публикации документов в Wiki.

В серверных командах можно использовать серверные макросы, как в событиях или алармах. Для передачи IP адреса надо использовать %a, например

/usr/local/bin/nxsnmpset -c private -t INTEGER %a .1.3.6.1.4.1.259.6.10.94.1.7.3.0 3

С динамическими адресами пока довольно плохо. Можно делать discovery и искать вновь появившиеся адреса, но это не совсем то.

По поводу NAT - сервер подключается к агентам, поэтому один прокси на сеть скорее всего понадобится.

Hi!

Unfortunately it's not possible. You can only expand macros in template items, and only at the moment when you apply template to node.

Best regards,
Victor

Dobrij den'!

Sborok pod Ubuntu poka net, k sozaleniju. V attache sobrannij na Ubuntu Server 10.10 MySQL driver dlja NetXMS. Dostatochno ego prosto polozit' v /usr/lib i postavit' package netxms-server - po idee dolzno rabotat'.

Добрый день!

Распределение примерно такое:

0 = дебаг выключен
1 = дополнительные сообщения при инициализации и остановке сервера
2 = + больше сообщений при инициализации, некоторые внутренние ошибки
3 = + дебаг авторизации пользователей, исполнения команд
4 = + дебаг network discovery и ISC
5 = + дебаг событий, поллеров, push параметров, дополнительный дебаг ISC и network discovery
6 = + дебаг клиентских сессий, дополнительный дебаг поллеров и network discovery
7 = + дополнительный дебаг поллеров и сбора данных
8 = + дополнительный дебаг сбора данных
9 = + все SQL запросы

Общая идея примерно такая - до уровня 5-6 дебаг можно держать включенным постоянно (хотя сильно зависит от количества узлов). Начиная с 7 уровня дебаг очень подробный, туда пишутся записи о повторяющихся каждые несколько секунд операциях - соответственно и растет он очень быстро. Я обычно использую уровень 5 или 6 при отладке - 7 и выше нужны обычно при поиске дедлоков.

В отдельный лог писать нельзя, давно хочу это сделать, но никак не доберусь.

Hi!

Scripting slowly moves to more and more areas of NetXMS I agree that creating and binding objects from scripts is a very good idea. I'm not sure, however, that auto bind script is the best place to create additional objects. For network discovery purposes, additional hook will be better. For example, it can be done that way that for each newly added node system executes some script from library. Or take more generic approach, and allow script execution as action in event processing policy - that way you will be able to execute your script on each SYS_NODE_ADDED event, as well as do many other things for other events.

Best regards,
Victor

Hi!

For syslog-based events to be generated, host which is source of the event must be registered as node in NetXMS. Also, I suppose you just omit <parser> tag from posted config - <rules> must be wrapped in it.

Best regards,
Victor