NetXMS Support Forum

Попробуйте просто ORCL в качестве TNSName, раз он прописан в tnsnames. Ну и запуск агента с дебагом прояснил бы ситуацию - вполне возможно что не выставлен например ORACLE_HOME и клиент не может нормально работать, или еще что-то (я писал выше как агента в дебаг режимне запустить).

Делаете новый объект Network Map с типом "IP Topology". В качестве seed объекта указываете любую ноду из етой подсети. В свойствах карты отмечаете "Include End Nodes" и "Custom discovery radius", discovery radius выставляете в 1. На карту будут автоматически добавлены все устройства из подсети, в которой находится seed узел.

Hi!

Do you have core file left?

Best regards,
Victor

Hi!

If you install NetXMS from sources, you should add --with-client option to configure.

Best regards,
Victor

Hi!

No, there are no built-in check for Windows updates in agent. We was thinking about adding this, but it's quite complicated to check this from C, so we postpone it. Best solution is probably to creae some vps or power shell script and add it as external parameter to agent.
Btw, you can check that firewall, antivirus, and anti-spyware is active and up to date using the following parameters (provided by WMI subagent):

System.AntiSpywareProduct.Active
System.AntiSpywareProduct.DisplayName
System.AntiSpywareProduct.UpToDate
System.AntiVirusProduct.Active
System.AntiVirusProduct.DisplayName
System.AntiVirusProduct.UpToDate
System.FirewallProduct.Active
System.FirewallProduct.DisplayName
System.FirewallProduct.UpToDate

Best regards,
Victor

Hi!

Thanks for the patch, I've applied it to the trunk.

Best regards,
Victor

Hi!

I've added NXSL functions chr() and ord() to 1.2.9 release.

Best regards,
Victor

Можно. Вы хотите строить автоматические карты или добавлять устройства на каждую карту руками?

Hi!

Please enable crash dumps on the server (see this page for instructions: http://wiki.netxms.org/wiki/UM::Troubleshooting).
When server hangs next time, try to connect to it with nxadm tool and force server crash by entering command raise access. Then send resulting dump to me for analysis.

Best regards,
Victor

Hi!

I was under impression that you are using NetXMS agent on server with ppp interfaces. Can you test what interface list returned by SNMP agent using SNMP walk? Like this:

nxsnmpwalk -c community server_address .1.3.6.1.2.1.2.2.1.2

I suppose that it is a bug in Linux snmpd which causes to return all previous instances of ppp interface along with current one.

Another problem is changing interface index. I take a quick look inside ppp module in Linux kernel, and it looks like it assigns new interface index on each ppp connection setup. Because when you collect interface data via SNMP the only option to identify interface is by index, you cannot create simple DCI which will always work, because you'll need to change SNMP OID when interface index changes.

The easiest way to solve this would be to install NetXMS agent on this Linux server - then you'll be able to gather data by interface name. Event if it's some kind of appliance installing NetXMS agent is most likely possible if you can access it's file system and execute commands.

Best regards,
Victor

Hi!

We don't get much patches, so there are no established workflow I suggest that small patches for fixing specific bugs should be submitted via our bugtracker. Regarding large changes please contact me first and we will discuss better way.

We don't have plan to migrate to public repositories. As we are trying to build business around NetXMS (which will allow as to keep working on open source project), we have some closed source extensions and need repository we have full control of.
Our current repository is subversion, but we plan to migrate to git soon. I'll provide you with necessary access as soon as you'll need it.

Best regards,
Victor

Это надо делать на том агенте, который будет подключаться к базе. На скриншоте отсутствует начало секции ORACLE, возможно в этом проблема. Для диагностики можно запустить агента в дебаг режиме (с ключом -D9), тогда будет видно, подключается он к базе или нет (только перед этим обязательно поставить лог в файл).

Hi!

nxaction is a tool intended for connecting to agent and executing action on agent (defined in nxagentd.conf using Action parameter). For executing server action simpliest way is to use nxevent for sending custom event and executing action you need in event processing policy as usual.

Best regards,
Victor

Hi!

It should be like this:


WMI.Query(root\CIMV2\, Select * from Win32_NTLogEvent Where Logfile = 'System' and EventType = '3' and EventCode = '1020',%%count%%)


Best regards,
Victor

Hi!

Just got to issue 303. It turns out that limit for events and alarms messages was already raised to 2000. I do tests with similar security log events. Text is there, but looks like list control has some limitations as well - text is truncated when you look at events or alarms in tabular form. However, if you open alarm detail or copy appropriate record to clipboard and paste into text editor you'll see full message text.

Best regards,
Victor