They should be are in the "contrib" folder, but looks like latest release was packaged incorrectly. I've fixed it in CVS, so next release will be fine. But as for now — I put sample configs on the web so you can download them: http://www.alk.lv/netxmsd.conf-dist http://www.alk.lv/nxagentd.conf-dist http://www.alk.lv/nxhttpd.conf-dist

Links was not fixed during forum migration. I've updated post. New link is: https://www.netxms.org/forum/index.php/topic,50.html

Hello! Unfortunatelly, currently web GUI offer only some read-only functionality. For NetXMS configuration you still need Windows console application - nxcon.exe (it also runs on Linux under Wine). We are working on both full-functional web interface and portable (wxWidgets-based) console, but they are not ready yet. Best regards, Victor

Hello! First, I recommend you to look at user's manual - although it's not complete, you may found some useful information there (at least data collection part is complete). Also, I recommend you to install agents on your servers - it will simplify configuration. For sample step-by-step configuration of collecting parameter from server and setting up alerts you can take a look at https://www.netxms.org/documentation/confexample/ (a bit outdated, but still valid). You can found list and short description of all parameters provides by agents here: https://www.netxms.org/documentation/common_parameters.html . And feel free to ask if you will have any problems (but remember - more specific questions can be answered faster and easier  ) Best regards, Victor

Hello! NetXMS server polls for configuration changes (configuration polls) not instantly, but with interval (1 hour by default). If you just install agent on host, NetXMS server will know about it when next configuration poll occurs. You can also manually run configuration poll by right-clicking host object and selecting Poll -> Configuration. Best regards, Victor

Hello! We plan this feature (custom maps) for the next major development branch. However, with current version you can create custom map, but this is a bit tricky. Below is an instruction: Create new container object under "All Services", and look at container's object id. Stop NetXMS server. Perform the following SQL query in NetXMS database UPDATE maps SET root_object_id=<place container object id here> WHERE map_id=1 Start server again. After that, all objects added to container created in step one will be shown on map. With upcoming 0.2.19, you also will be able to create links between objects. And remember, it's just a hack, not a complete custom map implementation! Best regards, Victor

It's not possible now. I see that this is a common requirement (along with possibility to create calculated DCIs), so I definitely will implement this in one of the future versions. Best regards, Victor

Found the solution :). Correct syntax: ..\..\bin\nxmibc -d . -z Geert

Unfortunately, it's impossible now. I have a plans (and pending requests) for implementing "table" DCIs, which will be suitable for this task. Most likely it will not be in upcoming 0.2.19, but I hope that I will be able to implement it in 0.2.20. Best regards, Victor

Unfortunately not. However, I can add it in 0.2.19 - there are no much work, just nobody asking about such feature before. Best regards, Victor

Hello! "Calculate status as" determines how object's status should be calculated based on child objects statuses. For objects without child objects (like conditions) it has no meaning. "Propagate status as" determines how object present it's status to parent object(s). For example, you have a switch with various interfaces. Normally, when interface goes down, it's status changes to CRITICAL, and status of entire node object changes to CRITICAL (and so on up to the root). However, if you have not very important interfaces and wish that node status changes not to CRITICAL, but to WARNING when this interface  goes down, you can change "Propagate status as" property of interface object so it will propagate it's CRITICAL status as WARNING. Best regards, Victor

@cme said in CPU-Usage of more than one PC via Script: Second question: I have the event SYS_THRESHOLD_REACHED let's say for this CPU monitoring... If I further want to watch the DiskUsage.. (if it's above 90%) Do I have to create another new event like this or use another one? So do I have to create such a event for every "thing" that is watched? Example: CPU -> CPU_TOO_HIGH -> action: email "CPU of PC123 too high.." Disk -> DISK_FULL -> action: "Disk of PC123 too full.." .. Yes, it's the main idea - you create different events for different thresholds, so you can process them differently. After NetXMS installation you already have some example events for threshold violations - their names starts with DC_ prefix. Also, you may create different events for different thresholds (for example HIGH_CPU_USAGE and LOW_DISK_SPACE), but handle them identically - for example, write one rule in event processing policy: add both HIGH_CPU_USAGE and LOW_DISK_SPACE to event field; in alarm generation field as alarm text use %m macro, which will expand to actual event's text. With this approach, you can have relatively simple event processing policy but use meaningful texts in alarms and messages.

Sorry for the false alarm. The error was produced by incompatibility of ASCII files between Unix and DOS. Using a tool such as Winzip to unpack source.tgz and make sure to handle CR/LF between Unix and DOS properly.

Default login is admin and password is netxms (all small letters). Btw, this is mentioned in Installation Guide on page 20  Best regards, Victor

Hello! Did you mean that you wish to view history of events for particular node? For now, you can only view last few thousands of event log without filtering. However, if you only need the event history occasionally, you can do direct requests against SQL database (table event_log). In the future, we plan to implement filters in event log so you will be able to see event history for specific node from console. Best regards, Victor

nxmibc expects that all mib files have .txt extension. Most likely you have something different.

thx

https://www.netxms.org/cgi-bin/mwf/topic_show.pl?pid=201#pid201 dabi ne floodit`

Hello! You have found a new bug, just introduced in 0.2.17 Problem is with malformed SQL request - you can see it in the log if you enable logging of failed SQL queries by adding LogFailedSQLQueries = yes to netxmsd.conf. I'll fix it today. Looks like 0.2.17 is one of the buggiest versions we ever release... Best regards, Victor P.S. Normally, server commits all unsaved configuration changes to database periodically - every 60 seconds by default. All unsaved changes also will be commited on shutdown.

Hello! Having NetXMS agents on monitored systems is recommended, but not required. If you only interested to now if particular host is alive or not (responds to ping) and/or that particular services (like ssh or http) are alive, you don't need agent on that host. But if you wish to get more information (like CPU usage or status of particular process) you will need an agent on monitored system (you may also use SNMP agent and collect data via SNMP). Best regards, Victor