Technical Tip: In Fabric Overlay Orchestrator setup traffic is denied when shared interfaces are member of a zone
| Description | This article describes the behavior of the Fabric Overlay Orchestrator (FOO) when internal interfaces are part of a zone. |
| Scope | FortiGate v7.4+ and v7.6.0-2. |
| Solution | In this article, the Fabric Overlay Orchestrator (FOO) (Using the Fabric Overlay Orchestrator) is deployed with a Hub FortiGate configured with the 'Automatic' method for policy creation. When 'shared interfaces' on the spokes are members of a zone, the automatic method will create firewall policies using system interfaces and not the system zone.
config system interface
config system zone
config firewall policy
This behavior will lead to a policy failure until a policy is created using the zone instead of the system interface.
id=65308 trace_id=39 func=print_pkt_detail line=5932 msg="vd-root:0 received a packet(proto=1, 10.1.1.1:69->192.168.22.1:2048) tun_id=10.191.19.23 from fabric_vpn_1. type=8, code=0, id=69, seq=0."
This behavior has been changed in FortiOS v7.6.3+, and when an interface is a member of a zone and the interface is selected as 'shared interface', the firewall policies will be created with the zone (known issue ID=1128032 Resolved issues).
config firewall policy
To troubleshoot the automatic configuration creation on a FortiGate device, execute the following CLI commands:
diagnose debug enable
Enable FOO, then stop the debug:
diagnose debug reset
Related documents: |
