index int64 0 4.08k | text stringlengths 34 4.9k ⌀ | url stringclasses 38
values |
|---|---|---|
3,155 | System
next
end
The SNMP configuration is synchronized to all cluster units.
To get CPU, memory, and network usage information from the SNMP manager for each cluster unit
using the reserved management IP addresses:
1. Connect to the SNMP manager CLI.
2. Get resource usage information for the primary unit using the MIB ... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,156 | System
NTP over reserved management interfaces
When NTP is enabled in an HA cluster, the primary unit will always be the unit to contact the NTP server and synchronize
system time to the secondary units over the HA heartbeat interface. However, in the event that the primary should
contact the NTP server over the HA res... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,157 | System
To add an in-band management IP address to port23 with HTTPS, SSH, and SNMP access:
config system interface
edit port23
set management-ip 172.25.12.5/24
set allowaccess https ssh snmp
next
end
Upgrading FortiGates in an HA cluster
You can upgrade the firmware on an HA cluster in the same way as on a standalone F... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,158 | System
To enable interrupted upgrade:
config system ha
set upgrade-mode simultaneous
end
Distributed HA clusters
FGCP HA supports cluster units installed in different physical locations to achieve geo-redundancy. This may be
desirable in large enterprises that deploy multiple data centers and network infrastructure to ... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,159 | System
A longer interval and threshold can lead to slower failover time, and a shorter interval and threshold may lead to false
positives. Therefore, these settings should be fine-tuned based on individual network scenarios. Additional options
include:
l Using multiple heartbeat interfaces and different link paths for ... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,160 | System
To configure the example:
1. Disconnect the physical connections between Site 1 and Site 2:
l Disconnect the cable on Site 1 FSW-1 port 12.
l Disconnect the cable on Site 1 FSW-2 port 10.
2. Configure Site 1:
a. On the FortiGate, go to WiFi & Switch Controller > FortiLink Interface and configure FortiLink:
b. Go... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,161 | System
d. Assign the native VLAN of the switch ports that are connected to the heartbeat ports to the created VLAN. Each
HA heartbeat should be in its own VLAN.
i. Go to WiFi & Switch Controller > FortiSwitch Ports.
ii. In the Native VLAN column for the heartbeat port that is connected to FSW-1, click the edit icon and... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,162 | System
l Connect a cable from Site 1 FSW-1 port 12 to Site 2 FSW-1 port 22.
l Connect a cable from Site 1 FSW-2 port 10 to Site 2 FSW-2 port 20.
6. On all of the FortiSwitches, configure the auto-isl-port-group. The group must match on both sides.
a. Site 1 FSW-1:
Set members to the port that is connected to Site 2 FSW... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,163 | System
To test the configuration to confirm what happens when there is a failover:
1. On both PC-1 and PC-2, access the internet and monitor traffic. The traffic should be going through the primary
FortiGate.
2. Perform a continuous ping to an outside IP address, then reboot any one of the FortiSwitches.
Traffic from b... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,164 | System
Examples
The examples use the following topology:
Traffic between hardware switches
When using Hardware switch in HA environment, a client device connected to the hardware switch on the primary
FortiGate can communicate with client devices connected to the hardware switch on secondary FortiGates as long as
there... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,165 | System
set allowaccess ping ssh http https
next
end
After configuring the hardware switches, PC1 and PC2 can now communicate with each other.
Traffic passes through FortiGate
If client device needs to send traffic through the FortiGate, additional firewall configuration on the FortiGate is required.
All traffic from th... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,166 | System
config router static
edit 1
set device Hardware-SW2
set gateway 172.16.200.254
next
end
Traffic from PC1 and PC2 can now reach destinations outside of the FortiGate cluster.
VDOM exceptions
VDOM exceptions are settings that can be selected for specific VDOMs or all VDOMs that are not synchronized to other
HA mem... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,167 | System
l all: Configure the object independently on all VDOMs.
l inclusive: Configure the object independently only on the specified
VDOMs.
l exclusive: Configure the object independently on all of the VDOMs that
are not specified.
vdom The names of the VDOMs that are included or excluded.
Objects
The following setting... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,168 | System
Configure a different syslog server on a secondary HA device
To configure the primary HA device:
1. Configure a global syslog server:
config global
config log syslog setting
set status enable
set server 172.16.200.44
set facility local6
set format default
end
end
2. Set up a VDOM exception to enable setting the ... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,169 | System
end
end
2. After the primary and secondary device synchronize, generate logs on the secondary device.
To confirm that logs are been sent to the syslog server configured on the secondary device:
1. On the primary device, retrieve the following packet capture from the secondary device's syslog server:
# diagnose s... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,170 | System
Configure a different syslog server in the root VDOM on a secondary HA device
To configure the primary HA device:
1. Configure a global syslog server:
config global
config log syslog setting
set status enable
set server 172.16.200.44
set facility local6
set format default
end
end
2. Set up a VDOM exception to en... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,171 | System
set server 172.16.200.44
set facility local6
set format default
end
end
After syslog-override is enabled, an override syslog server must be configured, as logs will not be sent to the global
syslog server.
To configure the secondary HA device:
1. Configure an override syslog server in the root VDOM:
config root
... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,172 | System
Routing NetFlow data over the HA management interface
In an HA environment, the ha-direct option allows data from services such as syslog, FortiAnalyzer, SNMP, and
NetFlow to be routed over the outgoing interface.
The following example shows how NetFlow data can be routed over the HA management interface mgmt1.
... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,173 | System
set override enable
set priority 100
set ha-direct enable
end
(global) # config system interface
edit "mgmt1"
set ip 10.6.30.112 255.255.255.0
set allowaccess ping https ssh http telnet fgfm
set type physical
set dedicated-to management
set role lan
set snmp-index 1
next
end
3. On the primary unit (FortiGate A),... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,174 | System
Force HA failover for testing and demonstrations
This command should only be used for testing, troubleshooting, maintenance, and
demonstrations.
Do not use it in a live production environment outside of an active maintenance window.
HA failover can be forced on an HA primary device. The device will stay in a fai... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,175 | System
FGT3HD3914800153(updated 3 seconds ago): in-sync
System Usage stats:
FGT3HD3914800069(updated 4 seconds ago):
sessions=5, average-cpu-user/nice/system/idle=0%/0%/0%/100%, memory=30%
FGT3HD3914800153(updated 3 seconds ago):
sessions=41, average-cpu-user/nice/system/idle=0%/0%/0%/99%, memory=30%
HBDEV stats:
FGT3H... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,176 | System
sessions=0, average-cpu-user/nice/system/idle=0%/0%/0%/100%, memory=30%
FGT3HD3914800153(updated 2 seconds ago):
sessions=38, average-cpu-user/nice/system/idle=0%/0%/0%/100%, memory=30%
HBDEV stats:
FGT3HD3914800069(updated 3 seconds ago):
port3: physical/1000auto, up, rx-bytes/packets/dropped/errors=16302442/43... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,177 | System
In this example, FGT_A and FGT_B are in HA a-p mode with two virtual clusters. Two primaries exist on different
FortiGate units. PC1 eth1 can access PC5 eth1 through VDOM1, and PC1 eth2 can access PC5 eth2 through VDOM2.
On PC5, to listen for an SCTP connection:
sctp_darn -H 172.16.200.55 -B 172.17.200.55 -P 250... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,178 | System
Session states before failover
When HA is working, the ICCP session information is stored in the HA session cache on the secondary FortiGate.
To verify the HA session cache on the secondary FortiGate:
# diagnose ips share list
HA Session Cache
client=10.1.100.178:57218 server=172.16.200.177:102
service=39, ignor... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,179 | System
Sample log on current primary FortiGate:
# execute log display
304 logs found.
10 logs returned.
28.8% of logs has been searched.
1: date=2021-06-04 time=16:54:40 eventtime=1622850881110547135 tz="-0700" logid="1059028704"
type="utm" subtype="app-ctrl" eventtype="signature" level="information" vd="vd1" appid=446... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,180 | System
npu_state=0x003c94 ips_offload
npu info: flag=0x81/0x81, offload=8/8, ips_offload=1/1, epid=71/71, ipid=134/132,
vlan=0x0000/0x0000
vlifid=134/132, vtag_in=0x0000/0x0000 in_npu=1/1, out_npu=1/1, fwd_en=0/0, qid=10/10
The server and client IPs, ports, and NPU state remain the same.
Sample log on new primary Forti... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,181 | System
is_autoscale_master()=1
debugzone
global: 56 49 b3 02 f2 b7 5b 82 ec 2d c2 1a ff 80 8c 79
root: bf 18 cf 83 1e 04 c3 04 4c e4 66 bc 38 fe 3a dc
all: 77 06 d0 89 6e 06 c0 86 17 98 53 72 33 85 ae ff
checksum
global: 56 49 b3 02 f2 b7 5b 82 ec 2d c2 1a ff 80 8c 79
root: bf 18 cf 83 1e 04 c3 04 4c e4 66 bc 38 fe 3a ... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,182 | System
interface that the VLAN subinterface is added to. Redundant or 802.3ad aggregate interfaces are assigned the VMAC
address of the first interface in the redundant or aggregate list.
If a cluster is operating in transparent mode with an automatic VMAC assignment method, FGCP assigns a VMAC
address to the primary d... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,183 | System
If you disable sending gratuitous ARP packets, it is recommended to enable the link-failed-signal setting. The
linked-fail-signal alerts the connected switches of a failed link, which triggers them to react immediately to the
changes.
For more information about gratuitous ARP packets see RFC 826 and RFC 3927.
De... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,184 | System
In a 48-bit MAC address, the U/L bit refers to the second least significant bit in the first octet of
the hexadecimal MAC address. When this bit is 0, it indicates that the MAC address is
Universal, meaning that it is assigned by a central authority. When this bit is 1, it indicates that
the MAC address is Local... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,185 | System
The logic uses the vcluster ID, group ID, and physical index variables to determine VMAC addresses as summarized in
the following table:
Logic Vcluster ID Group ID Physical index
Logic 1 0 or 1 Greater than 255 Less than 128
Logic 2 0 or 1 Less than 256 Less than 128
Logic 3 0 or 1 Less than 256 Greater than 127... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,186 | System
Logic 2: vcluster ID 0 & 1, group ID < 256, and physical index < 128
The start of the VMAC address is always 00:09:0f:09:--:-- with the last 16 bits defined as follows:
Group ID Vcluster ID Physical index
- - - - - - - - : - - - - - - - - -
This example uses group ID = 200, vcluster ID = 1, and interfaces with p... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,187 | System
l 110 = 12
l Vcluster ID = 1
l Interfaces:
l port40 physical index = 230
l 230 – 128 = 102
l 10210 = 11001102
l port45 physical index = 240
l 240 – 128 = 112
l 11210 = 11100002
l port50 physical index = 250
l 250 – 128 = 122
l 12210 = 11110102
Resulting in these VMAC addresses:
Interface VMAC binary (last 24 bit... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,188 | System
l port3 physical index = 910
l 910 = 00000010012
Resulting in these VMAC addresses:
Interface VMAC binary (last 24 bits) VMAC hex (full)
Preset bits Physical index Vcluster
ID Group ID
port1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 1 0 1 0 0 1 1 1 0 e0:23:ff:fc:03:4e
port2 1 1 1 1 1 1 0 0 0 0 0 0 0 1 1 0 0 1 0 0 1 1 1 0 e0... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,189 | System
You can diagnose packet loss by pinging from one cluster to the other, or by pinging both of the clusters from a device
within the broadcast domain.
To check for a MAC address conflict in a HA cluster:
1. On Cluster_1 and Cluster_2, check the VMAC address (Current_HWaddr) used in an interface on the primary
devi... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,190 | System
This example is for demonstration purposes only. In a normal failover, TLS sessions from
clients will automatically be able to re-establish using an abbreviated handshake through the
new primary unit.
To verify if an abbreviated TLS handshake is used after HA failover:
1. On the client using OpenSSL, open a new ... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,191 | System
This example assumes ZTNA and EMS server settings are already configured.
To configure the HA settings:
config system ha
set group-name "501E"
set mode a-p
set password **********
set hbdev "ha" 0
set session-pickup enable
set override disable
set monitor "port1" "port2"
end
To verify that the proxy sessions are... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,192 | System
expire : 597
LAN:
bytes_in=2093 bytes_out=5753
WAN:
bytes_in=2024 bytes_out=1235
b. Apply a filter to WAD debug to diagnose the wad informer process:
501E-primary # diagnose test application wad 2400
Set diagnosis process: type=informer index=0 pid=305
c. Show the user cache from the WAD infor... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,193 | System
service="HTTPS" proto=6 action="accept" policyid=1 policytype="proxy-policy"
poluuid="ea7a8a04-a56e-51ec-9d7b-90d24b3a28e9" policyname="ztna" duration=5
user="localuser1" gatewayid=1 vip="ztna" accessproxy="ztna"
clientdeviceid="EF73C831C3FE4FF195A5B2030B******" clientdevicetags="FCTEMS8821000000_all_
registered... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,194 | System
Basic configuration
To configure the FGCP cluster in the GUI:
1. On the primary FortiGate (FG-1800F-DC), go to System > HA.
2. Configure the following settings:
Mode Active-Passive
Device priority 128
Group ID 0
Group name Example_cluster
Password Enter a password.
Session pickup Enable this setting.
Monitor int... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,195 | System
To configure the FGCP cluster in the CLI:
1. Configure the primary FortiGate (FG-1800F-DC):
config system ha
set group-name "Example_cluster"
set mode a-p
set password **********
set hbdev "ha2" 0 "ha1" 0
set session-pickup enable
set override disable
set monitor "port5" "port6"
end
2. Configure the secondary Fo... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,196 | System
memory=22%
HBDEV stats:
FG180FTK*******1(updated 4 seconds ago):
ha2: physical/10000full, up, rx-bytes/packets/dropped/errors=18367581/33512/0/0,
tx=9563450/16609/0/0
ha1: physical/10000full, up, rx-bytes/packets/dropped/errors=11543018/22166/0/0,
tx=12359673/22151/0/0
FG180FTK*******2(updated 5 seconds ago):
ha... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,197 | System
Secondary: FG180FTK*******2, HA operating index = 1
Primary: FG180FTK*******1, HA operating index = 0
Testing synchronization in the cluster
Based on the preceding example, the interface and firewall policy configurations are changed on the primary FortiGate.
These configuration changes and sessions are synchron... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,198 | System
a. Verify the interface settings:
show system interface
config system interface
...
edit "port5"
set vdom "root"
set ip 10.1.100.1 255.255.255.0
set allowaccess ping https ssh http telnet
set type physical
set alias "To_Client_PC"
set snmp-index 9
config ipv6
set ip6-address 2000:10:1:100::1/64
set ip6-allowacce... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,199 | System
checksum
global: 4e 15 af c3 c6 87 32 f5 69 5c b7 33 b1 8b 27 12
root: 4a 52 e4 f1 6a 2b eb 7d 84 7d f1 48 50 93 fe d9
all: 95 4e 92 c3 39 75 8e 0e db 83 8d b7 b2 b1 9f 04
To test session synchronization in the FGCP cluster:
1. On PC1, verify the IP address and gateway:
root@pc1:~# ifconfig eth1
eth1 Link encap:... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,200 | System
reply-shaper=
per_ip_shaper=
class_id=0 ha_id=0 policy_dir=0 tunnel=/ vlan_cos=0/255
state=may_dirty npu synced log-start
statistic(bytes/packets/allow_err): org=112/2/1 reply=60/1/1 tuples=2
tx speed(Bps/kbps): 0/0 rx speed(Bps/kbps): 0/0
orgin->sink: org pre->post, reply pre->post dev=13->14/14->13 gwy=0.0.0.0... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,201 | System
# get system ha status
HA Health Status:
WARNING: FG180FTK*******1 has mondev down;
Model: FortiGate-1800F
Mode: HA A-P
Group Name: Example_cluster
Group ID: 0
Debug: 0
Cluster Uptime: 0 days 1:16:13
Cluster state change time: 2023-05-29 20:08:56
Primary selected using:
<2023/05/29 20:08:56> vcluster-1: FG180FTK... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,202 | System
number of vcluster: 1
vcluster 1: work 169.254.0.1
Primary: FG180FTK*******2, HA operating index = 0
Secondary: FG180FTK*******1, HA operating index = 1
4. On PC1, verify that the HTTP traffic remains uninterrupted:
...
74700K .......... .......... .......... .......... .......... 75% 100K 3m13s
74750K ............ | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,203 | System
How it works
In local-only and secondary-only modes, the specific cluster member is upgraded and sessions are
synchronized to it. The following tables show which members are upgraded based on the mode and where the upgrade
is initiated.
local-only
Upgrade method Outcome Recommendation
Initiate the upload or upgr... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,204 | System
Administrators can manually trigger failover to make Node-B the new primary when ready. This can be done by resetting
the HA uptime or changing device priorities, whichever method is desired. Traffic now passes through Node-B.
The upgraded system (Node-B) can be tested to verify that traffic can pass smoothly. I... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,205 | System
To configure the HA cluster:
config system ha
set group-id 260
set group-name "kkk"
set mode a-p
set password **********
set hbdev "port3" 0
set session-pickup enable
set upgrade-mode local-only
end
To perform the upgrade:
1. On the secondary member (FGVM02TM22027810), log in to the CLI console.
2. Execute a TFT... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,206 | System
vcluster-1: start_time=1692750718(2023-08-22 17:31:58), state/o/chg_time=2(work)/2
(work)/1692750721(2023-08-22 17:32:01)
pingsvr_flip_timeout/expire=3600s/0s
mondev: port1(prio=50,is_aggr=0,status=1) port7(prio=50,is_aggr=0,status=1)
port8(prio=50,is_aggr=0,status=1)
'FGVM02TM22027808': ha_prio/o=0/0, link_fail... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,207 | System
FGVM02TM22027810 # get system status
Version: FortiGate-VM64 v7.4.1,build2461,230828 (interim)
…
4. On the primary unit, verify that HA is still formed between the three members:
FGVM02TM22027808 # diagnose sys ha dump-by group
HA information.
group-id=260, group-name='kkk'
has_no_aes128_gcm_sha256_member=0
gmem... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,208 | System
Troubleshooting common HA formation errors
One member keeps shutting down during HA setup (hard drive failure):
If one member has a hard drive failure but the other does not, the one with the hard drive failure will be shut down during
HA setup. In this case, RMA the member to resolve the issue.
Split brain scen... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,209 | System
scanned by downstream FortiGates. FGSP can perform session synchronization of IPv4 and IPv6 TCP, SCTP, UDP,
ICMP, expectation, RSSO authenticated user logon information, and NAT sessions to keep the session tables
synchronized on all entities. If one of the FortiGates fails, the upstream load balancer should det... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,210 | System
Session synchronization link
The session synchronization link is an optional configuration that allows peers to synchronize sessions over a dedicated
interface instead of the interface in which the peer IP is routed. In this configuration, communications occur over L2
instead of L3. Configuring session synchroni... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,211 | System
set startip 172.20.120.10
set endip 172.20.120.20
next
end
In NAT mode, only sessions for route mode security policies are synchronized. FGSP is also available for FortiGate units
or virtual domains operating in transparent mode. Only sessions for normal transparent mode policies are synchronized.
The following ... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,212 | System
Example
This example uses two peer FortiGates. The load balancer is configured to send all sessions to Peer_1, and if Peer_1
fails, all traffic is sent to Peer_2.
To configure a basic FGSP peer setup:
These instructions assume that all FortiGates have been factory reset.
1. Make all the necessary connections as ... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,213 | System
To test the FGSP peer setup:
1. Initiate TCP traffic (like HTTP access) to go through Peer_1.
2. Check the session information:
# diagnose sys session filter src <IP_address>
# diagnose sys session list
3. Enter the same commands on Peer_2 to verify if the same session information appears.
Optional filters
Filte... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,214 | System
end
end
To synchronize only sessions with a particular destination address range:
config system standalone-cluster
config cluster-peer
edit 1
config session-sync-filter
set dstaddr6 2001:db8:0:2::/64
end
next
end
end
Session pickup
You can enable this setting to synchronize connectionless (UDP and ICMP) sessions... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,215 | System
next
end
end
Configuring unique group and member ID
FGSP can function between standalone FortiGates or between FGCP clusters. In either case, the standalonegroup-id must match between FGSP members, and the group-member-id must be unique for each FGCP cluster.
This allows each member to actively process traffic ... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,216 | System
There are some limitations when synchronizing sessions between FGCP clusters:
l All FortiGates must have the same model and generation, hardware configuration, and FortiOS version.
l A total of 16 clusters can share sessions.
l The configurations related to session tables should match. For example, the logical n... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,217 | System
config system interface
edit "port5"
set vdom "root"
set ip 10.10.10.2 255.255.255.0
set allowaccess ping https ssh snmp http telnet
next
end
In this example, cluster B uses port5 and its IP address, 10.10.10.2, is reachable from another cluster.
5. On cluster B, configure FGSP, including cluster and session syn... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,218 | System
Session synchronization in FGCP over FGSP
To provide full redundancy, FGCP clusters can be used in FGSP peering. This is called FGCP over FGSP. In these
complex environments, as well as in high performance, low latency data centers, using the FGCP session
synchronization interface is recommended, as it offloads ... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,219 | System
1. The session starts with the Client SYN packet.
2. As the session is established, Cluster-1A synchronizes the session with Cluster-1B over the heartbeat interface,
and with Cluster-2A over the session synchronization interface.
3. Cluster-2A then synchronizes the session with Cluster-2B over its heartbeat inte... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,220 | System
This example requires the following settings:
l The internal and outgoing interfaces of both FortiGates in the FGSP pair are in the same subnet.
l Both peers have layer 2 access with each other.
Due to the bouncing of traffic back to the session owner, performance degradation is
expected.
To configure FGT_1:
1. ... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,221 | System
To configure FGT_2:
1. Configure FGSP cluster attributes, including setting the peer IP to the IP address of FGT_1:
config system standalone-cluster
set standalone-group-id 1
set group-member-id 1
set layer2-connection available
unset session-sync-dev
config cluster-peer
edit 1
set peerip 10.2.2.1
next
end
end
2... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,222 | System
In this example, traffic from the internal network first hits FGT_1, but the return traffic is routed to FGT_2. Consequently,
return traffic is packed and sent from FGT_2 to FGT_1 using UDP encapsulation between two peer interfaces (port 3).
Traffic is then inspected by FGT_1.
Both of the FortiGates in this exam... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,223 | System
set utm-status enable
set av-profile "default"
set logtraffic all
set nat enable
next
end
To configure FGT_2:
1. Configure FGSP cluster attributes, including setting the peer IP to the IP address of FGT_1:
config system standalone-cluster
set standalone-group-id 1
set group-member-id 1
set layer2-connection unav... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,224 | System
In the case of an unavailable peer, once the original FGSP peer is back online, it will perform session sync. While it is
syncing, it will share a not-ready status over FGSP so peers will not bounce traffic back to it. Once session sync is
complete, it will share a ready status and accept sessions to fail back t... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,225 | System
Monitor routing prefix for FGSP session failover
FGSP now supports another method for determining a FGSP peer as unhealthy, by monitoring the health of a routing
prefix from RIP, OSPF or BGP. Using this method, FortiGate can prevent network isolation and blackholing by
recognizing a critical data path is down. F... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,226 | System
In the scenario that one of the peers (FGT_1) no longer sees a route to a prefix, disrupting the flow of traffic, instead of
causing network isolation and blackholing by bouncing the traffic back to the peer (FGT_1), traffic instead continues
through the healthy peer (FGT_2).
Note that in this case, traffic does... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,227 | System
S* 0.0.0.0/0 [10/0] via 172.16.200.254, wan1, [1/0]
C 10.1.100.0/24 is directly connected, port1
C 10.2.2.0/24 is directly connected, ha1
R 20.1.1.0/24 [120/2] via 172.16.200.3, wan1, 00:01:46, [1/0]
C 172.16.200.0/24 is directly connected, wan1
C 192.168.2.0/24 is directly connected, mgmt
b. As such, the health... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,228 | System
sync-other=1, sync-exp=1, standalone-sync=1, mtu=0
ipsec-tun-sync=1, encrypt-enabled=0
fgsp-peers-num=1, kernel-filters-num=1
fgsp-peers:
vdom=0, ip/port=10.2.2.2:708
fgsp_route_health=0
mon_prefix: vdom=root vrf=0, prefix=192.168.2.0(255.255.255.0) healthy=1
mon_prefix: vdom=root vrf=0, prefix=20.1.1.0(255.255.... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,229 | System
Topology
In this topology, there are three FGSP peer groups for each FortiGate. Sessions are synchronized between each
FortiGate and its peer groups. Redundancy is achieved by using two dedicated session sync device links for each peer
setup. There are a total of six peer IPs for each session synchronization dev... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,230 | System
set mtu 9216
next
end
5. Configure FGSP session synchronization:
config system standalone-cluster
config cluster-peer
edit 1
set peerip 10.1.1.2
next
edit 2
set peerip 10.2.2.2
next
edit 3
set peerip 10.1.1.3
next
edit 4
set peerip 10.2.2.3
next
edit 5
set peerip 10.1.1.4
next
edit 6
set peerip 10.2.2.4
next
end... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,231 | System
set mtu 9216
next
edit port6
set ip 10.2.2.2/24
set mtu-override enable
set mtu 9216
next
end
5. Configure FGSP session synchronization:
config system standalone-cluster
config cluster-peer
edit 1
set peerip 10.1.1.1
next
edit 2
set peerip 10.2.2.1
next
edit 3
set peerip 10.1.1.3
next
edit 4
set peerip 10.2.2.3
... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,232 | System
config system interface
edit port5
set ip 10.1.1.3/24
set mtu-override enable
set mtu 9216
next
edit port6
set ip 10.2.2.3/24
set mtu-override enable
set mtu 9216
next
end
5. Configure FGSP session synchronization:
config system standalone-cluster
config cluster-peer
edit 1
set peerip 10.1.1.1
next
edit 2
set pe... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,233 | System
config system session-ttl
set default 300
end
4. Configure the interfaces:
config system interface
edit port5
set ip 10.1.1.4/24
set mtu-override enable
set mtu 9216
next
edit port6
set ip 10.2.2.4/24
set mtu-override enable
set mtu 9216
next
end
5. Configure FGSP session synchronization:
config system standalon... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,234 | System
To upgrade the firmware in an FGSP deployment:
1. Switch all traffic to FGT-1:
a. Configure the load balancer or router that distributes traffic between the FortiGates to send all traffic to FGT-1.
2. Disconnect FGT-2 from the network.
Make sure to also disconnect the interfaces that allow heartbeat and synchron... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,235 | System
l The configurations related to session tables should match. For example, the logical names used in firewall policies,
IPsec interface names, VDOM names, firewall policy tables, and so on.
Different firmware versions
When operating in FGSP, the firmware needs to have compatible data structures and session synchr... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,236 | System
l Session synchronization between the FGSP peers (FGCP A-P Cluster 1 and 2) only occurs for the service specified
in the filter, which is HTTP/80.
l The preceding behavior is applicable when virtual clustering is configured. This example focuses on vdom2, which
belongs to vcluster2. FGT_A is the primary for vclu... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,237 | System
To configure the HA clusters:
1. Configure FGCP A-P Cluster 1 (use the same configuration for FGT_A and FGT_B):
config system ha
set group-id 146
set group-name "FGT_HA1"
set mode a-p
set password **********
set hbdev "wan2" 100 "ha" 50
set session-pickup enable
set session-pickup-nat enable
set vcluster-status ... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,238 | System
To configure the FGSP peers:
1. Configure FGT_A:
config system standalone-cluster
set standalone-group-id 1
set group-member-id 1
config cluster-peer
edit 1
set peervd "vdom2"
set peerip 10.1.1.2
set syncvd "vdom2"
config session-sync-filter
config custom-service
edit 1
set dst-port-range 80-80
next
end
end
next... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,239 | System
FGT_C (global) # diagnose sys ha fgsp-zone
Local standalone-member-id: 1
FGSP peer_num = 1
peer[1]: standalone-member-id=1, IP=10.1.1.1, vd=vdom2, prio=1
3. Initiate two sessions, HTTP and SSH.
4. Verify that the HTTP session is synchronized from Cluster 1 to Cluster 2.
a. Verify the session list of vdom2 on FGT... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,240 | System
b. Verify the session list of vdom2 on FGT_B:
FGT_B (vdom2) # diagnose sys session list
session info: proto=6 proto_state=01 duration=736 expire=3100 timeout=3600
flags=00000000 socktype=0 sockport=0 av_idx=0 use=3
origin-shaper=
reply-shaper=
per_ip_shaper=
class_id=0 ha_id=1:0 policy_dir=0 tunnel=/ vlan_cos=0/... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,241 | System
origin-shaper=
reply-shaper=
per_ip_shaper=
class_id=0 ha_id=1:0 policy_dir=0 tunnel=/ vlan_cos=0/255
state=log dirty may_dirty npu f00 syn_ses
statistic(bytes/packets/allow_err): org=0/0/0 reply=0/0/0 tuples=2
tx speed(Bps/kbps): 0/0 rx speed(Bps/kbps): 0/0
orgin->sink: org pre->post, reply pre->post dev=11->7/... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,242 | System
FGSP static site-to-site IPsec VPN setup
When configuring static site-to-site IPsec VPN between FGSP FortiGates and a remote gateway, the FGSP peers must
have the passive-mode setting enabled in the vpn ipsec phase1-interface configuration to function as an
IPsec responder. This is a required configuration in th... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,243 | System
next
end
2. Configure the phase 2 settings:
config vpn ipsec phase2-interface
edit "IPSec"
set phase1name "IPsec"
set proposal aes256-sha256
set dhgrp 14
next
end
To configure IPsec on the remote FortiGate:
1. Configure the phase 1 settings:
config vpn ipsec phase1-interface
edit "IPsec"
set type static
set set ... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,244 | System
Example
In this example, the FGSP peers are connected on port4 over 172.31.1.1-4/24. Each peer has a loopback interface, lb1,
with the same IP address. This loopback interface is used as the local gateway on each of the phase 1 connections to
avoid each FGSP member having different IPs on port2. The DC Router us... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,245 | System
1. Configure the FGSP settings:
config system standalone-cluster
set standalone-group-id 1
set group-member-id 1
config cluster-peer
edit 1
set peerip 172.31.1.2
next
edit 2
set peerip 172.31.1.3
next
edit 3
set peerip 172.31.1.4
next
end
end
2. Configure the VPN tunnel phase 1 settings:
config vpn ipsec phase1-... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,246 | System
peer0: vfid=0, peerip:port = 172.31.1.2:708, standalone_id=2
session-type: send=0, recv=0
packet-type: send=0, recv=0
peer1: vfid=0, peerip:port = 172.31.1.3:708, standalone_id=3
session-type: send=0, recv=0
packet-type: send=0, recv=0
peer2: vfid=0, peerip:port = 172.31.1.4:708, standalone_id=4
session-type: se... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,247 | System
...
standalone_id=15:
2. Initiate a dialup tunnel connection from the IPsec Client 2 FortiGate (192.168.1.2).
3. Verify the tunnel list for vpn1_1 on each peer. The output shows the bi-directional SAs for that particular tunnel are
synchronized to all participating FGSP peers.
a. DC1_VM1:
DC1_VM1 # diagnose vpn ... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,248 | System
SA: ref=3 options=682 type=00 soft=0 mtu=1280 expire=10466/0B replaywin=2048
seqno=10000001 esn=0 replaywin_lastseq=00000000 qat=0 rekey=0 hash_search_
len=1
life: type=01 bytes=0/0 timeout=10788/10800
dec: spi=a575b631 esp=aes key=16 5de449f75c7d70258f4972506dd164e2
ah=sha1 key=20 7e65d641be6bc52655619ff542c67c... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,249 | System
FGCP over FGSP per-tunnel failover for IPsec
For additional redundancy, an FGCP cluster on one site may form FGSP peering with FGCP clusters on other sites. The
FGCP over FGSP peers can still synchronize IPsec SAs and act as the primary gateway for individual tunnels for the
same dialup servers. When failover ha... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,250 | System
In a larger scale there may be many more members in the FGCP clusters, more FGSP peers, and more IPsec dialup
clients connecting. Each eligible FGSP peer will be the primary gateway for a set of dialup tunnels, and is in standby for
the rest of the tunnels. When the FGCP cluster is configured in A-P mode, the tu... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,251 | System
end
end
The configuration is automatically synchronized to DC2_VM2.
2. Configure DC2_VM3:
config system standalone-cluster
set standalone-group-id 2
set group-member-id 2
config cluster-peer
edit 1
set peerip 172.31.2.1
next
end
end
The configuration is automatically synchronized to DC2_VM4.
3. To configure the ... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,252 | System
To verify the configuration:
1. The FGCP HA cluster and the FGSP peering have formed. Verify the respective HA statuses.
a. Verify the FGCP cluster status on DC2_VM1:
DC2_VM1 # diagnose sys ha status
HA information
Statistics
traffic.local = s:0 p:439253 b:89121494
traffic.total = s:0 p:440309 b:89242174
activit... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,253 | System
phyindex=7: mac=00:09:0f:09:02:07, linkfail=1
phyindex=8: mac=00:09:0f:09:02:08, linkfail=1
phyindex=9: mac=00:09:0f:09:02:09, linkfail=1
standalone_id=3:
...
standalone_id=15:
c. Verify the FGCP cluster status on DC2_VM3:
DC2_VM3 # diagnose sys ha status
HA information
Statistics
traffic.local = s:0 p:443999 b:... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
3,254 | System
phyindex=5: mac=00:0c:29:bb:77:e1, linkfail=1
phyindex=6: mac=00:0c:29:bb:77:eb, linkfail=1
phyindex=7: mac=00:0c:29:bb:77:f5, linkfail=1
phyindex=8: mac=00:0c:29:bb:77:ff, linkfail=1
phyindex=9: mac=00:0c:29:bb:77:09, linkfail=1
standalone_id=3:
...
standalone_id=15:
2. Initiate traffic from PC1 to the Server. ... | https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.