Fortinet Document Library

Version:

Version:

Version:

Version:

Version:


Table of Contents

FortiGate-7000 Release Notes

Configure FortiGate-7000 FPMs to send logs to different syslog servers

Previous versions of FortiGate-7000 allowed you to us the VDOM exception configuration to:

  • Set up each FPM in a FortiGate-7000 to send log messages to different FortiAnalyzers.
  • Set up individual VDOMs on each FPM to send log messages to different FortiAnalyzers.

FortiGate-7000 for FortiOS 6.2.4 now supports the same functionality for syslog servers.

Note

This configuration is only supported for fortianalyzer and syslogd and not for fortianalyzer2, fortianalyzer3, fortianalyzer-cloud, syslogd2, syslogd3, and syslogd4.

Note

When you have completed the VDOM exception configurations described in this section, the FIMs and FPMs will have different logging configurations. In addition, some configurations that are affected by the logging configuration (for example, DLP content archiving) will be different on some modules. Because of this, using the various methods available to check for synchronization between modules will show that the configurations of the modules are not synchronized. The FortiGate-7000 will continue to operate normally even with these configuration synchronization issues.

Configure FortiGate-7000 FPMs to send logs to different syslog servers

Previous versions of FortiGate-7000 allowed you to us the VDOM exception configuration to:

  • Set up each FPM in a FortiGate-7000 to send log messages to different FortiAnalyzers.
  • Set up individual VDOMs on each FPM to send log messages to different FortiAnalyzers.

FortiGate-7000 for FortiOS 6.2.4 now supports the same functionality for syslog servers.

Note

This configuration is only supported for fortianalyzer and syslogd and not for fortianalyzer2, fortianalyzer3, fortianalyzer-cloud, syslogd2, syslogd3, and syslogd4.

Note

When you have completed the VDOM exception configurations described in this section, the FIMs and FPMs will have different logging configurations. In addition, some configurations that are affected by the logging configuration (for example, DLP content archiving) will be different on some modules. Because of this, using the various methods available to check for synchronization between modules will show that the configurations of the modules are not synchronized. The FortiGate-7000 will continue to operate normally even with these configuration synchronization issues.