NetXMS Support Forum

Hi!

usually you use containers in object tree to group your servers. Then you can easily create rules in event processing policy for these groups - just by specifying required container as source. For example, to send e-mail to different people for group A and group B, you should create two rules:

1. Source = Container_A, Action = send_email_to_admin_1
2. Source = Container_B, Action = send_email_to_admin_2

Best regards,
Victor

Eto oznachaet kakoj-to bug v servere, iz-za kotorogo zavisajut vnutrennie processi. A kakaja versija servera u vas stoit?

And just in case - I made changes Java console. Do you use new Java console (nxmc.exe) or legacy one (nxcon.exe)?

Best regards,
Victor

Console uses port 4701 to connect to server, so on client side you should allow remote port 4701 for nxcon.exe (and Java console), and on server side you should allow local port 4701 for process netxmsd.exe.

Best regards,
Victor

Hi!

You should use full path name to parser xml file in agent's configuration. Otherwise agent will look for it in current directory, which is usually root of disk C: or directory where nxagentd.exe is located.

Best regards,
Victor

It's not possible to do that by configuration, only by changing console code. I have added these 3 new presets, next version of the console will have them.

Best regards,
Victor

Zamenite
DBDriver = /usr/local/lib/libnxddr_oracle.so
v netxmsd.conf na
DBDriver = oracle.ddr

Pomenjalas' shema imenovanija DB driverov v 1.1.3 (stala takoj-ze, kak v Windows). Dolzni bili sozdatsja symlinki, no ne sozdajutsja.

Hi!

I don't think that transformation script is a right place for SNMP trap generation. Normally you should create threshold, and generate traps, send emails, etc. from event processing policy via actions. Currently you don't have built-in option for SNMP trap sending, but you can use any command line tool capable of sending SNMP traps and call it via "execute command" action. I agree that having built-in SNMP trap sending action is a good feature, but until it is not implemented, there is workaround.

As for multiple actions for event - you already can do that - in one rule in event processing policy you can specify multiple actions.

Best regards,
Victor

Hi!

On performance tab you will see only DCIs explicitly marked for that. In DCI properties dialog, go to "performance tab" section and check "show on performance tab" option.

Best regards,
Victor

Hi!

Yes, it's possible. Communication failure message means that console cannot connect to the server. If you can connect locally (from console installed on server machine), possible reasons could be: firewall on server machine; firewall in between server and client; misspelled server name or IP address.

Best regards,
Victor

Hi!

No, server's parameter configurationpollinginterval controls how often server do configuration polls on nodes. If you change agent configuration, you have to restart agent - agent read config only on startup.

Best regards,
Victor

I agree that rpm packages are necessary, but unfortunately I'm not familiar with rpm creation, so it probably will take lot of time for me. And if somebody will make them, that will be great.

Best regards,
Victor

Hi all!

NetXMS version 1.1.3 is out. It's mostly a bugfix release which solves some critical issues found in 1.1.2. Change log:

- Added SMS driver for Portech MV-37x VoIP GSM gateways
- Fixed serious memory leaks in server
- Fixed compilation problems on some Linux distributions
- Multiple fixes and minor improvements in server and management console

Best regards,
Victor

In 1.1.3, naming scheme for database drivers was changed. It is supposed to create symbolic links, but looks like it doesn't. You can fix it in two ways:

1. Change DBDriver line in config to

DBDriver = mysql.ddr

2. or manually remove /usr/local/lib/libnxddr_mysql.so and create symlink with same name to /usr/local/lib/netxms/dbdrv/mysql.ddr

Best regards,
Victor

Java console version 1.1.3 available for download at download page.

Best regards,
Victor