Configuration File
etc/filesync.xml
Description
By default files and directories specified by the etc/filesync
.xml located on the system hosting the BVE server pushed out to synchronized on all DGEs and DGE extensions. Any new configuration files or changes made in these files and directories on the central BVE server are automatically distributed to all Traverse components within minutes. If a remote DGE or DGE-x is down when a change is made, it will update its configuration files when it reconnects to the BVE. This feature can be disabled by unchecking the File Synchronization Server option using the Traverse Service Controller.
Note: By default, customizations made in the /plugin
directory of DGEs or DGE extensions, are not overwritten. This allows you to maintain, if you wish, separate plugin customizations for each DGE or DGE extension, unaffected by file synchronization.
Reloading Configuration Files
IMPORTANT: Even though the configuration files are distributed automatically, you must reload the configuration files manually. This is done to ensure that an invalid configuration file does not impact a running system.
In order to reload configuration files or new device signatures, you can either reload the configuration files using the Web Application or else run a command line utility to reload.
Reload using Web UI
superuser
and navigate to the Superuser > Health tab.This page automatically displays which DGE or DGE extension has updated configuration files and need to be reloaded.
Reload using Command Line Utility
Run utils/adminUtil.pl
with the following parameters:
adminUtil.pl --action=reload --address=host,host --username=xyz --password=abc
You can specify the --help
option for the different options.
The following files will be reloaded:
etc/licenseKey.xml
etc/typedef/
and plugin/monitors/
etc/messages/
and plugin/messages/
etc/reports/
etc/actions/
etc/profiles/
and plugin/profiles/
lib/mibs
and plugin/mibs
for trapsplugin/actions
for action profiles and Event Manager