Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Fortinet Certified Solution Specialist: Enterprise Firewall & Secure Networking 7.6 Architect · Fortinet
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
When peering over FGSP, by default, the FortiGate devices or FGCP clusters, share information over layer 3 between the interfaces that are configured with peer IP addresses. You can also specify the interfaces used to synchronize sessions in layer 2 instead of layer 3 using the session-sync-dev setting. When a session synchronization interface is configured and FGSP peers are directly connected on this interface, then session synchronization is done over layer 2, only falling back to layer 3 if the session synchronization interface becomes unavailable. WHAT IS UNCLAR? By def. both config and sessions are syncing via L3. If you enalbe session-syn-dev <interface> command you CREATE DEDICATED L2 connectoins for sessions sync only!! and CONFIG sync still remain in old L3 ( Heratbeat interface). exmple: config system ha set session-sync-dev port10 port12 end So if both port10 and port12 failed, session sync "return back" from L2 to original HeartBeat L3 interface. Only B is correct answer.
Session synchronization (FGSP): By default, it occurs at Layer 3. It can be moved to Layer 2 using the set session-sync-dev command, as shown in the configuration. Configuration synchronization (FGCP): It is a separate feature, independent of FGSP. By default, it operates at Layer 2 and uses the hbdev command. It can be moved to Layer 3 using the unicast-peers command, which is not configured here. Since the configuration in the exhibit moves session synchronization to Layer 2 using the set session-sync-dev command, and configuration synchronization remains at Layer 2 by default, both session and configuration synchronization will now occur at Layer 2. Correct Answer: D. To have both sessions and configuration synchronization in layer 2
Refer to study guide page 113 You can also specify the interfaces used to synchronize sessions in layer 2 INSTEAd of layer 3 using the session-sync-dev setting. When a session synchronization interface is configured and FGSP peers are directly connected on this interface, then session synchronization is done over layer 2, only falling back to layer 3 if the session synchronization interface becomes unavailable.