NetXMS Support Forum

Hi!

Send them to dump-at-netxms.org

Best regards,
Victor

Quote from: aaa-aaa on January 19, 2011, 10:48:27 AM
добрый день, не подскажете возможно ли установить интервал опроса по snmp отличным от интервала опроса по icmp? по умолчанию, как я понимаю, интервал опроса 60 сек (параметр StatusPollingInterval).

Если речь идет о status poll, то нет.

Начиная с версии 1.0.9 данные типа OCTET STRING автоматически конвертируются в Hex формат, если содержат непечатаемые символы. Это можно отключить, выстави параметр сервера AllowTrapVarbindsConversion в значение 0.
Также в версии 1.0.9 nxsnmpget, nxsnmpwalk, и MIB Browser в консоли автоматически конвертируют OCTET STRING в Hex формат, если те содержат непечатаемые символы - по аналогии с утилитами из пакета Net-SNMP.

What would be your preferred (or desirable) way of working with NetXMS? I don't mean current situation, when you should use Windows-based management application, but how you would like to work with the system.

Best regards,
Victor

Hi all!

NetXMS version 1.0.9 is out! Changes from previous release:

- Added LLDP support
- MIB compiler improved
- SNMP tools improved
- Added automatic conversion of non-printable strings in SNMP traps
- New MIBs added: APPLICATION-MIB, JVM-MANAGEMENT-MIB, APACHE2-MIB,
  SYSAPPL-MIB, RADIUS-AUTH-CLIENT-MIB, RADIUS-DYNAUTH-CLIENT-MIB,
  RADIUS-AUTH-SERVER-MIB, RADIUS-DYNAUTH-SERVER-MIB, RDBMS-MIB,
  RADIUS-ACCT-CLIENT-MIB, MSSQLSERVER-MIB, RADIUS-ACCT-SERVER-MIB,
  BAY-STACK-MIB, S5-AGENT-MIB
- Fixed broken static agent build
- Fixed issues: #313, #318

Most likely this will be the last release in 1.0.x branch (unless there will be serious bugs - in that case I will create bugfix releases). I plan to focus on development of 1.1.x branch. Version 1.1.0 will be released in a few days.

Best regards,
Victor

К сожалению, получить дополнительную информацию о причинах неуспешного запуска команды от агента сейчас нельзя. Попробуйте запускать не net.exe, а скрипт, который будет перенаправлять вывод в какой-нибудь файл.

С уважением,
Виктор

У  меня совсем другая ошибка. Сначала было так:

.\zyxel-GS4024.mib.txt: ERROR 003: Parser error - syntax error, unexpected RIGHT_BRACE_SYM, expecting UCASEFIRST_IDENT_SYM or LCASEFIRST_IDENT_SYM or NUMBER_SYM in line 1462

Поправил MIB, убрав лишнюю запятую в конце списка:


        SYNTAX  INTEGER {
            config_1(1),
            config_2(2),
        }


стало


        SYNTAX  INTEGER {
            config_1(1),
            config_2(2)
        }


После этого получил

ZYXEL-GS4024-MIB: ERROR 002: Import module "DISMAN-PING-MIB" unresolved

Похоже он тоже нужен, помимо приложенных файлов.

С уважением,
Виктор

Hi!

Did you succeed with building UNICODE agent? If yes, it will be nice if you can share diff for converting agent to unicode - I then will be able to incorporate these changes to trunk and make unicode build as default option for Windows platform.

Best regards,
Victor

Hi!

Server considers node as down if all it's interfaces is not reachable and node cannot be contacted by SNMP or via agent. How long a reboot was taken? If it was relatively fast, then it is possible that moment when node was completely unreachable fall between two status polls (each 60 seconds by default), and server never seen these two nodes as completely down.

If this is the case, solution depends on your goal - for example, if you wish to detect that node was rebooted, you can add monitoring of system uptime, and if it below some small value, like 100 seconds, that means that node was just rebooted and you can generate appropriate event.

Best regards,
Victor

Hi!

Did you turn off automatic layout (menu Map -> Enable automatic layout)?

Best regards,
Victor

Because you are monitoring services using DCIs, you will not get service down events in case of entire node down, because there will be no new values for DCI, and therefore no events will be triggered. Btw, it is not recommened to use SYS_xxx events in thresholds - they are generated by server in various situations, and you can get unexpected results. SYS_SERVICE_DOWN and SYS_SERVICE_UP generated by server during status poll of network services. Until you are not using network service objects, you are fine, but if you eventually configure some, you will get unexpected events. Better approach is to create your own events.

Best regards,
Victor

Hi!

Try to use GetSituationAttrubute(s, "status") instead of s->status - there was a bug report that latter method of accessing situation's attributes still not working, although I was thinking that I have fixed it for 1.0.8 - I still didn't check that myself (see this: https://www.netxms.org/forum/configuration/logwatch-function/msg4934/#msg4934).

Best regards,
Victor

Did you try console programs as well (something very simple like cmd /c echo test > c:\test.txt)?

As you are running Windows 2008 R2, it is 64 bit. Are you running 1.0.4 agent? If yes, it is 32 bit, and it may cause some problem (although it shouldn't). In this case, could you please try to replace agent with x64 version (it will be agent version 1.1.0, but it is compatible with 1.0.x servers).

Best regards,
Victor

Hi!

How many nodes you are monitoring? Could you please check status of pollers and queue sizes at the moment when node in question is down, but not detected yet (by running nxadm -i and then giving commands "show pollers" and "show queues")?

Best regards,
Victor