![]() Section named "" contains parameters for agent itself. Beginning of a section is denoted by section Parameter = Value form, each parameter should be on its own line. ![]() In 'key = value' format configuration file can contain one or more parameters in Two formats are supported for configuration files and configuration file policies: XML and 'key = value' format. Set as MasterServers to be able to apply other configuration settings from the server.Īfter configuration file change agent should be restarted to apply new changes. Minimal configuration for master configuration file is server address. Master configuration file is the only mandatory file. Provides log file monitoring functionality.Īgent have 3 types of configuration files: master configuration file, additionalĬonfiguration files and Agent Policy configuration files.Provides file management possibilities on agent.Easy upgrade - you can upgrade all agents at once from console.Extensible: you can add new parameters very easy using configuration option like ExternalParameter or by writing your own subagents.:term:`SNMP Trap` proxy: agent can be used as a proxy to get messages from remote SNMP device.:term:`SNMP` proxy: agent can be used as a proxy to reach remote SNMP devices.Proxy functionality: agent can be used as a proxy to reach agents on hosts not directly accessible by |product_name| server.Remote command execution - agents can be used to execute commands on managed systems as a reaction to certain events.TCP instead of UDP is used for communications with agent - this can help in case of slow and poor quality links.More secure: communications between |product_name| server and agent can be encrypted, additional authentication on agent can be configured.Centralized configuration - you can change configuration of agent from management console if needed, you can even store agent configs on |product_name| server.This is optional for installation, but it's installation gives following advantages: |product_name| agent is daemon or service that runs on a :term:`node` to provide additional 13.5 Macros for Event Processingġ4 Data and Network visualisation 14.1 Network maps. 12.8 Working with collected dataġ3 Event processing 13.1 Event Processing Policy. 111 12 Data collection 12.1 How data collection works. ![]() ġ1 Network discovery 111 11.1 Introduction. 10.3 Common object properties 10.4 Object Details. ġ0 Object management 10.1 Object browser. 8.3 Setting default SNMP credentials 8.4 Using ifTable and ifXTable. 7.3 Synchronization between servers 7.4 netxmsd commandline options. Server management 7.1 Configuration file. 6.3 Agent configuration options from server 6.4 Agent registration. 5.2 Basic agent configuration 5.3 Basic server tuning. 4.4 Generic upgrade using source tarball. 4.2 Upgrading on Red Hat, Fedora, CentOS or ScientificLinux 4.3 Upgrading on Windows. Upgrade 4.1 Upgrading on Debian or Ubuntu. 3.6 Generic installation, upgrade and downgrade using source tarball 3.7 Cryptographic verification of installation files. 3.3 Installing on Red Hat, Fedora, CentOS or ScientificLinux. Ĭoncepts 2.1 Architecture overview 2.2 Objects. 1.3 Supported operating systems and databases 1.4 Where to get support. NetXMS Administrator Guide Release 2.0-M2
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |