Fortinet black logo
6.4.0

Overview

Overview

FortiMail VM looks for three configuration files to apply:

  • mode: CLI command that has the system mode configured (i.e. Gateway, Server, or Transparent).
  • It is recommended to set the mode before any configuration, as setting the mode effectively factory resets the system.

    Note that some configuration options are only available in certain modes.

  • config: Any other CLI configuration that apply to the system after the mode is set.
  • license: The VM license file.

Any combination of these configuration files (or none) may be provided.

The license file is a typical VM license (.lic) file. Below are some samples of what might be in the mode and config files:

The mode text file:

config system global

set operation-mode server

end

The config text file:

config system interface

edit port1

set ip 172.20.140.250/24

set allowaccess https ping ssh telnet

next

end

config system dns

set primary 8.8.8.8

set secondary 4.4.4.4

end

config system route

edit 1

set gateway 172.20.140.2

next

end

config system admin

edit fmltest

set access-profile super_admin_prof

set password 123456

next

end

Bootup the instance

To bootup a FortiMail VM instance, OpenStack can use something similar to the following command (in this example, using nova boot):

nova boot --flavor FML_small --image fml_image --file license=FEVM010000041191.lic --file config=fmlinit.txt --file mode=fmlmode.txt fml_instance

Note

In this example the system will reboot twice: after loading mode and then after loading a new license.

Without OpenStack

Without OpenStack you would need to place all necessary configuration files in the Windows content directory. For example:

  1. Place the configuration files in:
  2. openstack/content/0000 (for example the "mode" file)

    openstack/content/0001 (for example the "config" file)

    openstack/content/0002 (for example the 'license' file)

    Note

    Any combination of these may be present.

  3. Create or update the openstack/latest/meta_data.json file to point to these files:
  4. {"files": [

    {"path": "mode", "content_path": "/content/0000"},

    {"path": "config", "content_path": "/content/0001"},

    {"path": "license", "content_path": "/content/0002"}

    ]}

Overview

FortiMail VM looks for three configuration files to apply:

  • mode: CLI command that has the system mode configured (i.e. Gateway, Server, or Transparent).
  • It is recommended to set the mode before any configuration, as setting the mode effectively factory resets the system.

    Note that some configuration options are only available in certain modes.

  • config: Any other CLI configuration that apply to the system after the mode is set.
  • license: The VM license file.

Any combination of these configuration files (or none) may be provided.

The license file is a typical VM license (.lic) file. Below are some samples of what might be in the mode and config files:

The mode text file:

config system global

set operation-mode server

end

The config text file:

config system interface

edit port1

set ip 172.20.140.250/24

set allowaccess https ping ssh telnet

next

end

config system dns

set primary 8.8.8.8

set secondary 4.4.4.4

end

config system route

edit 1

set gateway 172.20.140.2

next

end

config system admin

edit fmltest

set access-profile super_admin_prof

set password 123456

next

end

Bootup the instance

To bootup a FortiMail VM instance, OpenStack can use something similar to the following command (in this example, using nova boot):

nova boot --flavor FML_small --image fml_image --file license=FEVM010000041191.lic --file config=fmlinit.txt --file mode=fmlmode.txt fml_instance

Note

In this example the system will reboot twice: after loading mode and then after loading a new license.

Without OpenStack

Without OpenStack you would need to place all necessary configuration files in the Windows content directory. For example:

  1. Place the configuration files in:
  2. openstack/content/0000 (for example the "mode" file)

    openstack/content/0001 (for example the "config" file)

    openstack/content/0002 (for example the 'license' file)

    Note

    Any combination of these may be present.

  3. Create or update the openstack/latest/meta_data.json file to point to these files:
  4. {"files": [

    {"path": "mode", "content_path": "/content/0000"},

    {"path": "config", "content_path": "/content/0001"},

    {"path": "license", "content_path": "/content/0002"}

    ]}