Fortinet NSE7_SDW-7.2 Exam With Confidence Using Practice Dumps

VPN event logs record the status of VPN tunnels, such as the establishment, termination, or failure of a tunnel. The output includes the following information:

logid: the log ID number

type: the log type, either traffic or event

subtype: the log subtype, either vpn or ipsec

level: the log level, either error, warning, or notice

vd: the virtual domain name

logdesc: the log description

msg: the log message

action: the log action, such as tunnel-up, tunnel-down, or tunnel-stats

remip: the remote IP address

locip: the local IP address

remport: the remote port number

locport: the local port number

outintf: the outgoing interface name

cookies: the IKE SA cookies

user: the user name

group: the user group name

useralt: the alternative user name

xauthuser: the XAuth user name

authgroup: the XAuth user group name

assignip: the assigned IP address

vpntunnel: the VPN tunnel name

tunnellip: the tunnel loopback IP address

tunnelid: the tunnel ID number

tunneltype: the tunnel type, either ipsec or ssl

duration: the tunnel duration in seconds

sentbyte: the number of bytes sent

rcvdbyte: the number of bytes received

nextstat: the next statistics interval in seconds

advpnsc: the ADVPN shortcut flag, either 0 or 1

Based on the exhibit, the following statement is true:

There is one shortcut tunnel built from master tunnel T_MPLS_0. This means that the VPN tunnel T_MPLS_0 is a master tunnel that can send ADVPN shortcut offers to other spokes, and the VPN tunnel T_MPLS_0_0 is a shortcut tunnel that is built from the master tunnel T_MPLS_01. In the exhibit, the log action for T_MPLS_0 is tunnel-up, and the log action for T_MPLS_0_0 is shortcut-up. The advpnsc flag for T_MPLS_0 is 0, indicating that it is not a shortcut tunnel, while the advpnsc flag for T_MPLS_0_0 is 1, indicating that it is a shortcut tunnel.

According to the SD-WAN 7.2 Study Guide, the SD-WAN overlay template simplifies the configuration of IPsec tunnels in a hub-and-spoke topology. The template defines the following parameters:

type: dynamic for spokes, static for hubs

interface: the WAN interface to use for the IPsec tunnel

network-overlay: enable for spokes, disable for hubs

network-id: a unique identifier for each spoke

auto-discovery-sender: enable for hubs, disable for spokes

auto-discovery-receiver: enable for spokes, disable for hubs

Based on the exhibit, the FortiGate device has the following configuration:

type: dynamic

interface: port1

network-overlay: enable

network-id: 5

auto-discovery-sender: disable

auto-discovery-receiver: enable

Therefore, the FortiGate device is a spoke that establishes dynamic IPsec tunnels to the hub. It also has the network-overlay and auto-discovery-receiver options enabled, which means it can send ADVPN shortcut requests to other spokes when it receives a shortcut offer from the hub