uc_switchTo Make Configuration Active
| Goal | Syntax | Options |
|---|---|---|
| Activate LogLogic® Universal Collector | uc_switchTo -ucc <nameofconf> | |
|
Simulate the change of the active LogLogic® Universal Collector configuration. Displays possible errors and warnings in the stored configuration and changes between active and stored configurations. |
uc_switchTo -ucc <nameofconf> | -dryrun |
| Get help on the Switch command | uc_switchTo | -h |
| Indicate the port to connect to the LogLogic® Universal Collector | uc_switchTo -ucc <nameofconf> | -p <portnumber> |
| Get information on the Switch version | uc_switchTo | -v |
| Activate LogLogic® Universal Collector Configuration and display verbose information | uc_switchTo -ucc <nameofconf> | -vb |
Switching from One Configuration to Another
It is possible to switch from one configuration to another one.
To apply a new configuration, the command is:
uc_switchTo.bat -ucc {myconf}(under Windows)
uc_switchTo -ucc {myconf} (under RHEL, SUSE)
In case of an error, the configuration switch is interrupted and the configuration error is logged in the uc.log file.
Example: You want to switch from the current configuration ‘conf1’ to ‘conf2’.
Enter the command to apply a new configuration to the LogLogic® Universal Collector by using the CLI located in <INSTALL_DIR>/tools.
uc_switchTo.bat -ucc c:\tmp\conf2
The current configuration is now ‘conf2’.
Checking the Impacted Processes
It is possible to check which log sources and Forwarding connections are impacted by the new configuration - without having to apply it.
To check the impact on the processes:
-dryrun gives information on the switch or the update of configurations
-dryrun -vb gives detailed information on the switch or the update of configurations
Example: You want to check the impacted process during a switch of configurations.
Enter the following command:
uc_switchTo.bat -ucc {uc.conf.file}.ucc -dryrun -vb
You can obtain something like this:
3 configuration files checked
1 Log Source config updated
1 SYSLOG Log Source config updated
2 Forwarding connection updated (1 created, 1 removed)
1 LS Config Updated
============================================================
syslog.1 UPDATE
2 Forwarding Config Updated
============================================================
Lmi2 REMOVE
Lmi CREATE
WARNING data might not have been collected during the switch configuration operation, the log sources [syslog.1] may have been impacted
WARNING data contained in Forwarding connection spool of [MyCuteLmi2] may have been lost if remote Forwarding connection was not available
SUCCESS-[conf3] DryRun mode : No change has been applied to the running configuration
Limitations
During a switch process, some limitations might occur.
- First case--If you remove or update a Syslog Log Source, you might stop the flow and lose some data.
- Second case--If you switch from a Forwarding connection to another one for a given Syslog Log Source, you might lose a few events. This behavior is rare though.
- Third case--If you remove a Forwarding connection or modify the values of the buffer size while the connection to the Forwarding connection is not available (for example, network failure), the Forwarding connection buffer will try to empty itself by sending the remaining data to the Forwarding connection. This will cause the loss of the buffer content during the time-out.