NetXMS Support Forum

All this time I was thinking about possible causes - the only thing I can imagine is that somewhere this packages are blocked by firewall.

Most probably incorrect port.

The default setting is as follows:

• When [Off] is selected for "SSL"
  
  
  
  • If [Active Directory] or [Other LDAP Server] is selected, 389.
  • If [Active Directory Global Catalog] is selected, 3268.
• When [On (Full Validation: CA + Certificate)] or [On (Certificate Only, CA not validated)] is selected for "SSL"
  
  
  
  • If [Active Directory] or [Other LDAP Server] is selected, 636.
  • If [Active Directory Global Catalog] is selected, 3269.

Originally taken

Hi,

I have added some updates to LDAP section: https://www.netxms.org/documentation/adminguide/user-management.html#integration-with-ldap

Please check. Comments and corrections are welcome.

Thank you!

Hi.

There is information about ping subagent:
https://www.netxms.org/documentation/adminguide/subagents.html#ping

It is loaded with "SubAgent = ping.nsm" line added into agent configuration file. There is some information about agent configuration: https://www.netxms.org/documentation/adminguide/agent-management.html

From the next release ping response times can be collected without subagent: https://www.radensolutions.com/chiliproject/issues/511

About sending email notifications can be found there: http://wiki.netxms.org/wiki/How_to_send_e-mail_notification_when_disk_space_is_low

In configuration I see 1 mistake: no search filter. If all should be taken then filter should be "(objectClass=*)". In next release this value will be set by default if LdapSearchFilter will be empty.

It looks like your server is built without LDAP support. Please enable debug level 4, run command "ldapsync" in server console and provide output.

Thank you for advice! I'll add information about required fields, and some default configuration to documentation.

Hi,

There were some problems with file manager in version 1.2.15. Your may be connected with this bug: https://www.radensolutions.com/chiliproject/issues/618. Bug fix is included in version 1.2.16. Please try to update NetXMS to version 1.2.16.

Hi.

What exactly problems you have? You cannot login with synchronized user or you have problems with rights on objects or initial login to get users from LDAP goes with problems?

Also in your Previous config I can't see LdapUserClass and LdapMappingName. They are required for configuration.

LdapUserClass  - describes what class of objects will be treated as a users.
LdapMappingName - this is parameter that will be used as a login name.

In case of successful synchronization you will see something like:
"LDAPConnection::syncUsers(): User added: dn: %s, login name: %s, full name: %s, description: %s"

Also synchronized users will be seen on UI with all other NetXMS users.

Yes

There is no documentation bout it.

Short description:
It is coma-separated list of hosts, that are pinged by NetXMS server and if none of the hosts have responded, server considers that connection with network is lost and generates specific event.

It should look like this:

Agent Configuration Files on Server:

• Assignment is Rule based (In filter script only variables $1 - $5 are possible (changed in admin guide))
• Config download from server is each time the agent starts (if option '-M servername')
• When config is found on server, local Master config is overwritten, if not existing Master config is used
• Works with Master config
• Do not required initial config(can be started without config), but in this case agent will fail if nothing will be returned from server

Agent Policies:

• Not possible for bootstrap agent
• Also possible via proxy
• Assignment is only direct to nodes, not rule based
• Can be in XML or 'key = value' format
• Settings from different policies will be merged at agent startup
• SubAgent config sections also possible
• changed policies must be reinstalled on nodes (in console) and need agent restart
• At minimum the server connection parameters must be in Master config
• Works with Additional configuration files(policies)
• If policy and master config have same parameter that can be set only once like(MasterServers or LogFile), then policy will overwrite master config configuration
• If policy and master config have same parameter that can be set multiple times like(Target for PING subagent or Query for DBQUERY), then policy will merge lists of configs

I'll find appropriate section in documentation and will add this information.

Hi.

I didn't meant that config is updated just once. I just wanted to describe a possibility to get initial config(that is required in case if you will decide to use Agent Policies). If on agent start you added parameter -M <addr> agent will try first to get config from server and in case of fail it will start with the old one.

Documentation updated:
https://www.netxms.org/documentation/adminguide/agent-management.html#agent-configuration-files-on-server

About questions:
* Is it also possible for SubAgent Config Sections?
Yes. It will look like this:
<config>
   <agent>
      <MasterServers>127.0.0.1</MasterServers>
      <SubAgent>netsvc.nsm</SubAgent>
      <SubAgent>dbquery.nsm</SubAgent>
      <SubAgent>filemgr.nsm</SubAgent>
   </agent>
   <DBQUERY>
      <Database>id=myDB;driver=mysql.ddr;server=127.0.0.1;login=netxms;password=xxxxx;dbname=netxms</Database>
      <Query>dbquery1:myDB:60:SELECT name FROM images</Query>
      <ConfigurableQuery>dbquery2:myDB:Comment in param :SELECT name FROM images WHERE name like ?</ConfigurableQuery>
      <ConfigurableQuery>byID:myDB:Comment in param :SELECT name FROM users WHERE id=?</ConfigurableQuery>

   </DBQUERY>      
   <filemgr>
      <RootFolder>/</RootFolder>
   </filemgr>
</config>

* Is it correct, you need to restart agent manually after reinstall changed agent policy ?
Yes.

Sorry I have no answers on other your questions. They can be answered by Victor.

It is possible to have initial config in Agent Configuration Files on Server. Agent Config file received from server is saved as agent config. And next time agent may be started without requesting config. And all non initial(for me it is all except master server) can be applied through policies.

To do any manipulations with files on a node it is required to load filemng subagent and configure accessible paths. https://www.netxms.org/documentation/adminguide/file-management.html

The only 2 exceptions are agent update and upload of file to default path(When destination path is empty). Upload to default path is broken in version 1.2.15.

Bug fixed. Will be available in repack or in next release.

Забыли добавить. Будет исправлено.