Fortinet NSE 7—Enterprise Firewall 7.2 (NSE7_EFW-7.2) - Fortinet

Metadata variables in FortiGate are created to store metadata associated with different FortiGate features. These variables can be used in various configurations and scripts to dynamically replace the variable with its actual value during processing. A: You create metadata variables on FortiGate. They are used to store metadata for FortiGate features and can be called upon in different configurations. D: They can be used as variables in scripts. Metadata variables are utilized within the scripts to dynamically insert values as per the context when the script runs. Fortinet FortiOS Handbook: CLI Reference

To configure a loopback as the BGP source, you need to set the “ebgp-enforce-multihop” and “update-source” parameters in the BGP configuration. The “ebgp-enforce-multihop” allows EBGP connections to neighbor routers that are not directly connected, while “update-source” specifies the IP address that should be used for the BGP session1. Reference := BGP on loopback, Loopback interface, Technical Tip: Configuring EBGP Multihop Load-Balancing, Technical Tip: BGP routes are not installed in routing table with loopback as update source

The access to www.facebook.com is blocked based on the URL Filter configuration. In the exhibit, it shows that the URL “www.facebook.com” is specifically set to “Block” under the URL Filter section1. Reference := Fortigate: How to configure Web Filter function on Fortigate, Web filter | FortiGate / FortiOS 7.0.2 | Fortinet Document Library, FortiGate HTTPS web URL filtering …<br />
<br />
- Fortinet<br />
<br />
- Fortinet Community<br />
…

Virtual MAC Address and Failover<br />
<br />
- The new primary broadcasts Gratuitous ARP packets to notify the network that each virtual MAC is<br />
now reachable through a different switch port.<br />
<br />
- Some high-end switches might not clear their MAC table correctly after a failover - Solution: Force<br />
former primary to shut down all its interfaces for one second when the failover happens (excluding heartbeat and reserved management interfaces): #Config system ha set link-failed-signal enable end<br />
<br />
- This simulates a link failure that clears the related entries from MAC table of the switches.

From the OSPF interface command output, we can conclude that the port3 network has more than<br />
one OSPF router because the Neighbor Count is 2, indicating the presence of another OSPF router besides NGFW-1. Additionally, we can deduce that the interfaces of the OSPF routers match the MTU value configured as 1500, which is necessary for OSPF neighbors to form adjacencies. The MTU mismatch would prevent OSPF from forming a neighbor relationship.<br />
<br />
Reference: Fortinet FortiOS Handbook: OSPF Configuration