Fortinet black logo

Version:


Table of Contents

6.4.4
Download PDF
Copy Link

What’s new

This section identifies new features and enhancements available with SD-WAN Orchestrator MEA 6.4.1.r5.

For information about what's new in FortiManager 6.4, see the FortiManager 6.4 New Features Guide.

Non-standard HTTPS port support

SD-WAN Orchestrator supports FortiGates with non-standard HTTPS ports.

Version standardization

SD-WAN Orchestrator versions have been standardized to include a revision number. Previously the version included the build number, for example, 6.4.1-build0330-201113. Now the version includes a revision number and the build number, for example 6.4.1.r5-build0334-201222.

To view the SD-WAN Orchestrator version in the Root ADOM, go to SD-WAN Orchestrator > Maintenance > Upgrade.

Blackhole routes

You can add a blackhole static route to FortiGates for all intranet IP Pools. The blackhole static route entries will be deployed to FortiGate automatically by SD-WAN Orchestrator after an IP pool is created. This prevents intranet prefixes from being added to the route when the routes are resolved via underlay WAN ports in BGP.

To upgrade the configuration from 6.4.1.r4 to 6.4.1.r5:

When the LAN port is configured with a custom subnet instead of auto assigned, create a new IP pool or modify the existing IP pool to include the LAN custom subnet. See also Address group change and upgrade.

Dual hub load mode

When creating a business rule, the option Dual Hub Load Mode is added to control the behavior of the business rule in dual hub scenarios.

ACTIVE_PASSIVE: The business rule is split and deployed to FortiGate as two rules:

  • Primary hub: This includes all overlay links to the primary hub as priority members.
  • Secondary hub: This includes all overlay links to the secondary hub as priority members. This is the default option from 6.4.1.r5 builds.

ACTIVE_ACTIVE: The business rule will be deployed to FortiGate as one rule.

The priority members will include all overlay links between the edge and the hubs. This behavior is the same as 6.4.1.r4 and previous builds.

This option is only available when the Group Type is Overlay or All.

What’s new

This section identifies new features and enhancements available with SD-WAN Orchestrator MEA 6.4.1.r5.

For information about what's new in FortiManager 6.4, see the FortiManager 6.4 New Features Guide.

Non-standard HTTPS port support

SD-WAN Orchestrator supports FortiGates with non-standard HTTPS ports.

Version standardization

SD-WAN Orchestrator versions have been standardized to include a revision number. Previously the version included the build number, for example, 6.4.1-build0330-201113. Now the version includes a revision number and the build number, for example 6.4.1.r5-build0334-201222.

To view the SD-WAN Orchestrator version in the Root ADOM, go to SD-WAN Orchestrator > Maintenance > Upgrade.

Blackhole routes

You can add a blackhole static route to FortiGates for all intranet IP Pools. The blackhole static route entries will be deployed to FortiGate automatically by SD-WAN Orchestrator after an IP pool is created. This prevents intranet prefixes from being added to the route when the routes are resolved via underlay WAN ports in BGP.

To upgrade the configuration from 6.4.1.r4 to 6.4.1.r5:

When the LAN port is configured with a custom subnet instead of auto assigned, create a new IP pool or modify the existing IP pool to include the LAN custom subnet. See also Address group change and upgrade.

Dual hub load mode

When creating a business rule, the option Dual Hub Load Mode is added to control the behavior of the business rule in dual hub scenarios.

ACTIVE_PASSIVE: The business rule is split and deployed to FortiGate as two rules:

  • Primary hub: This includes all overlay links to the primary hub as priority members.
  • Secondary hub: This includes all overlay links to the secondary hub as priority members. This is the default option from 6.4.1.r5 builds.

ACTIVE_ACTIVE: The business rule will be deployed to FortiGate as one rule.

The priority members will include all overlay links between the edge and the hubs. This behavior is the same as 6.4.1.r4 and previous builds.

This option is only available when the Group Type is Overlay or All.