Fortinet black logo

online help

VDOM Mapping Section

VDOM Mapping Section

Because a single Stonesoft config could contain multiple configurations for multiple devices, an explicit info of mapping from firewall names (e.g. <fw_cluster> or <fw_single> or <virtual_fw>) to policy package names (<fw_policy>) is required. Otherwise, policy packages that are missing mapping information will fail to apply.

There are two ways to specify the mapping:

  1. 1. Before the conversion, for each firewall-policy pair, manually modify the config by adding <granted_policy_ref> tag with the following format to the end of the config.

  2. If <granted_policy_ref> tags are not found while parsing, it is possible to select them from the dropdown list in VDOM mapping page. (For <master_engine> tag, just choose "Master Engine" from the dropdown list.)

VDOM Mapping Section

Because a single Stonesoft config could contain multiple configurations for multiple devices, an explicit info of mapping from firewall names (e.g. <fw_cluster> or <fw_single> or <virtual_fw>) to policy package names (<fw_policy>) is required. Otherwise, policy packages that are missing mapping information will fail to apply.

There are two ways to specify the mapping:

  1. 1. Before the conversion, for each firewall-policy pair, manually modify the config by adding <granted_policy_ref> tag with the following format to the end of the config.

  2. If <granted_policy_ref> tags are not found while parsing, it is possible to select them from the dropdown list in VDOM mapping page. (For <master_engine> tag, just choose "Master Engine" from the dropdown list.)