NetXMS Support Forum

Hi,

currently you cannot do that. Feel free to register feature request

Best regards,
Victor

Hi,

you can use nxget command line tool to get any list or table. For example, to get interface list:


C:\Source\NetXMS\release>nxget -e0 -l 10.5.0.162 Net.InterfaceList
1 127.0.0.1/8 24 000000000000 lo0
2 10.5.0.162/24 6 000000000000 bge0


to get file system table:


C:\Source\NetXMS\release>nxget -e0 -T 10.5.0.253 FileSystem.Volumes
MOUNTPOINT       |VOLUME           |LABEL            |FSTYPE           |SIZE.TOTAL       |SIZE.FREE        |SIZE.FREE.PCT    |SIZE.AVAIL    |SIZE.AVAIL.PCT   |SIZE.USED        |SIZE.USED.PCT    |
C:\              |\\?\Volume{39e06104-63ef-11dd-92a4-806d6172696f}\ |                 |NTFS             |40015953920      |33852870656      |84.598435        |33852870656      |84.598435        |6163083264       |15.401565        |
D:\              |\\?\Volume{2ae1c26a-6dc5-11dd-8464-806d6172696f}\ |                 |                 |0                |0
        |0                |0                |0                |0                |0                |
A:\              |\\?\Volume{2ae1c26b-6dc5-11dd-8464-9be8208dfb96}\ |                 |                 |0                |0
        |0                |0                |0                |0                |0                |


There are two useful lists: Agent.SupportedLists and Agent.SupportedTables to get list of all lists and tables supported by agent.

Best regards,
Victor

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