Fortinet black logo

Session-Aware Load Balancing Cluster Guide

Individual FortiAnalyzer settings on each worker

5.2.10
Copy Link
Copy Doc ID 31a89d05-200d-11e9-b6f6-f8bc1258b856:385453
Download PDF

Individual FortiAnalyzer settings on each worker

If the workers are running FortiOS 6.0 or newer, you can use the following command to configure individual workers to send log messages to a different FortiAnalyzer for each worker in your SLBC cluster.

config system vdom-exception

edit 1

set object {log.fortinanalyzer.setting | log.fortianalyzer.override.setting}

set scope {all | inclusive | exclusive)

set vdom <vdom-name> [<vdom-name> ...]

end

where:

object is the name of the configuration object that can be configured independently for all VDOMs. Currently you can control the synchronization of FortiAnalyzer settings

scope determines whether the configuration object can be configured separately for all VDOMs or if some VDOMs share the same configuration. Scope can be:

  • all object configuration is independent for all VDOMs.
  • inclusive object configuration independent for the listed VDOMs. Other VDOMs use the global configuration.
  • exclusive use the global object configuration for the listed VDOMs. Other VDOMs can be configured independently.
  • vdom the name (s) of the VDOMs that are part of the scope.

Individual FortiAnalyzer settings on each worker

If the workers are running FortiOS 6.0 or newer, you can use the following command to configure individual workers to send log messages to a different FortiAnalyzer for each worker in your SLBC cluster.

config system vdom-exception

edit 1

set object {log.fortinanalyzer.setting | log.fortianalyzer.override.setting}

set scope {all | inclusive | exclusive)

set vdom <vdom-name> [<vdom-name> ...]

end

where:

object is the name of the configuration object that can be configured independently for all VDOMs. Currently you can control the synchronization of FortiAnalyzer settings

scope determines whether the configuration object can be configured separately for all VDOMs or if some VDOMs share the same configuration. Scope can be:

  • all object configuration is independent for all VDOMs.
  • inclusive object configuration independent for the listed VDOMs. Other VDOMs use the global configuration.
  • exclusive use the global object configuration for the listed VDOMs. Other VDOMs can be configured independently.
  • vdom the name (s) of the VDOMs that are part of the scope.