NetXMS Support Forum

Hello!

Just test it - yes, there are some another bug. I'll fix it. (I have registered this bug in bugtracker under ID 264). I'm very sorry for inconvenience

And what you mean saying that you cannot specify OID? It's just a text field in DCI configuration dialog. Did you mean that you cannot see appropriate subtree in MIB browser?

Best regards,
Victor

Hi!

Attached is ecs.nsm with timeout set to 30 seconds.

Best regards,
Victor

Hello!

No, NetXMS agents cannot work in "push" mode. However, there are very little difference between server polling agents and agents sending collected data to the server in terms of traffic - you have to transfer the same amount of data anyway. The only difference is a direction of TCP connection. If connecting to remote network is problematic, there are no complete solution, however, in some cases the following workarounds may help:
1. You can use only one IP address and port for accessing entire remote network - you can setup proxy agent on gthat address, and configure NetXMS server to access other servers in this network via proxy;
2. Sometimes you can collect information with scripts or system commands and send it to NetXMS server via nxpush command - in this case, connection will come from remote machine to NetXMS server.

Best regards,
Victor

Очень странно. У меня нет Cisco к сожалению, проверил с Linux'ом. На сервере сделал


root@u300:~# net-snmp-config --create-snmpv3-user -a "QDiNDm5oiSp9MAtM" -A SHA netxms
adding the following line to /var/lib/snmp/snmpd.conf:
  createUser netxms SHA "QDiNDm5oiSp9MAtM" DES
adding the following line to /usr/share/snmp/snmpd.conf:
  rwuser netxms
root@u300:~#


После этого


C:\Source\NetXMS\debug>nxsnmpget -v 3 -a SHA1 -A QDiNDm5oiSp9MAtM -u netxms 172.30.30.12 .1.3.6.1.2.1.1.1.0
.1.3.6.1.2.1.1.1.0 [04]: Linux u300 2.6.28-15-generic #49-Ubuntu SMP Tue Aug 18 19:25:34 UTC 2009 x86_64

C:\Source\NetXMS\debug>


snmpd тоже показывает что все хорошо:


root@u300:~# snmpd -f -V -d
No log handling enabled - turning on stderr logging
NET-SNMP version 5.4.1

Received 92 bytes from UDP: [172.30.30.11]:49901
0000: 30 5A 02 01  03 30 0F 02  02 17 54 02  03 01 00 00    0Z...0....T.....
0016: 04 01 01 02  01 03 04 22  30 20 04 00  02 01 00 02    ......."0 ......
0032: 01 00 04 06  6E 65 74 78  6D 73 04 0C  76 D8 77 9F    ....netxms..v.w.
0048: 81 9A 4C 41  43 11 A3 A7  04 00 30 20  04 00 04 00    ..LAC.....0 ....
0064: A0 1A 02 02  17 54 02 01  00 02 01 00  30 0E 30 0C    .....T......0.0.
0080: 06 08 2B 06  01 02 01 01  01 00 05 00                 ..+.........

Connection from UDP: [172.30.30.11]:49901
Received SNMP packet(s) from UDP: [172.30.30.11]:49901

Sending 117 bytes to UDP: [172.30.30.11]:49901
0000: 30 73 02 01  03 30 0F 02  02 17 54 02  03 00 FF E3    0s...0....T.....
0016: 04 01 00 02  01 03 04 27  30 25 04 11  80 00 1F 88    .......'0%......
0032: 80 09 70 CF  06 58 73 CE  49 00 00 00  00 02 01 47    ..p..Xs.I......G
0048: 02 01 0C 04  06 6E 65 74  78 6D 73 04  00 04 00 30    .....netxms....0
0064: 34 04 11 80  00 1F 88 80  09 70 CF 06  58 73 CE 49    4........p..Xs.I
0080: 00 00 00 00  04 00 A8 1D  02 02 17 54  02 01 00 02    ...........T....
0096: 01 00 30 11  30 0F 06 0A  2B 06 01 06  03 0F 01 01    ..0.0...+.......
0112: 04 00 41 01  01                                       ..A..


Received 126 bytes from UDP: [172.30.30.11]:49901
0000: 30 7C 02 01  03 30 0F 02  02 17 54 02  03 01 00 00    0|...0....T.....
0016: 04 01 01 02  01 03 04 33  30 31 04 11  80 00 1F 88    .......301......
0032: 80 09 70 CF  06 58 73 CE  49 00 00 00  00 02 01 47    ..p..Xs.I......G
0048: 02 01 0C 04  06 6E 65 74  78 6D 73 04  0C 36 3A 5F    .....netxms..6:_
0064: 23 A8 58 27  28 A3 85 52  D1 04 00 30  31 04 11 80    #.X'(..R...01...
0080: 00 1F 88 80  09 70 CF 06  58 73 CE 49  00 00 00 00    .....p..Xs.I....
0096: 04 00 A0 1A  02 02 17 54  02 01 00 02  01 00 30 0E    .......T......0.
0112: 30 0C 06 08  2B 06 01 02  01 01 01 00  05 00          0...+.........

Connection from UDP: [172.30.30.11]:49901
Received SNMP packet(s) from UDP: [172.30.30.11]:49901
  GET message
    -- SNMPv2-MIB::sysDescr.0

Sending 207 bytes to UDP: [172.30.30.11]:49901
0000: 30 81 CC 02  01 03 30 0F  02 02 17 54  02 03 00 FF    0.....0....T....
0016: E3 04 01 01  02 01 03 04  33 30 31 04  11 80 00 1F    ........301.....
0032: 88 80 09 70  CF 06 58 73  CE 49 00 00  00 00 02 01    ...p..Xs.I......
0048: 47 02 01 0C  04 06 6E 65  74 78 6D 73  04 0C E3 47    G.....netxms...G
0064: AC E6 29 19  88 1C FF 2C  BA 56 04 00  30 81 80 04    ..)....,.V..0...
0080: 11 80 00 1F  88 80 09 70  CF 06 58 73  CE 49 00 00    .......p..Xs.I..
0096: 00 00 04 00  A2 69 02 02  17 54 02 01  00 02 01 00    .....i...T......
0112: 30 5D 30 5B  06 08 2B 06  01 02 01 01  01 00 04 4F    0]0[..+........O
0128: 4C 69 6E 75  78 20 75 33  30 30 20 32  2E 36 2E 32    Linux u300 2.6.2
0144: 38 2D 31 35  2D 67 65 6E  65 72 69 63  20 23 34 39    8-15-generic #49
0160: 2D 55 62 75  6E 74 75 20  53 4D 50 20  54 75 65 20    -Ubuntu SMP Tue
0176: 41 75 67 20  31 38 20 31  39 3A 32 35  3A 33 34 20    Aug 18 19:25:34
0192: 55 54 43 20  32 30 30 39  20 78 38 36  5F 36 34       UTC 2009 x86_64


Наиболее вероятно конечно то, что NetXMS формирует не совсем правильные пакеты, которые snmpd воспринимает, а Cisco нет. Можно было бы прислать полный дамп пакетов?
Ну и я собираюсь в ближайшее время купить тестовое оборудование Cisco, тогда смогу протестировать у себя.

Attached is a corrected files that should compile. Main problem was that according to SNMP RFC, identifiers should start with lowercase letters, but authors of these MIBs ignores this restriction. Also, there was one syntax error in line 426 of ACULAB-APPLIANX-MIB.txt (missing comma).

Best regards,
Victor

Unless you have mail server on same machine as NetXMS server, you should set parameter SMTPServer to IP address or domain name of your mail server, not to localhost. Your mail server should support SMTP, and should not require authentication.

Best regards,
Victor

Hello!

No, NetXMS can work only with it's own web server. Anyway, web interface is for read-only access and is not required. You can use only management console and do not install web interface.

Best regards,
Victor

В текущей версии фильтровать по severity в syslog'e нельзя. Добавлю в следующей версии (добавил в bugtracker под номером 263).

You can configure these tools via Control Panel -> Object Tools.
For example, to configure telnet tool under Tools->Connect, add new tool of type Command with name &Connect->&Telnet. In the "Command" field, enter telnet %OBJECT_IP_ADDR%, and add Everyone (or specific users/groups) to access list.

Best regards,
Victor

Hello!

Attached is a simple program that will print size of address space available to applications in megabytes. It will show 2047 for 2GB mode, and something near 3072 for 3GB mode. I can add this as agent's parameter in next release.

Best regards,
Victor

А пользователь тот-же при запуске скрипта руками, под которым агент работает? Единственно что приходит в голову - разница в environment и/или другой пользователь при запуске из-под агента и руками. Кстати, а если скрипт этот скажем через cron запустить, он работает?

Hello!

You cannot change when SYS_NODE_DOWN sent. However, you can process it depending on other node's status using situations. For example, you have to nodes: node_A and node_B, and wish to track their status, you can do the following:

1. In console, go to View -> Situations;
2. Create new situation called NodeDown (you can choose any name of course);
3. Open event processing policy
4. Create new or change default rules for SYS_NODE_DOWN and SYS_NODE_UP events: in situation column, select Edit, than check "Update situation if current rule match"; select situation NodeDown; as situation instance, enter %n (this will create separate instance for each node, each instance identified by node name); in the attribute list, add attribute called "status" (again, you van choose any name here), and as value enter 1 for SYS_NODE_DOWN event, and 0 for SYS_NODE_UP.

Now we have defined situation, which will have separate instance for each node, and for each instance wil will have attribute "status" set to 1 if appropriate node is down, and to 0 if it is not.

Now you can use this information in filtering scripts by accessing the situation:

s = FindSituation("NodeDown", "node_name");

and looking at situation's attribute "status":

s->status

For example, if I wish that certain event will be processed only if both node_A and node_B are down, I can use the following filtering script:


sub main()
{
   s1 = FindSituation("NodeDown", "node_A");
   isDownA = (s1 != null) ? s1->status : 0;
   s2 = FindSituation("NodeDown", "node_B");
   isDownB = (s2 != null) ? s2->status : 0;
   return s1 && s2;
}


Construction (s1 != null) ? s1->status : 0 is needed because FindSituation will return null if given instance does not exist. In our example, if situation's instance for node does not exist, we assume that this node is up (status attribute equals 0).

Hope this helps!

Best regards,
Victor

Похоже дальше надо вставлять отладочную печать в скрипт. Можно добавить в скрипт, чтобы он выводил результат не только на stdout, но и в какой-нибудь файл? Тогда сразу будет понятно, в какую сторону дальше копоть.

When you start agent as standalone program, not as system service, you should not use -d option. So, to debug, you should use command

"C:\Program Files (x86)\NetXMS\bin\nxagentd.exe" -D -c "C:\Program Files (x86)\NetXMS\etc\nxagentd.conf" -M "192.168.0.1"

Best regards,
Victor

Hi!

Yes, it's the same bug. I have added it to bug tracker (number 262) - it was not registered before.
The only way to add columns manually is to modify database (you can use existing table tools as an example) and then restart server.

Best regards,
Victor