NetXMS Support Forum

Yes, this is AD LDAP page size limit. Next release of NetXMS will support LDAP paging so you'll be able to synchronize larger amount of users without increasing page size on AD LDAP server.

Best regards,
Victor

Hi,

sounds really weird. OID you mentioned used only during topology polls to get VLAN information. Unmanaging node or disabling topology polling on it should stop it. Can you check if there is an active topology poll for this switch at time you get those SNMP requests?

Best regards,
Victor

Quote from: farcsa on October 28, 2014, 06:38:30 PM
1:
Is there a simpler method to exclude events with predefined event id? (e.g.: 5,1006,1008,...)

not really - you can specify ID range in one rule, like <id>1001-1099</id>, but that will not help if you have non-adjacent IDs to ignore.

Quote from: farcsa on October 28, 2014, 06:38:30 PM
2:
I manage Windows 7, Windows Server 2008 and Windows Server 2012, and i see that the severity levels are the following:
Critical =1
Error=2
Warning =3
Information=4

The above example captures only Windows error level events. How to set the <level> parameter to capture Windows critical events? (And, of course, how to combine the values?)

combining codes described here: https://www.netxms.org/documentation/adminguide/log-monitoring.html#level-tag

Quote from: farcsa on October 28, 2014, 06:38:30 PM
3:
With the above parser, the agent always misses the event with event id 1. What could be the reason?

In the parser I don't see specific rule for DI 1, so it can only be caught by last rule by severity. Are you sure that severity for this event is "Error"?

Best regards,
Victor

Hi,

seems that you got counter ID's instead of names. Is it non-English Windows version? Can you see counter names locally via Windows standard tools? Also, can it be that you install 32bit agent on 64bit system? Maybe you need to rebuild perf counter library as described here: http://support.microsoft.com/kb/300956.

Best regards,
Victor

Hi,

I've registered it as a bug. We'll take a look.

Best regards,
Victor

Hi,

you should use ${} (UNIX-like) for environment variable expansion in configs. I've choose that form because you may need to pass % sign to underlying layer (for example, it is often used in names of performance counters), and then you'll have to escape all % that are already there in configs. So, ${ProgramFiles} should work.

Best regards,
Victor

Hi,

is there anything in log? If not, try to set logging to file in netxmsd.conf and run netxmsd from command line with full debug:

netxmsd.exe -D9

Best regards,
Victor

Hi,

it is a process that started within each desktop session, and can be used to take screenshots from workstations (via "take screenshot" option in node's context menu).

Best regards,
Victor

Hi,

as previously noted, you can select one or more DCIs with "Use this DCI for node status calculation". Server expects such DCI to return numeric value in range 0 .. 4 which indicates status (0 =  normal, 1 = warning, 2= minor, 3 = major, 4 = critical). Most critical status of all status DCIs and active alarms will be taken as current node status.

Best regards,
Victor

Hi,

try to find and kill all netxmsd.exe processes that are running. I also recommend to reboot the OS after installer finishes.

Best regards,
Victor

That's very strange. I just test it just in case, and it works as expected. Let's try to delete all DCIs already created and create new one from scratch to be sure that everything is correct, and then run configuration poll so instance discovery will occur.

Best regards,
Victor

It could be that your agent does not support 64 bit interface counters (they are supported only on Windows Vista and later). Then you have to use Net.Interface.BytesIn.

Best regards,
Victor

Hi,

seems like some file(s) was not updated. Can you please find out what file in bin directory contains string "getKeyByIndex"?

Best regards,
Victor

Hi all!

NetXMS version 1.2.17 is out. Changes since previous release:

- New DCI source: NXSL script executed on server
- Configurable node matching policy for built-in syslog server (controlled by SyslogNodeMatchingPolicy configuration parameter)
- Oracle monitoring subagent improved (bugs fixed, new metrics)
- nxalarm tool supports commands add-comment and get-comments
- Source port number added to events generated from SNMP trap (available via "sourcePort" named parameter)
- Jira link: added possibility to set project's component for issues being created
- ICMP proxy can be set for nodes
- New methods in NXSL classes Node, Interface, and NetObj: setStatusCalculation and setStatusPropagation
- New attributes "slot" and "port" in NXSL class Interface
- Can execute arbitrary NXSL script in context of node, cluster, subnet, or container object from management console
- Improved network topology changes detection
- Added driver for H3C switches
- Management console:
    - Can show alarms for multiple selected objects
    - Fixed non-working ordering in event list in alarm details view
    - Fixed bug with LDAP user system rights
    - Added default search string for LDAP to select all objects: "(objectClass=*)"
    - Added device geolocation tracking and display on map
    - Filter in event processing policy editor
    - Fixed bug with deletion of subnet with corrected IP
    - Added command line option to open specific dashboard after login
- Android console:
   - Fixed issue #661
   - Added node boot time to overview tab
   - Fix bug in notifying connection point not found
   - Fix bug in computing interface expanded list size (removed hardcoded values)
   - Added manage, unmanage, set expected state (up, down, ignore) and find switch port to interface list
   - Fix aesthetic problems in expandable list (graphs and interfaces list)
   - Integration of new support library
   - Target to new API version (20)
- Fixed issues: #51, #91, #324, #359, #409, #532, #542, #571, #563, #590, #593, #613, #617, #624, #626, #629, #632, #635, #638, #639, #641, #642, #649, #658, #663

Best regards,
Victor

That's the historical problem - event parameters for recovery event goes in different order than for activation event. If you want to use single policy you should access them by names instead of positions, like %<dciDescription> instead of %2. You can use the following names: dciId, dciName, dciDescription, thresholdValue, currentValue, instance, isRepeatedEvent.

Best regards,
Victor