NetXMS Support Forum

Hi!

Thanks for the translation! I have added language switch for Spanish and Chinese languages, and add files you have sent to the project. I also forgot to mention that there are additional files to translate - they are called bundle.properties, and located in <project_root>/OSGI-INF/l10n.
I'll post to this thread as I will prepare more plugins for translation.

Best regards,
Victor

Also, I suppose that you have to use custom event log name, not a full path to actual .evt file. If I understand correctly, all available logs are listed in registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog. But I never works with custom Windows event logs, so I may be wrong.

Best regards,
Victor

Hi!

If you give file name in <file> tag, logwatch subagent will threat it as regular text file, which I suppose is not the case. If you need to openWindows event log, you must prepend it's name with asterisk, like <file>*System</file>. And you have missing opening angle bracket in second rule, maybe just a copy/paste error.

Best regards,
Victor

Hi!

You have to get current svn repository: https://svn.netxms.org/public/netxms/trunk. Sources of Java console are under src/java/netxms-eclipse. Below that point there are various messages.properties in different plugins, like src\java\netxms-eclipse\core\src\org\netxms\ui\eclipse\console\messages.properties. There should be one message file per plugin, usually located in the root package of a plugin. PLease note that currently only few plugins are prepared for translation.

Best regards,
Victor

I plan to add additional option to SNMP trap parameter mapping - something like "don't convert to HEX string".

Best regards,
Victor

Hi!

Is it possible to install test server 1.1.7 somewhere and add those access points? Versions 1.0.x and 1.1.x has different configuration polling code, and it will be helpful to know if both versions are affected or only old one.

Best regards,
Victor

Added.

Best regards,
Victor

Support for clients with dynamic addresses is partially here - you an replace primary IP address with DNS name, and then server will do name resolution at each poll. Looks like we need additional option to use DNS name instead of IP address for discovered nodes, then this problem will be solved completely. I'll add this to my to-do list.

Best regards,
Victor

Hi!

NetXMS converts string to hex string if it sees non-printable characters in it. It is not configurable now - I'll add an option to override this behavior in next release.

Best regards,
Victor

Hello!

Looks like these devices responds strangely to NetXMS server's requests. Could you please provide me with following information:

1. What is NetXMS server version?
2. What driver is selected for those devices (you can see it on object overview page) - relevant only for version 1.1.x
3. Result of nxsnmpwalk for the following OIDS:

.1.3.6.1.2.1.1
.1.3.6.1.2.1.2.1
.1.3.6.1.2.1.2.2.1
.1.3.6.1.2.1.4.20.1

Best regards,
Victor

I'll do my best to make a release in the end of December, but it's not 100% guaranteed.

Best regards,
Victor

Currently there no such view in Java console. I'll add it to my to-do list.

Best regards,
Victor

Hi!

I start preparing Java console for translating to different languages. Actual translation is done by creating appropriate language files. You can try to locate existing messages.properties in projects (currently projects library, core, and alarm browser are prepared for translation), and create files messages_zh_CN.properties with Chinese translation. Then I will add appropriate language switch and include these translated files into main source tree.

Best regards,
Victor

Sorry, oshibsja - vmesto Agent.SupportedEnums nado ispol'zovat' Agent.SupportedLists.

Hi!

Quote from: lindeamon on December 08, 2011, 02:00:39 PM
what are the plans for the near future ?
what do i have to look for for the next release ?

My current to-do list for release 1.1.8 is following:

1. Remove "NAT adapter" pseudo-interfaces
2. Driver for Cisco Catalyst switches
3. Implement agent package deployment in Java console
4. Implement configuration export in Java console
5. Fix selection bug in network maps
6. Implement concept of "normal" interface state
7. Improve dial charts
8. Show threshold violations in "Last Values" view/widget
9. Add additional page for containers where threshold violations for underlying nodes are shown
10. Implement dashboard copy (clone)
11. Make log viewers really usable
12. Improve "local command" object tool implementation in Java console
13. Add "custom port" field to SNMP DCIs (like in old console)
14. Allow per-DCI SNMP version settings
15. Optimize database updates when multiple DCIs collected in short interval

Best regards,
Victor